
Almost every BIM-mandated project in Dubai now references ISO 19650 somewhere in its tender documentation or BIM Execution Plan, yet a surprising number of professionals working on those projects couldn’t accurately explain what the standard actually requires. This guide sets out what ISO 19650 actually standardizes, walks through its main parts, and explains — specifically — how it applies to projects governed by Dubai Municipality and Abu Dhabi Municipality (ADM).
ISO 19650 is not a modeling standard. It will not tell you how to draw a wall, which family to use for a door, or how many segments a curtain wall panel should have. It is an information management standard: it defines how project information should be organized, named, shared, controlled, and handed over across everyone working on a built asset, from the earliest design concept through construction and into the building’s operational life.
Published jointly by the International Organization for Standardization in 2018, ISO 19650 was developed as an international evolution of the UK’s BIM Level 2 framework, led by the British Standards Institution, the Centre for Digital Built Britain, and the UK BIM Alliance. Where Level 2 described a maturity level a project had reached, ISO 19650 codifies the actual mechanics: what an appointing party must specify, what an appointed team must deliver, and how information moves between them in a controlled, auditable way.
The ISO 19650 series currently comprises several parts, though most working BIM professionals will interact primarily with Parts 1 and 2:
| Part | Focus | Who It Matters Most To |
|---|---|---|
| Part 1 | Core concepts, terms, and principles — information requirements, roles, the information delivery cycle, and the Common Data Environment | Everyone on a BIM project; foundational reading |
| Part 2 | Information management requirements during the delivery phase (design and construction) | BIM Coordinators, Managers, and appointed design/construction teams |
| Part 3 | Information management during the operational phase — the transition from Project Information Model to Asset Information Model | Facilities managers and asset owners |
| Part 4 | Information exchange | Teams handling data interoperability between platforms |
| Part 5 | Security-minded approach for sensitive information | Projects with security-sensitive assets (government, infrastructure, defence-adjacent work) |
| Part 6 | Health and safety information | Health and safety-critical information handover |
Most introductory training — and most day-to-day project work — concentrates on Parts 1 and 2, since these establish the core principles and delivery-phase processes that a working BIM Coordinator or Manager actually applies on a live project.
Underneath the parts and clauses, ISO 19650 is built around a small number of practical mechanisms that every working BIM professional needs to understand, not just recognize as jargon:
Understanding these concepts in practice is what separates someone who can simply operate Revit’s modeling tools from someone who can function inside a properly managed, multi-consultant BIM project — which is the level Dubai’s larger developers and consultancies now expect from BIM Coordinators and Project Architects, not just entry-level modelers.
Dubai Municipality’s BIM circular mandates BIM submission on projects above a defined value threshold and on high-rise developments above a set number of floors. In practice, the workflow the circular expects — coordinated 3D models per discipline, digital clash detection, and structured digital model submission alongside traditional permit drawings — corresponds directly to ISO 19650-aligned working practice: a managed Common Data Environment, clearly assigned modeling responsibilities, and defined Levels of Development for each discipline’s model at each project stage.
For a design team operating in Dubai, this means ISO 19650 isn’t an abstract international standard to reference in a proposal document — it directly shapes the specific drawing conventions, digital submission formats, and coordination checkpoints that a project actually has to hit to pass Dubai Municipality’s review process.

