What is the AIR?
The AIR (Asset Information Requirements) describes, under ISO 19650-3 (operational phase), which data operations need across the whole life cycle. It derives from the OIR and feeds the Asset Information Model (AIM) — the asset's "digital record". Where the EIR drives a project, the AIR drives the operation afterwards.
What goes in — and why the standards require it
A good AIR asks not just "which attributes" but the context that justifies the data demand. The international operations standards set the frame:
- FM operating model (ISO 41001) — in-house, outsourced or hybrid; which hard/soft FM services the data must support.
- Asset taxonomy & tagging (ISO 14224 / ISO 81346) — how assets are broken down and coded.
- Maintenance strategy per asset class (EN 13306) — preventive, corrective, condition-based or predictive — not one global strategy.
- Criticality per asset (ISO 55001 / 14224) — critical assets drive the required attribute depth.
- Reliability data (ISO 14224) — failure modes, MTBF/MTTR, availability — as an attribute group for critical assets.
- Life-cycle cost (ISO 15686-5) — analysis period, cost categories, residual value, discount rate.
- Trigger events (ISO 19650-3) — which events (maintenance, refurbishment, regulation) update the AIM.
Common mistakes
- One global maintenance strategy for all assets instead of per class.
- Data volume without a criticality logic → expensive, unused attributes.
- No handover/trigger process → the AIM is stale from day one.
- Target system (CAFM/IWMS) undefined → data goes nowhere.
Generate it
In the generator you set data categories, mandatory attributes per asset class and target systems — and anchor the operational context (maintenance, criticality, LCC). The result: a consistent, ISO 19650-3-compliant AIR as DOCX/PDF, derived from the OIR.