Ask five people on a construction project what happens to the BIM model after handover, and you'll get five different answers. COBie is supposed to be the answer everyone agrees on — and yet it's still one of the most misunderstood deliverables in the whole BIM process.

COBie stands for Construction Operations Building Information Exchange. In plain terms, it's a structured spreadsheet-style data set — pulled out of the BIM model — that hands facility managers everything they need to run a building once construction is finished: equipment lists, model numbers, warranties, maintenance schedules, spatial locations, and more. No 3D geometry, no walkthroughs — just clean, organised data that a facilities team can load straight into their maintenance software.

The problem is that most projects treat COBie as a box-ticking exercise rather than a real deliverable. A model gets built for design and construction, and then someone tries to extract COBie data from it at the very end, discovers half the fields are empty or inconsistent, and spends weeks manually patching gaps that should never have existed in the first place.

Why COBie Actually Matters

A building's design and construction phase might last two or three years. Its operational life lasts thirty, forty, sometimes longer. Every asset in that building — every pump, panel, valve, and unit — needs to be tracked, maintained, and eventually replaced. Without structured handover data, facility teams start that thirty-year job with nothing but PDFs, static drawings, and whatever the outgoing contractor remembers to mention.

Good COBie data means:

• Facility managers can identify every asset's manufacturer, model, and warranty status without digging through folders
• Maintenance schedules are built into the handover data from day one, not reconstructed after the fact
• Space and zone data ties equipment to physical locations, so a call-out doesn't start with "which floor is that on again?"
• Asset replacement planning becomes a data query instead of a site survey

Where COBie Goes Wrong on Most Projects

The most common failure point isn't the export — it's everything that happens before it. COBie is only as good as the discipline behind the modelling process:

1. Naming and classification inconsistency. If mechanical, electrical, and plumbing teams each name equipment differently in their own models, the COBie export inherits that mess.
2. Left too late. COBie fields need to be populated progressively through design and construction, not bolted on in the final two weeks before handover.
3. No clear data owner. Someone on the project needs to be responsible for COBie compliance from day one — otherwise it falls through the cracks between disciplines.
4. Treated as a formality. Teams that see COBie as a contractual checkbox produce exactly that: a checkbox-quality deliverable that facility managers can't actually use.

Done properly, COBie isn't an end-of-project scramble — it's a natural byproduct of a well-coordinated model that's been populated with the right data from the earliest design stages.

Who Should Actually Own COBie on a Project

COBie responsibility tends to get lost between the architect, the MEP consultants, and the facilities team — and by the time anyone notices, the data gaps are already baked in. The BIM coordinator or BIM manager is usually best placed to own it, since they're the one party with visibility across every discipline's model. Their job isn't to fill in the spreadsheet themselves — it's to make sure classification standards are agreed early, data fields are populated as design progresses, and the final export is checked against the employer's information requirements (EIR) before it ever reaches the client. Treated this way, COBie stops being a last-minute headache and becomes just another coordination checkpoint, no different to a clash detection run.bim365.in