What the BEP states
The BEP states how a delivery team will meet the appointing party's information requirements: who does what, to what standard, in what environment and on what schedule. ISO 19650-2 expects a pre-appointment BEP with the tender and a confirmed BEP after award. Together with the TIDPs and the MIDP, it plans who delivers what, and when.
How the TIDP and MIDP fit together
- A TIDP (task information delivery plan) belongs to one task team. It lists that team's information containers, the author and reviewer, the level of information need, the milestone and the due date.
- The MIDP (master information delivery plan) aggregates all TIDPs into one schedule for the project, so milestones and dependencies can be seen across disciplines.
- Each task team owns its TIDP; the lead appointed party owns the MIDP that rolls them up.
| Plan field | Typical content |
|---|
| Container ID and title | The information container following the project naming convention |
| Author and reviewer | Who produces the container and who checks it |
| Level of information need | The agreed need for that container at that milestone |
| Status | The CDE state and suitability, for example WIP or Shared |
| Milestone and due date | The information exchange the container supports |
Ten steps to a BEP
- Information requirements: capture OIR, AIR, PIR and EIR, and set exchange requirements and acceptance criteria.
- BIM use selection: choose high-value uses and avoid unnecessary model effort.
- Delivery team structure: assign roles and the responsibility matrix.
- CDE workflow set-up: the Work in Progress, Shared, Published and Archive states and the status codes.
- Level of information need: geometry, data and documentation by purpose.
- openBIM exchange rules: IFC, BCF, IDS and COBie, with software-neutral workflows.
- Model production method: authoring standards, naming, classification and templates.
- Coordination and issues: the clash process, issue ownership and close-out.
- Information delivery plan: a TIDP per task team and the MIDP, with milestones.
- Asset handover readiness: asset data, O&M information and digital-twin foundations.
Keep the BEP alive
The BEP should be updated as the project moves between phases, not written once for the tender. A useful test is traceability: every EIR requirement should be answered by a step in the BEP, and each step should map to a dated milestone in the TIDP and MIDP.
What to check
- Every EIR requirement is answered by a step in the BEP.
- The TIDP and MIDP exist and have dated milestones.
- The BEP is updated across phases.
- Roles are written as a responsibility matrix with one accountable role per activity.
This guide is drawn from DEIM's approved knowledge base. The ten steps align with the ISO 19650-2 delivery process; the way of working described is DEIM's recommended approach.
References
- ISO 19650-2: delivery phase of assets (BEP, TIDP, MIDP)
- UK BIM Framework: BIM Execution Plan guidance
Drawn from the approved DEIM knowledge base
Related service: Digital Delivery (BIM and ISO 19650)
Related guides
