MAA BIM Standards

May 15, 2018 Version 1.02

MAA BIM Standards

May 15, 2018 2 Version 1.02

Table of Contents 1 BIM PROJECT MANAGEMENT ....................................................................................................... 5

1.1 Why BIM ‐ MAA Asset Lifecycle Vision ............................................................................................ 5

1.2 Begin with the End in Mind .............................................................................................................. 5

1.3 MAA Digital Process Goals ............................................................................................................... 7

1.4 BIM on Projects ................................................................................................................................ 8

1.5 BIM Kick‐Off Meeting and Model Coordination Meetings .............................................................. 9

1.5.1 BIM Execution Plan Template .......................................................................................................... 9

1.5.2 MAA BIM Uses ............................................................................................................................... 10

1.6 BIM Roles and Responsibilities ...................................................................................................... 11

1.6.1 Required Expertise of BIM Teams (Design, Contractor) ................................................................ 12

1.6.2 Collaborative Work Teams ............................................................................................................. 12

2 SUBMISSIONS ............................................................................................................................ 13

2.1 BIM Deliverables ............................................................................................................................ 13

2.2 Use of e‐Transmit for Models and Documentation ....................................................................... 13

2.2.1 e‐Transmit for Revit Models .......................................................................................................... 14

2.2.2 E‐Transmit Revit Files Best Practices ............................................................................................. 14

3 GENERAL INFORMATION ............................................................................................................ 16

3.1 MAA Referenced Standards ........................................................................................................... 16

3.2 Access to Documentation and Templates ..................................................................................... 17

3.2.1 MAA Approved Software ............................................................................................................... 17

3.3 Data Ownership & Utilization ........................................................................................................ 17

3.3.1 Waiver of Requirements ................................................................................................................ 18

3.4 Quality Assurance and Control ...................................................................................................... 18

3.4.1 Graphic and Data Quality Assurance ............................................................................................. 18

3.4.2 Data Management ......................................................................................................................... 18

4 MODEL REQUIREMENTS ............................................................................................................. 19

4.1 Project Browser .............................................................................................................................. 20

May 15, 2018 3 Version 1.02

4.2 Minimum Modeling for Projects .................................................................................................... 21

4.3 Model Referencing ......................................................................................................................... 22

4.4 Multiple Building Projects .............................................................................................................. 22

4.5 Modeling Tolerances and Dimensioning ....................................................................................... 22

4.6 Geo‐Reference Requirements ....................................................................................................... 23

4.7 Data Integrity and Standards ......................................................................................................... 24

4.7.1 OmniClass Codes ............................................................................................................................ 24

4.7.2 Model Level of Development (LOD) .............................................................................................. 25

4.7.3 Level of Development Definitions ................................................................................................. 26

4.8 Properties and Annotations ........................................................................................................... 26

4.9 BIM Objects .................................................................................................................................... 27

4.9.1 Object Authoring ............................................................................................................................ 27

4.10 Modeling Spaces ............................................................................................................................ 28

4.10.1 Spatial Data ........................................................................................................................... 28

4.10.2 Space Modeling ..................................................................................................................... 28

4.10.3 Door Numbering .................................................................................................................... 29

4.10.4 Space and Room Naming and Numbering ............................................................................ 30

4.10.5 Modeling Space Reservations (Maintenance Review) ........................................................ 30

4.11 Modeling Room Contents – Equipment ........................................................................................ 31

4.12 Equipment Objects ........................................................................................................................ 32

4.13 Schedules and Details .................................................................................................................... 32

4.14 Model Properties ........................................................................................................................... 32

4.15 Legends and Symbols ..................................................................................................................... 32

5 MODEL STRUCTURE, NAVIGATION AND CONVENTIONS ............................................................. 33

5.1 Discipline Model Designations ....................................................................................................... 33

5.1.1 Architecture ................................................................................................................................... 34

5.1.2 Structure ........................................................................................................................................ 35

5.2 Interiors .......................................................................................................................................... 35

5.2.1 Building Systems – Mechanical ...................................................................................................... 35

May 15, 2018 4 Version 1.02

5.2.2 Electrical ......................................................................................................................................... 36

5.2.3 Plumbing ........................................................................................................................................ 36

5.2.4 Fire Protection ............................................................................................................................... 36

5.2.5 Communications ............................................................................................................................ 37

5.2.6 Food Service ................................................................................................................................... 37

5.2.7 Furniture, Fixtures, and Equipment (FFE) ...................................................................................... 37

6 MODEL NAVIGATION .................................................................................................................. 37

6.1 Worksets ........................................................................................................................................ 37

6.1.1 Convention for Three Workset Types ............................................................................................ 38

6.1.2 Project Start Worksets ................................................................................................................... 38

6.2 Model Level Naming Conventions ................................................................................................. 40

6.2.1 View Codes ..................................................................................................................................... 40

6.3 File Naming Conventions ............................................................................................................... 42

6.3.1 Revit Central File ............................................................................................................................ 43

6.3.2 Plot Sheet Files, Drawing Sets and Sheet ....................................................................................... 43

6.4 Folder Structure ............................................................................................................................. 43

7 GLOSSARY OF TERMS ................................................................................................................. 45

May 15, 2018 5 Version 1.02

1 BIM Project Management

1.1 Why BIM ‐ MAA Asset Lifecycle Vision

Building Information Modeling (BIM) and related civil information modeling, herein referred to as BIM,

represents significant changes in the tools, processes, management, and deliverables for Maryland

Aviation Administration (MAA) projects. It is an integrated and comprehensive approach to planning,

architecture, engineering, construction, operations, and facilities management at MAA.

MAA recognizes the National BIM standards definition:

“BIM is a digital representation of the physical and functional characteristics of a facility. BIM is a shared

knowledge resource for information about a facility, forming a reliable basis for decisions during its

lifecycle, and defined as existing from earliest conception to demolition.” – National Institute of Building Sciences

1.2 Begin with the End in Mind

In his best‐selling book, 7 Habits of Highly Effective People,

Stephen R. Covey encourages readers to “begin with the end

in mind”. For MAA, the adoption of BIM is part of a multi‐year

information strategy to develop a common data environment

that supports MAA assets across all lifecycle phases and

business uses, as shown in Figure 1.

MAA has several BIM goals:

Information should be modeled once and at the

quality required for sharing between project teams

across the project lifecycle. 2D documentation will be

derived from an accurate and coordinated model.

The model and the derived documentation provides

the General Contractor (GC) with unambiguous and

accurate information for bidding and construction,

reducing the number of RFIs and change orders, and

ensuring information accuracy and quality.

MAA will utilize BIM on projects to provide stakeholders a greater understanding of how a

project is planned, designed, constructed, used, and managed. This facilitates a more informed

decision process.

FIGURE 1‐ COMMON DATA ENVIRONMENT

May 15, 2018 6 Version 1.02

To maximize BIM MAA, design and construction teams should utilize lean construction

principles,

1 and collaborative model sharing to adhere to MAA project management goals.

Lean Design and Construction Principles:

1. Communicate more effectively across teams.

2. Produce less waste and make fewer mistakes.

3. Improve planning and forward scheduling.

4. Determine value from a customer’s perspective, identify processes that deliver value, and eliminate processes that do not.

5. Drive immediate and apparent change.

6. Provide a cleaner, safer, more effective work site.

7. Continually improve from one project to the next.

1 https://www.leanconstruction.org

May 15, 2018 7 Version 1.02

1.3 MAA Digital Process Goals

It is the intent of MAA to move toward a digital design and construction process for all types of projects

with electronic collaboration, reviews, and submissions. Project teams, A/E, construction, MAA and CMi

should have experience utilizing BIM and digital review tools. Teams should recognize the importance of

normalized data for sharing throughout the project lifecycle.

Figure 2 outlines MAA’s BIM process from planning, design, and bid to construction, handover, and operation.

FIGURE 2 ‐ MAA BIM PROCESS

May 15, 2018 8 Version 1.02

1.4 BIM on Projects

MAA is committed to adopting BIM processes and deliverable requirements for MAA needs, resources,

and asset management goals. Projects will require BIM on an “as need basis”. Table 1 provides

guidelines for BIM requirements on a project.

TABLE 1 – MAA BIM PROJECT MATRIX

May 15, 2018 9 Version 1.02

1.5 BIM Kick‐Off Meeting and Model Coordination Meetings BIM modeling affects the overall design and construction schedule. It is required that the design and construction BIM managers attend project scope and kick‐off meetings to understand MAA project goals, scope of work, and then interpret this into project BIM requirements and uses for the project. A BIM development schedule that supports project requirements and milestones is developed as part of the BIM Execution Plan (BIMxP).

1.5.1 BIM Execution Plan Template

The BIMxP is a required process management document used to track progress towards meeting the

