J2g FAA BIM Execution Plan_v1.2 CAEG.pdf

FAA BIM Execution Plan (BxP)

2 August 2024 Version 1.2

AIR TRAFFIC ORGANIZATION

COMPUTER AIDED ENGINEERING GRAPHICS (CAEG) PROGRAM OFFICE

AIR TRAFFIC CONTROL FACILITIES

AJW-29 NATIONAL ENGINEERING SERVICES (NES) GROUP

[THIS PAGE INTENTIONALLY BLANK]

TABLE OF CONTENTS

1. INTRODUCTION

2. FAA BIM PROJECT TYPES

2.1 Design-Build Projects

2.2 Design-Bid-Build Projects

3. DESIGN & COORDINATION OF BIM PROJECTS

3.1 Project Execution Plan (PxP)

3.2 Kickoff Conference for Design and Construction

3.3 BIM Coordination and FAA Approved Modeling Software / Tools

3.4 Model Reference & Common Alignment

3.5 BIM Clash Review & Resolution

3.6 Facility Data

4. FAA BIM SUBMITTAL REQUIREMENTS

4.1 Digital Submittals

4.2 Design Submittals

4.3 BIM and CAD Data Submittals

4.4 Submittal Reviews

4.5 Model Level of Development (LoD)

4.6 Model Granularity

5. GENERAL BIM REQUIREMENTS

5.1 General Provisions

5.2 BIM File Naming

5.3 Discipline-Specific Provisions

5.3.1 Architectural

5.3.2 Interiors

5.3.3 Structural

5.3.4 Mechanical (Ductwork, Fittings, Equipment & Related Piping)

5.3.5 Plumbing (Domestic Water Systems)

5.3.6 Plumbing (Drain, Waste, Vent & Storm Systems)

5.3.7 Fire Suppression

5.3.8 Fire Alarm

5.3.9 Electrical Lighting

5.3.10 Electrical Power

5.3.11 Electrical Lightning Protection, Grounding & Cathodic Protection

5.3.12 Telecom Data/Network Systems

5.3.13 Telecom Mass Notification

5.3.14 Telecom Security

5.4 Civil / Site

5.4.1 Terrain (DTM)

5.4.2 Drainage

5.4.3 Storm Water and Sanitary Sewers

5.4.4 Utilities

5.4.5 Roads and Parking

5.4.6 Geographic Referencing

5.5 Indoor Air Quality (IAQ) Management Plan

6. PROJECT DIRECTORY STRUCTURE (FAA’s Post-Construction Document Storage)

6.1 Facility Folder

6.2 Configuration Management (CM) Folder

6.3 Projects Folder

6.4 Record, Reference, Support Folders

7. BIM AND DATA SECURITY

8. DATA OWNERSHIP

9. BEST PRACTICES AND PROCEDURES

9.1 General Guidelines

9.2 Software Performance

9.3 Compacting Files

9.4 Creating the BIM

9.5 Creating Views in the Model

9.6 Project Execution Plan (PxP)

10. APPENDICES

10.1 Acronyms & Glossary of Terms

10.2 BIM Data Requirements by Discipline / Worksets / Components

10.3 Schedules in Drawings

10.3.1 Graphic Presentation of Schedules

10.3.2 Schedule Formats

INTRODUCTION / SCOPE

1. INTRODUCTION

The following FAA Building Information Modeling (BIM) Execution Plan (BxP) defines the implementation protocols, specific requirements, activities and processes for design and construction of projects using BIM within, or for, the FAA. Information from Architectural and Engineering firms (AEs), and internal FAA organizations, is stored in the FAA’s Electronic Document Management System (EDMS) ProjectWise and continually used throughout the Lifecycle Management Process. Utilizing BIM, and the BIM processes identified in this document, will ensure fully coordinated building construction, and ensure key information regarding building systems, equipment, and assets can be utilized effectively in the overall maintenance and lifecycle of the constructed building. This makes the use of BIM an integral part of the NextGen transformation.

This document defines minimum modeling requirements and procedures for BIM projects utilizing the Autodesk Revit BIM platform. All projects using a BIM platform to produce drawings and reports shall adhere to these requirements in full.

The purpose of this document is:

• To outline the FAA’s expectation of BIM used in service of FAA projects during design, construction and building operation and,

• To define basic requirements for BIM which will assure that the phase-specific needs of the FAA will be met by the developing BIM throughout each stage of design, construction, and operations.

The FAA has implemented ProjectWise eDMS for managed access and file sharing during the operations stage by FAA project participants. The eDMS is more than just a simple utility for file receiving, retrieval, and storage. All Project files, including but not limited to BIM, reside within the eDMS, synchronized between all participating sites, and are available for check-in/out, viewing, and editing within the limits of defined secure access rights.

The FAA requires the use of Autodesk Revit for all BIM based projects. Revit-based projects will be used by the FAA within the workflows supported by ProjectWise as delivered by Bentley Systems.

The requirements of this document have been prepared to work within this framework.

The current implementation of BIM includes the use of BIM processes to assure coordination between building systems and derivation of drawings directly from this coordinated project model.

Data shall be embedded within the project model and delivered to the FAA for use in Operations after Construction.

Each project shall be governed by its BIM Project Execution Plan (PxP), described in 3.1 below, which shall set the project-specific goals for BIM, how the models shall be structured to achieve these goals, appropriate software to be used, and the relationship between the project participants.

2. FAA BIM PROJECT TYPES

