What actually distinguishes a live digital twin from a static as-maintained BIM model, connecting BIM elements to building automation and IoT data, facility management and predictive maintenance use cases, COBie-style handover data, and where BIM-to-twin projects commonly stall.
“Digital twin” is one of the most overused terms in AEC technology, and this module opens by drawing a precise line: a twin is live and data-connected, continuously synchronized with the physical asset's real current state, while even a highly detailed as-built model is a snapshot that silently drifts out of date. From there it covers the actual mechanics of connecting BIM elements to building automation and IoT data through shared identifiers, the facility-management, space-utilization, and predictive-maintenance use cases that live connection unlocks, and the COBie-based handover data every one of those use cases ultimately depends on.
By the end of this module you should be able to explain why BAS-to-BIM ID mapping is the most common technical bottleneck standing between an as-built model and a working twin, and why assigning ongoing ownership of a twin's live connections matters just as much as building the connection in the first place.