Attachment 29 - Project BIM Execution Plan.pdf

APPENDIX 3

Project BIM Execution Plan

USACE ADVANCED MODELING PROJECT EXECUTION PLAN TEMPLATE - VERSION 4.0

USACE ADVANCED MODELING

PROJECT EXECUTION PLAN

(PxP) – V4.0

TRANSMITTAL NO: N/A

FOR

HINES VAMC

DESIGN – ELECTRONIC HEALTH RECORD

MODERNIZATION (EHRM)

INFRASTRUCTURE UPGRADES

HINES, IL

USACE CONTRACT NUMBER: 36C77621C0075

578-21-701

05-31-2023

DEVELOPED BY

Specialized Engineering Solutions

VA Hines EHRM Infrastructure Upgrades May 31, 2023

USACE ADVANCED MODELING PROJECT EXECUTION PLAN

TEMPLATE - VERSION 4.0

ii

INSTRUCTIONS AND REFERENCE INFORMATION

This template is a tool that is provided to assist in the development of an Advanced Modeling Project Execution Plan

(PxP) as required per Awarded Contract or Proposal Submission Requirements, or for use on a USACE District In-house design project. It was adapted from the United States National BIM Standard (NBIMS–USTM)1. For Reference

Information needed to complete content in this template, such as Model Use definitions, see the NBIMS–USTM Chapter

5 Practice Documents and related Section 5.3 BIM Project Execution Planning Guide at www.nationalbimstandard.org.

The U.S. Army Corps of Engineers is an Alliance Sponsor Member of the National Institute of Building Sciences (NIBS) http://www.nibs.org. NBIMS–USTM is a product of the buildingSMARTalliance® (bSa) which serves as a Council of

NIBS http://www.nibs.org/?page=bsa.

Bracketed GRAY TEXT is to be modified as needed to document the project. If modified, the format of the text should be changed to match the rest of the document. This can be completed, in most cases, by selecting the Normal Style in the template styles. Contractor shall not delete any sections or paragraphs. If a section or paragraph is not applicable to the project, mark it as such.

The terms ‘Organization’ and ‘Submitter’ can refer to a USACE in-house design team, other government entity, contractor or company.

If the PxP is being developed by USACE personnel for an in-house design project, instructions or references to a

Contractor are applicable to the USACE Project Delivery Team.

Questions pertaining to an individual solicitation shall be directed to the advertising District's Contracting Specialist for that Solicitation.

TABLE OF CONTENTS

SECTION 1: PROJECT INFORMATION

SECTION 2: KEY PROJECT CONTACTS

SECTION 3: PROJECT MODEL USES

SECTION 4: ORGANIZATIONAL ROLES / STAFFING

SECTION 5: ADVANCED MODELING PROCESS DESIGN

SECTION 6: MINIMUM MODELING AND DATA REQUIREMENTS

SECTION 7: COLLABORATION PROCEDURES

SECTION 8: QUALITY CONTROL

SECTION 9: TECHNOLOGICAL INFRASTRUCTURE NEEDS

SECTION 10: ADVANCED MODELING ORGANIZATION

SECTION 11: PROJECT DELIVERABLES

SECTION 12: GEOGRAPHIC INFORMATION SYSTEM (GIS)

SECTION 13: GOVERNMENT FURNISHED MATERIAL (GFM)

SECTION 14: ATTACHMENTS

SECTION 15: TEMPLATE CHANGE LOG

1 Version 3, Section 5.4 BIM Project Execution Plan Content – Version 2.1, BIM Project Execution Plan Template.

http://www.nationalbimstandard.org/ http://www.nibs.org/ http://www.nibs.org/?page=bsa

SECTION 1: PROJECT INFORMATION

To successfully execute Advanced Modeling requirements on a project, Specialized Engineering Solutions has developed this detailed Advanced Modeling PxP. The PxP defines Project Model Uses on the project, along with detailed processes for executing Advanced Modeling requirements and options on this project.

1.1 PROJECT INFORMATION

1.2 BRIEF PROJECT DESCRIPTION

The goal for this project will be to modernize the Hines Campus OIT infrastructure in order to accommodate current electronic medical records infrastructure and OIT needs.

1.3 ADDITIONAL PROJECT INFORMATION

Other important aspects of this project include developing redundant electrical and mechanical infrastructure to support OIT spaces as well as the development of the new OIT spaces.

1.4 ADVANCED MODELING GOALS

ADVANCED MODELING GOALS

PRIORITY GOAL DESCRIPTION PROJECT MODEL USES

HIGH New architectural model contents and general elements.

COORDINATION AND

LOCATION OF NEW

WORK

HIGH

New Mechanical, Electrical, and Telecommunications model contents and general elements.

COORDINATION AND

LOCATION OF NEW

WORK

HIGH New Cable Tray routes and Low Voltage pathways.

COORDINATION AND

LOCATION OF NEW

WORK

HIGH New Site Topography and new Low Voltage routes on site.

COORDINATION AND

LOCATION OF NEW

WORK

PROJECT INFORMATION NUMBER / DESCRIPTION

FACILITY OWNER HINES VAMC

PROJECT TITLE

DESIGN – ELECTRONIC HEALTH RECORD MODERNIZATION

(EHRM) INFRASTRUCTURE UPGRADES

PROJECT LOCATION HINES, IL

USACE CONTRACT NUMBER 36C77621C0075

CONTRACT TASK ORDER N/A

PROJECT NUMBER (PN) 578-21-701

OTHER AGENCY PROJECT CODE(S) N/A

CONTRACT DELIVERY METHOD DESIGN-BID-BUILD

