# BACnet Protocol Explained: How It Works, Objects, BACnet/IP vs MS/TP and BACnet/SC Security

> What is the BACnet protocol and how does it work? The object model, BACnet/IP vs MS/TP, BACnet vs Modbus, PICS and BTL checks and a 6-step integration list.

Source: https://digitalbridge.com.tr/en/blog/bacnet-building-automation.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: IoT & Hardware
Published: 2026-10-04 · Updated: 2026-10-22

The BACnet protocol (Building Automation and Control Networks) is an open communication standard that lets building equipment such as chillers, air handlers, lighting and energy meters exchange data regardless of manufacturer. It is defined by ANSI/ASHRAE 135 and ISO 16484-5. Because it describes every device as standard "objects", one [building management system (BMS)](https://digitalbridge.com.tr/en/glossary.html#bms) can read and command many vendors' controllers.

## Key takeaways

- BACnet is an open, vendor-neutral protocol built for building automation; as of 2026 the current edition is ANSI/ASHRAE 135-2024.
- BACnet describes every measurement and command point as standard objects, such as Analog Input or Binary Output, accessed through read and write services.
- BACnet/IP runs on the Ethernet backbone, BACnet MS/TP on RS-485 field trunks, and BACnet/SC adds TLS encryption for new projects.
- A "BACnet compatible" claim should be verified at tender stage through the PICS document, device profile and BTL listing.
- A 2017 PNNL study found that correct use of controls could cut annual commercial building energy use by an average of 29%.

## What problem does BACnet solve, and where is it used?

Most buildings accumulate equipment from different contractors over many years. The chiller comes from one maker, the air handling unit's control panel from another and the fan coil thermostats from a third. Each works perfectly well on its own screen, but a central system can only see them side by side if they share a language.

BACnet was designed for exactly that. The [BACnet standard page](https://www.ashrae.org/technical-resources/bookstore/bacnet) of ASHRAE (the American Society of Heating, Refrigerating and Air-Conditioning Engineers) says the protocol was built specifically for the communication needs of HVAC (heating, ventilation and air conditioning) control, fire and life safety, energy management, lighting, physical access control and lift monitoring. The [official BACnet Committee site](https://bacnet.org/) lists ANSI/ASHRAE 135-2024 as the latest edition as of 2026, so this is a living standard that is still being revised.

We cover what a building management system does and which systems it pulls together in our [smart building BMS guide](https://digitalbridge.com.tr/en/blog/smart-building-bms-guide.html). This BACnet guide goes one layer down: what "BACnet compatible" in a specification really means, and how to verify it before you sign off an integration.

## Why does protocol choice matter in building automation?

Buildings are not a minor energy line. According to the [IEA's Energy Efficiency 2025 report, buildings chapter](https://www.iea.org/reports/energy-efficiency-2025/buildings), buildings account for around 30% of global energy demand. In Türkiye, the [Ministry of Energy and Natural Resources' Second National Energy Efficiency Action Plan](https://enerji.gov.tr/Media/Dizin/BHIM/tr/Duyurular/T%C3%BCrkiyeninEnerjiVerimlili%C4%9Fi2030StratejisiveIIUlusalEnerjiVerimlili%C4%9FiEylemPlan%C4%B1_202401161407.pdf) reports that buildings and services took 32.6% of final energy consumption in 2022.

Controlling building energy consumption starts with equipment that can share data. The value of automatic control has been measured:

> A 2017 study by the US Pacific Northwest National Laboratory (PNNL) found that widespread, correct use of controls could cut annual commercial building energy use by an average of 29%, yet only about 15% of US commercial buildings have building automation systems. ([PNNL – commercial building controls study](https://www.pnnl.gov/news-media/cut-us-commercial-building-energy-use-29-widespread-controls))

Protocol lock-in quietly blocks that savings potential. Buy a controller with a closed protocol and every future integration depends on the vendor's own software or an extra gateway. Security is a separate cost: [Verizon's 2026 Data Breach Investigations Report](https://www.verizon.com/business/resources/T1ae/reports/2026-dbir-data-breach-investigations-report.pdf) found that exploitation of vulnerabilities was the most common initial access vector for breaches, at 31%. A building control network left reachable from the internet is precisely that kind of entry point.

## How does BACnet work? Objects, properties and services

The strength of the BACnet protocol is a vendor-neutral data model. Three ideas are enough to follow any integration meeting.

**Objects.** Every measurement or command point is a standard object type. A temperature sensor is an Analog Input, a valve command an Analog Output, a fan run status a Binary Input and a setpoint an Analog Value. Schedule, Calendar, Trend Log and Notification Class objects standardise timetables, logging and alarms, and every device carries a single Device object that identifies it.

**Properties.** Each object has properties such as Present_Value, Units and Status_Flags (fault, alarm, out of service). Commandable objects include a 16-level priority array, so a fire mode command can override a routine schedule command. How doors should behave when the fire alarm trips is covered in our [access control and fire alarm integration](https://digitalbridge.com.tr/en/blog/access-control-fire-alarm-integration.html) guide.

**Services.** Devices use services to read and write those objects. Who-Is and I-Am discover devices on the network, while ReadProperty and WriteProperty read or change values. SubscribeCOV (change of value) sends updates only when a value changes, which is far lighter on the network than constant polling.

## What is the difference between BACnet/IP, MS/TP and BACnet/SC?

BACnet carries the same data model over different physical networks; MS/TP stands for Master-Slave/Token-Passing serial communication. These are the options you will meet most often on site:

| Transport | Physical medium | Typical use | Watch out for |
|---|---|---|---|
| BACnet/IP | Ethernet, UDP (default port 47808) | Supervisory controllers, BMS server, chiller and air handling unit (AHU) panels | Broadcasts do not cross subnets; a BBMD (BACnet Broadcast Management Device) is needed between them |
| BACnet MS/TP | RS-485 serial trunk | Fan coils, VAV (variable air volume) boxes, thermostats and other field devices | Baud rate, termination, duplicate MAC addresses and cable length |
| BACnet/SC | WebSocket over TLS with certificates | New projects, cloud links, traffic between network segments | Certificate management and hub design need planning; not all devices support it yet |
| Gateway (Modbus/KNX to BACnet) | Mixed | Legacy equipment without native BACnet | Undocumented point mapping makes maintenance painful |

Classic BACnet/IP and MS/TP installations in the field run, in practice, without authentication or encryption: anyone on the network can read and write. BACnet Secure Connect (BACnet/SC) was developed to close that gap with TLS and certificates. We look at control-network risks and segmentation in more depth in [OT security for SCADA](https://digitalbridge.com.tr/en/blog/ot-security-scada.html).

## How does BACnet compare with Modbus, KNX and OPC UA?

BACnet is rarely the only protocol in building automation; on site it usually works alongside others. DALI and KNX are common for lighting, and [Modbus RTU or TCP](https://digitalbridge.com.tr/en/blog/modbus-rtu-vs-tcp.html) for energy analysers. If building data also has to reach production systems, understanding [how OPC UA works](https://digitalbridge.com.tr/en/blog/opc-ua-explained.html) helps you decide at which layer the two worlds should meet.

| Protocol | How it describes data | Typical use |
|---|---|---|
| BACnet | Standard objects with name, units and status; scheduling, alarm and trend services | HVAC, chillers, air handlers and site-wide BMS |
| Modbus | Numbered register addresses; meaning comes from the device manual | Energy analysers, meters, simple field devices |
| KNX | Room and building functions through group addresses | Room control, lighting, blinds and shutters |
| DALI | Addressing at luminaire and driver level | Lighting control |
| OPC UA | Rich information model with a built-in security layer | Production lines, machines and SCADA data |

## Six steps to verify a BACnet integration

"BACnet compatible" on a datasheet is not enough. A device may expose a few readable objects yet refuse writes, alarms or schedules. Working through this sequence moves the surprises from commissioning to the tender stage:

1. **Ask for the PICS.** The Protocol Implementation Conformance Statement declares which object types, services and transports the device supports. Without a PICS, a BACnet claim cannot be checked.
2. **Check the device profile.** The standard defines profiles such as B-BC (building controller), B-AAC (advanced application controller) and B-ASC (application specific controller). A fan coil may only need B-ASC, whereas a supervisory controller running schedules and alarms should be a B-BC.
3. **Look at the BTL listing.** Products that pass testing by BACnet Testing Laboratories (BTL), run under BACnet International, are listed. Listing is not mandatory, but it is a strong signal of interoperability.
4. **Build the points list.** For each device, record which object maps to which physical point, its units and whether it is writable. Confirm that device instance numbers are unique across the whole site.
5. **Draw the network.** Produce a diagram showing BACnet/IP subnets, BBMDs, MS/TP trunks and routers. Separate the BMS network from the corporate LAN and never expose UDP 47808 to the internet.
6. **Test on site.** Run a Who-Is discovery with a BACnet explorer, read and write a handful of critical points, and check COV subscriptions and alarm delivery. Attach the results to the commissioning report.

This six-step BACnet checklist is also useful when [choosing a remote monitoring platform](https://digitalbridge.com.tr/en/blog/remote-monitoring-iot-platform.html): ask which BACnet services its driver actually supports.

## How is BACnet data turned into energy savings?

Reading BACnet points is only half the job. The value appears when data is stored and analysed: which air handler runs outside working hours, which valve sits at 100% open, which zone has its setpoint overridden by hand every afternoon. Moving that data to the cloud or a central platform often involves a lightweight messaging layer such as [MQTT](https://digitalbridge.com.tr/en/blog/mqtt-protocol-industrial-iot.html). Answering questions such as out-of-hours running or valves stuck open also needs the right storage, and we compare the options in our guide to [time-series databases for sensor data](https://digitalbridge.com.tr/en/blog/time-series-database-iot-data.html).

Where buildings and production share a site, BACnet building data can sit alongside process data in [a SCADA system](https://digitalbridge.com.tr/en/blog/what-is-scada.html). In critical buildings such as hospitals, deciding what to optimise and what to leave untouched matters even more; we cover that in [hospital building energy management](https://digitalbridge.com.tr/en/blog/hospital-building-energy-management.html).

## How Digital Bridge delivers BACnet integration

Our [smart building BMS](https://digitalbridge.com.tr/en/industry-40/smart-building-bms.html) projects work with Modbus, BACnet, KNX and DALI. The approach runs in clear stages:

- **Discovery and requirements analysis.** We survey the site, collect the equipment inventory, any existing PICS documents and the network layout. Where legacy equipment has no BACnet interface, we define the gateway or extra hardware at this stage.
- **Pilot.** Rather than connecting the whole building at once, we bring one air handler or one floor online with its points list, alarms and trend logs. The pilot data sets the priorities for the next phase.
- **Integration.** We combine BACnet points with [energy monitoring and management](https://digitalbridge.com.tr/en/industry-40/energy-monitoring-management.html), and bring separate systems such as fire panels, IP cameras and access control with our own [SmartPass](https://digitalbridge.com.tr/en/smartpass.html) product into one panel through our [system integrations](https://digitalbridge.com.tr/en/technology-hardware/system-integrations.html) work. For dispersed estates we add a [remote monitoring](https://digitalbridge.com.tr/en/industry-40/remote-monitoring-saas.html) layer. Because the SmartPass dashboard shows how many staff, subcontractors and visitors are inside at any moment, it gives emergency teams information that complements BMS alarms.
- **Security.** Network separation, strong authentication for remote access and a path to BACnet/SC are planned as part of our [cyber security consultancy](https://digitalbridge.com.tr/en/consultancy/cyber-security.html).
- **Software and hardware from one team.** When a device has no usable protocol support, we can design the control board and firmware ourselves; the process is described in our [IoT device development process](https://digitalbridge.com.tr/en/blog/iot-device-development-process.html) article.

We do not sell off-the-shelf packages. After the requirements analysis we issue a written proposal setting out scope, phases and price, and the site assessment for Industry 4.0 projects is free of charge. We work across Türkiye, on site and remotely.

## Next step

The quickest way into a BACnet integration project is knowing which protocol your equipment already speaks. Send us your equipment list, any PICS documents and the building plans, and we will work out together which devices connect natively and which need a gateway. You can reach us through our [contact page](https://digitalbridge.com.tr/en/contact.html).

For more guides on sensors, connectivity and field hardware, browse all our [IoT and hardware articles](https://digitalbridge.com.tr/en/blog/topic/iot-donanim.html).

## Frequently Asked Questions

### What is BACnet used for?

BACnet is used so that devices in building automation systems can communicate with each other regardless of manufacturer. It standardises data exchange for HVAC control, chillers and air handlers, lighting, energy management, fire and life safety, access control and lift monitoring. As a result, a single building management system can monitor and command controllers from different vendors on one screen.

### What is the difference between BACnet and Modbus?

Modbus is a simple protocol that reads and writes numbered registers; you learn what each register means from the device manual. BACnet presents every point as a standard object with its name, units, status and alarm information, and it defines scheduling and alarm services as well. That is why BACnet is more common in building automation, while Modbus is more common in energy analysers and simple field devices.

### How do I choose between BACnet/IP and BACnet MS/TP?

The choice is usually made per device. Supervisory controllers and the BMS server connect over Ethernet using BACnet/IP, while large numbers of small field devices such as fan coils and thermostats sit on RS-485 trunks using MS/TP. MS/TP cabling is inexpensive, but bandwidth is limited and response times grow as more devices share a trunk.

### Is BACnet a secure protocol?

Classic BACnet/IP and MS/TP installations in practice run without authentication or encryption, so anyone with network access can read values and send commands. The BMS network should therefore be separated from the corporate LAN, remote access protected with strong authentication, and the BACnet port never exposed to the internet. New projects can adopt BACnet/SC, which uses TLS and certificates.

### What if older equipment does not support BACnet?

If the equipment offers Modbus, KNX or a vendor-specific interface, a gateway can translate those points into BACnet objects. If there is no communication interface at all, data can be collected with additional sensors or a control board. The right method is decided per device during the site survey, and the point mapping should always be documented.

### What drives the cost of a BACnet integration?

The main cost drivers are the number of devices and points to connect, whether existing equipment speaks BACnet natively, how many gateways and routers are needed, the condition of the MS/TP cabling, the licensing model of the BMS software and the commissioning tests. Security requirements such as BACnet/SC or network separation also shape the scope. A realistic budget can only be written after the survey produces a points list and the PICS documents have been reviewed.

### Why does a PICS document matter?

The PICS is the formal statement of which parts of BACnet a device actually implements. It tells you which object types can be read or written and whether alarm, scheduling and change-of-value services are available. Requesting it at tender stage lets you spot incompatibilities before they surface during commissioning, when they are far more disruptive to fix.