project BIM requirements. The BIMxP is executed by the AE and its consultants, and then the GC and its

sub‐contractors, defining how BIM will be used to meet MAA project requirements. The BIM managers

will use the MAA BIMxP Template. The content of a BIM Execution Plan includes the following:

Project information

BIM goals & uses

Each project member’s roles, staffing and competency

BIM process and strategy

BIM exchange protocol and submittal format

BIM data requirements including additions to the MAA data naming conventions when new instances are added

Collaboration and discipline model referencing procedures for shared Models

Quality control

Technology infrastructure & software

The AE, with the assistance from the MAA BIM manager, will assist in the transition between the design

and construction BIMxP in Design‐Bid‐Build (DBB) procurements. The AE BIMxP must be used as the

basis for the GC BIMxP and will be updated as required by the GC.

May 15, 2018 10 Version 1.02

1.5.2 MAA BIM Uses Table 2 lists MAA’s BIM uses and the responsible parties. This includes the Architectural Engineer (AE),

General Contractor (GC), and Commissioning Team (Cx).

No. BIM USE GENERAL DESCRIPTION AE GC

BIM Uses 1‐13 are required per scope of work. Others may be added and documented in the BIMxP

1 Existing Conditions Modeling

The model/s are developed from field measurement, existing documentation, and laser scanning to produce accurate conditions. Existing conditions are modeled within the discipline model. The AE and the GC are individually responsible for implementing any process or technology required to adequately field‐verify existing conditions needed in the performance of their contractual obligations. (Existing Conditions: Existing Site and Utilities Modeling, Building Extensions, Building Conditions, and Building Systems Locations.)

AE

2 AE ‐ Model Authoring

Various discipline models as a basis of design development, analysis, and construction documentation

AE

3 Visualization and Animations

3D model views developed to more realism supporting stakeholder understanding, public reviews, and decision process

AE

4 Space /Program Validation

Quantifying and classifying of space in model for variations from project space requirements and codes. See section 5.6 Modeling Spaces in BIM standards

AE

5 Fire Safety Review

Model review of fire suppression systems, alarm, with architectural model for interactive FM and Fire System reviews.

AE

6 Design Analysis Analysis of design per scope of work. Required egress plan, vertical circulation coordination, energy, others as required in SOW

AE

7 Constructability Reviews

In‐depth reviews of design for constructability utilizing model, virtual mock‐ups, and details. Use of Navisworks or Solibri Model Checker for “Clash Detection” and data requirements.

AE GC

8 Quantity Take‐Off Reports

Reporting on areas, volumes, square footage, object, and material quantities supporting analysis, validation, procurement, and estimating, and building system analysis

AE GC

9 Phasing‐Design Construction Planning

Use of model internal phasing tools to show design phases, and construction planning.

AE

10 Logistics Modeling

Modeling of phases and representative views or animations supporting stakeholder decision process and GC site planning, material and equipment handling, traffic patterns

GC

11 4D Construction Sequencing

GC Model showing construction phases and project build development over time GC

12 3D Trade Coordination

Use of Model Checking and “Clash ‐ Conflict Resolution” to verify model/s coordination – A Clash Resolution report is a deliverable

GC

13 Facilities Data Turnover

Record Model LOD 300 with accurate COBie Data, GIS Data for FM. AE will update the Record LOD 300 model with COBie data from GC or Commissioning

AE GC

14 Digital Layout Use of laser layout equipment for field layout of walls and other elements in construction.

GC

15 Laser Scanning Use of laser scanning and BIM to develop highly accurate existing conditions or documentation of “As‐Built”

GC

16 Digital Commissioning

Commissioning of the model for data integrity – Use of model in the field during commissioning to verify data

AE Cx

17 Design Analysis and Reporting

All types of analysis including: energy, daylighting, sun studies, LEED, as needed to meet project scope

AE

TABLE 2 – MAA BIM USES

May 15, 2018 11 Version 1.02

1.6 BIM Roles and Responsibilities

The designer and contractor teams shall designate

a BIM manager responsible to MAA for the overall

execution of the project model(s) information,

construction documentation, data development,

quality, and integration of the models for

submissions, as seen in Figure 3. Additional roles

and team members are assigned per the SOW, BIM

uses, and project complexity. Table 3 describes the

BIM roles and responsibilities for MAA, the design

BIM team, and the construction BIM team.

BIM ROLES on MAA PROJECTS

MAA PM MAA PROJECT MANAGER – is the MAA representative with project management and oversight responsibilities on behalf of the MAA. The PM manages all aspects of the project to achieve the project goals. The PM works closely with the MAA BIM M=manager on BIM schedule, deliverables, and data handovers.

MAA CMi CONSTRUCTION MANAGER/INSPECTION – If a CMi is used by MAA, then this group may have oversight and review authority on BIM deliverables including the BIMxP per their SOW.

MAA BIM Mgr

MAA BIM MANAGER – The MAA BIM manager reviews and provides oversight on BIM requirements and deliverables.

MAA Cx COMMISSIONING TEAM – The Commissioning team may request the model or model data for the commissioning process..

AE DESIGN BIM TEAM GC CONSTRUCTION BIM TEAM Design BIM Manager overall execution of the project model/s information, construction documentation, data quality, and collaboration of the modeling teams for submissions

Construction BIM Manager overall execution of the project model/s information, construction documentation, data quality, and collaboration of the modeling teams for submissions

Discipline Modelers

Major disciplines have specific modeling teams with the expertise to develop these models and provide analysis as needed per the project SOW

Fabrication Modelers

Sub‐contractors to the GC unless self‐performed. Use the Design Intent Model and add further detail for construction. May use

tools other than Revit by waiver.

BIM Use Modelers Rendering, Animation, Public Presentations Separate team members may be designated as Visualization task coordinator supporting model visualization products defined per the SOW. Report to the BIM Managers

BIM Use Modelers Schedule (4D), Estimating, (5D) Construction Logistics Visualizations tasks per the SOW, may be coordinated by separate team members. Report directly to BIM manager

QA‐QC – Model Management Separate team members may be designated as QA/QC task coordinator supporting model and data checking, model integration, and other multi‐disciplinary activities reporting to the BIM managers

QA‐QC – Model Management Separate team members may be designated as QA/QC task coordinator supporting model and data checking, model integration, and other multi‐disciplinary activities reporting to the BIM managers

FIGURE 3 – BIM ROLES AND RESPONSIBILITIES

May 15, 2018 12 Version 1.02

1.6.1 Required Expertise of BIM Teams (Design, Contractor) All BIM work for MAA facilities must take place under the formal direction of a BIM design or

construction professional with a minimum of four years of proven experience using BIM for similar

projects of size and complexity, and who can provide examples of competency to execute the

requirements in MAA BIM standards.

BIM Manager (Designer or Contractor) Responsibilities:

Ensure compliance with MAA BIM standards, BIM uses, and required deliverables.

Develop, maintain, update, and provide clarifications to/for the Project Execution Plan (PEP).

Manage model creation, maintain, and review model and data quality control across all firms, disciplines, or trades under the contractual umbrella.

Participate in project kick‐off meeting. Lead and facilitate the BIM management project kick‐off meeting with project team modelers to explain the BIM project objectives and management protocols.

Verifying that the geo‐references in all associated discipline models are properly referenced to the identified project permanent survey point and with each other.

Ensuring regularly scheduled periodic design coordination and/or construction coordination review meetings and coordinating conflict resolution between discipline models.

Coordinating updates of the Design‐Intent model(s) to create the FM Model and delivery of BIM‐derived 2D Drawings and other information as required to support the project delivery process.

Instituting Quality Control (QC) for proper modeling, standards adherence, and classification of all spaces and equipment as required.

1.6.2 Collaborative Work Teams

Model management and integration of the discipline models is integral to project success. Construction

documentation will be derived from a coordinated (clashed) model. At the BIM kick‐off and subsequent

meetings, the design BIM manager will outline the discipline model integration schedule to meet project

requirements. This is documented in the BIMxP. It is the BIM manager’s responsibility to create a

coordination/issue report detailing the resolution of each issue and responsibility of each party. This

coordination report is agreed upon at the BIM Kick‐off meeting and documented in the BIMxP.

Data and Model Handover This task is a joint effort between the Design BIM Manager and the CG BIM Manager for final record model and COBie data handover per SOW.

Data and Model Handover This task is a joint effort between the design BIM manager and the CG BIM manager for final record model and COBie data handover per SOW.

TABLE 3 – BIM ROLES ON MAA PROJECTS

May 15, 2018 13 Version 1.02

2 Submissions

The model shall be developed using the required BIM software supplemented with Computer Aided

Design (“CAD”) content as necessary to produce a complete set of construction documents.

