Theme Open building automation
BACnet in brief
BACnet is a communication protocol for building automation and control systems. ANSI/ASHRAE Standard 135 and ISO 16484-5 describe objects, properties and services through which ventilation, heating, cooling, lighting and supervisory systems can exchange information.
In context
The important idea is not merely that two products exchange packets. They can express data through a shared object model: an analogue value can carry a present value, unit and status; a schedule can be represented as a schedule. This creates a stronger basis for interoperability, but does not guarantee an understandable or secure facility.
What happens in a real building?
An air-handling unit can expose supply temperature, fan command, operating mode and alarms as BACnet objects. A BMS can read values, change permitted setpoints and subscribe to changes. The integrator avoids inventing a transport format for every vendor.
An open protocol reduces technical friction. Open information reduces dependency across the lifecycle.
Interoperability is a verifiable outcome
Two compliant BACnet products can still produce an expensive integration. Object selection, naming, units, command priorities, alarm logic and supported services must align with project use cases. BTL certification provides valuable product evidence, but does not replace site- and function-specific acceptance tests.
BACnet/IP and BACnet/SC
BACnet can use several data links. BACnet/IP is common on IP networks. BACnet Secure Connect, BACnet/SC, is an addendum using WebSocket and TLS for secure communication and is designed to work more naturally with modern IP infrastructure. It does not automatically provide sound segmentation, certificate governance or least privilege. The security architecture still needs an owner.
Five requirements before procurement
- An object and naming standard linked to stable asset identities.
- Mandatory objects, properties and services for each function.
- Rules for units, status, timestamps, command priority and alarms.
- Network, identity and certificate architecture, including BACnet/SC where appropriate.
- Machine-readable delivery, test cases and post-handover change ownership.
When is BACnet right?
BACnet is a natural integration choice within building automation, particularly where multiple suppliers meet a long asset life. A governed API or data platform can be a better next interface for enterprise systems, broad analytics or external digital services. Do not expose the automation network’s full internal structure merely because the protocol makes it reachable.
HubMind’s view
BACnet becomes strategic when the client owns the meaning above the protocol. Require testable information deliveries, clear identity and a secure lifecycle. The standard can then become a platform for progress rather than a new form of lock-in.
Related concepts
Related: BMS, BAS, OPC UA and data governance.
Scope and freshness
This page covers BACnet under ANSI/ASHRAE 135 and ISO 16484-5, including BACnet/SC as a secure IP transport option. Reviewed 31 August 2026; review again for a new standard edition or changed BACnet/SC guidance.