<PROJECT NAME>

BIM PROTOCOL MANUAL BIM STANDARDS AND PROTOCOLS

<DATE>

<PROJECT> DATE

[CONTENTS]

1. INTRODUCTION 1.1. PURPOSE 1.2. PROJECT TEAM 1.3. TEAM ROLE PLAYERS 1.4. STANDARD DIGITAL TOOLS 1.5. MODEL SPLITTING/LINKING

2. SCOPE OF MODELING

2.1. INTENT OF THE MODEL(S) 2.2. EXTENT OF MODELED ELEMENTS 2.3. MODELING REQUIREMENTS & LEVEL OF

DEVELOPMENT

3. MODELING PROCESS 3.1. DATA FLOWS 3.2. DATA SHARING 3.3. IMPORTING / EXPORTING

4. CREDITS/ BIBLIOGRAPHY

<PROJECT> DATE

[1 INTRODUCTION] 1.1 PURPOSE The intent of the BIM Protocol Manual for the <Project> is to provide a unified focus for the utilization of BIM and related technologies specific to this project team. It will provide a roadmap for workflows and processes specific to this project and during each phase of project design and documentation, as well as during construction. It also establishes a minimum baseline for the team’s utilization of BIM and its advantages to facilitate project development.

Further description of ASG’s Documentation Standards and general BIM Protocols are defined in our Manual of Studio Standards. This will be distributed at the outset of each project.

1.2 PROJECT TEAM

DESIGN TEAM PROJECT ROLE SOFTWARE A/S/G Architects Architect of Record Revit 2016 Xxxxxx Lab Planner Revit 2016 CONSTRUCTION TEAM Xxxxx Contracting

Civil Engineers Structural Engineers MEP Engineers Code Consultants Audiovisual / Technology Lighting Design Lighting Design Consultants PROJECT ROLE Construction Manager

Civil3D 2016 Revit 2016 Revit 2016 Revit 2016 Revit 2016 SOFTWARE Navisworks 2016

1.3 TEAM ROLE PLAYERS

FIRM MODEL MANAGER / BIM EXPERT A/S/G Architects <Consultant>

Xxxxxx & Xxxxxx Xxxxxx & Xxxxxx

<PROJECT> DATE

1.4 STANDARD DIGITAL TOOLS ASG utilizes several software tools that will assist and enhance our development and handover of projects. These tools are listed below, and are appropriate and approved for use on this project.

Autodesk Navisworks Manage Coordination + Clash Detection 2016 Revit Design + Documentation 2016 Autodesk 3D Studio Max Visualization 2016 Lumion Walkthroughs + Client Interaction Autodesk Inventor Detailed Component Modeling 2016 Sketchup Massing Studies

1.5 MODEL SPLITTING / LINKING It has become standard industry practice to develop a comprehensive project model as a combination of several model files divided by discipline. Further, given the size and complexity of this specific project, it is expected that the models will be further broken down by building, as described below.

FIRM MODEL SUBDIVISION A/S/G Architects Xxxxxx & Xxxxxx <Consultant> Xxxxxx & Xxxxxx

<PROJECT> DATE

[2 SCOPE OF MODELING] 2.1 INTENT OF THE MODEL It is the intent of the design team to develop and deliver a technically accurate virtual model of the new facility for the <Project>. A higher level of accuracy and development will ultimately allow for greater project success during construction and occupancy. Included in the BIM deliverable will be existing and proposed topography, below grade utilities, building structure, parking garage, detailed architectural envelope and interiors, mechanical and users’ equipment, duct distribution, air devices, plumbing systems and major electrical systems. 2.2 EXTENTS OF MODELED ELEMENTS The plan extents of modeled elements shall extend to adjacent streets in order to portray utility infrastructure, and include simple masses of neighboring buildings for analyzing site access, solar shading, pedestrian, etc. The vertical extents will include modeled foundation components and utilities up to the highest point of vertical space and mechanical equipment. 2.3 MODELING REQUIREMENTS & LEVEL OF DEVELOPMENT The level of model development defined below will be required by the project team by phase, and for final deliverable. While there may be capability to deliver an even greater level of model development, that high level of detail should only be provided when necessary to convey design intent or for coordination in very complex areas. All modeled components shall be modeled as dimensionally accurate, but can be generic in nature, given the nature of product acquisition during construction. [Should be reviewed / agreed-upon after initial BIM Kick-Off meeting with consultant team] MODEL ELEMENTS

MODEL/DRAFT

PHASE DESCRIPTION

GENERAL Architectural Model will not contain items in 3D that would not be shown on drawings of less than 1/8” = 1’-0” Scale

CORE / SHELL Model SD DD

Enclosure walls: Heights and Thickness Thermal and Material properties

