BACnet (Building Automation and Control Networks) is an open communication protocol for building automation systems, developed by ASHRAE and standardised as ASHRAE 135 and BS EN ISO 16484-5. Because it isn't owned by any manufacturer, any BACnet-compliant device can exchange data with any other, regardless of who made it.
Every time a facilities manager inherits a BMS that can't talk to the fire alarm, the lighting controls, or the energy meters, the same question comes up: why can't these systems just communicate with each other? In most cases it's because they were installed using different proprietary protocols, each manufacturer's systems speaking their own language with no common ground. BACnet exists to solve exactly that, and understanding what it is, how it works, and what it means for your building matters for anyone responsible for commercial building operations.
BACnet — Building Automation and Control Networks — is an open communication protocol designed specifically for building automation systems. It was developed by ASHRAE (the American Society of Heating, Refrigerating and Air-Conditioning Engineers) and is standardised internationally as ASHRAE 135 and BS EN ISO 16484-5. The important word is open: BACnet is not owned by any single manufacturer, and any equipment that implements the standard correctly can communicate with any other BACnet-compliant device, regardless of who made it.
Before BACnet, every BMS manufacturer used proprietary protocols. Trend controllers talked to Trend controllers. Siemens talked to Siemens. Honeywell talked to Honeywell. If you wanted to integrate systems from different manufacturers — or replace one manufacturer's controllers while keeping another's field devices — you needed protocol translation gateways, which added cost, complexity, and points of failure. BACnet removes that by providing a common language every compliant device can use.
The protocol defines how devices discover each other on the network, how they share data (object properties like temperature readings, setpoints, schedules), how they generate and distribute alarms, how trend data is logged and retrieved, and how schedules and calendars are managed. BS EN ISO 16484-5 specifies the data communication protocol for building automation and control systems, establishing the framework for interoperable building controls that isn't tied to any single vendor.
BACnet organises everything around objects and properties. Every sensor, actuator, setpoint, schedule, and alarm in the BMS is represented as a BACnet object with defined properties. A room temperature sensor, for example, is an Analog Input object with properties including Present Value (the current temperature reading), Object Name (a human-readable description), Status Flags (indicating whether the sensor is in alarm, overridden, or out of service), and Units (degrees Celsius).
That object model is what makes BACnet powerful for integration. When a chiller controller from Manufacturer A needs to read a flow temperature from a sensor connected to a controller from Manufacturer B, it simply reads the Present Value property of the relevant Analog Input object on the other controller. It doesn't need to know what brand the controller is, how it's programmed internally, or what its native protocol is. As long as both devices implement BACnet correctly, the data exchange works.
BACnet defines several network layer options for different physical media:
The single most important benefit of BACnet is that it prevents vendor lock-in. If your BMS is BACnet-native, you can maintain and expand the system using any competent BACnet integrator — you're not tied to the original installing contractor. That's a real commercial advantage: it enables competitive tendering for maintenance contracts, gives you negotiating leverage with service providers, and means you can change contractors without replacing hardware.
Modern commercial buildings have multiple systems that need to share data: BMS, fire alarm, lighting controls, access control, energy metering, lift management. BACnet lets these systems communicate directly without bespoke gateways. The fire alarm system can send a BACnet signal to the BMS to shut down AHUs and switch to smoke extract mode. The lighting controls can share occupancy data with the BMS to enable demand-controlled ventilation. The energy meters can feed consumption data into the BMS for trending and alarm generation.
Specifying BACnet doesn't just solve today's integration requirements — it protects against tomorrow's. When the building owner decides to add solar PV monitoring, connect electric vehicle chargers to the BMS, or integrate a smart building analytics platform, BACnet-compliant systems provide the data access layer without requiring custom development or proprietary middleware.
We'll assess your controls and provide a detailed quotation.
BACnet/IP runs over Ethernet networks at high speed (typically 100 Mbps or 1 Gbps) and is used for communication between plant controllers, supervisors, and head-end workstations. BACnet MS/TP runs over RS-485 serial wiring at lower speeds (up to 115.2 kbps) and is used for field-level networks connecting smaller controllers and I/O modules. Most modern BMS installations use both: IP as the backbone and MS/TP at the field level, with routers or multi-protocol controllers bridging between them.
In theory, yes — but in practice, interoperability depends on both devices implementing the same BACnet services and object types. BACnet defines conformance classes called BIBBs (BACnet Interoperability Building Blocks) that specify which capabilities a device supports. Two devices that share the same BIBBs will interoperate correctly. The BTL (BACnet Testing Laboratories) certification programme tests devices against the standard and publishes a list of certified products — specifying BTL-listed products reduces integration risk.
Yes, using protocol translation gateways. The most common scenario is integrating Modbus devices (energy meters, VFDs, generator controllers) with a BACnet BMS using a Modbus-to-BACnet gateway. These gateways map Modbus registers to BACnet objects, making the Modbus device appear as a native BACnet device to the BMS. The gateway adds cost and a potential point of failure, but it's a mature, well-understood approach.
Traditional BACnet/IP has no built-in encryption or authentication — traffic is sent in clear text and any device on the network can read or write to any other device. This is a known limitation, and the standard response is network segregation: putting the BMS on a dedicated VLAN with firewall rules preventing unauthorised access. BACnet/SC (Secure Connect) addresses this directly by adding TLS encryption and certificate-based authentication, but adoption is still in the early stages. NCSC (the UK's National Cyber Security Centre) guidance for operational technology recommends network segregation as the primary defence for building automation systems, with encrypted protocols like BACnet/SC as an additional layer where available.
BACnet MS/TP networks use RS-485 wiring, which requires end-of-line (EOL) termination resistors at both physical ends of the bus to prevent signal reflections. The standard termination is a 120-ohm resistor across the data pair at each end of the trunk cable. Missing or incorrectly placed EOL resistors are one of the most common causes of intermittent communication failures on BACnet MS/TP networks — the system appears to work during commissioning when only a few devices are online, then develops random communication dropouts as the network fills up. For a detailed guide on EOL resistors in BMS networks, see our article on end-of-line resistors and VAV termination.
On a practical level, BACnet has become the default specification for new BMS installations in UK commercial buildings. Most current specifications from M&E consultants require BACnet/IP as the primary communication protocol, with BTL certification required for all major system components. This is a direct result of the vendor lock-in problems that plagued earlier generations of building controls — consultants and building owners have learned, often through expensive experience, that proprietary systems create long-term cost and flexibility problems that open-protocol systems avoid.
The shift to BACnet also enables a new generation of building analytics platforms — products like Demand Logic, CIM, and IES — that sit on top of the BMS network and provide automated fault detection, energy analytics, and performance benchmarking. These platforms work by reading BACnet data directly from the controllers, without requiring any modification to the BMS programming. That kind of integration is only possible because BACnet provides a standardised data access layer any authorised system can read.
Alpha Controls designs and commissions BACnet-compliant BMS systems across London and the South East, working with Trend, Distech, and Schneider platforms. Whether you're specifying a new BMS installation, integrating third-party systems into an existing BACnet network, or diagnosing communication problems on a BACnet MS/TP field bus, get in touch or request a quote. We're happy to review your network architecture and give you practical advice on making your building systems work together.
Specialist BMS installation, commissioning, and maintenance across London and the South East. SafeContractor Approved, BCIA Member.
Our team of building automation specialists is ready to help you optimise your building's performance and efficiency.
Get in Touch