Abu Dhabi Municipality (ADM) runs its own building permit and drawing submission framework, with its own conventions for what a compliant submission package looks like — distinct enough from Dubai’s that a BIM professional who has only ever worked to Dubai Municipality’s format can genuinely struggle on their first Abu Dhabi project. Both frameworks draw on the same underlying ISO 19650 information-management principles — a managed CDE, clearly defined information requirements, coordinated multi-discipline models — but the specific submission checklists, title block conventions, and review processes differ between the two emirates.
A BIM professional genuinely working across the UAE, rather than exclusively within one emirate, needs to understand both frameworks rather than assuming Dubai’s requirements automatically transfer to an Abu Dhabi project, or vice versa. This is precisely the gap Orbit’s Revit Architecture and BIM Manager training program address directly — walking students through the same project modeled and documented to both Dubai Municipality and Abu Dhabi Municipality submission formats, so the differences are visible firsthand rather than discovered the hard way on a live project.
For someone stepping into a BIM Coordinator role on a Dubai or Abu Dhabi project, ISO 19650 compliance in practice comes down to a manageable set of concrete responsibilities:
Before ISO 19650 existed, the UK’s BIM Level 2 approach was underpinned by a set of British Standards — primarily BS 1192 and the PAS 1192 series — which defined much of what later became ISO 19650’s core structure: the Common Data Environment concept, information exchange protocols, and collaborative production of architectural, engineering, and construction information all trace their lineage directly back to these earlier documents. ISO 19650 essentially took that proven UK framework and internationalized it, adapting terminology and structure so it could be adopted consistently outside the UK, including across the Gulf region. For a BIM professional, this history explains why so much ISO 19650 terminology — the CDE’s Work in Progress / Shared / Published / Archived states in particular — will feel immediately familiar to anyone who previously worked under the older British Standards, because it is substantially the same underlying framework, formalized and internationalized rather than reinvented from scratch.
| Term | What It Means in Practice |
|---|---|
| Appointing Party | The client or organization commissioning the project and defining what information it needs |
| Appointed Party | The consultant, contractor, or supplier delivering design or construction information against the client’s requirements |
| EIR (Exchange Information Requirements) | The client’s defined information needs, agreed before modeling starts |
| BEP (BIM Execution Plan) | The delivery team’s documented plan for how they will meet the EIR |
| CDE (Common Data Environment) | The single managed digital space where project information is shared, reviewed, and approved |
| LOD / LOI (Level of Detail / Information) | The agreed degree of geometric and data detail a model element should carry at a given project stage |
| PIM (Project Information Model) | The model built and maintained during the design and construction phases |
| AIM (Asset Information Model) | The trimmed-down model handed over for operational and facilities management use |
There is no single universally mandatory “ISO 19650 certification” required to work on compliant projects, which surprises some professionals expecting a formal exam-based credential comparable to, say, a professional engineering license. In practice, competence is demonstrated through a combination of structured training that covers ISO 19650’s core concepts in depth, hands-on Revit and coordination-tool proficiency, and genuine project experience operating inside a managed Common Data Environment. Orbit’s BIM Manager Training Program is built specifically to cover this combination — ISO 19650 process knowledge alongside the practical Revit and Navisworks skills needed to actually apply it — rather than treating the standard as a purely theoretical topic disconnected from day-to-day modeling work.
ISO 19650 describes information management as a repeating cycle rather than a single one-time process, and understanding that cycle in sequence makes the standard far less abstract. It begins with the appointing party establishing their Organizational Information Requirements and Project Information Requirements — what they need to know, and why, framed at the organizational and project level respectively. Those requirements are then translated into Exchange Information Requirements for a specific appointment, defining what the appointed team must actually deliver. The appointed team responds with a BIM Execution Plan setting out how they’ll meet those requirements, broken down into a Master Information Delivery Plan and discipline-specific Task Information Delivery Plans. Information is then produced, checked, reviewed, and approved through the Common Data Environment’s status workflow before being shared with the rest of the project team. At defined trigger points — project stage gates, or ultimately practical completion — the cycle culminates in information being either handed over as part of the operational Asset Information Model or fed back into the next stage’s requirements. For a BIM Coordinator, recognizing which stage of this cycle a project is currently in is often more useful day to day than reciting the standard’s clause numbers from memory.
ISO 19650-5 sets out a security-minded approach for projects handling sensitive information — typically government, infrastructure, or defence-adjacent work where a building’s digital model could reveal information a client would rather not have widely accessible. While most private commercial and residential BIM projects in Dubai don’t require this level of security overlay, professionals working on government, transport infrastructure, or utility projects should understand that ISO 19650-5 principles — controlling who can access which parts of a model, and being deliberate about what sensitive data gets embedded in a shared Common Data Environment — can apply on top of the standard Part 1/Part 2 information management process. It’s a good example of why ISO 19650 is described as a family of standards rather than a single document: different parts become relevant depending on a project’s specific sector and sensitivity, not every part applies equally to every project.
It’s worth stepping back from the process detail to state plainly why ISO 19650 compliance is worth the discipline it requires, beyond simply satisfying Dubai Municipality’s submission checklist. Projects run with genuine ISO 19650 discipline consistently show fewer late-stage coordination surprises, since clashes and information gaps get surfaced through the structured CDE and clash-detection process rather than discovered informally and late. They also hand over more usable long-term asset data, since the PIM-to-AIM transition was planned from the start rather than improvised at completion. And they create a clearer audit trail of who was responsible for which piece of information at which point — genuinely useful when disputes arise over design responsibility, which they eventually do on almost any complex project. None of this is abstract compliance theatre; it’s a process built around avoiding some of the most expensive, recurring failure modes in construction project delivery.
For a professional new to the standard, it’s worth setting realistic expectations about how long genuine comfort with ISO 19650 actually takes. Reading through the core concepts — the CDE, EIR, BEP, and PIM/AIM distinction — can be done in a single focused study session, and most structured BIM training programs cover this foundational layer within their first few sessions. Genuine working fluency, where you can draft a sensible BEP section, interpret an EIR critically rather than just accept it at face value, or manage a live CDE’s status discipline without supervision, typically takes several months of combined training and real project exposure, since the standard’s value is almost entirely in its practical application rather than its written definitions. Professionals who rush past the fundamentals to chase a “BIM Manager” title too early often struggle precisely because they’ve memorized the vocabulary without the practical judgment that only comes from actually running the process on a live, imperfect project with real coordination pressure.
Put together, the practical reality for a BIM Coordinator or aspiring BIM Manager working in Dubai today is this: ISO 19650 is not optional theory to reference in a proposal document, it is the working framework that most BIM-mandated projects in the city are already, at least nominally, operating under. The gap between projects that claim ISO 19650 compliance and projects that actually practice it consistently is where genuine professional value gets created — a BIM Coordinator who can close that gap, project after project, becomes measurably more valuable than one who can only recite the standard’s terminology. Combined with the dual requirement to understand both Dubai Municipality and Abu Dhabi Municipality submission conventions specifically, that combination of genuine process fluency and UAE-specific regulatory knowledge is what separates a BIM professional who is merely aware of ISO 19650 from one who is genuinely trusted to run a compliant project from kickoff to handover.
ISO 19650 itself is an international standard rather than UAE law, but Dubai Municipality’s BIM circular effectively requires ISO 19650-aligned working practice — coordinated models, structured information exchange, digital clash detection — on projects that fall under its mandate.
No. Both draw on the same underlying ISO 19650 information-management principles, but each emirate maintains its own specific submission formats, conventions, and review processes, and a BIM professional working across both needs to understand each framework separately.
The EIR is the client’s stated requirements for what information they need, defined before modeling starts. The BEP is the appointed team’s plan for how they will actually deliver against those requirements — the EIR is the ask, the BEP is the answer.
In practical terms, yes — ISO 19650 formalizes and expands on the same collaborative, federated-model principles first set out in BIM Level 2, and most current project documentation references ISO 19650 directly rather than the older Level 2 terminology.
A formal certification is not always a strict prerequisite, but demonstrable, practical understanding of ISO 19650’s core mechanisms — the CDE, EIR, BEP, and PIM/AIM distinction — combined with genuine Revit and coordination-tool proficiency, is what employers on BIM-mandated Dubai projects actually screen for.


