When a $400M power plant capital project reaches mechanical completion, the handover package it delivers to the operations team determines the quality of maintenance for the next 30 years. Yet industry studies consistently find that owner-operators spend 2–4% of total project cost — up to $16M on a large plant — manually re-entering, validating, and correcting asset data that should have arrived clean at handover. The problem is not the volume of information. It is the absence of a structured handover standard that forces contractors to capture it at source. BIM-based COBie (Construction-Operations Building Information Exchange) solves this by standardising what data is collected, who captures it, and when — delivering a complete, CMMS-ready asset register on day one of commercial operation. This template library gives power plant project teams a ready-to-use handover framework, from COBie worksheet structure to CMMS import mapping, built for direct import into Oxmaint CMMS — or book a 30-minute handover readiness session with our asset commissioning team.
The Handover Gap
Why Power Plant Handovers Fail Operations Teams
The day a power plant achieves commercial operation, the operations team inherits a maintenance problem. Contractors hand over pallets of paper manuals, disconnected spreadsheets, and incomplete equipment records. The operations team spends months — sometimes years — rebuilding the asset register that should have arrived complete. This is not a new problem. It is a structural one that BIM and COBie were designed to eliminate.
2–4%
of project cost spent manually re-entering data into CMMS post-handover (FIATECH)
$6–16M
hidden data validation cost on a $300–400M power plant project
60%
of that cost eliminated with progressive, structured COBie handover methodology
Paper-based O&M manuals
Contractors deliver hundreds of binders at project close. Operations teams spend man-years transcribing data — and still produce error-laden asset registers months after first fire.
Single end-of-project data dump
All handover data arrives at once, at the worst possible time. Errors cannot be traced back to source because the contractor has demobilised. Corrections require expensive change orders.
No CMMS-ready format
Even digital handover packages rarely arrive in a format that CMMS systems can ingest directly. Custom mapping, data cleansing, and manual import take months and cost six figures.
Missing maintenance data
Warranty periods, initial PM schedules, spare parts lists, and commissioning test records are inconsistently captured — leaving the maintenance team guessing on assets they have never operated.
BIM and COBie Explained
What BIM and COBie Actually Deliver to a Power Plant Operations Team
BIM (Building Information Modelling) produces the digital model of the plant during design and construction. COBie is the structured data extract from that model — the non-geometric subset of information that operations teams actually need: equipment types, components, locations, warranties, spare parts, maintenance tasks, and documents. COBie is not a software product. It is a data standard delivered as a structured spreadsheet that any CMMS can import.
BIM Model
What it contains
3D geometry of all plant structures and systems
Clash detection and spatial coordination
Design intent and engineering specifications
Construction sequences and phasing data
Asset attribute data — types, components, systems
O&M documents linked to model elements
Warranty and spare parts records
COBie Deliverable
What operations gets
Facility — project metadata and site context
Systems — every plant system with hierarchy
Types — equipment type records with specs
Components — individual asset instances with tag numbers
Spares — field-replaceable units per asset
Jobs — initial PM tasks and intervals
Documents — warranties, O&M manuals, test certs
Import Your COBie Handover Package Directly Into Oxmaint
Oxmaint accepts COBie-formatted spreadsheets and maps equipment types, component instances, PM tasks, and spare parts directly into your live asset register. First work orders generate automatically. No manual data entry. No six-month CMMS configuration project.
COBie Worksheet Structure
The COBie Worksheet — Power Plant Data Fields by Tab
A COBie handover package is structured as a multi-tab spreadsheet. Each tab captures a different category of asset information. For power plant projects, the tabs below are the minimum required for a CMMS-ready handover. The shaded fields are mandatory — blank cells in these columns block CMMS import and require manual correction.
Facility
Project Name
Site / Plant ID
Country & Phase
Project Manager
Contractor Contact
COBie Version
One row per project. Sets the master context for all other tabs.
Systems
System Name
Category (OmniClass)
Description
Parent System
P&ID Reference
Defines the hierarchy: Boiler, Turbine, Generator, BOP, auxiliaries.
Types
Type Name
Manufacturer
Model Number
Expected Life (years)
Replacement Cost
Nominal Power / Capacity
One row per equipment type. Multiple components share one type record.
Components
Component / Tag No.
Type Reference
Serial Number
Installation Date
System Reference
Location / Area
One row per asset instance. This becomes your CMMS asset register.
Spares
Spare Part Name
Type Reference
Part Number
Supplier
Stocking Quantity
Field-replaceable units per asset type. Feeds initial spare parts register.
Jobs
Job Name / Task ID
Type Reference
Task Description
Frequency / Interval
Trade / Skill Required
Duration (hours)
OEM-recommended PM tasks. Imports directly as CMMS work order templates.
Documents
Document Name
Document Type
Stage (Design / As-Built)
File Reference / URL
Expiry Date (warranties)
Links O&M manuals, test certs, warranties, and drawings to asset records.
Warranty
Warranty Name
Type Reference
Guarantor (Contractor)
Warranty Start Date
Duration (Parts / Labour)
Captures all warranty obligations. CMMS triggers alerts before expiry.
Required — blank = import blocked
Optional — recommended for complete CMMS record
Handover Timeline
Progressive COBie Data Capture — From Design to Day One Operations
The single biggest COBie mistake is treating it as a handover document. It is a progressive data collection process that runs for the life of the project. Data captured at source — during design, procurement, and construction — arrives accurate at handover. Data reconstructed at the end of a project arrives inaccurate, incomplete, and months late.
Design Phase
Facility, Systems & Types
Architect / Engineer of Record
Define facility metadata and system hierarchy (Facility, Systems tabs)
Populate equipment Types from design specifications and OEM datasheets
Set OmniClass classification codes for all maintainable asset types
Link design-intent O&M document references to type records
Procurement Phase
Manufacturer Data & Spare Parts
Contractor / Procurement Team
Update Types with confirmed manufacturer, model, serial number ranges
Populate Spares tab from OEM recommended spare parts lists
Capture warranty terms from purchase orders — Parts, Labour, Duration
Link final OEM O&M manuals and data sheets to Types as document references
Construction Phase
Components, Locations & As-Built Data
Site Contractor / BIM Manager
Populate Components with individual tag numbers, serial numbers, and install dates
Record physical locations and P&ID references for every component instance
Update as-built document links — replacing design-intent refs with as-built drawings
Log first-power and first-start dates for warranty period commencement
Commissioning Phase
Jobs, Test Records & Final Validation
Commissioning Agent
Populate Jobs tab with OEM-recommended PM schedules and intervals
Attach commissioning test certificates and loop check records to Components
Validate COBie completeness against CMMS import requirements — resolve gaps before handover
Confirm warranty start dates and issue Warranty tab to operations team
Day One Operations
CMMS Import & Live Maintenance Programme
Operations & Maintenance Team
Import validated COBie package into Oxmaint — asset register, types, components, spares
PM work orders generate automatically from Jobs tab data — first outage planned from day one
Warranty expiry alerts configured — no manual tracking, no missed claims
Spare parts register pre-loaded — procurement team can act on initial stocking requirements immediately
Power Plant Asset Register
COBie Component Template — Power Plant Critical Assets
The table below is a COBie-structured asset register starter for the major equipment classes in a thermal power plant. Tag number format follows ISA-5.1 instrumentation tagging convention. Each row maps directly to a CMMS asset record — populate serial numbers and installation dates at site, then import.
CMMS Integration
COBie to Oxmaint — How the Import Works
A validated COBie package imports into Oxmaint in a single session. The mapping below shows exactly which COBie field populates which Oxmaint field — so your handover team can verify completeness before the contractor demobilises, and your operations team launches maintenance on day one without manual data entry.
Components Tag No.
Asset ID / Tag Number
Components Serial Number
Asset Serial Number
Types Manufacturer
Asset Manufacturer
Types Expected Life
Asset Lifecycle / End-of-Life Alert
Components Installation Date
Asset Commissioned Date
Systems System Name
Asset Parent System / Hierarchy
Jobs Task + Interval
PM Work Order Template + Recurrence
Spares Part Name + Part No.
Spare Parts Register — linked to Asset
Warranty Start Date + Duration
Warranty Tracker + Expiry Alert
Documents File Reference
Asset Document Library (O&M, drawings)
Frequently Asked Questions
Power Plant Handover — Common Questions
Do we need BIM modelling software to use COBie for power plant handover?
No. COBie is most commonly delivered as a structured Excel spreadsheet (.xlsx). While BIM authoring tools can extract COBie data automatically from 3D models, a manually populated COBie spreadsheet — correctly structured and validated — achieves the same outcome. The priority is data accuracy, not generation method.
Oxmaint imports both BIM-extracted and manually populated COBie packages with the same mapping logic.
When should we specify COBie requirements in the project contract?
At EPC contract award — not at project close. COBie requirements must be part of the contractor's scope so that data capture responsibilities are assigned from day one. Contractors who discover COBie requirements at project end produce inaccurate, reconstructed data that defeats the purpose. Include COBie data drops as milestone deliverables at design freeze, equipment procurement, and mechanical completion.
Our team can help you draft handover data requirements in a 30-minute session.
How do we validate a COBie package before accepting it from the contractor?
Run an automated completeness check against your CMMS import requirements before accepting the handover package. Mandatory fields (tag numbers, serial numbers, installation dates, system references) must be 100% populated. Validate against your plant's tag register to confirm every P&ID asset has a COBie component record.
Oxmaint's COBie validation tool flags missing mandatory fields so gaps are resolved before the contractor demobilises — not after.
What happens to assets added or modified during construction — do they appear in COBie?
Only if your BIM manager maintains progressive COBie updates throughout construction. Any site modification — valve relocation, equipment substitution, tag number change — must be reflected in the COBie Components and Types tabs before handover. RFI and change order registers should trigger COBie updates as a contractual obligation.
Book a session to see how Oxmaint handles post-COBie asset modifications for assets changed after handover.
How long does CMMS import from a validated COBie package typically take?
A validated COBie package for a 500 MW plant — typically 3,000–8,000 component records — imports into Oxmaint in a single session of 4–8 hours, including field mapping, validation review, and first PM schedule activation. Compare this to the 6–18 months of manual data entry that characterises traditional handovers.
Start a free trial to test your COBie file against Oxmaint's import validator before your commercial operation date.
Stop Inheriting a Data Problem — Start Operations With a Complete Asset Register
Oxmaint is built to accept structured handover data from day one. COBie import loads your full asset register, PM schedules, spare parts, and warranty records in a single session. First work orders generate automatically. Your maintenance team starts with complete information — not a 12-month data entry project. Deployed and live in under 10 weeks.
