BIM that survives handover.
Asset data, live operations and FM-ready models from day one. Built on a clean Asset Information Model, not bolted on after.
When asset data dies at handover, operations rebuilds it from scratch.
Asset data sits in PDFs, spreadsheets and siloed systems. FM teams spend the first year of operations rebuilding what should have been handed over on day one. Maintenance runs on a calendar, not on condition, and the model decays the moment handover ends.
Live data, on a clean foundation
Our digital twin services build a verified Asset Information Model (AIM), then integrate live operational data on top of it. The AIM is the foundation, structured to ISO 19650-3 and COBie so your facilities and operations teams can trust it; the live extension turns it into a working operations system.
AIM foundation
LOD 500 geometry, COBie data and O&M docs linked to model elements.
Your as-built record handed over as a live twin, not a stack of PDFs.
Sensor integration
IoT, BMS and BACnet connected to the model.
Occupancy, HVAC, energy and equipment state.
Live dashboards
Monitoring on the model, not in reports.
Dashboards for FM, energy and maintenance teams.
Predictive maintenance
Equipment faults predicted from live data.
Raised in your CAFM/CMMS before downtime.
A live operations system, working from day one.
Twins we've commissioned
Operational digital twins handed over with asset data structured for facilities management from day one.
DWC Airport
Terminal-scale design packages for Dar Al-Handasah on Dubai World Central's next…
Read the case
Dubai Metro Blue Line
MEP modelled and coordinated across Blue Line stations and depots for MNG Esmas,…
Read the case
Wynn Ras Al Khaima
Over 100 people at peak across MEP, structural and interior fit-out packages on …
Read the case
Stargate Data Centre
Every N+1 and 2N redundancy path verified in 3D against Tier-rating requirements…
Read the case
Zayed National Museum
Mechanical, electrical and plumbing threaded through Foster + Partners' steel-fe…
Read the case
Emaar Golf Hillside Tower
Shop drawing release synced to the tower pour cycle on AFE's fast-track golf-fac…
Read the caseThe digital twin ISO 19650 pack.
A working set we issue with every digital twin engagement: Asset Data Requirements, Sensor & IoT Specification, Integration Checklist and Handover Validation Matrix. Sets up your project for a digital twin from day one, before handover data goes stale.
- Contents
- 20+ documents · Word, Excel & PDF · one zip
- Aligned
- ISO 19650-3 · COBie 2.4 · Uniclass 2015
- Audience
- Developers · Operators · FM Leads · Asset Managers
How digital twin delivery actually runs
-
A UAE PM owns your programme
Onsite, accountable, one name on the contract. Available in your meetings, your time zone, your site walks.
-
A 260-person studio delivers the work
Scaled to your programme, ramped up and down as packages move. You pay for capacity, not for a bench.
-
ISO 19650 is baked in, not bolted on
Author-Checker-Approver on every deliverable. EIR, BEP and CDE governed from project setup through handover.
6 min
From LOD 350 to fabrication-ready
Why "coordinated" models still cause site rework, and the handoff that fixes it.
Read
5 min
The BEP subcontractors actually follow
The difference between a filed document and a working agreement is five sections.
Read
5 min
Clash detection to zero
Zero hard-clash is table stakes. Here is the tolerance standard we hold a federated model to before sign-off.
Read
6 min
QTO as the single source of truth for variations
When quantities come straight from the model, variations stop being arguments and become deltas.
Read
5 min
As-built from day one
Retrofitting an as-built at practical completion is a tax. Updating it weekly is a habit.
ReadCommon questions about digital twins
An as-built model is a static record of what was built. A digital twin adds a live layer on top: sensor and BMS feeds, operational dashboards and maintenance triggers, all bound to a structured Asset Information Model. The as-built captures the geometry once; the twin keeps it current and connects it to how the building actually runs. Existing buildings can be twinned too, starting from a scan-to-BIM record model.
Two kinds. Static asset data at handover: LOD 500 geometry, COBie parameters and O&M documentation linked to each element. And live operational data during use: IoT sensors, building management and BACnet streams for occupancy, HVAC, energy and equipment state. The AIM holds the static base; the feeds keep it live.
The AIM is the operational information model ISO 19650 hands over at the end of delivery, structured against the client's Asset Information Requirements. We build it to the ISO 19650 framework so facilities and operations teams inherit clean, governed data instead of rebuilding it after handover.
Yes. We laser-scan the asset, build a coordinated record model, structure it into an AIM and connect live feeds from there. Most twinning work on operational buildings across Dubai and the wider UAE starts this way, from survey rather than from design.
It depends on asset size, how much of the AIM already exists and how many live systems you connect. A single-asset twin built on an existing model costs far less than a portfolio programme scanned from scratch. Book a discovery call and we'll scope it against your building and your FM requirements.