They're not competing formats. One is the full model exchange — the other is a spreadsheet pulled out of it for a completely different audience.
It's easy to see "IFC" and "COBie" both mentioned in a BIM Execution Plan's data-delivery section and assume they're two alternative ways of exchanging the same kind of thing — pick one, like choosing between two file formats for the same job. They aren't alternatives. IFC is a full, open, geometry-plus-data BIM exchange schema, used throughout design and construction by every discipline. COBie is a structured, spreadsheet-style, non-geometric data deliverable, specifically extracted from a BIM model at handover for the facility management team. COBie is downstream of a BIM model — often literally generated as a filtered export of the same data IFC carries — not a rival to it.
IFC (Industry Foundation Classes) is an open, vendor-neutral schema for exchanging a complete BIM model — geometry, spatial relationships, standardized property sets, and system connectivity — between the software different design and construction disciplines actually use day to day. COBie (Construction Operations Building Information Exchange)is a specification for a much narrower thing: a structured spreadsheet (or a COBie-compliant subset of an IFC file) containing only the non-geometric asset data a facility management team's CMMS software needs — equipment types, components, warranties, model/serial numbers, O&M documents — organized into named worksheets, with zero 3D geometry included at all. One is a model. The other is a handover data extract.
A facility manager troubleshooting an air handling unit doesn't need to navigate a 3D BIM viewer to find the equipment's model number, warranty expiration, or maintenance schedule — they need that data in a system built for work orders, and CMMS platforms are built around structured records, not 3D geometry. COBie exists specifically to bridge that gap: it takes the subset of a model's data that an FM team actually uses, strips out everything geometric, and reorganizes it into worksheets (Facility, Space, Component, Attribute…) that map cleanly onto how a CMMS expects to receive asset data. The relationship only makes sense in one direction: COBie is generated froma BIM model's data (often as a filtered subset of the same information an IFC export carries), never the other way around, and it was never meant to replace IFC as a design-and-construction exchange format.
No — this framing misunderstands what each one is for. IFC is a full model-exchange schema, carrying geometry alongside data, used continuously between design and construction disciplines. COBie is not an alternative way to exchange a model at all — it's a structured, spreadsheet-style deliverable containing only the non-geometric asset data a facility management team needs, produced by extracting and filtering that subset directly out of the BIM model's existing data (COBie can even be generated as a specific, restricted subset of an IFC file's data, using a defined COBie Model View Definition). They aren't solving the same problem for the same audience— IFC exists so the model can keep being worked on across platforms; COBie exists so the model's useful data can be handed off to people who will never open the model at all. A BIM Execution Plan that specifies both isn't hedging between two competing choices — it's correctly specifying two different deliverables for two different audiences at two different project stages.
Explains why COBie and IFC are not competing BIM exchange standards — IFC is a full, open geometry-plus-data model exchange schema used throughout design and construction, while COBie is a structured, non-geometric spreadsheet deliverable extracted from the model specifically for facility-management handover — using a side-by-side diagram of the full IFC exchange and the filtered COBie extraction that follows it.
IFC and COBie both show up in the same BIM Execution Plan section — "data delivery and interoperability" — which makes it easy to file them mentally as two options for the same job. They solve genuinely different problems for genuinely different audiences. IFC (Industry Foundation Classes) is buildingSMART's open, vendor-neutral schema for exchanging a complete BIM model — geometry, spatial relationships, standardized property sets, and system connectivity — so different platforms can keep collaboratively working on it throughout design and construction. COBie (Construction Operations Building Information Exchange) is a specification for a narrow, non-geometric data deliverable: a structured spreadsheet (or a COBie-compliant IFC subset) containing exactly the equipment, space, and asset data a facility management CMMS needs, with no 3D geometry included at all.
A COBie deliverable is organized into standardized worksheets — commonly Facility, Floor, Space, Zone, Type, Component, System, Attribute, Assembly, Connection, Spare, Job, Document, Coordinate, Issue, PickLists, and Contact — each a structured table of rows and columns rather than any kind of 3D view. A Component row for an air handling unit, for example, carries its name, type, manufacturer, model and serial number, installation date, and warranty period — the exact fields a facility manager or CMMS platform needs to plan maintenance, order replacement parts, or track warranty status, without ever opening a BIM viewer.
COBie is most commonly required as a project closeout/handover deliverable, often specified explicitly in a BIM Execution Plan or an ISO 19650-aligned Exchange Information Requirements (EIR) document, precisely because it targets the operations phase rather than design or construction. Producing a clean, accurate COBie export depends on the underlying BIM model actually carrying the right data at the right LOD by handover — a model where equipment isn't correctly typed, classified, or parameterized during design will produce an incomplete or unreliable COBie extract regardless of how good the extraction tooling is.
No. They serve different purposes at different project stages for different audiences. IFC is used continuously during design and construction to exchange a complete model between BIM platforms. COBie is typically produced once, at or near handover, as a filtered, non-geometric data deliverable for facility management — it doesn't carry the geometry IFC does, and it isn't meant to.
Yes — COBie can be produced as a defined, restricted subset of an IFC file's data (using a COBie-specific Model View Definition), or exported directly from BIM authoring software using COBie extension/export tools. Either path pulls the same kind of non-geometric asset data out of the model; the destination format is the structured COBie spreadsheet either way.
Because its intended consumer — a CMMS or facility management system — doesn't need geometry to do its job. Work orders, maintenance schedules, and warranty tracking are all handled through structured records (equipment name, type, location, specs, dates), not through 3D visualization, so including geometry would add file complexity without adding value for that audience.
The COBie deliverable inherits those gaps directly — COBie extraction only reorganizes data that already exists in the model, it cannot invent missing manufacturer, model number, or classification data. This is why BIM Execution Plans that require COBie handover typically also specify data requirements (parameter completeness, classification standards) that must be met well before the extraction happens, not scrambled together at closeout.
It varies by project, but it's commonly the BIM manager or a designated model coordinator, working from the federated design/construction model as it approaches handover, sometimes with input or QA review from the owner's facility management team to confirm the extracted data actually matches what their CMMS expects to import.
Try our BIM, CAD & Digital Design Studio
More calculators, simulators, and guides for this discipline.