The model doesn't stop at handover.
A digital twin is only as good as the asset information underneath it. We build that layer first — verified geometry, structured asset data, and the governance that keeps both true once the building is running.
What a digital twin actually is
A digital twin is a live, data-connected model of a physical asset — kept synchronized with sensors and operational data after construction handover.
The distinction that matters: a BIM model describes what was designed and built. A twin keeps describing the asset as it actually operates — which means it needs a maintained connection to reality, not just a good model on the day of handover.
Where most twin projects fail
They start at the dashboard. A visualization layer goes on top of asset data that was never structured, verified, or assigned an owner — and the twin produces confident-looking answers from unreliable data.
We work in the opposite order. Requirements, then verified as-built information, then structured asset data, then integration. The interface is the last problem, not the first.
What we deliver
Six capabilities that can be scoped together as a full twin programme, or taken individually — most owners start with one or two.
Asset Information Requirements
The specification layer. We define what information the asset must carry, in what structure, and at which handover gates — written to ISO 19650 and to the decisions your operations team actually makes.
As-Built & As-Operated Models
Geometry you can trust. Record models verified against the built condition — and, where the paper record is unreliable, rebuilt from laser scan or photogrammetry with the deviations documented rather than quietly absorbed.
Asset Data & COBie Handover
The part that decides whether the twin is useful. Equipment registers populated, classified and validated against the AIR — so maintenance, warranty and replacement data is queryable instead of buried in O&M PDFs.
Model Federation & Web Viewer
The federated model published where non-modelers can actually reach it — in a browser, no Revit licence, with asset data attached to the objects people click.
Operational Systems Integration
Where the twin stops being a picture. We map model objects to the tags your building already emits — BMS points, IoT sensors, CMMS work orders — so live data lands on the right asset.
Twin Governance & Lifecycle Updates
A twin decays without an owner. We define who updates what, on what trigger, and how a change gets validated — then run that cycle with you until your team can carry it.
A twin inherits whatever discipline produced the model beneath it. That upstream layer is what ConstruBIM has delivered at scale: NAICM Mexico City Airport — the single largest federated BIM model in the world at the time, with ISO 19650-aligned governance and CDE workflows across dozens of disciplines (Autodesk AEC Excellence Award, 2016); Soumaya Museum — 14,808 unique facade panels coordinated from concept geometry through installation; and NEOM, where ConstruBIM led digital delivery, defining governance, BEPs and CDE workflows at programme scale. These were BIM and digital-delivery engagements, not operational twin deployments — the point is that the information management underneath them is the same discipline a twin depends on.
Find your level before you buy a platform
"Digital twin" covers four very different things. Most owners are sold level four and need level one. Here is how we scope it honestly.
Accurate record
A verified as-built model and a structured asset register. Static, but true — and the foundation everything above depends on.
Connected data
Asset information linked to the systems that consume it — CMMS, warranty, O&M — and reachable in a browser by people who don't model.
Live asset
Operational data flowing onto the model: BMS points and sensor streams mapped to the assets they belong to, kept current by a defined update cycle.
Predictive
Analytics and simulation on top of a trusted live dataset — the level that only pays off once the three below it are genuinely in place.
What we need from you
Twin engagements stall for predictable reasons. These are the five things that decide whether yours runs cleanly — worth checking before you scope anything.
A defined asset scope
Which buildings, which systems, which equipment classes. Twin scope creep is expensive because every added class needs its own data definition.
Whatever record information exists
Models, drawings, equipment schedules, O&M manuals — even incomplete. We audit what you have before proposing to recreate it.
Access for verification
Site access where records need checking or scanning. This is the single most common schedule risk on existing assets.
A named data owner
Someone on your side who owns asset information after handover. Without this the twin is accurate exactly once.
Your operational systems
Which BMS, CMMS or IoT platforms the twin must speak to, and who administers them.
The decisions it must support
What you want to be able to ask the twin. Requirements written backwards from real decisions produce far less wasted data capture.
Tell us the asset — get a number.
Our instant quote engine simulates cost, team size and timeline live as you describe the scope. No call required to get a range.
Frequently asked questions
The questions owners — and AI assistants — ask about digital twins.
What is a digital twin in construction?
A digital twin is a live, data-connected model of a physical asset — kept synchronized with sensors and operational data after construction handover. It differs from a BIM model in one decisive way: a BIM model describes what was designed and built, while a twin keeps describing the asset as it actually operates. See the BIM glossary for related terms.
Do I need a digital twin, or just a good as-built model?
Most owners need the as-built and asset data layer first. A twin without reliable underlying information produces confident-looking answers from bad data. ConstruBIM will tell you when an accurate asset information model and COBie handover is the right stopping point for your budget and operating maturity — that is level one and two on the ladder above, and it is where most of the value actually sits.
What does ConstruBIM actually deliver on a digital twin engagement?
Asset information requirements (OIR, AIR, PIR), verified as-built and as-operated models, structured asset registers and COBie handover, a federated model published to a browser-based viewer, integration mapping to BMS, IoT and CMMS systems, and the governance that keeps the model true after handover. Each can be scoped on its own.
What do you need from us to start?
A defined asset scope, whatever record information exists (models, drawings, O&M manuals, equipment schedules), access for verification or laser scanning where records are unreliable, a named owner for asset data on your side, and clarity on which operational systems the twin must speak to.
Which standards does ConstruBIM work to?
ISO 19650 for information management across the asset lifecycle, including OIR, AIR, PIR and EIR definition, CDE workflow states and approval gates, and naming and metadata rules. Asset handover is typically structured as COBie, with IFC for open exchange. See ISO 19650 consulting for the governance side.
Can you work from an existing building with no BIM model?
Yes. Where record information is missing or unreliable, the starting point is reality capture — laser scanning or photogrammetry converted into accurate as-built models, with deviation and verification reporting so you know which parts of the record are trustworthy.
How is a digital twin engagement priced?
Scope drives price: asset count and complexity, the state of existing record information, how much verification or scanning is required, the depth of asset data captured per equipment type, and which operational systems must be integrated. ConstruBIM's quote engine gives a live estimate as you describe the asset.
Who owns the twin and its data?
You do. Deliverables are handed over in open, portable formats — IFC and COBie alongside native files — so the asset information model is not locked to a single vendor platform or to ConstruBIM.