Digital Twin Handover in Owner Contracts

Most digital twin handovers fail not because the technology is immature - it isn’t - but because nobody wrote the requirement down. By the time substantial completion arrives, the contractor has handed over a Revit model last updated in design development, COBie sheets full of “n/a” entries, and a PDF O&M binder nobody asked for. The owner’s facilities team opens the model, can’t read it without a $10,000 software seat, and the digital twin dies in a shared drive folder within six months.

We provide field-verification scanning and BIM audit services across a range of project types - office towers, hospital wings, data center fit-outs, and university lab renovations. Every failed handover traces to the same root cause: the contract never defined what “done” looks like. This article gives you the language, the referenced standards, and the cost data to close that gap before it costs you a rework budget.

---

Why Most Digital Twin Handovers Fail Before Beneficial Occupancy

A large share of BIM practitioners - across both the UK and comparable US markets - report receiving models at closeout that required significant rework before they were usable for FM operations. The geometry is typically frozen at LOD 200. COBie data is absent or garbage. The model is georeferenced to Revit’s internal (0,0,0) origin rather than the owner’s campus coordinate system.

The failure modes cluster into four categories:

1. Wrong LOD: Contractor modeled MEP systems at LOD 200 (approximate massing) when the owner needed LOD 350 (fabrication-ready geometry with clearances). The HVAC model shows a generic air-handler box - no access panels, no coil dimensions, no connection points. Without a clearly stated LOD requirement in the contract, mechanical contractors routinely default to whatever is cheapest to produce.
2. Missing COBie data: The IFC export has geometry but zero asset attributes. The CMMS can’t auto-populate a PM schedule from a model with blank manufacturer and serial number fields.
3. No georeferencing: The model coordinate origin is (0,0,0) in Revit’s internal coordinate system. It can’t be overlaid on the owner’s GIS or campus master model without a full re-setup - a two-day rework that should have been a 30-minute QA check during design.
4. Proprietary format lock-in: The model was delivered only as a .RVT file for a Revit version the owner doesn’t own. No IFC export, no NWD. Effectively inaccessible two years post-handover when the contractor’s subscription lapses.

The root cause of every one of these failures is the same: the handover requirement was never written into the contract. The contractor assumed the owner wanted what was cheapest to produce; the owner assumed the contractor would deliver what was needed for FM. Neither assumption was correct, and no financial consequence was attached to getting it right.

Our scan-to-BIM services and deliverables include independent field-verification scanning specifically for this scenario - but a scan can’t fix a contract that never defined the target.

---

The Four Contractual Pillars of a Digital Twin Handover

Pillar 1 - Geometric Fidelity (LOD/LOA)

Specify minimum LOD by system using the BIMForum LOD Specification 2023 as the reference document - name the edition explicitly so there is no ambiguity about which version governs.

Our standard recommendation: LOD 350 minimum for mechanical, electrical, plumbing, fire protection, and structural steel. LOD 300 is acceptable for architectural shell and site elements where exact connection geometry is less critical for FM. Pair every LOD citation with an LOA citation (see the LOD vs. LOA section below) - one standard without the other leaves a contractual gap a contractor can exploit.

Pillar 2 - Data Richness (COBie / Asset Data)

Specify COBie 2.4 as the data exchange standard. Define which systems are in scope - at minimum: HVAC, plumbing, electrical distribution, and life-safety. Name the mandatory fields explicitly in a contract attachment rather than by reference:

• Asset.Name, Asset.Description, Asset.SerialNo
• Type.Manufacturer, Type.ModelNumber, Type.WarrantyDurationLabor
• Job.TaskNumber, Job.Frequency, Job.TaskType

Vague COBie requirements produce vague COBie deliverables. Name the fields, name the CMMS, and - critically - specify which IFC property set populates which COBie column (see the COBie section below for the Pset mapping table that contractors actually need).

Pillar 3 - Accuracy & As-Built Verification

Require an independent field-verification scan comparing the contractor’s design BIM against a registered point cloud before final payment is released. Our Trimble X7 terrestrial scanner delivers 3.5 mm point accuracy at 20 m. Tolerance threshold: no MEP or structural element may deviate more than 6 mm from the registered scan. Architectural envelope: 12 mm acceptable.

