Most digital twins die quietly at handover, when the model's asset data turns out too incomplete, inconsistent or poorly structured to actually operate the facility from. An ISO 19650-aligned information-delivery plan, set at project outset rather than assembled retrospectively, is what stops this from happening on Australian projects.
Asset Information Requirements: Defining the Target Before Design Starts
Asset Information Requirements (AIR), a core ISO 19650 concept, define exactly what data the asset owner needs at handover to operate and maintain the facility — specific attributes required per asset type, required classification systems, and data formats. Setting this at project outset means the design and construction teams know precisely what handover data quality bar they're delivering to throughout the project, rather than the far more common and costly alternative: discovering the data gap during handover, when there's no remaining budget or programme time to fix it properly.
COBie vs Bespoke Schemas
- COBie (Construction Operations Building Information Exchange) is a widely recognised, standardised schema that many Australian facilities management software platforms already support out of the box.
- This makes COBie a sensible default choice unless the specific asset owner's operational systems have particular integration requirements that genuinely justify a bespoke schema.
- Bespoke schemas add cost at delivery and reduce interoperability with future software changes, since a proprietary format locks the asset owner into whatever tooling was built to read it.
Design takeaway: Set Asset Information Requirements before design begins, choose COBie unless there's a genuine reason not to, and validate ELV asset data against the physical installation before practical completion — catching gaps before handover is dramatically cheaper than discovering them once operations staff are already relying on the data.
Validating ELV Asset Data Before Practical Completion
A formal data validation step — sampling asset records against the physical installation and against the Asset Information Requirements — should occur before practical completion, not assumed correct because the 3D model looks visually complete. ELV asset data is particularly prone to gaps because ELV systems are often modelled and documented by multiple subcontractors with inconsistent naming and attribute conventions, making this validation step especially important for exactly the systems (security, comms, controls) that a digital twin most needs reliable live data from.
Frequently Asked Questions
What are Asset Information Requirements under ISO 19650?
Asset Information Requirements (AIR) define exactly what data the asset owner needs at handover to operate and maintain the facility — specific attributes per asset type, required classification systems, and data formats — set at project outset so the design and construction teams know precisely what handover data quality bar they're delivering to, rather than discovering the gap during handover.
Should Australian projects use COBie or a bespoke asset data schema?
COBie (Construction Operations Building Information Exchange) is a widely recognised, standardised schema that many Australian software platforms already support, making it a sensible default unless the specific asset owner's operational systems have particular integration requirements that justify a bespoke schema — bespoke schemas add cost and reduce interoperability with future software changes.
How should ELV asset data be validated before practical completion?
A formal data validation step — sampling asset records against the physical installation and against the Asset Information Requirements — should occur before practical completion, not assumed to be correct because the model looks complete. Catching missing or incorrect asset attributes before handover is dramatically cheaper than discovering the gap once the operations team is already relying on the data.