Contents
Contents
General Overview of BIM Execution Plan
Document Revision History
Overview
A. Project Info
B. Definitions
C. Project Schedule
D. BIM Execution Plan Timeline
E. Reference Points
Project Team
A. Roles/Responsibilities
B. Team Directory
Project Specific Deliverables
A. BIM Goals
B. BIM Uses
C. Project Deliverables
Design
Construction
Electronic Communications
A. Software Requirements
B. Electronic File Storage
C. Information Exchange Schedule
E. Model Naming
F. Sheet View Naming
G. Trade Contractor Coordination File Naming
Collaboration Procedures
A. Meetings
Project Meetings
BIM Coordination Meetings
B. Coordination Schedules
Design
Construction
C. Quality Control
Model Content Requirements
A. Model Content Progression
B. Embedded Data
Appendices
Appendix 1 - Model Progression Schedule
General Overview of BIM Execution Plan
The purpose of this BIM Execution Plan manual is to create a standard format across all GW projects that utilize BIM to work in concert with the GW BIM Procedures Manual. The GW BIM Procedures Manual defines the type and level of information and data needed by GW at project closeout to have the data necessary to effectively manage properties. This BIM Execution Plan has been formatted to facilitate the conversations between the design and construction partners to prepare for the collection of this data, as well as to encourage the project team to explore other ways in which the use of BIM can enhance project delivery.
In order to implement this execution plan, the following will be performed:
-Identification of team members involved in BIM implementation and project timelines
-Evaluation of project intended BIM uses, and development of BIM standards to work with final deliverables expected by GW
-Establishment of electronic communication requirements for the project, including software, file storage, and naming conventions
-Documentation of collaboration procedures, including information exchange schedules and coordination meetings.
Document Revision History
At a minimum, updates are required at the beginning of the project, start of SD, start of DD, and hiring of Construction Manager.
Rev / Date / Section / Description of UpdatesThe Table of Contents is set up to automatically pull in the page numbering. In order to update as content is added to this execution plan, click anywhere within the table to highlight it, then at the top of the table click “Update Table” and then select “Update Page Numbers only”.
Overview
This section defines basic project reference information and determined project milestones.
A. Project Info
Confirm official GW project name and project number to utilize with GW Development Manager per GW BIM Manual Section Naming Conventions.
GW Project NameGW Project Number
Project Location and Address
Brief Project Description
B. Definitions
A
AiM AssetWorks
Facility Management system utilized by GW to track all project assets and documents, including submittals, maintenance information, and warranties.
As-Built Drawings
Physical mark-up of a printed set of Construction Documents that captures changes and updates throughout the construction process, including RFIs, bulletins, and field conditions. This does not involve the updating of any models.
As-Built Record Model
Design Model that has incorporated changes and updates throughout the construction process, including RFIs, bulletins, and field conditions.
Asset
Individual items incorporated into the construction of a project. For GW, information is collected by this for use as facility data.
B
BIM Project Execution Plan
A document created utilizing GW’s provided template to define procedures and roles for the preparation of electronic media during the project.
BIS or BISM
Building Information Systems Manager
C
Closeout Documents
Consist of approved submittals, operating and maintenance manuals, as-builts, warranties, and other documentation and paperwork that is prepared by either the Contractor or Architect for the Owner’s information and use, and is provided as a condition precedent to Final Payment.
COBie
An abbreviation that stands for Construction Operations Building Information Exchange. It is way to capture information regarding assets outside of the BIM model for use by an Owner to import into their facilities management system.
Contractor
The firm serving as lead builder for the project, working in the capacity of either General Contractor or Contractor.
Coordination Model
BIM Model prepared by Contractors to further develop the Design Model for use in system fabrication or field construction.
D
Design Model
BIM Model prepared by Designers to communicate aspects of the design. It may consist of sub-models prepared by each of the Discipline Designers, such as Architecture, Mechanical, Electrical, and Structural.
Designer
The firm serving as developer of the project documents, working in the capacity of Architect, Engineer, or Consultant.
.DWG
File type associated with a native AutoCAD file.
F
Facilities Information Management (FIM)
Information regarding the design and construction of a facility utilized by the University for managing buildings
L
Level of Development (LOD)
A way to define the level of detail of elements within a BIM model.
M
MasterFormat
A numbering system developed by CSI to organize specifications. Additional information may be found at:
N
.NWF
File type associated with a native Navisworks file.
O
OmniClass
A numbering system developed by International Organization for Standardization (ISO) to provide structure for electronic databases. It is helpful for categorizing assets in a BIM model or facilities management system.
OmniClass Table 23
Spreadsheet that contains the corresponding codes utilized in the BIM Model to categorize assets within GW’s facility management system.
P
Project Closeout
The managed and orderly transition of the work from Substantial Completion to Final Payment, including the finalization of final paperwork.
Project Team
The collective group of representatives from GW, the Designer, and Contractor.
R
.RVT
File type associated with a native AutoDesk Revit file. It is the deliverable file format for all projects.
S
Substantial Completion
Establishes a date that the Work can be used for the purpose intended, and involves the formal transition of property management from the Contractor to GW
C. Project Schedule
Include BIM milestones, design activities, and any other major activities during the project.
Project Phase / Milestone / Estimated Start Date / Estimated Completion DateD. BIM Execution Plan Timeline
The timeline for implementation of BIM over the life cycle of the project needs to be documented. Chart is pre-populated with recommendations on which phase each activity will take place. Adjust as needed specific to project needs.
BIM Activity / Schematic Design / Design Development / Construction Documents / Construction / Facility TurnoverDivision 1 BIM Spec Creation / X
BIM Kickoff Meeting / X / X
Revit standards and templates / X / X / X
BIM Execution Plan updates / X / X / X
BIM collaboration meetings / X / X / X / X / X
Model progression table / X / X / X / X
Asset Table / X / X / X / X
Record Model / X / X / X
E. Reference Points
All models will be coordinated around one control point, determined at the beginning of the project. GW will provide GPS survey information to the team.
The composite model will contain a 3D target element that is a visual reference point to assist in aligning the Revit models. The 3D target also contains the reference data found in the site survey from the project (e.g. elevation above sea level, compass orientation, etc)
Replace the example 3D target below with the project specific target:
Project Team
A. Roles/Responsibilities
Each organization participating in the BIM process shall designate a BIM Manager. These individuals will be responsible to lead and enforce the requirements of the BIM Execution Plan within their team. The roles are defined as follows:
Role / ResponsibilitiesA/E BIM Manager / -Develop and publish the BIM Execution plan
-Coordinate with project Discipline Model Managers
-Enforce compliance with filing naming, LOD requirements, and modeling responsibilities
Discipline Model Manager / -Enforce compliance of discipline’s design model with project requirements
-Coordinate with other project Discipline Model Managers and project Trade Model Managers
CM BIM Manager / -Assist A/E BIM Manager with development of BIM Execution plan
-Coordinate with project Trade Model Managers
-Coordinate creation and management of Record As-Built Model
Trade Model Manager / -Enforce compliance of trade model with project requirements
-Coordinate with other project Trade Model Managers and Discipline Model Managers
B. Team Directory
Enter in BIM contacts for each organization involved with the project.
Discipline / Organization / Name / Role / Time Zone / Email / PhoneProject Specific Deliverables
A. BIM Goals
The project team needs to document BIM uses on this project to aid in populating the table found in the next section. Examples have been provided – these should be deleted and replaced with project specific information.
Project Phase / Goal Description / Potential BIM UsesDesign / Address conflicts in design / 3D Design coordination
Construction / Identify concerns with construction sequences / 4D modeling
Turnover / As Built model / Turnover to model
B. BIM Uses
Referring to the BIM Goals identified in the previous section, indicate the BIM uses that will be implemented on this project by placing a mark next to the item, utilizing the legend in the table[1]. Insert any additional uses as applicable in the empty cells provided.
X / Plan / X / Design / X / Construct / X / OperateProgramming / Design Authoring / Site Utilization Planning / Building Maintenance Scheduling
Site Analysis / Design Reviews / Construction System Design / Building System Analysis
3D Coordination / 3D Coordination / Asset Management
Structural Analysis / Digital Fabrication / Space Management /Tracking
Lighting Analysis / 3D Control and Planning / Disaster Planning
Energy Analysis / Record Modeling / Record Modeling
Mechanical Analysis
Other Eng. Analysis
Sustainability (LEED) Evaluation
Code Validation
Phase Planning (4D Modeling) / Phase Planning (4D Modeling) / Phase Planning (4D Modeling) / Phase Planning (4D Modeling)
Cost Estimation / Cost Estimation / Cost Estimation / Cost Estimation
Existing Conditions Modeling / Existing Conditions Modeling / Existing Conditions Modeling / Existing Conditions Modeling
Legend: X = Confirmed Use; O = Potential Use
C. Project Deliverables
Define the deliverables below for design and construction. Verify that the information pre-populated below is accurate for this project. This list must include those contractually required, but may include non-contractually required documents that the team has elected to prepare and share with other team members.
Design
Phase / Submission Requirements / FormatProgramming / Narrative / .pdf
Schematic Design / Narrative
Drawings / .pdf
Design Development / Specifications
Drawings
Design Model / .pdf
.rvt
Construction Documents / Project Manual
Drawings
Design Model / .pdf
.rvt
Bid Process / Addenda / .pdf, .rvt
Construction / Bulletins / .pdf, .rvt
OmniClass Table 23 / At end of CDs / .pdf, .xls
Record Documents / Specifications / .pdf
Construction
Type / Submission Requirements / FormatCoordination Models – MEP, Structural, Exterior Skin / At end of coordination / .rvt, .dwg, native format
As-Built Model - Final / At project completion – with submittals, O & M’s, and warranties attached / .rvt, .dwg
OmniClass Table 23 / At project completion / .pdf, .xls
COBie Compliant Sheets / At 75% project completion / .xls
Electronic Communications
A. Software Requirements
Below are the standards for software requirements on GW projects. If a team member has any deviations, this needs to be discussed with GW to understand potential impact to final deliverables.
BIM Use / Discipline / Software / VersionArchitecture Design / Architecture / AutoCAD & Revit Architecture 2012 / 20110916_2132
Structure Design / Structure / AutoCAD & Revit Structure 2012 / 20110916_2315
HVAC Design / HVAC / AutoCAD 2012 (Add-on) CADductCADmech / TSI Version: 21 2.41.157.SP4
Plumbing Design / Plumbing / AutoCAD 2012 (Add-on) CADductCADmech / TSI Version: 21 2.41.157.SP4
Electrical Design / Electrical / AutoCAD 2012 (Add-on) CADelec
Civil Design / Civil / AutoCAD Civil 3D 2012
Fire Protection Design / Fire Protection / MEP CAD AutoSprink / Version 8.1
HVAC Fabrication / HVAC / AutoCAD 2012
(Add-on) CADductCADmech / TSI Version:21
2.41.157.SP4
Plumbing Fabrication / Plumbing / AutoCAD 2012
(Add-on) CADductCADmech / TSI Version:21
2.41.157.SP4
Electrical Fabrication / Electrical / AutoCAD 2012
(Add-on) CADelec / TBD
Fire Protection Fabrication / Fire Protection / MEP CAD AutoSprink / Version 8.1
Structure Detailing / Structure / TBD / TBD
Coordination / CM Coordination / Navisworks Manage 2012 / 9.0.0.69686
B. Electronic File Storage
An electronic storage location needs to be identified to provide a workspace for regular transferring of files. This location should store both archive and current files. Complete the following matrix after the BIM kick off meeting. Information currently populated is an example.
File Location / File Path /Directory / File Type / Password Protect / File Maintainer / UpdatedFTP site
ftp://ftp.***.***/*** / Root Project Folder
/Arch
/Mech
e.g. GWSEH/Arch / SEH 11456 Architecture – R13 2013-11-13 * / .rvt / Yes
******** / Joe Smith / Weekly
* Refer to BIM Procedures Manual for filing naming conventions
C. Information Exchange Schedule
Document the information exchanges and file transfers that will occur on the project. Below is a sample – delete and customize with project specific information.
Transfer of models and database files shall take place on a regular basis to the locations identified in the previous section under Electronic File Storage. Files shall be uploaded according to the following schedule by the Discipline Model Managers or Trade Model Managers who are responsible for ensuring their models are copied as agreed for coordination purposes. Additional uploads may be required as requested by the A/E or CM BIM Manager.
Information Exchange / File Sender / File Receiver / One-Time or Frequency / Due Date or Start DateAuthoring – 3D Coordination / Architectural / Structural / FTP Post – Coordination Lead / Weekly / [Date]
As-built model updating check / Contractor / Monthly
Process for as-built model checking during construction needs to be discussed. Include this discussion here, including when the handoff from Designer to Contractor will take place, as well as how updates in the model will be documented and verified:
Teams may desire to further expand the process of model exchange. If desired, include this information below:
E. Model Naming
For more information, refer to the section on Model Naming in the GW Procedures Manual.
The Designer shalldefine the naming conventions for models in accordance with the following format:
Format / [GW Project Number] Space [Discipline Designator] Space [-] Space [Software Version Designator] Space [Reference Date]Example / 11456 Architecture – R13 2013-11-13
11456 Structure – R13 2013-11-13
11456 Mechanical – R13 2013-11-13
Architect shall confirm with GW Manager-PIRC on the official project number to use for the establishment of model naming.
The discipline designator shall consist of one alphabetical character utilizing the following list:
A / Architectural / Q / Audio VisualC / Civil / S / Structural
E / Electrical / T / Information Technology/Telecommunication
F / Fire Protection & Fire Alarm / V / Elevators
L / Landscape / X / Security
M / Mechanical / Z / Zoning
P / Plumbing
Depending on project size, a project may be broken into multiple models with one coordinated model file per floor, area, or level. If this segmentation is done, the major design disciplines need to be sectioned into Architectural, Structural, and Mechanical models. In this case, these additional discipline designators may be utilized:
MD / Mechanical Ductwork / ED / Electrical Distribution and Fit-outMH / Mechanical Hydronics / EL / Electrical Lighting
ME / Mechanical Equipment / FP / Fire Protection
PL / Plumbing, Waste, and Vent / CV / Civil
The software version designator shall utilize the following list:
R13 / Autodesk Revit 2013 / R14 / Autodesk Revit 2014Reference date formatting shall be 4-digit year [-] 2-digit month [-] 2-digit day
F. Sheet View Naming
For more information, refer to the section on Sheet View Naming in the GW Procedures Manual.
Naming conventions for sheet views generated in the model shall be in accordance with the following format:
Format / [GW Project Number] Space [Discipline Designator] Space [Sheet Sequence Number] Space [-] Space [Sheet Title]Example / 11456 A0101 – First Floor Plan
It is important that files are named in this exact format so as to avoid system conflicts when drawings are uploaded to GW’s asset management system and allow them to sort properly.
The discipline designator shall consist of one alphabetical character utilizing the following list:
The George Washington University BIM Manual | 1
Version 1.0 - August 2014
A / Architectural / L / LandscapeB / Building Permits / M / Mechanical
C / Civil / P / Plumbing
D / Demolition / Q / Audio Visual
E / Electrical / S / Structural
F / Fire Protection & Fire Alarm / T / Information Technology/Telecommunication
G / General Notes/Information/Life Safety / V / Elevators
I / Interior Design / X / Security
K / Kitchen Equipment / Z / Zoning
The sheet sequence number shall consist of four numerical characters utilizing the following list:
0000 / General (Symbols, Legends, Notes) / 0500 / Details0100 / Plans (including Reflected Ceiling Plans) / 0600 / Schedules and Diagrams
0200 / Elevations / 0700 / Elevators and Stairs (plans, details, sections) or User Defined (non-architecture)
0300 / Sections / 0800 / Enlarged Restroom Plans and Interior Elevations or User Defined (non-architecture)
0400 / Enlarged Views (plans, sections, elevations) / 0900 / Interior Details, Partition Types, Window Types
G. Trade Contractor Coordination File Naming
For files that are generated by the CM and trade contractors during the coordination process, the following naming conventions shall be utilized.
Format / [GW Project Number] Space [Trade Designator] [-] [Level] [-]Area [-] [Phase Code] [-] [3D] [-] [ Reference Date]Example / 11456 A-02-C-DSN-3D-2013-11-13
11456 E-03-D-SUB-3D-2013-11-13
The trade designator shall consist of up to three alphabetical characters utilizing the following list:
The George Washington University BIM Manual | 1
Version 1.0 - February 2014
A / Architectural / PP / Plumbing PipeINT / Casework / MG / Lab Piping
EE / Electrical Equipment / CW / Curtainwall
LTS / Light Fixtures / PC / Precast
FA / Fire Alarm / PA / Metal Panels
FP / Fire Protection / S / Structure
MP / HVAC Mechanical Pipe / SPC / Special Items/Misc
MD / HVAC Mechanical Duct
The level shall be a two digit code (Customize for this project):