How to Create, Contract, and Manage Asset Information Requirements (AIR)

This guide walks through a complete, structured workflow for creating and managing Asset Information Requirements (AIR) - from strategic intent through to automated COBie handover.

 1. Getting Started 
  • Create new project: “Southbank Business Park” and import the AIR template document
  • Strategic Purpose - Understand Organizational Information Requirements (OIR) goals using the OIR template
  • Identify Maintainable Assets - List key assets linked to operational goals that require servicing, maintenance, or compliance
  • Define Key Information Fields - Clarify why each data field matters (e.g., energy tracking, warranty claims, inspection cycles, serial number, power rating, install date)
Why this matters: Structured AIR workflows unify scope, documentation, and deliverables into a single traceable process. This improves version control and enables smoother handover.
 2. Creating the AIR (in Scope) 
  • Create Assets manually or using templates and bSDD
  • Import CSV Asset Information Requirements
    • Import Asset List
    • Import Information Requirements
    • Set up Custom Information Fields
  • Complete Requirementsusing AI to enrich, standardize, and define validation rules
    • Model-based information
    • Descriptions
    • Checklists
    • Documents
    • Links
  • Export and Import IDS - Generate machine-readable, standardized information requirements to support delivery and verification

 AIR_Asset Information Requirements_Example (Southbank Business Park).xlsx 

 AIR Asset List.csv 

 AIR Information Requirements.csv 

Why this matters: Combining manual input, AI assistance, templates, and standards-based imports builds structured AIRs with greater consistency and alignment to ISO 19650 processes.
 3. AIR as a Contract (with Work Packages) 
  • Assign responsibilities and group into Work Packages
  • Export contract-ready documentation with cover page, contents, and hyperlink navigation
  • Enable digital agreement workflows with e-sign approvals
Why this matters: Turning requirements into contract-ready deliverables improves accountability and sets clear shared expectations.
 4. AIR Quality Tracking + COBie Handover 
  • Upload and manage documents against each information requirement
  • Track conditions of satisfaction using structured checklists
  • Automatically validate models and deliverables against defined AIRs
  • Filter model data and export in COBie format
Why this matters: Connecting requirements, documentation, models, and validation in one environment streamlines reviews and ensures complete, verified handover data.
 5. Recap 
  • A complete and structured AIR workflow
  • Start from Excel, IDS, templates, and AI
  • Create Work Packages and e-signed contracts
  • Manage progress tracking and auto-check models
  • Automate handover data
Why this matters: A structured, repeatable AIR workflow supports better collaboration, clearer expectations, and more reliable project closeout - reducing delays and rework at handover.