How to Structure an ISO 19650 BIM Execution Plan (BEP): CDE, Naming & MIDP Guide

Many project teams copy-paste bloated 90-page BIM Execution Plan templates that nobody reads—while failing to lock basic Revit version parity or shared site coordinates on day one. Under BS EN ISO 19650-2, the BIM Execution Plan evolves across two distinct contractual stages between the Appointing Party (Client / Developer) and the Lead Appointed Party (Lead Designer or Design & Build Main Contractor).

First, the Pre-Appointment BEP is submitted during tender to demonstrate capability, federation strategy, software stack, and proposed amendments to the client’s Exchange Information Requirements (EIR). Once commissioned, the team co-authors the binding Post-Appointment BEP alongside the Responsibility Matrix and the Master Information Delivery Plan (MIDP)—locking exact file-drop Fridays, clash tolerances, and parameter schemas before a single wall is modeled.

The fastest way to ruin a multidisciplinary BIM project is allowing the architect to model arbitrarily near Revit’s internal `(0,0,0)` in millimeters while the civil engineer works 450 kilometers away in real-world UTM meters. Every SerMimar® BEP begins with a physical Control Model establishing the exact Survey Point (e.g., ITRF96 / UTM / OSGB36 Easting, Northing, and MSL Elevation), Project Base Point (intersection of Grid A-01 at Ground FFL `±0.00`), and Angle to True North—distributed via `Acquire Coordinates` to every task team.

Volume Subdivision (Spatial Breakdown)

Whenever a single Revit file exceeds 220–250 MB, RAM utilization spikes and cloud synchronization slows across teams. On campuses, resorts, and 25,000+ m² developments, the BEP subdivides models cleanly by Volume / Zone (e.g., `Podium`, `Tower-A`, `Facade-Envelope`, `MEP-Basement`) so parallel pods work at peak velocity without element-borrowing locks.

Whether hosted on Autodesk Construction Cloud (ACC), Dalux, Asite, Aconex, or Trimble Connect, a Common Data Environment is a governance workflow—not merely a cloud folder. Under ISO 19650 National Annex conventions, every information container follows an unambiguous machine-readable string: Project-Originator-Volume-Level-Type-Role-Number (for example, SRM26-SMR-B01-ZZ-M3-A-0001 denoting Project SRM26, Originator SerMimar, Building 01, All Levels, 3D Model, Architectural, Sequence 0001).

Files never jump straight from a modeler’s desktop to the site superintendent. Every Friday, task teams run a model health purge and promote verified models from WIP (`S0`) into Shared (`S1`) for weekly Navisworks clash detection. Only after closing hard clashes and receiving formal Lead Appointed Party sign-off do sheets and models transition into Published (`A1–A4`) for tender or site execution—automatically logging superseded versions in the immutable Archive container.

To prevent last-minute deadline chaos, ISO 19650 requires each discipline (Architectural, Structural, HVAC, Plumbing, Electrical, Facade, Landscape) to author a Task Information Delivery Plan (TIDP) listing every model, schedule, and drawing sheet it will produce, who owns it, its target LOD/LOIN, and estimated engineering hours. The BIM Manager aggregates all TIDPs into one master schedule: the Master Information Delivery Plan (MIDP).

Simultaneously, the BEP distributes a single locked Shared Parameters `.TXT` file and classification standard—Uniclass 2015 for UK/international projects, OmniClass / CSI MasterFormat for North America and GCC, or DIN 276/277 for DACH—ensuring 5D cost estimators and COBie facility managers never encounter inconsistent parameter spelling (`FireRating` vs. `Fire_Resistance` vs. `Yangin_Sinifi`).

An enforceable BEP specifies objective, automated pass/fail metrics audited via Autodesk Model Checker, Solibri Office, and Navisworks Manage at every milestone drop: zero unplaced/unbounded rooms, zero generic `IfcBuildingElementProxy` exports, <2% tolerable Revit warning ratio, zero hard clashes exceeding ±3 mm, and verified IFC4 Reference View / Design Transfer View export translator setups. Finally, banning emailed screenshot PDFs in favor of cloud-synced BCF 2.1/3.0 (BIM Collaboration Format) teleports every engineer’s camera directly to the exact clashing Element GUID—cutting weekly coordination meetings from 3 hours down to 35 decisive minutes.