BIM Execution Plan (BEP) or the BIM manual, as it is more commonly known in Norway, is a central document describing the level and objectives of BIM use on the project, dividing responsibilities, and presenting workflows. It was an important document on a model-based project such as the Randselva Bridge.
The BEP consists of two parts: a general and a project-specific. The general section applies to all BIM projects in a company and it describes work processes and areas of use for BIM. The project-specific part is filled in after contracting the designer in the BIM-start-up meeting. It defines the project-specific framework for data flow, interdisciplinary planning, and collaboration in the project.
The BIM manual is a living document that should be continuously revised in the project, if necessary.
The purpose of BIM Execution Plan / BIM manual is to ensure common expectations, good interaction and understanding between all stakeholders in the project. The BEP should describe how the company carries out BIM projects with a model as the central information carrier from the early stages to planning and production. The document provides a description of the requirements for BIM collaboration in the project, and how responsibilities, execution and participation in the activities must be taken care of with a focus on model management and the end product - the BIM model used for execution, and, if agreed on with the client, during the facility management (FM).
For the Randselva Bridge, the BIM manual was prepared together by the contractor and the designer, after a series of meetings. The document was updated during the project, when new methods or workflows were found to function better for this particular project.
<aside> 💡 Common agreement in the project about its BIM level and objectives. These will have consequences on the modeling and structure of the model
</aside>
<aside> 💡 Clarification and setup for roles, responsibilities, interaction, and interdisciplinary control. Usually clarified during a start-up meeting
</aside>
<aside> 💡 Main information, as project layout with units, 0-point, and coordinates, project and model division, and naming
</aside>
<aside> 💡 Simple modeling principles, information about software and file exchange
</aside>