All models and facility/site data shall be submitted in native format required for the project and 2D and 3D PDF as required. The submittals shall be fully operable, compatible, and editable within the native BIM tools.

2.1 BIM Deliverables MAA requires electronic/digital deliverables. The consultant is responsible for seeing that the submitted

files follow MAA standards in the MAA Design Standards, Volume 3, Section 5.

Document classification can be found in MAA Design Standards, Volume 1, 4.14.2 Design Progress

Milestones.

This standard shall apply, but not be limited, to the following submission types regardless of source:

2.2 Use of e‐Transmit for Models and Documentation

MAA requires the use of e‐Transmit for Revit model submissions. The process for e‐Transmit of .dwg files is explained in MAA Design Standards, Volume 3, Appendix H ‐ 5.1.4.2e – Transmit Procedures for Construction Documents.

DOCUMENT CLASSIFICATION TYPES

Construction drawings for new and existing facilities

Design, planning, and record drawings

Installation permit drawings Model files (.rvt Central Model and associated files)

Building permit drawings Design, planning, and record drawings

Space Allocation drawings Data files (COBie Excel spreadsheet)

May 15, 2018 14 Version 1.02

2.2.1 e‐Transmit for Revit Models

The Revit model submission shall use the e‐Transmit for Autodesk Revit add‐in. The service provider must provide a narrative describing how the delivered files are connected and in what order they should be opened so that MAA can open the models without errors. The e‐Transmit file should be tested, and any errors removed before sending to MAA.

UNACCEPTABLE ERRORS

“Error (must be addressed to continue)”

“Can’t obtain permission to edit the element. The Central model is inaccessible”

“Unresolved References. Revit could not find or read n references. What do you want to do?”

“Open Manage Links to correct the problem” does not allow the recipient to point to a file included in the e‐Transmit package

“New shared parameters: id nnnn”

“The File could not be found.”

2.2.2 E‐Transmit Revit Files Best Practices 1. Include related dependent files such as linked models and DWF markups. Include supporting files

such as documents or spreadsheets. 2. Disable worksets. 3. Remove unused families, materials, and other objects from the Revit models to reduce file size. 4. Delete unnecessary sheets, and specific view types so that the models do not contain unnecessary

data. 5. Include only the views that are placed on sheets. 6. Include dependent files. In some cases, not including these files can make the model unusable by

the recipient. 7. Dependent files can be included automatically in the transmittal folder, reducing the possibility of

error. All fully specified (absolute) paths of dependent files are converted to relative paths or "no path" to ensure that the dependent files can be located by the model.

8. Ensure that all models are closed.

These file types are not automatically included in the transmittal folder during the e‐Transmit process.

These files can be manually to the transmittal directory after the e‐Transmit process is complete.

Point clouds

Shared parameter file

Lookup tables

Material rendering images

XRefs linked to CAD models

External font files

May 15, 2018 15 Version 1.02

Table 4 summarizes the MAA BIM deliverables to include the format, delivery method, responsible

party, and timeframe.

MAA BIM DELIVERABLES/SUBMISSIONS

DELIVERABLE FORMAT DELIVERY METHOD

RESPONSIBLE PARTY TIMEFRAME

1 BIM Project Execution Plan (BIMxP)

Excel template Upload to project site

AE GC 30 calendar days after contract award; design submittals and construction milestones

2 Site Survey Information and Utility Locations

Native Format, IFC, Digital 2D PDF

Upload to project site

AE Before Design starts

3 Laser Scans Native Files


AE GC 30 days after scan

4 Blocking & Stacking, Phasing Sequencing (Phasing project dependent)

AVI, MPEG, MOV Upload to project site

AE GC Concept design submittal; construction phasing submittal

5 Design Coordination and Construction Coordination Reports

Navis and EXCEL Upload to project site

AE GC Each design submittal; after each Construction Coordination meeting

6 Design‐Intent 2D Drawings (Building and Site)

DWG, Digital 2D PDF


AE Each design submittal

7 Design‐Intent Model(s) (Building & Site)

Native Format, NWD (or Equal)


AE Each design submittal

8 Final Design‐Intent Model(s) (Building & Site)

Native Format, IFC, NWD, 3D PDF


AE 100% Design

9 Conformed Model Native Format,


AE Updates Design‐Intent Model with Contractor Comments

10 Construction Models, including Fire Protection

Native Formats, NWD (or Equal)


GC Shop models for A/E review and approval

11 Record (FM) Model(s) (Building and Site)

Native Format, IFC, NWD or Equal, 3D PDF


AE Within 60 calendar days of completing drywall on interior partitions

12 As‐Built Drawings (Building and Site)

DWG, Digital 2D PDF


AE Within 30 Days of Completion of FM Model(s)

13 FM Data EXCEL/COBie


AE After Concepts, at each Design Submittal

14 Updated FM Data EXCEL/COBie


GC To AE at Construction Milestones, Final to AE 60 calendar days before occupancy

15 Room Contents List with Equipment Data

EXCEL Upload to project site

AE TBD

16 Final FM Data to Maximo EXCEL/COBie


AE Construction Milestones, Final by Beneficial Occupancy

17 Models to Maximo (Buildings and Site)

Record Model, COBie


AE By Beneficial Occupancy

18 Civil 3D Model (CIM)

Record Model/As‐Built


AE Design and construction milestones, As‐Built

TABLE 4 – MAA BIM DELIVERABLES/SUBMISSIONS

May 15, 2018 16 Version 1.02

3 General Information When used on a project, the BIM standards will supplement current MAA standards and project requirements. BIM standards applies to new and existing facility projects at Baltimore/Washington International Thurgood Marshall (BWI) and Martin State Airports (MTN).

This document is not a Revit tutorial and assumes the user has sufficient BIM proficiency

to comprehend the requirements in this standard. The term model is used when describing the

electronic model deliverable. The term modeling is used when describing part of the process, and the

term uses refers to a required activity such as analysis or clash interference of the model. The term

object is used for both manufactured products (windows, escalators, equipment) and assemblies (walls

or floors).

MAA project standards are continually updated to reflect the changing policies, procedures, and design criteria of the MAA. If any of the standards or requirements contained herein conflict with applicable codes or regulations, or require updating to meet industry best practices, it should be brought to the attention of the BIM manager. Send an email to [email protected].

3.1 MAA Referenced Standards

The BIM Guideline references existing MAA standards to decrease redundancy and conflicts.

Referenced standards include:

MAA Design Standards, Volumes 1‐3

MAA GIS Data Standards

MAA GIS Data Standards – Utilities Supplement

MAA Data Quality Standards

MAA Data Security Standards

MAA Naming, Identification & Addressing Standards

MAA CADD Standards

National BIM Standards (NBS)

COBie – (Construction Owner Building Information Exchange)

OmniClass ‐ Construction Specification Institute (CSI)

NBS Level of Development (LOD) – Associated General Contractors (AGC)

May 15, 2018 17 Version 1.02

3.2 Access to Documentation and Templates

The MAA website provides access to current MAA Documentation for designers, consultants, and

contractors. The address is https://www.airportal.maa.maryland.gov. Available content is listed in Table

5, below.

3.2.1 MAA Approved Software MAA has adopted Autodesk Revit software for BIM Projects. Any other software application (third party) shall be approved by MAA before use. The BIM execution plan (BIMxP) shall document all BIM software used on the project. Approved software is show in Table 6, below.

3.3 Data Ownership & Utilization

MAA shall have ownership of all CAD files, BIM models, and facility data developed for the project. MAA

reserves the right to make use of this data for any purpose it desires.

MAA places significant importance on the accurate creation and management of building information data during design and construction and handover of the data deliverables at project completion. This information supports MAA facilities and asset management, operations, and maintenance.

ADDITIONAL AVAILABLE CONTENT

Current CADD standard MAA Design Manual

Linetypes MAA Signage Symbols

Symbols Plot Styles (ctb)

Logos Standards Borders

MAA Additional Topographic Symbols

Layer Template – X000‐Geom.dwg

Standards Title Block, Index Sheets BIM Execution Plan Template

APPROVED SOFTWARE APPLICATION NAME

BIM Authoring Tool Autodesk Revit Building Suite (Architecture, MEP, Structure)

CIM Authoring Tool Autodesk Civil 3D

Model Checking Tool Navisworks

Drawing Submissions e‐Transmit

Document Review BlueBeam and Autodesk Design Review

Animation/Visualization 3D MAX, Lumion, BIM123

TABLE 6 – APPROVED SOFTWARE

TABLE 5 – AVAILABLE CONTENT

May 15, 2018 18 Version 1.02

3.3.1 Waiver of Requirements Project situations may arise where a modification to the MAA standards is in the best interest of the project. In such situations, a written waiver identifying the purpose, deviation, and alternative must be submitted to the MAA BIM manager for approval prior to use. The decision of the MAA BIM manager will be final on any changes. The AE and the GC will document any approved waivers in their BIMxP.

