BEP: BIM Execution Plan

The BEP (BIM Execution Plan) is a fundamental document in the design, construction, and management of projects using the BIM (Building Information Modeling) methodology. It is an operational guide that defines how BIM should be used in a specific project and ensures that all involved parties collaborate effectively and in a coordinated manner.

A Bit of History

The BEP originated in the Anglo-Saxon world within the framework of PAS 1192-2:2013 (Publicly Available Specifications). PAS documents are publicly available specifications, essentially standardization documents similar in structure and format to technical standards, designed to accelerate the standardization process.

The PAS 1192-2:2013 is now obsolete and has been incorporated into UNI EN ISO 19650-1:2019 for Europe. In particular, Italy and the UK have adopted their own National Annexes: UNI 11337 (2015, 2017, 2018; parts 1, 3, 4, 5, 6, 7) for Italy; and, for the UK, the “19650-0” Guide, the National Foreword to “19650-1”, and the National Annex to “19650-2”.

BEP Objectives

• Project Planning and Management: Establishes the BIM requirements, processes, and standards to be followed to ensure project objectives are met.
• Coordination Among Stakeholders: Ensures smooth collaboration and a shared language among teams.
• Quality and Control: Defines criteria for verifying and validating both information and models.

EIR – Exchange Information Requirements

The starting point is the EIR (Employer’s Information Requirements), formerly part of PAS and now replaced by ISO 19650 as Exchange Information Requirements. The EIR defines the information requirements and objectives that the client (employer) sets out when launching a tender.

In detail, in this phase, the client, through the Project Information Specification, uses the EIR to define how data should be shared and how deliverables should be created, verified, archived, and submitted among project participants.

The EIR should contain the following documents:

• OIR (Organizational Information Requirements): Defines the information needed to set goals for those intending to participate in the tender.
• AIR (Asset Information Requirements): Contains all the information required for a built asset to function and be properly maintained (management, commercial, and technical data).
• PIR (Project Information Requirements): Based on the tasks to be carried out, these describe additional details to meet the objectives set out in the OIR.

Note: EIR and BEP are distinct documents and phases.

BEP Phases

Pre Contract BEP

The next phase after the EIR is the offer phase: the Pre-Contract BEP. Its main purpose is to respond to the EIR by outlining the bidder’s approach, capabilities, and competencies in executing the BIM project. Through the PIM (Project Information Model), the bidding professional team provides all the preliminary documents (design, scheduling, execution, delivery) required for the offer.

The client then validates the team’s capabilities by drafting the PIP (Project Implementation Plan).

Post Contract BEP

This phase is essential for communication and the delivery of project documents. It contains the contractual requirements for information exchange within the agreed timeframes and through established channels. It is much more detailed than the pre-contract phase and includes:

• MIDP (Master Information Delivery Plan): Specifies the information to be delivered, their formats, and includes both models and drawings.
• TIDP (Task Information Delivery Plan): A component of the MIDP, to be prepared by each coordinating figure in the project, detailing their scope. The MIDP is essentially the collection of all TIDPs for the project.

This phase also includes:

• BIM Models and Information: Required Level of Development (LOD), file structure and naming conventions, model sharing and update methods;
• Roles and Responsibilities: Key roles such as BIM Manager, BIM Coordinator, BIM Modeler, along with responsibilities and workflows;
• Information Management Plans: Use of Common Data Environment (CDE) platforms, approval and review procedures;
• Standards and Protocols: Reference standards (e.g., ISO 19650);
• Interoperability Rules and File Formats (e.g., IFC).

You might be interested in