FAA ATO authorizes new occupied buildings to be delivered using different methodologies. Some of the common types of projects executed by the ATO are described below. The FAA intends to maintain the usage and adoption of BIM consistently across these projects, despite differences in the parties responsible for creating and maintaining the BIM.

While BIM is not considered the FAA’s document of record, 2D documents of record shall be generated from the final BIM and a fully unified set of discipline-specific BIM files, representing the aggregate whole building, shall be provided at each deliverable phase for review and comment.

Independent of project delivery method, PDF plots shall be the 2D Documents of Record, created from the approved BIM project platform. All supporting files used in the creation of the PDF drawings shall be delivered in whole at each submission (e.g., Linked images and CAD, etc.)

Projects “Issued for Construction” or “Ready to Advertise” shall have achieved the Level of Development (LoD) as described in section 4.5 below, and so documented in the project’s PxP, setting the “Basis of Design”. This includes embedment of the initial system data within the BIM for the major equipment modeled, as described in the Project Specifications. The material and systems selection process, during construction, requires the modeled components to be updated as alternates and substitutions are adopted.

2.1 Design-Build Projects

The Prime Contractor shall deliver to the FAA, project BIM which is coordinated with all trades and disciplines, accurate to the systems dimensions and data, and a reflection of the progression through the project schedule. The final submitted model shall reflect fully coordinated, As-Built conditions for the project.

2.2 Design-Bid-Build Projects

The Project Architect/Engineer (AE) shall deliver a fully coordinated and conflict-free BIM that reflects the project progress and design phase. The project BIM shall be prepared by the AE to the LoD as described in 4.5 below and documented in the project’s PxP prior to Advertisement for Bidding or Issuance for Construction. Each stage of submission shall include review by the FAA, and all issues shall be rectified by the AE prior to acceptance of the next stage.

At Award, the Prime Contractor (PC) shall be given access to the project BIM as designed and shall verify its component systems. Any discrepancies shall immediately be brought to the attention of the FAA. As alternates and substitutions are adopted, the PC shall modify the model and underlying data accordingly, resolving all coordination issues with the model. Final system data shall reflect fully coordinated, As-Built conditions for the projects.

PROCESS

3. DESIGN & COORDINATION OF BIM PROJECTS

The Architect/Engineer (AE) will adhere to these protocols, processes, and activities during the design and coordination of all FAA BIM Projects.

3.1 Project Execution Plan (PxP)

The BIM Project Execution Plan (PxP) provides the framework where all stakeholders, project team members and anyone else involved in the project, obtain a common operating vision regarding the use and implementation of BIM through the project. It presents a plan for the generation of project information during the project’s design and construction lifespan. The PxP will also provide a timeline and description of BIM related deliverables that ensure the project is completed on time and with minimal design or coordination issues.

The PxP is not intended to restate all the requirements of the FAA’s BxP, but to document where the needs for Project BIM exceed the minimum requirements stated in the FAA’s BxP. The PxP shall define the uses and execution of BIM across the lifecycle of the project, to include:

• Project Initiation o Participant Roles & Responsibilities

• Best Practice o Modeling Level of Development (LoD)

• Modeling Plan o Modeling Reference & Common Alignment o Planned Models (List by AE / PC) o Modeling & Data requirements that exceed the minimum requirements of the FAA’s BxP o BIM File Naming o Deliverables

• Project Collaboration & Communication o Collaborative Data Environment (File Sharing Method) o Clash Management

• Project Technology Plan o Software Component Selection o Delivery Formats

The PxP shall address the viability of the BIM design and analysis technologies selected for the Project. From concept development through As-Built drawings and propagation of the FAA Maintenance System, the PxP shall detail how the project will be implemented, monitored, and controlled with regard to BIM. The PxP will be coordinated with the Project’s master schedule and the scope of the TFDS. It will identify the AE’s and the Contractor’s BIM coordinator, as well as lead team members responsible for creation, development, and maintenance of the BIM data, and how the BIM data shall be managed and interoperate (data storage, sharing, viewing and updating, as necessary) among all AE / Contractor team members. The AE and the Contractor shall be responsible for all necessary model and data component clarifications to deliver BIM to the FAA compliant with the FAA’s BxP.

The PxP will specifically address and describe BIM uses during design and construction phases and will include value management, interference management, and design-change tracking, or such other uses as the contractor proposes. The AE and the Contractor shall be responsible for all model and data component clarifications necessary to deliver BIM models to the FAA, that are compliant with the FAA’s BxP.

The FAA requires a Project Execution Plan (PxP) within forty-five (45) days of the project being initiated in design, and again, of being awarded unless otherwise specified. The PxP is further required to be updated and submitted for review at Design & Construction submittals when the documented content requires change and is approved for change by the FAA CO/COTR. Questions about PxP may be directed to the FAA Project Team through the appropriate point of contact (PoC) for the Project.

The FAA’s PxP template is available in Word (.docx) through the appropriate FAA PoC for the Project.

3.2 Kickoff Conference for Design and Construction

Clarification of the BIM requirements shall be provided within the context of initial project kickoff meetings provided both for Design and for Construction. The scope of the Project’s BIM utilization shall be further clarified, including the use of BIM for design, generation of 2D views for sheets, coordination between various disciplines, clash review and resolution, and to support integration of the required facility data.

The PxP will be reviewed for clarification, and to verify the functionality of the project’s BIM technology, protocols, processes, and activities. The FAA shall confirm acceptability of the PxP and advise of any required additional processes or activities to be incorporated. If modifications are required, the AE / Contractor shall execute the modifications and resubmit the final PxP for FAA acceptance.