CONTRACTOR INFORMATION NUMBER

PROJECT CONTRACTOR SPECIALIZED ENGINEERING SOLUTIONS

CONTRACTOR PROJECT NUMBER(S) 21081

CONTRACTOR PROJECT CODE(S) N/A

1.5 PROJECT PxP CHANGE LOG

If any items in an approved PxP are required by an organization to be changed during the course of the project, consult with the District BIM/CIM Manager or Delegate to determine if a resubmittal of the PxP is required. If a resubmittal is required, all changes to the approved PxP are to be logged below providing a date, section number and brief description of each change.

PROJECT PxP CHANGE LOG

DATE SECTION DESCRIPTION

SECTION 2: KEY PROJECT CONTACTS

The following are lists of the Key Project Contacts for modeling activities of each organization on the project. As needed, additional contacts can be included later. The roles currently shaded in red are required by USACE.

2.1 USACE / AGENT CONTACTS

USACE/AGENT ROLE ORGANIZATION NAME EMAIL

TIME

ZONE

PHONE

PROJECT MANAGER VA

DISTRICT BIM/CIM

MANAGER

N/A

2.2 CONTRACTOR CONTACTS FOR ADVANCED MODELING ACTIVITIES

Discipline Advanced Modeling Leads are assigned for each discipline identified in the Section 6.1, ‘M3: Attachment 3, Tab 3’ as being included in the project (Elements in the M3 Tab ‘03. Scope-LOD-Grade’ are marked ‘Yes’), and others as required.

CONTRACTOR ROLE ORGANIZATION NAME EMAIL

TIME

ZONE

PHONE

PROJECT MANAGER

Specialized Engineering

Solutions Jeremy Klima jklima@specialized eng.com

Mountain 308-284-7323

PROJECT MANAGER

Specialized Engineering

Solutions Kris Burnham kburnham@speciali zedeng.com

Central 402-991-5520

PROJECT MANAGER

Specialized Engineering

Solutions Brad Carne bcarne@specialized eng.com

Central 402-991-5520

PROJECT MANAGER

Specialized Engineering

Solutions Tony Pabon tpabon@specialize deng.com Central 402-991-5520

BIM/CIM MANAGER

Specialized Engineering

Solutions Andrea Alderton aalderton@specializ edeng.com

Central 402-991-5520

ARCHITECTURE /

INTERIORS LEAD

Guidon Erin Sikorski esikorski@guidonde sign.com Eastern 417-522-5618

ARCHITECTURE PROJECT

MANAGER

Guidon Luke Leising luke@guidondesign

.com Eastern 317-800-6388

CIVIL / SURVEY /

MAPPING LEAD

Guidon Stacey Paul spaul@guidondesig n.com Eastern 317-800-6388

CIVIL / SURVEY /

MAPPING LEAD

Guidon David Marquardt dmarquardt@guido ndesign.com Central 317-800-6388

ELECTRICAL LEAD IMEG Mike Daley Michael.k.daley@im egcorp.com Central 314-951-2529

TELECOM LEAD IMEG Dave Larson david.l.larson@ime gcorp.com Central 314-951-2529

TELECOM LEAD IMEG Joe Kowols joe.f.kowols@imegc orp.com Central 314-951-2529

TELECOM LEAD

Specialized Engineering

Solutions Nate Timm ntimm@specialized eng.com

Central 402-991-5520

FIRE PROTECTION LEAD

Specialized Engineering

Solutions Dellan Llewellyn dellan.j.llewellyn@i megcorp.com

Central 402-991-2529

HAZARDOUS MATERIALS

LEAD

TTL Harry Singh hsingh@ttlassoc.co m Eastern 419-214-5058 mailto:jklima@specializedeng.com mailto:jklima@specializedeng.com mailto:kburnham@specializedeng.com mailto:kburnham@specializedeng.com mailto:bcarne@specializedeng.com mailto:bcarne@specializedeng.com mailto:tpabon@specializedeng.com mailto:tpabon@specializedeng.com mailto:aalderton@specializedeng.com mailto:aalderton@specializedeng.com mailto:luke@guidondesign.com mailto:luke@guidondesign.com mailto:spaul@guidondesign.com mailto:spaul@guidondesign.com mailto:dmarquardt@guidondesign.com mailto:dmarquardt@guidondesign.com mailto:gregory.j.lyford@imegcorp.com mailto:gregory.j.lyford@imegcorp.com mailto:david.l.larson@imegcorp.com mailto:david.l.larson@imegcorp.com mailto:joe.f.kowols@imegcorp.com mailto:joe.f.kowols@imegcorp.com mailto:ntimm@specializedeng.com mailto:ntimm@specializedeng.com mailto:jmartin@specializedeng.com mailto:jmartin@specializedeng.com mailto:hsingh@ttlassoc.com mailto:hsingh@ttlassoc.com

MECHANICAL (HVAC)

LEAD

Specialized Engineering Solutions

John Martin jmartin@specialized eng.com Central 402-991-5520

SPECIALITY

CONSULTANTS

OCMI Kyle Veater kveater@ocmi.com Eastern 202-229-0530 mailto:jmartin@specializedeng.com mailto:jmartin@specializedeng.com mailto:kveater@ocmi.com

SECTION 3: PROJECT MODEL USES

3.1. MANDATORY MODEL USES

The Model Uses in Section 3.3 shaded in red and identified with an (X) must remain as MANDATORY Model Uses on the project. Reference the BIM Project Execution Planning Guide at www.nationalbimstandard.org for descriptions of Model Uses.

3.2. ELECTIVE MODEL USES (NON-CONTRACTUAL / INNOVATIVE MODEL USES) – Not Applicable

