■ MEP BIM INSIGHTS — TOOLS & SOFTWARE

What Is COBie and When Do You Actually Need It?

COBie — Construction Operations Building Information Exchange — appears in project specifications, owner requirements documents, and BIM contract riders with enough frequency that most BIM teams have heard of it. Fewer understand exactly what it is, what it contains, and when a project actually requires it vs. when it is listed as a requirement by default.

This article explains COBie plainly: what the format is, what data it carries, which project types mandate it, and how to produce it correctly from a Revit model.

---

What COBie Is

COBie is a data schema — a structured format for organizing and delivering facility asset information from the design and construction process to the building owner for use in facility management (FM) after handover.

In its most common form, COBie is delivered as a spreadsheet (Excel .xlsx) with a defined set of worksheets, columns, and data relationships. It is not a 3D model format. It is not a drawing format. It is a data handover format: a structured record of what equipment exists in the building, where it is, what type it is, and what documentation comes with it.

The COBie standard is defined in the National BIM Standard — United States (NBIMS-US) and is buildingSMART-aligned. It maps to IFC property sets, meaning a properly attributed Revit model can export COBie data directly via IFC or through dedicated COBie export tools.

---

What COBie Contains

A COBie spreadsheet is organized into worksheets. The core worksheets that MEP teams are responsible for are:

Worksheet	What it contains	MEP responsibility
Facility	Building name, address, project phase, site information	Shared — typically owner or CM
Floor	Level names and elevations	Shared — architectural model
Space	Room names, numbers, departments, area	Shared — architectural model
Type	Equipment type: manufacturer, model number, warranty duration, maintenance requirements	Primary MEP responsibility
Component	Individual equipment instances: tag number, serial number, install date, space location	Primary MEP responsibility
System	System name and classification each component belongs to	Primary MEP responsibility
Connection	Connections between components (e.g., pump serving specific AHU)	MEP responsibility where required
Document	Links to O&M manuals, submittals, warranties per equipment type	MEP / commissioning agent
Attribute	Additional parameters beyond the core fields: efficiency ratings, flow data, pressure data	MEP responsibility

The Type and Component worksheets are where most of the MEP work lives. Every piece of equipment — every AHU, chiller, pump, VAV box, fan coil unit, electrical panel, transformer, fixture — needs a Type row (the equipment specification) and one or more Component rows (the individual installed instances).

---

When COBie Is Actually Required

COBie is not required on every project. Understanding when it is actually mandated saves teams from preparing a full COBie deliverable for projects that only listed it in the specification boilerplate.

Projects where COBie is typically required

• US federal government projects — GSA, Army Corps of Engineers, VA, and other federal agencies mandate COBie as part of their BIM requirements for projects above a certain dollar threshold
• State and municipal government projects — many state DOTs, public universities, and state agencies have adopted COBie requirements; varies significantly by state
• Healthcare facilities — large hospital systems increasingly require COBie for MEP equipment to populate their CMMS at handover
• Higher education — major university systems (University of California, Texas A&M, etc.) have published BIM standards that include COBie requirements
• Large commercial owner-occupiers — corporate real estate portfolios managing 50+ buildings often require COBie to standardize FM data across their portfolio

Projects where COBie is listed but not enforced

COBie appears in many project specifications as a standard clause copied from a master spec without active enforcement. On private commercial projects without a sophisticated FM operation, the owner may list COBie as a requirement but have no actual CMMS to import it into and no process to verify delivery.

Before investing significant effort in COBie preparation, confirm with the owner or CM: Is there an actual CMMS or IWMS that will receive this data? Who is responsible for importing it? What is the acceptance criterion?

If the answer is “we don’t have a system yet” or “facilities will figure it out” — a simplified equipment register in Excel will often satisfy the intent without a full COBie implementation.

---

How COBie Is Produced from Revit

The data lives in the model

COBie data is not created at handover — it is collected throughout the project. The information in the Type worksheet (manufacturer, model number, warranty) comes from equipment submittals. The Component worksheet data (tag numbers, space locations) comes from the as-built model. The Document worksheet links come from the project closeout package.

Teams that try to produce COBie as a last-minute deliverable by filling in a spreadsheet from scratch will spend far more time than teams that populate the data in the model as the project progresses.

Shared parameters are the foundation

COBie data in Revit is stored as shared parameters. As covered in our article on Revit shared parameters for MEP, COBie parameters must be set up as shared parameters — not project parameters — to export correctly. The key Type worksheet parameters that must be present in the MEP families as shared parameters:

• COBie.Type.Manufacturer
• COBie.Type.ModelNumber
• COBie.Type.WarrantyDurationLabor
• COBie.Type.WarrantyDurationParts
• COBie.Type.ReplacementCost
• COBie.Type.ExpectedLife

Export methods

There are three ways to get COBie data out of Revit:

• IFC export with COBie property sets — Revit’s IFC export can include COBie property sets if the shared parameters are mapped correctly. The resulting IFC file can be processed by COBie-aware tools to generate the spreadsheet. Most reliable for open BIM workflows.
• Autodesk COBie Extension — a Revit add-in that exports COBie directly to Excel. Requires the shared parameters to be present and mapped. The extension is available through the Autodesk App Store.
• Manual spreadsheet assembly — pulling data from Revit schedules and formatting into the COBie template. Labor-intensive but sometimes necessary when the model data is inconsistent or the automated export produces errors.

---

COBie Quality Checks Before Delivery

• Every equipment Type has Manufacturer and ModelNumber populated — no “TBD” or blank cells
• Every Component has a unique tag number matching the equipment schedule
• Every Component is assigned to a Space — no components with blank space assignments
• Every Component is assigned to a System
• Warranty durations are populated for all equipment types
• Document links reference actual files in the project closeout package, not placeholder paths
• The COBie file validates against the COBie checker tool (free from the buildingSMART Data Dictionary)

Our COBie Capability

GEOMETRY-S includes COBie-ready shared parameter setup as a standard part of our MEP BIM project template for projects that specify a COBie deliverable. We populate Type and Component data as equipment submittals are received during construction, rather than assembling the COBie file at the end of the project.

If your project requires a COBie deliverable and you are not sure how to set up the workflow, we are happy to review the owner’s COBie requirements and advise on the correct preparation approach before modeling begins.