Skip to main content
COMPLIANCE · ISO 19650-2

ISO 19650 certified. The standard your project deserves.

ISO 19650 is the international standard for managing information across the lifecycle of a built asset using BIM — adopted as the BIM mandate baseline by Saudi Arabia's Vision 2030 giga-projects and increasingly required in Royal Commission tenders since 2023. Design Zone is BSI-certified to ISO 19650-2 (the delivery-phase standard), registered as a BSI Associate Consultant, and an Autodesk Authorized Training Center. Every project we deliver — from a single villa in Jeddah to a 90,000 m² Royal Commission pavilion in Riyadh — follows the standard from EIR authoring through Asset Information Model handover, with a contract-grade audit trail at the end.

  • ISO 19650-2 certified
  • 55+ projects to standard
  • BSI Associate Consultant
  • Autodesk ATC
WHY IT MATTERS

BIM without a standard is just expensive 3D modeling.

  1. 01

    No common language across appointments

    Without ISO 19650, every consultancy invents its own file naming, model federation rules, and handover protocols. Five appointed parties on the same Vision 2030 project end up with five mutually incompatible "BIM" deliverables — the structural model uses Project North, the MEP model uses True North, the architectural model classifies by Uniclass while the civil model uses CSI MasterFormat. Owners are then told they have "a BIM model" when what they actually hold is five fragments that nobody can federate. ISO 19650-2 §5.4 explicitly requires the appointing party to publish information naming conventions, classification systems, and federation strategy before any modeler opens their software — and §5.5 requires the appointed parties to demonstrate compliance during mobilisation.

  2. 02

    Information requirements drift unless they're contractual

    Without an EIR (Exchange Information Requirements) authored to ISO 19650-2 §5.2, what the appointing party asked for at appointment is not what gets delivered at handover. Halfway through a 24-month project, the Level of Information Need quietly relaxes to meet the schedule; at handover the COBie spreadsheet that was supposed to feed Facility Management arrives with empty columns and a note saying "will be updated later." The standard exists precisely to make the asks unambiguous, traceable, and verifiable. Each information container has a named requester, a delivery date in the MIDP, an approval workflow that cannot be skipped, and acceptance criteria that are checked before status changes from Shared to Published.

  3. 03

    No audit trail means no defensible position

    ISO 19650-2 §5.5 requires a Common Data Environment with version control, defined approval workflows, and audit logs that record every status change with author, timestamp, and approver. Without it, three years post-handover when a structural defect surfaces, "the model was up to date" becomes a claim nobody can verify. With it, the appointing party can answer "which version of the structural model was the steelwork fabricated from, and who approved its release on what date" in 60 seconds. For a Royal Commission project running 5+ years through construction and into operations, this isn't a nice-to-have — it's the difference between a defensible position in a forensic dispute and an indefensible one.

WHAT ISO 19650 GIVES YOU

Eight authored documents that turn BIM from intention into contract.