Prior to beginning of Design or Construction and based on project Type, it will be determined how the BIM will be used to serve as a coordination and conflict resolution model to resolve potential clashes between disciplines during the design and construction phases.

3.3 BIM Coordination and FAA Approved Modeling Software / Tools Deliverables shall be stored, post-construction, within the FAA’s document management system ProjectWise and actively used in maintenance of the record of built works. The mandate for secure and managed access outweighs the benefits and features of any single BIM platform. The FAA allows the use of BIM and CAD which are demonstrated as viable within the framework of ProjectWise.

Autodesk’s AutoCAD is known to operate fully within the ProjectWise environment. Autodesk Revit is acceptable for use only within the workflows supported by ProjectWise which have been demonstrated as viable by Bentley Systems.

The AE / Contractor is responsible for developing the BIM with facility data for the purposes of coordination between all disciplines. All submitted BIM’s and associated facility data shall be fully generated by FAA approved BIM software / tools. The BIM approved software for the FAA is the IFC certified versions of Revit as confirmed by the FAA’s CAEG Program Office as supported by the FAA’s eDMS. Additional information required for the project such as schedules, cost data, energy models, etc. must be delivered in a BIM format compatible with the approved Revit version. The coordinated

BIM shall also be geographically aware and contain coordinate information that will allow the BIM to be connected to a Geographic Information System (GIS).

3.4 Model Reference & Common Alignment

Files that are in alignment horizontally and vertically are termed “in-registration”. Registration of all BIM files is critical to cross-discipline coordination and multi-file work. The FAA requires that all BIM files develop their work through common selection of one of two methods, 1st, relative to the Revit Base Point (effectively XYZ = 0,0,0) without re-assigning that origin point within a file. Or 2nd, by use of a Revit Shared Coordinate System between all the project’s discipline-specific BIM’s. The method selected shall be documented in the Project’s PxP.

The FAA shall test the relationship of the files by independently attaching them as a reference (or link) to an unmodified master in the executed version of Revit, and the clash management software Navisworks Manage. Files found to be not “in-registration” shall be required to be corrected by the submitting authority.

The 1st method of alignment as clarified for Revit is:

Revit files have both their initial Project Base Point and Survey Point set to (0,0,0).

• Do not move the Project Base Point in any file. If necessary, move the Survey Point.

• Establish a structural grid relative to (0,0,0). Modelers may then author the building systems corresponding to the grid with assurance of a coordinated position relative to the project Origin.

• Attachments (or links) of other building systems shall inherently be positioned in proper alignment in both BIM authoring and clash management software.

3.5 BIM Clash Review & Resolution

Projects shall be delivered filly coordinated and clash free. Each submittal shall be reviewed for clash resolution, and issues found shall be provided to model authors as comments to be resolved as the project advances.

Within a Revit project, Navisworks Manage shall be used to check the modeled system’s “registration” and to verify the resolution of all found clashes.

The BIM shall be set up to support clash/conflict/interference checks. AEs and their discipline consultants shall be responsible for setting up their respective coordination protocols to complete the BIM with relevant data that is spatially aware. It is the responsibility of the AE/Contractor to update their BIMs to reflect coordinated resolution, ensure the design intent has been followed, and ensure models only contain intended elements.

A written report shall be provided to log all hard clashes, where two elements are occupying the same physical space within the BIM (ex., mechanical vs. structural or mechanical overlaps in the same location) and soft clashes (conflicts regarding service access, clearances, code elements, fireproofing, insulation, etc.) Additional reports shall be provided to show all clashes have been resolved. Coordination software will be used for assembling the various design BIM’s and for providing a report and viewing a list of design coordination issues. Detailed records of all conflict resolution shall be maintained. The design team, including the team’s BIM Facilitator and Discipline BIM Leads, will review the model and the clash reports in coordination meetings with FAA personnel.

The AE/Contractor is responsible for conducting periodic single-discipline and cross-discipline interference checks and resolving the identified interferences. The AE/Contractor shall also be responsible for presenting a clash-checking schedule in the PxP that includes interference checks at every major submission to the FAA. Additional coordination checks will be performed on an as-needed basis.

In case of unresolved clashes between modeled building systems during construction, the FAA shall assess the need to lead a Clash Resolution Workshop, where all the affected parties shall mutually determine the best course of action to resolve the affecting clashes.

3.6 Facility Data

The FAA requires embedded data within the BIM in accordance with Appendix 10.2, BIM Data Requirements by Discipline/Workset/Components. This requirement acknowledges the evolution of the data in line with the evolving design geometry through the design submittal stages.

All schedules on sheets shall be driven by the underlying facility data stored in component Types and paced Instances. Refer to Appendix 10.3, Schedule Formats, for the collection of pre-defined Schedule Layouts for Revit as well as the parameters supporting their use. These can be added to any Revit file through Revit’s utility “Transfer Project Standards” from the FAA’s source file. This is available via the CAEG Program Office on request from the FAA’s PoC for the project. Appendix 10.3, Schedule Formats, includes description of the graphic components of schedules to direct the definition of project schedules beyond the few pre-defined layouts provided.

DELIVERABLES / SUBMITTALS

4. FAA BIM SUBMITTAL REQUIREMENTS

The AE/Contractor shall provide the FAA a 3D interactive visualization in Navisworks, Adobe 3D PDF or an equivalent format. The FAA may request other formats if needed to address Project-specific requirements. Facility data as available will be provided through a COBie spreadsheet.

Refer to section 4.5 below for LoD requirements. The following deliverable requirements apply:

AE Phase Milestone BIM LoD Deliverable Prior to Kickoff Meeting 0% 0% PxP PPD 10% LoD200 Updated PxP

PPD

Arch/Intr BIM Structural Layouts MEP Equipment Layouts 2D Drawings (PDF & CAD)

Schematic 45% LoD200-LoD300 Updated PxP & PPD Arch/Intr/Strc BIM MEP Room Layouts Mechanical Calcs Clash Reports Preliminary CE Data 2D Drawings (PDF & CAD) Visualization (.nwf / 3D PDF)

Design Development 70% LoD200-LoD300 Updated PxP & PPD Arch/Intr/Strc BIM Mech/Plbg/Fsup BIM Falr/Elec/Tcom BIM Revised Calcs Clash Reports CE & Quantity Reports 2D Drawings (PDF & CAD) Visualization (.nwf / 3D PDF)

Construction Documentation

100% LoD350 Updated PxP & PPD Arch/Intr/Strc BIM Mech/Plbg/Fsup BIM Falr/Elec/Tcom BIM Revised Calcs Clash Reports CE & Quantity Reports 2D Drawings (PDF & CAD) Visualization (.nwf / 3D PDF)

AE Phase Milestone BIM LoD Deliverable Corrected 100% FINAL LoD350 Updated PxP & PPD

Arch/Intr/Strc BIM Mech/Plbg/Fsup BIM Falr/Elec/Tcom BIM Revised Calcs Clash Reports CE & Quantity Reports 2D Drawings (PDF & CAD) Visualization (.nwf / 3D PDF)

Modeling Passes from AE to Contractor

Contractor Phase Milestone BIM LoD Deliverable Prior to Kickoff Meeting n/a n/a Updated PxP Shop Drawings / Systems Selection

As Submitted LoD400 Updated PxP Affected Discipline BIMs Revised Calcs as affected Shop Drawings (PDF)

Progress Review Monthly LoD400 Updated PxP & PPD Arch/Intr/Strc BIM Mech/Plbg/Fsup BIM Falr/Elec/Tcom BIM Clash Reports 2D Drawings (PDF & CAD) List of Installed Systems

Facility Commissioning E/O Construction LoD400 As-Built Discipline BIMs As-Built Drawings (PDF & CAD)

JAI / Closeout FAA Handover LoD400 Revise As-Built BIMs Revised As-Built Drawings

(PDF & CAD)

Models Pass from Contractor to FAA

Table 4-1, FAA BIM Submittal Requirements

4.1 Digital Submittals

Digital submittal drawings (PDF) derived from BIM shall be of such resolution that supports printing full-size (ANSI D) size, and suitable for half-size (11”x17”) scaled reproduction, or at such alternate size in accordance with FAA STD 002 and approved by the project’s FAA CO or representative.

4.2 Design Submittals

CAD drawings extracted from the BIM shall comply with the latest version of FAA STD 002. Any deviations must be approved by the FAA. 2D Documentation shall be generated from the BIM and prepared with FAA approved BIM Authoring Software. All plans, elevations, sections, details, and schedules shall be fully coordinated with the BIM. All other documents are to be submitted per the contract requirements.

4.3 BIM and CAD Data Submittals

The submitted BIM shall include, but not limited to, all files and reports as listed in table 4-1 above.

4.4 Submittal Reviews

The FAA will review BIM project design submittals, and as submitted for Construction progress review, for compliance with the FAA’s BxP for resolution and discussion with FAA personnel during design coordination reviews.

The submittal review provides an evaluation of the BIM project for compliance including the following areas:

• Verfication that all required files have been provided.

• BIM File Naming

• BIM Structure (file segregation by discipline as as noted in the project’s PxP)

• Verification of Common Alignment of Discipline BIM

• Verification of Clashes Reported and degree of resolution achieved.

• LoD meets requirements per submittal.

• Validation of BIM deliverables percent complete by discipline.

4.5 Model Level of Development (LoD)

All designs evolve through many stages from inception of design through to construction of the design, requiring an evolving amount of detail appropriate to both the need to support design drawings, and later to support construction of the coordinated design.

LoD shall be as defined in the AIA G202 Project BIM Protocol, and coupled with the design process as follows:

Initially, modeled objects shall be LoD200, dimensionally correct. As the presentation of the design requires schedules in the drawings, information shall also be embedded as object data, and all presented schedules shall express the embedded information within the BIM.

LoD300 is defined as objects dimensionally correct, with embedded data. The data required evolves through the design process as defined in Appendix 10.2, BIM Data Requirements. The submitted Final Design shall be LoD300 as defined in the requirements of section 5, General BIM Requirements and Appendix 10.2, BIM Data Requirements. The BIM at Final Design shall reflect both the submitted information of the PPD and the specified “Basis of Design” building components.

As submittals are approved, the Contractor shall update the model to LoD400 where applicable, both by updating the components and data, and as system supports for installation are added to the model & coordinated, prior to construction. LoD400 is required of all custom ordered elements such as, but not limited to, steel members, metal work, precast concrete panels, and duct work. Items ordered and installed, but not specifically fabricated for the project, such as VAV boxes, Chillers, Plumbing Fixtures, etc., are considered “specified products”, and LoD400 modelling is not required.

Refer to both Section 5, General BIM Requirements, and Appendix 10.2, BIM Data Requirements.

4.6 Model Granularity

Models may vary in the amount of detail for individual elements within a model, but at a minimum must include all features that would be included on a 1/4” = 1’-0” scaled drawing (eg. At least 1/16th, 1/8th, and 1/4th) and all the elements of fire protection, or appropriately scaled Civil drawings.

