Building Information Modeling Manual - George … · Web viewProject Name BIM Project Execution...

Project NameBIM Project Execution Plan

ContentsContents______________________________________________________________________________2

General Overview of BIM Execution Plan________________________________________3Document Revision History___________________________________________________3Overview___________________________________________________________________4

A. Project Info_____________________________________________________________4B. Definitions_____________________________________________________________4C. Project Schedule________________________________________________________6D. BIM Execution Plan Timeline______________________________________________7E. Reference Points________________________________________________________7

Project Team_______________________________________________________________8A. Roles/Responsibilities____________________________________________________8B. Team Directory__________________________________________________________9

Project Specific Deliverables__________________________________________________9A. BIM Goals______________________________________________________________9B. BIM Uses_______________________________________________________________9C. Project Deliverables_____________________________________________________10

Design_______________________________________________________________________________10Construction__________________________________________________________________________11

Electronic Communications__________________________________________________11A. Software Requirements__________________________________________________11B. Electronic File Storage__________________________________________________12C. Information Exchange Schedule__________________________________________12E. Model Naming__________________________________________________________13F. Sheet View Naming_____________________________________________________14G. Trade Contractor Coordination File Naming_________________________________15

Collaboration Procedures____________________________________________________16A. Meetings______________________________________________________________16

Project Meetings_______________________________________________________________________16BIM Coordination Meetings______________________________________________________________17

B. Coordination Schedules_________________________________________________17Design_______________________________________________________________________________17Construction__________________________________________________________________________17

C. Quality Control________________________________________________________17Model Content Requirements_________________________________________________18

A. Model Content Progression______________________________________________18B. Embedded Data________________________________________________________18

Appendices________________________________________________________________19Appendix 1 - Model Progression Schedule____________________________________19

The George Washington University BIM Manual | 2 Version 1.0 - August 2014

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 HistoryAt 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 Updates

The 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 Name

GW Project Number

Project Location and Address

Brief Project Description

B. Definitions

AAiM AssetWorksFacility Management system utilized by GW to track all project assets and documents, including submittals, maintenance information, and warranties.

As-Built DrawingsPhysical 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 ModelDesign Model that has incorporated changes and updates throughout the construction process, including RFIs, bulletins, and field conditions.

AssetIndividual items incorporated into the construction of a project. For GW, information is collected by this for use as facility data.

B

BIM Project Execution PlanA document created utilizing GW’s provided template to define procedures and roles for the preparation of electronic media during the project.The George Washington University BIM Manual | 4 Version 1.0 - August 2014

BIS or BISMBuilding Information Systems Manager

C

Closeout DocumentsConsist 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.

COBieAn 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.

ContractorThe firm serving as lead builder for the project, working in the capacity of either General Contractor or Contractor.

Coordination ModelBIM 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.

DesignerThe firm serving as developer of the project documents, working in the capacity of Architect, Engineer, or Consultant.

.DWGFile 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: http://www.csinet.org/Home-Page-Category/Formats/MasterFormat/MF-use.aspx

N

.NWFFile type associated with a native Navisworks file.

O

OmniClassA 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 23Spreadsheet that contains the corresponding codes utilized in the BIM Model to categorize assets within GW’s facility management system.

P

Project CloseoutThe managed and orderly transition of the work from Substantial Completion to Final Payment, including the finalization of final paperwork.

Project TeamThe collective group of representatives from GW, the Designer, and Contractor.

R

.RVTFile type associated with a native AutoDesk Revit file. It is the deliverable file format for all projects.

S

Substantial CompletionEstablishes 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 Date


http://www.csinet.org/Home-Page-Category/Formats/MasterFormat/MF-use.aspx

D. 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 Turnover

Division 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 Responsibilities

A/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 Phone

Project 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 Uses

Design 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 table1. Insert any additional uses as applicable in the empty cells provided.

X Plan X Design X Construct X Operate

Programming Design Authoring Site Utilization Building 1 USACE Project Execution Plan Template, found at www.nationalbimstandard.orgThe George Washington University BIM Manual | 9 Version 1.0 - August 2014

Planning 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 ModelingMechanical

AnalysisOther Eng. Analysis

Sustainability (LEED) Evaluation

Code ValidationPhase Planning (4D Modeling)

Phase Planning (4D Modeling)



Cost Estimation Cost Estimation Cost Estimation Cost EstimationExisting Conditions

ModelingExisting Conditions



ModelingLegend: 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 Format

Programming Narrative .pdf

Schematic Design NarrativeDrawings

.pdf

.pdf

Design DevelopmentSpecificationsDrawingsDesign Model

.pdf

.pdf

.rvt

Construction DocumentsProject ManualDrawingsDesign Model

.pdf

.pdf

.rvtBid 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 Version

Architecture Design Architecture AutoCAD & Revit Architecture 2012 20110916_2132

Structure Design Structure AutoCAD & Revit Structure 2012 20110916_2315

HVAC Design HVACAutoCAD 2012 (Add-on) CADduct & CADmech

TSI Version: 21 2.41.157.SP4