ISO 19650 is built around a small set of authored documents that move with the project from assessment-and-need through asset-information-model handover. Design Zone authors each one as a contract-grade deliverable — not a placeholder template. The list below shows what an appointing party should expect to see, name by name, on a properly run ISO 19650-2 project.

  • EIR (Exchange Information Requirements) — authored to ISO 19650-2 §5.2 before the appointed party is even shortlisted. Defines information purposes, Level of Information Need (LOIN) per stage and discipline, information protocol, federation strategy, and acceptance criteria. A real EIR for a Vision 2030 giga-project is typically 40-80 pages — not a 3-page boilerplate.
  • Pre-appointment BEP (BIM Execution Plan) — submitted by each tendering team showing HOW they would deliver against the EIR if appointed. The appointing party uses pre-appointment BEPs to score tender responses on capability, not just price. A weak BEP at tender stage predicts a weak project.
  • Post-appointment BEP — becomes contractually binding once the appointment is awarded. Lists task teams by role, software versions, federation cadence, naming convention, classification system, and the agreed Levels of Information Need per discipline. Updates whenever the project boundary changes.
  • MIDP (Master Information Delivery Plan) — schedule of WHEN each information container delivers, by WHICH task team, to WHICH project milestone. The MIDP is the operational instrument that turns the BEP into weekly project management.
  • TIDP (Task Information Delivery Plan) — per-discipline breakdown of the MIDP. Each modeler — architectural, structural, MEP, civil, fit-out — has their own delivery schedule traceable to the master plan. A 200-modeler giga-project may have 15+ TIDPs feeding one MIDP.
  • CDE (Common Data Environment) — the single source of truth, configured with the standard four-state status workflow: Work-in-Progress → Shared → Published → Archived. Every status change is logged with author, approver, date, and rationale. Industry-standard platforms include Autodesk Construction Cloud, Bentley ProjectWise, and Trimble Connect — chosen per project, not per consultancy preference.
  • IDS (Information Delivery Specifications) — the technical handover specification: open file formats (IFC 4.3+ for federation, native formats for editability), naming conventions per ISO 19650-2 Annex A, model federation rules, classification system (Uniclass 2015 or CSI as appropriate), and the LOIN matrix.
  • Quality assurance + ISO 19650-2 audit log — every approval is logged. At handover, the appointing party receives a Project Information Model with full audit trail and an Asset Information Model ready to feed ISO 19650-3 operations-phase processes. Independent assessor confirmation is included for tender qualification across the GCC.
HOW WE IMPLEMENT IT

Standard from day zero, not standard at handover.

Most consultancies "do ISO 19650" by rebadging their existing process and stamping the EIR on top of an already-running project. We start from the standard's assessment-and-need stage before geometry exists, then follow each ISO 19650-2 clause through to Asset Information Model handover. The four-stage process below is how every Design Zone project runs, from a Jeddah villa to a Vision 2030 giga-project.

  1. 01

    Assessment + need (ISO 19650-1)

    Before any geometry exists, we work with the appointing party to define the three layers of information requirements per ISO 19650-1: OIR (organisational information requirements — what the owning organisation needs across its asset portfolio), AIR (asset information requirements — what this asset needs to deliver during operations), and PIR (project information requirements — what this project must produce). Most consultancies skip this stage and start at the EIR. The result is an EIR that asks for things the owner can't use and misses things the owner needs.

  2. 02

    Invitation to tender + appointment (ISO 19650-2 §5.2-5.4)

    EIR authored to ISO 19650-2 §5.2-5.4 with full Level of Information Need matrix per stage, federation strategy, and information protocol. Tender package goes to market with EIR attached. Each tendering team submits a pre-appointment BEP showing capability. Post-appointment BEP from the winning team becomes contractual and is signed by both parties before mobilisation. This stage typically runs 6-12 weeks for a Saudi giga-project.

  3. 03

    Mobilisation (ISO 19650-2 §5.5)

    Per ISO 19650-2 §5.5: CDE stood up with the four-state status workflow configured and audit logging enabled, naming convention published to the project handbook, task teams briefed in person and signed off, model templates issued with the agreed origin/levels/grids, federation strategy locked in with a sample federated model proving interoperability before production. This phase typically takes 4-8 weeks and is the single biggest predictor of project success — projects that skip it pay for it later.

  4. 04

    Collaborative production + handover (ISO 19650-2 §5.6-5.8)

    Information containers move through the CDE status workflow under continuous audit. Weekly federation against the master federated model. Status changes from Work-in-Progress to Shared trigger task-team review; Shared to Published triggers appointing-party approval. At completion, the Project Information Model is handed over with full audit trail; the Asset Information Model is fed into the appointing party's ISO 19650-3 operations-phase processes — typically connected to a CAFM system, a digital twin platform, or both.

FREQUENTLY ASKED

ISO 19650 — questions Saudi appointing parties keep asking.

