GRAPHISOFT

BIM Execution Plan Template

Created by the GRAPHISOFT Customer Support Services Department

Author Date Version

Enikő Paukó 05.12.2017. V2

Copyright © 2017 by GRAPHISOFT, all rights reserved. Reproduction, paraphrasing or

translation without express prior written permission is strictly prohibited.
Table of Contents
0. NOTES 4

1. PROJECT INFORMATION 5

1.1. Core Project Data 5

1.2. Project Stakeholders 5

1.3. Project Goals 5

1.4. Roles and Responsibilities 5

1.5. Project Team Structure 6

1.6. Project Milestones 6

1.7. Level of Completeness 6

1.8. Project Deliverables 6

1.9. Approval 7

1.10. Collaboration Procedures 7

1.10.1. Information Management Strategy 7
1.10.2. Naming Conventions 7
1.10.3. Meeting Schedule 7
1.10.4. Model Delivery Schedule 7

1.11. Existing Legacy Data Handling 7

2. MODELING REQUIREMENTS 7

2.1. Survey Strategy 7

2.1.1. Survey Sources 7
2.1.2. Survey Data Handling 8

2.2. Geographic Location, Orientation and Origin 8

2.1. Specific Uses 8

2.1.1. Modeling Existing Conditions 8
2.1.2. Site Analysis 8
2.1.3. Space Equipment Validation 8
2.1.4. Visualisation 8
2.1.5. Code Checking 8
2.1.6. Sustainability Evaluation 8
2.1.7. Structural Modeling and Analysis 8
2.1.8. Energy Analysis 8
2.1.9. Lighting Analysis 8
2.1.10. Quantity Take-off 8
2.1.11. 3D Coordination 8
 2.1.12. Construction System Design 8
2.1.13. Facilities Management 8

2.2. Project Standards 8

2.2.1. Project File Hierarchy 8
2.2.2. Libraries 8
2.2.3. Project Sharing 8
2.2.4. Project Info 9
2.2.5. Volume Strategy 9
2.2.6. Origin and Orientation 9
2.2.7. Layer Naming 9
2.2.8. Modeling Unites and Tolerances 9
2.2.9. Standard Drawing Sheets and Title Blocks 9
2.2.10. Annotation and Symbols 9
2.2.11. Attribute Data 9
2.2.12. Schedules 9
2.2.13. Filtered Information 9

2.3. Model Quality Control 9

2.3.1. Model Checking 9

3. SOFTWARE VERSIONS AND MIGRATION 10

4. DISASTER AND RECOVERY PLAN 10

0. Notes
This document contains the minimum topics necessary to fulfil the client’s information
requirements by the project team (AE). Depending on local standards, traditions, and
requirements, you may extend the content with additional relevant topics.
The content of this template is based on our experiences and the UK Level 2 BIM standards.
Instructions appear in italic blue.
Information provided as example appear in grey.

We recommend start developing the BEP of a project once it is started. This way pre-
contract information can be filled in the early (tender) phases, that gives you a relevant basis
for cost calculations, while post-contract information helps in the successful and smooth
execution of the BIM-based project development and coordination.

Content of a pre-contract BEP:

 Project Implementation Plan (PIP)
 Information Model Delivery Strategy

Additional content from post-contract phase:

 Software Versions
 Exchange Formats
1. Project Information
1.1. Core Project Data
Fill the table with core project information.
Project Name
Project Number
Project Brief Description
Site Name
Site Description
Site Location
Site Area
Facility Name
Facility Description
Client Name
Client Address
Client Contact Name
Client Contact Phone no.
Client Contact Email
Contract Type

1.2. Project Stakeholders

Name Title Date Signature
Project Manager
Owner’s representative
Architect
Mechanical Engineer

1.3. Project Goals

Fill the table with Client’s goals, priorities and how BIM supports it, e.g. schedules, BIMx hypermodel, etc.
Goal Description Priority BIM Uses

1.4. Roles and Responsibilities

Fill the table with information of all involved representatives.
Name Role Company/Authority Job Title Email Phone Responsibility
 1.5. Project Team Structure
Place a figure of organisational relationship between team members.

1.6. Project Milestones

Milestone Start Date Completion Date Stakeholder
1. Project Definition Client’s representative
2. Tender Design
3. Schematic Design
4. Design Development
5. Construction Design
6. Technical Design
7. Construction
8. Closeout
9. FM
10.

1.7. Level of Completeness

Information required at each level is defined by the Project Milestones above. Depending on your position in the
project team, you may fill this sheet for the architectural part only or for all parties.
Milestone 1 Milestone 2 Milestone …
Design Completeness 5%
Level of Geometry
Level of Information

1.8. Project Deliverables

1.9. Approval
Document here who is responsible for undertaking the approval of information, timescale of approvals, and
what happens if information is not approved in a timely manner.
 1.10. Collaboration Procedures