As supplementary to the Mandatory Model Uses in Section 3.3, Contractor may choose to implement Elective

Model Uses (Non-Contractual / Innovative Model Uses) either through identifying non-mandatory Model Uses as electives or adding Contractor-developed innovative Model Uses. This option provides the Contractor with two benefits; a method to attempt non-mandatory Model Uses without fear of negative consequences if the execution does not go as planned, and also a method to demonstrate to USACE Model Uses that have been executed well.

All submitted Elective Model Use content is considered non-contractual in nature and will not be negatively evaluated or critiqued by USACE, but MUST be properly documented in Sections 3.2.a, b and c.

a. Provide in the table below a ‘Process Description and Added-Value’ for each Elective Model Use chosen or developed for the project.

b. All Elective Model Uses are to be identified with an (E) in Section 3.3 in the Design or Construct columns only. Do not identify or add Elective Model Uses in the Plan or Operate columns.

c. Provide information in Section 11.2 concerning any related submittals. Submittals may be submitted as

‘For Information Only’.

ELECTIVE MODEL USE PROCESS DESCRIPTION and ADDED-VALUE

[ELECTIVE MODEL USE] [DESCRIPTION]

3.3. PROJECT MODEL USES

Project Model Uses are the combination of ‘Mandatory Model Uses’ in Section 3.1 and the ‘Elective Model Uses’ in Section 3.2, and identified in the table below.

3.4. INTEGRATION OF PROJECT MODEL USES IN OTHER SECTIONS

All Project Model Uses identified in Section 3.3 are to be integrated into the following Sections as well. All Elective

Model Use content provided is considered non-contractual in nature and will not be negatively evaluated or critiqued by USACE, but MUST be properly documented in Sections 3.2.a, b and c.

4.1 DESIGN PHASE PROJECT MODEL USE 8.2 QUALITY CONTROL CHECKS

4.2 CONSTRUCTION PHASE PROJECT MODEL USE 9.1 DESIGN PHASE SOFTWARE

5.1

LEVEL ONE - PROCESS OVERVIEW MAP:

ATTACHMENT 1

9.2 CONSTRUCTION PHASE SOFTWARE

5.2

LEVEL TWO - DETAILED PROCESS MAPS:

ATTACHMENT 2

11.2

PROJECT DELIVERABLES FOR ELECTIVE MODEL

USES

PROJECT MODEL USES

PLAN

(NOT IN CONTRACT)

DESIGN CONSTRUCT

OPERATE

(NOT IN CONTRACT)

PROGRAMMING X DESIGN AUTHORING SITE UTILIZATION PLANNING BUILDING SYSTEM ANALYSIS

SITE ANALYSIS X PROGRESS REVIEWS

CONSTRUCTION SYSTEM

DESIGN

ASSET MANAGEMENT

X

INTERFERENCE

MANAGEMENT

(3D COORDINATION)

X

INTERFERENCE MANAGEMENT

(3D COORDINATION)

SPACE MANAGEMENT /

TRACKING

STRUCTURAL ANALYSIS DIGITAL FABRICATION DISASTER PLANNING

LIGHTING ANALYSIS

3D CONTROL AND PLANNING

(DIGITAL LAYOUT)

ENERGY ANALYSIS X RECORD MODELING

OPERATION & MAINTENANCE

RECORD MODELING

PROGRAM VALIDATION FIELD / MATERIAL TRACKING

MECHANICAL ANALYSIS PROGRAM VERIFICATION

OTHER ENG. ANALYSIS

SUSTAINABILITY (LEED)

EVALUATION

CODE VALIDATION

PHASE PLANNING (4D)

PRELIMINARY

CONSTRUCTION SCHEDULING

(4D)

CONSTRUCTION SCHEDULING

(4D)

BUILDING MAINTENANCE

SCHEDULING (4D)

COST ESTIMATION (5D) COST ESTIMATION (5D) COST ESTIMATION (5D) COST ESTIMATION (5D)

EXISTING CONDITIONS

MODELING

EXISTING CONDITIONS

MODELING

EXISTING CONDITIONS

MODELING

EXISTING CONDITIONS

MODELING

FACILITY DATA EXCHANGE

(FDE)

FACILITY DATA EXCHANGE

(FDE)

FACILITY DATA EXCHANGE

(FDE)

FACILITY DATA EXCHANGE

(FDE)

LEGENDEL U

X MANDATORY MODEL USE

E ELECTIVE MODEL USE

SECTION 4: ORGANIZATIONAL ROLES / STAFFING

For each Project Model Use identified in Section 3.3, noting each applicable Contractor on the Team, identify the organization (or organizations) responsible for staffing and implementation. Staff members may fill multiple project roles.

4.1. DESIGN PHASE PROJECT MODEL USES

DESIGN PHASE

MODEL USE

ORGANIZATION OFFICE LOCATION(S) LEAD CONTACT

DESIGN AUTHORING

GUIDON

SES

IMEG

TTL

INDIANAPOLIS

OMAHA

CHICAGO

DETROIT

LUKE LEISING

JEREMY KLIMA

DAVE LARSON

HARRY SINGH

PROGRESS REVIEWS

GUIDON

SES

IMEG

ANDERSON

SECONDARY REVIEW

ARCH

IMEG SECONDARY

REVIEW MEPT

INDIANAPOLIS

OMAHA

CHICAGO

ST. LOUIS

CHICAGO

LUKE LEISING

JEREMY KLIMA

DAVE LARSON

TOM OLESAK

DAVE LARSON

INTERFERENCE MANAGEMENT