5. GENERAL BIM REQUIREMENTS

This Section establishes the technical criteria required to develop a project using BIM technology for the FAA. The following requirements shall be included in the BIM as the design is developed and refined. The BIM shall be set up with the intention of being the source and container for all project information. Changes to the design and data shall be coordinated through the BIM. The BIM shall be created to support 3D model visualization that represents the design including snapshots of 3D imagery and walk and fly-throughs for virtual navigation.

5.1 General Provisions

The BIM shall be developed to include the systems described below as they would be built. The BIM shall also include as many of the systems described below as are necessary and appropriate for each design review cycle reflecting the progress of the design stage. Existing conditions shall be exempt from the modeling requirements except at areas where the new systems interface with existing.

Performance attributes and specifications shall be included as attributes to the BIM object elements to the extent possible and per the LoD specifications. Minimum Systems to be modeled are identified by Discipline below, including general framework for each listed system.

The FAA shall inspect submitted works to verify all modeled components are correctly assigned to the related worksets within the Revit BIM’s.

5.2 BIM File Naming

BIM filenaming, for the PROJECT folder, shall follow the convention LID-NNNNNNNN-xxxxxx.rvt, consistent with FAA-CAD-STD-002, where:

• LID is the provided Location ID,

• NNNNNNNN is the JCN# or other control number provided by the FAA, and