Is ISO 19650 mandatory for Saudi Vision 2030 projects?
As of 2024, Saudi Arabia's National Construction Body (NCB) and the Royal Commissions for Riyadh, AlUla, and the Holy Sites explicitly require ISO 19650-aligned BIM delivery for projects above a defined budget threshold. Every Vision 2030 giga-project RFP we have seen since 2023 — NEOM, Qiddiya, Red Sea, AMAALA, Diriyah Gate, King Salman Park — includes ISO 19650 deliverables as a tender qualifier. Treating the standard as optional is no longer commercially viable for any consultant or contractor pursuing Saudi public-sector work.
What's the difference between ISO 19650-1, -2, -3, -4, and -5?
ISO 19650-1 (2018) defines concepts and principles — the "what is BIM information management" baseline. ISO 19650-2 covers the delivery phase (design + construction) and is the standard most BIM consultancies certify against. ISO 19650-3 covers the operational phase (asset information management) — relevant for digital twins and FM. ISO 19650-4 covers information exchange between actors. ISO 19650-5 covers a security-minded approach for sensitive projects. For most Saudi projects, ISO 19650-2 is the certification that matters in tender qualification.
What does an EIR (Exchange Information Requirements) actually include?
An EIR authored to ISO 19650-2 §5.2 includes: (1) information purposes — why the appointing party needs each model; (2) Level of Information Need (LOIN) per stage and per discipline; (3) information protocol referencing the appointing party's classification system (Uniclass 2015, CSI); (4) federation strategy — how discipline models combine; (5) acceptance criteria — what "done" looks like for each deliverable. A real EIR for a Vision 2030 giga-project runs 40-80 pages, not a 3-page boilerplate.
How long does ISO 19650 implementation take?
For an appointed party (consultancy or contractor), full mobilization to ISO 19650-2 §5.5 standards takes 4-8 weeks before the first model is touched — CDE setup, naming convention publication, federation strategy lock-in, BEP finalization, task team briefings. For an appointing party (owner) building ISO 19650 capability internally, expect 9-12 months to author EIR templates, organisational information requirements, and tender qualification language. Saudi giga-projects typically run owner capability-building in parallel with project kick-off.
What's the cost of ISO 19650 implementation?
For a project, ISO 19650 delivery typically adds 3-5% of the BIM scope budget — embedded in the consultant's fee, not charged separately. For an organization (owner-side capability), expect 250-500K SAR over 12 months for a 200-person engineering department, depending on existing maturity. For Design Zone clients, ISO 19650-2 delivery is the standard methodology — not an optional add-on — so there is no separate line item for it.
Can ISO 19650 be retrofitted to a project already underway?
Yes, but the cost climbs steeply. Clean implementation starts at the assessment-and-need stage before any modeling begins. Retrofitting from detailed design onward means re-authoring the EIR, rebuilding the CDE structure with the four-state status workflow, re-issuing models against new naming conventions, and re-running approvals. Budget 40-60% of the work already done before the retrofit. The honest answer to the appointing party: lock the standard at appointment, not at handover.
What certification should we look for in an ISO 19650 consultant?
Look for ISO 19650-2 certified — issued by an accredited certification body (BSI is the most common in Saudi, alongside Lloyd's Register and others). The certificate number should be referenced on the consultancy's website (Design Zone's appears in our About page footer). "ISO 19650 aware" or "ISO 19650 trained" is NOT the same as certified — the latter means an independent assessor has audited the consultancy's process. Some Saudi RFPs now specifically require certification, not just awareness. Ask for the assessor's report — a confident consultant shares it.
START YOUR PROJECT

Tell us about your project.

Drop your details — a senior BIM lead will reach out.

What happens next
  1. 1

    You send the inquiry

    60 seconds — name, email, scope brief.

  2. 2

    We respond within 24 hours

    A senior BIM lead reads your scope and replies — bilingual EN/AR.

  3. 3

    30-min consultation call

    Real conversation. EIR + BEP scope outline. ISO 19650 aligned.

24hResponse
55+Projects
60+Specialists
Quick inquiry · 60 seconds
Your data stays with us