Explore
  • What is RPF
  • Explore
  • Roles
  • Profiles
  • Flows
  • Library
Tools
  • Tools
  • For organisations
  • What you can do
  • Contact RPF
Reference
  • Help
  • New to RPF
  • Admin quick start
  • Sign in

Content licensed CC BY-NC-SA 4.0

BIMe Initiative by: ChangeAgents AEC

  • Privacy
  • Terms
  • Contact Us
  • bimexcellence.org
Roles, Profiles & Flows
What is RPFExploreToolsFor organisationsHelp
Sign inStart a conversation
  1. Home
  2. /
  3. Flows
  4. /
  5. Information management in operation — ISO 19650-3 (asset phase)
Published

Ask about recognition

Preview questions about recognition and credential templates.

Preview

Select a question to preview its prompt. This preview does not send questions or return credential matches.

Suggested questions

Pick a question above to pre-fill a prompt for the recognition agent.

Chips share only the data shown on this page (object slug, recognising bodies, jurisdiction). No personal data is sent.

Open the recognition help sectionEmail a human reviewer
AcceptedEvidenced

Lifecycle flow · PW-D-TSCNFLQA

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

A Facility Manager operates the asset information lifecycle under ISO 19650-3: framing organisational and asset information requirements, baselining the asset information model, running trigger-event information exchanges with appointed parties, and keeping the AIM authoritative through continual review.·Linked profile: BIM Fundamentals Profile·Role: Facility Manager

Stages
5
Materials
0
Gaps
0
Authored

Five-stage navigational layer mapping the operational-phase information management cycle to ISO 19650-3 concepts: OIR/AIR framing, AIM baseline, trigger events, acceptance against requirements, and continual improvement.

Project context: Anchored to the ISO 19650-3:2020 operational-phase specification; pairs with the delivery-phase flow (ISO 19650-2) at handover.

Trust

Not yet verified

An authored guide. Not yet confirmed by a verification panel.

Activity Flow Diagram
This flow is described by AFD.2001.V0.1
Open the full diagram
  1. 1Select Information Uses
  2. 1.1Select Document Uses
  3. 1.2Select Model Uses
  4. 1.3Select Data Uses
Stage 1 · Frame OIR and AIRStage 2 · Baseline the AIMStage 3 · Run trigger-event exchangesStage 4 · Accept against the AIRStage 5 · Maintain and improve
  1. 1Frame OIR and AIR
  2. 2Baseline the AIM
  3. 3Run trigger-event exchanges
  4. 4Accept against the AIR
  5. 5Maintain and improve
  1. 01

    Frame OIR and AIR

    ●IM responsibility · Appointing Party — asset owner / operator

    Derive organisational and asset information requirements from organisational objectives and the trigger events the asset will face.

    Embedded guidance

    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
  2. 02

    Baseline the AIM

    ●IM responsibility · Appointing Party — information manager (operation)

    Establish the asset information model baseline — inherited delivery information, surveyed state, and the CDE arrangement for operation.

    Embedded guidance

    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
  3. 03

    Run trigger-event exchanges

    ●IM responsibility · Appointing Party with Lead Appointed Party per event

    For each trigger event, appoint and brief the parties who must deliver or consume asset information.

    Embedded guidance

    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
  4. 04

    Accept against the AIR

    ●IM responsibility · Appointing Party — acceptance authority

    Verify and accept delivered information against the asset information requirements before it enters the AIM.

    Embedded guidance

    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
  5. 05

    Maintain and improve

    ●IM responsibility · Appointing Party — continual improvement owner

    Keep the AIM current and feed lessons back into the OIR/AIR set on a review cadence.

    Embedded guidance

    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