ISO 19650-2: Delivery Phase of Assets
The most widely adopted part of the ISO 19650 standard specifies the requirements and processes for information management during the design and construction phase. From tendering and BEP to delivery of the Project Information Model (PIM).
Standard Data
About ISO 19650-2
ISO 19650-2 is the most widely adopted and used part of the ISO 19650 series. Published in 2018, it specifies the requirements for information management during the delivery phase of built assets — that is, during the design and construction phase itself.
While ISO 19650-1 establishes principles and concepts, ISO 19650-2 provides the step-by-step operational process. It defines what must happen before contracting (pre-appointment activities) and what must happen after contracting (post-appointment activities), covering the entire duration of a construction project.
The standard introduces fundamental documents for BIM project management: BIM Execution Plan (BEP), Master Information Delivery Plan (MIDP) and Task Information Delivery Plans (TIDP). It also formalizes the information verification and approval process through suitability codes (S1-S4).
ISO 19650-2 applies to any project involving the construction or renovation of a built asset — from residential and commercial buildings to transport infrastructure and utilities.
Pre-Appointment Activities
Steps that take place before contracting the delivery team
Information Needs Assessment
- Client defines Organizational Information Requirements (OIR)
- Derivation of Exchange Information Requirements (EIR) from OIR
- Establishing the procurement strategy and required BIM maturity level
- Identification of applicable standards and necessary technologies
- Setting evaluation criteria for tenderers regarding BIM capability
Output: Preliminary EIR + Procurement Strategy
Tender Preparation
- Including complete EIR in tender documentation
- Specifying BIM Execution Plan (pre-BEP) requirements
- Defining applicable naming convention standards
- Establishing available CDE resources and access protocols
- Specifying accepted BIM software and exchange formats (IFC, etc.)
Output: Tender Documentation + Final EIR
Tender Evaluation
- Evaluation of Pre-BEP submitted by each tenderer
- Verification of proposed team's BIM capability
- Analysis of compliance with EIR requirements
- Evaluation of proposed CDE workflow
- Verification of BIM software and available licenses
Output: Evaluation Report + Team Selection
Post-Appointment Activities
Steps that take place after contracting the delivery team, during the project
Mobilization
Mobilization
- Project team is officially constituted
- Post-contract BEP is finalized and approved
- Master Information Delivery Plan (MIDP) is created
- Task Information Delivery Plan (TIDP) for each team
- CDE is configured with naming convention and folder structure
- Roles and permissions in CDE assigned to all members
Collaborative Production
Collaborative Production
- Iterative cycles of information creation in the WIP area
- Inter-disciplinary coordination and regular clash detection
- Publication to Shared area for inter-team review
- Feedback and resolution of coordination issues
- Model updates according to received observations
- EIR compliance verification at each cycle
Review and Approval
Review & Acceptance
- Author (Task Team) verifies information internally
- Reviewer (Appointed Party) performs technical verification
- Approver (Lead Appointed Party) authorizes publication
- Information transitions from Shared to Published in CDE
- Assignment of the corresponding suitability code (S1-S4)
- Automatic notifications to interested parties
Information Model Delivery
Information Model Delivery
- Compilation of the Project Information Model (PIM)
- Final compliance verification with all EIR requirements
- Formal delivery to Appointing Party
- Transfer of PIM to Asset Information Model (AIM) for operation
- Archiving all information in CDE
- Documenting lessons learned for future projects
Key Documents ISO 19650-2
ISO 19650-2 formalizes the use of several essential documents for project information management. Here is a quick reference table:
| Document | Prepared by | When | Purpose |
|---|---|---|---|
| BEP BIM Execution Plan | Lead Appointed Party | Pre-contract + Post-contract | The central document describing how, when and by whom BIM information will be produced. Contains standards, responsibilities, resources and procedures. Exists in pre and post-contract versions. |
| MIDP Master Information Delivery Plan | Lead Appointed Party | Mobilization | The consolidated plan of all information deliveries for the entire project. Integrates individual TIDPs from each task team into a single coordinated document. |
| TIDP Task Information Delivery Plan | Each Task Team | Mobilization | The individual plan of each task team, detailing what information they will produce, in what format, at what level of detail and according to what schedule. |
| EIR Exchange Information Requirements | Appointing Party | Pre-tender | Defines what information must be delivered, in what format, at what level of detail and at what points throughout the project. Forms the basis for tenderer evaluation. |
| PIM Project Information Model | Entire team | Final delivery | The totality of information produced during the design and construction phase. Includes BIM models, technical documentation and all data needed for construction and operation. |
| AIM Asset Information Model | Appointing Party / FM | Post-completion | The PIM transformed for use in the operational phase. Contains the information needed for asset management throughout its entire useful life. |
BIM Execution Plan
BIM Execution Plan
Pre-contract + Post-contract
Lead Appointed Party
The central document describing how, when and by whom BIM information will be produced. Contains standards, responsibilities, resources and procedures. Exists in pre and post-contract versions.
Master Information Delivery Plan
Master Information Delivery Plan
Mobilization
Lead Appointed Party
The consolidated plan of all information deliveries for the entire project. Integrates individual TIDPs from each task team into a single coordinated document.
Task Information Delivery Plan
Task Information Delivery Plan
Mobilization
Each Task Team
The individual plan of each task team, detailing what information they will produce, in what format, at what level of detail and according to what schedule.
Exchange Information Requirements
Exchange Information Requirements
Pre-tender
Appointing Party
Defines what information must be delivered, in what format, at what level of detail and at what points throughout the project. Forms the basis for tenderer evaluation.
Project Information Model
Project Information Model
Final delivery
Entire team
The totality of information produced during the design and construction phase. Includes BIM models, technical documentation and all data needed for construction and operation.
Asset Information Model
Asset Information Model
Post-completion
Appointing Party / FM
The PIM transformed for use in the operational phase. Contains the information needed for asset management throughout its entire useful life.
Information Acceptance Process
ISO 19650-2 defines a formal information acceptance process with multiple steps and distinct roles. Every piece of information must go through this process before becoming available for use:
Creates information in WIP
The author produces information in the WIP area. Internally verifies quality and compliance with naming convention standards and required level of detail.
Technical review in Shared
Information is published to the Shared area for inter-disciplinary verification. The reviewer checks technical aspects, coordination and EIR compliance.
Authorization for use
The approver formally authorizes the use of information and sets the suitability code. May request revisions or reject non-compliant information.
Automatic publication
Approved information automatically transitions to Published state in CDE. The suitability code is applied, notifications are generated and an audit trail record is created.
Important: If information is rejected (code C) or partially accepted (code B), it returns to the WIP area for the author to rework. The process restarts from the beginning, ensuring the quality of delivered information.
Suitability Codes
ISO 19650-2 defines a set of alphanumeric codes that indicate the authorization level of information and the purpose for which it can be used. These codes are assigned to information at the time of publication in CDE and are visible to all authorized users:
Work in Progress
Work in Progress
Information is being developed and is not yet available for sharing or use by other parties.
Suitable for Coordination
Suitable for Coordination
Information can be used by other disciplines for coordination. It is not final and may undergo significant changes.
Suitable for Information
Suitable for Information
Information can be used for reference and information. Suitable for understanding design intent, but not for construction.
Suitable for Construction
Suitable for Construction
Information has been approved for use in construction activities. Represents the definitive technical construction documentation.
As Constructed
As Constructed
Information accurately reflects what was actually built. Database for the Asset Information Model (AIM).
Accepted
Accepted
Information has been accepted by the Appointing Party. Used in the context of formal deliveries to the client.
Partial Acceptance
Partial Acceptance
Information has been partially accepted, with reservations or comments. Requires clarifications or minor modifications before complete acceptance.
Rejected
Rejected
Information has been rejected and must be reworked. The author must restart the process from the WIP area taking into account the comments received.
Definition Not Provided
Definition Not Provided
The suitability code has not yet been assigned or is not applicable in the respective context. Information is pending.
| Code | Usable for | Limitations |
|---|---|---|
| S0 | Internal team use | Cannot be shared |
| S1 | Inter-disciplinary coordination | Not for construction |
| S2 | Information and reference | Not for construction |
| S3 | Construction / Execution | Does not reflect as-built |
| S4 | Final documentation / AIM | Immutable after handover |
| A | Fully accepted by client | — |
| B | Partially accepted, with reservations | Requires clarifications |
| C | — | Rejected — to be reworked |
CDE 19650 Cloud and ISO 19650-2
The CDE 19650 Cloud platform fully implements the ISO 19650-2 process — from collecting EIR and Pre-BEPs during the tender phase, to the formal delivery of the Project Information Model (PIM) to the client.
Integrated Pre-Appointment Flow
Support for the tendering process: EIR upload, Pre-BEP collection from tenderers and comparative BIM capability evaluation.
Digital MIDP and TIDP
MIDP/TIDP creation and management directly in the platform, with Gantt visualization and automatic tracking of planned vs. actual deliveries.
Automatic Suitability Codes
Automatic assignment of S0-S4, A, B, C, D codes based on document state and approver decision in workflow.
Multi-Level Workflow
Author → Reviewer → Approver natively implemented. Automatic notifications, deadlines and escalation when deadlines are exceeded.
Automatic PIM Compilation
Automatic generation of the Project Information Model (PIM) inventory with the status of each deliverable at any time.
Complete Audit Trail
Complete traceability of all actions: who created, modified, approved or rejected each piece of information and when.
Implement ISO 19650-2 in your projects
The CDE 19650 Cloud platform guides you through each stage of the ISO 19650-2 standard, from the first EIR to the final PIM delivery.
Descarca Ghidul Complet CDE ISO 19650 (PDF)
Completati formularul pentru a primi ghidul gratuit