Model SD Doors (hardware – parameter, NOT MODELED) Model SD Windows – Mullion size/profile, glass thickness Model SD

DD Railings Post / Picket spacing + material

Model SD Structural roof slab

Model DD Tapered roof surface (Coord w/ parapet / door heights)

Draft CD Roof davits/walking pads

Model SD Floor Slabs – curbs/depressions - (shifts to S model in DD)

Model SD Shear walls (shifts to S model in DD)

<PROJECT> DATE

Model SD Non-Structural walls

Model SD Columns (shifts to S model in DD)

Model DD Soffits – Horizontal/vertical

INTERIOR WALLS

Model SD Overall thickness & Height (DD)

Draft CD Wall base

VAR DD Finish – 3D if thickness is necessary – joints/reveals – 2D

STAIRS Model SD Treads/risers/stringers

Handrails/guardrails

CEILINGS Height and thickness

Joints/reveals/lay-in grids

Soffits

Grills/diffusers

DOORS/ WINDOWS

Frames

Door thickness

Sidelights / door glazing

Hoistway doors

Elevator Cab / counterweights/ motor

CASEWORK Fixed Casework/shelving: Size, location, doors, drawers

(Hardware, to be in 2D)

FF&E Size/location

Finish – Parameter only unless needed for imagery

FIRE PROTECTION

Draft Sprinkler heads

Model FEC / FHV – Simplified family

MECHANICAL / ELECTRICAL / PLUMBING / FIRE PROTECTION MODEL / AV+IT MECH MODEL ELEMENTS

MODEL/DRAFT

PHASE DESCRIPTION

GENERAL The project will be modeled in Revit. There will not be a dual Autocad/Revit plan development. Revit documentation will begin in the schematic design phase. The MEP systems design will be coordinated internally and with outside design team members by employing clash detection workflows. Navisworks will be used

<PROJECT> DATE

extensively for clash detection and general coordination by the design team, led by the architect.

AIR DISTRIB. / PIPING

Model SD Ducts – using their outermost dimensions incl. insulation.

Model DD Piping – including insulation (greater than 2” dia) N/A Supports/seismic bracing/hangers/straps Model DD Diffusers/Grills (Modeled in M model, copy/monitor in A model) DIAGRAMS Draft DD Riser diagrams EQUIPMENT Data DD Built-in Intelligence – parameters utilized to analyze

cooling, heating, electrical loads SD Size and Location DD Maintenance / Clearance Zones

(built into equipment family) ELECTRICAL ELEMENTS

MAJOR EQUIPMENT

Model DD Bus ducts, Feeders 2” or greater dia., Pull boxes – 3D

DISTRIBUTION PATHWAYS

Model CD Conduits – 2” or larger

DEVICES Model CD Switches, Floor Boxes, strobes / Horns

BRANCH CIRCUITING

DRAFT DD

LIGHTING FIXTURES

MODEL DD Location/height/type (Modeled in E model, copy/Monitor in A model)

TELECOM ELEMENTS

INFRASTRUCTURE

Model CD Cable trays, metallic raceways, sleeves greater than 2” dia

Model CD Voice/data telecom outlet devices

Draft CD Horizontal station cabling or backbone cabling

AV + SECURITY

Model CD Cameras

Model DD Displays, Projectors, Screens, Wall Mounted Input Devices (CD)

Draft CD Circuiting, Card Readers

PLUMBING ELEMENTS

PIPING / EQUIPMENT

Model DD Piping greater than 1 ½”

N/A Supports/Seismic bracing/hangers/straps

Draft DD Riser Diagrams

FIRE PROTECTION

Model DD Primary system components, FD connections, fire pump,

<PROJECT> DATE

Standpipe

N/A Sprinkler branch piping

STRUCTURE ELEMENTS

BEAMS Model DD Steel beams shall be modeled at the required Top-of-Steel elevations. Model at the intended locations in plan using accurate sectional dimensions. Major penetrations in the beam web are modeled. Small openings required in beam web are not modeled. Beam end connections, stiffeners, beam bottom flange braces are fabrication details and are not modeled.

COLUMNS Model SD with required top and bottom elevations

BRACES & MISC STEEL

Model DD Seismic bracing for the building

Draft Minor kicker braces, gusset plates, hangers, misc metals

ROOF AND FLOOR SLAB

Model DD Copy / Monitor from A model. S model takes precedence in CD’s

Model DD Major mechanical shafts and elevator shafts

Model CD Slab depressions

Draft CD Housekeeping pads

Foundations Model DD Foundation elements, slab on grades, grade beams, mat slabs, piles etc

Draft CD Reinforcing

WALLS Model DD Basement structural concrete walls

Model CD Openings in structural walls