(3D COORDINATION) – NEW

CONSTRUCTION ONLY

GUIDON

SES

IMEG

INDIANAPOLIS

OMAHA

CHICAGO

LUKE LEISING

JEREMY KLIMA

DAVE LARSON

4.2. CONSTRUCTION PHASE PROJECT MODEL USES

CONSTRUCTION PHASE

MODEL USE

ORGANIZATION OFFICE LOCATION(S) LEAD CONTACT

INTERFERENCE MANAGEMENT

(3D COORDINATION)

UNKNOWN N/A

RECORD MODELING

GUIDON

SES

IMEG

INDIANAPOLIS

OMAHA

CHICAGO

LUKE LEISING

JEREMY KLIMA

DAVE LARSON

SECTION 5: ADVANCED MODELING PROCESS DESIGN

Provide a Process Overview Map and Detailed Process Maps that demonstrate how all Project Model Uses identified in Section 3.3 will be implemented. Sample Process Maps may be downloaded from www.nationalbimstandard.org.

Sample maps should be modified based on project information and requirements, and internal procedures and processes. Use the Process Maps format for all Project Model Uses.

All Process Maps are to incorporate each discipline identified in Section 2.2 as being included in the project.

5.1. LEVEL ONE - PROCESS OVERVIEW MAP: ATTACHMENT 1 – Not Applicable

Provide a Level One (L1) - Process Overview Map that includes ALL Project Model Uses identified in Section 3.3.

Submit as part of the PxP in Section 14.3, Attachment 1, on 11x17” page size.

5.2. LEVEL TWO - DETAILED PROCESS MAPS: ATTACHMENT 2 – Not Applicable

Provide a Level Two (L2) - Detailed Process Map for EACH Project Model Use identified in Section 3.3. Submit each as part of the PxP in Section 14.3, Attachment 2, on 11x17” page size.

SECTION 6: MINIMUM MODELING AND DATA REQUIREMENTS

6.1. MINIMUM MODELING MATRIX (M3): ATTACHMENT 3 – Not Applicable for Campus Model

Provide an M3 with Column ‘F’ on Tab ‘03. Scope-LOD-Grade’ modified to indicate the Element ID’s included in the Project Scope of Work. Use the M3 Template located at https://cadbimcenter.erdc.dren.mil/ and submit as part of the PxP in Section 14.3, Attachment 3, in PDF and Excel file formats. See M3 Tab ‘01. Instructions’ for additional information.

6.2. MODELING ENHANCEMENTS (OPTIONAL) – Not Applicable

List enhancements from minimum modeling requirements as specified in Contract. Note: Enhancements MUST exceed minimum requirements of the M3. (i.e. using newer release of A/E/C CAD Standard or IFC Version, modeling all of the plumbing system and not only 1.5” and larger diameter piping, laser scanning for Quality Check install, etc.)

ENHANCEMENT PURPOSE

https://cadbimcenter.erdc.dren.mil/

SECTION 7: COLLABORATION PROCEDURES

7.1. COLLABORATION STRATEGY

The team will be utilizing Autodesk Construction Cloud for live file share collaboration. The team will collaborate with Interference Checking on a weekly collaboration meeting with all disciplines.

7.2. COLLABORATION ACTIVITIES

Complete the table to identify and describe collaboration activities conducted by the Team.

ACTIVITY TYPE

REQUIRED

PER

CONTRACT

PROJECT

STAGE

FREQUENCY PARTICIPANTS LOCATION

DESIGN COORDINATION YES BD-CD WEEKLY

MODELING

TEAMS

TEAMS

MEETING

SECTION 8: QUALITY CONTROL

8.1. STRATEGY FOR QUALITY CONTROL

The project team will have a dedicated BIM Prooject Manager. This person will provide constant review and monitor of the model processes. The team has completed a full PxP which includes QC. A complete QC BIM Review at each submittal will be done.

8.2. QUALITY CONTROL CHECKS

The following checks should be performed to assure quality.

CHECKS REFERENCE DOCUMENT

RESPONSIBLE

PARTY

SOFTWARE

PROGRAM(S)

SUBMITTAL

FREQUENCY

USACE ADVANCED

MODELING PxP SUBMITTAL

REVIEW CHECKLIST V4.0

(PxP CHX)

USACE Advanced Modeling PxP V4.0, Section 14.5.

SES Word WITH EACH PxP

SUBMITTAL

USACE ADVANCED

MODELING SUBMITTAL

REVIEW CHECKLIST (CHX)

Contract requirements, Paragraph titled Advanced Modeling Submittal Review Checklist.

SES Word

WITH EACH

MODEL

SUBMISSION

MODEL STANDARDS

Contract Requirements, Paragraph titled Model Standards Checks and Reports.

SES Revit

WITH EACH

MODEL

SUBMISSION

INTERFERENCE

MANAGEMENT

(3D COORDINATION)

USACE Interference Management Standard

SES Revit

WITH FINAL

MODEL

SUBMISSION

8.3. INTERFERENCE MANAGEMENT COORDINATION – Not Applicable

a. Process. [Describe the process used for executing the required Interference Management Model Use, including how the conflicts in the Coordination Model will be reviewed and resolved.]

b. Disciplines or Trades. The items listed below are typical but not inclusive. Add Disciplines or Trades as required to better visualize and resolve interference management conflicts. An example of an added

Discipline/Trade is insulation on piping or mechanical system

c. Color Coding Schemes. Define the Coordination Model color code schemes in the tables below. All model elements in the Coordination Model are to be color-coded by either Discipline/Trade or group. The color schemes do not denote realistic building material, symbology, or print settings.