3.4 Quality Assurance and Control

The Architect/Engineer (AE) is responsible for model and data conformance to MAA standards across all

discipline models. Models and data must be submitted per the delivery schedule per the BIMxP. MAA’s

BIM manager will review and comment on BIM submissions throughout the project. The construction

management and inspection firm (CMI) may also have review responsibilities.

If the model organization, data, and modeling quality do not follow MAA standards and the agreed upon requirements in the BIMxP, then the MAA BIM manager will reject the model submission, and the AE or GC will resubmit the revised model within 15 business days.

3.4.1 Graphic and Data Quality Assurance

The value of BIM data is maintained by following MAA data requirements and industry modeling best

practices. The BIM managers and modelers have the responsibility to review and check models for

graphic and data conformance to the MAA CADD and BIM requirements throughout the project

lifecycle. Clash/coordination and data reports are project deliverables.

Drawings shall conform to the MAA CADD standards unless the graphic representation cannot be created in BIM. Example: Fire rated wall graphic for 3D/2D representation. If such a situation arises, the design BIM manager shall contact MAA BIM manager and propose a solution for approval.

Construction documentation drawings (plans, sections, elevations, major details, schedules) are derived from the model. MAA provided or approved details may be used as appropriate.

3.4.2 Data Management

MAA building, space, and equipment data are strategic assets that must be maintained to preserve

value. Team members working on MAA projects must ensure that data standards, nomenclature,

OmniClass and COBie 2F

2 are maintained during project development, submissions, and the transfer

between software applications. MAA uses the following data standards:

MAA will use the NBS COBie Format to transfer information from BIM to Maximo (MAA’s asset management system).

2 Construction Operations Building Information Exchange (COBie)

May 15, 2018 19 Version 1.02

COBie – a reduced data set identified in the COBie spreadsheet.

Level of Development (LOD) – AGC3F3 and NBS4F4 standards for graphic detail and data reliability. Use current version distributed by AGC. http://bimforum.org/lod/.

BIM to GIS handover. MAA Design Standards, Volume 3 – MAA GIS Data Standards. NCS Standards (NCS), current version.

Layers commonly used by MAA are listed in Appendix 1 of the MAA Design standards. Additional names as defined by the NCS shall be used as needed, in a manner that is consistent with their definitions. No other layers shall be used without prior written permission from MAA BIM manager.

4 Model Requirements

The Design Intent Model should consist of a collection of Revit and Civil 3D files created in a common coordinate system by the design team and used to produce construction drawings. Figure 4, above, illustrates the various model views in a BIM file. The design intent model should meet the following requirements:

Developed to LOD 300. Architecture, structure, and MEP models should be created in Revit. Civil model should be created in Civil 3D. Project origin should be clearly defined at the intersection of major grid lines and should be

used to link all trade models.

3 Associated General Contractors

4 National Institute of Building Sciences

FIGURE 4 ‐ MODEL VIEWS

May 15, 2018 20 Version 1.02

Context Revit site model should be created using shared coordinates and aligned with world coordinates established in civil files.

Structure and MEP files should acquire coordinates from linked architecture model. Preliminary coordination and clash detection should be performed throughout design stage of

the project. All MEP Systems should be connected. Workset organization, project browser organization, system types and names, phases, and

phase filters should comply with facility BIM requirements. Model geometry should be simplified and optimized for exports into polygon‐based

applications. In place families, model lines and groups should be avoided at all costs and should be used only

with client consent.

The Conformed Model should consist of a collection of adjusted design intent model files based on contractor review and design verification. The conformed model should meet the following requirements:

Developed to LOD 300. Original design intent model should be used to create conformed model. Should be used to create revision sheets containing design intent changes. All requirements of design intent model should be met.

The Construction Model should consist of a collection of model files created in special fabrication and shop drawings authoring applications with high accuracy and high level of detail. This model is used during construction. Each model should be exported to Navisworks model format (NWF) to be federated into the as‐built model. The construction model should meet the following requirements:

Developed to LOD 350 ‐ 400 as defined in BIMxP. Construction trade models should be created in special fabrication and shop drawings

applications (Tekla Structure, CAD MEP). For all trades that will not provide fabrication/trade models, conformed model (Revit) should be

adjusted and used to perform 3D coordination and clash detection.

4.1 Project Browser MAA requires a uniform project browser organization for all design teams and utilizing the same standards across all disciplines to ensure consistency between projects and files. The design intent model produced by the design team will be utilized long after design is completed and will be used for review, QA/AC procedures, construction management, and facility management. Proper project browser organization must be consistent across all projects and disciplines to streamline model review and verification by the client.

General Requirements:

All MAA Revit projects should contain default project browser organization present in MAA Revit template (category/subcategory).

May 15, 2018 21 Version 1.02

The default project browser organization for views, sheets, and schedules must be based on two project parameters: category and subcategory.

All view organization should sort the views by associate levels.

All views, schedules, and sheets in the Revit file should be categorized according to their purpose (function): administration, coordination, documentation, design review, design authoring, exports.

Additional views, schedules, and sheets categories might be added if agreed with a client and reflected in the BIMxP.

All views, schedules, and sheets should be named according to the naming conventions.

View Organization Requirements:

Any Revit file should contain at least three mandatory categories of views in the project browser:

administration, coordination, documentation.

If necessary, additional categories for views can be added during the project in accordance with best practices.

The category of administration views should contain at least three main subcategories: levels, worksets, and categories.

The category of coordination views should contain primary overall building working floor plans, elevation, and sections and should be divided into the corresponding subcategories.

The documentation views category should be divided into subcategories that represent the sheet index number of the corresponding construction documents: A01, A02, S01, etc.

When working with phases in a project, additional mandatory project browser organization should be created: phase/category/subcategory, sorting the views by their phase.

If several design disciplines are present in one model file, additional mandatory project browser organization should be present: discipline/category/subcategory, based on the discipline view parameter.

Each Revit file should contain mandatory views that help with model management, verification, and audit. Each model should contain the following views:

Category views: Views that contain certain isolated individual Revit categories. One per category. Limited number defined by the owner.

Level views: One view per level, directly connected with corresponding levels and sharing their names.

System view: Views with isolated mechanical, electrical, and plumbing system types. Workset views: Views that contain isolated individual user defined worksets. One

workset per view.

Sheets Organization Requirements: There are two mandatory sheet categories in the project browser—administrative and documentation. The subcategories of the sheets under the documentation category should be divided based on the construction document sheet index: A01, A102, S01, etc.

4.2 Minimum Modeling for Projects All elements within the scope of work (SOW) and within the limits of the construction site or affected by construction must be modeled, including but not limited to:

May 15, 2018 22 Version 1.02

Building structures, equipment, and building systems

Utilities above or below ground inside and outside to service connections

Construction details unless supplied by MAA

Major landscaping areas to be preserved

Any areas to be protected during construction

Project site conditions affecting safety, logistics, or public outreach

Equipment needed for facilities maintenance

Space reservation for maintenance

Existing conditions modeling

4.3 Model Referencing All discipline models must be referenced to each other, and the process described in the BIMxP, to ensure proper coordination (lighting to ceiling, utility hookups, structural support, etc.) between disciplines.

4.4 Multiple Building Projects There is only one building per file. If multiple buildings are part of the SOW, then a composite model file is created per SOW.

Duplication of the file structure shall be created for each building.

The composite model where individual building models are referenced into a site/civil model shall integrate the multiple building model files for delivery.

Model files may be saved for integration into GIS, building shell, foundation, major equipment, column grid, spaces.

4.5 Modeling Tolerances and Dimensioning Building objects must be modeled in their exact location within the industry standards tolerance with no case greater than 1/2”. All 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 the BIMxP or as needed to execute fabrication, laser lay‐out or installation.

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

May 15, 2018 23 Version 1.02

affecting current and future modeling must be documented in the BIMxP. Exceptions must be approved by MAA BIM manager and documented in the BIMxP.

Dimensions must comply with MAA CADD Standards graphics. Dimensions must be automated, object referenced and associated, and must not be overridden. Dimensional values (i.e., the text appearing in dimension strings) will be in Imperial Units (e.g., 10’‐0”).

4.6 Geo‐Reference Requirements MAA requires that all models contain geospatial information that is properly referenced between a permanent, physical, USGS survey markers geographic survey point available in the state plane coordinate system, and the coordinate system within the project itself. This gives a precise, measurable reference points for accurately locating and constructing buildings, site work, utilities, and infrastructure. The survey points are available in the MAA Survey document. Because of the importance of tying the model to an actual, physical point in space so they can be referenced properly during construction and for other purposes, ALL models must be correctly geo‐referenced and fulfill following requirements: All Revit files in the design model should have properly established project and shared coordinate systems. Project Coordinate System Requirements:

For each building, the project coordinate system should be established by placing the major grid line intersection at hardcoded Revit origin.

Each building in the project should be located orthogonality relative to the project north independent of true north orientation.

One of the building levels should be aligned with the hardcoded Revit origin and have elevation equal to “0” relative to the project base point.

All Revit files related to the same building should be linked “Auto ‐ Origin to Origin” only, to share the project coordinate system.

May 15, 2018 24 Version 1.02

Shared Coordinate System Requirements:

Each project should contain a Revit site context model with an established shared coordinate system aligned with Civil 3D files. This file should be used to properly position buildings in space relative to other buildings and structures located on site.

Shared coordinates should be established within the site context model in a way that all model elements or linked files are located within a 2‐mile radius from the hardcoded Revit origin in the site context model.

Major Civil grid line intersection should be aligned with hardcoded Revit origin and site project base point coordinates should be populated based on Civil grid line values.

For each architecture Revit file, a shared coordinate system should be established by placing the Revit file into the site context model, aligning it to the proper position in space (true north orientation, building elevation), and publishing the shared coordinate system back to the file.

All discipline Revit files should acquire the shared coordinate system from the linked architecture model.

4.7 Data Integrity and Standards Data must be developed using MAA standards so that information may be used throughout the facility lifecycle. Unique GUIDs 5F

5, assigned in the BIM tools, must be maintained throughout project development and delivery to support data workflows that require keeping track of space and equipment.

4.7.1 OmniClass Codes OmniClass Building Classification Tables published by the Construction Specification Institute (CSI) must be assigned to all spaces, building equipment, building systems, and underground utilities. Spatial objects and areas must maintain MAA naming, abbreviations, and codes. If a new space has been created or does not have an OmniClass identification, then the appropriate OmniClass code must be applied per the OmniClass system logic. The following tables must be used:

OmniClass Tables 13 and 14 in combination for spaces

OmniClass Tables 21, 22, and 23 for building assets Table 21 for systems Table 22 to align modeled technical solutions with specification sections Table 23 for building equipment

5 GUIDs are the unique identifier within Revit for all elements.

May 15, 2018 25 Version 1.02

4.7.2 Model Level of Development (LOD) The AGC BIMForum 6F

6 and NBS 7F

7 have jointly expanded the Level of Development (LOD) specification for BIM. A copy of the AGC LOD specification is available on the AGC webpage http://bimforum.org/lod/ Model objects should be clearly identified and carry the level of accuracy of placement assigned to the LOD number. LOD defines the graphic complexity and data reliability of a BIM object. The LOD of objects is defined in the BIMxP for MAA. Figure 5, below, illustrates the differences between a floor plan with an LOD of 100, 200, and 300.

Graphic Accuracy MAA requires the design team to accurately model the locations of objects so that the constructor can use the model with confidence into shop drawings. Examples include: Door offsets, outlet heights, walls on slabs and proper height, ceiling tiles with referenced lighting fixtures from MEP model. These locations should be reviewed by the design team as part of QA/QC and submit models with accurate object placement and relationships. The accuracy of placement can be more important than a highly detailed object. Data Reliability Utilize LOD to define the reliability of required information. At 100% documentation and final design intent, all elements should be at an LOD 300 in terms of graphic accuracy and data reliability.

6 Associated General Contractors BIMForum – Group within AGC developing the LOD specification

7 National Institute Building Sciences

FIGURE 5 – LOD FLOOR PLANS

May 15, 2018 26 Version 1.02

4.7.3 Level of Development Definitions

LOD 100 – No model information, not accurately placed or identified. LOD 200 – At this LOD elements are generic placeholders. They may be recognizable as the components they represent, or they may be volumes for space reservation. Any information including placement derived from LOD 200 elements must be considered approximate. LOD 300 – Elements are accurate. The quantity, size, shape, location, and orientation of the element as designed can be measured directly from the model without referring to non‐modeled information such as notes or dimension call‐outs. The project origin is defined, and the element is located accurately with respect to the project origin and nearby or attached elements. Ex. Doors are modeled with an accurate offset.

LOD 350 – Used for shop model and construction model accuracy

Figure 6 illustrates the differences between LOD 100, 200, 300, 350, and 400 in objects and systems.

4.7.3.1 LOD 400 and 500 Use

LOD 400 ‐ Represents modeling and data of the As‐Built condition. This is higher than is necessary for MAA facility and operations which requires LOD 300 for most graphics with accurate data. MAA requires the NavisWorks model at LOD 350‐400 as a deliverable. Access to the LOD 400 model (Navis model from GC) is needed by MAA for repairs or remodeling.

LOD 500 is not required in MAA BIM standards. MEP models include all piping and components to 1” and with required FM data. LOD 500 is for critical systems and when required this LOD will be defined within the Scope of Work.

4.8 Properties and Annotations The model(s) and objects must contain the appropriate non‐graphical properties to accurately automate annotation tags, generate schedules and COBie data from the model. All general annotations must comply with the MAA CADD standards graphics. Where the MAA standards does not explicitly define a standard for an annotation, the latest version of the National CADD standards applies. The models must use the appropriate tool within the BIM software designed for that purpose.

FIGURE 6 – LOD OBJECTS AND SYSTEMS

May 15, 2018 27 Version 1.02

All references including but not limited to elevations (interior or exterior, partial, or whole), sections (building, wall, or object), plan, and detail callouts or marks must be created using the appropriate tools/commands from within the BIM software and remain dynamically connected throughout the project. Manual overrides are not permitted.

Title block identification values (e.g., sheet number and sheet name) must be associated and automatically populated and remain current throughout the project. Annotation symbols such as tags are to read, and display information contained within the model properties. 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.

4.9 BIM Objects The term BIM object encompasses areas, elements, components, and systems. The basic concept refers to an individual item, or a collection of items, that comprise the model(s) for the design of the facility and the site. All BIM objects and categories must be named in accordance with OmniClass product descriptors found in OmniClass Tables 21 and 22. 4.9.1 Object Authoring All new objects must be modeled or created using the tool, family, and type within the software that is designed to be used for that specific object or purpose. For example, a BIM software’s wall tool must be used to create a wall. A wall is not permitted to be merely drafted lines. New Object Criteria Objects must be designated as the real‐world element it represents, with proper classification and/or data attributes for the project and object type and must report properly from the software as the objects they represent rather than unassigned graphic primitives. This allows associated information to be properly updated, reported, and available for export and reuse. Generic, miscellaneous, or unspecified categories are not allowed.

Global properties must be used where appropriate to increase modeling value and performance.

The attribute of any given object will reference global properties for its respective category. For example, a width property for one piece of equipment must use the same global properties designated as width for all equipment within the same category. Additional properties denoting the same attribute with slight variations must not be created (i.e., width1, object width, etc.)

Use BIM authoring software object libraries when creating objects whether they are actual 3D objects or 2D representations. Models must be comprised of the software’s objects for

May 15, 2018 28 Version 1.02

representing building products. Geometric lines, arcs, and vertices are not allowed. This is necessary to enable classification and reference keynoting, such as the Unified Facilities Guide Specification (UFGS) or MASTERSPEC number.

4.10 Modeling Spaces Spatial objects are defined as rooms, departments, areas, mechanical spaces, and zones that are typically a part of the architectural, mechanical, electrical, plumbing, fire protection, security, and communication technology, or interior design models. All spatial objects must be generated with the appropriate tool and associated with bounding elements (walls, doors, windows, floors, columns, ceilings). All properties information associated with spatial objects appearing in schedules, exports, tags, and diagrams, must be fully generated from, and connected to the model geometry which defines its boundaries.

4.10.1 Spatial Data Spatial data includes the properties of the spatial object and applies to areas of four square feet or greater. Model submissions at end of study and design development phase must contain data to generate a tabular calculation from the model for comparison with the proposed project program space requirements. The spatial object and data must be maintained throughout project lifecycle.

4.10.2 Space Modeling8 Area and spatial objects shall be modeled to meet the MAA space measuring standards in the MAA Design Standards Manual. Rooms: The Net Square Footage (NSF) must be modeled for each functional room and space. Rooms must be represented and broken down into functional areas even though they may be parts of a larger designed physical area. A physical area may contain several functional areas that are treated as individual “rooms” in the spatial program. If two rooms have different functional space classifications, even though they are within the same physical area, they must be modeled as two separate spaces. For example, a security checkpoint area that is not enclosed by walls must be defined as two separate non‐overlapping spaces. These spaces might also be grouped into a zone for visualization and analysis purposes (e.g. for thermal simulation calculations). Operational Areas, Airline Departments, Leased Spaces, Security: The MAA will define the organizational arrangement for providing services. Rooms must be grouped into departments for space

