Model, shadow or twin?
| Digital representation | Connection to the asset | Typical value |
|---|---|---|
| Static model / record | Updated manually at defined events | Context, visualization, documentation and handover |
| Connected dashboard / digital shadow | Operational data generally flows from asset to digital view | Monitoring, alarms, trends and investigation |
| Digital twin system | Governed synchronization at a defined frequency/fidelity; may support analysis and action | Diagnosis, prediction, optimization and decision support |
Terminology varies between industries. Define the business outcome, represented scope, synchronization, data authority and permitted actions instead of arguing over a label.
High-value built-asset use cases
- Locate and understand maintainable assets
- Monitor energy, indoor environment and systems performance
- Detect abnormal behavior and prioritize investigation
- Support condition-based or predictive maintenance
- Test operational scenarios before acting on the physical asset
- Plan space, occupancy, shutdowns and interventions
- Preserve change history and improve future capital projects
Each use case needs a named user, decision, frequency, confidence threshold and measure of value. “Create a digital twin” is not a testable requirement.
A practical architecture
- Physical asset: systems, spaces, equipment and processes in the real world.
- Identity layer: stable IDs that connect models, sensors, documents, work orders and asset registers.
- Source systems: BIM, GIS, BMS, IoT, CMMS/IWMS, inspections, documents and enterprise data.
- Integration and semantics: mappings, units, classifications, relationships, APIs and quality rules.
- Twin services: state, history, rules, simulation, analytics and access controls.
- User experience: dashboards, spatial views, alerts, workflows, mobile/AR or other interfaces.
- Governance: ownership, cybersecurity, privacy, retention, validation, change and decommissioning.
Where BIM helps—and where it stops
BIM can provide spatial context, asset identity, system relationships, geometry, documentation links and structured handover data. It does not create trustworthy live state by itself. Operational integration needs maintained identifiers, data mappings, system access, synchronization, validation and accountable owners.
Minimum viable twin: one operational decision, one asset/system scope, a small set of reliable data, a clear user workflow and a measurable outcome. Expand only after the first loop works.
Information prerequisites
- Asset register with stable, unique identifiers
- Named data owners and authoritative systems
- Required properties, units and validation rules
- System hierarchy and spatial relationships
- Links to approved documents, work orders and history
- Sensor/telemetry quality, timestamp and frequency definitions
- Change process that keeps physical and digital states aligned
Check model handover readiness ↗
Trust, security and human control
Digital twins combine IT, operational technology and domain information, which creates broader trust and security concerns than a standalone model. Define least-privilege access, data classification, provenance, validation, permitted automated actions, override/rollback, audit records, incident response and decommissioning.
Model predictions should state assumptions and confidence. A live-looking dashboard can still be wrong if sensors drift, mappings break, equipment is replaced or time stamps are misaligned.
A six-step starting roadmap
- Choose one decision with an accountable owner and measurable pain.
- Define the physical scope, user workflow and success metric.
- Audit available BIM, asset, operational and historical data.
- Create stable identity and mapping rules; test a representative sample.
- Build the smallest connected workflow with security and validation.
- Measure adoption and outcome, then scale or stop deliberately.
Questions for a vendor or internal team
- Which specific decisions will the system improve?
- What is synchronized, how often, at what fidelity and from which authority?
- How are asset IDs, model objects, sensors and work orders connected?
- How are data gaps, stale values and failed integrations shown?
- Which standards, APIs and export routes reduce lock-in?
- Who can view, change or act—and how is that audited?
- What ongoing work keeps the twin aligned with the asset?
- How will value, adoption and total lifecycle cost be measured?