COBie Requirement Review
Review supplied project templates, required fields, data rules and handover expectations.
COBie • ASSET INFORMATION • BIM HANDOVER • FACILITIES
COBie & BIM Handover Data Services
Structure project and asset information for digital handover using defined COBie or client-specific information requirements — connecting facilities, floors, spaces, equipment, asset types, systems, attributes, documents and other required operational data.
Define
Required Information
Collect
BIM & Asset Data
Validate
Required Fields
Deliver
Structured Handover
Structured Handover Information
Project Closeout Should Deliver More Than a Folder of Files
Facility teams may receive drawings, models, schedules, manuals, submittals and equipment records from multiple sources.
COBie-style structured handover organizes selected building and asset information so that key data can be transferred in a more controlled and reviewable format.
The exact data structure and acceptance criteria should always follow the actual project requirements, owner requirements, templates and contractual deliverables.
BIM + Asset Records + Facility Information → Structured Digital Handover
Project-defined data
prepared for
review and downstream use.
COBie & Handover Capabilities
Turn Project Information into Structured Handover Data
The data scope can be aligned with supplied owner information requirements, project templates, BIM execution requirements and agreed facility-handover deliverables.
COBie Data Preparation
Structure project-defined facility, space, asset and equipment information.
BIM-to-Handover Mapping
Connect selected model information with required handover data fields.
Asset Information Preparation
Organize project-defined equipment, component and asset information for handover.
Facility & Space Information
Structure building, floor, space and project-defined zone information.
System Information Mapping
Organize project-defined equipment relationships around required facility systems.
Document References
Structure references to supplied O&M manuals, warranties, submittals and related records.
COBie Data Validation
Review required fields, duplicates, references, formats and project-defined rules.
Digital Handover Support
Prepare agreed datasets, models and supporting information for final handover.
Structured Information
Typical Information Areas Within a COBie Workflow
Exact worksheets, columns, mandatory fields and project rules should follow the supplied project requirement.
DATA 01
Facility
Project-defined
facility
and building-level
information.
DATA 02
Floors
Building floor
or level
information required
for handover.
DATA 03
Spaces
Required room,
space
and location
information.
DATA 04
Zones
Project-defined
groupings of
spaces or
operational areas.
DATA 05
Types
Common equipment
or component
type information.
DATA 06
Components
Individual
project-defined
maintainable assets
or equipment records.
DATA 07
Systems
Required relationships
between equipment
and facility systems.
DATA 08
Documents
References to
supplied records,
manuals
and supporting information.
DATA 09
Attributes
Additional
project-defined
properties associated
with required records.
DATA 10
Contacts
Project-defined
contact information
where required
in the handover structure.
DATA 11
Spares
Supplied spare-part
information
where included
in project requirements.
DATA 12
Jobs / Tasks
Project-defined
operational
or maintenance
task information
where required.
Handover Data Control
A Completed Spreadsheet Does Not Automatically Mean the Handover Data Is Correct
Every required cell can appear populated while asset IDs, locations, classifications, document references or model relationships remain incorrect.
Handover QA should therefore review the meaning and relationship of the information — not only whether a field contains text.
Field Populated
Confirms data exists —
not that it
is correct.
Asset Match
Confirm information
belongs to
the intended
asset or component.
Location Match
Verify equipment
is associated
with the
correct space
or location.
Requirement Match
Check data
against the
actual project
handover requirement.
COBie Handover Workflow
From Information Requirements to Reviewed Handover Data
01
Define
Review required fields, templates, data rules and project deliverables.
02
Collect
Gather BIM, schedules, asset registers, submittals and closeout records.
03
Map
Map source information to required handover fields.
04
Populate
Populate agreed facility, space, asset and system information.
05
Validate
Review required values, references, duplicates and relationships.
06
Deliver
Prepare the agreed handover dataset and supporting files.
Asset & Equipment Information
Connect Handover Data to the Correct Assets
ASSET 01
Asset ID
Project-defined
identifier
connecting equipment
and handover records.
ASSET 02
Asset Type
Equipment category,
family
or project-defined type.
ASSET 03
Manufacturer
Supplied
manufacturer information
where required.
ASSET 04
Model Reference
Supplied product
or equipment
model information.
ASSET 05
Serial Reference
Asset-specific
serial information
where provided.
ASSET 06
Space
Required room
or spatial
location reference.
ASSET 07
System
Project-defined
facility-system
association.
ASSET 08
Installation Information
Supplied installation
or commissioning
data where required.
ASSET 09
Warranty Reference
Project-provided
warranty information
where applicable.
ASSET 10
O&M Reference
Link or reference
to supplied
operations documentation.
ASSET 11
Classification
Project-required
classification information
where applicable.
ASSET 12
Status
Required handover
or information
status reference.
Model & Data Relationship
The BIM Model and the Handover Dataset Should Describe the Same Facility
When asset information exists both in BIM and in structured handover data, the relationships should be controlled.
Equipment names, asset IDs, spaces, systems and required parameters should be reviewed so that the digital handover does not describe a different condition from the final project record.
BIM Object
Represents the
required digital
model element.
Asset Record
Carries required
operational
or handover information.
Shared Identifier
Helps maintain
the relationship
between model
and record.
QA Review
Confirms required
model-data
relationships
before delivery.
COBie Data Validation
Validate More Than Empty Cells
CHECK 01
Required Fields
Review completion
of project-defined
mandatory information.
CHECK 02
Data Format
Check supplied
project formatting
and field rules.
CHECK 03
Asset IDs
Review asset
identifiers
for required
consistency.
CHECK 04
Duplicate Records
Identify duplicated
equipment
or conflicting
data entries.
CHECK 05
Space References
Confirm component
locations reference
intended spaces.
CHECK 06
Type Relationships
Review component
relationships
with required
equipment types.
CHECK 07
System Relationships
Review required
asset-to-system
associations.
CHECK 08
Document References
Check required
supporting-document
references.
CHECK 09
Model Alignment
Compare key
information against
the agreed
record model.
CHECK 10
Naming Consistency
Review project-defined
naming conventions
across records.
CHECK 11
Source Traceability
Maintain clear
source references
where the workflow requires them.
CHECK 12
Acceptance Requirements
Review against
the actual
project acceptance criteria.
Inputs & Deliverables
Project Records In. Structured Handover Data Out.
Typical Inputs
- COBie / handover template
- Owner information requirements
- BIM execution requirements
- As-built BIM models
- Equipment schedules
- Asset registers
- Space schedules
- Approved submittals
- O&M documentation
- Commissioning / closeout records
Typical Deliverables
- Project-defined COBie dataset
- Structured facility information
- Floor and space information
- Asset / component records
- Equipment type information
- System relationships
- Document references
- Attribute information
- Data validation report
- Agreed digital handover package
COBie QA / QC
Check Information Before Final Handover
Structured handover data can affect downstream facility workflows, so project-defined information should be reviewed before issue.
QA can include required fields, identifiers, type relationships, spaces, systems, document references, duplicate records, source consistency and model alignment.
Required Field Check
Review completion
against supplied
project requirements.
Asset Match Check
Confirm records
relate to
intended equipment
or assets.
Space Check
Review component
location references
against required spaces.
Type Check
Verify required
asset-type
relationships.
System Check
Review project-defined
system relationships.
Duplicate Check
Identify duplicated
or conflicting
information records.
Document Check
Review required
document references
against supplied files.
Model Check
Compare selected
handover data
with the
intended record model.
Information Responsibility
Define Who Supplies, Reviews & Accepts the Data
ROLE 01
Information Requirement
Owner or project
requirements define
the expected
handover information.
ROLE 02
Source Information
Relevant stakeholders
provide required
project
and asset records.
ROLE 03
Data Preparation
Required information
is organized
into the
agreed handover structure.
ROLE 04
Data Review
Required checks
are completed
before formal issue.
ROLE 05
Clarification
Missing
or conflicting information
is routed
to responsible parties.
ROLE 06
Correction
Approved updates
are incorporated
into the
required records.
ROLE 07
Final Validation
Dataset is reviewed
against defined
handover criteria.
ROLE 08
Acceptance
Final acceptance
remains subject
to the
project authority
and contractual process.
Scope & Compliance
COBie Preparation Does Not Automatically Guarantee Contractual Compliance
MEP Global Engineering can support COBie data preparation, BIM-to-data mapping, asset information, data cleanup, validation and structured digital handover.
Final compliance depends on the exact project specification, owner information requirements, contractual requirements, required COBie version, templates, classifications, mandatory fields, validation rules and formal acceptance process.
Missing source data, equipment information, approved product records or stakeholder inputs cannot be reliably replaced by unsupported assumptions.
Project Requirement
Defines what
information must
actually be delivered.
Source Information
Forms the basis
for asset
and handover data.
Validation
Checks the dataset
against agreed
project rules.
Final Acceptance
Remains subject
to the project's
designated
reviewing authority.
COBie & Handover Applications
Structured Facility Information Across Complex Building Types
Data Centers
Structured handover
information
for equipment-intensive
technical facilities.
Healthcare
Asset,
space
and facility information
supporting complex
healthcare environments.
Industrial Facilities
Equipment
and system-focused
handover information
for operational facilities.
Commercial Buildings
Structured
building
and asset information
for owner handover.
Life Sciences
Controlled
asset and
facility information
for technical projects.
Semiconductor & High-Tech
Equipment-rich
structured handover
for high-density
technical facilities.
Education
Facility
and asset records
supporting institutional
building portfolios.
Hospitality
Structured project
and equipment data
supporting hotel
facility handover.
Multifamily
Repeatable
building
and asset
handover structures.
Related Services
Connect COBie to the Full Facility Information Lifecycle
Frequently Asked Questions
COBie & BIM Handover FAQs
What is COBie?
COBie is a structured approach for organizing selected building, space, asset and operational information for project handover and downstream use. The exact required format and data should follow the project's specified requirements.
Can COBie information be prepared from BIM models?
Yes. Suitable BIM information can contribute to COBie or structured handover data, particularly where model objects contain reliable project-defined parameters.
What other sources can be used?
Depending on project requirements, sources can include equipment schedules, asset registers, space schedules, approved submittals, O&M manuals, commissioning records and other closeout information.
Can existing COBie data be cleaned or validated?
Yes. Existing datasets can be reviewed for missing required fields, duplicate records, inconsistent identifiers, relationship issues and other project-defined validation rules.
Can asset data be linked back to BIM objects?
Yes. Where model structure and project identifiers permit, selected handover records can be aligned with corresponding BIM assets.
Does preparing COBie data guarantee compliance?
No. Compliance depends on the actual contract, information requirements, template, data rules, classification requirements, mandatory fields, validation process and final acceptance criteria. The dataset should therefore be reviewed against the specific project requirement.
COBie & Structured BIM Handover
Need to Prepare Asset & Facility Information for Final Handover?
Share your COBie template, owner requirements, BIM models, asset registers, equipment schedules and closeout documentation.