1.10.1. Information Management Strategy
Common data environment, file sharing strategy, document management systems among the parties. You may
also define different access rights (upload/download, read/write, etc.) and data security rules (identification).
Describe here sharing and federation protocols and used file formats.
Reference collaboration or management standards here if applicable.
Indicate here if any of the parties’ refuses sharing certain data that are company confidential.
1.10.2. Naming Conventions
Document here how project files and folders should be named to reflect project, discipline, content, revision, etc.

1.10.3. Meeting Schedule

Type Frequency Convenor Participants
Client briefing
Consultant kick-off
Model coordination

1.10.4. Model Delivery Schedule

1.11. Existing Legacy Data Handling

Existing documentation should be checked and validated by one of the parties to negotiate whether it can be
used as reference information. Factors you check: accuracy, actuality, format usefulness/compatibility,
Type of Information e.g. former approval documentation
Owner/Source
Has access
Validates
Format e.g. native model, paper, dwg, pdf
Date of release

2. Modeling Requirements
2.1. Survey Strategy
2.1.1. Survey Sources
Type Delivery Format Origin Notes

2.1.2. Survey Data Handling

Undertaking party
Used Base Point
Units
 2.2. Geographic Location, Orientation and Origin
Document here how models originating in different applications should be aligned. E.g. Survey Point Object
placed to indicate site Origin.

2.1. Specific Uses

Define here the procedures you are going to execute on the model. Add/remove items that are relevant in the
project. Project standards below have to support the requirements of these.

2.1.1. Modeling Existing Conditions

2.1.2. Site Analysis
2.1.3. Space Equipment Validation
2.1.4. Visualisation
2.1.5. Code Checking
2.1.6. Sustainability Evaluation
2.1.7. Structural Modeling and Analysis
2.1.8. Energy Analysis
2.1.9. Lighting Analysis
2.1.10. Quantity Take-off
2.1.11. 3D Coordination
2.1.12. Construction System Design
2.1.13. Facilities Management

2.2. Project Standards

List here all modelling standards applicable for all disciplines incl. client requirements, industry standards,
office standards.
Items listed here should be implemented in the project template files, which ensures consistent delivery of
information.

2.2.1. Project File Hierarchy

Depending on the estimated project size and complexity and project team structure, you may create one or more
files that are referenced into each-other. List the files here with a diagram, which shows the connection between
them.

2.2.2. Libraries

2.2.3. Project Sharing

LAN and/or WAN teamwork and access rights.

2.2.4. Project Info

Project level metadata that is retrieved independent on any building elements. E.g. Project mane, site location,
client data, designer data, etc.

2.2.5. Volume Strategy

Define here how structures are modelled in the different phases to avoid clashes as objects are developed. You
may have spatial volumes reserved for the certain disciplines, e.g. space between the load bearing slab and
reflected ceiling reserved for MEP systems.
 2.2.6. Origin and Orientation
Relation of geographical location, project origins, asset reference points, true north, rotation (user coordinate
systems) of the building models including grids. For better understanding, it is recommended to insert an image
showing the site with important points.

2.2.7. Layer Naming

In most BIM applications, layer system it the primary way of organizing elements. They are generally used at
least to filter data and control visibility. Layer names may reflect author, element type, location information.

2.2.8. Modeling Unites and Tolerances

This information is necessary for clash detection as well as checking the degree of accuracy authors must
archive in the model. Define also measurement units and decimals of precision.

2.2.9. Standard Drawing Sheets and Title Blocks

This section contains sheet sizes, title block content, sheet naming and numbering conventions, revisions, status
codes, etc. Paste here a screenshot of the title block as an illustration.

2.2.10. Annotation and Symbols

As part of the 2D deliverables, there may be standard or client-specific symbols you are going to use. List them
here with an image inserted as an illustration. Displayed information and graphic may vary by LOD.

2.2.11. Attribute Data

Define here what physical and meta data should be assignment to each building component. E.g. wall: element
ID, layer, position, structural function, classification, thickness, height, vertical location, building material, faire
resistance rating, renovation status, etc.

2.2.12. Schedules

2.2.13. Filtered Information

Define here what information subsets need to be delivered for the certain parties of the project. Subsets may
contain limited amount of model elements and metadata included (=Model View Definitions). These subsets are
created with the combination of features, e.g. Layer combination + Story of elements + Partial Structure
Display + Graphical Override + Translator.

2.3. Model Quality Control

Document here the how project consistency defined by the sections above is maintained and managed. Typically,
there is a model maintenance between each project phase made by the BIM Manager.

2.3.1. Model Checking

Type Goal Responsible Party Software
Visual check Eliminate
unnecessary
elements
Interference check Detect clashing
components
Standards check Find elements,
which do not meet
the standards listed
above
Information check Dataset
completeness
3. Software Versions and Migration
Software solutions and versions need to be harmonised to ensure smooth communication.

4. Disaster and Recovery Plan