Skip to content
Book a call

From a model object
to an asset record.

See how an equipment identifier connects model information to the asset register and the work that follows.

Synthetic, non-confidential data. This page runs an identifier-matching check over four example records. It does not process an IFC file or connect to an operational system. The names, identifiers and work orders are invented for this demonstration.

Explore the mapping ↓Download example JSON
  1. 01 · Model objectTerminal air-handling unit

    Model reference: IFC GlobalId
    Equipment tag: DEMO-AHU-001

  2. 02 · Asset registerTerminal ventilation unit

    Asset ID: DEMO-AHU-001
    Record status: In operation

  3. 03 · Maintenance recordReview filter inspection record

    Work order: DEMO-WO-101
    Linked through the same asset ID

Match what is known.
Flag what needs review.

The check matches EquipmentTag to assetId, then finds work orders with that asset ID. It preserves the model’s ifcGlobalId as a separate reference. No name-based or guessed matches are made.

4 illustrative model objects

2 matched asset records

2 records need review

Computed identifier matches from the downloadable synthetic dataset
Model objectEquipment tagAsset recordWork orderResult
Terminal air-handling unitAirportDEMO-AHU-001Terminal ventilation unitDEMO-WO-101Matched
Auxiliary water pumpPower stationDEMO-PMP-002Auxiliary services pumpDEMO-WO-102Matched
Estate standby generatorDefense estateNot suppliedNot linkedNot linkedEquipment tag missing
Uninterruptible power supplyData centerDEMO-UPS-004Not linkedNot linkedAsset record missing

These counts describe this four-record example only. They are not customer results, a performance benchmark or evidence of production data quality.

Airport · Synthetic record

Terminal air-handling unit

Matched
Model reference · IFC GlobalId
0A1b2C3d4E5f6G7h8I9j0K
Illustrative IFC class
IfcUnitaryEquipment
Equipment tag
DEMO-AHU-001
System / location
Ventilation
Illustrative terminal plant room
Linked asset / responsible team
DEMO-AHU-001
Illustrative facilities team
Linked work order

DEMO-WO-101 · Open
Review filter inspection record

The shared identifier establishes the link in this example. A production workflow still needs agreed property checks, permissions and ownership of changes.

Power station · Synthetic record

Auxiliary water pump

Matched
Model reference · IFC GlobalId
1B2c3D4e5F6g7H8i9J0k1L
Illustrative IFC class
IfcPump
Equipment tag
DEMO-PMP-002
System / location
Auxiliary water
Illustrative services building
Linked asset / responsible team
DEMO-PMP-002
Illustrative commissioning team
Linked work order

DEMO-WO-102 · Planned
Review commissioning documents

The shared identifier establishes the link in this example. A production workflow still needs agreed property checks, permissions and ownership of changes.

Defense estate · Synthetic record

Estate standby generator

Equipment tag missing
Model reference · IFC GlobalId
2C3d4E5f6G7h8I9j0K1l2M
Illustrative IFC class
IfcElectricGenerator
Equipment tag
Not supplied
System / location
Standby power
Illustrative support facility
Linked asset / responsible team
No linked asset record
Linked work order
No linked work order

Agree and supply the equipment tag before linking this model object. Its name alone is not used to assign an asset.

Data center · Synthetic record

Uninterruptible power supply

Asset record missing
Model reference · IFC GlobalId
3D4e5F6g7H8i9J0k1L2m3N
Illustrative IFC class
IfcElectricFlowStorageDevice
Equipment tag
DEMO-UPS-004
System / location
Electrical supply
Illustrative electrical room
Linked asset / responsible team
No linked asset record
Linked work order
No linked work order

Review whether the register needs a new asset or the supplied tag is incorrect. This example does not create an asset automatically.

What makes this useful
in a working solution?

xeoVision combines technology, reusable application components and integration services. Your team defines the information handover; we help connect the model context to the systems where it will be used.

Agree the information contract

Select the identifiers, model properties, ownership and handover checks. Decide how missing, duplicate and changed records are reviewed.

Connect the selected components

Use xeokit SDK for the model context, the selected xeokit Data Engine processors for supported files, and an integration scoped to your asset or maintenance system.

Validate the complete workflow

Test representative files, permissions and operational records. Agree deployment, component terms, support and responsibility for updates before rollout.

The example demonstrates identifier matching only. Model extraction, geometry viewing, automated synchronization, asset creation and work-order updates require a separately implemented and validated workflow.

Discuss your handover workflow →BIM & VDC for critical infrastructure →Explore business integrations →