DISCIPLINE/TRADE COLOR CODE SCHEME

DISCIPLINE/TRADE COLOR NAME R G B TRANSPARENCY

[STRUCTURAL] -- [MULTIPLE] -- -- -- [0%]

[ARCHITECTURAL] -- [UNASSIGNED] [--] [--] [--] [25%]

[MECHANICAL] [ORANGE] [255] [128] [0] [0%]

[PLUMBING] [CYAN] [0] [255] [255] [0%]

[ELECTRICAL] [YELLOW] [255] [255] [0] [0%]

[FIRE PROTECTION] [PINK] [255] [0] [127] [0%]

[SURVEY/MAPPINGS] -- [UNASSIGNED] [--] [--] [--] [25%]

[CIVIL] [BROWN] [204] [102] [0] [0%]

[LANDSCAPE] [DARK GREEN] [0] [153] [0] [0%]

[INTERIORS] [LIGHT BLUE] [51] [153] [255] [0%]

[TELECOMMUNICATIONS] [PURPLE] [153] [51] [255] [0%]

GROUP COLOR CODE SCHEME

GROUPS COLOR NAME R G B TRANSPARENCY

[STRUCTURAL CONCRETE] [GRAY] [192] [192] [192] [0%]

[STRUCTURAL STEEL] [MAROON] [204] [0] [0] [0%]

[GLAZING] [LIGHT GREEN] [204] [255] [204] [20%]

[SPATIAL RESERVATION] [RED] [255] [0] [0] [80%]

d. Acceptable Clash Types. List any anticipated Acceptable Clash Types and their justification in the table below.

ACCEPTABLE CLASH TYPE JUSTIFICATION

[Minor penetrations through slab less than 4” and not grouped together] [Minor holes typically not cut in slabs]

[Domestic water supply of less than 1½” diameter] [Exceeds requirements of the M3]

[8” diameter Flex Duct in open plenum] [Can be routed in field]

e. Clash Test Naming Convention. [Provide an example of the Clash Test naming convention that will be used.]

SECTION 9: TECHNOLOGICAL INFRASTRUCTURE NEEDS

List software used, and applicable disciplines identified in Section 2.2 as being included in the project, to execute EACH

Project Model Use identified in Section 3.3. Remove Model Uses from tables 9.1 and 9.2 that are not identified as

Project Model Uses. Software versions in an approved PxP cannot be changed without concurrence by the

USACE BIM/CIM Manager and approval by the Contracting Officer Representative.

9.1. DESIGN PHASE SOFTWARE

DESIGN MODEL USE DISCIPLINE USER SOFTWARE VERSION

DESIGN AUTHORING GUIDON / SES / IMEG

Revit 2020

PROGRESS REVIEWS SES / ANDERSON / IMEG BLUEBEAM / ADOBE ANY

INTERFERENCE MANAGEMENT

(3D COORDINATION)

GUIDON / SES / IMEG Revit 2020

EXISTING CONDITIONS MODELING –

ONLY AS NECESSARY

GUIDON / SES / IMEG Revit 2020

9.2. CONSTRUCTION PHASE SOFTWARE – Not Applicable

CONSTRUCTION MODEL USE DISCIPLINE USER SOFTWARE VERSION

[SITE UTILIZATION PLANNING]

[CONSTRUCTION SYSTEM DESIGN]

INTERFERENCE MANAGEMENT

(3D COORDINATION)

[DIGITAL FABRICATION]

[3D CONTROL AND PLANNING]

RECORD MODELING

[FIELD / MATERIAL TRACKING]

[DIGITAL LAYOUT]

[CONSTRUCTION SCHEDULING (4D)]

[EXISTING CONDITIONS MODELING]

[FACILITY DATA EXCHANGE (FDE)]

[OTHER ELECTIVE MODEL USE IF

APPLICABLE]

9.3. ADVANCED MODELING STANDARDS

Identify the versions of the following standards as required by Contract.

STANDARD VERSION

PLATFORM CONFIGURATIONS Revit 2020

A/E/C CAD STANDARD A/E/C CAD Standard ver. 6.1

A/E/C GRAPHICS STANDARD A/E/C Graphics Standard ver.2.1

IFC IFC2x3

GIS SPATIAL DATA STANDARDS FOR FACILITIES,

INFRASTRUCTURE, AND ENVIRONMENT (SDSFIE)

Not Applicable

FACILITY DATA EXCHANGE (IF REQUIRED BY CONTRACT) Not Applicable

SECTION 10: ADVANCED MODELING ORGANIZATION

10.1. MODEL STRUCTURE – NOT APPLICABLE

Describe and provide a DIAGRAM how Models are distributed to cover the required project content. For example, by building, floors, floor zones, end use areas, and/or discipline, etc.

10.2. FILE NAMING STANDARDS

As applicable in each category below, provide examples of proposed file names for each discipline identified in Section 2.2 as being included in the project.

a. BIM FILES

Provide file naming convention and samples here or in Section 14.4, Attachment 4; for example, 610-701.B02.T_R20.rvt

b. CIM FILES

610-701.B02.T101.2021.03.17.dgn

c. GIS FILES

d. CAD FILES

Must comply with the ‘Electronic drawing file naming conventions’ Section of the latest A/E/C CAD

Standard. Provide file naming samples here or in Section 14.4, Attachment 4

610-701.B02.T101.2021.03.17.dwg

e. COORDINATION MODEL FILES

610-701.B02.T.nwd

10.3. COORDINATE AND MEASUREMENT SYSTEMS – Not Applicable

