NEGOTIATED CONTRACTS ADDENDUM TO USC BIM GUIDELINES...

Architects - Ini al _______

General Contractor - Ini al _______

1 October 12, 2012 Addendum #1 to USC BIM Guidelines V1.6 dated April 18, 2012

Addendum for Negotiated Contracts | BIM Guidelines

NEGOTIATED

CONTRACTS

ADDENDUM TO USC BIM GUIDELINES VS. 1.6 ADDENDUM #2

Building Informa on Modeling (BIM) Guidelines V 1.6 (April 18,2012)

CIVIL GUIDELINES

USC Capital Construc on Development and Facili es Management Services

DRAFT March 18, 2014 June 18, 2014

2 November 22, 2013 Addendum #2 to USC BIM Guidelines V1.6 dated April 18, 2012

Addendum for Civil Works | BIM Guidelines

Table of Contents (for those items that have changed from V1.6 and

Addendum #1 only)

1 Introduction

1.1 STATEMENT OF PURPOSE

2 USC Responsibilities

USC CAPITAL CONSTRUCTION PROJECT MANAGER

USC BIM CONSULTANT FACILITATOR

3 Deliverables

3.2 MODEL AND DATA DELIVERY

3.3 DESIGN OF PROJECT TREE STRUCTURE

4 Design Team BIM Process and Modeling Requirements

4.2 GEO-REFERENCED MODELS

4.2.1 Survey Data

4.2.2 Shared Coordinate or Shared Site File

4.4 DESIGN BIM FACILITATOR

4.5 MODEL QUALITY AND LEVEL OF DETAIL: ARCHITECTURAL, MEPF and CIVIL

5 MEPF Specifications

5.1 SHARED PARAMETERS AND ASSOCIATED DOCUMENTS

APPENDIX A: Model Elements and Level of Detail

7. Civil Engineering



APPENDIX B: BIM DATA ACQUISITION GUIDELINES FOR FACILITIES MANAGEMENT

CIVIL 3D SPECIFICATIONS

USCSiteCode

USCEquipmentNumber

USCEMSId

OmniClassNumber

OmniClassTitle

UniformatNumber

MasterFormatNumber

UtilityOwner

UtilityStatus (Abandon, In Use…)

TypeName (cobie)

TypeDescription (cobie)

SystemName

InstanceName

InstanceDescription

APPENDIX F: Collision Detection and Design Review

Clash Detection

APPENDIX G: USC FMS Outline Schedule Data Specification

SITE UTILITIES (GENERAL)

SITE UTILITIES (SPECIFIC)

OTHER (NON-UTILITY RELATED)

UTILITY MANAGEMENT ATTRIBUTE MATRIX



The following are additions and/or changes from Vs. 1.6 of the BIM Guidelines and Addendum #1. All text in italic is an addition or revision, non-italicized text is reprinted verbatim from the original guidelines.

1. Introduction

1.1 STATEMENT OF PURPOSE

This document describes USC’s requirements for the production and use of Building Information Models (BIM) in the design, construction and maintenance of its facilities for negotiated contracts (GMAX, GMP) with early contractor involvement including civil scope of work including site utilities and topography.

This document shall be used in combination with the USC BIM Guidelines V1.6 (April 18, 2012) and Addendum #1 (October 12, 2012). The use of BIM for Civil work will allow for a fully integrated process including all site and building related activities.

The Civil models will provide the overall context for coordination between buildings, topography, site utilities, hard/landscaping and site furnishings. The goals of the civil component of the BIM are outlined below.

Civil BIM Goals:

Utilize Civil models and their BIM Data to facilitate and support the design and construction stages of a project.

Utilize Civil models and their BIM Data to support the operations and maintenance process.

Enhance BIM coordination between buildings and their surroundings

Support into USC’s GIS program



2. USC Responsibilities

USC Capital Construction Project Manager:

For each project the Project Manager will review and make the appropriate modifications to the civil model BIM scope of work as outlined in the BIM Execution Plan.

USC BIM Consultant Facilitator:

For each project the BIM consultant will assist and advise the Project Manager in reviewing and making the appropriate modifications to the building model BIM scope of work and the civil model BIM scope of work as outlined in the BIM Execution Plan.

3. Deliverables

3.2 MODEL AND DATA DELIVERY

a. Fully coordinated architectural, structural and MEP 3D models in Revit and civil models in Civil 3D at 100% CD by the Design Team.

d. Complete “as constructed” Revit or Civil 3D models provided by the Designers conforming to USC FMS requirements as detailed in Appendix B.



g. At the outset of each phase of work the Civil Engineering team shall participate in completing a MODEL DELIVERY SCHEDULE and APPLICATION AND FILE EXCHANGE TYPE table for the appropriate phase of work. (see Appendix 1 Section F.3 of the JBEP) This table establishes the frequency, location and format for coordination meetings and file exchanges.

This table shall be implemented with the following goals in mind:

Incorporate 3d model coordination between civil and building BIM

Facilitate work-in-progress design

Management of model ownership and model handoffs between consultants

Ability to facilitate and support BIM data in a variety of formats

Integrate detailed engineering knowledge into the models as early as possible to reduce future re-work of generic systems.

Recurring as opposed to one-time transactions of 3D models

Flexibility to manage evolving project work breakdown structure

3.3 Civil Model Organization

The Civil Models shall provide the context for the entire site and will interface with various building elements. They shall be structured in such a way as to both provide the engineering and appropriate documentation that is needed by the Engineering teams as well as provide context for coordination with building structures. Clarity of model structure will facilitate specific processes such as managing trade interfaces and other coordination needs. Please see Section I.2 of the JBEP. This appendix shall outline the specific consultant responsibilities for geometry and data entry of both Civil and Non Civil Site objects into the Civil Model.

Section I shall be updated at the beginning of each phase of work in accordance with the BIM Coordination Plan.

4. Design Team: BIM Process and Modeling Requirements

4.1 BIM AUTHORING SOFTWARE

The Architects, Structural Engineers and MEPF Designers shall model their systems in Revit. The Civil Engineer shall model their systems in Civil 3D.



4.2 Geo-Referenced Model

The Civil Engineer and Surveyor will collaborate with the architect to set the spatial coordinates at the beginning of the project. The coordinates will be geo‐referenced to a permanent campus monument. The monument chosen as the project reference point will be coordinated between the Civil Engineer, the surveyor, the Architects and USC. Jointly the Civil Engineers and the surveyor are responsibility to verify the accuracy of the coordinates.

4.2.1 Survey Data

The surveyor shall provide electronic files that clearly define the project site and include accurate x/y/z coordinates of all survey items. The files shall be in a format that allows for interoperability into the BIM models utilized by project consultants. The survey shall identify and represent all USC campus survey monuments within the project boundary. If less than three survey monuments are located within a project site the Survey will identify and represent the nearest three monuments. Survey points shall be coordinated between the Civil Engineer, the Architects and USC. The survey shall provide topographic data to support 3D modeling of the elements identified in Appendix A. Survey shall provide utility data to support 3D Modeling of elements identified in Appendix G Utility Attribute Matrix. In addition to this document Surveyor shall also cross reference their work with USC BOD Section 02 2100. These standards apply to both the initial project survey and post completion record surveys.

4.2.2 Shared Coordinate or Shared Site File

The architect and civil engineer shall be responsible for collaborating to produce and maintaining a Revit Shared Site File which is interoperable with the Civil 3D files. Coordination between the models shall be based on information provided by the Civil Engineer and the Architect. The architect and the civil engineer shall work together to synchronize a commonly agreed upon real world campus marker with the Revit model survey point and project base points. Detailed instructions defining Revit Shared Coordinate and Civil 3D set up, data transfer and file maintenance shall be included as an attachment under Section L of the Joint BEP.

4.4 DESIGN BIM FACILITATOR

k. Ensuring that the common reference point as established by the civil engineer is distributed and used by ALL team members at the beginning of design.



4.5 MODEL QUALITY AND LEVEL OF DETAIL: ARCHITECTURAL, MEPF and CIVIL

e. Surveys shall represent topography data as survey objects (points or contours) Provision of raw topographic data to the Civil Engineer from the Surveyor such as DTM or equivalent is encouraged.

5. MEPF & Civil Specifications

5.1.1 SHARED PARAMETERS

See Appendix B: MASTER ATTRIBUTES for required parameter fields for ALL MEPF and CIVIL system families.

5.5 POINT OF CONNECTION

The Design Team will define the point of connection in Section J of the BEP. This will be the point to which all underground building utilities shall be extended. In general the point of connection shall be representative of the scope of work of each consultant.

APPENDIX A: Model Elements and Level of Detail for Models

DESIGN DEVELOPMENT AND CONSTRUCTION DOCUMENTS

7. Civil Engineering

Model the following civil elements at a minimum. The detail and responsibility to fulfill these modeling requirements shall be addressed within the BIM Execution Plan.

The civil model will be separate from building models and shall be organized based on agreement with USC. At a minimum, models will be divided into two primary zones, site topography and site utilities.

Site Topography Model – 3D terrain of all site work as designed, including retaining walls and existing site work to remain as part of new design. Terrain surface shall be divided by materials for both visualization and data extraction. This model shall include the site and surrounding areas that contribute to the site’s drainage system or otherwise impact the site. The model shall include all surface parking as designed including a representation of the parking stalls. Unless otherwise stated in the JBEP Topography shall be modeled to the far edge of all public or private streets adjacent to the project. Landscaping elements include planting areas, such as raised planting beds and berms, parking islands, pools/ponds/other water features, terraces and



other items not included elsewhere in the model are to be included. Trees and representations of tree root balls and any other large clearances for planted items shall be included in the model. The trees may be highly simplified representations so as not to burden the overall model size.

Site Utilities Model - Includes existing and proposed site utilities by all utility operators. The model organization and attributes listed in Appendix B outline how utility owner and status will be identified. Existing and proposed utilities shall be extended to the centerline of the nearest adjacent street or to point agreed upon and documented in the JEP.

CONSTRUCTION COORDINATION

General Concepts

Layers within the scope of the building model shall be labeled as per the architectural drawings to identify the utilities.

Layers within the scope of the Civil Model shall be labeled as per the civil drawings to identify the utilities.

Each MEPF model shall be inclusive and contain all elements back to the point of connection. All utilities beyond the point of connection and within the project site shall be included in separate MEPF site utilities models. Project consultants shall detail site utility deliverables in Section J of the BEP.

12. Civil Model

Site Topography Model – see Appendix A Design Development and Construction Documents Item #7 for detailed requirements.

Site Utilities Model – see Appendix A Design Development and Construction Documents Item #7 for detailed requirements.

APPENDIX B: BIM DATA ACQUISITION GUIDELINES FOR FACILITIES

MANAGEMENT SERVICES

CIVIL 3D SPECIFICATIONS

1. Creating a property set definition



Access the Property Set Definitions through either the stylemanager or propertysetdefine commands. Right click on Property Set Definitions and select New. Enter the following information into the first two tabs.

Definition

Use the Add Manual Property Definition button and add the Extended Data Properties individually:

General Applies To Definition

Name: USC Shared Parameters

Objects: All Objects (This can be done quickly by choosing Select All)

USCSiteCode

USCEquipmentNumber

USCEMSId

OmniClassNumber

OmniClassTitle

UniformatNumber

MasterFormatNumber

UtilityOwner

UtilityStatus (Abandon, In Use…)



TypeName (cobie)

TypeDescription (cobie)

SystemName

InstanceName

InstanceDescription

2. Adding Extended Data

Entries can now be entered in the fields within the Extended Data tab.

APPENDIX C: Nomenclature

Civil 3D Blocks, Utilities and Topography Objects shall follow the same nomenclature logic as Revit Families. See Appendix C of the BIM Execution Plan for detail description.

For Civil 3D Native Network Objects: (Pipes, Structures ect…)

FAMILY NAME

Civil 3D – General: Network Name

INSTANCE NAME

Civil 3D – Information: Name or Description

TYPE NAME

Civil 3D –General: Style Name



For Custom Civil 3D objects that do not belong to an inherent Civil 3D Network the Extended Data Parameters will be used for the nomenclature convention.

APPENDIX F: Collision Detection and Design Review

Clash detection

Civil Utilities and their applicable Clearance vs Walls, Enclosures, Footings, Basements and other Building or Site Infrastructure Constructions.

Civil Utilities and their applicable Clearance vs Ground Surfaces

Civil Utilities and their applicable Clearance vs Hard/Landscaping

Civil Utilities and their applicable Clearance vs Building Points of Connection

Civil Utilities and there applicable Clearance vs MEPF Site Utilities

APPENDIX G: USC FMS Outline Schedule Data Specification

SITE UTILITIES (GENERAL)

a) Unique Identifier b) Center of Manhole/Vault Lid c) Bottom of Manhole/Vault d) Manhole/Vault Dimensions e) Center of Valve Lid f) Valve Type (Gate, Butterfly) g) Center of Clean-Out Lid h) Top of Pipe Depth (Main Lines 3" or Greater) i) Bottom of Pipe Depth (Invert) j) Pipe Inside Diameter k) Pipe Outside Diameter l) Pipe Material

FAMILY NAME

Civil 3D – Extended Data: SystemName

INSTANCE NAME

Civil 3D – Extended Data: InstanceName

TYPE NAME

Civil 3D – Extended Data: TypeName



m) Top of Encasement Depth n) Bottom of Encasement Depth (Invert) o) Encasement outside dimensions p) Encasement Material q) Underground Valve Locations r) Building Point of Entry s) Building Lateral Isolation Valve Locations t) Change in elevation (> 6" new invert outside vault) u) Date of Construction (by segment) v) Pipe Slope

SITE UTILITIES (SPECIFIC)

a) Voltage b) # of Conduits and Conduit Diameter c) # of Conductors (per conduit) d) Size of Conductors e) Conductor Material f) Cable Insulation Type (Rating / Thickness) g) Low voltage direct bury conduit outside diameter h) Low voltage direct bury conduit bottom depth i) Low voltage direct bury conduit top depth j) Lateral Connection Locations (3" or larger) k) Hydrant Location l) Hydrant Lateral Locations m) Hydrant Valve Locations n) Fire Water Backflow Device o) Irrigation Meter/Backflow p) Fountain Pump Equipment q) Gas Meter Location r) Catch Basin / Collection System Location s) Catch Basin / Collection System Dimensions t) Stormwater Mitigation System Dimensions u) Stormwater Mitigation System Depth v) Underground Interceptor Dimensions w) Underground Interceptor Depth x) Building Generator Location (if outside building) y) Building Transformer Location (if outside building) z) Medium Voltage Switch Gear (if outside building) aa) Normal Operating Pressure Range bb) Normal Operating Temperature Range

OTHER (NON-UTILITY RELATED)

a) Representative Tree Species



b) Tree Drip Lines c) Site Wall Footings d) Site Walls e) Light pole foundations f) Representative Light fixtures g) Security Camera Foundations h) Representative Security Camera i) Blue Phone Foundations j) Blue Phones k) Fence Footings l) Fence m) Mechanically Operable Gates n) Mechanically Operable Bollards o) Fountains p) Signpost Foundations q) Representative Sign Objects r) Miscellaneous Underground Structures

OTHER (TOPOGRAPHY)

a) Site Code b) Shape Length c) Shape Area d) Surface or Vegetation Type e) Install Date f) Condition g) Owned By h) Managed By i) Last Maintenance j) Last Editor

Note: Text within parenthesis following an item shall not be included as part of the item name in the data base. The extra information listed within parenthesis is meant to clarify they type of data being recorded.

NEGOTIATED CONTRACTS ADDENDUM TO USC BIM GUIDELINES...

Documents

Transcript of NEGOTIATED CONTRACTS ADDENDUM TO USC BIM GUIDELINES...