BIM consultancies that improvise per project fail at scale. We run a documented five-phase delivery workflow on every engagement — from EIR authoring through asset-information-model handover. The system is ISO 19650-aligned, CDE-managed, and federated by default. It's why 55+ projects shipped without drama.
The owner asks for X at appointment. The consultant delivers Y at handover. The gap is paid in change orders, rejected deliverables, and trust loss. Our workflow front-loads the EIR / BEP so the ask is contractually unambiguous before the model exists.
When architectural, structural, and MEP teams model in isolation, every interface becomes a tender-time crisis. We federate weekly from LOD 200 — clashes resolve when they cost minutes, not when they cost RFIs.
Three years after handover, the question "who approved this model on what date" should have one answer. With an ISO-aligned CDE, it does. Without one, every defect investigation becomes archaeology.
The shape is always the same — only the depth changes with project complexity. A villa runs the same five phases as a Vision 2030 giga-project. The workflow is what scales.
Methodology fails at the principle level, not the workflow level. These four are what we hold to even when budget pressure or timeline pressure makes them inconvenient.
No EIR, no engagement. The Exchange Information Requirements must be authored, agreed, and signed before any team opens Revit. This is the single highest-leverage gate in the entire delivery chain.
Single source of truth, version-controlled, audit-logged. BIM 360 / ACC / Aconex — the platform is project-driven but the workflow is constant. No emailing models. No SharePoint folders.
Not at the end. Not at LOD 300. From LOD 200 — when discipline models are still sparse. Catching clashes early is the entire economic argument for BIM.
Drawings, schedules, BOQ — all extracted, not maintained separately. If the drawing and the model disagree, the model wins and the drawing is wrong. This is the discipline that prevents documentation drift.
The methodology run end-to-end on Saudi Arabia's flagship cultural destination. EIR authored, CDE mobilised, A+MEP federated weekly, LOD 300 → LOD 400 progression managed, ISO 19650-2 audit trail maintained through handover. Royal Commission for Riyadh City + Freyssinet Contractors as the appointing party.
It is the only globally-recognised standard that addresses the entire information lifecycle of a built asset — from EIR (Employer's Information Requirements) through BEP (BIM Execution Plan), CDE (Common Data Environment), federated authoring, and asset handover. Saudi Arabia's Ministry of Municipal & Rural Affairs and major giga-project clients (NEOM, ROSHN, AMAALA, Diriyah Gate) increasingly require ISO 19650-2 compliance in their tender documents. Working to it from project start eliminates the rework that comes from retrofitting compliance later.
The 5-phase workflow (Programming → Mobilisation → Federated Authoring → Documentation/Tender → LOD 400/Handover) takes 9-18 months on a giga-project building. Smaller commercial projects (a hotel, a single tower) compress to 4-9 months. The pacing is set by stage gates: we don't advance to LOD 300 until LOD 200 federation is clean, and we don't advance to LOD 400 until tender documents are extracted from a clash-free LOD 300 model.
A CDE is the single, version-controlled source of truth where every model, drawing, and document lives. Without one, teams email files back and forth and inevitably work from outdated revisions. Design Zone uses Autodesk BIM 360 / ACC as the default CDE, with naming conventions and access permissions defined in the BEP at project start. We can also integrate with a client-specified CDE (Bentley ProjectWise, Trimble Connect) when contractually required.
Yes. The OIR drives everything downstream: the AIR (Asset Information Requirements) → PIR (Project Information Requirements) → EIR (Employer's Information Requirements) cascade. If the owner doesn't have a written OIR yet (common on first BIM-mandated projects), we author one collaboratively before issuing the EIR. This ensures the as-built AIM (Asset Information Model) we hand over actually answers the questions the operator will ask.
Yes — the 5-phase workflow is the spine, but the tooling is replaceable. We have delivered projects using BIM 360, Bentley ProjectWise, Trimble Connect, and even SharePoint (when a federal client mandated it). What stays constant is the ISO 19650 information governance: naming, status codes, suitability codes, and the responsibility matrix. The CDE platform is a delivery detail — the standard is the discipline.
Phase 1: signed EIR + BEP. Phase 2: configured CDE + naming standard + task team briefings. Phase 3: federated LOD 200 → LOD 300 model with weekly clash reports. Phase 4: drawings, schedules, specifications, BoQ, all extracted from the LOD 300 model with zero priority-1/2 clashes. Phase 5: LOD 400 fabrication content + as-built AIM ready for ISO 19650-3 operations handover.
Drop your details — a senior BIM lead will reach out.
60 seconds — name, email, scope brief.
A senior BIM lead reads your scope and replies — bilingual EN/AR.
Real conversation. EIR + BEP scope outline. ISO 19650 aligned.