Pillar 4 - File Formats & Interoperability

Mandate open formats alongside native files. Require: IFC 4.x, native Revit RVT (current version per BEP), federated Navisworks NWD, and raw point cloud in .RCP, .E57, and .LAZ. Include a perpetual license clause: the owner retains an irrevocable, royalty-free license to all native files, export formats, and point cloud data. This matters when the contractor’s Revit subscription lapses 24 months post-handover - and it will.

---

Sample Contract Language You Can Adapt Today

Compatibility note: The following specification language is compatible with AIA G202-2013 (Project BIM Protocol Form) and ConsensusDocs 301 (BIM Addendum). For EJCDC-based projects, the applicable design-build agreement is EJCDC D-520; note that EJCDC E-520 is the Short Form of Agreement between Owner and Engineer for Professional Services, not a design-build form. Consult legal counsel before incorporating into binding documents.

---

Division 01 74 23 - BIM Closeout and Digital Twin Handover

1.1 BIM Execution Plan (BEP)
The Design-Build Entity shall submit a Project BIM Execution Plan (BEP) within 30 calendar days of Notice to Proceed (NTP), subject to Owner review and written approval by the Owner’s designated BIM Authority (Owner’s BIM consultant or Owner’s Project Manager, as identified in Exhibit ). The BEP shall be consistent with Owner’s BIM Requirements Document [v dated ___] and shall address: (a) authoring software, version numbers, and a commitment that authoring software and version shall not change without 30 days written notice to Owner and Owner’s written approval; (b) file-naming and layer/category conventions; (c) project coordinate reference system (State Plane [Zone] or as defined in Exhibit __); (d) model subdivision strategy by discipline and building section; (e) Common Data Environment (CDE) platform and Owner access credentials; and (f) handover milestone schedule tied to project phases.

BEP approval authority: The BEP must be approved in writing by the Owner’s designated BIM Authority before the first pay application is processed. Owner’s BIM Authority means [Owner’s BIM Consultant / Owner’s PM / Architect - circle one and identify by name and firm in Exhibit ___]. Ambiguity about who holds sign-off authority has invalidated BEP enforcement on numerous projects; name the individual, not the role class.

1.2 Authoring Software Change Control
If the Design-Build Entity or any sub-consultant proposes a change in BIM authoring software or version (e.g., a substitution of AutoCAD MEP for Revit MEP on the mechanical discipline) after BEP approval, the entity shall submit a written Change Request to Owner’s BIM Authority no fewer than 30 calendar days before the proposed change. The Change Request shall document: (a) the reason for the change; (b) the impact on LOD milestones, COBie export workflows, and CDE interoperability; and (c) a transition plan showing how existing model content will be migrated without data loss. Owner’s BIM Authority shall respond within 10 business days. Unauthorized mid-project authoring software changes are a breach of the BEP and shall be grounds for withholding the progress pay application for the affected discipline until the breach is remediated. (Note: A Revit-to-AutoCAD MEP switch mid-project without this clause is a documented failure mode - the COBie IFC export workflow breaks, property set mapping resets, and the owner inherits a hybrid-format model with no enforcement remedy.)

1.3 LOD Schedule by Phase

LOD 350 vs. LOD 400 at Final Handover - MEP/FP: LOD 350 is the minimum for all MEP/FP systems. LOD 400 (fabrication/assembly detail, shop-drawing accuracy, LOA 50 / ±1-2 mm) is required for: (a) prefabricated piping assemblies 4” diameter and larger; (b) custom air-handling units with non-standard coil configurations; (c) mission-critical power distribution systems (switchgear, UPS, PDU) in data center and hospital environments where the owner has confirmed a BACnet/IP integration requirement; and (d) any system where the owner’s commissioning agent has issued a written request for LOD 400 geometry during construction. All other MEP/FP systems remain at LOD 350.

All geometry shall meet LOA 20 (±6 mm) per USIBD Guide for LOA for systems at LOD 350 or greater. Structural steel, primary ductwork, pipe mains 2” and larger, and electrical conduit runs 1” and larger shall be individually modeled at LOD 350/LOA 20 minimum.

