Your own digital twin.
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 digital twin actually 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.
The model as a way in
Most operational questions start spatially. Which air handling unit serves this wing? What is above this ceiling? Which assets are affected if this riser is isolated?
Those are questions a drawing answers slowly and a navigable model answers immediately. Connecting model objects to your asset identifiers turns the model into the index for everything else you hold.
Design data and as-built reality
Handover models describe the design intent. Point clouds describe what was actually built, and what has changed since. Holding both in one view is what makes the twin useful after year one, rather than an artefact of the handover.
Growing into it
The common failure is trying to specify the complete twin before delivering anything. Starting from a working viewer with real model data lets you put something in front of operators early and extend it where it earns its place — which is also how you find out which integrations actually matter.
