Please enable JavaScript.

Coggle requires JavaScript to display documents.

📌 Information Management Practitioner Course 19/3/25 - Coggle Diagram

- - - - 🎯 Purpose
        
        Define all information requirements and set up the delivery environment
      - 📦 Key Activities
        
        • Appoint individuals to undertake the information management function
        
        • Establish OIR, AIR, PIR
        
        • Identify assets and foreseeable trigger events
        
        • Set delivery milestones and information protocol
        
        • Define standards, production methods, reference info
        
        • Establish the Common Data Environment (CDE)
        
        • Establish and plan for AIM maintenance
    - - 🎯 Purpose
        
        Communicate information requirements to prospective delivery teams
      - 📦 Key Activities
        
        • Decide type of activity providing information
        
        • Define EIR (Exchange Information Requirements)
        
        • Define evaluation criteria and response format
        
        • Compile reference info & shared resources
        
        • Package the tender documentation
    - - 🎯 Purpose
        
        Delivery team demonstrates capability, approach, and readiness
      - 📦 Key Activities
        
        • Nominate individuals for information management roles
        
        • Submit pre-appointment BEP
        
        • Assess and document task team capability & capacity
        
        • Submit mobilisation plan and risk register
        
        • Compile complete tender response
    - - 🎯 Purpose
        
        Finalise detailed plans and complete all appointments
      - 📦 Key Activities
        
        • Confirm BEP
        
        • Develop detailed responsibility matrix
        
        • Define lead appointed party’s exchange requirements
        
        • Create TIDPs and compile into MIDP
        
        • Complete appointment documentation (all levels)
    - - 🎯 Purpose
        
        Prepare all systems, people, and procedures before production begins
      - 📦 Key Activities
        
        • Mobilise resources and IT infrastructure
        
        • Test production methods and procedures
        
        • Ensure readiness for trigger events (planned/unplanned)
        
        • Confirm team knows what, why, when, and how
    - - 🎯 Purpose
        
        Produce high-quality information coordinated across all teams
      - 📦 Key Activities
        
        • Check access to shared resources and reference info
        
        • Generate information according to agreed standards
        
        • Undertake quality assurance checks
        
        • Review & approve for sharing
        
        • Review and authorize information model for delivery
    - - 🎯 Purpose
        
        Appointing party formally reviews and accepts (or rejects) model
      - 📦 Key Activities
        
        • Submit model to appointing party
        
        • Review for completeness, quality, and contractual compliance
        
        • Accept or reject with clear explanation
    - - 🎯 Purpose
        
        Finalize and archive project data, update or create asset info model
      - 📦 Key Activities
        
        • Archive project information model in CDE
        
        • Aggregate into AIM
        
        • Maintain AIM over asset lifecycle
        
        • Capture lessons learned for future projects
    - - 🔵 Path A – Foreseen (planned maintenance, inspections)
      - 🔴 Path B – Unforeseen (regulation changes, disasters)
      - ⚪ Path C – No delivery team (leasing or third-party assets)
    - - 🟨 Appointed Parties / Task Teams
      - 🟦 Lead Appointed Party / Delivery Team
      - 🟩 Appointing Party
  - - - A requirement is something a receiver needs from a provider
      - Usually formalized in contracts or task orders
      - Central to all appointments and exchanges in the supply chain
    - - 📁 Project Information Model (PIM)
        
        Produced during delivery phase
        
        Used for design, construction, and contributes to AIM
      - 🗂️ Asset Information Model (AIM)
        
        Used in operation & maintenance
        
        Enables asset owner to achieve operational objectives
    - - At any point in internal/external supply chain
      - Always part of an appointment between sender and receiver
    - - 🏢 Organizational Information Requirements (OIR)
        
        Info needed to operate the organization now and in future
      - 🏗️ Asset Information Requirements (AIR)
        
        Info needed to operate and maintain the asset
      - 🛠️ Project Information Requirements (PIR)
        
        Info needed to make decisions during the delivery phase
      - 🤝 Exchange Information Requirements (EIR)
        
        Requirements specific to each appointment
    - - 🧑‍💼 Requirement Owner
        
        Usually the receiver of information
      - 📝 Requirement Description
        
        Clear purpose of the required information
      - 🎯 Level of Information Need
        
        Must be defined across graphical, non-graphical, and documentation
      - ✅ Acceptance Criteria
        
        How the info will be checked before acceptance
      - 📎 Supporting Information
        
        Materials that support information production
      - 📆 Exchange Date
        
        When or how often the information must be exchanged
    - - 📊 Must be "just right" — not too much, not too little
      - 🔍 Defined across:
        
        • Graphical
        
        • Non-graphical
        
        • Documentation
      - 🧱 Apply to asset breakdown:
        
        • Complex → Entity → Element → System → Product
    - - ✍️ Descriptive Method
        
        Written descriptions at each lifecycle stage
      - 📚 Industry Specification Method
        
        Use Level of Definition (UK) or Level of Development (US)
      - 🧱 Asset Definition Method
        
        Most complete method, tailored to each asset
        
        May combine with industry specs as a base
    - - Depends on risk and need for accuracy
      - Higher upfront effort = higher probability of success
  - - - 🧱 Elements of Business
        
        Assets
        
        Stakeholders
        
        Strategies, plans, policies, obligations
      - 📊 Informed Decision-Making
        
        Combine business + asset information
        
        Ensure they are integrated
        
        Define information needs upfront
    - - 💬 Scenario-based Requirements Capture
        
        Simple, human conversations
        
        Put receivers of information first
        
        Written by requirement owners
        
        Use non-technical language
      - 🧠 Stakeholder Roles (not job titles)
        
        "persona" – who needs the info
        
        "need to" – activity or task
        
        "so that" – purpose and value
      - ✅ Benefits of Scenario-Based Requirements
        
        Focus on Receiver
        
        Enable Collaboration
        
        Drive Creative Solutions
        
        Make it Measurable
    - - 🏁 Step 1: Define Performance Outcomes
        
        Use sustainability criteria
        
        Agree outcomes collaboratively
      - 📥 Step 2: Establish Need for Info
        
        🔧 Delivery Phase – exchange info during project
        
        📈 Operation Phase – assess after Years 1, 2, 3
      - 📝 Step 3: Prepare Requirements
        
        Translate outcomes into clear info needs
        
        Use reliable data sources (meters, records, etc.)
    - - 🛡️ Step 1: Identify Sensitive Assets
      - 🧭 Step 2: Establish Security Strategy
      - 🗂️ Step 3: Create Security Management Plan
      - 📃 Step 4: Define Security Requirements
      - 🤝 What if No Agreements Exist?
        
        Draft an Information Sharing Agreement
        
        Used for tenders or third-party sharing
        
        Includes relevant Security Requirements
  - - - 🔺 Key Decision Points
        
        Defined by the appointing party
        
        Varies by project type, size, complexity
        
        Linked to major delivery phase decisions
      - ❓ Questions to be Answered
        
        Answers come from the Project Information Model
        
        Questions should guide information needs
      - 🧠 Asking the Right Questions
        
        Written in plain, non-technical language
        
        Framed as questions, not predefined info
        
        Promotes innovation by delivery teams
      - 🧩 Project Information Model (PIM)
        
        Must align with level of information need
        
        Includes only what is necessary
    - - 📐 Design Intent Model
        
        First key deliverable of the PIM
        
        Built using design information requirements
      - 🏗️ Virtual Construction Model
        
        Second key deliverable
        
        Adds construction information requirements
      - 🧮 Combined Requirements
        
        PIM = Project + Design + Construction info
        
        Tailored for each key decision point
    - - 📋 Definition
        
        Schedule added to each appointment
        
        Specifies what info to produce in the PIM
      - 🔗 Appointment Structures
        
        One to One – One lead, one key point
        
        One to Many – Multiple leads, same point
        
        Many to One – One lead, multiple points
      - 🧭 Cascading Responsibilities
        
        Appointing Party defines initial EIR
        
        Lead Appointed Party defines EIR for their own appointed parties
      - 📂 Example
        
        Lead combines:
        
        Design info + appointing party’s EIRs
        
        Then issues to appointed parties
- - - - Key player in information procurement
      - Can assign responsibilities via Responsibility Assignment Matrix
      - May delegate tasks to third-parties or appointed parties
    - - Pre-Appointment Activities
      - Tender Response Requirements
      - Invitation to Tender
    - - Prepare Project Information Management Documents:
        
        • Project Information Requirements
        
        • Information Delivery Milestones
        
        • Information Standards
        
        • Management & Production Methods and Procedures
        
        • Information Protocol
      - Establish Common Data Environment (CDE)
      - Prepare Reference Information and Shared Resources
    - - Evaluate:
        
        • Delivery team's approach (via BIM Execution Plan)
        
        • Capability and Capacity
        
        • Risk related to information delivery
      - Provide:
        
        • Templates
        
        • Clear structure for responses
    - - Compile:
        
        • Exchange Information Requirements
        
        • Project-specific documents
        
        • Tender response guidance (e.g. templates, page limits)
      - Confirm:
        
        • Reference info and shared resources are ready in CDE
    - - R: Responsible
      - A: Accountable
      - C: Consulted
      - I: Informed
      - Used to define scope and clarify who does what
  - - - Purpose: Inform appointing party's selection
      - Collaborative input from delivery team
      - Depends on project size and complexity
      - Key components:
        
        • Information Management Roles & Responsibilities
        
        • Information Delivery Strategy
        
        • Proposed Federation Strategy
        
        • High-level Responsibility Matrix
        
        • Amendments to Information Standard
        
        • Schedule of Enabling Technologies
        
        • Risk Register
    - - ✔️ Capability = right people, skills, tools
      - ✔️ Capacity = enough people to meet deadlines
      - Three types of assessment:
        
        • Establish what's needed
        
        • Assess each task team
        
        • Summarize delivery team status
      - Outcome:
        
        • Identify shortfalls
        
        • Address in Mobilization Plan
    - - Purpose: Ensure team knows:
        
        • What info to produce
        
        • When and how
        
        • Tools/resources available
      - Mobilization Plan includes:
        
        • Tasks & responsibilities
        
        • Timescales
        
        • Shared resources
    - - Trigger: After appointment is awarded
      - Key activities:
        
        • Confirm BIM Execution Plan
        
        • Detailed Responsibility Matrix
        
        • Exchange Info Requirements
        
        • Task Information Delivery Plans
        
        • Master Information Delivery Plan
    - - Internal and external appointments
      - Multiple appointments may be needed
      - 📄 Lead Appointed Party Appointment includes:
        
        • Exchange Info Requirements
        
        • Information Standard
        
        • BIM Execution Plan
        
        • Master Info Delivery Plan
      - 📄 Appointed Party Appointment:
        
        • Same as above, but:
        
        – Exchange Info Reqs = from Lead
        
        – Task Info Delivery Plan replaces Master
      - Always ensure legal review
  - - - • Specification for how all information is produced
      - • Enables:
        
        – Search & Retrieval
        
        – Use & Re-use
        
        – Spatial Coordination
        
        – Presentational Consistency
      - 📂 Key Codes:
        
        • Container ID
        
        • Status Code
        
        • Revision Code
        
        • Classification Code
        
        • Project-specific codes (e.g. author, date)
      - 📁 Format & Structure:
        
        • Compatible formats (e.g. PDF, IFC)
        
        • Consistent structure for machine interpretation
      - 🧰 Resources:
        
        • Object/style libraries
        
        • Increase productivity + enforce standards
    - - • Method = How the activity is done
      - • Procedure = Tasks to execute the method
      - • Considerations:
        
        – Time, Cost, Pros/Cons, Skills
      - 🧪 Examples:
        
        – Method 1: Printed mark-up (least efficient)
        
        – Method 2: Digital mark-up (2D)
        
        – Method 3: VR model review (3D)
      - 📝 Documenting Procedures:
        
        • Simple list, Swim-lane diagram, or RACI Matrix
    - - • Reusable content:
        
        – Templates, Symbols, 2D/3D Libraries, Colour Tables
      - • Benefits:
        
        – Increase quality, reduce waste, improve speed
      - • Ownership:
        
        – Licensing via Information Protocol
        
        – Ideally owned by appointing party
    - - • Purpose:
        
        – Break down model into manageable units
        
        – Define container breakdown structure
      - • Supports:
        
        – Simultaneous Working
        
        – Information Security
        
        – Efficient Exchange
      - 🧱 Examples:
        
        – Linear assets (roads, tunnels): offset volumes
        
        – Buildings: interlocking spatial volumes
      - ⚙️ Establishing Strategy:
        
        • Done collaboratively
        
        • Should reflect asset breakdown, not just WBS
  - - - Combine all task information delivery plans
      - Create a single schedule of all information deliverables
      - Guide delivery during the appointment
    - - Schedule-based (not tabular like task plans)
      - Uses the waterfall method (sequential flow)
      - Focus: dependencies and production sequence
    - - Defines minimum time to deliver all outputs
      - Longest necessary sequence of dependent tasks
      - ✅ 4 Steps to Identify:
        
        Step 1: List all information deliverables
        
        Step 2: Note delivery milestones and associated outputs
        
        Step 3: Break down deliverables into tasks, add durations
        
        Step 4: Identify task dependencies (what must happen first)
    - - Initial version of Master Plan
      - Must be approved by appointing & lead appointed parties
      - Used to:
        
        • Track progress
        
        • Manage changes in scope/time/resources
        
        • Align task plans if changes occur
- - - - Four production activities:
        
        • First two by Lead Appointed Party
        
        • Last two by Appointing Party
    - - 🔍 Review (Lead Appointed Party)
        
        Review information submitted by Task Teams
        
        Conduct technical and commercial review
        
        Ensure alignment with agreed methods and procedures
        
        Decide to:
        
        • Authorize the model
        
        • Or Reject and request re-submission
      - ✅ Authorize (Lead Appointed Party)
        
        If review passes:
        
        • Authorize information model
        
        • Instruct Task Teams to share for acceptance
        
        If review fails:
        
        • Reject entire model (partial rejection discouraged)
        
        • Instruct updates and resubmission
      - 🔎 Review (Appointing Party)
        
        Review the authorized model from lead appointed party
        
        Follow project’s production methods
        
        Consider technical and contractual compliance
      - 📬 Accept (Appointing Party)
        
        If review successful:
        
        • Accept model into Common Data Environment
        
        If review fails:
        
        • Reject and request changes
        
        Avoid partial acceptance to prevent coordination issues
  - - - Definition: File, database, etc. holding model info
      - Tied to an asset and model component
      - 📑 States
        
        🛠️ WORK IN PROGRESS
        
        Visible/editable by Task Team
        
        Not approved
        
        🔁 SHARED
        
        Read-only, shared with Delivery Team
        
        Approved for specific purpose
        
        📢 PUBLISHED
        
        Read-only, accepted as deliverable
        
        Used by Project/Asset Team
        
        🗄️ ARCHIVED
        
        Superseded version
        
        Read-only for admin, record only
      - 🔄 Transitions
        
        WIP → SHARED
        
        Check, Review, Approve (Task Team)
        
        SHARED → PUBLISHED
        
        Review & Authorize (Lead Appointed Party)
        
        Accept (Appointing Party)
    - - 🆔 Container ID
        
        Unique, never changes
        
        Structured using codes
      - 🔁 Revision
        
        Pxx (Preliminary), Cxx (Contractual)
      - ⚙️ Status
        
        S1, S2... (Shared); A2, A3... (Authorized)
      - 🗂️ Classification
        
        ISO 12006-2 or bespoke standard
      - 🧾 Archive/Journal
        
        Archive = All current & archived states
        
        Journal = Transaction logs (who/what/when)
    - - Not a single system—integrated IT setup
      - May include asset sensors, scanners, finance tools
      - ☁️ Distributed CDE
        
        WIP done locally (e.g. internal network)
        
        Then uploaded to main CDE when approved
      - ⚙️ Functional Requirements
        
        🧩 Container-based
        
        Unique ID, status, revision, classification
        
        🔄 Workflow support
        
        State transitions, trackable changes
        
        🔐 Security
        
        Access control by container & state
        
        🗃️ System Capabilities
        
        Manage model, data, docs
        
        Database & transmittal features
- - - - 🔑 Core Idea
        
        Right Information, Right People, Right Time
      - 📌 Importance of Information
        
        Supports daily life (homes, workplaces, infrastructure)
        
        Asset management efficiency
      - 🏗️ Assets
        
        Definition: Objects adding value
        
        Physical Assets
        
        Virtual Assets (Digital Twin)
      - 💻 Information Models
        (virtual asset)
        
        📐 Graphical Models
        
        Usually 3D
        
        Federation (linking graphical models)
        
        📋 asset Data
        
        Asset attributes: size, cost, performance, materials, weight, ID, location. ویژگی ، مشخصه
        
        📚 Documentation
        
        Reports, Drawings, Photos
        
        Historical and regulatory records
        
        Often outdated; requires updates
    - - 🔑 Core Principle
        
        Right people, Right information, Right time
        
        Receiver == information requirements ==> Provider
        Provider == information model ==> Receiver
      - 📍 Why information exchanged?
        
        Receivers require information at all stages of asset’s life
        
        Receivers ensure correct information produced
        
        e.g. Legal, Business, Asset, Project, and Register Questions.
      - 🕒 When information exchanged?
        
        Agreed collaboratively by receivers and providers
      - ⚙️ How information exchanged?
        
        Decide method early and collaboratively
        
        Information fits intended purpose
        
        e.g. now or future use, format, structure, naming, history, which part of information
      - 📑 What information exchanged?
        
        once establishing why, when, and how can collaboratively be exchanged.تبادل
    - - 🔗 Collaborative Approach
        
        Information production is a process involving:
        
        Generating, Checking, Reviewing/Approving, Reviewing/Accepting
      - 📏 Information Standards
        
        Determined by receiver, asset type, and purpose (rtp)
      - 🛠️ Production Methods
        
        Choose effective methods:
        
        Example: Printed documents (markup with pen)
        
        Example: Digital asset data (comments digitally)
        
        Example: Virtual Reality (comments within models)
      - 📖 Documented Procedures
        
        Define clearly who is: (RACI)
        
        Responsible, Accountable, Consulted, Informed
      - 📂 Shared Repository
        
        Central place for information:
        
        Produced once, used multiple times
        
        Trusted, clear ownership, secure access
  - - - 📈 Global Population Growth
        
        From 7.7B to 9.7B by 2050
        
        $57T infrastructure needed by 2030
        
        Infrastructure near breaking point
      - 🏛️ Built Assets
        
        Should support public services
        
        Driven by citizens’ needs
        
        Often lack the right information
      - 💻 Digitally Built Environment
        
        Centralized information
        
        Continuous feedback & feedforward
      - 🌟 Benefits
        
        Citizens: Better use, better decisions, better outcomes
        
        Organisations: New markets, growth, competitive edge
        
        Nations: Higher economic return, asset value, efficient services
      - 📊 Economic Impact
        
        Reduce rework, extend asset life, optimize services
    - - 🧭 Organisational Management
        
        Defined by ISO 9000
      - 📁 Information Management
        
        Based on ISO 19650 series
        
        Operational info is generated during delivery
        تولید، تبادل و استفاده از اطلاعات در طول چرخه حیات دارایی
      - 🏗️ Asset & Project Management
        
        Uses ISO 55000 (Asset) & ISO 21500 (Project)
      - 📜 ISO 19650 Overview
        
        Part 1: ISO 19650-1 | Concepts and principles
        
        Part 2: ISO 19650-2 | Delivery phase of the assets (national annex included)
        
        Part 3: ISO 19650-3 | Operational phase of the assets (examples, trigger events)
        
        Part 4: ISO 19650-4 | Information exchange (non-proprietary format)
        
        Part 5: ISO 19650-5 | Security-minded approach to information management (risk, vulnerability)
    - - 🧾 Appointments
        
        Receiver–Provider relationships via contract or task order
      - 🧑‍💼 Parties
        
        Appointing Party: Receiver of infor, i.e. Asset owner/client
        
        Appointed Party: Provider of info, i.e. Multiple, internal/external
        
        Lead Appointed Party: Primary provider to receiver(appointing)
      - 🧑‍🤝‍🧑 Teams
        
        Task Team: Executes specific tasks
        
        Delivery Team: Lead party + sub-parties
        
        Asset/Project Team: All involved parties
      - 👤 Roles
        
        No pre-defined roles
        
        Each team should nominate Information Manager
        
        Central contact, represents team, must have authority & capacity
    - - 📊 8 Steps (Grouped into 3 phases)
        
        Steps 1 & 8: Once per lifecycle
        
        Steps 2–7: Repeated for each appointment
      - Steps
        
        🟩 Phase 1: Pre-Appointment
        
        Assessment & Need – Define what, why, and how
        
        Invitation to Tender – Define requirements (PROCUREMENT PHASE)
        
        🟦 Phase 2: Appointment Phase
        
        Tender Response – Teams respond with approach & capacity (PROCUREMENT PHASE)
        
        Appointment – Detailed planning before formal agreement (PLANNING)
        
        Mobilisation – Ensure team knows what/when/how to deliver (PLANNING)
        
        Production – Coordinate, generate, approve information (PRODUCTION)
        
        🟩 Phase 3: Post-Production
        
        Information Model Acceptance – Review, accept/reject (PRODUCTION)
        
        Close Out – Archive & aggregate into AIM
      - ⚠️ Trigger Events
        
        🔵Path A: Foreseen → Can be planned in advance
        e.g. maintenance, inspections
        
        🔴Path B: Unforeseen → Can't be planned in advance
        e.g. natural disasters, changes in regulation, refurbished assets
        
        ⚪ Path C: Unforeseen → Can't be planned in advance & no delivery team need to be appointed
        e.g. acquiring or leasing a new asset
        
        The information management process begins when a trigger event occurs.
      - 🚀 Delivery Start
        
        Used when operational phase parties are unknown
        
        Follows Path B with limited activity in Steps 1 & 8
    - - 🟩 Phase 1: Pre-Appointment
        
        Assessment & Need
        
        Define OIR, AIR, PIR
        
        Appoint Information Manager
        
        Establish CDE & AIM Plan
        
        Define standards, methods, trigger events
        
        Invitation to Tender
        
        Define EIR
        
        Prepare evaluation criteria
        
        Share reference info & tender documents
      - 🟦 Phase 2: Appointment Phase
        
        Tender Response
        
        Submit BEP (pre-appointment)
        
        Nominate IM roles
        
        Provide mobilisation plan & risk register
        
        Appointment
        
        Confirm BEP
        
        Develop Responsibility Matrix
        
        Create TIDP & compile MIDP
        
        Finalize appointment documents
        
        Mobilisation
        
        Mobilise people, systems, IT
        
        Test methods & procedures
        
        Prepare for trigger events
        
        🟨 6. Production of Information
        
        Generate info per standards
        
        QA checks
        
        Approve & authorize information model
      - 🟩 Phase 3: Post-Production
        
        Information Model Acceptance
        
        Submit model for review
        
        Check quality, completeness
        
        Accept or reject with reasons
        
        Close-Out & AIM Aggregation
        
        Archive project info
        
        Update/create AIM
        
        Maintain AIM
        
        Capture lessons learned
      - 🔁 Trigger Event Paths
        
        🔵 Path A: Foreseen (e.g. inspections)
        
        🔴 Path B: Unforeseen (e.g. disasters)
        
        ⚪ Path C: No delivery team
      - 📘 Roles Legend
        
        🟩 Appointing Party
        
        🟦 Lead Appointed Party / Delivery Team
        
        🟨 Appointed Parties / Task Teams
- - - - EIR: Establish the appointing party’s Exchange Information Requirements
      - Response & Evaluation setup: Establish tender response requirements & evaluation criteria
      - Tender packaging: Compile information for Invitation to Tender
    - - Pre-BEP: Establish the (pre-appointment) BIM Execution Plan
      - Team Capability & Capacity: Establish the delivery team’s capability & capacity
      - Mobilization Plan: Establish the proposed delivery team’s mobilization plan
      - Tender Response: Establish the delivery team’s tender response
    - - 🔴Path B: Unforeseen → Can't be planned in advance - Unplanned but with delivery team (is appointed reactively)
        e.g. natural disasters, changes in regulation, new or refurbished asset
  - - - BEP: Confirm delivery team’s BIM Execution Plan
      - TIDP <-> MIDP: Coordinates all Task Information Delivery Plan into one coherent Master Information Delivery Plan
      - Appointment Documents: Complete appointed & lead appointed party’s appointment documents
      - Lead Appointed party's EIR
    - - Mobilize Information Technology
      - Mobilize Resources
      - Test Information Production Methods & Procedures
  - - - Generate Information
      - Complete Quality Assurance Check (Quality Control)
      - Authorize Information Model for Delivery
      - Review Information & Approve for Sharing (Formal approvals)
      - Review Information Model (Formal approvals)
    - - Submit Information Model for Appointing Party Acceptance
      - Review & Accept the Information Model
    - - 🔵Path A: Foreseen → Can be planned in advance
        e.g. maintenance, inspections
    - - ⚪ Path C: Unforeseen → Can't be planned in advance & no delivery team need to be appointed - Unplanned with no delivery
        e.g. acquiring or leasing a new asset
  - - - No → Revise and Resubmit
      - If accepted
        
        Archive project information model
        
        Aggregate into Asset Information Model (AIM)
      - Yes → Path A / Path B / Path C
    - - Review and Continue Maintenance of the AIM
      - Aggregate Information Model into the Asset Information Model (AIM)