1.4 COBie Deliverable Trigger
COBie 2.4 data shall be submitted as a validated XLSX and IFC export no later than Substantial Completion. COBie shall cover all systems listed in Exhibit __ (HVAC, plumbing, electrical distribution, fire protection, life-safety). Mandatory fields per Section 01 74 23 Attachment A. Validation shall be performed using Solibri Model Checker or BIMcollab; the Owner-accepted validation report shall accompany the COBie deliverable. Final payment shall not be released until a passing COBie validation report is on file.

1.5 Field-Verification Scan - Pay-Application Condition
As a condition of the final pay application, the Owner may commission (at Owner’s election and cost, as specified in the Division 01 Allowance) an independent terrestrial laser scan of the completed facility. The scanning contractor shall register the point cloud to the project coordinate system at ≤3 mm RMS registration residual. A deviation analysis shall be performed comparing the registered point cloud against the contractor-submitted BIM. Any element deviating more than 6 mm (MEP/structural) or 12 mm (architectural) from the scan shall be identified in a deviation report (color-coded heat map + BCF markup). The Design-Build Entity shall correct all flagged elements and resubmit within 10 business days. Final payment (or [___]% retainage) shall not be released until the Owner accepts the corrected model.

---

Where these clauses live in the spec: Primary home is Division 01 (specifically 01 74 23 or a standalone BIM Protocol exhibit). Cross-reference in trade specs: 23 09 00 (HVAC instrumentation and controls digital twin data), 26 00 00 / 16 00 00 (electrical distribution asset data), 21 00 00 (fire protection COBie scope). Do not bury handover requirements only in trade specs - they will be missed by the GC’s project manager until closeout.

Who pays for the verification scan: Budget 0.1-0.3% of total construction cost for a commercial building, structured as an owner-direct cost in the Division 01 allowance. For a $10M renovation, that’s $10,000-$30,000. Do not put this in GC scope - it gets value-engineered out in the first VE meeting every time.

---

LOD vs. LOA: Why Contracts That Cite Only One Standard Are Incomplete

These are two different standards measuring two different things.

• LOD (Level of Development) - governed by BIMForum LOD Specification 2023. Defines what information is included in a model element: its geometry, attached data, and the reliability of that information. LOD answers “what’s in the model and how complete is it?”
• LOA (Level of Accuracy) - governed by USIBD Guide for LOA. Defines how accurately the modeled geometry represents physical reality. LOA answers “how close to true dimensions is the geometry?”

A contractor can deliver a fully LOD 350-compliant model - every property set populated, every connection shown - where every duct run is modeled 50 mm off its actual centerline. That model fails LOA 20 but passes a pure LOD check. The dual citation is what closes that gap.

Write it this way in your contracts: “Primary structural steel and MEP pipe mains 2” and larger shall be modeled at LOD 350 / LOA 20 (±6 mm) per BIMForum LOD Specification 2023 and USIBD Guide for LOA.” That dual citation is what contractors need to bid and deliver to a defined standard.

For a deeper breakdown, see LOD 200 vs LOD 300 in scan-to-BIM projects and digital twin services and deliverables explained.

---

The As-Built Scan Verification Clause: How It Works in Practice

Here’s the step-by-step workflow for field-verification scan engagements:

1. Contractor submits design BIM at substantial completion - Revit RVT + federated NWD, registered to project coordinate system.
2. Owner commissions independent scan. We deploy a Trimble X7 terrestrial scanner (3.5 mm point accuracy at 20 m) for terrestrial scanning, with handheld scanners available for detailed or hard-to-reach components. Station spacing: one scan position per 400-600 sq ft of floor area, with ≥20% overlap between adjacent stations. A 50,000 sq ft building typically requires 90-130 scan stations and one to two field days.
3. Point cloud registration. We register all scan stations in Trimble RealWorks or Autodesk ReCap Pro, targeting ≤3 mm RMS residual across the full point cloud. The registered cloud is exported as .RCP for Revit linking and .E57 for archival. For how point cloud import into Revit works, we use ReCap as the processing bridge between raw scan data and the Revit environment.
4. Deviation analysis. The registered .RCP is linked into Revit or the .E57 is imported into Navisworks Manage. We run a geometric deviation analysis comparing model element faces against the nearest cloud points. For complex curved geometry - custom ductwork, structural connections, historic facades - we use CloudCompare’s M3C2 distance algorithm, which handles non-uniform surface normals correctly and produces a signed deviation map rather than a simple nearest-point distance.
5. Deviation report issued. The report contains: (a) a color-coded heat map showing deviation magnitude across the building plan and sections, scaled at ±6 mm / ±12 mm thresholds; (b) a table of non-conforming elements sorted by Revit category and peak deviation magnitude; (c) a BCF markup file for direct import into Revit or BIMcollab; (d) maximum, mean, and 90th-percentile deviation per building zone.
6. Contractor corrects and resubmits. Targeted spot checks confirm corrections on flagged elements. Final payment release follows Owner written acceptance of the corrected model.

