Why Should Owners Specify COBie at the EIR Stage, Not at Handover?

TL;DR

COBie (Construction-Operations Building Information Exchange) is a structured spreadsheet format for handing over asset data from construction to facility management. Most BIM engagements end where the operational phase begins — the contractor delivers PDFs and the FM team is asked to make do. This is a missed opportunity at every level. The data exists in the BIM model, FM platforms can consume structured data, and COBie is the bridge. The single most expensive mistake owners make is specifying COBie too late — adding it as a handover requirement after the model is mostly complete typically costs several times what it would have cost to capture as the model was built.

Definitions

COBie is a structured spreadsheet format defining exactly which fields of asset data should be delivered at handover, in what columns, with what relationships between sheets. It is open-format and platform-agnostic.

CAFM (Computer-Aided Facility Management) is the platform category used by FM teams — Maximo, Archibus, FM:Systems, Planon, and others.

CMMS (Computerized Maintenance Management System) is closely related to CAFM, often the same platform with maintenance focus.

EIR (Exchange Information Requirements) is the client’s written specification for what information they need at each project stage.

Asset register is the structured list of all maintainable assets in a facility.

The conversations behind this article

“We just took handover. The FM team has 3,000 PDFs and a model file they can’t open.”

“The client wants COBie at handover. We’re three months from completion. What do we do?”

“Our CAFM platform expects specific attribute names. The model has different naming. Do we re-key everything?”

“We’re an owner. We bought a building expecting BIM-ready FM data. We got binders. What’s the recourse?”

These conversations almost always come too late. The work to fix them is more expensive than the work to prevent them.

What is COBie, in plain terms?

COBie is a spreadsheet. That’s it. A structured one with rules — but a spreadsheet.

It defines exactly which fields of asset data should be delivered at handover, in what columns, with what relationships between sheets. It’s open-format. Almost any FM platform — Maximo, Archibus, FM:Systems, Planon, even custom in-house systems — can ingest COBie. It is the lingua franca for asset data exchange.

What does a COBie deliverable contain?

Why is the lifecycle math compelling?

Across a typical commercial building’s 50-year lifecycle, design and construction account for a small fraction of total cost. Operations and maintenance — energy, repairs, replacements, FM staff — account for most of it.

Yet most BIM engagements end exactly where the operational phase begins. The contractor delivers a stack of as-built drawings (PDF), some operating manuals (PDF), and maybe a model file. The FM team — staffed and structured for spreadsheets and CAFM platforms — is handed PDFs and asked to make do.

Why specify COBie at the EIR stage, not at handover?

This is the single most expensive mistake owners make.

If COBie is added as a handover requirement after the BIM model is already mostly complete, contractors charge a premium to retrofit the data — sometimes several times what it would have cost to capture as the model was being built. Worse, the data quality is degraded because attributes were filled in retrospectively rather than as decisions were made.

The fix is simple in principle:

1. Include COBie requirements in the Exchange Information Requirements (EIR) at the start of the project.
2. Specify which COBie sheets are required, which attributes are mandatory per element category, and what FM platform the data will be loaded into.
3. Reference COBie in the BEP so the modelling team builds discipline around it from day one.

What does COBie specification look like in Saudi tenders?

• Hospitality and large mixed-use (Red Sea Global, Diriyah, AMAALA) — full COBie deliverable expected at handover, often integrated with the operator’s CAFM platform.
• Government and ministry projects (MoMRAH-overseen, Royal Commission programs) — COBie referenced in EIRs.
• Healthcare (Ministry of Health-overseen projects) — COBie aligned with ministry’s FM data structure.
• Infrastructure (Riyadh Metro, NEOM Spine) — COBie-aligned asset data with linear referencing.
• Residential at scale (ROSHN, NHC) — COBie typically simplified, focused on common assets.

What should an owner do this quarter?

1. Audit your current FM data sources. If your facility management team can answer the question “what asset is in this room and when was it installed?” within 30 seconds, you don’t need COBie.
2. Add COBie to your standard EIR template. Specify required sheets, mandatory attributes per category, and the target FM platform.
3. Brief your FM team on what they’re getting. A COBie-structured handover is only useful if the receiving team knows how to ingest it.

What should a contractor do this quarter?

1. Read EIRs for COBie language carefully. Generic “COBie data” without specifics typically means the client doesn’t fully know what they want.
2. Include COBie in your BEP from day one. Author a parameter set in the modelling standard.
3. Charge for it. COBie work is real work. Price it explicitly rather than absorbing it into general BIM scope.

How does OnePoint engage on COBie?

• EIR review and authoring — We review or author COBie sections of the EIR.
• COBie-disciplined modeling — We embed COBie attribute requirements in the modeling standard from project start.
• Handover preparation — We export COBie at handover, run QA against the target FM platform’s import requirements, and support the FM team’s ingestion process.
• Retrofit COBie on existing models — Where COBie was specified late, we can retrofit the data, though we’ll be honest about the cost premium.

See OnePoint’s Asset & FM Management service →

Frequently asked questions

Is COBie required by Saudi regulation?

Not by general regulation, but specific government programs and project types increasingly require it via EIR specification.

Can COBie work without BIM?

Technically yes — COBie is a spreadsheet format. In practice, populating COBie manually for a building of any size is prohibitive. BIM is the practical authoring environment.

What if our project’s BIM model is already complete and COBie wasn’t specified?

It can be retrofitted, but expect a cost premium versus building it in from the start.

Does COBie work with Revit?

Yes. Revit has built-in COBie export capability, and several add-ins extend it.

Can OnePoint integrate COBie data directly with our CAFM platform?

We deliver COBie in the standard format. Direct integration with a specific CAFM platform requires platform-specific configuration as a separate scope.

Key takeaways

• COBie is a structured spreadsheet format that bridges BIM-era asset data with FM-era platforms.
• Most BIM engagements end where operations begin — leaving the FM team with PDFs instead of structured data.
• The lifecycle math heavily favours specifying COBie: design and construction is the small cost; operations is the dominant cost.
• The single most expensive mistake is specifying COBie at handover instead of at the EIR stage.
• Saudi sectors increasingly specify COBie or COBie-equivalent — hospitality, government, healthcare, infrastructure.

Related reading

• Why Is BIM No Longer Optional in Saudi Arabia?
• What Does LOD 100 to LOD 500 Actually Mean?
• Scan to BIM: When the Drawings Don’t Exist (Or Lie)
• 4D and 5D BIM: Making Schedule and Cost Visible
• Choosing a BIM Partner: 7 Questions That Tell You What You’re Buying

OnePoint is a Saudi-registered BIM Solutions practice based in Riyadh, established in 2017. To discuss a project, request a quote or reach us at info@onepoint.com.sa.