A Linux Foundation coalition group is drafting Division 25 bid language for open controls
The Coalition for Smarter Buildings, a Linux Foundation project, is drafting standard Division 25 bid language so owners can require open, interoperable building controls. Related open-licensed GitHub specs and tools cover data ingestion, semantic models and control testing. The editorial argues interoperability gets decided at bid time.
This story was produced through MarketScale. See how Building Management teams put it to work with Customer Stories & Case Studies.
Key takeaways
Sinclair argues interoperability gets decided in bid documents long before open-source code is downloaded, making Div2525’s Division 25 spec language a first step owners can act on.
Owners and consulting engineers can shape the specs without coding: working groups take naming conventions, procurement language and operational workflows, and joining takes a free GitHub account and a Linux Foundation ID.
A sharper question for the next controls bid: will the deliverable include a validated semantic model and control sequences an engineer can simulate before startup?
Free workspace
Turn your Building Management expertise into content.
Record interviews, organize footage, and write with AI on a free trial of the MarketScale platform for qualifying companies. No demo required, no credit card.
Ken Sinclair laid out a map on November 17 in an AutomatedBuildings.com editorial on how the building automation industry gets from closed, vendor-specific systems to open building control. The piece reads like a field guide to the Coalition for Smarter Buildings (C4SB), a Linux Foundation project series, and the code it hosts.
For owners, the item most likely to change the next project may be a document. Div2525, a C4SB group, is writing standard Division 25 procurement specifications aimed at owners, consulting engineers and Master System Integrators. Sinclair says the group is solving the contractual bottleneck: owners get specification language they can copy and paste into bid documents, so open, interoperable systems become a requirement during bidding.
Writing openness into the bid
Sinclair's editorial describes Div2525 as copy-and-paste specification text for owners, consulting engineers and Master System Integrators. Owners can drop it into bid packages to require open, interoperable systems. He identifies the contract itself as the bottleneck. That's the right spot to work on. Interoperability is settled in the bid documents, long before anyone downloads a line of open-source code.
The coalition is also set up so the people who write those specs can shape them. According to the editorial, C4SB deliberately takes contributions from facility managers, owners and consulting engineers who don't write code: naming conventions, procurement language, operational workflows. Joining the working and interest groups takes a free GitHub account and a Linux Foundation ID.
What the C4SBF repositories hold
C4SB keeps public repositories at github.com/C4SBF, where working groups post reference architectures, Python libraries, command-line tools and specification documents. Because the material is released under open licenses (Apache, MIT and the Community Specification License), vendors and building owners are free to adopt, audit and improve the specifications without getting locked in to a vendor. Sinclair also points to related projects outside the coalition's own organization.
The open stack has distinct layers, and the working groups follow them fairly closely:
- Open Building Stack: developing open software (obs-python, obs-cli, obs-simulators) that connects legacy field protocols (BACnet, Modbus, LON and N2) to modern local and cloud applications. The goal is a free, standardized layer for ingestion and discovery, so legacy buildings can be retrofitted without proprietary gateways.
- Div2525: standard-form Division 25 procurement specifications, written for owners, consulting engineers and Master System Integrators.
- Interoperable Building Box: defining an open digital architecture for cloud-native, on-premises data exchange between applications and cataloging the IBBs already available. It also includes a blueprint for edge hardware and for software containers that connect on-site OT equipment securely to cloud analytics.
- Managed BACnet: tackling the practical technology, security and implementation problems that come up when BACnet is deployed in modern, cloud-native networks, and helping legacy BACnet networks adopt modern IT/OT practices such as BACnet/SC and automated device management.
- Semantic Buildings and Lifecycle Ontologies: testing open semantic models (Brick, Haystack, ASHRAE 223P) and aligning them across design, construction and operations, so metadata produced during BIM and design flows into operational BMS and AI agents with no manual re-tagging.
- UDMI Working Group: developing the Universal Device Management Interface specification, used to manage physical IoT devices at scale. It defines common JSON/MQTT payload schemas covering telemetry, configuration and state reporting for heterogeneous edge devices.
- Asset Leadership Standard: laying out the executive business case for smart, interoperable building assets, so facility leaders can justify open-control investments to C-suite executives by tying interoperability to asset value and grid markets.
- LonMark and Grid-Interactive Buildings: bringing legacy LonWorks standards under Linux Foundation open governance and developing frameworks for grid-responsive facilities.
According to AutomatedBuildings.com, repositories such as BuildingMOTIF (NREL/BuildingMOTIF), Brick Schema and ASHRAE 223P models let teams download standardized semantic templates and validation scripts. Sinclair writes that this ensures a VAV box or chiller is modeled the same way across different buildings and vendors. For an owner running analytics across a portfolio, consistent models could decide whether a single fault rule can run at every site or must be rewritten for each one.
Testing logic before it reaches the chiller
Lawrence Berkeley National Laboratory's OpenBuildingControl project (lbl-srg/obc) keeps machine-readable HVAC control sequences and verification tools on GitHub. Engineers can use them to simulate, test and verify control logic before it is loaded onto physical field hardware. AutomatedBuildings.com reports that developers and facility teams can also run autonomous control agents against simulated BACnet and Modbus equipment, such as obs-simulators, without risking live building operations.
A contributed post from Facil.AI, published on AutomatedBuildings.com the same day, shows what those agents look like in practice. Every five minutes, the company's agent reads all of a central plant's telemetry along with NOAA weather data and forecasts, occupancy and load. It then calculates setpoints for chillers, cooling towers and pumps. It doesn't send recommendations to an operator. It makes the changes itself, with no human in the loop, and keeps looking for the point where chiller energy and tower and pump energy balance best.
One autonomous plant agent, by the numbers
Facil.AI via AutomatedBuildings.com
Facil.AI also offers new sites a performance-based arrangement: no savings, no charge. Nothing in the post says the results depend on C4SB tools. That's a fair test of the open-control argument. It suggests an owner may be able to get large central plant savings without the open stack. The case for open tools rests on something else: whether the data model, the sequences and the integration work still belong to the owner after the next contractor or the next agent comes in.
The open stack's verification tools become more important once an agent writes setpoints on its own. Executable sequences and simulated equipment give an engineering team a way to test what software will do before it runs a real plant. For operators who run agents across several sites, consistent semantic models could matter as well.
Questions for the next controls bid
Open control doesn't require tearing out what's already installed, and the coalition's own structure shows it. The LonMark group exists to protect existing LonWorks investments, and Managed BACnet exists because putting BACnet on cloud-connected networks still raises practical and security problems. For an owner with a large installed base of older field devices, the realistic path is open ingestion and data models on top of current equipment. Replacement can wait.
For a consulting engineer or owner's representative writing a controls spec now, three editorial suggestions follow from the toolkit. These are not reported requirements. First, ask whether the deliverable includes a semantic model in Brick, Haystack or ASHRAE 223P that passes an open validator. Second, ask whether device discovery and data collection can be shown with open tools rather than a single proprietary gateway. Third, ask whether the control sequences come in a form an engineer can simulate before startup.
Before the bid goes out, ask the integrator to hand over the building's equipment model as a file that an open validator such as BuildingMOTIF can check. If they can't, the building is open only on paper.
The signal to watch is the Div2525 text itself. If its specification language appears in the C4SBF repositories and owners start putting it into actual bid packages, that would suggest open control has reached the contract stage.
Sources
Featured companies
Your experts belong here
Every story in MarketScale Building Management starts with a company putting its facilities engineers, energy managers, and service technicians on the record. Buyers are already reading this topic. The only question is whose experts they find.
Owners and facilities teams pick on trust, and your engineers turn that trust into inbound conversations.
About the author
The MarketScale Newsroom reports on the companies, technologies, and trends shaping 16 B2B industries. It turns primary sources and expert commentary into clear, useful coverage for the people doing the work.