Practical Application of the ISO 19650 Standard
Fundamental Concepts and Principles
ISO 19650-1 establishes the conceptual framework for managing information throughout the lifecycle of built assets. Here are the three key domains:
Definition of Information Requirements
Clause 5Clients must identify critical assets and departmental questions. The requirements cascade reduces specifications into deliverables for each individual specialist, ensuring all participants work with accurate data.
CDE Workflow
Clause 12CDE proficiency is essential for BIM managers. It includes defining team structures, access groups, and permissions. Release processes include validation, verification, and approval procedures.
Federation Strategies and Container Breakdown
Annex AFederation strategies enable simultaneous work by teams on different components, ensuring information security and facilitating transfer by reducing file sizes.
What does an efficient CDE enable?
A Common Data Environment properly configured according to ISO 19650-1 offers these fundamental capabilities:
Distributed team collaboration
Teams from different locations work simultaneously on the same project.
Conflict analysis
Detection and resolution of conflicts based on document versions.
Accelerated retrieval
Rapid finding of any document through metadata and advanced search.
Information Management Process
ISO 19650-2 defines a structured 8-step process for managing information during the asset delivery phase. Each step has clear objectives and specific deliverables.
The 8-Step ISO 19650-2 Flow
Assessment and Needs Definition
5.1Invitation to Tender
5.2Clients should not request "more than what is necessary for their needs"
Tender Response
5.3Appointment
5.4Mobilization
5.5"What has been tested should work, and what has not been tested will almost certainly fail"
Collaborative Production of Information
5.6Information Model Delivery
5.7Project Close-out
5.8Logical Grouping of Steps
Steps 1-3
Needs assessment, tender, response. Defining the information framework before work begins.
Steps 4-6
Appointment, mobilization, production. Concrete implementation and information creation according to plan.
Steps 7-8
Delivery and close-out. Handing over information, archiving, and collecting lessons learned.
ISO 19650 Fundamental Concepts
Understanding these concepts is essential for correct implementation of the standard in any construction project.
Information Requirements Cascade
From the client's general needs to specific deliverables for each specialist. OIR, AIR, EIR cascade hierarchically down to individual task level.
The S.M.A.R.T. Principle
Specific, Measurable, Appropriately Assigned, Realistic to deliver, and Time-bound. Information requirements must comply with this principle for maximum efficiency.
Essential Documents
EIR (Exchange Information Requirements), BEP (BIM Execution Plan), MIDP (Master Information Delivery Plan) — the fundamental documents of the process.
Quality Assurance
Systematic verification before cross-disciplinary sharing. Discipline-specific checklists and structured validation procedures.
Mobilization Planning
Pre-project testing of systems, processes, and capabilities. Access verification, submission testing, and team training.
Continuous Improvement
Documented lessons learned with implementation responsibilities. Continuous progress from one project to the next through structured feedback.
The S.M.A.R.T. Principle
Well-formulated information requirements must meet these five criteria:
Practical application: Each requirement in the EIR must be specific enough for the delivery team to understand exactly what is expected, measurable to verify compliance, clearly assigned to a responsible party, realistic in relation to available resources, and have a clearly defined deadline.
Essential Process Documents
Exchange Information Requirements
The information exchange requirements defined by the client. The document that specifies WHAT information is needed, IN WHAT FORMAT, and WHEN.
BIM Execution Plan
The BIM execution plan that describes HOW information will be delivered. Includes personnel, tools, formats, and coordination strategies.
Master Information Delivery Plan
The overall information delivery plan. A dynamic document that monitors progress and dependencies between deliverables.
How the CDE Platform Implements ISO 19650
Our CDE platform maps each step of the ISO 19650-2 process with concrete functionalities, automations, and dedicated tools.
Configurable EIR Templates
Predefined templates for Exchange Information Requirements, adaptable to each project's specifics. Rapid generation of compliant documentation.
Automated Workflow
Automatic WIP, Shared, Published, Archived transitions with validations at each step. ISO 19650 compliant roles and permissions.
Roles and Permissions Matrix
Granular access control based on ISO 19650 roles: Lead Appointing Party, Appointing Party, Lead Appointed Party, Task Team.
Complete Audit Trail
Complete recording of every action: who, what, when, from where. Total traceability for compliance and dispute resolution.
Automated Notifications
Email alerts for every status transition, deadlines, and critical events. All stakeholders informed in real time.
Export and Reports
Compliance report generation, CSV/PDF export for audits and presentations to clients or authorities.
MIDP Dashboard
Real-time monitoring of the Master Information Delivery Plan. Visualization of progress, delays, and dependencies.
Automated ISO 19650 Workflow
The CDE platform automatically manages document transitions according to the 4 states defined by the standard
WIP
Team creates
Shared
Coordination
Published
Officially approved
Archived
Final storage
Information Requirements Cascade
How information requirements cascade from organizational level down to individual task level, ensuring complete traceability.
Information requirements at organizational level. What information does the organization need for strategic decisions?
Information requirements at asset level. What information is needed for managing the built asset?
Information exchange requirements. What information must be delivered at each project stage?
Delivery plan at task level. What information does each team produce and when?
Key principle: Each level of information requirements derives from the level above, ensuring that information produced at task level is relevant and aligned with the organization's strategic needs. This cascade prevents information overproduction and focuses effort on what is truly necessary.
Quality Assurance
Systematic verification before sharing
Warning: ISO 19650 warns against "information obesity" — including unnecessary information in models that increases complexity without adding value.
Mobilization Planning
Pre-project system testing
"What has been tested should work, and what has not been tested will almost certainly fail." — ISO 19650 Principle
Continuous Improvement — Lessons Learned
Step 8 (Project Close-out) is not just about archiving. It is the critical moment when the organization captures value for future projects through systematic documentation of lessons learned.
Brainstorming Sessions
Structured meetings with the senior team, similar to the risk register creation process.
Formal Documentation
Each lesson learned is recorded with context, impact, and recommended actions.
Clear Responsibilities
Each documented improvement has a designated responsible party and an implementation deadline.
Application in New Projects
Lessons learned are integrated into EIRs and BEPs of subsequent projects.
Ultimate goal: Every project should be better than the previous one. ISO 19650 is not a static standard — it is a continuous improvement framework that transforms the organization step by step.
Implement ISO 19650 with the CDE Platform
Our CDE platform provides all the tools you need to implement the ISO 19650 standard in your projects, from EIR to archiving.