Real cost for a 50,000 sq ft commercial building - field work (1-2 days), registration and processing (0.5 days), deviation analysis, and report - runs $4,000-$9,000. Undetected field-relocated MEP systems can produce six-figure renovation change orders when capital planning proceeds from incorrect as-built geometry - the cost of a verification scan is a fraction of that exposure.

See also writing a complete laser scanning deliverable specification and scan-to-BIM clash detection tolerances and settings for the technical parameters behind this workflow.

---

COBie: The Data Layer That Makes the Digital Twin Useful

COBie (Construction Operations Building Information Exchange) is a data schema that maps asset information from the construction model to the FM/CMMS system. It can be delivered as XLSX, as IFC property sets, or via direct CMMS API integration.

A BIM model without COBie data is geometry only. It won’t auto-populate a PM schedule. It won’t generate a work order. It won’t tell the tech which filter goes in which AHU.

Critical COBie sheet tabs for FM handover:

IFC Property Set to COBie Field Mapping

This is the number-one practitioner pain point - which IFC Pset populates which COBie column - and it is almost never specified in contracts. When it isn’t specified, every subcontractor maps it differently, and the integrator spends two weeks of billable time reconciling the resulting inconsistency. Define it in the BEP and reference it in Section 01 74 23 Attachment A:

Include this table as Attachment A to Section 01 74 23. Require that the BEP confirm Revit shared parameter names that map to these IFC Psets before the first pay application.

CMMS-Specific COBie Import Behavior

Not all CMMS platforms handle COBie the same way. Specifying “COBie-ready” without naming the owner’s CMMS platform is insufficient:

Contract language: “COBie 2.4 deliverable shall be validated against the Owner’s [Maximo / Archibus / ServiceNow / eMaint] CMMS import workflow. The Design-Build Entity shall provide a completed COBie-to-CMMS field mapping table, approved by Owner’s FM Director, as a condition of Substantial Completion payment.” Leaving the CMMS name out of the contract means you discover the import incompatibility the week the FM team tries to go live.

Contract-level COBie failure modes to guard against:

• Blank “n/a” entries in mandatory fields - require validation rules that reject null values in specified columns
• Duplicate GUIDs across components - Solibri and BIMcollab both flag these; a clean validation report is a contract deliverable
• Mismatched Space names between architectural and MEP models - define the authoritative Space naming convention in the BEP and confirm it against the CMMS room-numbering schema before CDs are issued

---

Coordinating the BIM Execution Plan (BEP) With Handover Requirements

The BEP is the contractor’s promise of how they’ll deliver. If it doesn’t mirror your contract requirements, you have two documents that may contradict each other - and contract precedence language (typically “the Agreement governs over exhibits”) may still leave gaps that require expensive legal interpretation to resolve. The correct fix is to make the BEP a contract-required submittal with Owner written approval as a condition of the first pay application, not a reference document.

Required BEP contents (specify these in the contract):

• Authoring software and version numbers (Revit 2024, AutoCAD MEP 2024, etc.) - and the change-control clause from Section 1.2 above
• File-naming convention standard - specify CSI MasterFormat or owner-defined prefix schema
• Project coordinate reference system: State Plane coordinate system and zone, or project-specific grid with a tie-in to a named, monument-referenced survey control point
• Model subdivision strategy: discipline-based models (Arch, Struct, MEP) federated in Navisworks - or zone-based for campuses larger than 500,000 sq ft
• CDE platform (Autodesk Construction Cloud/BIM 360, Procore, ProjectWise) with Owner admin-level access from NTP through the warranty period minimum - not just at handover
• Handover milestone schedule with deliverable due dates tied to specific pay applications, not just phase labels

