BACnet basics for building owners

If you own or manage a commercial building, you have probably seen "BACnet" in a controls specification or heard a contractor promise that their system is "BACnet compatible". BACnet is the most widely used open communication protocol in building automation, and understanding the basics helps owners ask the right questions, avoid being locked into a single vendor, and get full value from their building data.

This guide explains what BACnet is, the key terms, and how to specify and verify a BACnet system.

What BACnet is

BACnet stands for Building Automation and Control Networks. It is a data communication protocol published as ANSI/ASHRAE Standard 135 and adopted internationally as ISO 16484-5. It defines how devices from different manufacturers exchange information: sensor readings, setpoints, alarms, schedules and trends.

BACnet is a common language, not a product. A BACnet controller from one manufacturer can share data with a BACnet front end from another, provided both support the same features. It does not define what a controller does internally or how a sequence is programmed.

Key concepts

Devices

Every BACnet device, such as a controller, router or workstation, has a unique device instance number on the network. Duplicate instance numbers cause communication failures, so a site-wide numbering plan is important.

Objects

Information inside a device is organized into standard objects. Common types include:

Each object has properties such as present value, units, status flags and description. Consistent, meaningful object names and descriptions make a system far easier to operate and integrate.

Services

Services are the actions devices perform: reading and writing properties, subscribing to changes of value (COV), sending alarms and events, synchronizing time, and discovering devices with Who-Is and I-Am messages. Not every device supports every service.

Priority array

Commandable objects such as outputs use a 16-level priority array. Higher priorities, such as life safety or manual operator override, take precedence over lower ones such as automatic control. Leftover manual overrides at a high priority are a common reason equipment fails to respond to its program, so operators should know how to find and release them.

Networks: IP and MS/TP

BACnet runs over several network types. The two most common in commercial buildings are:

• BACnet/IP: uses standard Ethernet and IP networks. Fast, flexible, and typically used for supervisory controllers, front ends and larger equipment.
• BACnet MS/TP: a serial RS-485 network used for field controllers such as VAV boxes and fan coils. Inexpensive and robust, but slower and more sensitive to wiring, termination and device count.

Routers connect MS/TP trunks to the IP network. Poorly designed MS/TP networks, with too many devices, wrong baud rates, missing terminations or mixed wiring, are a common source of slow graphics and intermittent communication.

BACnet Secure Connect

BACnet/SC is a newer addition to the standard that uses TLS encryption and certificate-based authentication over standard IP infrastructure, addressing the lack of built-in security in traditional BACnet/IP. Adoption is growing, and owners planning new systems or upgrades should ask whether products support it. See cybersecurity for building automation systems.

Interoperability documents

PICS

A Protocol Implementation Conformance Statement (PICS) is a manufacturer's document listing which BACnet objects, services and features a product supports. Comparing PICS for a controller and a front end shows whether they can work together as intended.

Device profiles and BIBBs

BACnet defines standard device profiles, such as building controller (B-BC), advanced application controller (B-AAC), application specific controller (B-ASC) and operator workstation (B-OWS). Profiles are built from BACnet Interoperability Building Blocks (BIBBs), which describe specific capabilities like scheduling, trending and alarming.

BTL listing

The BACnet Testing Laboratories (BTL) program tests products for conformance. BTL-listed products have been independently tested against their claimed profile, which gives far more confidence than a claim of "BACnet compatible". Specifying BTL-listed devices is a simple way to raise the baseline.

How owners can use BACnet well

1. Require native BACnet at the controller level, not proprietary controllers connected through a gateway, wherever possible.
2. Specify BTL listing and the device profile required for each controller type.
3. Require full access: programming tools, licences, passwords and editable program files should be turned over to the owner so another qualified contractor can service the system.
4. Set naming and numbering standards for devices, objects and points across your portfolio.
5. Define trending and alarming requirements so the data you need is captured.
6. Plan the IT side: coordinate IP addressing, VLANs, firewall rules and remote access with your IT group.
7. Verify at turnover: confirm device instance numbers, object names, trends, alarms and schedules match the specification.

Being "open" at the protocol level does not guarantee freedom from vendor lock-in. Many systems use BACnet for communication but require proprietary software to program controllers. Owners who want true serviceability should address tools, licensing and file access contractually.

BACnet and other protocols

Other protocols remain common: Modbus for meters, VFDs and some equipment; LonWorks in older buildings; and various proprietary protocols. Gateways translate between them and BACnet, but they add points of failure and often expose only a subset of data. For lab airflow controls and similar specialized systems, see air valve controls integration with BACnet. When planning an upgrade, the BAS upgrades and migration guide covers strategy.

Key takeaways

• BACnet is an open communication protocol (ASHRAE 135, ISO 16484-5), not a product or a control strategy.
• Objects, properties and services define how devices share data; consistent naming makes systems usable.
• BACnet/IP serves supervisory networks, MS/TP serves field devices, and BACnet/SC adds encryption and authentication.
• PICS, device profiles and BTL listing are the tools for verifying interoperability.
• Owners avoid lock-in by requiring tools, licences and program files at turnover, not just BACnet communication.