Provide the Coordinate System (geo-referenced) and Measurement System (Imperial or Metric) required by Contract.

PROJECT COORDINATE AND MEASUREMENT SYSTEMS

COORDINATE SYSTEM

ZONE

HORIZONTAL (SITE) UNITS OF MEASURE

VERTICAL (BUILDING) UNITS OF MEASURE

HORIZONTAL DATUM

VERTICAL DATUM

SECTION 11: PROJECT DELIVERABLES

11.1. CONTRACTUAL PROJECT DELIVERABLES

List the deliverables for the project and the stage and format in which the information will be delivered.

Reference the Contract requirements.

ADVANCED MODELING DELIVERABLES

SUBMITTAL

FREQUENCY

FORMAT NOTES

LIST OF ALL SUBMITTED FILES (EXCEL

SPREADSHEET PREFERRED)

ALL Excel

ADVANCED MODELING SUBMITTAL REVIEW

CHECKLIST (CHX)

ALL PDF

ADVANCED MODELING BIM FINAL Revit

ADVANCED MODELING CAD FINAL AutoCAD

DRAWING FILES IN PDF FORMAT ALL PDF

IFC COORDINATION VIEW FINAL IFC

QUALITY CONTROL REPORT – MODEL

STANDARDS CHECK

FINAL HTML

COORDINATION MODEL FINAL NWD

COORDINATION MODEL FILE EXPORT FINAL HTML

DRAWING INDEX ALL Excel

11.2. PROJECT DELIVERABLES FOR ELECTIVE MODEL USES – Not Applicable

For each Elective Model Use identified in Section 3.3, list the submittal items for the project and the format in which the information will be delivered. Submittals will be provided as ‘For Information Only’.

SECTION 12: GEOGRAPHIC INFORMATION SYSTEM (GIS)

NOTE: RESERVED FOR FUTURE USE

SECTION 13: GOVERNMENT FURNISHED MATERIAL (GFM)

NOTE: RESERVED FOR FUTURE USE

SECTION 14: ATTACHMENTS

14.1. LEVEL ONE - PROCESS OVERVIEW MAP: ATTACHMENT 1 (From SECTION 5.1) – Not Applicable

14.2. LEVEL TWO - DETAILED PROCESS MAPS: ATTACHMENT 2 (From SECTION 5.2) – Not Applicable

14.3. MINIMUM MODELING MATRIX (M3): ATTACHMENT 3 (From SECTION 6.1, submitted in Excel and PDF file formats) – Not Applicable

14.4. FILE NAMING STANDARD: ATTACHMENT 4 – Not Applicable

14.5. ADVANCED MODELING PxP SUBMITTAL REVIEW CHECKLIST (PxP CHX) – V4: ATTACHMENT 5. Every

PxP Submittal must include a completed PxP CHX in accordance with the PxP CHX Submitter Instructions.

Similar in function to the CHX, it provides a process for checking on the quality of a PxP prior to submittal and as a review tool for USACE reviewer.

14.6. BIM WAIVER: ATTACHMENT 6

SECTION 15: TEMPLATE CHANGE LOG

Refer to the “USACE Advanced Modeling PxP Template V3.0 to V4.0 Change Log” document for a record of changes to this template.

ELECTIVE MODEL USE DELIVERABLE STAGE FORMAT NOTES

[ELECTIVE MODEL USE] [SUBMITTAL ITEM] [ALL]

BIM Request for Waiver

Date: 05/31/2023

Project Name: VA Hines EHRM Infrastructure Upgrades Phase II Project #: 21081.001

Re: Architectural, Mechanical and Telecommunications

VA DRAWING DELIVERABLE REQUIREMENTS

Section 5.2.1. Module 1 – Drawing Set Organization

1. Standard: “Model Filename Example: 489-423.800.A.20171202.rvt”.

A. Reason for request: SES understands following a standard file naming convention but including the date at the end of a Revit model causes opening errors and file linking issues on the VA’s end once the model has been received.

B. Request: SES suggests removing the date at the end of the file name.

C. Impact on VA: The files will open and link correctly once in VA’s possession.

D. Alternate Approach: Leave the file naming convention and SES is not responsible for issues upon opening the files or links.

Section 5.2.6. Module 6 – Symbols

1. Standard: Utilization of symbols from NCS or VA.

A. Reason for request: Marion team understands following a standard within reason but believes the scope of work will work best if utilizing individual company symbols.

B. Request: Team will use company standard symbols and a symbol legend will be provided on cover sheets to identify elements as necessary.

VA BIM STANDARD

Section 1.2.2. Contract Documents

1. Standard: “the Design-Intent Model takes precedence over the 2D drawings”.

A. Reason for request: SES understands the importance of the 3D information required for the VA. However, engineers are legally bound to the 2D drawings as those are what they sign and seal.

B. Request: SES suggests removing this portion of the VA Standards due to legality.

Section 2.1. General

1. Standard: “At a minimum, all elements within the scope of work and within the limits of the construction site or that may be affected by construction must be modeled, including but not limited to:”

A. Reason for request: SES understands the reason for this statement but would like to further define as to clarify which existing elements will need modeled.

B. Request: SES suggests “At a minimum, all elements within the limits of the construction scope/site that will require coordination with/into must be modeled, including but not limited to:”

www.specializedeng.com

VA Hines EHRM Infrastructure Upgrades Phase II SES Project #21081.001

BIM Request for Waiver Page 2 of 6 05/31/2023

Section 2.3 BIM TECHNOLOGY AND PLATFORMS

1. Standard: “The results of the Model Compliance Report must be submitted to VA at each design progress review.”

