COBie BIM File

What is COBie?

COBie was created to support the handover of building information from design and construction teams to owners and facility-management teams. Its purpose is to make sure operational data is not trapped inside drawings, PDFs, or disconnected project documents, but is instead delivered in a structured format that software and people can both use.

From a BIM perspective, COBie focuses on asset information, not on full geometric model exchange. WBDG describes COBie data, from the designer's perspective, as the compiled set of schedules found on design drawings, while the National BIM Guide for Owners defines it as a format for exchanging information about building assets such as equipment, products, materials, and spaces.

Is COBie a file format?

This is a common source of confusion. In everyday BIM workflows, "COBie file" often refers to a spreadsheet deliverable, but the standard itself is broader. WBDG notes that large projects may use IFC-standard STEP and ifcXML representations, while smaller projects often exchange COBie data in spreadsheet form.

The NIBS COBie specification also states that SpreadsheetML may be used as an optional physical format and that JSON support was added in Version 3. That means a COBie deliverable can exist in more than one machine-readable representation depending on project requirements, software stack, and contract language.

What kind of information does COBie contain?

COBie is used to organize building lifecycle data in a structured way. Typical information includes:

• Spaces, floors, and zones
• Systems and equipment types
• Installed components
• Documents, jobs, events, and risks
• Attributes tied to facility operation and maintenance

buildingSMART's COBie v3 executive summary describes the structure as a set of tables covering overall, spatial, asset, process, and support information.

In practical building projects, this includes information about construction materials, internal structure, and building systems such as HVAC, along with the asset data facility teams need to understand what was installed, where it is located, and how it should be operated or maintained.

How does it work in a BIM workflow?

COBie is typically assembled progressively during design, construction, and commissioning rather than created only at the end of a project. Different stakeholders contribute different parts of the dataset, and the completed exchange is handed over to owners or FM systems as a structured operations dataset. WBDG's COBie guidance emphasizes implementation strategy, responsibility assignment, and the fact that project teams must define how COBie is produced and validated.

That makes COBie especially important at the handover stage. Instead of giving facilities teams only graphical BIM models, the project can also deliver an organized register of assets and related information that is easier to query, validate, and connect to maintenance workflows.

Applications and Industry Use Cases

COBie is widely used in facility handover, asset management, and operations readiness workflows. It helps owners and operators receive structured data about installed equipment, spaces, materials, and building systems without depending on a single authoring platform.

Common use cases include:

• Populating computerized maintenance management systems
• Preparing preventive-maintenance records
• Documenting installed equipment and manufacturer information
• Organizing room and space data
• Improving the transition from construction to long-term operations

For software developers, COBie matters when building applications that need to bridge BIM authoring, model coordination, data validation, owner handover, and facilities-management workflows. It is particularly relevant where a system must connect structured asset data with related BIM or CAD geometry coming from other file formats.

Challenges or Common Pitfalls

A common mistake is to treat COBie as if it were just an Excel sheet export. Spreadsheet delivery is common, but the standard itself is broader, and reducing COBie to a spreadsheet can hide its relationship to IFC-based mappings and other formal exchange structures.

Another pitfall is to assume COBie is a full geometric BIM replacement. It is primarily a non-graphical asset-information exchange, so it usually complements geometric BIM deliverables rather than replacing them. Teams that expect full 3D coordination or exact geometry from COBie alone are misunderstanding its role.

Data quality is also a major issue. COBie is only useful when the source data is complete, consistently classified, and assigned clearly across project participants. WBDG and related COBie guidance stress that implementation rules, picklists, responsibilities, and validation practices must be defined carefully to avoid inconsistent handover data.

Finally, developers should be aware that mappings between IFC-based COBie data and spreadsheet views are not trivial. buildingSMART community guidance notes that extracting COBie into spreadsheet form can involve one-way mappings and possible data loss, so the human-readable spreadsheet is valuable but not always equivalent to the full source model context.

How Spatial Helps

Our role in COBie-related workflows sits on the BIM interoperability and visualization side rather than COBie authoring itself. Our SDKs address three recurring needs in BIM software development: interoperability across formats, handling complex datasets with engineering precision, and 3D visualization.

Data ingestion and interoperability. 3D InterOp is directly relevant when COBie data must connect to the geometric BIM and CAD data that surround it in real applications. 3D InterOp reads and writes around 30 CAD, BIM, mesh, and visualization formats, supports selective import of product structure, tessellated geometry, exact geometry, and metadata, and targets AEC, BIM, and plant-design workflows.

That matters because COBie rarely stands alone in production software. A facility or owner-facing application often needs both the structured handover data and the related model context. We help developers ingest and work with the geometric side of BIM workflows while preserving the metadata needed for downstream engineering applications.

Visualization and review. HOOPS Visualize and HOOPS Visualize Web handle large-model visualization, web and mobile rendering, and interactive 3D application development. In a COBie-centered workflow, these capabilities complement asset-information exchanges by letting users inspect the associated model context rather than relying on tabular data alone.