A vendor asked for my BACnet information — what do I send them?

Q: A vendor asked for my BACnet information — what do I send them?

In almost every case they want four things: a points list (object type, instance number and name for each point), the device instance IDs and IP addresses of the controllers, the network layout (which devices sit behind a BACnet router or on MS/TP trunks), and a statement of whether they will need read-only or read-write access. A CSV export from a network scan covers the first two in one step.

Short answer

In almost every case they want four things: a points list (object type, instance number and name for each point), the device instance IDs and IP addresses of the controllers, the network layout (which devices sit behind a BACnet router or on MS/TP trunks), and a statement of whether they will need read-only or read-write access. A CSV export from a network scan covers the first two in one step.

The checklist

Points list. Object type, object instance, point name, current value, units, and the device each point belongs to. This is the bulk of what they need. See what a points list is and how to produce one.
Device instance IDs. Every BACnet device has a unique instance number. Integrators address devices by this number, not by name, so a list of names alone will send them back to you.
IP addresses and port. Which subnet the controllers are on and whether they use the standard UDP port 47808 or something else.
Network topology. Are all devices on one IP subnet, or are some behind a BACnet router on an MS/TP trunk? Is there a BBMD, and where? If the vendor will connect from a different subnet or over a VPN, this determines whether discovery will work at all.
Access expectations. State plainly whether they are getting read-only access or whether they will be commanding points. If they will write, agree in advance on which BACnet priority level they may use — this is the single most common cause of a building being left in a bad state after an integration. See BACnet priority and stuck overrides.
A point of contact. Whoever maintains the control system, so the vendor is not guessing about what a cryptic point name means.

The fastest way to produce it

If you already have current documentation, send that. If you do not, a network scan produces items 1 and 2 in a few minutes. Easy BACnet was built for exactly this handoff: connect a phone to the building network, scan, and email the resulting CSV straight to the vendor. The export contains device ID, device name, device IP, object type, object number, point name, present value, units, and status for every point it found.

What to think twice about

Do not put the control network on the public internet to make a vendor's life easier. If they need remote access, use a VPN with an account you can revoke.
A points list is a map of your building's controls. It is not usually sensitive on its own, but combined with remote access it is a complete attack surface description. Send it to a named person, not a shared inbox.
Watch out for write access granted casually. Read-only integration is safe. Write access to a live plant is a commissioning activity and deserves a scheduled window and someone on site.
Check for duplicate device IDs before you send. Two devices claiming the same instance number will break the vendor's integration and waste a site visit. A scan will flag them.

A reasonable reply template

Attached is a CSV points list exported from a live scan on [date].
It covers [N] BACnet/IP devices on subnet [x.x.x.0/24], port 47808.

Columns: Device ID, Device Name, Device IP, Object Type,
Object Number, Point Name, Present Value, Units, Status.

Topology: [all devices on one IP subnet] / [devices 1001-1012 sit
behind a BACnet router at 10.x.x.x on an MS/TP trunk].

Access: read-only for now. Let us know if you need write access and
we will schedule a window and agree a priority level.

Technical contact: [name, email].