Model format at handover: Specify both federated and discipline-specific. A federated NWD for coordination and visualization, plus separate discipline RVT files for long-term maintainability. A single monolithic Revit model is harder to update when systems are modified; separate discipline files federate cleanly in Navisworks but require a documented federation protocol.

Version control: All model versions stored in the CDE with owner read access from NTP through the warranty period minimum. Continuous CDE access also gives the owner a timestamped paper trail if model quality degrades or geometry is backdated during construction - a documented failure mode on fast-track projects where the model isn’t updated to reflect field changes in real time.

See scan-to-Revit point cloud modeling workflow for how we handle point-cloud-to-model coordination within a CDE environment on active construction sites.

---

Special Considerations for Complex or Historic Buildings

Renovation Projects: Phased Scanning for Occupied Buildings

When an existing building is being renovated, the original design drawings are typically 20-40 years old and wrong in ways that matter: duct runs relocated during previous tenant fit-outs, structural reinforcements not shown on as-drawns, and sprinkler systems reconfigured without as-built updates. The as-built scan is the ground truth, not a verification check against existing documents.

Specify for renovation scan-to-BIM: scan station spacing ≤5 m, overlap ≥20%, registration accuracy ≤3 mm RMS. The point cloud becomes the LOA reference against which the BIM is verified rather than a secondary check.

Phased scanning for occupied buildings introduces constraints that must be addressed in the specification:

• After-hours scanning windows: In occupied office, healthcare, and institutional buildings, scanning must occur during off-hours to avoid people-occlusion artifacts in the point cloud. Specify scanning access windows (e.g., 10 PM-6 AM on weekdays, all-day Saturday) and confirm them with the owner’s facilities director before mobilization. Budget an additional 20-30% for after-hours crew premium.
• Zone-by-zone delivery: For a large occupied hospital renovation, zone-specific registered point clouds and partial BIM models are typically delivered in three to five phases aligned with the construction phasing plan. Each phase delivery uses the same project coordinate origin, registered to the same survey control points, so phase deliveries merge cleanly in the CDE.
• Modeling around live operations: Live HVAC, electrical, and plumbing systems that remain operational during renovation must be modeled at their current as-installed location, not the design location. Detailed scanning of complex multi-floor environments - including active biosafety labs or other restricted areas - is completed in phased after-hours sessions using our Trimble X7 terrestrial scanner, with the resulting existing-conditions BIM delivered at LOD 350 for the renovation design team before the first wall comes down. This approach routinely surfaces conflicts between active ceiling-level mechanical systems and proposed structural work that are not visible on decades-old as-drawns.
• Safety and coordination: Confirm PPE requirements, area shutdowns, and security escort protocols with the owner’s facilities team before mobilization. These are specification items, not field assumptions.

Scan deliverable expectations are covered in what your laser scanning deliverables should include.

Historic Structures (HBIM)

For buildings with Historic Preservation Tax Credit involvement, coordinate with SHPO early. HBIM handover should include:

• Photogrammetric texture overlays registered to the point cloud (industry scanners such as the NavVis VLX are common for interior corridors; high-density color scanning is used for facade and decorative elements)
• Feature-rich geometry at LOD 300+ per ICOMOS documentation standards and NPS Preservation Brief guidance
• A separate preservation documentation package including orthographic elevations, section cuts, and annotated photographic record

Specify that the full-resolution point cloud and photogrammetric data be archived in the owner’s CDE at native resolution - these records are irreplaceable if the building is damaged. Compressed deliverables are acceptable for working use; uncompressed originals must be in the archival package.

Mission-Critical Facilities (Data Centers, Hospitals, Labs)

Real-time sensor integration readiness must be contractually specified. Require:

• IFC property sets for IoT tag attachment: BACnet point name, IP address, and physical location reference populated in the Component Pset before handover
• GUID stability guarantees across model updates: the contract must prohibit regenerating element GUIDs during model maintenance after handover. A GUID change in Revit breaks every downstream CMMS work order, every COBie Component.ExtIdentifier link, and every BACnet-to-BIM mapping simultaneously
• Verified COBie-to-CMMS API compatibility tested against the owner’s specific platform (Maximo, ServiceNow, Archibus, eMaint - name it; see the CMMS table above) before final payment release

