Information management in operation — ISO 19650-3 (asset phase)

ISO 19650-3 starts from the organisation, not the building: information requirements descend from organisational objectives.

• List the foreseeable trigger events (maintenance, refit, transfer, incident, compliance reporting)
• Derive AIR per trigger event; keep requirements answerable and measurable
• Name the acceptance criteria alongside each requirement

The AIM is the single referenced source for operational decisions.

• Reconcile handover deliverables (ISO 19650-2 close-out) against the AIR before accepting them into the AIM
• Record provenance and verification state per information container
• Keep the operational CDE states (work-in-progress / shared / published / archived) enforced

Operational appointments are smaller and more frequent than delivery-phase ones — the discipline is the same.

• Issue exchange information requirements scoped to the trigger event
• Agree the (often lightweight) BIM execution plan and delivery timetable
• Hold appointed parties to the agreed information standard and classification

Acceptance is requirement-by-requirement, not file-by-file.

• Validate structure, classification and completeness automatically where possible
• Reject to the delivering party with precise requirement references
• Update the AIM register and notify consuming functions on acceptance

Information requirements age as the organisation and asset change.

• Schedule OIR/AIR reviews against organisational planning cycles
• Archive superseded containers rather than deleting them
• Track which AIR were never consumed — candidates for retirement