• xxxxx is a descriptor for the file (any # of characters) chosen by the authoring agent.

(ex. CHS-123458-Architectural.rvt, CHS-123458-Structural.rvt, etc.)

As-Built Record BIM, for the FACILITY folder, shall follow the convention LID-M-FAC-xxxxxx.rvt, consistent with FAA-STD-002, where:

• LID is the FAA provided Location ID,

• M indicates a model file, and

• FAC is the FAA provided Facility ID, and

• xxxxx is a descriptor for the file (any # of characters) chosen by the authoring agent.

(ex. CHS-M-TRACON-Architectural.rvt, CHS-M-TRACON-Structural.rvt, etc.)

Note that a list of files to be prepared shall be included in the Project Execution Plan (PxP), and updated for each submittal as necessary.

5.3 Discipline-Specific Provisions

The Project BIM is to be an aggregate of individual discipline-specific BIM’s. Projects shall, at a minimum, develop individual files for Architecture (ARCH), Interiors (INTR), Structural (STRC), Mechanical (MECH), Plumbing (PLBG), Fire Suppression (FSUP), Fire Alarm (FALR), Electrical (ELEC) and Telecommunications (TCOM).

5.3.1 Architectural

Workset System Components A-Spaces Rooms & Spaces (shall be used to validate against program SF & area quantities).

A-Flooring Floor Systems, above structural components modeled separately & linked.

A-Wall Wall Systems, coded by type (incl. Thermal, Acoustic & Fire Ratings) A-Opening Doors, Windows & Louvers coded by type (incl. clearance zones) w/data required to create schedules.

A-Ceiling Ceiling Systems, incl. soffits, materials & special conditions.

A-Roof Roof Systems, above structural components modeled separately & linked (incl. drainage system, penetrations, curbs & specialties) A-Circulation Circulation Systems (Stairs, Walks, Ladders, Elevators, Guards & Rails, limits of shafts for coordination, supporting equipment & clearance zones).

A-Plbg Fixtures Plumbing Fixtures A-Toilet Partitions Toilet Partitions A-RR Accessories Restroom Accessories A-Casework Fixed Cabinets and Counters. Built-Ins.

A-Specialties Specialties (Masterformat Div. 10 Items) A-FE Specialties Fire Extinquishers, FE Cabinets, FP Hose Reel Cabinets, etc.)

5.3.2 Interiors

I-Systems Furniture Systems Furniture & Panels w/data required to identify.

I-Furniture Relocatable Furniture w/data required to identify.

I-Equipment Equipment (incl. clearance zones) w/data required to create schedules.

I-Partitions Demountable partitions, coded by type.

I-Plant Interior Plantings (containerized) w/data required to identify or create schedules.

I-Artwork Art Objects w/data required to identify I-Signage Signage w/data required to create schedules.

I-OF Equipment Owner Furnished Equipment (incl. respective data & clearance zones as provided).

5.3.3 Structural

S-Foundation Foundations S-Floor Framing Floor Framing (frame components, deck, slab, exp/cntr joints, shafts, pits, openings, etc.)

S-Roof Framing Roof Framing (frame components, deck, slab, exp/cntr joints, shafts, pits, openings, etc.)

S-Columns Columns, Column grouted baseplates. Modeling of bolted connections is not required.

S-CIP Cast-In-Place Concrete Components (incl. joints & openings) excl. slabs.

S-Precast Precast Concrete Components (incl. openings) S-Circulation Circulation System Structural Components S-Wall Structural Wall Systems S-Glazing Structural Glazing Systems

5.3.4 Mechanical (Ductwork, Fittings, Equipment & Related Piping)

M-Duct-Supply Air Supply Air ductwork & fittings M-Duct-Return Air Return Air ductwork & fittings M-Duct-Exhaust Air Exhaust Air ductwork & fittings M-Duct-MUOA Makeup / Outside Air ductwork & fittings **add other duct systems in similar fashion as necessary M-Diff/Grilles Diffusers & Grilles M-Equipment Mechanical Equipment & control systems (incl. clearance zones & respective data) M-Piping Mechanical Piping M-System-FUEL Fuel Oil System (Distribution, Equipment & Devices) M-System-NGAS Natural Gas System (Distribution, Equipment & Devices) M-System-LPGS LPG System (Distribution, Equipment & Devices) M-Supports Supports for Mechanical Systems (hangers, etc.)

5.3.5 Plumbing (Domestic Water Systems)

P-DOMW-Cold Water CWS/CWR piping & fittings P-DOMW-Hot Water HWS/HWR/HWRR piping & fittings P-DOMW-Equipment DOMW Equipment (incl. clearance zones & respective data) P-Supports Supports for Plumbing Systems (hangers, etc.)

5.3.6 Plumbing (Drain, Waste, Vent & Storm Systems)

P-DWVS-Drainage Drain piping & fittings P-DWVS-Sanitary Sanitary waste piping & fittings P-DWVS-Vent Vent piping & fittings P-DWVS-Storm Storm piping & fittings P-DWVS-Equipment DWVS Equipment (incl. clearance zones & respective data)

5.3.7 Fire Suppression

FS-Distribution Fire Suppressions piping & fittings FS-Equipment Fire Suppression Equipment (incl. clearance zones & respective data) FS-Devices Fire Suppression devices (heads, etc) FS-Supports Supports for Fire Suppression System (hangers, etc)

5.3.8 Fire Alarm

FA-Distribution Fire Alarm Distribution (conduit, trunking, cable tray, etc.)

FA-Equipment Fire Alarm Equipment (Control Panels, etc. incl. clearance zones & respective data) FA-Devices Fire Alarm devices (sensors, detectors, pull stations, alarms, etc.)

FA-Supports Supports for Fire Alarm System (hangers, etc)

5.3.9 Electrical Lighting

E-Lighting Distribution Lighting System Distribution (conduit, trunking, cable tray, etc.)

E-Lighting-Equipment Lighting System Equipment (Panels, Distribution Boards, etc. incl.

clearance zones & respective data) E-Lighting-Devices Lighting System Devices (Lights, switches, etc.)

5.3.10 Electrical Power

E-Power-Distribution Power Distribution (conduit, trunking, cable tray, etc.)

E-Power-Equipment Power Equipment (panels, disconnects, generators, transformers, etc.

incl. clearance zones & respective data) E-Power-Devices Power Devices (receptacles, etc) E-Supports Supports for Electrical Systems (hangers, etc.)

5.3.11 Electrical Lightning Protection, Grounding & Cathodic Protection

E-Ltng-Prot-Distribution Lightning Protection Distribution E-Ltng-Prot-Equipment Lightning Protection Equipment (incl. clearance zones & respective data) E-Ltng-Prot-Devices Lightning Protection Devices E-Grounding-Equipment Grounding System Equipment (incl. clearance zones & respective data) E-Grounding-Devices Grounding System Devices

5.3.12 Telecom Data/Network Systems

T-Data/Ntwk-Distribution Data Distribution (cable tray, etc.)

T-Data/Ntwk-Equipment Data Equipment (servers, control panels, etc. incl. clearance zones & respective data) Distributionasdfasdf Data Devices (data ports, etc.)

T-Supports Supports for Telecom Systems (hangers, etc.)

5.3.13 Telecom Mass Notification

T-MN-Distribution Mass Notification Distribution (conduit, trunking, cable tray, etc.)

T-MN-Equipment Mass Notification Equipment (control panels, etc. incl. clearance zones

& respective data) T-MN-Devices Mass Notification Devices (speakers, etc.)

5.3.14 Telecom Security

T-Security-Distribution Security Distribution (conduit, trunking, cable tray, etc.)

T-Security-Equipment Security Equipment (servers, control panels, etc. incl. clearance zones & respective data) T-Security-Devices Security Devices (cameras, sensors, etc.)

5.4 Civil / Site

The Civil BIM may vary in the amount of detail for individual elements, but at a minimum must include all features that would be included on a 1” = 100’ scaled drawing. Additional minimum BIM requirements include:

5.4.1 Terrain (DTM)

All relevant site conditions and proposed grading shall be modeled with the necessary intelligence to produce accurate Project site topographical plans and cross sections.

5.4.2 Drainage

Drainage shall be modeled to include all existing and new drainage piping, including upgrades thereto, and shall contain the necessary intelligence to produce accurate plans and profiles for the Project site.

5.4.3 Storm Water and Sanitary Sewers

All existing and new sewer structures and piping, including upgrades thereto, on the Project site shall be modeled with the necessary connection to mains or other distribution points as appropriate, including necessary intelligence to produce accurate plans and profiles for the Project site.

5.4.4 Utilities

Utilities will be modeled with all necessary new utility connections from the Project building(s) to the existing or newly created utilities, and all existing above-ground and underground utility conduits, containing the necessary intelligence to produce accurate plans and site-sections.

5.4.5 Roads and Parking

The model will include all necessary roadways and parking lots and/or parking structures, with the necessary intelligence to produce accurate plans, profiles and cross-sections.

5.4.6 Geographic Referencing

The Civil/Site BIM shall include geo-referencing to accurately locate the building within the site.

The display of the linked Building BIM’s shall provide rotation & positioning of the linked files to assure accurate placement in the context of the site, without affecting registration of the various files composing the aggregate BIM.

The Civil/Site BIM shall include a geo-reference to accurately locate the buildings within the site and to give them a physical location context at larger scales. The Civil/Site BIM shall geo-reference site plans for site layout surveying and future GIS use in accordance with the State Plane Coordinate system where the project is located. Once the project’s geo coordinates are set in the model, they may not be changed without consent from the FAA.

5.5 Indoor Air Quality (IAQ) Management Plan

The project shall include an IAQ management plan that links the BIM design information to testing procedures during construction.

6. PROJECT DIRECTORY STRUCTURE (FAA’s Post-Construction Document Storage) The primary goal of the Project Directory Structure is to improve coordination among all Stakeholders and their consultants, as well as to develop consistent BIM projects in a way that will facilitate the further use of the electronic information for all FAA stakeholders through the facility life cycle.

6.1 Facility Folder

When the project is handed over to the FAA, files shall be uploaded into the ProjectWise EDMS. The Facility Folder will be updated to store the As-Built BIM and supporting documentation in the standard folder structure as shown below:

FACILITY As-Built Record CAD BIM As-Built Record BIM files RECORD As-Built Record PDFs

CM

REFERENCE Graphic Reference for CAD and BIM PROJECTS JCN Specific CAD BIM JCN Specific BIM RECORD JCN Record PDFs REFERENCE Graphic References for JCN CAD and BIM

SUPPORT

DOCUMENTATION Documentation pertaining to the facility, IT, O&M Manuals, etc.

PHOTOS

Figure 6-1, Facility Folder Structure

6.2 Configuration Management (CM) Folder

Each Configuration Management (CM) folder will store the most recent Project CM requirements for that facility.

CM information provided to the Project Lead in submittal format and contained in the BIM will include requirements for:

• NAS System Interface

• Electronic Interface

• Electric Bus

• Configuration Managed Component Equipment

6.3 Projects Folder

Each Project Folder will store the most recent Project Requirements for that facility.

Project information provided to the Project Lead in submittal format and contained in the BIM will include requirements for:

• Project Siting

• Facility Sizing Requirements (room sizes, height, etc.)

• HVAC Size & Type

• Power Capacity & Redundancy

• Modes of Egress

• Structural Capacities

• Fire Life Safety

• NAS Systems

6.4 Record, Reference, Support Folders

The Record, Reference and Support folders will store the most recent Project Information contained in the Model of that facility. Project record, reference & support information provided to the Project Lead in submittal format and contained in the BIM will include:

• Manufacture Specifications

• Permits

• Earthquake & Flood Zone

• Building Codes

• FAA Specific Requirements

DATA SECURITY AND OWNERSHIP

7. BIM AND DATA SECURITY

The models shall be set up and maintained in compliance with the FAA’s established Information Technology and Modeling security protocols. The Design Teams and Contractors shall further take necessary steps to prevent any possible data corruption, virus “infections”, and data misuse or deliberate damage by their own employees or outside sources.

8. DATA OWNERSHIP

The FAA shall have ownership and rights to all BIM files, CAD files, images and any other files used to develop the project design using Revit, and associated facility data developed for the project in accordance with AMS Clause 3.5-13.

BEST PRACTICES AND ADDITIONAL RESOURCES

9. BEST PRACTICES AND PROCEDURES

The following best practices and procedures should be incorporated into all FAA BIM projects:

9.1 General Guidelines

When creating the project BIM consider how the following characteristics will affect the BIM’s performance:

• Complex Geometry

• Size and scale of the design with respect to model organization

• Multiple parametric relations

• Multiple constraints

• Linked Files

• BIM platform category or layer centric

9.2 Software Performance

Only FAA approved software applications may be used together to create, validate and deliver the

BIM.

The software being used by all subcontractors shall be approved by the design team to:

Ensure applicability & compatibility with the approved BIM software.

Keep a complete listing including versions of all software tools used for the project.

Track which subcontractors and design disciplines are using each software tool.

Obtain concurrence from the FAA prior to using new tools. This includes obtaining concurrence prior to upgrade of Revit version used during the project.

9.3 Compacting Files

Compact central and local files to reduce file sizes when saving. Remove obsolete and/or unused families to reduce file size. Eliminate all unresolved clashes prior to submission to the FAA.

9.4 Creating the BIM

• Many facility types within the FAA are based on prototype designs. Determine if a prototype

BIM exists for specific projects prior to beginning the project.

• Until component types are determined, use the generic versions of elements such as walls, doors, HVAC, electrical panels, pumps, lights, etc. which incorporate less geometry.

• Create coordinated discipline BIM with multiple small models to assure file sizes do not get too large to perform simulation or transfer data within a reasonable time frame.

• Regularly review and fix warnings and errors.

• Minimize the number of linked or imported DWG files.

• Only link essential DWG files into necessary views.

• Remove links of all types if not used.

• Turn off shadows in views where they are not necessary.

• Close unnecessary windows.

• Maintain naming conventions that are consistent with the FAA Terminal Facilities design manual.

• Preserve Design Options only as long as they are useful to the project.

• Consider whether options should be preserved long-term in separate BIM that can be linked as needed.

• Maintain correct categorization of all components

• Assign object/component/element characteristics, material definitions, and other basic qualities directly to the objects.

• Associate/host model content to appropriate geometric plane/datum or model component

(Wall, Ceiling, Floor, etc.) to avoid excessive offsets.

9.5 Creating Views in the Model

• Avoid manually drafting elements where there is a tool available for modeling the element.

• All views (floor plans, elevations, sections, details, etc.) shall utilize model content to the greatest extent possible.

• Contract (Construction) Drawings (Sheets) shall be created utilizing views derived from the model(s) to the greatest extent possible.

• Additional drafting may be applied to modeled elements in certain views to provide further detail.

• Schedules shall be derived from modeled content and data contained in each modeled element.

• Drafting Views, where information is created with standard linework, text, and dimensions should only be used for “standard details” which describe typical construction means and methods utilized in the project’s design.

9.6 Project Execution Plan (PxP)

The PxP should contain details for the following areas:

• Coordinate PxP among subcontractors prior to submission to FAA.

• Tailor BIM to be specific to the project.

• Develop a quality control plan identifying responsible party and frequency of reviews.

• Identify responsible party for primary activities.

10. APPENDICES

10.1 Acronyms & Glossary of Terms

Definition of the acronyms and terms used in this document:

Acronym Full Name AE Architecture / Engineer, Architectural Engineering ATO Air Traffic Organization BIM Building Information Model(ing), Building Information Management BxP BIM Execution Plan CAD Computer Aided Design CAEG Computer Aided Engineering Graphics CM Configuration Management COBIE or COBie Construction to Operations Building Information Exchange CPC Critical Power Centers DTM Digital Terrain Model DP Distribution Panel EDMS Electronic Document Management System FAA Federal Aviation Administration FFE Furniture, Fixtures, Equipment FIM Facility Information Model / Management GC General Contractor GIS Geographical Information System IFC Industry Foundation Class JAI Joint Acceptance Inspection JCN Job Control Number LCN Logistic Control Number LOBs FAA Lines of Business LoD Level of Development, Level of Detail LRU Lowest Replaceable Unit ODBC Open Database Connectivity NextGen Next Generation ATO Air Transportation Systems NFPA National Fire Protection Association PSG Power Services Group PxP Project Execution Plan

10.2 BIM Data Requirements by Discipline / Worksets / Components

• Facility Data for a current submittal shall include data required at previous submittals, revised as necessary to the current phase.

• Component size & Product Data shall match Manufacturer cut sheets as submitted in Basis of Design Specifications, and the updated PPD during Design phases.

• Component size & Product Data shall match Manufacturer cut sheets as approved during the Construction phase.

Architectural

Workset Component Data Required

PPD / 10% 45% 70% 100% Final As Built

A-Space Room / Space Workset, Assembly Code Rm#, Schedule Data --- --- --- ---

A-Flooring System above Structural Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Wall Wall System Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Temporary Wall Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Demountable Wall Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

Toilet Partitions Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Opening Doors Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

Windows Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

Louvers Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Ceiling Ceilings & Soffits Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Roof Insulation & Membrane Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

Roof Specialties Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Circulation Elevator Workset, Assembly Code Mark, Type, Rm#, MEP Connection Req’s. --- Mfr, Model --- Revised As Built

Stairs Workset, Assembly Code Rm# --- --- --- Revised As Built

Stair Treads/Risers Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Escalators/Moving Walks Workset, Assembly Code Mark, Type, Rm#, MEP Connection Req’s. --- Mfr, Model --- Revised As Built

Ladders Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Guards & Rails Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Plbg-Fixtures Plumbing Fixtures Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-RR Accessories RR Accessories Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Casework Cabinets & Counters Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-Specialties Architectural Specialties Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

A-FE Specialties FE Specialties Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

Interiors

I-System Furniture Systems Furniture Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

I-Furniture Relocatable Furniture Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

I-Equipment Equipment Workset, Assembly Code Mark, Type, Rm#, MEP Connection Req’s. --- Mfr, Model --- Revised As Built

I-Plant Interior Plantings Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

I-Artwork Art Objects Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

I-Signage Signage Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

Structural

S-Foundation Footings & Pads Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Piles Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Pile Caps Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Grade Beams Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Retaining Walls Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

S-Floor Framing Beams Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Joists / Trusses Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Decking / Slabs Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

S-Roof Framing Beams Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Joists / Trusses Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Decking / Slabs Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

S-Columns Columns Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

S-Circulation Elevators Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Stairs Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Escalators/Moving Walks Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

Ladders Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

S-Wall Structural Wall Workset, Assembly Code Mark, Type, Rm# --- --- --- Revised As Built

S-Glazing Structural Glazing Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

Mechanical

M-Duct-Supply Air Ductwork & Fittings Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-Duct-Return Air Ductwork & Fittings Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-Duct-Exhaust Air Ductwork & Fittings Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-Duct-MUOA Ductwork & Fittings Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-Diff/Grilles Diffusers & Grilles Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-Equipment Mechanical Equipment Workset, Assembly Code Mark, Type, Rm#, MEP Connection Req’s --- Mfr, Model --- Revised As Built

M-Piping Mechanical Piping Workset, Assembly Code --- --- --- --- Revised As Built

M-System-FUEL FUEL Piping Workset, Assembly Code --- --- --- --- Revised As Built

FUEL Equipment Workset, Assembly Code Mark, Type, Rm#, MEP Connection Req’s --- Mfr, Model --- Revised As Built

Fuel Devices Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-System-NGAS NGAS Piping Workset, Assembly Code --- --- --- --- Revised As Built

NGAS Equipment Workset, Assembly Code Mark, Type, Rm#, MEP Connection Req’s --- Mfr, Model --- Revised As Built

NGAS Devices Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-System-LPGS LPGS Piping Workset, Assembly Code --- --- --- --- Revised As Built

LPGS Equipment Workset, Assembly Code Mark, Type, Rm#, MEP Connection Req’s --- Mfr, Model --- Revised As Built

LPGS Devices Workset, Assembly Code Mark, Type, Rm# --- Mfr, Model --- Revised As Built

M-Supports Supports / Hangers Workset, Assembly Code --- --- --- --- Revised As Built

Plumbing

P-DOMW-Cold Water…