---

Cost Reality: What Owners Should Budget for a Proper Digital Twin Handover

Budget breakdown for a 50,000 sq ft commercial building:

Context: Accurate as-built documentation commonly produces meaningful FM cost avoidance over a building’s lifecycle - driven primarily by reduced re-survey costs at renovation, reduced PM schedule errors from accurate equipment data, and avoided emergency repairs from undetected system conflicts. At a $27,500 investment on a $10M renovation, the verification scan and BIM audit address exposures that can reach multiples of that cost when incorrect as-built geometry drives capital planning decisions.

To illustrate the stakes: an incorrect as-built model showing primary chilled-water mains that were actually field-relocated during construction can result in a six-figure renovation change order issued against that wrong geometry before the error is caught. The verification scan and BIM audit to prevent it are a fraction of that cost.

Structuring the cost: Specify as an owner-direct cost in a Division 01 allowance - a named line item, not buried in GC scope. Language: “Owner’s Digital Twin Verification Allowance: $[___]. This allowance covers independent field-verification scanning, BIM audit, COBie validation, and deviation reporting as described in Section 01 74 23.” When this budget lives in GC scope without explicit protection, it disappears in the first value-engineering meeting.

---

Digital Twin Handover Checklist: What to Demand at Closeout

Use this as both a contract exhibit and a closeout punch list. Each item includes the acceptance criterion - not just the deliverable name.

Item 13 - as-built 2D drawings in PDF and DWG - is frequently omitted from BIM-centric closeout checklists. Most AHJ plan review processes, fire marshal inspections, and certificate-of-occupancy filings still require 2D as-builts. FM staff performing quick lookups at a job site don’t open Revit; they open a PDF. Both deliverables are necessary.

Final note: Even with all 16 items checked, owners without in-house BIM expertise should retain a scan-to-BIM consultant to perform the item 16 acceptance sign-off. The contractor cannot validate their own model against physical reality - that is the entire point of independent verification.

---

FAQ

What LOD and LOA should I require for a digital twin handover - and what is the difference between them?

LOD and LOA answer different questions. LOD (per BIMForum LOD Specification 2023) governs what information is in the model - geometry, attached data, and the reliability of both. LOA (per USIBD Guide for LOA) governs how accurately that geometry represents physical reality. A model can be fully LOD 350 compliant - every connection shown, every COBie field populated - and still fail LOA 20 if the duct runs are modeled 50 mm off their actual centerlines.

For active FM systems, require LOD 350 / LOA 20 (±6 mm) as the floor. LOD 300 / LOA 20 (±6-12 mm) is acceptable for architectural shell. For mission-critical MEP systems in data center or hospital environments with confirmed BACnet integration requirements, require LOD 400 / LOA 50 (±1-2 mm) on those specific systems. Write the requirement as: “Primary HVAC systems: LOD 350 / LOA 20 (±6 mm) per BIMForum LOD Specification 2023 and USIBD Guide for LOA.”

Which file formats must be in a digital twin handover specification - and why does the point cloud matter?

Minimum required set: native Revit RVT (version per BEP), federated Navisworks NWD, IFC 4.x, COBie 2.4 XLSX, and raw point cloud in .RCP, .E57, and .LAZ. The point cloud - registered at ≤3 mm RMS in ReCap or Trimble RealWorks - is the only deliverable that cannot be fabricated or backdated in an office. IFC 4.x and E57 are your open-format insurance: when the project team’s Revit subscription lapses, the IFC opens in Solibri Viewer (free), Tekla BIMsight (free), or any IFC-compliant viewer. E57 opens in CloudCompare (open source). Proprietary format lock-in is not a theoretical risk; it is a documented failure mode on projects 18-36 months post-handover.

How does the verification scan pay-application clause work in practice?