Draft CD Minor openings required for pipe penetrations, etc (less than 4” in diameter)

SITE FEATURES

Model CD Site landscape walls and/or retaining walls

STAIR STRINGERS

Draft DD Stair stringers for typical stairs

Model DD Stringers for complex stair geometries

<PROJECT> DATE

[3 PROJECT BIM MANAGEMENT] The following sections define the methodologies to be used in the sharing of information and modeled content. These processes will aid in streamlining the flow of data, as well as providing a clear avenue through which information and revisions can be shared, and how decisions can be more effectively made. 3.1 Project Model Management – Design Phases The diagram below illustrates key players in the flow of BIM data, as well as generalized timeframes for certain project actions during design and documentation.

<PROJECT> DATE

3.2 Project Model Management – Construction The diagram below illustrates Model Management responsibilities during construction.

<PROJECT> DATE

3.3 BUILDING COORDINATION, DATA REVIEW, AND CLASH DETECTION

• Beginning at 50% DD Phase, the design team shall review the combined model using Navisworks Manage, which will allow visual reviews of the models and to perform detailed clash detections.

• During Bi-Weekly BIM Coordination meetings, individual areas targeted for coordination should not be larger than approximately 20,000 SF. This will allows the number of clashes to remain at a manageable level to coordinate the area efficiently.

• Individual areas should be kept to a single floor during a review session. This allows the number of clashes to remain manageable to not only coordinate the area efficiently, but also allow for quick understanding of the areas of concern.

• ASG and consultants will review each other’s data and communicate changes or discrepancies using Autodesk Design Review or Bluebeam. Marked-up DWFs or PDF’s will be distributed via Newforma Info Exchange as necessary.

Clash Detection Reports will be issued subsequent to each BIM Coordination meeting in Excel and PDF formats for review. These reports will include a thumbnail image of the clash, an element ID number, location of the clash by level and grid, and comments and to whom the responsibility has been assigned.

3.4 Data Sharing In order to help ensure that information is passed back and forth between team members in an efficient and predictable way, it is important to define the manner and schedule in which those exchanges are to happen. As a general standard, it is the intent of the Project Team to post progress updates (during the design phase) to the project team via Newforma Info Exchange. The frequency will be variable, depending on extent of changes, but typically it will follow this schedule:

• During SD and DD: Weekly

• During CD’s: Bi-weekly.

• During Construction: Monthly, depending on frequency of model revisions and utilization of modeled content by the CM.

During times of intense activity it can be expected that frequent coordination updates will be necessary to meet project milestones and deadlines. In addition to posting the BIM data, it will be necessary to also post PDF versions of the information that will also be generated for the project. Bluebeam and Newforma allow sheets to be overlaid on each other to quickly locate revisions.

A. Distributing Information via Newforma Info Exchange

1. Design review and coordination PDFs shall be posted via Newforma Info Exchange as necessary to communicate between team members.

2. E-mail notification to the lead project manager for each member of the Project Team should be sent at the time the information is posted.

<PROJECT> DATE

B. BIM Information Exchange

1. A substantial amount of background work has been done to understand both the overall process and the details of how information gets exchanged between members of the Project Team. This covers not only Revit to Revit file exchanges, but for various other software currently anticipated for use on the project. Below is a review of the specifics associated with each exchange type.

3.4.1 Importing and Exporting Procedures

This section will deal with procedures for software importing, exporting, and orientation. Following are sections for each software application proposed to be utilized by the consultant team.

DWG to REVIT

• On the project browser expand floor plans and double click on Site to make it the active view.

• Go to the File menu and scroll down to Import/Link and select CAD Format.

• Use the following parameters:

o Determining whether to Import or Link:

! Check Link if this background is still being developed.

o Scaling:

! Choose Feet for drawings with decimal units in feet like in civil drawings.

! Choose Inches for all other drawings.

o Positioning:

! Check Automatically Place and Origin to Origin

• Click Open.

Sharing Coordinates in Revit

ASG will develop a Revit template with correct elevation (z-coordinate) established based on project site origin locator (x/y coordinate). When first establishing links with the architectural model, it is important to follow these steps so that files link in the correct location, and so that they export to Navisworks with expected outcomes.

<PROJECT> DATE

Shared Coordinates:

At the outset of the project, the Project Team will establish an origin point that will be associated with a known benchmark or location in the vicinity of the project. It is important to coordinate this point early with the civil engineer so that the Revit models link easily together and reference the same coordinate system.

It is expected that members of the Project Team will incorporate this same origin, which will establish relative locations and floor levels.

<PROJECT> DATE

[4 CREDITS / BIBLIOGRAPHY] Authored and Compiled by: Andrew Watkins, AIA

Associate Principal