Lesson 4.4Lesson 4.4 · Interoperability & openBIM
COBie & Structured Handover
The model designed the building; COBie hands the operator the data to run it
The facility manager opens your beautiful model, looks for the boiler's warranty, and closes it again.
The team spends years building a rich, coordinated model. At handover it is passed proudly to the people who will operate the building — who mostly do not use BIM authoring software, do not want to navigate a 3D model to find a serial number, and need answers to painfully practical questions: what is this pump, who made it, when is it under warranty, when is it next due for service, which room is it in?
They do not want the *model*. They want the *data inside it*, in a form they can actually use. COBie — Construction Operations Building information exchange — is the open, structured way to hand that data over: a disciplined extract of exactly the asset information an operator needs, distilled from the model at each milestone. It is where BIM finally pays off for the fifty-year owner — or, done badly, where all that modelling quietly fails to deliver its biggest promise.
The operator never opens your model. They open the spreadsheet you distilled from it — so make that the deliverable you care about.
What COBie is: the operator's data, not the geometry
COBie is a structured schema for the *non-geometric* information an operator needs about the manageable assets in a building — the spaces, the systems, the equipment, and the components that get maintained, serviced and replaced. For each, it captures the practical facts: what it is, its type and manufacturer, where it is located, its warranty, its spare parts, its maintenance requirements, its identifying numbers.
Deliberately, COBie is not the 3D geometry. It is the information a facility-management system can ingest and a maintenance team can act on — which is why it is most familiar as a structured spreadsheet (a set of linked worksheets for spaces, types, components and so on), a form almost any organisation can open and use, though it can also travel as IFC. The point is that COBie takes the vast, rich model and distils from it precisely the slice that operating the building requires — no more, no less. It is the answer to 'we spent years modelling; what does the operator actually get?'
Filled progressively, not scrambled at the end
The most important practical truth about COBie is *when* it is built. The failure mode is to treat handover data as an afterthought — a frantic scramble in the last weeks of a project to populate thousands of fields nobody captured along the way, producing a rushed, error-riddled spreadsheet that the operator cannot trust.
Done well, COBie is populated progressively, milestone by milestone: the designer contributes the space and type information, the contractor and suppliers add the real installed products, manufacturers, serial numbers and warranties as the building is actually built. By handover, the data has accumulated naturally from the people who genuinely knew it, at the moment they knew it. This is the operational reason the whole information discipline of BIM exists — the required data (the EIR), assigned to the right party, validated as it goes (increasingly checkable now via IDS from the last lesson). COBie is not a document you write at the end; it is a harvest you gather all the way through. On Indian public projects this is explicit: the CPWD framework requires COBie-style structured handover for facility management, precisely so the asset data is a deliverable, not a hope.
COBie done at the end is a panic. COBie done all along is just tidiness that pays off at handover.
The honest limits: it is only as good as the data, and the operator must want it
Two honest cautions keep COBie from being oversold. First, COBie is a container, not a guarantee of quality. A COBie file can be perfectly formatted and full of wrong, blank or placeholder data — the same silent failure we met in Module 3, now at the scale of a whole building. A tidy spreadsheet of useless data is still useless. COBie's value depends entirely on the information discipline behind it: required, assigned, filled by those who knew, and validated. The format is necessary; it is nowhere near sufficient.
Second, handover data only delivers if the receiving side can and will use it. If the operator has no system to ingest COBie, or no process to maintain it as the building changes, even perfect handover data goes stale on a shelf. Good handover is therefore a two-sided commitment: the project produces trustworthy structured data, *and* the owner is set up to consume and maintain it. Get both right and the model that designed the building genuinely becomes the data that runs it for decades — the destination this whole module has been travelling toward. Get either wrong and the handover is a beautiful file nobody uses, which is the quiet, common way BIM's biggest promise is missed.
Three altitudes on the same idea
Read the band that fits you — or all three.
Learn COBie as the operator's data extract. COBie (Construction Operations Building information exchange) is the open, structured way to hand over the *non-geometric* asset data an operator needs — for each space, system and serviceable component: what it is, its manufacturer, location, warranty, spare parts and maintenance. It is not the 3D geometry; it is most familiar as a structured spreadsheet a facility-management system can ingest. Two things to remember: fill it *progressively* through the project (not in a last-minute scramble), and know it is only a container — a tidy COBie file full of wrong data is still useless.
Harvest handover data as you go. Contribute your part of COBie at each milestone — designers the spaces and types, contractors and suppliers the real installed products, serials and warranties — rather than reconstructing it painfully at the end. Map your model's data to the COBie structure, and validate it (IDS helps) before it goes out. Watch for the silent failure: correctly formatted, wrongly populated. Your goal is a handover the operator can actually load and trust, which means the data must be complete, correct and captured by whoever genuinely knew it, at the time they knew it.
Specify handover, resource it, and make sure it lands. Define the structured handover the operator needs (COBie or an agreed schema) in the information requirements, assign who fills which fields at which milestone, and validate it (increasingly via IDS) so it is a checkable deliverable, not an end-of-job scramble — the posture India's CPWD framework already mandates for FM. Critically, confirm the *receiving* side: the owner needs a system to ingest COBie and a process to keep it current, or even perfect data dies on a shelf. Handover is the operational payoff of the entire BIM effort; treat producing *and* consuming the asset data as one commitment, or the biggest promise of BIM quietly goes unmet.
“Handing over the 3D model is the handover — the operator has everything in it.”
Do it yourself
Step into the operator's shoes and see why geometry is not the handover.
- 1Pick one serviceable item — a rooftop air-conditioning unit. As the facility manager, list the five things you need to know to maintain it: what it is, who made it, where exactly it is, its warranty, its next service. None of these is its shape.
- 2Now ask where each fact should have come from, and when: which party knew it, at which project stage? (Type from the designer; manufacturer, serial and warranty from the supplier/contractor at installation.) That is why COBie is filled progressively.
- 3Imagine receiving all this as a 3D model you must navigate to find each serial number, versus as a structured sheet you can search and load into your maintenance system. Note which one you would actually use.
- 4Finally, imagine the sheet arrives beautifully formatted but half the warranties are blank and three serial numbers are wrong. Write one line: why is a tidy COBie file not the same as a useful one — and what discipline (from this whole module) would have prevented it?
The one line to carry out
We now have the open standards to move models, issues, meaning, requirements and handover data — all vendor-neutral. But standards alone do not manage information; a process does. Module 5 opens ISO 19650: the Common Data Environment, EIR and BEP, and the discipline that governs the whole information lifecycle.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →