→Sign in
Explore
  • Roles
  • Profiles
  • Flows
  • Jurisdictions
Tools
  • Analysers
  • Transform My Role
  • Compare
  • Transformations
  • Matrices
Reference
  • Library
  • Framework
  • Glossary
  • Help
  • About
Creative Commons
BIMe Initiative by:CHANGE AGENTS AEC
Contact UsSubscribePrivacyTermsHome
Roles, Profiles & Flows
RolesProfilesFlowsAnalysersTransformCompareJurisdictionsLibraryHelpAbout
  1. Home
  2. /
  3. Flows
  4. /
  5. ●Appointing-party information delivery planning — ISO 19650-2
Published

    Ask about recognition

    Find credentials that map to this object, or draft a template.

    Preview

    Inline assistance — chips pre-fill a question for the recognition agent. The free-form chat backend lands in a later milestone.

    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
    Project journey · PW-D-TC6V7H3F

    Appointing-party information delivery planning — ISO 19650-2

    A Project Manager acting for the appointing party plans and assures information delivery across appointments under ISO 19650-2: establishing the project's information needs, building procurement around them, coordinating delivery plans across lead appointed parties, holding the milestone acceptance cadence, and closing out into the asset phase.·Linked profile: BIM Fundamentals Profile·Journey for Project Manager

    Authored
    Stages
    5
    Materials
    3
    Gaps
    0

    Five-stage navigational layer for the client-side view of ISO 19650-2 — the appointing party's information duties across the whole appointment structure, complementing the delivery-team flow.

    Trust

    Not yet verified

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

    Project context:
    Client-side companion to the delivery-team ISO 19650-2 flow; clause references follow ISO 19650-2:2018 numbering.
    Stage 1 · Establish the project's information needsStage 2 · Procurement around informationStage 3 · Coordinate delivery plans across appointmentsStage 4 · Milestone assurance & acceptanceStage 5 · Close-out into the asset phase
    1. 01

      Establish the project's information needs

      ●IM responsibility · Appointing Party — project manager as information sponsor

      Fix what the project must know at each decision point, and write it down as project information requirements.

      Embedded guidance

      Client decisions, not models, drive information requirements.

      • Tie each information requirement to a decision the client must make (§5.1)
      • Set the project information standard and production methods once, for all appointments
      • Procure reference information (surveys, existing-asset data) before appointing designers

      Linked ecosystem materials (1)

      Standards & clauses (primary)
      • ISO 19650·Clause
        ISO 19650-2 §5.1.4
        Establish project information requirements
        §5.1.4 — establishing project information requirements
    2. 02

      Procurement around information

      ●IM responsibility · Appointing Party — procurement lead

      Build invitations to tender that let bidders price information management honestly.

      Embedded guidance

      What tenders omit, variations supply — expensively.

      • Issue exchange information requirements with every invitation (§5.2)
      • Require pre-appointment BEPs and judge them on capability evidence
      • Keep requirement language testable: a bidder should know what acceptance means

      Linked ecosystem materials (1)

      Standards & clauses (primary)
      • ISO 19650·Clause
        ISO 19650-2 §5.2.1
        Tender response — pre-appointment BEP
        §5.2.1 — tender response and pre-appointment BEP
    3. 03

      Coordinate delivery plans across appointments

      ●IM responsibility · Appointing Party — across lead appointed parties

      Align each lead appointed party's MIDP so cross-appointment dependencies surface before they bite.

      Embedded guidance

      Each appointment plans its own delivery; only the appointing party sees the whole.

      • Review MIDPs together: sequencing, shared dependencies, common milestones (§5.4)
      • Make inter-appointment information dependencies explicit and owned
      • Synchronise milestone calendars before mobilisation completes

      Linked ecosystem materials (1)

      Standards & clauses (primary)
      • ISO 19650·Clause
        ISO 19650-2 §5.4.1
        Mobilisation — TIDP/MIDP
        §5.4.1 — TIDP/MIDP structure the client reviews
    4. 04

      Milestone assurance & acceptance

      ●IM responsibility · Appointing Party — acceptance authority

      Run the acceptance cadence: review delivered information against requirements at every exchange.

      Embedded guidance

      Acceptance discipline early sets the cost of quality for the whole project.

      • Review against the exchange information requirements, clause by clause (§5.7)
      • Reject precisely — name the requirement, not the feeling
      • Track acceptance metrics per appointment as a leading indicator
    5. 05

      Close-out into the asset phase

      ●IM responsibility · Appointing Party — asset information transition

      Carry accepted project information into the asset information model and the operating organisation.

      Embedded guidance

      The project ends; the information does not.

      • Map accepted deliverables to asset information requirements (ISO 19650-3 handshake)
      • Archive the project information record with provenance intact (§5.8)
      • Debrief appointments on information performance, not just programme