There is a conversation happening across building automation right now about data. Why buildings have so much of it and so little to show for it. Why artificial intelligence cannot get a foothold in operations. Why intelligent buildings remain more promise than reality for most facility teams.
The answer, in many cases, is not in the building itself. It is in what happened the day the keys were handed over.
The Problem Has a Name
Construction projects generate enormous amounts of structured data. Every piece of equipment has a manufacturer, a model number, a warranty, a maintenance schedule, and a location. Every system has a design intent. Every space has a purpose. This information lives in Building Information Models during design and construction.
Then the project closes out. The model gets filed away. And the building automation system starts from scratch.
This disconnect is so common it has earned its own informal name: the BIM graveyard. It is the recurring pattern of receiving models at completion with no operational use. The data existed. It just never crossed the threshold.
The consequences show up years later. Buildings that cannot produce a reliable performance record. Facility teams are rebuilding asset inventories from scratch. AI platforms have nowhere clean to start. This site has been documenting the downstream effects — here and here — but the upstream cause has gone largely unnamed.
What COBie and IFC 4.3 Are Trying to Fix
Two open standards exist specifically to solve this problem. Most building automation professionals have not heard of either.
COBie (Construction Operations Building Information Exchange) is a data specification that defines exactly which information from a BIM model should be sent to the operations team. Rather than delivering a complex 3D model that facility managers cannot open, COBie packages operationally relevant data — equipment names, types, locations, warranties, spare parts, and maintenance schedules — into a structured format that building systems can actually use. It has been a mandatory deliverable on UK government projects since April 2016, when the government required BIM Level 2 compliance on all centrally procured contracts.
IFC 4.3, developed by buildingSMART International, is the underlying open schema that makes structured handover possible at scale. Published in 2022 and formally approved as an ISO standard in January 2024, IFC 4.3 expanded beyond building geometry to include building services and the mechanical and electrical systems that building automation teams actually operate. Together, COBie and IFC 4.3 give the industry a practical, vendor-neutral path for structured handover that simply did not exist in this form before.
The goal of both is the same: ensure that reliable, structured data travels with the building from design through demolition.
Why This Is an Automation Problem, Not Just a Construction Problem
Building automation professionals tend to think of BIM as someone else’s domain. The BAS team comes in at the end.
That framing is the root of the problem.
A BAS cannot be intelligent without context. A temperature sensor reading of 74 degrees means nothing without knowing which space it serves, what the design intent was, which equipment controls it, and what the acceptable range is. That context exists in the BIM model. Without a structured handover, the BAS team spends weeks manually re-entering information already captured during construction, often with errors and always incompletely.
A 2025 critical literature review published in Buildings found that interoperability between BIM and facility management systems “depends on open, vendor-neutral standards, yet operational uptake remains constrained by fragmented workflows, incompatible schemas, and non-standardized delivery.” Separate research found that BIM representations of building automation systems are “limited mostly to physical setup of devices,” leaving control logic, sequences, and operational intent out of the model entirely.
This is the upstream cause of problems the industry has been diagnosing from the downstream end for years.
The Evidence Problem Starts Before the Building Opens
A building that cannot produce a credible performance record when questioned almost always has the same origin story: structured asset data was never formally handed over at construction close-out. The record that matters has to begin before occupancy. The commissioning baseline that operations teams rely on requires knowing what was installed, how it was configured, and what it was meant to do. A COBie-compliant handover is where that record begins.
Why 2026 Is the Right Time to Pay Attention
Three things are converging, making a structured BIM-to-BAS handover more urgent than at any point before.
First, AI integration in building operations requires clean, contextualized data. The knowledge graph frameworks, semantic tagging, and Haystack-based platforms that the industry is investing in cannot compete with a BAS configured manually from incomplete paper submittals. The intelligence layer depends on the data layer. The data layer depends on handover.
Second, building performance standards creates legal accountability for operational outcomes. New York City’s Local Law 97 covers approximately 50,000 buildings over 25,000 square feet and charges $268 per metric ton of carbon over the annual limit. Boston’s BERDO applies to buildings over 20,000 square feet with penalties of $234 per metric ton over target. Washington State’s Clean Buildings Act sets mandatory Energy Use Intensity targets with compliance deadlines running through 2028. Demonstrating compliance requires records. Records require structured data from day one.
Third, the standards are ready. COBie and IFC 4.3 give the industry a tested, vendor-neutral handover path. The gap now is not the technology. It is the expectation.
What a Good Handover Looks Like
A structured BIM-to-BAS handover does not require a perfect 3D model. It requires the right data in the right format at the right time:
- Every controlled piece of equipment is identified with naming conventions that match the BAS
- Manufacturer data, model numbers, and installation dates captured in COBie format before substantial completion
- Space relationships and system boundaries are defined so the BAS knows what equipment serves what zone
- Design intent is documented for each system, so commissioning has a baseline to work from
- The handover deliverable is written into the contract as a requirement, not left as a courtesy
This is not a technology problem. It is a workflow and contract problem. The technology exists. The standards exist. What is missing is the expectation that it will happen.
The Conversation That Needs to Start Earlier
Every conversation about AI readiness, knowledge graphs, semantic infrastructure, and evidence-grade data eventually traces back to the same question: where does the structured data come from in the first place?
For most buildings, the honest answer is that it was created once during design and construction, and then lost. COBie and IFC 4.3 are the industry’s best current answers. The building automation community should be leading that conversation, not waiting for it to arrive from the construction side.
Sources
- The Smart Building’s Evidence Problem — AutomatedBuildings.com
- The Commissioning Never Continued — AutomatedBuildings.com
- Digital Twin Discourse 1999 to 2026 — AutomatedBuildings.com
- IFC 4.3 Approved as ISO Standard — buildingSMART International
- COBie Overview — NIMA
- BIM-FM Interoperability Through Open Standards — MDPI Buildings 2025
- Supporting BAS in BIM/IFC: Reviewing the Information Gap — ResearchGate
- UK BIM Level 2 Mandate — Letsbuild
- Local Law 97 — KODE Labs
- BERDO — Facilities Dive