Plumbing Design PlumbingAutoCAD 2012 (Add-on) CADduct & CADmech

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 HVACAutoCAD 2012(Add-on) CADduct & CADmech

TSI Version:212.41.157.SP4

Plumbing Fabrication PlumbingAutoCAD 2012(Add-on) CADduct & CADmech

TSI Version:212.41.157.SP4

Electrical Fabrication Electrical AutoCAD 2012 TBDThe George Washington University BIM Manual | 11 Version 1.0 - August 2014

(Add-on) CADelecFire 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

ProtectFile

Maintainer Updated

FTP siteftp://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 File Sender File Receiver One-Time or Due Date or The George Washington University BIM Manual | 12 Version 1.0 - August 2014

Exchange Frequency Start Date

Authoring – 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 shall define 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-1311456 Structure – R13 2013-11-1311456 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 StructuralE Electrical T Information Technology/TelecommunicationF Fire Protection & Fire Alarm V ElevatorsL Landscape X SecurityM Mechanical Z ZoningP 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 LightingME Mechanical Equipment FP Fire ProtectionPL Plumbing, Waste, and Vent CV Civil

The software version designator shall utilize the following list:

R13 Autodesk Revit 2013 R14 Autodesk Revit 2014

Reference 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:

A Architectural L Landscape


B Building Permits M MechanicalC Civil P PlumbingD Demolition Q Audio VisualE Electrical S StructuralF Fire Protection & Fire Alarm T Information Technology/TelecommunicationG General Notes/Information/Life Safety V ElevatorsI Interior Design X SecurityK Kitchen Equipment Z Zoning

The sheet sequence number shall consist of four numerical characters utilizing the following list:

0000 General (Symbols, Legends, Notes) 0500 Details

0100 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-1311456 E-03-D-SUB-3D-2013-11-13

The trade designator shall consist of up to three alphabetical characters utilizing the following list:

A Architectural PP Plumbing PipeINT Casework MG Lab PipingEE Electrical Equipment CW CurtainwallLTS Light Fixtures PC PrecastFA Fire Alarm PA Metal PanelsFP Fire Protection S StructureMP HVAC Mechanical Pipe SPC Special Items/MiscMD HVAC Mechanical Duct

The level shall be a two digit code (Customize for this project):


01 Level 1 02 Level 203 Level 3 04 Level 4

The area shall consist of one alphabetic character utilizing the following list (Customize for this project):

A [Name] B [Name]C [Name] D [Name]

The phase code shall utilize one of the following choices:

DSN Documentation generated from design models SUB Documentation generated from trade models

The type code shall utilize one of the following choices:

2D 2-dimensional drawing documentation 3D 3-dimensional drawing documentation

Reference date formatting shall be 4-digit year [-] 2-digit month [-] 2-digit day

The Contractor shall require subcontractors, fabricators, suppliers, and manufactures to submit all models to the contractor in both an .NWD (Navisworks) format and an .RVT (AutoDesk Revit) format. These models should be updated after each project coordination meeting or as changes occur in the field during construction.

Collaboration Procedures

A. Meetings

Project Meetings

In the table below, define the type of meetings held during the project, including coordination meetings, owner updates, progress meetings, etc. Indicate the required attendees and scope of the meeting.

Meeting Type Phase Frequency Participants Location

BIM Coordination Meetings

In the table below, define the type and frequency of meetings related to BIM Coordination. Indicate the required attendees and scope of the meetings.


Meeting Type Phase Frequency Participants Location

B. Coordination Schedules

Outline the deliverables required and the anticipated date for completion.

Design

Deliverable Date

Construction

Deliverable Date

C. Quality Control

The following checks should be performed in the BIM models to assure quality:

Checks Definition Responsible Party

Software Program(s) Frequency

Visual CheckEnsure there are no unintended model components and the design intent has been followed

All Navisworks, Revit Weekly

Interference Check

Detect programs in the model where any building components are clashing including hard and

All Navisworks, Revit

Weekly


soft

Standards Check

Ensure that the BIM modeling standards have been followed (Refer to GW BIM Procedures Manual)


Model Integrity Checks

Describe the QC validation process used to ensure that the Project Facility Data set has no undefined, incorrectly defined, or duplicated elements and the reporting process on non-compliant elements and corrective action plans


Model Content Requirements

A. Model Content Progression

Refer to GW BIM Manual for minimum model element standards under LOD Definition. It indicates the minimum standards required by project deliverable. Project team shall develop a model progression table utilizing the template provided to expand the detail.

Model progression table has been provided in a Microsoft Excel format for editing in Appendix 1. Attach a version of this to the BIM Project Execution Plan.

B. Embedded Data

No embedded data is required by GW at this time.

Teams may desire to utilize embedded data. If desired, include this information below:


Appendices

Appendix 1 - Model Progression Schedule


Building Information Modeling Manual - George … · Web viewProject Name BIM Project Execution...

Documents

Transcript of Building Information Modeling Manual - George … · Web viewProject Name BIM Project Execution...