BACnet Commissioning: Point Naming Matters More Than Wiring
The difference between a BACnet install that's still serviceable in five years and one that isn't lives in naming, not wiring. Get Object_Name and Device Instance conventions agreed before the first controller powers up.
The commissioning sequence that actually holds up
Lock the naming convention first
Agree a floor-system-point Object_Name and Description format across every trade before any controller ships. Auto-generated names like AI-1 or BO-14 are fine on the bench and unreadable on a BMS graphic five years later.
Confirm Device Instance uniqueness site-wide
Every BACnet device needs a unique Instance number across the full 0–4194302 range — not just within its own segment. Clashes between contractors on the same site are the most common cause of silent discovery failures.
Run Who-Is/I-Am and verify every controller answers
Broadcast a Who-Is across BACnet/IP and MS/TP segments and check the I-Am responses against your as-built device list — anything missing gets resolved before handover, not after.
Cross-check the points list against the PICS
Request the PICS (Protocol Implementation Conformance Statement) for every device before ordering, then verify the as-built points list against it during commissioning — not after the panel is wired shut.
Why naming discipline is the whole game
Device Instance range
Every BACnet device carries a unique Instance number in this range, valid across the entire network — the addressing base for Who-Is/I-Am discovery. Duplicate it anywhere on site and discovery breaks quietly.
Object_Name over auto-generated tags
Standard object types — AI/AO/AV, BI/BO/BV, multi-state, Device, Schedule, Calendar, Trend Log — are meaningless to a fault-finder unless Object_Name and Description carry the floor, system and point in plain language.
PICS checked at selection, not at handover
The PICS tells you exactly which object types and services a device supports before you commit to it. Reading it after wiring is finished only tells you what you got wrong.
Priority Array resolves conflicts, naming resolves confusion
The 16-level Priority Array lets multiple systems write to the same AO or BO without conflict — level 1 for life-safety override, level 8 for manual operator override, level 16 as default. None of that helps if nobody can find the point.
COV over polling, once names are trustworthy
Change-Of-Value subscriptions cut network load by reporting only real changes instead of continuous polling — but only pay off once the BMS graphics point to correctly named objects instead of guesswork.
Segmentation protects what naming organises
A dedicated VLAN for the BAS network, firewalled to UDP 47808 traffic only, with Foreign Device registration limited to known BBMD addresses, keeps a well-documented site well-documented.
What we deliver on a BACnet commissioning job
Documentation and verification you can hand to the facility team, not just a working system.
- Agreed Object_Name/Description naming convention, signed off before controllers are powered
- Device Instance register confirming site-wide uniqueness across BACnet/IP and MS/TP segments
- Who-Is/I-Am discovery log cross-checked against the as-built device list
- PICS review per device, checked against the specified points list before order placement
- Naming-convention document and points schedule handed over with the O&M package
Frequently asked questions
Why do auto-generated point names like AI-1 or BO-14 cause problems later?
They work fine for the commissioning engineer who wired them, but mean nothing to whoever troubleshoots the system in three years. A consistent floor-system-point convention in Object_Name turns a BMS graphic into something a technician can actually read at 2am.
What is a PICS and when should we ask for it?
A Protocol Implementation Conformance Statement lists exactly which BACnet object types and services a device supports. Request it during device selection — if you only check it after the panel is wired, any gap becomes a site visit instead of a spec change.
Does every BACnet device need a unique Device Instance number, or just within its subnet?
Unique across the entire site, not just the local segment — the Instance sits in a 0–4,194,302 range and is what Who-Is/I-Am discovery uses to address devices. Two contractors picking overlapping instance blocks on the same job is a recurring, avoidable failure.
Can BACnet/IP and MS/TP devices be commissioned together on one site?
Yes — most real installs mix BACnet/IP over UDP port 47808 with MS/TP segments over RS-485, joined by a router. Commissioning has to confirm broadcasts reach across both, which is where BBMD or Foreign Device registration usually needs checking.
What does BACnet/SC add that classic BACnet/IP and MS/TP don't have?
BACnet Secure Connect, finalised in 2020, adds TLS 1.3-encrypted WebSocket transport and X.509 certificate-based device authentication — addressing the lack of encryption and authentication in classic BACnet networks that now sit closer to IT infrastructure than they used to.
Commissioning a BACnet site and want a second set of eyes on the naming convention?
Send us the points list and device schedule — our engineers review PICS documents, Device Instance allocation and naming conventions before handover, not after.