openBIM Information Lifecycle
This simple example follows a single pump to show how OpenBIM allows information to be used throughout the lifecycle of an asset.
01 - Owner Requirements
The process begins with a question: What information will the owner need to operate and maintain the asset?
Asset: Stormwater Pump
| Required Information | Requirement | Purpose |
|---|---|---|
| Asset ID | Required | Identify the physical asset |
| Manufacturer | Required | Maintenance and replacement |
| Model | Required | Identify equipment specification |
| Capacity | Required | Operational information |
| Serial Number | Required | Asset identification |
| Maintenance Interval | Required | Planned maintenance |
What is happening?
The owner is simply defining the information they need. These requirements can subsequently be translated into structured, machine-readable information requirements.
02 - Information Delivery Specification
The information requirements are expressed as an Information Delivery Specification (IDS).
<ids:specification name="Pump Requirements">
<ids:entity name="IfcPump"/>
<ids:property
name="AssetID"
required="true"/>
<ids:property
name="Manufacturer"
required="true"/>
<ids:property
name="Model"
required="true"/>
<ids:property
name="Capacity"
required="true"/>
<ids:property
name="SerialNumber"
required="true"/>
</ids:specification>
Every pump must have an Asset ID.
AssetID must exist.
What has changed?
The requirement has become a machine-readable specification useful for automated checking.
03 - IFC Model
The designer creates the pump using their preferred design software and exports an IFC model. The IFC contains both the object and information about that object.
#101=IFCPUMP(
'3kPUMP001',
$,
'Stormwater Pump P-001',
$,
$,
...
);
#201=IFCPROPERTYSINGLEVALUE(
'AssetID',
$,
IFCLABEL('P-001'),
$);
#202=IFCPROPERTYSINGLEVALUE(
'Manufacturer',
$,
IFCLABEL('Grundfos'),
$);
#203=IFCPROPERTYSINGLEVALUE(
'Model',
$,
IFCLABEL('CR 64-2'),
$);
#204=IFCPROPERTYSINGLEVALUE(
'Capacity',
$,
IFCLABEL('20 L/s'),
$);
SerialNumber required by the IDS has not been supplied.
04 - IDS Validation
The IFC can now be checked against the information requirements defined by the IDS.
IDS Requirements
Validation Result
The IFC does not contain the required SerialNumber.
Corrected IFC
#205=IFCPROPERTYSINGLEVALUE(
'SerialNumber',
$,
IFCLABEL('SN-458721'),
$);
The designer has added the missing information.
05 - BCF Issue Management
If validation identifies missing or incorrect information, the issue can be communicated using BCF.
Missing Serial Number
| Element | P-001 |
| IFC GUID | 3kPUMP001 |
| Issue | SerialNumber required by IDS |
| Assigned To | Mechanical Engineer |
The IFC has been updated and the information requirement has been satisfied.
06 - Common Data Environment (CDE)
Once checked, information can be managed through a CDE that is accessible to all the project contributors.
Mechanical
Why this matters
This prevents project information being locked into proprietary authoring applications.
07 - Digital Handover
The information required for operation and maintenance is assembled into an appropriate handover dataset.
Project Information
- IFC model
- Commissioning information
- Product information
- O&M documentation
- Warranty information
Operational Information
- Asset ID
- Manufacturer
- Model
- Serial Number
- Location
- Maintenance information
08 - Facility Management
The information can now be used by the facilities team to operate and maintain the asset.
P-001
Associated Information
From Requirement to Asset
Information requirements have now travelled through the project to the operational phase.