8 MAA uses BOMA space standards for modeling spaces and determining square footage.

May 15, 2018 29 Version 1.02

management and square footage analysis. They shall be color coded to help distinguish space belonging to the different organizations.

Circulation, Egress Calculations: Must be calculated based on the spatial values derived from the floorplates in BIM.

4.10.3 Door Numbering MAA utilizes door numbering as a primary data point. The room number is used for the space number. Each door (or opening designated as a door), regardless of type, will be assigned a unique door identification number, as shown in Figure 7.

TERMINAL LOCATION CODES

A

Concourse A SKY Skywalks and Towers

B Concourse B AT A‐B Terminal, Pier A side

C Concourse C BT A‐B Terminal, Pier B side

D Concourse D ST South Terminal

DX Concourse DX CT Center Terminal

DY Concourse DY NT North Terminal

E Concourse E NTE North Terminal, Pier E side

DOOR NUMBERING CONVENTIONS

Door Number [A]<S>[##][####]<#c>

[A] Terminal location code

<S> <Optional> S to indicate Stairwell

[##] Two‐character level/floor indicator (LL, UP, L1, L2, etc.)

[####] 2‐4‐digit door number (E Terminal door numbers are 4‐digit, all others are 2‐3)

<#c> <Optional> Door letter suffix

FIGURE 7 – DOOR SYMBOL

TABLE 7 – TERMINAL LOCATION CODES

May 15, 2018 30 Version 1.02

Vestibules Numbering Vestibules along the terminal roadway are numbered 1‐18 (lower level) and 1‐20 (upper level), starting on the Terminal A‐B side. All Other Doors and Doorways All other doors, interior and exterior, are numbered using the same convention as above.

4.10.4 Space and Room Naming and Numbering Functional spaces are named using a combination of the door numbering convention, terminal location table, and OmniClass tables 13 and 14. This information should be incorporated into the room tag and the room/space schedule. The door number is used to identify the room space. Additionally, an OmniClass space type will be added as a functional space classification.

4.10.5 Modeling Space Reservations

(Maintenance Review) The AE and the GC must model space reservations (clearance space and zones) to show access to mechanical, electrical, plumbing, fire protection, security, and communication technology, building equipment and distribution systems, and coordinating the locations and access to systems that are installed after major building systems are put into place, such as communication technology (low‐voltage), business systems, and fire protection systems. These space objects should be grouped in such a manner as to allow them to be hidden for some uses. Space reservations must be included in all design and construction coordination management activities. Space Reservation Modeling: Space reservation zones must be modeled with 3D transparent (volumetric) shapes. Transparency must be between 65% and 85%. They should be labeled by discipline, color coded, and designated “Not in Contract” (when applicable) in the model and plans.

FIGURE 8 – GENERAL AND SPECIFIC SPACE USES

May 15, 2018 31 Version 1.02

Space reservations must accommodate:

Operations, adequate physical and tool/tool cart access (including unobstructed paths of travel) for repair, maintenance, and replacement.

Major equipment removal, equipment replacement pathways to access hatches, knockout panels, doors, and hoists, and access to equipment, systems, and attachments located above ceilings.

Space accessibility reservations for code requirements, manufacturer’s maintenance zones, equipment specifications, and any manufacturer specific design requirements.

Space Reservation Use During design coordination, space reservations must be based on the maximum anticipated size of the equipment, as seen in Figure 9 above. Model routing reservations accordingly. The General Contractor’s Construction Coordination Space reservation settings must be based on the actual access requirements of the system or equipment selected or managed (e.g., Fire Protection) by the GC for installation. The GC must confirm with MAA Maintenance the routing and sizes needed for business systems, etc., and assure that the space reservations for those systems are not encroached. MAA will approve the final routing and space reservations; the GC must install the building systems to the approved construction coordination locations. Examples must be modeled as a space reservation and included in design and construction coordination (each project must have these systems identified)

4.11 Modeling Room Contents – Equipment Room areas, furniture, fixtures, and equipment (FF&E) are categorized by type, utility requirements, coordination with the GC, and third‐party providers. System equipment must carry the appropriate properties for COBie.

SPACE RESERVATION MODELING

• Low‐voltage systems • Radio/Wireless • IT system components • Video • Internet/WIFI • Security • Telephone • Wayfinding – Signage • Public Address • Television –Information Screens

FIGURE 9 – SPACE RESERVATION MODELING

May 15, 2018 32 Version 1.02

4.12 Equipment Objects

Existing Equipment and equipment to be installed must be modeled to LOD 300 (accurately sized) so that model efficiency will not be impacted. The final equipment selection data will be part of the COBie deliverable. Equipment purchased through the construction contract must be appropriately modeled for fabrication (e.g., casework) or for adequate mechanical room test fitting (e.g., boilers, generators). When modeling, do not attach furniture, fixture and equipment objects to a surface, because the ability to replace the initial (design‐intent) objects with the actual objects after final selection will be compromised. Single instances of rooms or areas must have 3D equipment objects (LOD 300) placed in each room/area for test fitting. Where there are multiple instances of the same room/space with the same building equipment and the utility connections to the building have standardized room locations, one standardized room/area which contains 3D equipment objects must be modeled, and duplicate spaces may show the equipment as 2D objects in the plans, elevations, etc. Assure all 2D objects are intelligent for classification/reporting. This form of modeling, with intelligent 2D objects and standardized 3D objects, is sufficient for existing conditions modeling. This must be reviewed by the MAA BIM manager and documents in the BIMxP.

4.13 Schedules and Details Both details and schedules are to be derived from the model with as little 2D drawing as possible. All construction details must be “Model Details” and created with BIM tools and linked to the 3D view. No “Drafting Details” created in 2D software and added to the 2D Drawings will be accepted unless they are approved MAA details for existing equipment installs. All schedules must be derived from the properties of the model object, except for 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.

4.14 Model Properties Physical construction and products that are represented as objects must include the properties of the object as described in the MAA SOW and the MAA COBie requirements. The AE may use external BIM tools to manage the data during design. The final deliverable must provide the required information in a COBie format for import into Maximo. (There is a COBie import feature available in Maximo for the data and a viewer API for the 3D Model.)

4.15 Legends and Symbols 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

May 15, 2018 33 Version 1.02

immediate updated 2D representation). Actual BIM objects must be 3D objects with attached or associated data and metadata as defined throughout this MAA BIM Standards. MAA Design Standards, Volume 3, Appendix H provides the required graphics, shown in Figure 10, below.

5 Model Structure, Navigation and Conventions The usefulness of the model across the project lifecycle and into facility management requires definition of the model structure and navigation conventions for MAA models.

5.1 Discipline Model Designations AE design models must be subdivided by discipline and by non‐building equipment as required in the MAA BIM standards. All discipline model divisions are to be documented in the BIMxP. In general, each discipline model, with the exceptions noted herein, must contain the objects that relate to their discipline’s design. Table 8 contains the discipline model designations.

Each project will require different discipline models depending on the scope of work. It is the responsibility of the AE and GC to appropriately structure their modeling to provide adequate

DISCIPLINE CODE

DISCIPLINE DISCIPLINE CODE

DISCIPLINE DISCIPLINE CODE

DISCIPLINE

A Architectural G General Q Equipment‐BaggageB Geotechnical H Hazardous R Real Estate/LeaseC Civil I Interiors S Structural D Demolition L Landscaping T TelecommunicationE Electrical M Mechanical V Surveying/MappingF Fire P Plumbing Z Contractor/Shop

MAA Design Standard Appendix H

FIGURE 10 – MAA GRAPHICS FOR MODEL

TABLE 8 – DISCIPLINE MODEL DESIGNATIONS

May 15, 2018 34 Version 1.02

information as needed for the project. However, MAA has the following requirements for these discipline models, which must be included in the FM Model.

5.1.1 Architecture Architectural models must include the BIM objects relative to floors, exterior and interior walls and partitions, roofs, vertical transportation, windows, doors, stairs, ramps, railings, ceilings, grilles and gates, interior specialties, etc. Required structural blocking such as restrooms must be modeled for quantities, size, shape, and location, etc. Reference major structural components from the structural model including but not limited to structural walls, floors, roof structure, columns, and foundations. Reference the interiors model, the equipment models, and appropriate building equipment and systems models, and others as needed to coordinate the work. Interior Partitions, Fire‐Rated Partitions & Smoke Barriers: Must be modeled to include fire resistance ratings in the wall object properties and must graphically be depicted in 2D plan sets and in 3D model views. A different partition name is to be created for each type of wall used in the models. Figure 11 illustrates a fire rated wall graphic. Electrical Outlets: Model the location of electrical outlets required for equipment. Door Objects: Properties of door objects must

include finish information, door swing, vision

panels, seals, acoustical properties, hardware,

locks and keying, electrical requirements, and applicable fire resistance ratings. Door objects

must have an accurate offset in the model as an LOD 300 object in the design intent model.

Ceilings: Properties of ceilings must include fire ratings and sound transmission coefficients.

Raised Floors: Access/raised floors are modeled excluding supports.

Casework: All architectural casework, millwork and features provided by the GC must be modeled to include finish information and be collected in the room properties to be included in the overall room finish tag. Casework materials will generally consist of a horizontal and/or vertical element. Casework and countertops must be modeled to correct dimensions (i.e., length/width, depth, and height).

FIGURE 11 – FIRE RATED WALL GRAPHIC

May 15, 2018 35 Version 1.02

5.1.2 Structure Structural models must be the basis of evaluating and analyzing the building structure, and include all the objects, elements, and components to do so. All material and material properties must be included for structural objects. The building structure and geometry must be accurately defined and labeled for foundations, subgrade enclosures, slab‐on‐grade, superstructure, and exterior vertical enclosures and roofs.

5.2 Interiors

Interior Finishes: Interior finish plans, ceiling plans, elevations, and intelligent scheduling of objects/elements must be used to convey materials and finishes in a separate Interiors model, associated with the architectural model (and others as required). Interior finishes must be included as a part of the room properties. All materials that are representative of a system greater than ¼ inch in thickness must be included in the model as 3D geometry (example: wall protection, interior cladding such as stone, masonry, glass, metal, or wood paneling). Paint is not represented graphically. It is a color and a material property. Walls: Walls must be modeled (based on dimension and type) accurately for laser layout during construction. Wall finishes greater than ¼ inch thickness must be modeled for coordination and clearance. Nongeometric data (e.g., actual material specified) will be included as part of the room finish tag on the architectural finish plans. Fire‐rated walls shall show an interior fill in 3D and 2D.

Modular Furniture: Manufactured modular furniture selected for the design‐intent documents which will be purchased by MAA and installed by the GC must be modeled to correct dimensions (length/width, depth, and height) and linked to the basis‐of‐design cut sheet for the item. Ceilings: All ceiling materials, other than paint, must be modeled and included as part of the overall room finish tag. Stairs: All stair finishes will be scheduled in the model.

5.2.1 Building Systems – Mechanical Mechanical: Mechanical equipment and distribution systems are a vital part of operating a facility. Consequently, all components of the mechanical systems must be model accurately and include the necessary space reservations for appropriate access during operations. Mechanical, electrical, plumbing, fire protection, security and communication technology systems must be in their own discipline models, referenced to the architectural model and other discipline models as needed.

May 15, 2018 36 Version 1.02

All system models must include all equipment necessary for operations, including (but not limited to) boilers, chillers, geothermal and solar energy systems; pumps and piping distribution systems (including modeling for pipe slope and insulation), water‐side terminal units; fans, air handlers, air distribution and evacuation systems (including modeling for duct and equipment insulation), air‐side terminal units, VAV boxes; electrical feed and distribution systems transformers, electrical panels and switchgear, lighting, emergency circuitry, emergency generators; all public utility systems from tap, all control systems, data and phone wiring and terminal devices, data switches, data rooms, etc.

Fire protection must include fire ratings, sprinkler medium, pressure and flow volume. Use OmniClass Table 21 to identify the system each asset is a part of, Table 22 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 to the first connection point of the system.

All system elements 1.0 inches in diameter and larger (e.g., general plumbing, fire protection, etc.

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.

The designer shall incorporate the manufacturer, model, serial number, refrigerant type, capacity (full charge), number of circuits, and the charge per circuit for any new HVAC equipment.

5.2.2 Electrical Ceilings diffusers, light fixtures, etc. are cosmetically arranged by the architect but the systems are designed by the electrical engineer. The architectural and electrical models must reference each other and be a part of the design coordination to eliminate mismatches between the models.

5.2.3 Plumbing Restrooms are to be modeled to meet MAA requirements and fixtures classified using OmniClass designations.

5.2.4 Fire Protection A “Design Build” procurement executed by the GC is generally used for fire protection systems. The GC must assure that the fire protection system is a part of the BIM construction coordination management. It is the GC’s responsibility to assure that the fire protection system is installed so that it does not interfere with the location or maintenance access to other building systems or equipment. The GC must provide as‐built documentation regarding the final location of the fire protection for updating the record model.

May 15, 2018 37 Version 1.02

5.2.5 Communications Business systems infrastructure must be in separate models. These systems, if not a part of the GC’s contract, must be modeled as space reservations and included in the design and construction coordination activities.

5.2.6 Food Service This is typically a permit project. While BIM is recommended, it is not required of all permit projects.

5.2.7 Furniture, Fixtures, and Equipment (FFE) Furniture, fixtures, and equipment that is fixed (e.g., built‐in casework) and purchased as a part of the construction contract must be placed in the architectural model or the Interiors model that is referenced to the architectural model file. CIM – Civil Site Modeling

In all cases, model building and infrastructure systems should be developed to a level that allows the team to verify clearances, analyze conflicts/clashes and properly coordinate the work with all other aspects of the project. Site models shall be developed in 3D per SOW. If the site is not modeled, then the current MAA CADD and GIS standards apply. Items to be modeled will be documented in the BIMxP. Civil 3D site models must be compatible with the project Revit model, and integrated into a BIM project model file.

6 Model Navigation The Design BIM manager is responsible for the naming conventions and coordination of all discipline models and worksets for efficient navigation in the models.

6.1 Worksets Worksets are a primary method of model organization for collaboration. Table 9 lists the three worksets types to be defined.

May 15, 2018 38 Version 1.02

6.1.1 Convention for Three Workset Types WORKSET TYPES

Worksets that contain building elements:

01 00 00 Substructure Worksets organization carried out by OmniClass (Table 21)

Worksets that contain External Links:

Link CAD Worksets used for linking DWG documents.

Link [name of the connection file]

Worksets for linking. rvt file must be created for each connection file separately.

Workspaces that contain elements related to the model:

Model Rooms Worksets that contains the room space, the line of separation of rooms and other elements connected with them.

Model Levels and Grids Worksets in which there are levels and axis.

Model Levels Primary (Model Levels Secondary)

Worksets that are used in many levels.

Model Grids Primary (Model Grids Secondary)

Worksets that are used in many axes.

6.1.2 Project Start Worksets

OmniClass is used for worksets naming conventions and content definition. Worksets will increase according to model progression and complexity. Additional workset types include documentation. Worksets that are “workspaces” will be deleted before final submission. The preliminary workset list shown in Figure 12 shall be used at project inception. If a model is used for a study and not carried forward then a reduced worksets may be used, however, if there is a potential of the model moving forward, then OmniClass building worksets with more granularity should be used.

TABLE 9 – WORKSET TYPES

May 15, 2018 39 Version 1.02

Phase Naming Conventions OmniClass Table 31, as seen below (Table 10), is used to define project phases and relate to the current study, schematic, 30‐60‐100% complete submissions, and handover.

OmniClass Table 3131‐10 00 Inception Phase 31‐20 00 Conceptualization Phase 31‐30 00 Criteria Definition Phase 31‐40 00 Design Phase 31‐50 00 Coordination Phase

31‐60 00 Implementation Phase 31‐70 00 Handover Phase

31‐80 00 Operations Phase 31‐90 00 Closure Phase

FIGURE 12 – FIRE RATED WALL GRAPHIC

TABLE 10 – OMNICLASS TABLE 31

May 15, 2018 40 Version 1.02

6.2 Model Level Naming Conventions The MAA CADD and GIS standards define the levels of MAA buildings to be used in the model view naming. Views within the project browser shall be named beginning with the view type code, followed by an optional level/sequence number, and an optional user description as described in Table 11. The views should take the form of:

<View>‐<Level/Sequence>‐<Description>

LEVEL NAMING

View View Type Code Refer to charts below

Level/Sequence (Optional) Level Number or Sequence Number (Two-digit number)

Description (Optional) Brief User Description (up to 12 characters) The following characters should not be used as part of the description @ $ % ^ & < > / \ “ ” : ; ? * | , ‘

6.2.1 View Codes ALL DISCIPLINES

VIEW CODES

VIEW TYPE CODE VIEW TYPE NAME VIEW TYPE CODE VIEW TYPE NAME

3D 3D Views LG Legends

AP Area Plans LP Location Plan

BS Building Sections MT Material Takeoff

CP Ceiling Plans NB Note Block

CS Construction Staging or Construction Sequence NO General Notes

DL Drawing List ON One Line Diagram Plan

DR Drafting Views QP Equipment Plan

DS Detail Sections RD Riser Diagram

DV Detail Views RO Roof Plan

EE Exterior Elevations RP Reports

EP Enlarged Plan SC Sections

ES Engineering Estimates SL Sheet List

FE Framing Elevation SP Site Plan

FP Floor Plans SQ Schedule/Quantities

IE Interior Elevations VL View List

KL Keynote Legend WT Walkthroughs

TABLE 11 – LEVEL NAMING

May 15, 2018 41 Version 1.02

ARCHITECTURAL VIEW TYPE CODE VIEW TYPE NAME

FU Furniture Plan

SP Signage Plan

ELECTRICAL

VIEW TYPE CODE VIEW TYPE NAME

AC Access Control Plan

AX Auxiliary Power Plan

CM Communication Plan

CO Corrosion Protection Plan

FA Fire Alarm Plan

GP Grounding Plan

LI Lighting Plan

LT Lightning Protection Plan

NS Network System Plan

PA Public Address System Plan

PP Power Plan

RS Radio System Plan

SS Security System Plan

TC Telecommunication Plan

WD Wiring Diagram Plan

MECHANICAL

VIEW TYPE CODE VIEW TYPE NAME

CC Control Schematic Plan

CD Communication System Plan

CN Control Plan

FP Fire Protection Plan

FS Fire Suppression Plan

HP HVAC Ductwork Plan

MD Machine Design Plan

MH Material Handling Plan

PI Piping Plan

PL Plumbing Plan

SI Specialty Piping Plan

SK Sprinkler Plan

May 15, 2018 42 Version 1.02

Project Browser: The image to the right shows the floor plans views within the project browser, organized by its view type code, followed by a sequence number and description.

Example 1: Architectural floor plans should be named as follows if the optional level/sequence number is not used:

FP‐First Floor

FP‐Second Floor

FP‐Third Floor

6.3 File Naming Conventions The MAA Design Standards, Volume 3, Appendix H – Table 4‐6, Construction Drawing Set contains file naming conventions for drawings.

STRUCTURAL VIEW TYPE CODE VIEW TYPE NAME

CF Concrete Framing Plan

DP Decking Plan FD Foundation Plan FR Framing Plan GC Graphical Column Schedule

L Joist Girder Load Diagram

PP Precast Panel Plan

RE Reinforcement Plan

SF Stair Framing Plan

ST Steel Framing Plan

TB Truss Bracing Plan

WG Wind Girt Plan XB X Bracing Plan

TABLE 12 – VIEW CODES

May 15, 2018 43 Version 1.02

6.3.1 Revit Central File The central model file naming convention includes: project number, software version, discipline code(s) and central file. The BIM manager shall use the discipline codes located in Section 7.16. Example: MAA‐4604_R17_A_Central.rvt

6.3.2 Plot Sheet Files, Drawing Sets and Sheet The document types are named using the MAA CAD standards naming convention. Refer to MAA Design Standards, Volume 3, Appendix H – Table 4‐6, Construction Drawing Set.

6.4 Folder Structure P:/ MAA 489 Campus (BWI or MTN) 641‐423 Project Folder (Project Number and name) 800 Building Number DD1_2015_0704 Submittal Phase Folder (Submittal Phase_YYYY_MMDD)

01_Project_Managment 01_Support_Files (templates, logos, graphics, etc.) 02_BIM_BIMxP (Design, Construction) 03_Reports (QA/QC, Model Checks, Error Reports, System Coordination Reports) 04_Schedules (Phasing, Critical Path Method)

02_Models (BIM files) 01_Composite_Models 01_Design‐Intent_Model 02_Analysis_Model (NWD or equivalent) 03_Discipline Models (subfolders created separately by discipline) 04_Construction_As_Built_Models & Information (subfolders created separately by discipline) 05_Record_Model (subfolders created separately by discipline) 02_Discipline_Models (Subfolders by NCS Discipline Code) 01_G‐General (each discipline shall add a “links” folder for linked content) 02_A‐Architectural 03_AJ‐Program NSF/GSF validation 04_B‐Geotechnical 05_C‐Civil 06_D‐Process 07_E‐Electrical 08_F‐Fire_Protection 09_H‐Hazardous_Materials 10_I‐Interiors 11_IF‐ Furnishings, Fixtures, & Equipment 12_L‐Landscape 13_M‐Mechanical

May 15, 2018 44 Version 1.02

14_O‐Operations (Equipment maintenance, repair, and replacement no‐fly‐zones) 15_ P‐Plumbing 16_QF – Food Service 17_ S‐Structural 18_ T‐Telecommunications 19_V‐Survey‐Mapping 20_ W‐Distributed Energy 21_ X‐Other Disciplines (or Trade specific models) 22_ Z‐Contractor‐Shop Drawings

03_Renderings‐Animations (still renderings, walk/fly through, functional validations) 04_Drawings (DWG/CAD or equivalent, follow 02 Discipline Model structure)

05_Electronic PDF 01_Full‐Size_Set (composite PDF with hyperlinks and bookmarks) 02_Half‐Size_Set (composite PDF with hyperlinks and bookmarks) 03_Single_Sheets (individual PDFs – 1:1 ratio corresponding to each sheet in the set) 06_Specifications

07_Sustainability (LEED or other sustainability documentation) 08_FM_Data (COBie)

Submittal of the models and 2D documentation shall be copied to the submittals folder. Files placed in the submittals folders are snapshots of the project at a given point in time based upon requirements of the project schedule. Maintaining consistent file naming and structure is critical for referenced (linked) files to function properly across project teams and for end users such as facility managers to be able to retrieve files quickly once the project is complete.

May 15, 2018 45 Version 1.02

7 Glossary of Terms The following terms have been used in this standard.

Asset Information Model (AIM)

The asset information model or AIM is a term used to describe the collated set of information gathered from all sources that supports the ongoing management of an asset.

Building Information Model (BIM)

The creation and use of coordinated, internally consistent, and computable information about a project in design and construction. In this document, it is specifically related to Revit files.

Civil Information Model (CIM)

The creation and use of a coordinated 3D model of site, infrastructure, and horizontal construction.

BIM Denoting projects that span vertical facilities and civil projects like airports.

Views/ Output files A generated rendition of graphical or non‐graphical information (a plan, section, elevation, schedule, or other views of a project).

Central Files

The central file is the source of the record (as‐built) file. It is created the first time you save the project after sharing it. This file stores current ownership information for all Worksets in the project. The central file acts as the distribution point for publishing work to the rest of the team. All users should save their own local copies of the file, work locally, and then save changes back to the central file for other users to see their work.

Worksets

Autodesk Revit projects can be subdivided into Worksets. A Workset is a collection of building elements (such as walls, doors, floors, stairs, etc.) in the building. In the Autodesk Revit project, users have the option of checking out entire Worksets or individual elements in a Worksets. All other team members may view these elements or Worksets, but are unable to change them, preventing possible conflicts in the project.

View Types

Defines some graphics properties, such as a reference label and tags for elevations, callouts, or sections. It can also specify a view template to apply to a new view, and whether template updates should be applied to existing views.

May 15, 2018 46 Version 1.02

Coordinates

There are two coordinate systems in a Revit project: project internal and shared. Each system has essential features and limitations. Project Internal Coordinate System: Every Revit project has an internal coordinate system referred to in several places as Project. The project coordinate system cannot be changed. Shared Coordinates: The shared coordinate system consists of a single origin and true north orientation which can be synchronized between models and even AutoCAD drawings.

View Templates

A view template is a collection of view properties, such as view scale, discipline, detail level, and visibility settings. Use view templates to apply standards settings to views. View templates can help to ensure adherence to office standards and achieve consistency across construction document sets.

View Range

Every plan view has a property called View Range, also known as a visible range. The view range is a set of horizontal planes that control object visibility and display in the view. The horizontal planes are Top, Cut Plane, and Bottom. The top and bottom clip planes represent the topmost and bottommost portion of the view range. The cut plane is a plane that determines at what height certain elements in the view are shown cut. These 3 planes define the primary range of the view range.

Families

A family is a group of elements with a common set of properties, called parameters, and a related graphical representation. Different elements belonging to a family may have different values for some, or all, of their parameters, but the set of parameters (their names and meanings) is the same. These variations within the family are called family types or types. There are 3 types of Revit Families – System Families, Component Families and In‐Place Families.

Object Styles

The object styles tool specifies line weights, line colors, line patterns, and materials for different categories and subcategories of model objects, annotation objects, and imported objects in a project. You can override project object styles on a view‐by‐view basis with Visibility Graphics.

Visibility Graphics

The visibility and graphics settings of a view define whether elements and categories are visible in the view and their graphical appearance (color, lineweight, and linestyle). The Visibility/Graphics Overrides dialog lists all categories in the project. Some examples of categories are furniture, doors, and window tags. The visibility status and appearance of each category can be modified for each view in the project. Use the context menu to modify the appearance and visibility of individual elements.