BACnet is a communication protocol that lets HVAC equipment from different manufacturers talk to each other over a shared network. Short for “Building Automation and Control Networks,” it was developed by ASHRAE and published as standard 135-1995. It has since become the global open standard for building automation, used in everything from small office HVAC systems to hospital-wide climate, lighting, and security networks.
Before BACnet, building owners who bought a chiller from one company and an air handler from another often found the two couldn’t communicate without expensive custom programming. BACnet solved that by creating a common language, so devices from any manufacturer can exchange data on temperature, airflow, schedules, and alarms without proprietary translators.
How BACnet Represents HVAC Data
BACnet organizes every piece of information in a building as an “object” with properties. A fan’s on/off status, for example, is a Binary Input object (ON or OFF). A modulating valve that opens anywhere from 0% to 100% is an Analog Output object. A thermostat’s temperature reading is an Analog Input. These categories are standardized, so when a device publishes a data point, its meaning is immediately clear to any other BACnet device on the network. A temperature sensor reports directly in degrees Celsius or Fahrenheit with no ambiguity, and no need to cross-reference a manufacturer’s documentation to decode what the number means.
Beyond simple sensor readings, BACnet defines objects for scheduling, trending, and alarming. A Schedule object can automatically write commands to other devices at set times: turn lights to 100% at 7:00 a.m., ramp down the air handler at 6:00 p.m. Trend Log objects record historical data for energy analysis, and Notification objects push alarms when something goes wrong. The current standard defines 54 object types, covering nearly every function a modern building needs.
Common HVAC Equipment That Uses BACnet
BACnet is widely used across chillers, boilers, air handlers, variable air volume (VAV) boxes, and rooftop units. In a typical commercial building, each of these devices connects to a BACnet network and reports its operating data (supply air temperature, discharge pressure, fan speed) to a central building automation system. From there, a facility manager can monitor and adjust the entire mechanical plant through a single interface, even if the equipment came from five different vendors.
BACnet/IP vs. BACnet MS/TP
BACnet can run over different physical wiring, and the two most common options serve very different building sizes.
BACnet MS/TP (Master-Slave/Token-Passing) runs over RS-485 serial wiring in a daisy-chain configuration. It tops out at 115.2 kbps, which is plenty for a small or medium building with fewer than about 50 devices. The cabling is inexpensive, and installation is straightforward for standalone HVAC and lighting systems in offices, retail spaces, or small facilities.
BACnet/IP runs over standard Ethernet and IP networks, the same infrastructure your IT department already manages. Speeds reach 1 Gbps or higher, making it the choice for large-scale facilities: university campuses with thousands of devices across multiple buildings, hospitals where HVAC, lighting, and security all demand real-time monitoring, or smart city projects integrating traffic control and environmental sensors. Because it shares existing network infrastructure, BACnet/IP also makes remote access and cloud-based analytics far simpler to set up.
Many larger buildings use both. BACnet/IP connects high-level controllers and the building management server, while MS/TP handles the field-level devices (individual VAV boxes, sensors, actuators) that don’t need high-speed connections.
Why BACnet Instead of Other Protocols
The two main alternatives in building automation are Modbus and LonWorks, and BACnet’s biggest advantage over both is what engineers call its “self-descriptive ontology.” In plain terms: BACnet data points carry their own meaning. When you read a value from a BACnet device, you know it’s a temperature in degrees Celsius or a damper position in percent open. With Modbus, a register is just a number. You have to look up the manufacturer’s documentation to figure out what that number represents, what units it uses, and how to interpret it. That difference adds real time and cost during installation and troubleshooting.
BACnet is also an open, internationally recognized standard (ISO 16484-5), which protects building owners from vendor lock-in. You can replace a controller from one manufacturer with a BTL-certified controller from another and expect it to work on the same network. Modbus is also open but lacks BACnet’s built-in semantics, while LonWorks uses a more proprietary ecosystem that can limit flexibility.
Scalability is another strength. BACnet works on a small RS-485 bus with a handful of devices and scales to enterprise IP architectures spanning entire campuses, all within the same protocol framework.
BTL Certification and Interoperability
Just because a product claims BACnet compatibility doesn’t guarantee it will integrate smoothly. That’s where BTL (BACnet Testing Laboratories) certification comes in. Products that carry the BTL Mark have been independently tested by a Recognized BACnet Testing Organization to confirm they correctly implement their specified BACnet features. The testing is rigorous enough to catch implementation errors before a product reaches the market.
If you’re specifying equipment for a new building or retrofit, looking for the BTL Mark is the simplest way to reduce integration headaches. You can also search the online BTL Listing database to verify a product’s certification and see exactly which BACnet features it supports.
Device Roles in a BACnet Network
BACnet defines standardized device profiles so you know what role a piece of hardware plays on the network. The two most common in HVAC are the Building Controller (B-BC), which typically serves as the main supervisory controller for an entire building or large subsystem, and the Advanced Application Controller (B-AAC), which handles a specific mechanical system like an air handling unit or chiller plant. There are eight profiles in total, ranging from simple sensors to full building-level servers. These profiles set expectations for what each device can do, making it easier to design a system and predict how devices will interact.
BACnet Secure Connect
Traditional BACnet networks were designed for isolated building systems and lacked built-in security. As more buildings connect to corporate IT networks and the cloud, that became a serious gap. BACnet Secure Connect (BACnet/SC) addresses it by adding peer authentication and message encryption using WebSockets and TLS, the same encryption technology that protects online banking. Devices verify each other’s identity before exchanging data, and all communication is encrypted in transit. For any building connecting its automation system to an IP network, BACnet/SC is the path to doing it without exposing control systems to unauthorized access.