COBie is the deliverable everyone agrees is important and almost nobody enjoys populating, mostly because it's treated as an end-of-project scramble instead of a habit built into modeling from day one. Here's what it actually is, and how to avoid the scramble.
What COBie actually is
Construction Operations Building Information Exchange (COBie) is a structured spreadsheet format for handing over asset, space, and equipment data from the design and construction model to a building owner's facility management (FM) system. FM software generally can't directly consume a Revit or IFC file — COBie is the structured, simplified bridge that makes the handover data usable by maintenance and asset management teams who aren't BIM specialists.
The core COBie worksheets, and what they actually need
| Worksheet | What it contains | Where the data usually comes from |
|---|---|---|
| Facility | Project-level identification data | Project information parameters |
| Floor | Level/storey data | Revit levels |
| Space | Room/space data, area, department | Revit rooms, correctly bounded |
| Type | Equipment/product type data (manufacturer, model, warranty) | Type parameters on equipment families |
| Component | Individual instances of equipment, tied to a Type and a Space | Instance parameters, correctly placed in space |
| Attribute | Additional asset data (serial numbers, install dates) | Shared parameters specifically set up for COBie |
Why "populate it at the end" fails
COBie data quality depends entirely on modeling habits maintained throughout the project — correctly bounded rooms, properly categorized equipment families, and consistently populated manufacturer/model/warranty data on type parameters. Trying to retrofit this onto a model in the final weeks before handover means manually chasing down information that should have been captured as equipment was specified and modeled. I've seen handover teams spend weeks on this when it should have been a continuous, low-effort habit.
The most common COBie population failures
- Equipment modeled as generic 3D shapes instead of properly categorized families with manufacturer/model data attached — COBie export then has nothing useful to pull.
- Rooms not properly bounded (the same issue that breaks area schedules, covered in our schedule errors guide) — this breaks the Space-to-Component relationship COBie depends on.
- Warranty and maintenance data left blank because nobody was assigned ownership of populating it — this needs a named responsible party in the BEP/IPP, not an assumption that "someone" will fill it in eventually.
- Using Dynamo or a COBie extension without validating output — automated COBie extraction tools are genuinely useful, but they extract whatever data exists; garbage in the model produces garbage in the spreadsheet, just faster.
A practical habit that prevents the end-of-project scramble
Assign COBie-relevant parameters (manufacturer, model number, warranty period) as required fields the moment equipment families are first placed in the model, and run a partial COBie export at each major milestone — not just at final handover — to catch gaps while there's still time to chase the missing data from the right discipline.
COBie data structuring and FM handover workflow are covered in our Apex plan, alongside ISO 19650 and EIR/BEP authoring. Full curriculum on the Programs page.
Frequently asked questions
What does COBie stand for?
Construction Operations Building Information Exchange — a structured data format for handing over asset and equipment data from design/construction to facility management teams.
Is COBie the same as a BIM model?
No. COBie is a structured spreadsheet-format deliverable extracted from a BIM model, not the model itself.
