The BACS decree (French decree 2020-887 on building automation and control systems) requires an interoperable automation system in your commercial buildings. BACnet remains the most widely deployed communication protocol to meet this requirement. You still need to know what it actually covers. Behind the acronym lie several network variants, a standardized object model and field limitations that building management reveals every day. This article explains how the protocol works, its variants and what we observe in operation.
Definition, origins and operation of the BACnet protocol
Building Automation and Control Networks: what the acronym means
BACnet - short for Building Automation and Control Networks - is an open communication protocol dedicated to building automation and control. An ISO standard since 2003, this BACnet standard lets equipment from different manufacturers communicate on the same network. A supervisory system can query a Schneider controller, a Siemens Desigo controller or a Johnson Controls Metasys without a proprietary gateway. To understand what a BMS is and how a BMS works, this multi-vendor interoperability system is the foundation to master.
ASHRAE, ANSI and ISO 16484-5 standardization
The ISO 16484-5 standard has been adopted in more than 30 countries. It guarantees that a device certified in Germany or Japan exposes the same objects and services as a device deployed in France.
BACnet was born in an ASHRAE committee (American Society of Heating, Refrigerating and Air-Conditioning Engineers). The standard was adopted as ANSI/ASHRAE 135 in 1995, then incorporated into the international standard ISO 16484-5 in 2003 (source: ASHRAE SSPC 135). This triple standardization anchoring sets BACnet apart from a proprietary protocol: in a CCTP (the French technical specification of a tender), requiring an open ISO-standardized protocol protects the building owner against technical lock-in.
From 1987 to BACnet/SC: thirty years of evolution of the standard
The ASHRAE SPC 135 committee began its work in 1987. The first ANSI standard came out in 1995, ISO adoption followed in 2003. In 2019, the BACnet/SC (Secure Connect) addendum added a communication layer secured by TLS 1.3 to meet the cybersecurity requirements of converged IP networks (source: ASHRAE SSPC 135). A standard that has held for more than 35 years is not a technology gamble.
Protocol layers: from the cable to the application
The layers of the BACnet protocol
Click each layer to explore its role in the BACnet stack
BACnet (ASHRAE 135 / ISO 16484-5) structures its exchanges in stacked layers, from physical transport up to application objects. Each layer performs a specific function in the communication between BMS devices.
Sources: ASHRAE 135-2020 standard, ISO 16484-5:2022, BACnet International
BACnet does not prescribe a single physical layer. Its architecture rests on three levels. The physical layer supports Ethernet, RS-485 (MS/TP) or LonTalk. The network layer encapsulates frames in IP packets (BACnet/IP) or in TLS websockets (BACnet/SC). The application layer exposes the protocol's objects and services, independently of the underlying cabling. This separation explains the flexibility of the protocol - and its integration complexity.
The object model: analog input, binary output and notification class
Each BACnet device exposes typed objects. The ASHRAE 135 standard defines more than 60 of them (source: ANSI/ASHRAE 135-2020). The most common in BMS:
- Analog input: a sensor reading (temperature, pressure, flow rate)
- Binary output: command of an actuator (valve, damper)
- Notification class: structured alarm reporting
Each object carries properties such as present value or status flags. This object model is what makes interoperability possible. It is also where field problems begin: an exposed object does not mean a controllable object.
BACnet services and client-server architecture
BACnet services are the "verbs" of the protocol. ReadProperty reads the value of an object. WriteProperty writes a setpoint to a controller. SubscribeCOV monitors changes. Who-Is / I-Am handle network discovery. The architecture works as client-server: the supervisory system (the client) queries the controllers (the servers) that expose their data. In operation, the ability to write via WriteProperty depends on the configuration delivered by the integrator - that is often where control stops.
BACnet/IP, BACnet MS/TP and BACnet/SC: which variant to choose?
BACnet/IP: the network layer of the supervisory system
BACnet/IP encapsulates BACnet frames in UDP/IP packets on port 47808 (source: ANSI/ASHRAE 135, Annex J). The data rate depends on the underlying Ethernet infrastructure: 100 Mbps to 1 Gbps in practice. It is the variant used for supervision and multi-site hypervision. Remote diagnostics are native. BACnet/IP requires a dedicated network or VLAN segmentation to isolate OT traffic from the office IT network. You find this variant between the supervisory server and the floor controllers.
BACnet versus other protocols and the limits of interoperability in the field
LonWorks: a protocol still present in commercial building portfolios
LonWorks (LON, ISO/IEC 14908) is still deployed on a significant share of the BMS installed in French commercial buildings before 2015. Each LON node carries its own intelligence. In the field, BACnet/LON coexistence is a common case: a BACnet gateway at supervisory level federates the two networks of BACnet and LON devices without replacing the field controllers. Since the chip discontinuation announced by Renesas, LonWorks is end-of-life: the network works, but new spare parts will no longer follow.
KNX: the standard of the electrical package and commercial building automation
KNX (ISO 14543-3) dominates the lighting and blinds package in commercial buildings. It covers little of heavy HVAC. BACnet and KNX coexist in a building depending on the technical package: BACnet for heating, ventilation and air conditioning, KNX for lighting. The KNX/BACnet gateway is a classic of the multi-package communication protocol.
Modbus: the industrial protocol that persists in boiler rooms
Modbus (RS-485 or TCP/IP) persists on boilers, chillers and energy meters. This protocol works by reading and writing raw registers. No typed objects and no structured alarms. The gap with BACnet is clear: Modbus carries values, BACnet carries meaning. The distinction echoes the one between a BMS and a supervision-only system (called GTC in France) in heating, ventilation and air conditioning (HVAC).
Syntactic interoperability vs semantic interoperability
Syntactic interoperability vs semantic interoperability
Syntactic interoperability guarantees that two BACnet devices exchange compliant frames. Semantic interoperability guarantees that they behave as expected when you write a setpoint to them. In the field, the gap is huge. BACnet objects are often exposed as read-only when they should be writable. The manufacturer's PICS is almost never checked after commissioning.
- A binary output locked by the manufacturer
- A writable flag missing from the delivered configuration
- A promising PICS contradicted by the reality of the controller
BTL compliance covers the syntactic layer, not the application behavior (source: BACnet Interest Group Europe)
Checking the BMS classes lets you cross-check this reading with the functional integration requirements.
BTL compliance and PICS: what the certification actually covers
BTL (BACnet Testing Laboratories) tests the protocol compliance of a specific device. The PICS documents the supported objects and services. More than 1,200 products are listed in the BTL directory (source: btl.org). BTL certification covers standardized test cases. A certified controller can very well be write-locked in the configuration delivered to the building.
BACnet and the BACS decree: what the protocol changes for compliance
What the BACS decree requires in terms of communication between equipment
The deadline for buildings of 70 to 290 kW has been postponed from 1 January 2027 to 1 January 2030 by Decree No. 2025-1343 of 26 December 2025 (source: Légifrance).
The BACS decree No. 2020-887 requires a building automation and control system able to communicate with the building's technical equipment. The text requires specific functions - setpoint management, consumption monitoring, alarm reporting - without naming BACnet. The requirement for an interoperable system de facto points to open, standardized protocols. Buildings above 290 kW have had to comply since 1 January 2025 (source: Légifrance, decree No. 2020-887). To understand the interoperability required by the BACS decree, implementation relies on an ISO-standardized building management protocol.
What BACnet concretely enables for compliance
BACnet covers the three functions required by the decree:
- Setpoint management for temperature and ventilation via WriteProperty on the HVAC controllers
- Energy consumption monitoring via metering objects (accumulator, pulse converter)
- Structured alarm reporting via notification class and event enrollment
BACnet relies on an application model that makes these functions auditable. If the objects are not correctly configured in the BMS, the bus exists but the heating, ventilation and air conditioning (HVAC) function is not delivered (source: Légifrance, decree No. 2020-887, article 1).
Controlling an existing BMS without replacing it: gateways and protocol coexistence
In an existing portfolio, BACnet, LonWorks and Modbus coexist. BACnet/LON gateways and BACnet/Modbus gateways federate these protocols under a single supervisory system without works on the field controllers. This protocol coexistence is what Foobot handles every day: controlling your BMS over BACnet or LON via the existing supervisory system, without replacing the infrastructure in place.
How does Foobot use BACnet day to day on your BMS?
BMS advisory: auditing the BACnet configuration of your installation
When Foobot audits a BMS, the first step is to check the BACnet configuration. Do the exposed objects match the physical equipment? Are the points writable? Does the manufacturer's PICS reflect the reality in the field? This is BMS advisory applied to the protocol: we do not replace the BMS, we check that it keeps its promise.
AI Control: regulating HVAC every 15 minutes via BACnet
The Foobot digital twin writes temperature and flow rate setpoints to the BACnet controllers via WriteProperty, every 15 minutes, 24/7. The protocol is the command channel. Without BACnet (or LON), no AI Control. BACnet is not one more tool in the stack: it is the pipe through which every AI decision flows.
BACnet and LonWorks: controlling multi-protocol BMS without changing everything
Before replacing your LON controllers with BACnet/IP, check whether a software gateway at supervisory level would not be enough. The cost is divided by ten and the result is immediate.
Foobot integrates with BMS that mix BACnet and LonWorks (LON). Integration goes through the multi-protocol controller or directly through the supervisory layer, with no added hardware. Protocol coexistence is not an obstacle to AI control: it is our daily work. Before launching a hardware replacement, we recommend carrying out the obsolescence audit of your installation.
Field comparison - real operating criteria
| Criterion | BACnet/IP | BACnet MS/TP | BACnet/SC |
|---|---|---|---|
| Actual data rate in operation | 100 Mbps to 1 Gbps (Ethernet) | 9,600 to 76,800 baud (RS-485) | Ethernet data rate via TLS 1.3 websocket |
| Max devices per segment | Limited by the IP infrastructure | 128 addresses per segment | Limited by the IP infrastructure |
| Remote diagnostics | ✓ Native | ✗ BACnet/IP router required | ✓ Native - traverses firewalls |
| Compatibility with controllers > 10 years old | ✓ Broad - most support IP | ✓ Very broad - majority of the installed base | ✗ Rare - 2019 addendum, few compatible controllers |
| Network requirements | ~ Dedicated VLAN or IT/OT segmentation | ✓ None - standalone serial bus | ✗ PKI - X.509 certificates + TLS infrastructure |
| Upgrade cost | ~ Moderate - Ethernet switch + VLAN | ✓ None - already in place | ✗ High - firmware + PKI + training |
Sources: ANSI/ASHRAE 135-2020 (Annex J, clause 9) - ASHRAE SSPC 135 (addendum 135-2016bj)
From audit to control: the 5 phases of a BACnet project
Explore each phase to understand the actions, deliverables and key indicators
A BACnet control project is structured in progressive phases. Each phase calls on specific skills and produces measurable deliverables. Click a phase to explore the details.
Sources: ASHRAE 135-2020, ISO 16484 standard, field feedback on commercial building BMS 2024-2025
Moving from the BACnet protocol to concrete energy control
The 5 key steps to make the most of your existing BACnet infrastructure
Your building already communicates over BACnet but the equipment has been running on fixed sequences since commissioning. Here is the roadmap to turn this technical base into real savings, without replacing your HVAC equipment.
- Number and types of accessible BACnet points (AI, AO, BI, BO, AV, BV)
- State of the control sequences programmed in the controllers
- Actual interoperability between multi-brand controllers
- Available historical data (trends, alarms, logs)
- Detection of "ghost" points: declared but never updated
- AHUs on manual override at night or at weekends (30% of cases)
- Overlapping heating and cooling setpoints (dead band too narrow)
- Fixed-speed pumps and fans even though drives are installed
- Morning optimal start too early (sometimes 2 hours before actual occupancy)
- Heating curves never recalibrated after a change in how the premises are used
- Native BACnet/IP read/write (no additional gateway)
- Predictive algorithms based on weather, thermal inertia and occupancy
- Optimized start: the AI calculates the latest possible start time (AI Optimal Start)
- Continuous setpoint adjustment without human intervention
- Comfort maintained: upper and lower limits remain guaranteed
- Energy baseline established on 12 months of historical BACnet data
- Adjustments for heating degree days (HDD) and actual occupancy rate
- Monthly report: kWh avoided, euros saved, tCO2e reduced
- Compliance with Décret tertiaire requirements (justification of actions)
- Full transparency: the raw data is accessible to the client
- Automatic drift detection (alarm if consumption exceeds the model)
- Adaptation to changes of use (new floor occupied, modified hours)
- Quarterly performance reports with recommendations
- Human support alongside the AI (no black box)
- Décret tertiaire trajectory tracked year after year (-40% in 2030, -50% in 2040)
Is your building already equipped with BACnet?
Let's assess together the savings potential without works.
Sources: ASHRAE BACnet Committee 2024, IPMVP protocol (EVO), ADEME - Technical management of commercial buildings 2025
FAQ - BACnet
What is the BACnet protocol?
BACnet (Building Automation and Control Network) is an open communication protocol standardized as ISO 16484-5. It lets the equipment of a commercial building - controllers, sensors, supervisory system - communicate with each other regardless of the manufacturer.
How does BACnet work?
BACnet relies on an object model (analog input, binary output) and services (ReadProperty, WriteProperty). The application layer communicates in a client-server architecture: the supervisory system reads from and writes to the controllers, which expose their objects and properties.
What is the difference between the BACnet protocol and Modbus?
BACnet structures data into typed objects with standardized properties. Modbus works by reading and writing raw registers, without an object model. BACnet also handles structured alarms and change-of-value subscriptions, which Modbus does not cover.
BACnet IP vs BACnet MS/TP: what are the differences?
BACnet IP encapsulates frames in UDP packets over an Ethernet network. BACnet MS/TP uses an RS-485 serial bus with token passing between devices (128 addresses maximum per segment). Data rate and remote diagnostics favor BACnet IP.
What are the advantages of BACnet for building management?
BACnet brings multi-vendor interoperability standardized as an ISO standard. This protocol federates HVAC, lighting and meters under a single supervisory system. The object model makes maintenance, structured alarms and BACS compliance easier.
How do you implement BACnet in a commercial building?
Implementation starts with an audit of the existing installation. A BACnet gateway federates the protocols already in place (LON, Modbus). The PICS of each controller must be checked to confirm that the objects are actually writable in operation.
What does interoperable mean under the BACS decree?
The BACS decree requires an automation system able to communicate with all of the building's technical equipment. Interoperability implies an open ISO-standardized protocol such as BACnet, not a proprietary bus locked by a single manufacturer.