This video explains what Asset Information Requirements (AIR) are and why they matter in ISO 19650. The written guide below covers how the AIR defines the information needed to manage, operate, and maintain assets throughout their lifecycle, why different organisations need different asset data, and how standardised templates and structured scope data make AIR management practical and repeatable.
Why asset information requirements shape long-term value
A project does not end when the building is handed over. For the organisation that owns and operates the asset, that is when the real work begins. Every pump, HVAC system, security camera, lighting fixture, and piece of specialist equipment needs to be maintained, monitored, and eventually replaced. The Asset Information Requirements define what information is needed to do that effectively. Without a clear AIR, teams end up hunting through dozens of disconnected spreadsheets to find maintenance records, tracking asset performance through complex manual processes, and relying on individual knowledge rather than structured, accessible data. The result is lost information, reactive maintenance, and higher costs over the asset’s lifecycle.
Like the OIR, the AIR varies based on the type of organisation and the nature of the assets being managed. A zookeeper’s AIR might focus on habitat condition monitoring, enclosure maintenance schedules, humidity and temperature tracking, and feeding equipment records, all essential for ensuring animal welfare and visitor safety. A casino operator’s AIR would look completely different, prioritising security system performance, surveillance equipment uptime, slot machine tracking, and regulatory compliance data. Both need structured asset data, but the content, priorities, and exchange points are shaped by fundamentally different operational needs. The key is that the AIR is not a generic template applied to every project. It is a tailored set of requirements that reflects what the organisation actually needs to manage its specific assets.
The AIR must also align with the Organizational Information Requirements (OIR). If the organisation prioritises sustainability, the AIR should include information that tracks energy consumption, waste management, and equipment lifecycle data. If cost savings are the priority, the AIR should capture maintenance costs, asset depreciation, and operational expenses. This alignment ensures that asset management is not just efficient in isolation but is strategically connected to the organisation’s long-term goals. The AIR feeds directly into the Exchange Information Requirements (EIR), which define when and how asset-related information will be delivered during the project, at checkpoints like inspections, reviews, and handover.
How to create and manage asset information requirements
- Identify the key assets and their information needs – Map out the assets that need to be managed throughout the lifecycle, from major systems like HVAC and electrical to individual components like pumps, sensors, and safety equipment.
- Align the AIR with organisational goals – Connect each asset information requirement back to the OIR to ensure asset data supports the organisation’s strategic priorities, whether that is sustainability, cost reduction, safety, or regulatory compliance.
- Standardise across similar assets – Create standardised templates for common asset types so that maintenance schedules, performance metrics, and operational data are captured consistently without reinventing the structure for each asset.
- Define information exchange points – Specify when asset information must be delivered, such as at handover, during inspections, or at major performance reviews, and in what format, aligning with your exchange information requirements.
- Structure assets in the scope module – Define each asset as a structured item in the scope module with its own detailed breakdown of requirements, responsibilities, and tracking data so that everything is organised and accountable.
- Use document templates for the AIR – Start from the AIR template to capture maintenance schedules, performance metrics, and operational requirements without starting from scratch on every project.
- Connect to COBie and handover workflows – Ensure that the structured asset data feeds into COBie and handover packages so that the operations team receives useful, structured information rather than a patchwork of disconnected files.
What you’ll learn
- What an AIR is – How Asset Information Requirements define the data needed to manage, operate, maintain, and monitor assets across their full lifecycle.
- Why every organisation’s AIR is different – How a zoo, casino, hospital, or school each need fundamentally different asset data based on their operational priorities and regulatory environment.
- Alignment with the OIR – How connecting the AIR to organisational goals ensures that asset management supports long-term strategy rather than existing as an isolated data collection exercise.
- Standardising for efficiency – How using consistent templates and structures across similar asset types eliminates duplication and ensures reliable, repeatable data capture.
- Structured scope data – How defining assets in the scope module creates accountability, clarity, and a traceable connection from every asset to its information requirements and responsible parties.
Common questions
What is the difference between the AIR and the OIR?
The OIR defines the high-level strategic information the organisation needs to make decisions across its entire portfolio. The AIR narrows that focus to specific assets, defining what data is needed to manage, maintain, and operate each one throughout its lifecycle. The OIR sets the direction, and the AIR translates that into detailed requirements for individual asset types. For example, an OIR might state that sustainability data is a priority, while the AIR specifies that every HVAC unit must have energy consumption tracking and lifecycle replacement data.
Can the same AIR template be used for different asset types?
A standardised template can be used as a starting point for similar asset types, like applying the same structure to all HVAC systems across multiple buildings. However, different asset categories will need different templates. A security camera has different information needs than a mechanical pump. The goal is to standardise where possible to avoid duplication, while tailoring where the asset type demands it.
When should asset information be exchanged during a project?
Information exchange points should be defined as part of the EIR and aligned with key project milestones. Common exchange points include design stage reviews, pre-construction checks, commissioning, handover, and post-occupancy inspections. At each point, specific asset data should be delivered in the agreed format so that the receiving party can verify it meets the requirements before the project progresses further.
How does the AIR connect to the asset information model?
The AIR specifies what information must be included in the asset information model, which is the collection of verified data about the built asset that supports long-term operation. During the project, verified model data and documentation feed into this model. At handover, the asset information model should contain everything defined in the AIR, providing the operations team with a complete, structured dataset for every asset they need to manage.
Explore further
- AIR: Asset Information Requirements – The full expert course lesson with detailed walkthroughs and practical examples.
- EIR, PIR, and BEP documents with Plannerly – How the complete set of information requirement documents connects and can be managed from templates.
- ISO 19650 concepts and workflows – The full help centre collection covering how each component of ISO 19650 works together.
- ISO 19650 templates localised – How ready-made templates in multiple languages help teams get started with AIR, OIR, PIR, and EIR creation.