Skip to content

A BIM digital twin foundation for asset management

Use the xeoVision framework as the visual and data foundation for a digital twin. Bring BIM models, point clouds and object properties into an asset view, then connect it to the maintenance and operational systems that hold your asset records.

What a working digital twin needs

The phrase covers a lot of ground, but the operational version is narrower than the marketing version: a reliable 3D representation of the asset, object data you can trust, and a connection to the systems that hold the operational record.

xeoVision supplies the first two. The third is an integration against your own systems, and deliberately so, because your maintenance history and asset register should not move into a viewer.

From a BIM object to an asset record

See how an equipment identifier connects model information to the asset register and the work that follows, then download the example data.

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

Download example JSON

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 unitAirport DEMO-AHU-001 Terminal ventilation unit DEMO-WO-101 Matched
Auxiliary water pumpPower station DEMO-PMP-002 Auxiliary services pump DEMO-WO-102 Matched
Estate standby generatorDefense estate Not supplied Not linked Not linked Equipment tag missing
Uninterruptible power supplyData center DEMO-UPS-004 Not linked Not linked Asset record missing

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

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

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 isn’t 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 doesn’t create an asset automatically.

Connect BIM data to ERP, SAP and Power BI

Connect Revit and IFC data to ERP, SAP, Power BI and asset systems. The xeoVision framework combines xeokit Data Engine outputs with application foundations and integration services, so BIM properties can be mapped to ERP, project management and document systems through their APIs and your access policies.

Where BIM data usually stops

The model and the business systems rarely meet. Quantities and asset tags get retyped by hand, and the model goes unused once the asset is in operation.

Open outputs are the mechanism

The xeokit Data Engine writes object data as JSON and geometry as GLB and XKT, formats your systems can read. Connecting BIM to your ERP becomes an ordinary integration you can scope and own.

A connection in practice

Map model object IDs to your asset tags, cost codes or equipment numbers and keep them in step. Typical targets: ERP including SAP, project tools and document systems.

Model objects linked to operational and business recordsBIM models and point clouds are processed by xeokit Data Engine into a browser view and object data as JSON. A scoped integration, built on your APIs and access policies, maps each model object by a shared identifier to the asset register, maintenance, sensors and documents, and to ERP, reporting and project systems. The records stay in the systems that hold them. SOURCE DATA BIM models Design and as-built IFC RVT Point clouds Laser scans of site LAS LAZ Site context Optional GLB OBJ xeokit Data Engine Geometry and object properties IFC RVT/RFA STEP NWD iModel® RVM Outputs JSON GLB XKT Twin viewer xeokit SDK, browser Click an object to see its linked records upload scans optional load INTEGRATION Mapping By shared ID, on your APIs and access policies GUID ↔ asset tag asset register tag ↔ work order maintenance tag ↔ sensor optional GUID ↔ doc ID documents GUID ↔ cost code finance properties → KPIs reporting GUID ↔ task ID project tools JSON ID YOUR SYSTEMS OPERATIONS BUSINESS Asset register Equipment, locations, status Maintenance CMMS, work orders Sensors / IoT Live readings, optional Documents & handover O&M manuals, certificates ERP / SAP Assets, cost codes Reporting Power BI dashboards Project management Work packages, issues Linked by asset ID = object GUID Records stay in your systems. The viewer reads them live.
Design and as-built data become a browser view. Object identifiers and properties, as JSON, link each model object by a shared ID to the asset register, maintenance and documents, and to your ERP, reporting and project systems.

What should your digital twin connect first?

30 minutes, no slides. Bring your scenario and we’ll tell you what fits, and what doesn’t.

  • The asset and the operational questions to answer first
  • The BIM models and point clouds you already hold
  • The asset register, maintenance and business systems to connect
  • The identifiers, ownership and handover checks to agree
Włodzimierz Kurpiński CCO, Creoox AG

A 30-minute discovery call about your project, with no slides.

Discuss your handover workflow

Prefer to write instead? Send us a message.