A. Reason for request: The scope of work restricts the team from meeting all standards and the end report would be of little value.

B. Request: SES suggests removing from requirements.

Section 2.4. MODELING TOLERANCES AND DIMENSIONING

1. Standard: “Building Objects/elements must be modeled in their exact location within the industry standard tolerance for the trade or discipline being represented, but in no case greater than 1/8”. All BIM Objects for construction must be modeled to actual real-world dimensions (not nominal). The AE and GC are responsible for designating stricter tolerances if needed to facilitate the intended uses of the model as outlined in this manual or as needed to execute the project. GC modeling for construction uses must have tolerances that enable accurate manufacture or layout of elements to which it applies. If laser-guided layouts (such as Total Station), pre-fabrication, or modular assembly techniques are being used, then the modeling teams, preferably with the GC, will review the tolerances required in those areas and for that building system component. Results and any adjustments affecting current and future modeling must be documented in the BxPs. Exceptions must be approved by VA and also noted in the BxP.”

A. Reason for request: SES understands the reason for this statement but would like to adjust the tolerance. The scope of work will not allow for such a strict location of content.

B. Request: SES suggests changing the 1/8” to 6” for new Telecom rooms, 12” for all existing.

Section 2.5 PROPERTIES AND ANNOTATIONS

1. Standard: “Fire rating fill patterns must be constructed within 3D wall types so that the partition’s respective rating is shown through all scales and types of views, including 2D Drawings.”

A. Reason for request: Not in scope of work

B. Request: SES suggests removing from requirements.

Section 2.7 LEGENDS AND SYMBOLS

1. Standard: “Legends and symbols in the 2D drawings may be 2D representations but are to be connected to the actual BIM Objects to which they are referring (i.e., any change to the actual BIM Object will result in an immediate updated 2D representation). Actual BIM Objects must be 3D objects with attached or associated data and metadata as defined throughout VA BIM Standard.”

A. Reason for request: SES understands the intent of this request, but due to limited scope of work may not be possible to achieve.

B. Request: SES suggests removing from requirements.

Section 2.8 SCHEDULES AND DETAILS

1. Standard: “All construction details must be “Model Details” and created with BIM tools and linked to the 3D view. All details that appear on 2D Drawings must be derived from BIM and match the assembly in BIM. No “Drafting Details” created in 2D software and added to the 2D Drawings will be accepted. All 2D drawing schedules must be derived from the properties of the model object, with the exception of calculations (e.g., calculations for low voltage, structural, electrical, etc.). Schedules are not to be augmented with unconnected data. Exceptions where calculations are done outside of BIM must be noted in QA/QC reports and state the technical reason for the exception.”

A. Reason for request: SES understands the intent of this request, but due to limited scope of work may not be possible to achieve.

B. Request: SES suggests removing from requirements.

BIM Request for Waiver Page 3 of 6 05/31/2023

Section 2.9 GEO-REFERENCE REQUIREMENTS

1. Standard: “VA requires that all models contain geospatial information that is properly referenced between a permanent, physical, USGS13 Survey Marker’s geographic survey point (Site Origin Point) available in the State Plane Coordinate system where the project is located, and the coordinate system in the model space (Project Base Point14), thereby providing a precise, measurable reference point for accurately locating and constructing buildings, site work, utilities, and infrastructure. (See Appendix 5 – Instructions for Geo-Referencing)”

A. Reason for request: Existing coordinates not provided.

B. Request: SES suggests removing from requirements.

Section 2.10 QUALITY ASSURANCE/QUALITY CONTROL

1. Standard: “The AE and the GC are responsible for assuring their models and data submittals have been thoroughly checked and meet VA BIM Standard and contract requirements for the project. Models and data must be submitted as noted in Section 3.9 – Deliverable Summary, for compliance evaluation by VA.”

A. Reason for request: QA/QC of model provided in other required documents.

B. Request: SES suggests removing from BIM requirements.

Section 2.11

1. Standard: “The final deliverable must provide the required information in a COBie format for import into the CMMS.”

A. Reason for request: COBie not applicable to this project

B. Request: SES suggests removing from requirements.

Section 2.12. STARTING A NEW PROJECT (SEPS2BIM)

1. Standard: “VA will provide a Project BIM Export file from SEPS in an Excel spreadsheet format to the AE.”

A. Reason for request: No SEPS requirements on this project

B. Request: SES suggests removing from requirements.

Section 2.13.3 Modeling Space

1. Standard: Entire Section

A. Reason for request: Not applicable to existing info, but will be for new work.

B. Request: SES suggests removing from requirements.

Section 2.14 MODELING EQUIPMENT

1. Standard: Entire Section

A. Reason for request: Not applicable to existing info, but will be for new work.

B. Request: SES suggests removing from requirements.

Section 2.16. MODELING SPACE RESERVATIONS

1. Standard: “The AE and the GC must model space reservations (clearance or no-fly zones) for access to MEPFT building equipment and distribution systems, and for coordinating the locations for, and access to, systems that are installed after major building systems are put in place, such as medical technology (low-voltage), business systems, and fire protection systems.”

A. Reason for request: Revit lacks the capability to associate clearance zones to cable tray.

B. Request: SES would like to not be held accountable for modeling cable tray clearances but will accommodate space without an element.

BIM Request for Waiver Page 4 of 6 05/31/2023

Section 2.18. DISCIPLINE MODELS

1. Standard: “Each project will require different discipline models depending on the scope of work.”

A. Reason for request: As we will have 20+ models per discipline group, by combining some disciplines into groups (Bundling interior model content with the Architecture model, as example) they will have a more efficient package of information to manage.

