Practical guide
BACnet and BMS: validate integration by model
Check objects, services, releases, permissions and tests before promising device interoperability.
Two devices mentioning BACnet do not necessarily provide the functions a project needs. Validate integration against actual models and releases, available objects and services, licences and communications architecture.
What BACnet provides and what engineering must define
BACnet is the building automation communications protocol defined by ASHRAE Standard 135. It provides a common structure for information exchange. Point selection, data quality, command permissions and fault responses remain engineering and operations decisions.
A BACnet Testing Laboratories (BTL) listing provides testing evidence for the stated product and release. Check it against the installed model; it does not replace verification of every function in a particular integration.
Information to request
- Model, firmware, software, licences and the Protocol Implementation Conformance Statement (PICS).
- Objects, properties and services the project needs to exchange.
- Network architecture, transport type, communications owners and access controls.
- Naming conventions, units, schedules, time synchronisation and data quality handling.
Test a point list against explicit criteria
| Aspect | Agreed criterion | Evidence |
|---|---|---|
| Reading | Correct identity, unit, value and quality state. | Record checked against the source device. |
| Authorised command | Permissions, limits, priority and expected response. | Approved test with feedback and restoration. |
| Link loss | Communication loss indication and expected recovery. | Safe protocol and traceable event. |
Cybersecurity and integration boundaries
Define segmentation, access, change records and responsibilities before connecting networks. When evaluating secure communications features, verify both endpoints’ actual support and the required certificate or key management. The BACnet name alone does not guarantee a secure architecture.
BMS supervision does not authorise changes to life safety functions. Fire, smoke control and door interfaces require approved sequences and coordinated testing. Handover should provide the verified point list, limitations, change backups and outstanding actions; communicate compatibility by verified function.
How BBS organises the work
- Initial assessmentInventory, fault history and criticality.
- Intervention planScope, permissions, owners, contingency and acceptance.
- Execution and testingChange control and verification of authorised interfaces.
- Handover and follow-upEvidence, validated results and outstanding actions.
Sources and scope
Public reference sources checked on 5 October 2026. This BBS guide provides planning recommendations; applicable editions and requirements must be validated for each project.
LET’S TALK