BIM capability
Asset data structuring, classification governance and handover packages that prepare BIM information for facility management and operational technology integration — distinct from as-built record models.
Digital twin readiness prepares BIM-derived asset information for integration with facility management systems, building automation platforms and operational data governance frameworks. This capability structures, validates and packages asset data so operations teams can import, maintain and eventually connect live system data to building assets.
A digital twin is a living operational representation — not a static as-built model. LOD 500 record information provides the spatial and asset foundation, but twin readiness requires additional data architecture: unique asset identifiers, classification codes, maintenance attributes, spatial relationships, system connectivity and data governance protocols that FM and OT teams can sustain post-handover.
SEINZEN prepares the BIM-to-operations data bridge without overclaiming deliverable scope. The handover package provides structured, validated asset information ready for FM import and future sensor or BMS integration — the operational twin itself is established by the asset owner through their technology and governance investments.
Readiness means the asset register is complete, classified, validated and importable. The operational digital twin emerges when the asset owner connects live data streams, maintenance workflows and performance analytics to that register. BIM delivery provides the foundation; twin operation is an owner responsibility.
Asset owners increasingly specify asset information requirements in employer information requirements and asset information requirements documents. Without structured readiness planning, handover produces geometrically accurate models with incomplete asset data that FM teams cannot import without costly manual reconciliation.
MEP systems are the primary twin candidates — HVAC plant, electrical distribution, pumps, valves and controls carry maintenance data, warranty information and system relationships that operations teams need from day one of building occupation.
Readiness planning begins at project outset, not at handover. Shared parameters, classification codes and asset tagging conventions are defined in the BIM execution plan and populated during production modelling so that handover is an export and validation exercise, not a data creation exercise.
Analysis of AIR and EIR handover specifications for MEP asset scope.
Unique identifier convention aligned to owner FM system requirements.
Uniclass, OmniClass or custom codes applied consistently across all assets.
Warranty, spare parts, maintenance intervals and manufacturer data in model parameters.
Asset-to-space, asset-to-system and asset-to-asset relationships documented.
Structured asset data in format specified by asset owner.
Test import to client CMMS confirming field mapping and data integrity.
Field population verification against AIR requirements before handover.
Model, asset data, classification tables and validation reports combined.
Owner FM team orientation on data structure, update protocols and limitations.
Control point identifiers cross-referenced to asset tags where specified.
Assessment of BIM data versus twin integration requirements with owner technology team.
Analyse asset owner requirements at project outset defining data scope.
Define tagging, classification, parameters and relationships in BEP.
Populate asset parameters during modelling, not at handover.
Verify asset data population rates at construction issue and commissioning.
Confirm installed assets match model with field-verified serial numbers and locations.
Generate COBie or custom schema deliverable per AIR specification.
Test import to client CMMS identifying and resolving mapping issues.
Issue validated asset data package with governance briefing to owner team.
Every maintainable asset has a unique identifier with no duplicates across disciplines.
All assets carry agreed classification code per AIR specification.
Required warranty, spare part and maintenance fields populated per AIR field list.
Asset space assignment matches field-verified installed location.
Critical system connections documented — fed-from, serves, controls.
Deliverable format and fields match AIR specification without omission.
Successful import to client CMMS without manual data correction.
As-built record information without digital twin equivalence claims.
Asset tags consistent across Revit, COBie, IFC and BMS point schedules.
Owner briefing materials covering update protocols and data limitations.
Documented gaps between delivered data and full twin integration requirements.
Test results and commissioning records linked to asset identifiers where specified.
Major plant equipment
Maintainable MEP assets
Commissioned equipment
Full asset data package
| Milestone | Element | Purpose | Responsible | Geometric | Alphanumeric | Documentation | LOD / LOIN | Control | Acceptance |
|---|---|---|---|---|---|---|---|---|---|
| Design development | Major plant equipment | Establish asset tagging convention | MEP BIM author | Equipment location and size | Provisional asset tag, classification code | Equipment schedule with tags | LOIN 3 — asset identification | Tag convention audit | Tag convention approved by owner |
| Construction issue | Maintainable MEP assets | FM-ready asset register foundation | MEP BIM coordinator | LOD 350+ equipment and valves | Asset tag, type, classification, location | Asset register draft | LOIN 4 — asset data | Completeness audit | Construction issue asset data gate |
| Commissioning | Commissioned equipment | Verified operational asset data | MEP BIM lead | Field-verified position | Serial number, commissioning date, test results | Commissioning-linked asset records | LOIN 5 — record information | Site verification comparison | Commissioning data linked to assets |
| Handover | Full asset data package | FM import and twin readiness | BIM manager | As-built model geometry | Full AIR field set per asset | COBie or custom schema deliverable | AIR / LOIN 5 requirements | FM import test | Owner handover acceptance |
Asset readiness connects MEP engineering data to operations — equipment schedules, valve lists and panel schedules become the authoritative source for asset register population. Engineering parameters such as capacity, rating and design duty inform maintenance planning attributes in the handover dataset.
BMS and controls contractors contribute point schedules that must cross-reference BIM asset tags for future OT integration. Readiness planning defines this cross-reference convention at project outset.
Spatial relationships between assets — which AHU serves which zones, which panel feeds which equipment — are modelled as system assignments and documented as relationship tables for FM system import. These relationships are essential for fault diagnosis and maintenance routing in operational systems.
ISO 19650-3
ISO 19650-4
COBie
ISO 16739
ISO 12006-2
Uniclass 2015
ISO 55000
Client AIR
AIA LOD Specification
| Standard / Reference | Full title | Organization | Application area | Relevance | Edition status |
|---|---|---|---|---|---|
| ISO 19650-3 | Organization and digitization of information about buildings and civil engineering works — Part 3: Operational phase | ISO | Operational information | Asset information requirements and operational phase management. | Published — confirm edition at project start |
| ISO 19650-4 | Organization and digitization of information about buildings and civil engineering works — Part 4: Information exchange | ISO | Information exchange | Exchange protocols for operational information delivery. | Published — confirm edition at project start |
| COBie | Construction Operations Building Information Exchange | buildingSMART / NIBS | Asset handover | Structured asset data format for FM import. | Published — confirm edition at project start |
| ISO 16739 | Industry Foundation Classes (IFC) for data sharing | ISO | Asset geometry exchange | Spatial asset data in open format for FM and twin platforms. | Published — confirm edition at project start |
| ISO 12006-2 | Building construction — Organization of information about construction works — Part 2: Framework for classification | ISO | Asset classification | Classification framework for asset categorisation. | Published — confirm edition at project start |
| Uniclass 2015 | Unified Classification for the Construction Industry | NBS | Asset classification | Classification codes for asset register population. | Published — confirm edition at project start |
| ISO 55000 | Asset management — Overview, principles and terminology | ISO | Asset management | Asset management framework for handover data governance. | Published — confirm edition at project start |
| Client AIR | Asset Information Requirements | Project-specific | Operational specification | Primary reference for handover asset data requirements. | Project issue — confirm at appointment |
| AIA LOD Specification | Level of Development Specification | AIA | Record information | LOD 500 as-built scope — not digital twin equivalence. | Published edition — confirm at project start |
Applicable standards depend on the project jurisdiction, information requirements, contract documents, delivery method and authority requirements. The adopted editions shall be confirmed at project commencement.
Unique identifier protocol aligned to owner FM system.
Structured inventory of maintainable MEP assets with attributes.
Asset-to-classification code mapping per AIR specification.
Formatted asset data for FM import per AIR requirements.
Asset connectivity — fed-from, serves, controls relationships.
Field population rates against AIR requirements.
Evidence of successful CMMS import with field mapping confirmation.
Field-verified model with populated asset parameters.
Combined model, asset data, reports and governance briefing materials.
Documented scope between delivered data and full twin integration.
Automated check confirming no duplicate identifiers across model.
All assets carry required classification code before handover.
Required fields verified against AIR specification field list.
Installed assets matched to model with serial number confirmation.
Handover blocked until successful CMMS import test completed.
Tags consistent across Revit, COBie, IFC and BMS schedules.
Deliverable scope confirmed as record information, not twin operation.
Gaps between delivered data and twin integration documented for owner.
Owner FM team briefed on data structure and update protocols.
Owner formal acceptance of asset data package.
AIR-required fields populated across all maintainable assets.
>= 98%
Assets with assigned classification code.
100%
CMMS import without manual data correction.
First-pass success
Duplicate asset identifiers in model.
Zero duplicates
Modelled assets matching field-verified installation.
>= 99%
No. LOD 500 represents as-built record information verified against field conditions. A digital twin is a live operational system connecting physical assets to real-time data streams, maintenance workflows and analytics — requiring owner technology investment beyond BIM handover.
Structured, validated asset data ready for FM system import and future operational technology integration. The readiness package provides the data foundation; the operational twin is established by the asset owner.
At project outset. Asset tagging conventions, classification codes and parameter definitions are established in the BIM execution plan and populated during production modelling, not created at handover.
COBie is common but not universal. Asset information requirements define the required format — COBie, custom schema or IFC with embedded properties. Readiness means meeting the owner's specified format.
The asset owner establishes and operates the digital twin through their FM, BMS and OT investments. BIM delivery provides the asset data foundation and readiness package.
Cross-reference conventions are defined in the BEP. BMS point identifiers map to BIM asset tags enabling future integration between the asset register and building automation systems.
Let's plan the BIM scope, information requirements, delivery standards and coordination process in line with your project lifecycle.