B. Request: Models to be utilized will be structured as follows:

1. 610-701.Bxx.M_R20.rvt

a. Mechanical misc

2. 610-701.Bxx.F_R20.rvt

a. Fire Protection misc

3. 610-701.Bxx.A_R20.rvt

a. Architecture

b. Interior misc

c. Medical Equipment, Food Service, Laboratory Equipment misc

4. 610-701.Bxx.E_R20.rvt

a. Electrical

5. 610-701.Bxx.T_R20.rvt

a. Telecommunications

6. *Some models may be combined in the form of ET, MT, MP, MPT or MEPFT

a. models will be named appropriately for content contained

Section 2.18.1. Site Civil

1. Standard: “Objects must be modeled in 3D for civil underground utilities and site work, both existing and proposed, and be classified using OmniClass Table 21 to identify the system each asset is a part of, Table 22 for to align with specification sections and Table 23 to identify the asset type. Include all utility properties. Modeling will extend five feet beyond the project construction boundaries and will connect with the site and building utility services.”

A. Reason for request: Please provide files containing the existing utilities modeled as a 3D pipe network, if available.

B. Request: If additional existing data files are not available, we propose the following:

1. New fiber utility corridor existing ground topography collected during survey will be created as a 3D surface in AutoCAD Civil3D. The new duct banks or other underground fiber runs will be modeled as a 3D pipe network in AutoCAD Civil3D. Existing utilities coordinated with the new work will remain in 2D with reasonable assumptions on depths made based on available evidence. New work will be delivered in AutoCAD Civil3D and PDF plans.

Section 2.18.8. Mechanical, Electrical, Plumbing, Fire Protection, & Medical Technology (MEPFT)

1. Standard: “All system elements 1.0 inches in diameter and larger (e.g., general plumbing, fire protection, etc. but not individual electrical cables unless in Patient Headwalls), and other elements (ducts, cable trays, etc.) with a dimension 4 inches and over must be modeled. Conduit that will be consolidated into cable trays need not be modeled individually; only the tray needs to be modeled.”

A. Reason for request: SES understands the request for size requirements on modeled data.

BIM Request for Waiver Page 5 of 6 05/31/2023

B. Request: SES suggests following the table below on modeled elements. SES feels that following these guidelines will provide more value to the client during the design process. The items requested to not be modeled will save time in design not having to address small item conflict resolution when the contractor will likely install using construction means/methods unknown to SES.

Section 3.2 DESIGN-INTENT MODEL – BIDDING

1. Standard: Entire Section

A. Reason for request: Not applicable to this project

B. Request: SES suggests removing from requirements.

Section 3.4 FACILITY MANAGEMENT DATA

1. Standard: “VA requires data from the design and construction process to be reused for Facility Management. VA will use the information in a Computerized Maintenance Management System (CMMS) and Computer-Aided Facility Management (CAFM). To assure that data for Facilities Management (FM) can be adequately transferred into VA’s CMMS to operate the building, the data described in VA Data Requirements for Facility Management (FM Data) must be compiled during project delivery and provided in a COBie format. Both the AE and the GC must collaborate together and with VA to assure this information is available to the facility.”

A. Reason for request: Not applicable to this project

B. Request: SES suggests removing from requirements.

Section 3.5 RECORD MODEL

1. Standard: Entire Section

A. Reason for request: Scope of work

B. Request: Models will be updated and provided at the end of the construction period as a Record Model.

Section 3.6. GC AND AE CONSTRUCTION PERIOD SERVICES FOR FM

1. Standard: “provided in an electronic format by the GC to the AE, who will link the information to the appropriate BIM Objects in the building Record Model and site Record Model and 2D As-Built Drawings. (This information must not be referenced to a manufacturer’s website, as URLs change over time---See Linking References.) ”

A. Reason for request: SES understands the reason for the request of the associated data. SES has provided documentation linked like this before and experienced a massive amount of effort involved only to determine that there is not an associated value in doing this.

B. Request: SES suggests providing this data in a typical manner for containing this information in a folder structure or associating with COBie exported data. The VA folder structure should easily accommodate the needed data in a common location instead of trying to link within the model.

C. Impact on VA:

D. Alternate Approach: VA to remove this requirement.

Section 3.6. GC AND AE CONSTRUCTION PERIOD SERVICES FOR FM

1. Standard: “Coordinating with the GC, the AE must provide the continuously updated Record Model, the As-Built Drawings, the FM Data (in a COBie format), Linked Files, and a Comprised Progress Report to VA beginning at the 10% construction milestone and at a minimum of every three months thereafter for the duration of the work.”

A. Reason for request: SES understands the request.

B. Request: SES suggests that milestone documents are not provided, and a complete Record Model is provided at the end.

Conduits 3" and above

Cable Tray and Cable Sleeves - 3" and above

BIM Request for Waiver Page 6 of 6 05/31/2023

Section 4.3 FM DATA

1. Standard: Entire Section

A. Reason for request: Not applicable to this project

B. Request: SES suggests removing from requirements.

Section 4.5 VERIFICATION, ANALYSIS, & DECISION SUPPORT

1. Standard: Entire Section

A. Reason for request: Not applicable to this project

B. Request: SES suggests removing from requirements.

Section 4.7.1 Daylight, and Sun Studies

1. Standard: Entire Section

A. Reason for request: Not applicable to this project

B. Request: SES suggests removing from requirements.

Section 4.9.1 BIM Integrated Specifications

1. Standard: Entire Section

A. Reason for request: Not achievable with current required use of VA Master Specifications

B. Request: SES suggests removing from requirements.

Submitted By: Andrea Alderton mew