BACnet is arguably the most dominant communication protocol in Operational Technology (OT), and that’s not an accident. For over 40 years, the ASHRAE “BACnet Committee” has been working to guide the ongoing consensus around the development and adoption of new features for BACnet (aka ASHRAE/ANSI Standard 135).
With 11 currently operating working groups, the BACnet Committee continues to meet regularly to guide the evolution of the BACnet protocol. Our Co-Founder and CTO, Ping Yao, is also a participant in the Committee.
So with the start of another year, we thought it’d be a good idea to talk about what’s on the horizon for BACnet. What could the committee be thinking about adding, or changing, to keep BACnet evolving to keep pace with the IT/OT convergence we see everywhere?
And then we thought, “Why don’t we just ask them?” So we did!
We spoke with Coleman Brumley, the Chair of the BACnet Committee and Principal I/O Sub-Systems Engineer at PassiveLogic, and David Fisher, consultant to the committee and President of PolarSoft Inc. on what the team is working on for 2025, and what they see on the horizon for the BACnet protocol.
Side Note: BACnet/SC Isn’t Top of Mind
Let’s just get it out of the way: BACnet/SC might be a buzzy topic in the industry, but it’s not the top issue with the Committee. Coleman says, “I don’t think it’s the single most important addition to the standard… since we are not solely focused on security.”
There is a wealth of new addenda to existing standards and an entirely new standard being developed, none of which are security-focused.
David Fisher agreed. “There’s been a huge amount of effort put into testing and verification for BACnet devices. Out of the existing population of 100M+ BACnet devices, there are fewer than 1000 SC devices and that number isn’t going to increase very fast, very soon. So I’m much more interested in and concerned about, evolving changes to the standard that affect all devices, and that work to make all 100M devices work better, cost less to install and maintain, etc.”
What’s on Tap for BACnet in 2025?
While there are always going to be minor updates to definitions, changes based on interpretation requests, and similar improvements, we can generally boil down what the BACnet Committee sees on the horizon into three categories: The updated 2024 Standard, (hopefully) the introduction of a new Standard for BAS, and expectations for the next wave of BACnet devices.
BACnet Standard Updates for 2024-25
The BACnet standard itself is a living document, and it’s constantly evolving (the most recent revisions being published as recently as October 2024). That said, the completely updated BACnet standard was recently released, and it contains a roll-up of all the revisions, changes, and fixes that set the standard going forward into 2025.
Note: the “Standard” isn’t just a few pages that lay out what BACnet is. This is a 1400-page document that defines every aspect of how BACnet communicates, including a “comprehensive set of messages for conveying encoded building automation data between devices.” Keeping track of and maintaining this massive list of communication standards is a huge undertaking, mostly done by volunteers!
Here’s a summary, courtesy of David Fisher, of what’s notable in the update. They generally fall into six major areas and related addenda:
Clarification and Fixes | |
135-2020bv | Write_Every_Scheduled_Action to the Schedule object |
135-2020ce | MS/TP language manager/subordinate |
135-2020af | data attributes segmentation consistency |
135-2020ch | fixes to address segmentation errors |
135-2020ck | missing ASN.1 definition |
135-2020cn | changes to engineering units |
135-2020cq | improvements to JSON |
135-2020ci | relaxed requirements for DS-COV-A and DS-COVP-A |
135-2020co | Clarifications of out-of-service Fix fault algorithm confusion |
Color and Lighting | |
135-2020ca | Add Color concepts and new Color and ColorTemperature objects Update Lighting Object (LO) and Binary Lighting Object (BLO) with Color references |
135-2020cj | Improvements to LO, BLO for luminaire levels |
BACnet/SC | |
135-2020cc | BACnet/SC configuration Cert replacement/management New BIBBs for SC |
135-2020cs | Certificate Authority Requirements Interchange File Format (CARI) |
Network Port Object (NPO) Improvements | |
135-2020cc | MS/TP parts of Network Port Object (NPO) writable BIP and BIPv6 parts of NPO writable |
Proxying | |
135-2020bx | Device Address proxy Subordinate proxy |
Advancing security | |
135-2020cp | Authentication and authorization |
BACnet Energy Services Interface (ESI) | |
135-2020cm | NIST contribution to integrating BACnet with external systems |
A New Modeling Standard for BAS
This is still under development, but from what Coleman and David have shared, could be a big improvement for a lot of technicians and system integrators that work with BAS servers.
A bit of background: ASHRAE has been working alongside Project Haystack and The Brick Initiative since 2018 to “combine their respective semantic tagging and building data modeling concepts into the new proposed ASHRAE Standard 223P, Designation and Classification of Semantic Tags for Building Data. Standard 223P is set to provide a dictionary of semantic tags, such as those used on articles of news websites, for descriptive tagging of building data including building automation and control data along with associated systems.”
For those of us less technologically inclined, the new standard is a collaborative effort to make it easier for BAS systems to automatically tag (create semantic models) and share their data in universal ways. The goal is to be able to leverage the BACnet protocol to share tagged data that enables more modern analytics and testing, like automatic fault detection, digital twins, and more energy grid interactions.
“There has been a huge effort put into drafting a new standard ASHRAE 223P which purports to be a new way of modeling BAS. Expect to see a lot of additional activity as this proposed standard gets more public exposure.”
“Rev 19” and Future BACnet Devices
As worldwide implementation of BACnet continues to grow, demand grows. That drives competition. As a result, new features and revisions are continuously introduced, resulting in significant shifts in the types of devices available in the marketplace. While these changes may appear gradual, they are driving important advancements.
One notable trend is the wider adoption of Revision 19 certification standards. Until recently, most devices were developed using older Revision 12 and 14 benchmarks—meaning devices only contained the features and object functionality those certifications defined. In short, new products were still lacking newer features that had already been tested and approved by the BACnet Testing Lab (BTL) and in the BACnet standard.
Now, manufacturers are incorporating newer BACnet functionalities into their devices, and this trend is expected to accelerate. The year 2025, in particular, will likely see a surge in these advanced devices as manufacturers seek BTL certification.
In short: there are a lot more options available in the marketplace, so make sure to check what “REV” your prospective hardware supports!
As well, BTL is working to bridge the gap between the BACnet standard and its testing process. David Fisher explains the details. “ They are closing the gap between tests defined in 135.1 and tests that BTL has designed to accommodate newer devices that use features of BACnet for which (so far) 135.1 tests have not yet been defined.”
This ensures that the certification process stays up to date with the latest technology, making BACnet devices more reliable and consistent.
2025 Should Be One To Watch
BACnet is poised for another transformative year. With the release of updated standards, the adoption of Revision 19+ devices, and the development of new tools like ASHRAE 223P for better data sharing, BACnet continues to adapt to the needs of modern building automation systems. These advancements highlight its commitment to innovation, efficiency, and interoperability—ensuring that BACnet remains a cornerstone of the OT networking landscape. For professionals in the industry, the coming year offers an exciting opportunity to embrace these changes and help shape the future of smart buildings and connected systems.
Coleman summed up the future of BACnet this way:
“BACnet continues to evolve and shows that it can continue to adapt to ever-evolving market and technical needs. Continuing to extend BACnet/SC to include device-to-device security, adding to BACnet lighting integration, and responsiveness to new trends like data modeling will ensure that BACnet continues to remain relevant in today’s BAS market. And, this responsiveness with an eye towards interoperability shows why BACnet is a major contributor to the market with a 77%, and growing, global market adoption.”
How many issues will you solve today?
FAQ: What’s Coming in BACnet Updates?
1. What is BACnet?
BACnet (Building Automation and Control Network) is a communication protocol for building automation systems. It allows devices like HVAC, lighting, and access controls to communicate and work together seamlessly.
2. What are the latest updates coming to BACnet?
Recent updates to BACnet focus on enhancing security, interoperability, and scalability. This includes increased support for IoT devices and improvements to existing infrastructure.
3. How will these updates affect existing BACnet systems?
Systems using older BACnet versions will remain functional, but some updates may require software or hardware adjustments.
4. Are these updates compatible with all BACnet devices?
Most devices can adapt to the updates, but compatibility may vary depending on the manufacturer and the device’s age. It’s a good idea to consult your vendor or integrator to assess compatibility.
5. What do these updates mean for smart building owners and operators?
These updates enhance the security, scalability, and efficiency of building automation systems. Owners and operators can expect better integration with IoT devices, streamlined maintenance, and compliance with modern security standards.
6. How can I prepare for these updates?
Start by evaluating your current network and device compatibility. Work with your systems integrator to implement necessary upgrades and ensure proper network configurations to adopt new features smoothly.
9. Are there any challenges associated with these updates?
Some challenges include managing legacy systems, ensuring compatibility with existing devices, and addressing the learning curve for new technologies like BACnet/SC. However, these can be mitigated with proper planning and training.
10. Where can I learn more about BACnet updates?
For a detailed overview, visit the Optigo Networks BACnet Updates Page or consult with industry experts and your building automation systems integrator.
*Article FAQs are created with the help of AI