Pillar 2
Digital Twin Studio
A premium tier for the most critical assets that justify a deep, sensor-bound 3D model.
What it is
Fuse LiDAR, photography, BIM/IFC, and live IoT sensor feeds into a living, editable 3D replica of any physical asset. Edit geometry, run simulations, generate work orders, and watch the twin update in real time.
Pillar 2 is for the assets where a periodic survey isn't enough: pumping stations, viaducts, processing plants, listed buildings. Twins fuse design intent (BIM/IFC), as-built reality (LiDAR / photogrammetry) and live state (IoT / SCADA) into one editable model, with work orders dispatched against twin elements.
Capabilities
BIM / IFC import and versioning
AvailableImport IFC models, browse the element tree, and track versions across uploads.
Work orders against twin elements
AvailableDispatch jobs against specific twin components and watch their state update as the work completes.
Multi-source 3D fusion
In developmentCombine LiDAR meshes, photogrammetry, and BIM/IFC models in one editable scene.
Live IoT bindings
PlannedBind pressure, flow, load, and environmental sensors directly to twin components.
Simulation
PlannedRun what-if scenarios on the twin: structural load, flood propagation, and asset failure spread.
Sovereign deployment
PlannedRun the twin in your tenancy. Sensor data never leaves your environment.
Who it’s built for
Cross-industry use cases. For sector-specific detail, see the relevant Solutions page.
- Water utility pumping-station engineers
- Twin of the DMA bound to live SCADA, run pressure-setpoint simulations before changes touch live valves, dispatch work orders against twin elements.
- Rail structures and OLE engineers
- Twins of viaducts, major junctions and OLE structures with element-level scoring rolled up from inspection annotations.
- Construction PMs on flagship projects
- Design-vs-built twin on a 4D schedule, surfacing schedule slip and clash before they hit the critical path.
- Heritage and civic estate teams
- Twins of listed buildings and civic halls with environmental, vibration and microclimate monitoring for conservation decisions.
How it works
Import design intent
Bring in the IFC or Revit model. The element tree is browsable; versions are tracked across re-uploads with a defensible audit trail.
Layer as-built reality
Fuse LiDAR meshes and photogrammetry from Pillar 1 surveys into the same scene. Deviations between design and as-built surface as twin annotations.
Bind live sensors
Map IoT and SCADA feeds (OPC-UA, MQTT, Modbus, REST) to twin components. Pressure, flow, load and environmental values stream into the viewer over WebSocket.
Operate and simulate
Edit geometry, run what-if simulations (structural load, flood propagation, pressure setpoints), dispatch work orders against twin elements, watch state update live.
Integrations & data sources
IFC / Revit import
Element tree browsable, versions tracked. Standard ISO 19650 information management workflow.
AvailableLiDAR / photogrammetry from Pillar 1
As-built layers flow into the twin scene with no separate upload step.
In developmentSCADA / IoT historians (OPC-UA, MQTT, Modbus)
Live values bind to twin components and dashboard widgets via WebSocket.
In developmentBentley OpenRail / 3D Repo (IFC / IFD)
Two-way IFC import for shops with existing CDE.
PlannedSimulation engines (structural, hydraulic, fire)
Standard FE / CFD engines drive what-if scenarios from twin geometry.
Planned
Frequently asked
- Do I have to twin every asset?
- No. Pillar 2 is for the most critical assets where the depth of a sensor-bound twin pays off: pumping stations, viaducts, listed buildings, flagship projects. Pillar 0 already handles the rest of your asset base.
- Why a twin, and not just a 3D model?
- A twin fuses design intent (BIM/IFC), as-built reality (LiDAR/photogrammetry), and live state (IoT/SCADA) into one editable scene that you can run work orders against. A static 3D model goes out of date the moment something changes; a twin tracks the asset as it actually is, with the sensor feeds and the maintenance history bound to the components.
- Can the twin run in our tenancy?
- Yes. Sovereign deployment is supported on the ENTERPRISE tier. Sensor data and twin geometry never leave your environment. This is the deployment pattern most regulated industries pick.
- Do I need Pillar 0 and Pillar 1?
- Pillar 2 requires Pillar 0 (twin elements link to features in your asset register). Pillar 1 is recommended but optional. Without it you can still import BIM and bind IoT, but you won't have the as-built survey layer fusing in.
- What does pricing look like?
- Pillar 2 starts at £1,200/month as a flat add-on on top of Pillars 0 and 1. Your whole team gets access — no per-user metering. Contact us for portfolio (multi-twin) and sovereign-deployment pricing.
Industries using Digital Twin Studio
Sector-specific workflows, asset templates, integrations and compliance fit.