The contractor submits BIM at substantial completion. The owner commissions an independent scan - we deploy a Trimble X7 at one station per 400-600 sq ft, registering in ReCap or Trimble RealWorks at ≤3 mm RMS. We run a deviation analysis in Navisworks or CloudCompare, produce a color-coded heat map and BCF markup, and issue the deviation report to the contractor with a 10-business-day correction window. Final payment - or a defined retainage percentage, typically 2-5% - is withheld until the owner accepts the corrected model. The financial lever is what makes the clause effective. Without it, model corrections compete against the contractor’s next project.

What is the number-one COBie failure mode, and how do I prevent it in the contract?

The most common failure is not missing data - it is unmapped data: IFC property sets that are populated in the model but map to the wrong COBie field, or not at all, because the BEP never specified the Pset-to-COBie column mapping. The result is a COBie XLSX where geometry exists in IFC and data exists in Revit shared parameters, but the CMMS import gets blank Type.Manufacturer and null Job.Frequency fields. Prevention: include the IFC Pset-to-COBie field mapping table (see the table in the COBie section above) as Attachment A to Section 01 74 23, require the contractor to confirm Revit shared parameter names that map to those Psets in the BEP, and make a passing Solibri or BIMcollab validation report a pay-application condition at Substantial Completion, not a post-close deliverable.

My owner uses Maximo (or ServiceNow / Archibus / eMaint) - does COBie import work natively?

No, not for all platforms, and the differences are material. Maximo has no native COBie XLSX import - you need a custom ETL script or TRIRIGA Integration middleware, and Component.ExtIdentifier GUIDs must be pre-mapped to Maximo Asset Numbers before import. Archibus does have native COBie import via its BIM Integration module (v25.3+), but Space.Name must match Archibus Room Number exactly or records silently drop. ServiceNow requires an Integration Hub spoke or third-party connector. eMaint accepts CSV imports from the Component and Type sheets but does not consume the Job sheet natively, so PM schedules must be built manually from COBie Job data. Name your CMMS platform in the contract and require a completed COBie-to-CMMS field mapping table approved by the Owner’s FM Director as a Substantial Completion deliverable.

Where exactly in the contract should these requirements live, and who has sign-off authority on the BEP?

Primary home: Division 01, section 01 74 23 (or a standalone BIM Protocol exhibit referencing AIA G202-2013 or ConsensusDocs 301). Cross-reference - do not repeat in full - in trade specs 23 09 00, 26 00 00, and 21 00 00. The BEP must be a required contract submittal within 30 days of NTP, subject to written approval by a named individual - the Owner’s BIM Consultant, Owner’s PM, or Architect, identified by name and firm in Exhibit ___. “Owner review and approval” without naming who holds approval authority is a documented contract ambiguity: on projects where sign-off authority is undefined, BEP approval gets routed to whoever is available, and enforcement at closeout becomes a he-said-she-said dispute. Name the individual.

---

Get Your Digital Twin Handover Right - Before Final Payment

The contract language, checklists, IFC mapping tables, and cost data in this article address the documented failure modes in digital twin handovers: as-built models showing MEP runs that were field-relocated during construction; ductwork modeled at LOD 200 massing where LOD 350 was needed; mid-project authoring software substitutions that broke the COBie IFC export workflow. The specification language above was written to prevent each of these.

We can help in three ways:

1. Independent field-verification scanning - we mobilize our Trimble X7 terrestrial scanner (with handheld scanners available for detailed components), register the point cloud at ≤3 mm RMS in ReCap or Trimble RealWorks, and deliver a deviation heat map and BCF report against your contractor’s BIM before final payment releases. Engagements start at $4,000 for buildings under 30,000 sq ft.
2. Sample BIM Requirements Document - a complete owner BIM requirements document with the IFC Pset-to-COBie mapping table, the CMMS-specific import guidance, and Division 01 specification language, compatible with AIA G202-2013 and ConsensusDocs 301. For EJCDC-based projects, the design-build agreement form is EJCDC D-520; EJCDC E-520 is the owner-engineer professional services agreement.
3. COBie validation and CMMS integration review - we validate your COBie deliverable against your specific CMMS platform (Maximo, Archibus, ServiceNow, or eMaint) before you accept it, using the platform-specific import workflow rather than a generic schema check.

Contact us at weare-capture.com to scope a field-verification scan or request the sample BIM Requirements Document.