Over the past month, Monday Live! has explored a question that cuts to the heart of how smart buildings actually operate. What does governance really mean for our industry?
The final March session brought the conversation into sharp focus by examining something rarely considered. Governance is not a single thing. It comes in many flavors, each serving a different purpose.
A Simple Analogy
Consider a person who lives in a home with informal household rules. That home sits in a city with its own ordinances. The city is in a county, which is in a state, which is in a country. Each layer governs different things. The same person also has a workplace with its own governance structures and may participate in activities with yet another set of rules.
This person does not think about all these layers at once. When the car is stolen, the call goes to local police, not federal authorities. The interaction happens at the layer that matters for the problem at hand.
The same principle applies to building systems.
Layers of Device Governance
A VAV box is governed by its own internal controls. Above that sits the building management system. Above that, vendor platforms may be collecting telemetry. Facility management systems impose their own governance. Utility grids and emergency services add further layers. All exist simultaneously, each serving a different purpose.
Multiple governance layers operate simultaneously. They are not alternatives to one another but different tools for different needs.
The Foundation That Exists
What makes government layers work is that they rest on widely understood foundations. Jurisdiction is agreed upon. Commercial relationships are understood through money. Social and governmental norms are shared.
For devices, foundational requirements already exist. A VAV controller must have safety listings. It needs to comply with communication standards. It carries a serial number tied to a warranty. These are table stakes.
Safety standards, communication protocols, and warranty tracking form the basic governance foundation for devices.
Above that foundation, things get softer. Regulations become less defined. Enforcement becomes inconsistent. Owner requirements vary wildly.
Unlike government structures, where rules are consistent across a jurisdiction, building system governance above the basic layer is often unique to each project.
The Knowledge Gap
On the government side, most people have an intuitive sense of how the layers work. Basic civics and daily life create a shared mental model of what federal, state, and local governments do.
On the building systems side, that intuitive knowledge does not exist. People who work in facility management often have no understanding of how the original specification was written. Controls engineers may not understand what facility managers need. The industry has not developed that shared mental model.
The lack of a common mental model across different roles makes governance harder to implement and maintain.
Conflicting Priorities
Governance layers can conflict. Does a fire mode override a snow day request? Does a demand response signal from the utility take precedence over an owner’s weekend schedule? These are not academic questions. They happen every day in real buildings.
Governance hierarchies need to be defined in advance so systems know which rules take priority when conflicts arise.
A Practical Path Forward
Making governance work requires attaching rules directly to devices and systems in a way that both computers and people can access.
If every VAV box carried a digital file with relevant safety standards, communication protocols, warranty terms, original design intent, and local code requirements, that information would be available exactly when needed. The technology for this now exists. Storage is cheap. Processing is powerful. Networks are fast enough to query this information in milliseconds.
Technology now makes it possible to attach complete governance information to individual devices. The capability exists. Adoption is the next step.
The Role of AI
Two practical applications for AI are emerging.
First, AI can interrogate building systems and report on compliance. It can identify what is working, what is not, and who or what is controlling each component.
Second, as buildings generate more data, AI can collect evidence of performance over time. That evidence can validate whether governance rules are being followed and whether strategies are actually working.
AI can help by asking questions about compliance and by building evidence histories that prove whether governance is achieving its intended outcomes.
The Regulatory Dimension
Energy performance mandates, cybersecurity requirements, and data privacy laws are moving from policy debates into practical procurement criteria. Compliance is no longer just about documentation and periodic audits. It is increasingly about architectural design. Systems must be built to stay resilient, updatable, and trustworthy over their entire lifecycle.
Regulatory requirements are becoming a primary driver of governance architecture. Systems must be designed for compliance from the start, not audited for it after the fact.
The Current State
The government side of the analogy evolved over centuries. The building systems side is still being figured out. It changes frequently. It is less well understood. It has never been well governed.
But the tools to bring order are finally arriving. Knowledge graphs. Open data formats. Standardized device descriptions. These are not abstract concepts. They are practical technologies that enable attaching governance to devices at scale.
The technology for governed, interoperable building systems is proven. The question now is whether the industry will adopt it before ad hoc patterns become the next generation of proprietary silos.
What Comes Next
The March governance series on Automated Buildings has traced this conversation from data ownership through the practical implementation of governed connectivity. The full series is available on the site.
The window for getting this right is open. The tools exist. The question is how quickly the industry will use them.
