The Complete Guide to ISO 19650

Key Terms

Before diving in, here are the terms you'll see throughout this guide and in the standard itself.

Appointing Party

The organisation commissioning the project - typically the client, developer, or asset owner. They set the information requirements.

Appointed Party

Any organisation delivering information - consultants, contractors, subcontractors. They respond to the appointing party's requirements.

EIR (Exchange Information Requirements)

The document that defines what information the appointing party needs, when they need it, and to what standard.

BEP (BIM Execution Plan)

The appointed party's response to the EIR - how they'll deliver the information requested. Comes in two stages: pre-appointment (pBEP) and confirmed.

CDE (Common Data Environment)

The agreed source of information for the project. A structured system with defined workflows: work-in-progress, shared, published, archived.

Information Container

Any file or set of files that carries project information - a Revit model, a drawing sheet, a schedule, a report.

Part 1 - Concepts and Principles

ISO 19650-1 establishes the foundational concepts. It doesn't tell you what to do - it tells you how to think about information management across the asset lifecycle. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

The Information Management Process

At the heart of Part 1 is the concept that information should be managed as a structured process, not an ad-hoc activity. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante.

Donec eu libero sit amet quam egestas semper. Aenean ultricies mi vitae est. Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi, condimentum sed, commodo vitae, ornare sit amet, wisi.

Part 2 - Delivery Phase of the Assets

This is the part most people actually work with. Part 2 defines the information management process during design and construction - the workflow from EIR through to handover. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

The Eight-Stage Process

Part 2 breaks delivery into eight stages, from assessment and need through to project close-out. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

1. Assessment and need - defining what information is required and why
2. Invitation to tender - issuing the EIR as part of the procurement process
3. Tender response - appointed parties respond with their pBEP
4. Appointment - contract signed, pBEP becomes confirmed BEP
5. Mobilisation - CDE set up, team mobilised, standards confirmed
6. Collaborative production - the actual delivery of information
7. Information model delivery - formal handover of project information model
8. Project close-out - lessons learned, archive, asset information model

Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Sed ut perspiciatis unde omnis iste natus error sit voluptatem.

Part 3 - Operational Phase of the Assets

Part 3 extends the framework beyond construction into facilities management and asset operation. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Most projects in the UAE and KSA don't yet implement Part 3 rigorously, but the trend is moving in that direction - particularly for government-owned assets and large mixed-use developments.

Part 5 - Security-Minded Approach

Part 5 addresses information security within BIM workflows - who can access what, sensitivity classification, and handling of restricted information. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. Aenean ultricies mi vitae est. Mauris placerat eleifend leo.

Implementing ISO 19650 in the UAE and KSA

The standard is international, but implementation is local. Here's what you need to know about applying ISO 19650 in the Gulf region. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

UAE

Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore. Dubai Municipality and Abu Dhabi's Musanada have both issued BIM mandates that reference ISO 19650 either directly or through aligned local frameworks.

KSA

Saudi Arabia's Vision 2030 mega-projects - NEOM, The Line, Jeddah Tower, the Red Sea Project - are driving ISO 19650 adoption at scale. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Common Mistakes When Implementing ISO 19650

After working across dozens of ISO 19650 implementations in the Gulf, these are the patterns we see teams get wrong most often.

• Treating the BEP as a one-time document - the pBEP wins the work, but the confirmed BEP needs to be a living document that evolves as the project progresses.
• Confusing CDE status with approval - "shared" status doesn't mean "approved." Teams regularly skip the review gate between work-in-progress and shared.
• No information delivery plan - without a MIDP/TIDP, there's no schedule for when information is due. This causes cascading delays across disciplines.
• Ignoring the naming convention - ISO 19650 prescribes a structured naming convention for information containers. Non-compliant filenames make the CDE unmanageable at scale.
• Assuming compliance = software - ISO 19650 is a process standard, not a technology standard. You can be fully compliant with basic tools if the process is right.