Engineering

BIM
Standards

V.5
Last Updated: 03/01/2025
 Engineering BIM Standards

TABLE OF CONTENTS

1.0 INTRODUCTION ................................................................................................................................ 4

1.1 PURPOSE ............................................................................................................................. 4
1.2 DOCUMENT HIERARCHY ...................................................................................................... 4
1.3 APPLICABILITY ..................................................................................................................... 4
1.4 ACRONYMS AND ABBREVIATIONS ...................................................................................... 5
2.0 VDC ENGAGEMENT ........................................................................................................................ 6
2.1 PANYNJ PROJECT STAGES .............................................................................................. 6
2.2 BIM OBJECTIVES ................................................................................................................ 6
2.3 BIM DIMENSIONS APPLICATIONS ....................................................................................... 7
2.4 BIM MODELS EXPECTATIONS ............................................................................................ 8
2.5 BIM MODELS LIFECYCLE .................................................................................................... 9
2.6 VDC ROLES AND RESPONSIBILITIES ................................................................................. 9
3.0 VDC CONTENT MANAGEMENT ................................................................................................... 10
3.1 VDC DOCUMENTS AND SUPPORT FILES ......................................................................... 10
3.2 BIM EXECUTION PLAN (BEP) .......................................................................................... 11
3.3 REVIT TEMPLATES ............................................................................................................. 12
3.4 REVIT LIBRARY .................................................................................................................. 13
3.5 AUTODESK CONSTRUCTION CLOUD ................................................................................ 16
4.0 NAMING CONVENTION .................................................................................................................. 17
4.1 FILES NAMING CONVENTION ............................................................................................ 17
4.2 REVIT COMPONENTS NAMING CONVENTION ................................................................... 21
4.3 SHEET NAMING .................................................................................................................. 28
5.0 TECHNICAL REQUIREMENTS ....................................................................................................... 32
5.1 SOFTWARE ......................................................................................................................... 32
5.2 FILES OWNERSHIP............................................................................................................. 33
5.3 COORDINATE SYSTEMS .................................................................................................... 33
5.4 INFORMATION DELIVERY PLAN ......................................................................................... 33
5.5 3D MODEL EXCLUSIONS ................................................................................................... 36

2025 V.5 Last Updated: 03/01/2025

Page | 2
 Engineering BIM Standards

6.0 DESIGN REQUIREMENTS .............................................................................................................. 37

6.1 GOALS AND USES ............................................................................................................. 37
6.2 FOLDER STRUCTURE......................................................................................................... 37
6.3 DESIGN SITE MODEL (SM) ............................................................................................... 45
6.4 DESIGN CONTEXT MODEL (SCM) .................................................................................... 46
6.5 DESIGN MODELS ............................................................................................................... 46
6.6 ADDENDUM MODELS ......................................................................................................... 64
6.7 PACC MODELS ................................................................................................................. 67
6.8 BIM COORDINATION MODEL - DESIGN ............................................................................ 67
6.9 DESIGN DELIVERABLES .................................................................................................... 69
7.0 CONSTRUCTION REQUIREMENTS ............................................................................................... 72
7.1 GOALS AND USES ............................................................................................................. 72
7.2 CONSTRUCTION SITE MODEL ........................................................................................... 72
7.3 CONSTRUCTION CONTEXT MODEL ................................................................................... 72
7.4 CONSTRUCTION MODEL .................................................................................................... 76
7.5 BIM COORDINATION MODEL - CONSTRUCTION .............................................................. 78
7.6 4D SIMULATION MODEL .................................................................................................... 85
7.7 AS-CONSTRUCTED MODEL ............................................................................................... 88
7.8 REALITY CAPTURE ............................................................................................................ 90
7.9 CONSTRUCTION DELIVERABLES....................................................................................... 93
8.0 BIM COMPLIANCE REVIEW ......................................................................................................... 96
8.1 REVIEW MILESTONES AND REQUIREMENTS .................................................................... 96
8.2 REQUEST FOR VDC (BIM/CAD) REVIEW........................................................................ 97
8.3 BIM COMPLIANCE REPORTS ............................................................................................ 99
APPENDIX A: CONFIDENTIAL & CONFIDENTIAL PRIVILEGE PROJECTS ........................................ 110
APPENDIX B: BIM EXECUTION PLAN TEMPLATES ........................................................................... 116
APPENDIX C: BIM PROGRESS REPORT TEMPLATE......................................................................... 119

DOCUMENT OWNERSHIP

Questions regarding the Authority’s BIM Standards shall be directed to the Engineering Project Controls -
VDC Support Group at:
Port Authority of NY & NJ
4 World Trade Center, 19th Floor
New York, NY 10007
212-435-6102
[email protected]
2025 V.5 Last Updated: 03/01/2025
Page | 3
 Engineering BIM Standards

1.0 INTRODUCTION

1.1 PURPOSE

The Building Information Modeling (BIM) Standard introduces the information, management, and
technical specifications to support the implementation of Building Information Modeling (BIM) for The Port
Authority of New York & New Jersey (“Authority”). The Authority’s BIM Standards apply to the full life
cycle of a project from conceptual design through construction, close out and operations.
This document should be read in conjunction with the following as shown in the Table below:
Table 1-1 - Associated Materials

DOCUMENT TYPE PURPOSE

Details the requirements to support, produce, collect,
VDC Requirements Requirements and analyze CAD and BIM data on projects that is
consistent, relevant, and high quality.
Establishes requirements and procedures for the
CAD Standard Standard preparation and milestone submissions of CAD
based drawings throughout Design.
Details the technical BIM data requirements to be
Information Delivery
Specification consistent, relevant, and high quality for BIM
Plan
projects.
Document Templates,
Software Templates, Provides base documents, templates, standardized
VDC Support files Content Library for CAD content to support consistency during projects
and BIM, ACC development.
guidelines, and others.

1.2 DOCUMENT HIERARCHY

The image below shows the document hierarchy adopted by VDC.

Figure 1-1 - Document Hierarchy

1.3 APPLICABILITY

The Port Authority operates an exception to the rule policy meaning that BIM applies to all projects unless
specifically stated otherwise. This standard covers the entire project life cycle.

2025 V.5 Last Updated: 03/01/2025

Page | 4
 Engineering BIM Standards

1.4 ACRONYMS AND ABBREVIATIONS

Table 1-2 - Acronyms

ACRONYMS DESCRIPTION
ACC Autodesk Construction Cloud
BEP BIM Execution Plan
BIM Building Information Model
CAD Computer Aided Design
C Confidential
C3D Autodesk AutoCAD Civil 3D
CM Construction Model
CMD Construction Management Division
CN Contract Number
CP Confidential Privileged
DB Design Build
DBB Design Bid Build
DWG AutoCAD drawing file
EADD Engineering Architecture Design Division
EAM Enterprise Asset Management
FIM Facility Information Model
IDP Information Delivery Plan
IPD Integrated Project Delivery
LOD Level of Development
NWC Autodesk Navisworks Cache files
NWD Autodesk Navisworks Document file
NWF Autodesk Navisworks Federated file
PC Point Cloud
PID Project Identity Number
PIM Project Information Model
PP Project Principal (former LEA)
RCP Reflected Ceiling Plan
RE Resident Engineer
RFA Autodesk Revit Family
RVT Autodesk Revit
RTE Autodesk Revit Template
SCM Site Context Model
SDE Senior Design Executive
SM Site Model
TL Task Leader
VDC Virtual Design and Construction
WCS World Coordinates System

2025 V.5 Last Updated: 03/01/2025

Page | 5
 Engineering BIM Standards

2.0 VDC ENGAGEMENT

This section describes Agency BIM Project Workflow based on the BIM Master Plan.

2.1 PANYNJ PROJECT STAGES

The phases indicated in the table below relate directly to distinct Stages of a BIM project’s lifecycle
development at The Port Authority of NY & NJ.
Table 2-1 - BIM Project Phases

BIM PHASE PANYNJ STAGE DESCRIPTION

Conceptualization & Stage I Conceptual Design
Analysis Stage II Preliminary Design
Design & Documentation
Stage III Final Design
Management & Stage IV Construction
Construction & Operations
Maintenance Stage V Project Closeout

2.2 BIM OBJECTIVES

The Authority’s strategic objectives, relative to this Standard, are to:

1. Achieve interoperability between project teams to facilitate information exchange, enhance
communication and enable collaboration between functions.
2. Promote the expansion of Virtual Design Construction (VDC) Technologies and ensure Data Integrity
during the complete Project Lifecycle:

Figure 2-1 - VDC Dimensions

• 2D - Drawings, sketches, details development.

• 3D - Design development, visualization, review, and coordination.
• 4D - Scheduling, field coordination and logistics management.
• 5D - Quantity take off and estimating.
• 6D - Resilience and Sustainability.
• 7D - Facility management and enterprise asset management (EAM).

3. Ensure that all content, CAD, and BIM, is detailed appropriately, meeting the standards of the
Authority, and fit its purpose.

2025 V.5 Last Updated: 03/01/2025

Page | 6
 Engineering BIM Standards

2.3 BIM DIMENSIONS APPLICATIONS

Figure 2-2 - BIM Dimensions Uses through Project Stages

2025 V.5 Last Updated: 03/01/2025

Page | 7
 Engineering BIM Standards

2.4 BIM MODELS EXPECTATIONS

Figure 2-3 - BIM Models Expectations

2025 V.5 Last Updated: 03/01/2025

Page | 8
 Engineering BIM Standards

2.5 BIM MODELS LIFECYCLE

This graphic represents the process of creating, utilizing, and maintaining the building information. There
are 3 major phases throughout the life of a project: Design, Construction, and Operations and
Maintenance. All of them supported by a series of documents throughout the life cycle of a Project.

Figure 2-4 - BIM Models Lifecycle

NOTE:
In the event that existing BIM models or CAD files are provided by the VDC group, the use of these files
should be for reference only and shall not relieve the Consultant/Contractor of their sole responsibility for
verifying the accuracy of the conditions represented within these files.

2.6 VDC ROLES AND RESPONSIBILITIES

The following VDC related roles shall be taken on directly by the Authority:
• VDC Manager
• VDC Engineer
Roles performed by the Contractor/Consultant must be described fully within the BIM Execution Plan
(BEP). These roles may include:
• BIM Manager(s)
• BIM Coordinator
The Contractor/Consultant shall confirm the parties and named persons who will be responsible for the
project, describing what activities will be performed and what authorities will be held. Candidates shall
have the required experience for the size and scale of the project and shall seek clarification from the
Authority prior to nomination.

2025 V.5 Last Updated: 03/01/2025

Page | 9
 Engineering BIM Standards

3.0 VDC CONTENT MANAGEMENT

The Authority VDC Standard, Guidelines, Supporting Documents, Templates & Training content can be
found in different locations depending on who is accessing the information:
PANYNJ link for internal staff:
VDC SharePoint Site
Consultant/Contractor link for external users:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD)

3.1 VDC DOCUMENTS AND SUPPORT FILES

Table 3-1 –Documents and Content

VDC Documents > 01. Delivery

Requirements Contains the “VDC Requirements”.
Standards Contains the “BIM Standard & CAD Standard”.
VDC Documents > 02. Development > 2024 > Content > Revit > Families
All Disciplines Contains all cross-discipline support files and content.
<Discipline> Contains all discipline specific support files and content.
Lookup Tables Includes the support files for conduits and pipes.
VDC Documents > 02. Development > 2024 > Content > Revit
22x34 and 34x56 borders for PA Contract, Presentation, Report and
Borders
Title sheet drawings.
-Law Review, Preliminary, Quality Assurance and Percent
submission stamp for use on borders.
-Confidential Privileged Warning sign for use on stamp for use on
borders for CP drawings.
Stamps -Confidential stamp for use on borders for C drawings.
-One and Multiple consultant company providing NJ & NY PE
signatures on drawings.
-One and Multiple consultant company providing NJ & NY RA
signatures on drawings.
VDC Documents > 02. Development > 2024 > Folder Structure
Includes the Folder Structure templates to address both the Central
Folder Structure
File and the Local File.
VDC Documents > 02. Development > 2024 > Software Templates > Revit
Includes the discipline-specific template files for the Architectural,
Revit Templates
Electrical, Mechanical, and Structural disciplines.
Includes the Port Authority of NY & NJ custom Parameters file “PA-
Shared Parameters
VDC-DB-RVT-X-GN-SharedParameters.txt”.
VDC Documents > 02. Development > 2024 > Document Templates
Includes BIM Execution Plans, BIM Progress Report and BIM
Other templates
Coordination Clash Report templates.

2025 V.5 Last Updated: 03/01/2025

Page | 10
 Engineering BIM Standards

3.2 BIM EXECUTION PLAN (BEP)

At the start of every BIM project, a BEP must be submitted to the Port Authority VDC Support Group.
Please refer to Appendix B: BIM Execution Plan for BEP Templates.
Once approved by the Authority, BEP shall become the ultimate compendium on BIM requirements,
methodologies, and workflow for a specific project.
The BEP is considered a “living” document, subject to updates throughout the project lifecycle.
Circumstances that may trigger a revision on the BEP include, but are not limited to:
• Changes in staff, that directly affect the BIM processes and/or deliverables
• Changes in processes
• Changes in requirements
• Changes in BIM Schedule (Coordination sign-off dates, LOD milestones, etc.)
• Any other requirement specified by the Port Authority
Depending on who is accessing the information, the files can be accessed using the following links:
Internal link:
VDC Documents > 02. Development > 2024 > Document Templates > BIM Execution Plan

Figure 3-1 - BIM Execution Plan templates

External link:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 11
 Engineering BIM Standards

3.3 REVIT TEMPLATES

To promote consistency in the Revit models developed, the PANYNJ provides Revit templates that
contain several predefined elements such as supporting legends, a starting view, a predefined project
browser, shared parameters, loaded families, view templates, and defined settings such as units, fill
patterns, line styles, line weights, scales, text, and dimensions, among others.

Figure 3-2 - Revit Templates Content

To prevent the use of un-licensed fonts, all text styles, dimension styles, leaders, tags and content for the
Port Authority of New York and New Jersey (PANYNJ) have been defined using Arial Font.
All Revit projects must be created using the provided templates and version, which are:
• PA-TP-RVT-GN-2024-v1
• PA-TP-RVT-A-2024-v1
• PA-TP-RVT-MEP-2024-v1
• PA-TP-RVT-ST-2024-v1

Do not alter the settings within the template files. If needed, changes will be discussed and approved by
the VCD Group. All specific requirements should be defined in the project BEP.
Depending on who is accessing the information, the files can be accessed using the following links:
Internal link:
VDC Documents > 02. Development > 2024 > Software Templates > Revit
External link:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 12
 Engineering BIM Standards

3.4 REVIT LIBRARY

3.4.1 LOADABLE FAMILIES

The Port Authority of NY & NJ BIM Standard Templates includes System Families, such as Columns,
Beams, Walls, Roofs, Ceilings, Floors, etc. Users can customize this content and even create new
content as per project needs.
The Content folder contains 2D detail components, tags, and symbols as well as 3D families. The library
holds multi-discipline families to make the modeling process and drawings development easier and more
efficient.

Figure 3-3 - Revit Annotation Families example

Depending on who is accessing the information, the files can be accessed using the following links:
Internal link:
VDC Documents > 02. Development > 2024 > Content > Revit

Figure 3-4 – VDC Documents and Templates

External link:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 13
 Engineering BIM Standards

3.4.2 TITLESHEET & CONTRACT BORDER

All project sheets must be created using one of the Title-Sheet and Contract Border provided as part of
the shared content. Images showing the official Port Authority of NY & NJ Title Sheets and Contract

Figure 3-5 - Title Sheet Engineering 22x34 Figure 3-6 - Title Sheet PATH 22x34

Figure 3-7 - Contract Border Engineering 22x34 Figure 3-8 - Contract Border PATH 22x34

Depending on who is accessing the information, the files can be accessed using the following links:
Internal link:
VDC Documents > 02. Development > 2024 > Content > Revit > Borders

Figure 3-9 - Contract Borders Folder

External link:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 14
 Engineering BIM Standards

3.4.3 STAMPS
Submission stamps have been provided to be included as part of the Contract Border. The following
submission types have stamps provided with this standard:
• Law-Review
• Preliminary
• QA-Submission
• Percent Submission
• Record Drawing
Signature stamps have been provided for both the New York and New Jersey Professional Engineer
and Registered Architect and are to be used by outside consultants in-lieu of Consultant Logos.
Confidential Privileged Stamps have been provided be included as part of the Contract border on each
individual sheet unless the entire project is considered Confidential and Privileged, in which case the
stamps can be placed within the Contract Border.
All stamps should be inserted as families within the Contract Border.
Depending on who is accessing the information, the files can be accessed using the following links:
Internal link:
VDC Documents > 02. Development > 2024 > Content > Revit > Stamps
External link:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

Figure 3-10 - Stamps

2025 V.5 Last Updated: 03/01/2025

Page | 15
 Engineering BIM Standards

3.4.4 STANDARD DETAILS

For the purpose of facilitating the drawing development during Design, 2D Standard details have been
created for Architecture, Electrical, Mechanical and Structural disciplines.
All details have been saved within each discipline Revit file, in case used those should be transferred to
the Project file. It is important to clarify that these details have been developed to be used as a starting
point and need to be modified to adjust the project needs.
Both AutoCAD and Revit files and are available for Port Authority E/A Design Division in the EADD
Standards Center SharePoint Site as well as VDC SharePoint Site.
Internal link:
VDC Documents > 02. Development > 2024 > Content > Revit > Standard Details

Figure 3-11 - Standard Details Revit files

3.3.5 CREATING CONTENT

When creating new Revit content, the following practices must be considered:
• Revit Families must be created from PA family templates (by category)
• PA-Linestyles must be used.
• Arial Font must be used if creating an annotation family.
• Revit families cannot exceed a file size of 3 megabytes (MB). Limiting the file size helps manage
project file sizes and ensures that families are optimized for performance.
• Revit families are not allowed to contain DWG files as nested components. This restriction is in
place to maintain consistency, avoid potential issues with file compatibility or versioning, and
encourage the use of native Revit elements.

3.5 AUTODESK CONSTRUCTION CLOUD

Under the instruction of the Authority's Virtual Design and Construction (VDC) Group, the BIM files will be
hosted on Autodesk Construction Cloud throughout the duration of the work.
A project folder location will be created in the Authority's Autodesk Construction Cloud environment by the
Authority's VDC Group.
The assigned BIM team must be identified by the Project Principal at the time of the BIM Kick-off meeting.
The Project Principal shall submit personnel names, and other information as requested by the VDC
Engineer, to arrange for security training, and for providing access and setting permissions to the folder
location in Autodesk Construction Cloud.
The project team, including internal and all external staff shall complete, as necessary, all training and
documentation required by the Authority for access to the Authority's Autodesk Construction Cloud hub.
The training and documentation are required for any Contractor staff performing any actions on files or
documents residing in the Autodesk Construction Cloud environment.

2025 V.5 Last Updated: 03/01/2025

Page | 16
 Engineering BIM Standards

All official BIM submissions shall be submitted through eBuilder or other approved environment. All
active BIM file types (.rvt, .dwg, .nwc, etc.) shall remain in the Autodesk Construction Cloud environment.

NOTE:
The Authority has created a dedicated Autodesk Construction Cloud Page for PA employees. For more
information refer to Autodesk Construction Cloud Guideline.

4.0 NAMING CONVENTION

The Port Authority of NY & NJ has established standardized naming conventions for electronic project
files based on file type, which must be followed to ensure compliance.

4.1 FILES NAMING CONVENTION

As a general rule, filenames should take the form of:

“DPID–SN/DT/MT–DESCRIPTION”
Table 4-1 - File naming convention

ITEM DESCRIPTION
D Discipline Code
PID Eight-digit PID Number
DT/SN/MT Drawing Type / Sequence Number / Model Type
(Optional*) (Drawing Type or Two-digit consecutive numbers starting with 01)
Brief User Description (up to 24 characters)
DESCRIPTION
The following characters should not be used as part of the description: @ $ %
(Optional*)
^&<>/\“”:;?*|,‘

NOTE:
Optional*: Meaning one of the two should be used, either “DT/SN/MT” or “DESCRIPTION” or both.

4.1.1 DISCIPLINE CODES

There are nine main disciplines within The Port Authority of NY & NJ Engineering Department. All
electronic files should be named using the appropriate Discipline Code based on the following table:
Table 4-2 - Discipline Codes

DISCIPLINE
DISCIPLINE NAME
CODE
A Architectural
C Civil
E Electrical
N Environmental
G Geotechnical
M Mechanical
S Structural
T Traffic
R Resilience and Sustainable Design

2025 V.5 Last Updated: 03/01/2025

Page | 17
 Engineering BIM Standards

4.1.2 MODEL TYPE CODES

Table 4-3 - Model Type Codes

MODEL TYPE CODE DESCRIPTION

GENERAL
GN General Model
EC Existing Conditions Model
SM Site Model
PC Point Cloud Model
RM Removal
BR Bridges
PBB Pedestrian Boarding Bridges
TR Terminal
UT Utilities
3D 3D Coordination Model
4D 4D Simulation Model
ARCHITECTURAL
SC Site Context Model
CNP Canopy
CW Curtain Wall
FFE Furniture Fixtures and Equipment
CR Core
SH Shell
ELECTRICAL
CP Corrosion Protection
ES Electronics
FP Facility Power
LG Lighting
SA SCADA
SG Signage
TP Traction Power
MECHANICAL
BH Baggage Handling
FP Fire Protection
HVAC Heating, ventilation, and air conditioning
PL Plumbing
VT Vertical Transportation
STRUCTURAL
SS Superstructure
SB Substructure

2025 V.5 Last Updated: 03/01/2025

Page | 18
 Engineering BIM Standards

4.1.3 REVIT CENTRAL FILES

Each discipline should maintain its own Central Model; however, on large projects, a discipline’s work
may be split into several models. This division may be necessary due to file size constraints or to
separate models by sub-discipline or area. Once defined, the Central File name should remain
unchanged throughout the project lifecycle.
For Disciplines with a single model file, “GN” (General) Type Code shall be used.
File names should take the form of:
“DPID–MT_CENTRAL.rvt”
ITEM DESCRIPTION
D Discipline Code
PID Eight-digit PID Number
MT Model Type Code. Refer to MT chart.
CENTRAL This shall stay as is

NOTE:
The only exception to this naming convention is the Site Model, which is created and managed by the
VDC Group. The site model should be named as: PID-SM.rvt.
Example:
• Discipline: Architecture
• PID: 12345678
• Model Type: General
File name: A12345678-GN_CENTRAL.rvt

4.1.4 3D COORDINATION FILES

3D Coordination filename should take the form of:
“DPID-MT_CENTRAL.nwc”
“PID-3D.nwd”
ITEM DESCRIPTION
D Discipline Code
PID Eight-digit PID Number
MT Model Type Code. Refer to chart below.
3D This shall stay as is

4.1.5 4D SIMULATION FILES

4D Simulation filename should take the form of:
“PID-4D.nwd, or PID-4D.sp, or PID-4D.avi”
ITEM DESCRIPTION
PID Eight-digit PID Number
4D This shall stay as is

2025 V.5 Last Updated: 03/01/2025

Page | 19
 Engineering BIM Standards

4.1.6 PLOTSHEET FILES

Plotsheet files should be generated out of the Revit Models in PDF format.
Name the Plotsheet files using this format:
“DPID-DT-001_###.pdf”

ITEM DESCRIPTION
D Discipline Code
PID Eight-digit PID Number
DT Drawing Type
001_### First Sheet Number to Last Sheet Number

If Bluebeam Revu is being used, page labels should correspond to sheet numbers.
When using Series Numbers, either Option 1, Option 2 or Option 3 as described in Section 4.3.2
Drawing Number, the PDF files should be named not only by grouping them together by Drawing Type
but also by their Series Number.
For example:
The Architectural Group is creating a set of drawings using Option 1 (without using the Series Number),
which include the General drawings (1 through 7), Architectural drawings (1 through 37), and Landscape
drawings (1 through 11) for a project with a PID Number of 07963000, three multi-sheet files should be
created and named as follows:
• A07963000-G001_G007.pdf
• A07963000-A001_A037.pdf
• A07963000-LS001_LS011.pdf

4.1.7 AUTOCAD FILES

The filename should take the form of:
“DPID–MTSN–Description.dwg”
ITEM DESCRIPTION
D Discipline Code
PID Eight-digit PID Number
MT Model Type (refer to CAD Standard)
Sequence Number
SN
(Drawing Type or Two-digit consecutive numbers starting with 01)
DESCRIPTION Brief User Description (up to 24 characters)

2025 V.5 Last Updated: 03/01/2025

Page | 20
 Engineering BIM Standards

4.1.8 POINT CLOUD FILES

The filename should take the form of:
“PID_SRN*_F_DATE-CS_Description.rcs”

ITEM DESCRIPTION
PID Eight-digit PID Number
Central Survey Request Number
SNR*
*Optional, applicable only if Survey is performed by CSG.
F Facility
DATE Scan Start Date (YYYYMMDD)
Coordinate System
CS
ie: NJ83F
DESCRIPTION Brief Description (up to 24 characters)

4.2 REVIT COMPONENTS NAMING CONVENTION

4.2.1 3D MODEL FAMILIES

The filename should take the form of:
“CATEGORY-MANUFACTURER-DESCRIPTION.rfa”

ITEM DESCRIPTION
CATEGORY Names the element that the family creates
MANUFACTURER Manufacturer Name or the word “Generic”.
DESCRIPTION A brief Description and/or a Model Number.

When naming Family files keep in mind the following:

• Use UPPERCASE throughout the entire family name.
• Keep file names as short as possible because they need to display in the Type Selector.
• Create a Type Catalog for Family files that contain five or more types.
• No spaces or dashes should be used in the manufacturer and/or description.
• When needed, abbreviate “IN” (inches), “FT” (feet) or use the type name for the description.
For example:
• WINDOWS-ANDERSEN-DOUNBLEHUNG400SERIES.rfa

2025 V.5 Last Updated: 03/01/2025

Page | 21
 Engineering BIM Standards

4.2.3 ANNOTATION FAMILIES

Several standardized Annotation Families are provided with each of the PANYNJ project templates, and
their names shall not be changed.
The annotation family name should take the form of:
“CI-CATEGORY-DESCRIPTION1-DESCRIPTION2.rfa”
CI: Company Initials (Originator)
SUBCATEGORY
FAMILY SUBCATEGORIES
CODE
DI Detail Items
PR Profiles
Symbols
Generic Annotations
Callout Heads
SYM
Section Heads
Elevation Marks
View Title
TAG All Tags
TB Title-Blocks

For example:
• PA-TAG-ROOF.rfa
• PA-SYM-VIEWTITLE.rfa
• PA-SYM-NORTHARROW.rfa

NOTE:
If additional (not existing within the template) styles are needed, those should be named following the
existing styles naming convention, but instead of using “PA” use your company initials.
All text styles should use the Font Arial.

4.2.4 REVIT FAMILY TYPES

Types within a family file should indicate the key differences or variations between the different family
options. Depending on the family component, the type names might take one of the following forms:
• Model or Series Number
• Value or Capacity
• WidthxDepthxHeight

When naming family types, keep in mind the following:

• Capitalize the leading letters in each portion of the type name (when applicable).
• When types are named by size, use dimensions only.
• Keep file names as short as possible because they need to display in the type selector.
• Create a Type Catalog for family files that contain five or more types.
• Special characters like period or quotation marks are allowed.

2025 V.5 Last Updated: 03/01/2025

Page | 22
 Engineering BIM Standards

For example:
o WINDOWS-ANDERSEN-DOUBLEHUNG400SERIESARCHTOP.rfa

• WA1832
o Plumbing Fixtures-Generic-OvalUndercounterSink.rfa
• Standard Height
• ADA Height

4.2.5 WORKSETS
All models are required to be workshared. Each model should have at least Workset 1 and Shared Levels
and Grids in use.
When creating new Worksets, the Port Authority of NY & NJ BIM Standard naming convention should we
followed, adopting different approaches based on the project’s size and complexity. Workset names
should be defined according to their intended use.

4.2.5.1 DEFAULT
Naming Convention for this type of Worksets should take format of:
“Workset 1”
This is the default Workset to be used for all elements not specifically categorized in other Worksets.
Workset 1 cannot be deleted or merged. Because it is the only workset with this stipulation, do not
rename Workset 1.
“Shared Levels and Grids”
Default Workset to be used for all Levels, Grids, Scope Boxes, Reference Planes, and Work Planes. Do
not remove or rename.

Figure 4-1 - Default Worksets

2025 V.5 Last Updated: 03/01/2025

Page | 23
 Engineering BIM Standards

4.2.5.2 LINKED FILES

Additional Worksets shall be created for linked files:
• CAD links
• Revit links (1 Workset per Discipline)
• Point Cloud links

Naming Convention for linked files should take format of:

“LINK-DESCRIPTION”
For example:
• LINK-CAD
• LINK-STRUCTURAL
• LINK-POINTCLOUD

4.2.5.3 DISCIPLINE ELEMENTS

Additional Worksets can be created as needed by each discipline. The following factors should be
considered when creating Worksets:
• Project and Team size
• Project typology
• Disciplines involved
• Shared elements between models (lighting, rooms, etc.)
Naming Convention for this type of Worksets should take format of:
“D-DESCRIPTION”
ITEM DESCRIPTION
D Discipline Code
For example:
• A-LIGHTING (for Architecture)
• S-FOUNDATION (for Structural)
• M-PLUMBING (for Mechanical)
For large and/or complex projects, consider using the WHO-WHAT-WHERE logic for Worksets:
• A-EXTERIOR-LEVEL01
• M-EQUIPMENT-ZONEA
• S-FOUNDATION-EAST

4.2.5.4 WORKSET PROPERTIES

Active Workset: The Worksets to which new elements are added when selected.
Editing & Ownership: All Worksets can be edited, either by borrowing elements or checking out the
entire Worksets. If a Workset is Editable, the Workset is checked out which removes editing capability for
all elements on that Worksets from other users. If a Workset is non-Editable, the elements can be
borrowed by other users as needed.
Open/Closed: All Worksets can be closed which can improve model performance. If a Worksets is
closed, you will not be able to see elements on that Workset in any view regardless of Visibility settings.
Visibility: All Worksets can be shown in all or select views which can improve model performance.

2025 V.5 Last Updated: 03/01/2025

Page | 24
 Engineering BIM Standards

4.2.6 VIEWS
The Views should take the form of:
TC-LEVEL/LOCATION/SEQUENCE-DESCRIPTION

ITEM DESCRIPTION
TC View Type Code. Refer to chart below.
LEVEL/LOCATION/SEQUENCE Level Number or Location or Sequence
(Optional*) Number. (Two-digit integer)
DESCRIPTION
Brief User Description (up to 24 characters).
(Optional*)

NOTE:
All View names must include a Level/Sequence number and / or Description.
For Example:

Example including View Type, Level/Location/Sequence and Description:

• FP-LEVEL 01-CONSTRUCTION PLAN
• FP-02-SECOND FLOOR
• SEC-INTERIOR 01-ELECTRICAL ROOM
Example including View Type and Level/Location/Sequence:
• CP-03
• FP-LEVEL 01
• SEC-INTERIOR 01

4.2.6.1 VIEW TYPE CODES

General:
Table 4-4 - View Discipline General Type Codes

VIEW TYPE CODE VIEW TYPE NAME

3D 3D Views
AP Area Plans
BS Building Sections
RCP Reflected Ceiling Plans
CS Construction Staging or Construction Sequence
DL Drawing List
DR Drafting Views
DS Detail Sections
DV Detail Views
EE Exterior Elevations
EP Enlarged Plan
ES Engineering Estimates
FE Framing Elevation
FP Floor Plans
IE Interior Elevations

2025 V.5 Last Updated: 03/01/2025

Page | 25
 Engineering BIM Standards

VIEW TYPE CODE VIEW TYPE NAME

KL Keynote Legend
LG Legends
LP Location Plan
MT Material Takeoff
NB Note Block
NO General Notes
ON One Line Diagram Plan
QP Equipment Plan
RD Riser Diagram
RO Roof Plan
RP Reports
SEC Sections
SL Sheet List
SP Site Plan
SQ Schedule/Quantities
VL View List
WT Walkthroughs

Electrical:
Table 4-5 - Electrical Type Codes

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

2025 V.5 Last Updated: 03/01/2025

Page | 26
 Engineering BIM Standards

Architectural:
Table 4-6 - Architectural Type Codes

ARCHITECTURAL
VIEW TYPE CODE VIEW TYPE NAME
FU Furniture Plan
SP Signage Plan

Mechanical:
Table 4-7 - Mechanical Type Codes

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

Structural:
Table 4-8 - Structural Type Codes

STRUCTURAL
VIEW TYPE CODE VIEW TYPE NAME
CF Concrete Framing Plan
DP Decking Plan
FD Foundation Plan
FR Framing Plan
GC Graphical Column Schedule
JL 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

2025 V.5 Last Updated: 03/01/2025

Page | 27
 Engineering BIM Standards

4.2.7 LEVELS
At the beginning of each project, Architecture, or the lead discipline will establish the master level to be
used consistently across all Disciplines.
These levels should take the form of:
“DESCRIPTION-LEVEL”
ITEM DESCRIPTION
DESCRIPTION Level Description / Level Number
LEVEL This shall stay as is

Once the master levels are defined, all other disciplines must copy/monitor them, especially those critical
to their models. Typically, Architecture defines TOFF (Top of Finish Floor) levels, while Structure defines
TOS (Top of Slab) levels; These should also be copy/monitor by other disciplines as needed. Additional
discipline-specific levels may be created in individual Revit models only after primary levels are
successfully copied and monitored.

4.2.8 PHASES
Phases in Revit are used to simplify the creation of Renovation or Multi-Phases projects. Models should
include “Existing Conditions” and “New Construction” by default, with additional phases created as
needed and named consistently across all Revit models. The lead discipline will define the required
phases at project start, and each discipline leader will replicate them in their Revit models.

4.3 SHEET NAMING

The Sheet Names should take the form of:

“SHEET NUMBER-SHEET TITLE”

ITEM DESCRIPTION
SHEET NUMBER Sheet type code + Sheet number/s
SHEET TITLE Title or description

4.3.1 DRAWING TYPES

Drawing Types are categories used to organize the Contract Set of Drawings and refer to either one or
two letters that appear before the Sheet Number in the lower right-hand corner of each sheet.
The image shows an example of a Structural drawing:

Figure 4-2 - Example of Drawing Type Name

2025 V.5 Last Updated: 03/01/2025

Page | 28
 Engineering BIM Standards

The following table shows the Drawing Types Convention to be used on BIM Projects.
Table 4-9 - Drawing Type Naming Convention

ALL DISCIPLINES
TS Title Sheet
IX Index of Drawing Sheet
G General
SK Stage IV Sketch Sheets (For Stage IV use only)
CS Construction Staging or Sequence
ARCHITECTURAL
A Architectural
LS Landscape
CIVIL
C Civil
ML Marking Lighting & Signage
ELECTRICAL
CP Corrosion Protection
E Electrical
ES Electronics
FA Fire Alarm
ML Marking Lighting & Signage
ENVIRONMENTAL
N Environmental
GEOTECHNICAL
GT Geotechnical Plan
MECHANICAL
B Baggage Handling
FP Fire Protection
M Mechanical
P Plumbing
SP Sprinkler
VT Vertical Transportation
STRUCTURAL
S Structural
SS Super Structure
TRAFFIC
ITS Intelligent Transportation Systems
MT Maintenance of Traffic
SG Signal Plan
T Traffic

2025 V.5 Last Updated: 03/01/2025

Page | 29
 Engineering BIM Standards

4.3.2 DRAWING NUMBER

The Drawing Number Convention refers to the numbers that appear right after the Drawing Type and are
used to organize the Contract Drawings in order.
The Port Authority supports three options of sheet numbering, numbering by “One-Digit-Series”,
numbering by “Two-Digit-Series”, or numbering by “Counter” alone.
At the start of each project the Project Principal will determine which numbering option will be used. This
(and only this) option will be used by all disciplines for every contract drawing produced for the project.
When a “Series” numbering system is chosen by the Project Principal, each disciplines Task Leader will
be responsible for the determination of what drawing types are assigned to each of the available counters
in the series. This information will be distributed within the discipline by the Task Leader.
These three formats cannot co-exist on the same project. The Sheet Number will take the form of:

Option One Option Two Option Three

(001 through 999)

Counter Number

Counter Number

Counter Number
(01 through 99)
Series Number

(01 through 99)

(01 through 99)

Plotsheet Plan

Series Number
Plotsheet Plan

Plotsheet Plan
(1 through 9)
Type

Type

Type
S 1 01 S 01 01 S 001

Option I: One-digit series.

Option II: Two-digit series.
Option III: Without series.

4.3.2.1 OPTION I
For projects with nine or less series the sheet number format will include a one or two letter Plotsheet
Plan Type followed by a one-digit series number followed by a zero-padded, two-digit sheet “counter”
number.
• Use digits “1” through “9” as the series numbers.
• Series numbers can be skipped.
• Counter numbers must be consecutive numbers beginning at “01” for each series.
For example: D_Series Number_Drawing Counter
• S101

4.3.2.2 OPTION II
For projects with ten or more series the sheet number format will include a one or two letter Plotsheet
Plan Type followed by a two-digit series number followed by a two-digit sheet “counter” number.
• Use digits “01” through “99” as the series numbers
• Series numbers can be skipped
• Counter numbers must be consecutive numbers beginning at “01” for each series.

2025 V.5 Last Updated: 03/01/2025

Page | 30
 Engineering BIM Standards

For example: D_Series Number_Drawing Counter

• S0101

4.3.2.3 OPTION III

For projects that are not using a series the sheet number format will include a one or two letter Plotsheet
Plan Type followed by a zero-padded three-digit sheet “counter” number.
• Counter numbers must be consecutive numbers beginning at “001”
For example: D_Counter Number
• S001
The following images display how the three options would appear on a Plotsheet:

Option I Option II Option III

Figure 4-3 - Drawing Number options

4.3.3 SHEET CLASSIFICATION

Sheets should also be organized and controlled via parameters. The following Shared Parameters are
being used to properly classify sheet in the browser:
• PA-SHEET CATEGORY: Defines the sheet use.
• PA-SHEET SERIES: Defines the sheet type.

4.3.4 SHEET SET NUMBERING

All drawings must include sheet numbering in the upper-right corner of the set. However, it is not required
to incorporate this information in the Index of Sheets. Sheet numbering should be completed using
Bluebeam or other PDF readers with similar capabilities. For assistance, contact the VDC group.

NOTE:
The BIM Contract Border includes a parameter that allows the visibility of the “Sheet Numbering” to
toggled, displaying the format “Sheet [x] of [x]” for new drawings creating Addendum Process.

2025 V.5 Last Updated: 03/01/2025

Page | 31
 Engineering BIM Standards

5.0 TECHNICAL REQUIREMENTS

This section establishes specific requirements for the creation and collaboration of BIM files.

NOTE:
The content of this section is applicable for both Design and Construction Phases.

5.1 SOFTWARE

The Port Authority of NY & NJ CAD and BIM practice is comprised of several Autodesk products. The
VDC Standards will generally use terminology and references that are unique to the Autodesk-based
software applications.
All active project files shall be developed in accordance with the current software version in use by The
Port Authority of NY & NJ. This includes all third-party applications, regardless of when the project began.
Based on the backwards compatibility issues of some applications, please make sure to check which
version of the application is recently being used by the Port Authority of NY & NJ.
Current version used is 2024 for all Autodesk products.
Table 5-1 – Software Applications

Data Authoring *Specialist tools to be used where appropriate

Autodesk Revit
Autodesk Civil 3D
Autodesk AutoCAD
Autodesk MAP 3D
Data Exchange
E-Builder *project specific
OpenText *project specific
Autodesk Construction Cloud
Data Analysis
Autodesk Navisworks Manage
Synchro Pro
Primavera P6
Data Visualization
Microsoft Power BI
Asset Information Management
IBM Maximo
Sustainability Analysis
LCA Tally Plugin

2025 V.5 Last Updated: 03/01/2025

Page | 32
 Engineering BIM Standards

5.2 FILES OWNERSHIP

The Port Authority of NY & NJ holds ownership of the BIM Model including all inventions, ideas, designs,
and methods contained within. This includes, but is not limited to, Revit families (system-based and/or
component-based) and any other content submitted as part of the BIM Model itself.
Outside resources, such as consultants and/or contractors, using the BIM Model are granted temporary
use of it for the duration of the project. After project completion, they are required to return all copies of
the BIM Model to the Authority.

5.3 COORDINATE SYSTEMS

For all BIM projects the default coordinate systems are:

Horizontal:
Table 5.2. Default Horizontal Coordinate Systems.

STATE PLANE NAME CODE REGION UNIT

NAD83 New York State Plane NY83-LIF Long Island US Foot

NAD83 New York State Plane NY83-EF East Zone US Foot

New Jersey State Plane NJ83F US Foot US Foot

Vertical:

STATE PLANE NAME CODE REGION UNIT

NAVD88 State Plane NAVD88 North America US Foot

NOTE:
Depending on the project location, either the NY or NJ State Plane may apply. Therefore, it is necessary
that the CSG Group confirms which coordinates shall be applicable in each case. Also, the Project
Principal must determine at the beginning of the project if another coordinate system is to be used.
Finally, the project coordinate system selected will be established within the Site Model file by the VDC
Group and shared with the project team. All other BIM models’ coordinates necessary for the project
development are to set their coordinates by acquiring the ones established in the Site Model.

5.4 INFORMATION DELIVERY PLAN

The Information Delivery Plan (IDP) document contains the required information and data to be included
on each deliverable across the different project stages, such as:
• Level Of Development definitions.
• Model Element Table indicating the Level of Development (LOD) and Level of Information (LOI)
for elements.
• Project information data specification.
• Project common parameters data specification.
• Project detailed parameters data specification.
• Assets information requirements.

2025 V.5 Last Updated: 03/01/2025

Page | 33
 Engineering BIM Standards

5.4.1 LEVEL OF DEVELOPMENT (LOD)

The LOD defines the amount and degree of building information for both graphic and non-graphical
content. The latter one is often referred to as Level of Information (LOI). A popular “equation” has been
used nowadays to describe the formation of LOD as:
Level of Development = Level of Detail + Level of Information
The LOD is cumulative and should progress along with the design from stage to stage.
The LOD Specification is a reference that enables practitioners in the AEC Industry to specify and
articulate with a high level of clarity the content and reliability of Building Information Models (BIMs) at
various stages in the design and construction process.
The Port Authority of NY & NJ requires, at a minimum, that models adhere latest version of the BIM
Forum LOD Specification (Part I), publicly available at https://bimforum.org/lod.
This document shall be used along with the project specific Information Delivery Plan (IDP) spreadsheet
prepared by the Authority, where each element's LOD assignment is indicated, as well as the information
parameters to be included per element at each project stage.
The Port Authority of NY & NJ uses the term Design Model to distinguish a model in Design from a model
to be used for Construction purposes. Likewise, the term Construction Model is used to indicate a model
that has been developed to a higher level of LOD and shows how a project will be constructed in the field.

Figure 5-1 - Level of Development

2025 V.5 Last Updated: 03/01/2025

Page | 34
 Engineering BIM Standards

5.4.2 MODEL ELEMENT TABLE

The BIM models shall be created aligned with the Model Element Table meeting the Level of
Development (LOD) targets, by the end of each work stage.
Stage I Stage II Stage III Stage IV
Uniformat Omniclass Level Design (only) Attribute
Elements Conceptual Design Preliminary Design Basis of design Construction Attribute Table Coordination Sign-off As-Constructed
Table
1 2 3 4 5 1 2 3 4 5 LOD MEA LOD MEA LOD MEA LOD MEA LOD MEA
A 21- 01 00 00 SUBSTRUCTURE
A 10 21- 01 10 Foundations
A 10 10 21- 01 10 10 Standard Foundations
A 10 10 .10 21- 01 10 10 10 Wall Foundations Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 10 .30 21- 01 10 10 30 Column Foundations Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 10 .90 21- 01 10 10 90 Standard Foundation Supplemantary Components Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 21- 01 10 20 Special Foundations
A 10 20 .10 21- 01 10 20 10 Driven Piles Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .15 21- 01 10 20 15 Bored Piles Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .20 21- 01 10 20 20 Caissons Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .30 21- 01 10 20 30 Special Foundation Walls Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .40 21- 01 10 20 40 Foundation Anchors Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .50 21- 01 10 20 50 Underpinning Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .60 21- 01 10 20 60 Raft Foundations Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .70 21- 01 10 20 70 Pile Caps Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 10 20 .80 21- 01 10 20 80 Grade Beams Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 20 21- 01 20 Subgrade Enclosures
A 20 10 21- 01 20 10 Walls for Subgrade Enclosures
A 20 10 .10 21- 01 20 10 10 Subgrade Enclosure Wall Construction Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 20 10 .20 21- 01 20 10 20 Subgrade Enclosure Wall Interior Skin Common Parameters 200 PANYNJ 200 PANYNJ 300 EXTERNAL Common Parameters 300 EXTERNAL 300 EXTERNAL
A 20 10 .90 21- 01 20 10 90 Subgrade Enclosure Wall Supplymentary Components Common Parameters N/A PANYNJ N/A PANYNJ N/A EXTERNAL Common Parameters N/A EXTERNAL N/A EXTERNAL

Figure 5-2 - Model Element Table example

5.4.3 PARAMETERS
Defines Project, Common and Detailed parameters that are required by each modeled element by Stage.
Type Dataset Stage Field Definition Parameter Name Parameter Group Data Type Allowed Values Long Description Example Source
Project Project Information 1,2,3,4 Contract Number PA-CONTRACTNUMBER General String Any Contract Number assigned PAT-784.217 Assign By User
Project Project Information 1,2,3,4 Facility PA-FACILITY General String Per pick list Facility PATH Assign By User
Project Project Information 1,2,3,4 Line Department PA-LINEDEPARTMENT General String Per pick list Line Department AVIATION Assign By User
Project Project Information 1,2,3,4 PID PA-PID General String Any PID Number assigned 16010000 Assign By User
Project Project Information 1,2,3,4 Project Address Project Address General String Any Project Address Harrison, NJ 07029 Assign By User
Project Project Information 1,2,3,4 Project Name Project Name General String Any Project Name REPLACEMENT OF SUBSTATION 14 Assign By User
Project Project Information 1,2,3,4 CP Number PA-CPNUMBER Views and Sheets String Any Confidential Priviledge Number C Number Assign By User
Project Project Information 1,2,3,4 Work Order PA-WORKORDER Views and Sheets String Any Work Order Number #03 Assign By User
Project Project Information 1,2,3 BIM Standard Realease Date PA-BIMSTANDARDRELEASEDATE General String MM/DD/YYYY BIM Standard Realease Date MM/DD/YYYY Assign By User
Project Project Information 1,2,3 Discipline PA-DISCIPLINE Views and Sheets String Per BIM Standard's table Discipline of the Model Mechanical Assign By User
Project Project Information 1,2,3 SubDiscipline PA-SUBDISCIPLINE Views and Sheets String Per BIM Standard's table Subdiscipline of the Model Plumbing Assign By User
Project Project Information 1,2,3 Discipline Chief PA-DISCIPLINESCHIEF Views and Sheets String Any Name of the Discipline Chief in charge Name Assign By User
Project Project Information 1,2,3 Program Director PA-PROGRAMDIRECTOR Views and Sheets String Any Program Director assigned Name Assign By User
Project Project Information 1,2,3 Signee Name PA-SIGNEESNAME Views and Sheets String Any Original Signed By Name Assign By User

Figure 5-3 - Project Parameters

Type Dataset Stage Field Definition Parameter Name Parameter Group Data Type Allowed Values Long Description Example Source
Space Locational 1,2,3,4 Room Name Room Name Space String Must be unique per nomenclature The name of the room within the facility Pump Room Assign By User
Space Locational 1,2,3,4 Room Number Room Number Space String Must be unique per nomenclature The number of the room within the facility 5 Assign By User
Object 3D 1,2,3,4 Width Width Construction Floating Point >0 The width of the asset in inches or feet 8 (ft) Revit Built in Parameter
Object 3D 1,2,3,4 Depth Depth Construction Floating Point >0 The depth of the asset in inches or feet 8 (in) Revit Built in Parameter
Object 3D 1,2,3,4 Height Height Construction Floating Point >0 The height of the asset in inches or feet 4 (ft) Revit Built in Parameter
Object 3D 1,2,3,4 Volume Volume Construction Floating Point >0 The volume of the asset in cubic inches or feet 20 (cut) Revit Built in Parameter
Object 3D 1,2,3,4 Material PA-MATERIAL Materials and Finishes String Any Brief description of the principal material of the asset Concrete Assign By User
Space 3D 3,4 Is heated PA-ISHEATED Space Boolean Y or N Is the space mechanically heated N Assign By User
Space 3D 3,4 Is ventilated PA-ISVENTILATED Space Boolean Y or N Is the space mechanically ventilated Y Assign By User
Object 4D 4 Activity ID PA-ACTIVITYID Construction String Must be unique per nomenclature Schedule activity ID in accordance with schedule nomenclature PROJ4-12345 Assign By User
Object 4D 4 Construction Status PA-CONSTRUCTIONSTATUS Construction String Basis of Design, As Per Shop Drawing, As Constructed Defines the current status of the element per PANYNJ Workstage As-Constructed Assign By User
Object 4D 4 Stage PA-CONSTRUCTIONSTAGE Construction String Per Schedule and Contract Drawings Stage in which the project activity occurs in S3 Assign By User
Object 5D 3,4 Uniformat Level 4 Code Assembly Code Design & Construction String Per pick list (see Uniformat Level 4 Code) Division of work classification per Uniformat 2010 standard D3050.10 Predefined list
Object 5D 3,4 Uniformat Level 4 Description Assembly Description Design & Construction String Per pick list (see Uniformat Level 4 Description) Division of work classification per Uniformat 2010 standard Facility Hydronic Distribution Predefined list
Object 5D 3,4 PA Standard Spec. PA-SPEC Design & Construction String Per pick list Masterformat specifications-PANYNJ standard 08.41.13 (Doors-Generic-Exterior-Double-Two_Lite) Predefined list
Object 7D 3,4 Asset Flag PA-ASSETFLAG Asset Management String Y or N The Asset Flag is a Yes/No parameter designed to identify any asset. Y Assign By User

Figure 5-4 - Common Parameters

Dataset Stage Field Definition Parameter Name Parameter Group Data Type Allowed Values Long Description Example Source
Locational 1,2,3,4 Room Name Room Name Space String Must be unique per nomenclature The name of the room within the facility Pump Room Assign By User
Locational 1,2,3,4 Room Number Room Number Space String Must be unique per nomenclature The number of the room within the facility 5 Assign By User
3D 1,2,3,4 Width Width Construction Floating Point >0 The width of the asset in inches or feet 8 (ft) Built in Parameter
3D 1,2,3,4 Depth Depth Construction Floating Point >0 The depth of the asset in inches or feet 8 (in) Built in Parameter
3D 1,2,3,4 Height Height Construction Floating Point >0 The height of the asset in inches or feet 4 (ft) Built in Parameter
3D 1,2,3,4 Volume Volume Construction Floating Point >0 The volume of the asset in cubic inches or feet 20 (cut) Built in Parameter
3D 1,2,3,4 Material PA-MATERIAL Materials and Finishes String Any Brief description of the principal material of the asset Concrete Assign By User
3D 3,4 Is heated PA-ISHEATED Space Boolean Y or N Is the space mechanically heated N Assign By User
3D 3,4 Is ventilated PA-ISVENTILATED Space Boolean Y or N Is the space mechanically ventilated Y Assign By User
4D 4 Activity ID PA-ACTIVITYID Construction String Must be unique per nomenclature Schedule activity ID in accordance with schedule nomenclature PROJ4-12345 Assign By User
4D 4 Construction Status PA-CONSTRUCTIONSTATUS Construction String Basis of Design, As Per Shop Drawing, As Constructed Defines the current status of the element per PANYNJ Workstage As-Constructed Assign By User
4D 4 Stage PA-CONSTRUCTIONSTAGE Construction String Per Schedule and Contract Drawings Stage in project activity occurs in S3 Assign By User
5D 3,4 Uniformat Level 4 Code Assembly Code Design & Construction String Per pick list (see Uniformat Level 4 Code) Division of work classification per Uniformat 2010 standard D3050.10 Assign By User
5D 3,4 Uniformat Level 4 Description Assembly Description Design & Construction String Per pick list (see Uniformat Level 4 Description) Division of work classification per Uniformat 2010 standard Facility Hydronic Distribution Assign By User
5D 3,4 PA Standard Spec. PA-SPEC Design & Construction String Per pick list Masterformat specifications-PANYNJ standard 08.41.13 (Doors-Generic-Exterior-Double-Two_Lite) Predefined list
The Asset Flag is a Yes/No instance parameter used to identify elements representing assets in the 3D model. It must
7D 4 Asset Flag PA-ASSETFLAG Asset Management String Y or N be flagged as soon as the asset list is defined for the project and completed by selecting the checkbox where Y Assign By User
applicable.
The contractor will assign a unique 16-digit string to each asset, (such number will be connected to the rest of the
7D 4 Asset Tag PA-ASSETTAG Asset Management String 16-digit string information related to this same asset). Subsequently, upon the asset's installation on-site, a physical "asset tag" 2.45982E+15 Asset-specific Revit Category
bearing this code will be affixed to it.
The ADS code is generated by combining the Hierarchy Code, Subsystem Code, Asset Code, and Child Asset Code
7D 4 Asset Acronym PA-ADSCODE Asset Management String Per pick list (ADS Structure Sheet) FUNCT01A-PSBB-TUNN Asset-specific Revit Category
descriptions. To create this code, refer to the ADS Structure sheet provided in this row.
7D 4 Horizontal Location PA-HORIZONTALLOCATION Construction String To be specified in the BIM Execution Plan Describes asset positioning within the building layout relative to designated rooms. BR1 (Battery Room 1) TBD by Project
7D 4 Vertical Location PA-VERTICALLOCATION Construction String To be specified in the BIM Execution Plan Building level acronym where the asset/3D element is situated. L1 TBD by Project

Figure 5-5 - Detailed Parameters

2025 V.5 Last Updated: 03/01/2025

Page | 35
 Engineering BIM Standards

5.5 3D MODEL EXCLUSIONS

As a rule of thumb, objects smaller than 1” in size do not need to be modeled during the Design and
Construction phases.
The following objects are not mandatory in the BIM models, but may be included at the designer’s
discretion:
Table 5-3 - Model Exclusions
DISCIPLINE OBJECTS DESIGN CONSTRUCTION
Rebar X X
Structural Bolts X X
Anchors X
Couplings X
Fire Protection
Hangers X
Duct Insulation X
Pipe Insulation X
HVAC Couplings X
Filters X
Hangers X
Hangers for items X
Electronics
under 25lbs
Wires X X
Electrical
Conduits X
Couplings X
Plumbing
Hangers X

2025 V.5 Last Updated: 03/01/2025

Page | 36
 Engineering BIM Standards

6.0 DESIGN REQUIREMENTS

This section describes the requirements, processes and procedures currently demanded and in use by
The Port Authority of New York and New Jersey in relation to the use of BIM during the design phase,
which includes projects under Stage I to III for a traditional Design-Bid-Build project delivery method. For
Design-Build projects, this section should also be considered in addition to the Construction, any specific
process should be outlined in the BEP.

6.1 GOALS AND USES

The Design Model goal is to facilitate design coordination and generate Construction Documents.
As an owner, the PANYNJ considers the Design Model as a tool to facilitate:
• 2D Documentation linked to the 3D model.
• 3D BIM Coordination between all disciplines.
• 4D Simulation of future Construction phasing.
• 5D Cost Estimating and QTO.
• 6D Sustainability Analysis and Reporting.
• Risk mitigation, by providing reliable information earlier in time (compared to a non-BIM
methodology).
• Data recollection on relevant situations.

NOTE:
The specific project uses are to be confirmed with the Project Principal.

6.2 FOLDER STRUCTURE

The Port Authority of NY & NJ BIM Standard provides a structure for the organization of project
deliverables within the Engineering Department.
The primary goal is to improve coordination among all functional groups within the PANYNJ Divisions and
their Consultants, as well as to develop projects in a way that will facilitate the further use of the electronic
information beyond the initial contract.

6.2.1 FACILITY FOLDER

All Port Authority of NY & NJ projects are stored on a central server, which has internally been mapped
using the drive letter “M.” The Server (M:\ drive) is organized by Facility Folders using the following
Facility Codes.

Figure 6-1 - Facility Folder

2025 V.5 Last Updated: 03/01/2025

Page | 37
 Engineering BIM Standards

Table 6-1 - Facility Folder Codes

FACILITY CODE FACILITY NAME

AMT Automobile Marine Terminal
BB Bayonne Bridge
BRKMT Brooklyn Port Authority Marine Terminal
EP Elizabeth Port Authority Marine Terminal
EWR Newark Liberty International Airport
FERRY Ferry Transportation
GB Goethals Bridge
GWB George Washington Bridge and Bus Station
HCMF Harrison Car Maintenance Facility
HELI Downtown Manhattan Heliport
HH Howland Hook Marine Terminal
HT Holland Tunnel
IPY Industrial Park at Yonkers
JFK John F. Kennedy International Airport
JSTC Journal Square Transportation Center
LGA LaGuardia Airport
LT Lincoln Tunnel
MULTI Multi Facility Projects
NFC Newport Financial Center
NJMT New Jersey Marine Terminals
NLCC Newark Legal and Communication Center
OBX Outer Bridge Crossing
PABT Port Authority Bus Terminal
PACD Port Authority Police Academy
PATC Port Authority Technical center
PATH Port Authority Trans-Hudson Corporation
PHQ Police Headquarters
PJ Port Jersey
PN Port Newark
PRTC Police Rescue Training Center
RLLC Cross Harbor Rail Road NY/NJ
SWF Stewart International Airport
TEB Teterboro Airport
TLPT Staten Island Teleport
WTC World Trade Center

2025 V.5 Last Updated: 03/01/2025

Page | 38
 Engineering BIM Standards

6.2.2 _FIM FOLDER (FACILITY INFORMATION MODEL)

The Facility Information Model (_FIM) stores the latest version of the Facility 3D Model; completed
projects are uploaded here. The following image shows the workflow for PANYNJ BIM projects.
The FIM is stored as a Navisworks File Set (*.nwf) and composed of Navisworks Federated Files (*.nwf).

Figure 6-2 - Facility Information Model Flow Chart

The image below illustrates this concept using the _FIM Folder for PATH:

Figure 6-3 - FIM (Facility Information Model) Folder

6.2.3 PID FOLDER (PROJECT IDENTIFICATION)

The PID Number is a unique identifier assigned for all PANYNJ BIM projects. Every Facility Folder within
the Engineering Server has been divided into project folders using an eight-digit PID Number.
The image below illustrates this concept using a PATH project with the PID Number 07963625, which
includes the PIM Folder, the SM folder and eight pre-defined Discipline Folders.

Figure 6-4 - Example of a PID folder

2025 V.5 Last Updated: 03/01/2025

Page | 39
 Engineering BIM Standards

The Project Principal and/or Senior Design Executive shall request the creation of the Project Folder
Structure on the Engineering BIM server by filling out the TECNow form. Consultants are required to get
this number from either the Project Principal, or the discipline’s Task Leader (TL) at the project kickoff.

6.2.3.1 PID INTERNAL FOLDERS RULES

Table 6-2 - Rules for Project Folders

FOLDER RULES
Access for Other
Read-write
Sub-folders Disciplines
Permissions Archived
Permitted (Read-only
(per discipline)
Permission)
PIM ✓ ✓
SM ✓ ✓
DISCIPLINE ✓ ✓ ✓

6.2.4 _PIM FOLDER (PROJECT INFORMATION MODEL)

A Project Information Model (PIM) file is created for each BIM project. This file has a combination of all
the Revit-based and Civil 3D-based most recent Models. Each discipline should be exported as
Navisworks file (*.nwc).
The image below illustrates this concept using a project with the PID Number of 07963625, which
includes the PIM Folder at the top of the folder:

Figure 6-5 - Project Information Model

6.2.5 _SM FOLDER (SITE MODEL)

Each PID Folder contains an SM sub-folder that stores the Site Model file, which holds the project
coordinate system and controls the location, Project North, and elevation of all Discipline Models.
The image below illustrates this concept using a project with the PID Number of 07963625, which
includes the SM Folder.

Figure 6-6 - Site Model Folder

The Site Model Folder stores two files, an AutoCAD file in DWG format and a Revit file in RVT format,
both named PID-SM.

NOTE:
The VDC Group is responsible for creating and managing the files contained within the SM Folder.

2025 V.5 Last Updated: 03/01/2025

Page | 40
 Engineering BIM Standards

6.2.6 DISCIPLINE FOLDERS

This folder is used to share files among the eight Disciplines of the Port Authority of NY & NJ Engineering
Department:
• Architectural
• Civil
• Electrical
• Environmental
• Executive (for internal PA use)
• Geotechnical
• Mechanical
• RSD
• Structural
• Traffic

Every Discipline is provided with a folder in the Project Directory. Each Discipline folder has a series of
standardized sub-folders in which all design related data is to be stored.
The image below illustrates these standardized sub-folders using the Architectural folder as an example.

Figure 6-7 - Discipline Folders

The Model, Model_3D, Plotsheet, and Publish folders should always contain the most current version
and/or the working version of all CAD/BIM drawings related to the project. For more information on the
usage of these folders refer to the section titled Discipline Folder Rules of this standard.
The Project Principal should use the Executive folder to manage and coordinate the whole project
discipline files. This applies to all files produced in-house and by external consultants.
For more information on the Plotsheets_CP and PDF_CP folders refer to Appendix A Confidential &
Confidential Privileged Projects of this standard.

2025 V.5 Last Updated: 03/01/2025

Page | 41
 Engineering BIM Standards

6.2.6.1 DISCIPLINE INTERNAL FOLDER RULES

Each folder follows a predefined set of rules that both in-house teams and external consultants or
contractors must adhere to. The table below outlines the specific use and permissions for each folder,
ensuring consistency across all PA projects.
Table 6-3 - Folder Access Rules by Discipline

FOLDER RULES
Sub-folders Read-write Cross-Discipline
Permissions Access Archived
Permitted (per discipline) (Read-only Permission)
FROMOTHERPROJECTS ✓ ✓
MANAGEMENT ✓ ✓ ✓
MILESTONES ✓ ✓ ✓
MODEL ✓ ✓ ✓
MODEL_3D ✓ ✓ ✓
PHOTOS ✓ ✓ ✓ ✓
PLOTSHEETS ✓ ✓ ✓
PUBLISH ✓ ✓ ✓
RECEIVED ✓ ✓
RELEASED ✓ ✓
SCHEMES ✓ ✓
SCRATCH ✓ ✓
SHARED ✓ ✓ ✓

6.2.6.2 FROMOTHERPROJECTS FOLDER

This folder will contain drawings and data that have been taken from other projects that relate to the
current project. If a file from another project is required for reference purposes only and is not going to be
included as part of the contract set it will be stored in this directory. If a file is required to be part of the
contract set, then it will be copied to the MODEL/MODEL_3D folder and must comply with the current
CAD and BIM Standards. Related contracts and reference documents are shared in Livelink/E-Builder
with the consultants in Stage I through Stage III.

6.2.6.3 MANAGEMENT FOLDER

The MANAGEMENT folder will contain all non-drawing related project data. Spreadsheets, documents,
specifications, memos, estimates, etc. will be stored in this folder.

6.2.6.4 MILESTONES FOLDER

The MILESTONES folder is a location for storing independent (duplicate) copies of project information as
it appears at each milestone of the project. While the root Model, Model_3D, Plotsheets and Publish
folders contain the current versions of drawings which will evolve throughout the life cycle of the project,
the MILESTONES folder will preserve the state of those drawings at the instance of each milestone.
Sub-folders have been created for each submission milestone from Stage I through Stage IV.
Each discipline Task Lead is responsible for inviting their own discipline-specific Central Files into one of
the sub-folders within MILESTONES. After verifying that all discipline’s Task Lead have archived their
folders, the Project Principal should notify the VDC Group.

2025 V.5 Last Updated: 03/01/2025

Page | 42
 Engineering BIM Standards

NOTE:
For consultant led projects, the Project Principal shall post all discipline's files within the appropriate
subfolder of the Milestone folder within the Executive folder.

6.2.6.4.1 MODEL FOLDER

All design work and annotation must be stored inside AutoCAD drawings saved within the MODEL folder.
The CAD Standard refers to these design drawings as Model files.
Images and Office documents referenced or linked by drawing files will also be stored in the Model folder
and must comply with the rules for Model files. References to OLE objects are not permitted.

6.2.6.4.2 MODEL_3D FOLDER

This folder stores the Central Revit Model files.
Within this folder resides the SUPPORT sub-folder, which stores Revit-related information that is not
contained under any other available folder and does not need to be shared outside of each discipline.

6.2.6.4.3 PHOTOS FOLDER

The PHOTOS folder will contain all digital photographs relevant to the project, with the exception of those
used on contract drawings. If a photo needs to be part of the Contract Set, it should be moved or copied
into the MODEL or MODEL_3D folder and renamed accordingly.
Within this folder lives the RENDERING sub-folder, which stores Rendering files such as JPGs, PNGs,
TIFs, etc.

6.2.6.4.4 PLOTSHEETS FOLDER

All layouts for plotted sheets will be saved inside AutoCAD drawings stored within the PLOTSHEETS
folder. The CAD Standard refers to these layout drawings as Plotsheet Files. These files are assembled
sheets used for plotting. These drawings consist of a series of external references. Only Plotsheets files
will be stored within this folder.
All paper drawings in the Contract Set will have a corresponding Plotsheet file in the PLOTSHEETS
folder, the only exception is the Title Sheet.
Within this folder lives the PDF sub-folder, which stores PDF files assembled as sheets for printing. PDF
files will be created at full-size, directly from the Revit files and stored in the PDF folder.
The PDF folder will always contain the most recent milestone version of the PDF file(s). Earlier milestone
files once copied to the MILESTONES folder for the milestone will be either deleted from the PDF folder
or overwritten in place.

6.2.6.4.5 PUBLISH FOLDER

The PUBLISH folder will be used as a sharing mechanism between disciplines. A discipline may copy
Model files into its own PUBLISH folder, making them available for other disciplines to reference. Other
disciplines are not permitted to copy these files but will instead externally reference them directly from the
owner’s PUBLISH folder.
There will be only one Contract Border per project. The only exception to this rule is when new drawings
are added to the Contract Set as part of a Stage IV – PACC. If necessary, BIM Models will be exported as
DWG files and saved within this folder.

2025 V.5 Last Updated: 03/01/2025

Page | 43
 Engineering BIM Standards

It is important that this methodology for referencing design files from other disciplines be followed. If a
user copies design files from another discipline’s Model, Plotsheets or Publish folder then they must take
ownership of the file. By taking ownership, the discipline copying the file will then be responsible for all
CAD Standards compliance of that file as if it were created by that discipline. Only copies of Model files
for other disciplines to references shall be stored in the Publish folder. The owning discipline is not able to
reference file from its own PUBLISH folder.

6.2.6.4.6 HISTORY FOLDER

The HISTORY folder is the only sub-folder permitted within the PUBLISH folder. If a single file is to be
published more than once, the file that exists in the PUBLISH f older will be moved to a dated sub-folder
within the HISTORY folder. The updated version of the file will then be copied into the root of the
PUBLISH folder. This will allow other disciplines to continue to reference older or time-phased versions of
reference drawings if required by their design schedule by changing the external reference path to the
dated sub-folder within the History f older. Only copies of previously published files will be copied to the
HISTORY folder.

6.2.6.4.7 _DATASHORTCUTS FOLDER

The _DATASHORTCUTS folder is only populated in the folder structure for disciplines that use AutoCAD
Civil3D as an authoring application. This folder exists only under CIVIL and GEOTECHNICAL Publish
folder.
• This is the folder selected when setting up the Data Shortcut using Civil 3D the Toolspace
Prospector.
• Sub-folders are permitted within the _DATASHORTCUTS folder.
• The _DATASHORTCUTS folder has read-write permissions assigned to the owning discipline.
• Other disciplines have read permissions assigned to the _DATASHORTCUTS folder.
• The _DATASHORTCUTS folder will be archived with the project.

6.2.6.4.8 RECEIVED FOLDER

The RECEIVED folder will contain a dated archive of design information received from other disciplines
and outside sources. This folder is intended as a record to identify exactly what information was provided
and on what date.

6.2.6.4.9 RELEASED FOLDER

The RELEASED folder will contain a dated archive of design information provided to other disciplines and
outside sources. This folder is intended as a record to identify exactly what information was provided and
on what date.

6.2.6.4.10 SCHEMES FOLDER

The SCHEMES folder will contain various schemes of a design as well as any temporary design data.
This folder provides the designer with an area in which to make trial changes to a design and a place to
store temporary files. If a scheme is created and is later chosen as the final design version, the files
stored under that scheme are to be copied to the MODEL folder.
When using the Revit-based applications, Design Options is the preferred method to accomplish
schemes. This folder is a record intended to identify exactly when, and what information was provided to
a consultant.

2025 V.5 Last Updated: 03/01/2025

Page | 44
 Engineering BIM Standards

6.2.6.4.11 SCRATCH FOLDER

This folder is meant to be used by team members to work on details, or store Project related information
relevant to the Discipline members.

6.2.6.4.12 SHARED FOLDER

The SHARED folder will be used as a sharing mechanism for non-CAD\BIM-related information between
disciplines. A discipline may copy MANAGEMENT files into its own SHARED folder, making them
available for other disciplines. Files stored within the SHARED folder are not to be referenced into any
contract drawings and are provided for information only. Only copies of MANAGEMENT files shall be
stored in this folder. Model files are not permitted within the SHARED folder.

6.2.7 NEW FOLDERS

If additional sub-folders are required and permitted by the folder’s rules, they should be created within
the predefined project folder structure and adhere to the established folder naming convention.
Folders naming format:
“YYYY-MM-DD-Description”

ITEM DESCRIPTION
YYYY Four-digit Year
MM Two-digit Month
DD Two-digit Day
Brief User Description (up to 24 characters)
Description (optional) The following characters should not be used as part of the description: @ $ %
^&<>/\“”:;?*|,‘

6.2.8 AUTODESK CONSTRUCTION CLOUD (ACC) FOLDER STRUCTURE

The Port Authority of NY & NJ BIM Standard provides a structure for the organization of BIM projects on
Autodesk Construction Cloud.
A folder structure shall be created that is familiar with the PA internal drives. The folder structure is
created by the VDC Engineer using a Template with permissions and roles set up for consistency.
For more information refer to Autodesk Construction Cloud Guideline.

6.3 DESIGN SITE MODEL (SM)

The Site Model (SM) file is created and distributed by the VDC Group at the Project’s BIM Kick-off
meeting. This Site Model file has a combination of Aerial Photograph and CAD Files obtained from The
Port Authority of NY & NJ BMMS (Base Map Management System) and specific CAD file background with
coordinates provided by Central Survey Group. This file holds the project coordinate system and controls
the location, rotation, and elevation. All Discipline models must link the SM and acquire the project
coordinates from it. This model shall NOT be modified, will be provided for reference only.
Upon receipt of the base Site Model, the Consultant must perform an assessment to determine if there is
any information of particular importance that may require additional validation. .

NOTE:
Refer to Section 7.2 Construction Site Model for Site Model requirements during Construction.
2025 V.5 Last Updated: 03/01/2025
Page | 45
 Engineering BIM Standards

6.4 DESIGN CONTEXT MODEL (SCM)

This section refers to the particularities of the site Context Model, as a special case among all Models to
be developed by the BIM authors. The site Context Model developed during Design will be used as a
base to be further developed during Construction.
The Design site Context Model is a subcomponent of the Design Models, being the context the one that
must include all elements in the project surroundings (e.g., topography, property lines, fences, traffic
elements, buildings, bridges and more).
It is worth mentioning that due to the different project types within the PANYNJ portfolio, and their
potential locations, the Context Model requirements can greatly vary between projects.

6.4.1 DESIGN CONTEXT MODEL LIFECYCLE

The Consultant/BIM Leader is the owner and solely responsible for the development of the Context
Model. The Context model shall be submitted for Compliance Review in each official submission as part
of the Design Deliverables package.

Figure 6-10 – Design Context Model creation workflow

6.4.2 GOALS AND USES

Specific goals pursued by the Context Model include:
• To support site planning and logistics.
• To improve connectivity and accessibility.
• To improve sense of place adding to the development identity.
• To improve security.

6.5 DESIGN MODELS

The design model is a 3D representation, typically created in Revit, of each one of the disciplines that are
involved in a Project. Task leaders, adhering to Agency Standards, are responsible for developing these

2025 V.5 Last Updated: 03/01/2025

Page | 46
 Engineering BIM Standards

models and ensuring their continuous progress. To enhance coordination and accurately convey the
design intent, design models shall include links to the other discipline models.

2025 V.5 Last Updated: 03/01/2025

Page | 47
 Engineering BIM Standards

6.5.1 DESIGN MODELS CREATION WORKFLOW

Utilizing the PANYNJ BIM Revit Templates provided by the VDC group, each discipline will develop its
own design model. Once the model is created, project coordinates must be acquired from the Site Model
provided also by the VDC group. For initial settings, the Architectural file shall define the main levels of
the project, and the Structural file shall establish the primary grids. All other disciplines involved in the
same project shall use the Revit ‘copy/monitor’ function to replicate these levels and grids. When this
process is completed by all teams, each discipline shall link the other project models into their own to
ensure coordination and alignment.

Figure 6-11 - Design Models creation workflow

6.5.2 LINKING FILES

The process of linking files into Revit models follows specific guidelines:

6.5.2.1 LINKING REVIT FILES

All project Revit files should be linked into each other, including the Site Model.
Linked models must be pinned in place to ensure that they retain their coordinates relative to the active
model and other linked models in the project.

6.5.2.2 LINKING AUTOCAD FILES

There are some types of AutoCAD Drawings that might need to be linked into Revit; these are called
Reference Drawings. These refers to drawings such as Floor Plans, that will be used as an underlay to
build Revit Elements from their entities and will not be part of the Contract Set.

2025 V.5 Last Updated: 03/01/2025

Page | 48
 Engineering BIM Standards

The following minimal settings are required before linking them into Revit:
• Linked files should not contain ‘external references’.
• To preserve the AutoCAD line weight inside Revit, the line weight column within the ‘Layer
Properties Manager’ dialog box should be set to ‘Default’.
• Avoid importing unnecessary data like hatching or line-work such as construction lines.
• Delete all unnecessary parts and layers of the DWG file within AutoCAD and import only the
cleaned smaller version.
• Minimize the number of linked or imported DWG files.
• Only link essential DWG files into views.
• All linked AutoCAD files should be pinned.
• Do not explode the geometry imported from DWG files. The exploding operation within a Revit-
based application can change a DWG from a single-managed element to hundreds or thousands
of additional elements, depending on the number of entities in the imported DWG.

NOTE:
The Import CAD Tool should never be used instead of the Link CAD Tool since the Revit-based
applications handles AutoCAD entities individually, decreasing overall Model performance.
Reference Drawings are typically linked into Floor Plan Views and/or Ceiling Plan Views and are usually
used as an underlay to build Revit Elements from their entities.
In addition to the requirements described above, the Reference Drawings should have the following:
• DWG files shall be on NAD83 Coordinate System or as defined by the SM.
• DWG files shall be saved using the World Coordinates System (WCS) before they are linked into
in Revit in order to be correctly aligned.
• Elements within the DWG cannot be more than 2 miles apart from each other.

6.5.2.3 LINKING POINT CLOUDS

All Point Cloud files should be linked into the Revit models by shared coordinates.
Linked files must be pinned in place to ensure that they retain their coordinates relative to the active
model and other linked models in the project.

6.5.3 SHARED PARAMETERS

The Revit-based applications enable the creation of custom fields that may be shared between project
and family files and be scheduled and called out correctly through a function named “Shared
Parameters”. The Authority has made available a list of Shared Parameters that includes parameters that
are needed for schedules and may be added to as needed.
Refer to Information Delivery Plan spreadsheet for common and detailed parameters.

2025 V.5 Last Updated: 03/01/2025

Page | 49
 Engineering BIM Standards

6.5.4 STARTING VIEW

A Legend View is included in all Project Templates that allows important Project Information to be readily
available upon opening the project, as it is set as the default starting View. This View is used when
synchronizing with the Central model.

Figure 6-12 - Example of Starting View

Within the view you will find basic information and different references to other Legends that will provide
guidance on important aspects related to the use of Revit.

2025 V.5 Last Updated: 03/01/2025

Page | 50
 Engineering BIM Standards

6.5.5 PROJECT INFORMATION

Project Information should be completed at the beginning of the project.

Figure 6-13 - Project Information

2025 V.5 Last Updated: 03/01/2025

Page | 51
 Engineering BIM Standards

6.5.6 PROJECT BROWSER

Customized Revit Project Browser has been included within the different Discipline Templates, in which
Views and Sheets within the Project Browser will be grouped based on the PA-View Classification as
follows:
Table 6-4 - Types of project Browsers within a Discipline Template

PROJECT BROWSER
PA - VIEW CLASSIFICATION DESCRIPTION
Views are intended to be the Views that maintain the
coordination across the different Discipline Revit Models as
well as for coordination purposes only. These types of Views
COORDINATION include Floor Plans, Ceiling Plans, 3D Views and Elevations.
Subcategories have been defined and indicate the purpose
of each view: EXPORT, MODEL INTEGRITY and QAQC.
These views should not be deleted.
DOCUMENTATION Views intended to be included in the Contract Set.
These types of Views are for working purposes only and not
intended to be included in the Contract Set. These are
WORKING
temporarily views that should be deleted before the final
submission.

Figure 6-14 - General Project Browser

The Project Browser scheme should be set to “PA–CATEGORYSERIES”. Do not edit the Filter or Sort
settings of this scheme. It is fine to add other browser schemes temporarily, however, be sure to reset the
scheme to “PA–CATEGORYSERIES” as part of the submission preparation process.

2025 V.5 Last Updated: 03/01/2025

Page | 52
 Engineering BIM Standards

All Views need to be associated to their corresponding Category by assigning the appropriate View
Template. Once assigned, the associated Category will be shown in the correspondent parameters under
Identity Data.

Figure 6-15 - Highlighted PA-VIEW CATEGORY and PA-VIEWSERIES parameters

6.5.7 TEXT STYLES

Several Text Styles have been defined within the Templates as follows:
• PA-NOTE-ARIAL1/8-OPAQUE
• PA-NOTE-ARIAL1/8-TRANSPARENT
• PA-NOTE-ARIAL1/16-OPAQUE
• PA-NOTE-ARIAL1/16-TRANSPARENT
• PA-NOTE-ARIAL3/32-OPAQUE
• PA-NOTE-ARIAL3/32-OPAQUE-BOLD
• PA-NOTE-ARIAL3/32-OPAQUE-RED
• PA-NOTE-ARIAL3/32-TRANSPARENT
• PA-NOTE-ARIAL3/32-TRANSPARENT-BOLD
• PA-NOTE-ARIAL3/32-TRANSPARENT-RED
• PA-TITLE-ARIAL1/8-OPAQUE-BOLD
• PA-TITLE-ARIAL1/8-TRANSPARENT-BOLD
• PA-SCHEDULE TEXT-1
• PA-SCHEDULE TEXT-2

NOTE:
If a new text style is needed, they must follow the naming convention:
“ORIGINATOR-CATEGORY-DESCRIPTOR-SUBDESCRIPTOR”
Start with two letters for the ORIGINATOR “XX", followed by the new text style, the font and size, followed
by other attributes if applicable.
Only ARIAL font style is allowed in Text Styles.
2025 V.5 Last Updated: 03/01/2025
Page | 53
 Engineering BIM Standards

6.5.8 DIMENSIONS STYLES

Several Dimension Styles have been defined within the Templates as follows:
• PA-LINEAR-ROUNDED1/2-OPAQUE
• PA-LINEAR-ROUNDED1/2-TRANSPARENT
• PA-LINEAR-ROUNDED1/4-OPAQUE
• PA-LINEAR-ROUNDED1/4-TRANSPARENT
• PA-LINEAR-ROUNDED1/4-OPAQUE-INCHES
• PA-LINEAR-ROUNDED1/4-TRANSPARENT-INCHES
• PA-LINEAR-ROUNDED1/4-OPAQUE-ALTUNITS
• PA-LINEAR-ROUNDED1/4-TRANSPARENT-ALTUNITS
• PA-LINEAR-ROUNDED1/8-OPAQUE
• PA-LINEAR-ROUNDED1/8-TRANSPARENT
• PA-LINEAR-ROUNDED1/16-OPAQUE
• PA-LINEAR-ROUNDED1/16-TRANSPARENT
• PA-LINEAR-ROUNDED1/32-OPAQUE
• PA-LINEAR-ROUNDED1/32-TRANSPARENT
• PA-LINEAR-WORKINGEXACT-OPAQUE-RED
• PA-LINEAR-WORKINGEXACT-TRANSPARENT-RED

Identical Dimension Styles have been created for Radial and similar options for Angular, but it is
important to define, at the beginning of the project, which are the dimensions styles that will be needed in
order to keep the file clean and avoid unnecessary mistakes.

NOTE:
If a new dimension style is needed, they must follow the naming convention:
“ORIGINATOR-CATEGORY-DESCRIPTOR-SUBDESCRIPTOR”
Start with two letters for the ORIGINATOR “XX”, followed by the new dimension style, the rounding and
other attributes if applicable.
Only ARIAL font style is allowed in Dimensions Styles.

2025 V.5 Last Updated: 03/01/2025

Page | 54
 Engineering BIM Standards

6.5.9 LINE STYLES

Different Line Styles that match the Line Weights have been provided as follows:
Table 6-5 - Line Styles
LINE STYLES
NAME PEN # (WIDTH) LINE PATTERN
PA-BLACK-SOLID-PEN01 1 (0.0040”) Solid Black
PA-BLACK-SOLID-PEN02 2 (0.0080”) Solid Black
PA-BLACK-SOLID-PEN03 3 (0.0100”) Solid Black
PA-BLACK-SOLID-PEN04 4 (0.0150”) Solid Black
PA-BLACK-SOLID-PEN05 5 (0.0200”) Solid Black
PA-BLACK-SOLID-PEN06 6 (0.0280”) Solid Black
PA-BLACK-SOLID-PEN07 7 (0.0360”) Solid Black
PA-BLACK-SOLID-PEN08 8 (0.0480”) Solid Black
PA-RED-SOLID-PEN04 4 (0.0150”) Solid Red
PA-GREY20-SOLID-PEN08 8 (0.0480”) Solid Grey
PA-GREY40-SOLID-PEN06 6 (0.0280”) Solid Grey
PA-GREY60-SOLID-PEN04 4 (0.0150”) Solid Grey
PA-GREY80-SOLID-PEN02 2 (0.0080”) Solid Grey

NOTE:
If a new Line style is needed, they must follow the naming convention:
“ORIGINATOR-CATEGORY-DESCRIPTOR-SUBDESCRIPTOR”
Start with two letters for the ORIGINATOR “XX", followed by the new dimension style, the rounding and
other attributes if applicable.
Only ARIAL font style is allowed in Dimensions Styles.

6.5.10 LINE WEIGHTS

Line Weights have been provided for Model, Annotation and Perspective Objects as follows.
Sixteen Line Weights have been provided for Model, Perspective and Annotation Objects, which have
been defined at the 1/8” = 1’ Scale.
Table 6-6 - Line Weights

MODEL AND ANNOTATION LINEWEIGHTS

PEN # WIDTH
1 0.0040”
2 0.0080”
3 0.0100”
4 0.0150”
5 0.0200”
6 0.0280”
7 0.0360”
8 0.0480”

2025 V.5 Last Updated: 03/01/2025

Page | 55
 Engineering BIM Standards

6.5.11 SYMBOLS
Different Annotations such as, Tags, Callouts, North Arrow, Graphic Scales, View titles, among others
have been pre-loaded within the Templates based on the Discipline.

NOTE:
The Annotation Symbols are loaded under the Project Browser under FAMILIES tab within the Annotation
Symbols.
If a new symbol is needed, they must follow the naming convention:
“ORIGINATOR-SYM-DESCRIPTION1-DESCRIPTION2”
Start with two letters for the originator “XX”, followed by the new Symbol Type, then DESCRIPTION 1,
followed by DESCRIPTION 2 if applicable.
Only ARIAL font style is allowed in Symbols, if a text style is needed.

6.5.12 VIEW TITLE

All PA View Title families have a toggle control checkbox parameter (“View Scale”) that allows for the
scale to be hidden when the box is unchecked or displayed when the box is checked.

To display View
Scale, check this box.
To hide it, uncheck it.

Figure 6-16 – View Scale checkbox

Given the preference for the use of graphic scales in most projects, the View Title families have been set
to have their scales hidden by default. View Titles should see as the image below:

Figure 6-17 - Example of View Title family and Type Properties

6.5.13 GRIDS
Two Standard Grids have been provided as follows:
• PA-GRID-EXISTING (for existing construction)
• PA-GRID- NEW (for new construction)

2025 V.5 Last Updated: 03/01/2025

Page | 56
 Engineering BIM Standards

6.5.14 ELEVATIONS
Four Standard Elevations have been provided under the Coordination View in the Project Browser as
follows:
• EE-EAST ELEVATION
• EE-NORTH ELEVATION
• EE-SOUTH ELEVATION
• EE-WEST ELEVATION

6.5.15 FILLED REGIONS

Fill Regions (opaque and transparent) have been provided as follows:
Table 6-7 - Filled Regions

SCREENING
FILLED REGION NAME RGB VALUE RGB COLOR
PA-BLACK100%-OPAQUE
000-000-000
PA-BLACK100%-TRANSPARENT
PA-BLACK80%-OPAQUE
050-050-050
PA-BLACK80%-TRANSPARENT
PA-BLACK60%-OPAQUE
100-100-100
PA-BLACK60%-TRANSPARENT
PA-BLACK40%-OPAQUE
150-150-150
PA-BLACK40%-TRANSPARENT
PA-BLACK20%-OPAQUE
200-200-200
PA-BLACK20%-TRANSPARENT

NOTE:
Other “Out-of-the-Box” Fill Regions exist within the template to use.

2025 V.5 Last Updated: 03/01/2025

Page | 57
 Engineering BIM Standards

6.5.16 FILL PATTERS

Several Fill Patterns have been created in order to avoid inserting patterns not approved by the Agency,
for most cases patterns will be found in a small, medium and large versions:
Table 6-8 - Fill Patterns

FILL PATTERNS
PA-FILL2D-ANSI31 PA-FILL2D-CONC PA-FILL2D-GRATE
PA-FILL2D-ANSI32 PA-FILL2D-CONC-PRECAST PA-FILL2D-GRAVEL
PA-FILL2D-ANSI33 PA-FILL2D-CORK PA-FILL2D-GYPSUM
PA-FILL2D-ANSI34 PA-FILL2D-CROSS PA-FILL2D-HERRING
PA-FILL2D-ANSI35 PA-FILL2D-DASH PA-FILL2D-HEXAGONS
PA-FILL2D-ANSI36 PA-FILL2D-DIAG-DN PA-FILL2D-HONEY
PA-FILL2D-ANSI37 PA-FILL2D-DIAG-UP PA-FILL2D-HORIZ
PA-FILL2D-ANSI38 PA-FILL2D-DOLMIT PA-FILL2D-HOUND
PA-FILL2D-ALUM PA-FILL2D-EARTH PA-FILL2D-INSUL
PA-FILL2D-BOND PA-FILL2D-FLEMISH PA-FILL2D-MASONRY-BLOCK
PA-FILL2D-BRASS PA-FILL2D-RUBBER PA-FILL2D-STEEL
PA-FILL2D-MDF PA-FILL2D-RUNNING PA-FILL2D-STONE
PA-FILL2D-PARQUET PA-FILL2D-SAND PA-FILL2D-TACTILE
PA-FILL2D-PERF PA-FILL2D-GLASS PA-FILL2D-TRIANGLE
PA-FILL2D-PLASTER PA-FILL2D-SEALANT PA-FILL2D-VERT
PA-FILL2D-PLY-VENEER PA-FILL2D-SIDING PA-FILL2D-MASONRY-BRICK
PA-FILL2D-PLYWOOD PA-FILL2D-STACK PA-FILL2D-WOOD

NOTE:
Other “Out-of-the-Box” Fill patterns exist within the template to use. New Fill Patterns can be created,
they must follow the standard naming convention.

6.5.17 SCHEDULES
A series of Engineering Estimates Schedules are included in the Discipline Templates. These schedules
are categorized into two types:
• Schedules starting with “PA-DOC” are intended to support documentation or provide individual
information.
• Schedules starting with “PA-QTO” and “PA-MTO” are designed to assist the estimating process.
Additionally, a general list schedule has been incorporated for reference. For more details about
the Estimating process, refer to Section 6.5.21 Quantity Take Off.

NOTE:
Schedules can be duplicated within the Revit Model so the Filter and Sorting/Grouping Categories can be
used.
There are two “Admin” schedules created for QC purposes that should not be deleted or modified, those
are “PA-Admin-Multi-Category” and “PA-Admin-ViewList”.

2025 V.5 Last Updated: 03/01/2025

Page | 58
 Engineering BIM Standards

6.5.18 PHASES
Phases can be created to match the Project Construction Phases as necessary. The Lead Discipline is
responsible for coordinating how many Phases the project might have. For naming convention, refer to
Section 4.2.8 Phases. Phase Settings for Existing, Demolished, New and Temporary have been set as
shown in the image below. These settings for Phase Filters and Graphic Overrides should not be
modified.

Figure 6-18 - Graphic Overrides

Figure 6-19 - Phase Filters

2025 V.5 Last Updated: 03/01/2025

Page | 59
 Engineering BIM Standards

6.5.19 ROOMS
Rooms are Revit elements that should be created in the Architecture model, these elements are defined
by other elements in the model like walls and ceilings. All rooms should be enclosed spaces. In the
project, the room properties must be filled (like the room number and the room name). Having that
information completed, will help in the further steps like a model analysis, quantity takeoff, etc.
Room Computation has been enabled for Area and Volumes and has been set at wall finish as shown in
the image below.

Figure 6-20 - Area and Volume Computation Dialog Box

6.5.20 VIEW TEMPLATES

View Templates in Revit are predefined sets of rules and settings that are applied to views in a model.
They help ensure consistency, save time, and maintain standards across the project. This approach
streamlines tasks such as documentation, coordination, and visualization by automating and
standardizing view settings, including:
• Visibility/Graphics Overrides: control elements visibility and appearance (e.g., line weights,
patterns and colors)
• View Display Settings: Define settings like detail level, scale, and display styles.
• Filters and Overrides: Apply specific filters to highlight or hide elements.
• Discipline-Specific Customization: Tailor views for architecture, structure, or MEP purposes.
The VDC group has incorporated View Templates into each Revit Discipline Template using the
corresponding naming conventions and aligning them with the type of view they represent.

2025 V.5 Last Updated: 03/01/2025

Page | 60
 Engineering BIM Standards

6.5.20.1 MEP FILTERS AND COLOR SCHEMES

MEP Filters have been incorporated into each MEP Discipline View Template, assigning a unique color to
each system. This helps identify systems within the model, streamline modeling workflows, enhance
coordination, ensure quality control, and improve documentation. Users can utilize the pre-configured
views organized by discipline within the template.
Table 6-9- MEP Color Schemes

DISCIPLINE TRADE BREAKDOWN COLOR RGB LINE TYPE

Sprinkler Piping - Dry Dark Red 139,0,0 Solid

Sprinkler Piping - Wet Red 255,0,0 Solid

FIRE Solid
Sprinkler Piping - Pre-Action Yellow 255,255,0
PROTECTION
Clean Agent Purple 128,0,128 Solid

Deluge Blue 0,0,255 Solid

Piping - Chilled Water Supply Light Blue 173,216,230 Solid

Piping - Chilled Water Return Dark Blue 0,0,139 Dash Dot

Piping - Refrigerant Liquid Cyan 0,255,247 Solid

Piping - Refrigerant Suction Light Blue 0,204,255 Solid

Piping - High Pressure Steam Dark Red 139,0,0 Solid

Piping - Medium Pressure Steam Red 255,0,0 Solid

Piping - Low Pressure Steam Light Red 255,102,102 Solid

Piping - High Pressure Condensate Dark Green 0,100,0 Solid

HVAC
Piping - Low Pressure Condensate Light Green 0,255,0 Solid

Piping - Condenser Watter Supply Orange 255,165,0 Solid

Piping - Condenser Watter Return Dark Orange 255,140,0 Dash

Duct - Supply Air Green 0,176,80 Solid

Duct - Return Air Grey 217,217,217 Solid

Duct - Exhaust Air Magenta 255,0,255 Solid

Duct - Toilet Exhaust Air Light Brown 255,192,0 Solid

Duct - Kitchen Exhaust Air Light Yellow 242,250,10 Solid

Piping - Domestic Cold Water Blue 14,14,232 Solid

Piping - Domestic Hot Water Red 242,12,104 Solid

Piping - Domestic Hot Water Return Pink 255,109,109 Dash Dot

PLUMBING Piping - Sanitary Sewer Brown 139,69,19 Solid

Piping - Vent Light Green 169,208,142 Solid

Piping - Storm Grey 217,217,217 Solid

Piping - Natural Gas Yellow 255,255,0 Solid

2025 V.5 Last Updated: 03/01/2025

Page | 61
 Engineering BIM Standards

6.5.20.2 INTER-DISCIPLINE FILTERS

Within the template, there are 2D and 3D views that include all disciplines links for coordination purpose.
Filters can be created to easily identify discipline elements using the workset option and the Inter-
discipline Color Scheme outlined in Section 6.8.1 Inter-discipline Color Scheme.

6.5.21 QUANTITY TAKE-OFF

The Quantity Take-off (QTO) process is designed to enable accurate and efficient estimation of material
quantities and project costs directly from BIM models. By leveraging parametric data embedded within
model elements, QTO allows project teams to extract, categorize, and quantify components precisely,
aligning with project requirements and improving cost management across the project lifecycle.

The VDC group has incorporated QTO schedules to Revit templates organized by the Port Authority Spec
Divisions to obtain material and quantity information directly from models. These schedules start with “PA-
QTO” and “PA-MTO”.

The Design team must assign the appropriate PA Spec Number to each 3D model element to ensure
these elements are listed into the QTO schedules and that automatic QTO calculations are generated. To
achieve this, ensure that the “PA-5D Estimating.txt” is loaded in Revit by navigating to Manage>
Additional Setting> Assembly Code.

Figure 6-21 - Division 04 schedule from Revit

2025 V.5 Last Updated: 03/01/2025

Page | 62
 Engineering BIM Standards

Figure 6-22 - Division 04 elements from Revit

After assigning the relevant PA Spec data, schedules should be exported from Revit to Excel files. This
export can be performed individually per Division Schedule or via an Add-in to gather all information
simultaneously. The exported Excel data will then populate the Port Authority cost estimation template
provided by the Estimating Division.

NOTE:
The VDC Engineer assigned to the project is responsible for supporting the Design Team throughout this
process.

6.5.22 SUSTAINABILITY ANALYSIS

Life Cycle Assessment Analysis (LCA)
One of the most common methodologies for quantifying sustainability is Life Cycle Assessment (LCA).
This analysis of environmental impact includes the entire life cycle course of product, material, process, or
other measurable activities. Results from this analysis consist of various impact outcomes such as Global
Warning Potential (GWP), Ozone Depletion Potential (ODP), Smog Formation Potential (SFP), Primary
Energy Demand (PED), Non-Renewable/ Renewable Energy Demand.

Figure 6-23 - Life Cycle Assessment

2025 V.5 Last Updated: 03/01/2025

Page | 63
 Engineering BIM Standards

Figure 6-24 - LCA Outcomes

Designers and consultants must be able to conduct a Whole Building Life Cycle Assessment (WBLCA)
using Building Information Models (BIM) as part of the Port Authority requirements. However, building
models do not contain all the data that go into a building. Additional tools are required to add another
layer of detail to BIM by recognizing materials that are not modeled explicitly, such as the steel in
concrete assemblies, and by considering a model's diverse range of material classes.

LCA deliverables will be coordinated and managed by the Port Authority Resilience and Sustainability
Engineering group (RSE).

For more information about LCA scope, requirements and regulations, refer to this link: Resilient &
Sustainable Engineering - Tally LCA.

6.6 ADDENDUM MODELS

Designers should create a copy of the latest Design Model version before applying any addendum
changes. This saved version must be documented under Model Status in the PA-Admin-Dashboard as
Design Model_VXX.
Once this copy is created, the Addendum Model box must be checked in the live model to indicate that
the current version will contain Addendum Drawings.

Figure 6-25 - Addendum Model Status

2025 V.5 Last Updated: 03/01/2025

Page | 64
 Engineering BIM Standards

6.6.1 ADDING DRAWINGS TO CONTRACT DRAWINGS

If a new sheet is added to the set, the design team must bubble the drawing index indicating that a new
drawing has been added to the Contract Set. This new sheet should be placed below the last drawing in
the corresponding drawing series, and it will not contain a sheet number. As it does not contain a sheet
number, the top-right sheet numbering on the drawing must remain hidden, refer to Section 4.3.4 for
further details.

Figure 6-26 - Index for Added Drawings

Added drawings should not have revision clouds on the sheet for the corresponding addendum but
should contain a revision in the contract border with a description 'Addendum No.x – Added Drawing' and
the issue date.
The contract border for added drawings should include the updated contract border date, where the
original contract border is updated by replacing the Project Issue Date parameter with the Issue Date
parameter, as provided by VDC. Once the contract border is updated, the sheets within the model are
managed using the Sheet Issue Date parameter. The issue date for new sheets must be individually
updated on each sheet.

Figure 6-27 - Revision for New Drawings

The 'Added Drawing' note should be included in the description using the PA-TEXT-ARIAL-3/32” font,
while 'Addendum No. x' will be completed in the description field of the revision schedule.

2025 V.5 Last Updated: 03/01/2025

Page | 65
 Engineering BIM Standards

Figure 6-28 - Revision for New Drawings

6.6.2 MAKING REVISIONS IN CONTRACT DRAWINGS

A Revision Cloud will be placed either inside or outside the View Sheet surrounding just the area of the
drawing where changes were made. The revision triangle annotation with the Revision Number will be
placed right next to the Revision Cloud.

Figure 6-29 - Revision Cloud and Annotation

If a new revision is required to the same drawing, the revision cloud from the initial revision should be
hidden from the Sheet Issues/Revisions tool by adjusting the Show option, while retaining the revision
triangle annotation. The revised drawing will include clouds and triangle annotations for the new revision,
and the triangle from the previous revision.

6.6.3 SIGNATURE/SEALS/STAMPS
The Revision Schedule will include the Revision Number as well as the Date, the Description and the
Initials of the person that approved the changes. For the current revision, the initials must be provided as
an original signature. A default electronic signature color is acceptable for any software used to sign drawings
digitally.
If a new revision to the same sheet is required, the first revision initials should be added in the Sheet
Issues/Revisions using the Revit tool, while the initials for the new revision must be added as an original
signature.

Figure 6-30 - First revision example

NOTE:
Port Authority Design Division Drawings: Drawings issued during the bid period may either be signed or
may state “Original Signed by (O/S/B) <name of functional Chief>.
Consultant Drawings: Drawings issued during the bid period by Addenda must be signed and sealed in
the contract border by a Professional Engineer (PE) or by a Registered Architect (RA) licensed in the
state (s) in which the work is being performed.
2025 V.5 Last Updated: 03/01/2025
Page | 66
 Engineering BIM Standards

6.7 PACC MODELS

Designers should create a copy of the latest Design Model version before applying any PACC changes.
This saved version must be documented under Model Status in the PA-Admin-Dashboard as Addendum
Model_VXX. In case the model does not include addendum drawings from an earlier stage, the version
will be labeled as Design Model_VXX.

Figure 6-31 - PACC Model Status

After creating this copy, the PACC Model box must be marked in the live model to indicate that the
current version will contain PACC Drawings.
The process for adding new drawings and creating revisions within existing drawings is similar to the
creation of Addendum drawings, as explained in Section 6.6.1 Adding Drawings to Contract Drawings,
Section 6.6.2 Making Revisions in Contract Drawings, and Section 6.6.3 Signature/Seals/Stamps. The
PACC drawing description should follow the format PACC #XX. On a case-by-case basis, additional
descriptions may be added afterward to clarify the scope.

6.8 BIM COORDINATION MODEL - DESIGN

When project is done in-house, the VDC Engineer assigned to a project is responsible for setting up inter-
disciplinary clash detection testing and creating a BIM Coordination Clash Report one (1) month before
each, the 50% and 100% submissions during Stage III.
The inter-disciplinary clash detection will be performed by the project VDC Engineer using Autodesk
Navisworks. Each discipline’s Task Leader, including the Lead Discipline, is responsible for creating a
Navisworks file (.nwc) out of their Revit Models.
After testing the Coordination Model for clashes, the VDC Engineer has one (1) week to create the BIM
Coordination Clash Report and share it with the Project Principal.

NOTE:
For projects done by external consultants, it is expected for the assigned project BIM Manager to take
responsibility of the coordination process, host coordination meetings and incorporate coordination
processes in the BIM execution plan.

2025 V.5 Last Updated: 03/01/2025

Page | 67
 Engineering BIM Standards

6.8.1 INTER-DISCIPLINE COLOR SCHEME

The following color scheme is used to promote consistency and easy identification across all users when
coordinating the project and generating Clash Reports.
Table 6-9 - Color Scheme

DISCIPLINE COLOR
Architectural Cyan
Electrical Yellow
Electronics White
Corrosion Protection Orange
HVAC Green
Plumbing Magenta
Fire Protection Red
Vertical Circulation Pink
Structural Blue

NOTE:
Depending on the project needs further breakdown can be set either by level or by system. Contact the
VDC Support Group if you need to create new Color Schemes.

6.8.2 INTERFERENCE CHECK / CLASH DETECTION

The use of Clash Detection tools will have 3 possible outcomes within our BIM practice:
• No Clash: Absence of clash, this represents the perfect case scenario.
• Soft Clash: Alerts on an excessive proximity between two objects that could generate issues
during execution/installation or maintenance. During design this type of clash will not require any
additional action.
• e.g., Ducts going through Partition Walls.
• Hard Clash: Detects a physical collision between two model objects. This type of clash will
require action/work from the team.
e.g., Columns going through Equipment.

NOTE:
Clash Detection tool should be used during the design process to coordinate major building elements and
systems allowing the identification of interferences earlier in the process.

6.8.2.1 SINGLE-DISCIPLINE CLASH DETECTION

The Single-Discipline Clash Detection will be performed by each Discipline’s Leader using the
Interference Check tool within Revit or Clash Detective in Navisworks.

6.8.2.2 CROSS-DISCIPLINE CLASH DETECTION

The VDC Engineer is responsible for setting up Cross-Disciplinary Clash Detection sessions as often as
the project requires, usually defined in the BEP (BIM Execution Plan).

2025 V.5 Last Updated: 03/01/2025

Page | 68
 Engineering BIM Standards

During the Stage III, said frequency of the Cross-Disciplinary Clash Detection sessions shall be set to a
minimum of two (2). The first one, a month prior to the submission of the 50% progress of the project and
the second, a month before the 100% final submission of the stage.
The Cross-Discipline Clash Detection will be performed by the VDC Engineer using Autodesk
Navisworks.
Each Discipline Leader, including the Lead Discipline, is responsible for creating a Navisworks file out of
their Revit Models (.nwc).

6.8.3 NAVISWORKS CLASH REPORT

The VDC Engineer is responsible for compiling all the discipline specific Navisworks Cache files (.nwc)
into a single Master Navisworks file (.nwf).
The VDC Group has developed a Navisworks Template to be used as a base for coordination purposes.
Following every Clash Detection sessions, a Federated Model (.nwd) file shall be distributed to all
Discipline Leaders. The NWD file shall contain Saved Viewpoints of all clashes that are New or Existing.
Along with the NWD Federated Model and as a complement, The VDC Engineer shall create a Report
listing the clashes and issues that are analyzed during the sessions, indicating which course of action has
been agreed.
After the VDC Kick-off Meeting, the VDC Engineer will provide to the Contractor a 3D Coordination
Meeting Report template that will gather the following sections:
a. Introduction
b. List of Models Reviewed
c. Overview of Clash Report
d. Clash Detection Results

6.9 DESIGN DELIVERABLES

Electronic deliverables are required at the completion of every project. All submitted sheets must use
The Port Authority of NY & NJ Title Sheets and Contract Borders identified in this Manual.
All submitted electronic files must be compatible with the version of the Autodesk Revit software recently
being used by the Port Authority of NY & NJ and must conform and comply with the latest version of the
Port Authority of NY & NJ BIM Standard as outlined in this Manual.

6.9.1 ELECTRONIC DELIVERABLES

Electronic files are required for each milestone during Stages I, II and III. If the project does not have a
milestone scheduled prior to the 100% Submittal, files must be submitted no later than 2 weeks before
the submission for a BIM Wide Review.
The Port Authority of NY & NJ BIM Standard adopts the PDF format as the standard to be used when
creating sheets for plotting purposes. Plotting from the Revit-based application is accomplished by
exporting the sheets as a PDF file.
PDF files shall always be created as multi-sheet files, in full size (22x34 or 34x56), in black and white,
and grouped together by Drawing Type and by Series (if used).

2025 V.5 Last Updated: 03/01/2025

Page | 69
 Engineering BIM Standards

6.9.2 SUBMISSION PROCESS

All project-related files must be submitted in the MILESTONES folder inside the M Drive using the
following folder structure: MODEL, MODEL_3D, PLOTSHEETS and PUBLISH. Submission frequency
depends on project milestones, refer to Section 6.9.3 Submission Milestones to find this information.
Files from Consultants must be submitted on Livelink or E-Builder as indicated by Project Principal.
Depending on the project software used, the following formats are required on every submission:
• RVT: Autodesk Revit files
• NWD: Autodesk Navisworks Document files
• NWF: Autodesk Navisworks Federated files
• NWC: Autodesk Navisworks Cache files
• PDF: Adobe 2D Portable Document Format files

6.9.3 SUBMISSION MILESTONES

6.9.3.1 STAGE I_100 PERCENT
Stage I (Conceptual Design) is used to develop design concepts, confirm Facility scope, determine
anticipated construction costs and schedules and to compare alternatives before proceeding with Design
Development (Stage II) or Final Design (Stage III).
If and when drawings are developed, VDC will review those at the 100% submission. (MILESTONES >
Stage01 > 100percent). Refer to Section 8.0 BIM Compliance Review to know more about the process.

6.9.3.2 STAGE II_100 PERCENT

Stage II (Design Development) is used to develop the chosen design concept, further refine anticipated
construction costs and schedules before proceeding to final design (Stage III).
If and when drawings are developed, VDC will review those at the 100% submission. (MILESTONES >
Stage02 > 100percent). Refer to Section 8.0 BIM Compliance Review to know more about the process.

6.9.3.3 STAGE III_50 PERCENT

The Stage III_50 Percent (Progress of Final Design) effort includes preparation of contract documents that
will be used for construction. The procedures vary for alternate delivery methods such as Work Order
Contracts, Design/Bid/Build, Design/Build Contracts and Design/Build/Operate/Maintain Contracts.
Design files must be submitted at 50% of project completion. (MILESTONES > Stage03 > 50percent). Refer
to Section 8.0 BIM Compliance Review to know more about the process.

6.9.3.4 STAGE III_PA-WIDE (100%)

The Stage III (Final Design) effort includes preparation of contract documents that will be used for
construction. The procedures vary for alternate delivery methods such as Work Order Contracts,
Design/Bid/Build, Design/Build Contracts and Design/Build/Operate/Maintain Contracts.
PA Wide Review usually happens when the project is between 90% to 95% complete, this may vary
depending on the project specifics. When a project reaches PA-Wide Review, full-sized PDFs are required
to begin the Electronic Review Process.
During PA-Wide Review, Design files must be submitted at 100% of project completion. (MILESTONES >
Stage03 > PA-Wide). Refer to Section 8.0 BIM Compliance Review to know more about the process.

2025 V.5 Last Updated: 03/01/2025

Page | 70
 Engineering BIM Standards

6.9.3.5 STAGE III _AS-ADVERTISED-SIGNED-SET

The signed and sealed, updated based on PA-Wide 100% submission comments review, final submission
plotted on Permalife® paper is the “As Advertised Signed Set”. All original signatures shall be in blue ink.
Design files must be submitted to VDC in the appropriate Submission Milestones Folder for archival
purposes. (MILESTONES > Stage03 > As-Advertised-Signed-Set). The Project Principal is responsible for
notifying the VDC Engineer of the project about the submission via email.

6.9.3.6 STAGE III _ADDENDUM

The Addendum Set contains drawings that have been modified or new drawings that have been issued
after the original As Advertised Signed Set was signed, sealed, and issued for bid. Not all addenda
contain drawings; some may only contain specifications or other revised contract information pertinent to
bidders. Therefore, an Addendum Set may contain non-consecutive addenda sub-folders.
StageIII_Addendum folder should only contain the Addenda sub-folder in which drawings set and Revit
models were required. This folder should not contain the entire set of drawing files; it should only contain
the Addenda files.
Once all changes have been incorporated and addendum files have been issued, the Addendum Set
must be submitted to VDC for design archival proposes. (MILESTONES > Stage03 > Addendum). The
Project Principal is responsible for notifying the VDC Engineer of the project about the submission via
email.

6.9.3.7 STAGE III_AS-BID (CONFORMED SET)

The As-Bid Set incorporates all contract documents issued as addenda during the bid period and the As
Advertised drawings, specifications and contract book sections that have not been modified by Addenda.
The As-Bid set and its files must be submitted to VDC in the corresponding Submission Milestones Folder
for archival purposes. (MILESTONES > Stage03 > As-Bid). The Project Principal is responsible for notifying
the VDC Engineer of the project about the submission via email.

6.9.3.8 STAGE IV _PACC

The PACC Set (Post Award Contract Changes) contains As Bid drawings that have been modified or new
drawings that have been issued after the Contract was awarded.
The PACC Set must be submitted to VDC in the appropriate Submission Milestones Folder for archival
purposes. (MILESTONES > Stage04 > PACC). The Project Principal is responsible for notifying the VDC
Engineer of the project about the submission via email.

6.9.3.9 STAGE IV_RECORD DRAWINGS

The Drawing-of-Record Set is the set of drawings created after construction is completed.
In addition to any revisions required by the Project Principal, updated Design Models shall include all
approved (a) Shop Drawing changes as field verified by the Contractor, (b) revisions resulting from
responses to requests for information (RFIs) during performance of the Work, and (d) accurate geometry
and location for all constructed Work.
All Model submissions shall include a description of updates made to these models and all necessary
linked files to ensure a comprehensive, coordinated submission (including but not limited to *.rvt and
*.nwd files). Editable model geometry and data shall be submitted in native approved formats (e.g., *.rvt,
*.dwg) in addition to published formats (i.e., *.pdf, *.nwc, *.nwd, *.nwf).
All submission files should be delivered following the Standard Requirements; the Contract Border should
include the “Record Drawing” Stamp to indicate the drawings reflect the final conditions of each element
in the field.
2025 V.5 Last Updated: 03/01/2025
Page | 71
 Engineering BIM Standards

Files will be submitted for compliance review and must be approved to finalize the project closeout.
(MILESTONES > Stage04 > Drawing-of-Record). Refer to Section 8.0 BIM Compliance Review to know
more about the process.

7.0 CONSTRUCTION REQUIREMENTS

The current section describes requirements, processes and procedures currently demanded and in use
by The Port Authority of New York and New Jersey in relation to use of BIM in Stage IV Construction,
particularly for a traditional Design-Bid-Build project delivery method.

NOTE:
For Design Build projects, Design Requirements section should be considered as well.

7.1 GOALS AND USES

The main objective of this section is to provide the proper framework, so that all Stakeholders can deliver
and receive consistent information throughout the construction.
As an owner, the PANYNJ considers the Model as a tool to facilitate:
• Reutilization of information available from Stages I-III.
• Risk mitigation, by providing reliable information earlier in time (compared to a non-BIM
methodology)
• Reduction of errors during construction, improving project delivery on time, and within budget (for
example, by minimizing Change Orders and Coordination-driven delays and rework in the field).
• More efficient site planning and logistics.
• Improving project safety.
• Data recollection on relevant assets, for future Operation needs.

7.2 CONSTRUCTION SITE MODEL

The Site Model (SM) file is created and distributed by the VDC Group at the Project’s BIM Kick-off
meeting. This Site Model file has a combination of Aerial Photograph and CAD Files obtained from The
Port Authority of NY & NJ BMMS (Base Map Management System) and specific CAD file background
with coordinates provided by Central Survey Group. This file holds the project coordinate system and
controls the location, rotation, and elevation. All Discipline models must link the SM and acquire the
project coordinates from it. This model shall NOT be modified, will be provided for reference only.
Upon receipt of the base Site Model, the Contractor must perform an assessment to determine if there is
any information of particular importance that may require additional validation.

7.3 CONSTRUCTION CONTEXT MODEL

This section refers to the particularities of the Context Model, as a special case among all Models to be
developed by the BIM authors. The Context Model developed during Design might be used as a base to
be further developed during Construction.
The Context Model is a subcomponent of the Construction Model, so its required for the Context Model to
work in close relation to the schedule, in order to develop its full potential and provide real value. The
Context Model shall include the topography, site utilities, access and egress routes for materials, material
lay down, temporary work, etc.

2025 V.5 Last Updated: 03/01/2025

Page | 72
 Engineering BIM Standards

It is worth mentioning that due to the different project types within the PANYNJ portfolio, and their
potential locations, the Context Model requirements can greatly vary between projects.

7.3.1 CONSTRUCTION CONTEXT MODEL LIFECYCLE

The Contractor/BIM Leader is the owner and solely responsible for the development of the Context
Model. The Context Model shall be submitted for compliance review in each official submission as part of
the construction deliverables package.

Figure 7-1 - Construction Context Model creation workflow

7.3.2 GOALS AND USES

Specific goals pursued by the Context Model include:
• To support site planning and logistics.
• To improve project safety.
• To assist activities involving new underground utilities.
• To support program management, when applicable.

7.3.2.1 USES BY THE PANYNJ

• Contextual analysis: By showing site surroundings, the Model will better mirror the real-world
conditions, as no Construction project is impervious to the environment in which it transpires.
Access roads and logistic, impact on vehicle or pedestrian traffic, are some of the studies that can
be performed.
• Assisting on Program planning: By containing a unified coordinate system, a particular project
can be incorporated in a Program-level Construction Model, rather seamlessly. This allows to
analyze how different project interact with each other.
• Improving site safety: By incorporating geometry and schedule, some major hazards can be
simulated in time, and preventive or mitigation actions can also be defined for specific dates.
• Reference of existing underground utilities, when available: By incorporating existing site
utilities into the starting Context Model, as provided by the Authority.

2025 V.5 Last Updated: 03/01/2025

Page | 73
 Engineering BIM Standards

• Systematic Revision of 4D Site Plans: By incorporating project schedule, a more

comprehensive analysis on construction activities and their repercussions can be performed.
• Logistics Planning: The 4D Context Model is invaluable in planning logistics issues such as
access and egress routes for materials, traffic shutdowns, use of lay-down space, etc. This tool is
especially useful on tightly constrained project sites.

7.3.2.2 USES BY THE CONTRACTOR

For the Model to fulfil the uses envisioned by the Authority, it is the Contractor’s responsibility to develop
and maintain the Site Context Model. The Model shall comply with the general requirements made herein
and documented on the BEP.
Furthermore, the PANYNJ believes there are other potential uses that may provide value to the
Contractors and Subcontractors. In this spirit, the Authority encourages all parties to:
• Support and improve the efficiency of the site layout: From the visualization standpoint alone,
the Model may provide a different perspective to consider alternate possible layouts (location of
trailer, access to site and material lay down, etc.).
• Preliminary hazard detection and safety planning.
• Analysis of construction activities sequence: Either by a human operator or a computer-
based application, which may reveal new threats or opportunities, previously overlooked.
Unlike other Models (Discipline models) the Context Model will not typically undergo an LOD
transformation throughout the process, since it will mostly be elemental geometry acting as place holder
for temporary works.

7.3.3 REPRESENTED ELEMENTS AND ENTITIES

The following table includes elements to be represented by the Contractor on the Context Model.
Contractor is encouraged to include more representative geometry when available and also include any
other element that may be an additional part of the construction logistics and may affect the Project
development and its surroundings, such as pedestrian paths, traffic, city areas, etc.

Table 7-1 - Elements to be included in the Context Model

ELEMENT MODELING GUIDELINE WORKSET – COLOR

Modeled as a single element, of negligible
thickness and with an elevation equal to or Site – Layout; White,
Property line perimeter
higher than the top-most point of any Semitransparent
temporary or final work
Represented as simple prisms (overall Site – Layout; White,
Job Trailers
dimensions) Semitransparent
Material lay down areas Represented as simple prisms (overall Site – Logistics; Gray,
(non-hazardous) dimensions) Semitransparent
Modeled as a single element, of negligible
Site – Logistics; Gray,
Site access points thickness. May overlap with fencing and
Semitransparent
property line geometry.
Modeled as single or multiple elements of
Site – Layout; White,
Parking (temporary) arbitrary thickness. “Slab” tool is
Semitransparent
acceptable.
Modeled as single or multiple elements of
Site – Layout; White,
Fences arbitrary thickness. “Wall” tool is
Semitransparent
acceptable.

2025 V.5 Last Updated: 03/01/2025

Page | 74
 Engineering BIM Standards

ELEMENT MODELING GUIDELINE WORKSET – COLOR

Site – Equipment; Orange,
Geometry must suggest the type of Solid (equipment)
Cranes, hoists, and equipment when possible. Crane
Fixed Equipment envelopes, equipment clearance and other Site – Equipment; Red,
“no-fly” zones must be represented Semitransparent (envelopes
and “no-fly” zones)
Basic prismatic shapes showing overall Site – Construction Activity;
Excavation
dimensions. Red, Semitransparent
Basic prismatic shapes showing overall Site – Construction Activity;
Temporary Structures
dimensions. White, Semitransparent

7.3.4 MODELING REQUIREMENTS

Unlike discipline models, the Context Model shall not contain any final work and shall not be migrated to
the Agency’s Asset Management System. As a direct consequence, content requirements are fewer and
less strict.
However, the following practices are to be observed, at minimum:
• Contractor is always expected to follow PANYNJ BIM Standards during the development of the
Context Model.
• Revit Templates provided by the Authority will contain basic Worksets and custom materials as a
starting point. Contractor may create more at his own discretion, providing all color and Worksets
conventions as stated in the BEP.
• The LOD requirements for elements within the model will not be higher than a level of
development “LOD-200” as understood and interpreted by the BIM Forum’s LOD Specification
(Part I), version as stated in Section 5.4 Information Delivery Plan.
• No permanent work is to be included in the Context Model.
• The Model must remain a Revit native file, and its geometry must also be native to this software
(there may be some approved exceptions, like imported Civil 3D Pipe networks, that will be
treated on a case-by-case scenario).
• Use of the “Model in place” tool to create geometry, is accepted in the SC (unlike trade models).
• To avoid rework, consider the Project schedule requirements when creating content in the
Context Model, as some elements extent may be limited by some activity’s duration (e.g.: activity
duration limited to “x” days may determine how excavation geometry is modeled)

7.3.5 CONTEXT MODEL UPDATES

Contractor shall maintain the Context Model throughout the construction process by incorporating any
major change in geometry, logistics or site layout. Additionally, Contractor is also responsible for keeping
Model current in terms of Construction sequence.
Reporting: Contractor shall include a basic narrative on the BIM report, whenever there is a significant
change is made. There is no need to include a mention in the report when SC presents no modifications.

2025 V.5 Last Updated: 03/01/2025

Page | 75
 Engineering BIM Standards

7.4 CONSTRUCTION MODEL

The construction model contains all digital data relevant to the construction process. The construction
model is the source-of-truth for coordination purposes.
The Revit and Navisworks files will be monitored and updated as construction progresses. The
construction model will be composed of:
•
2D – Construction Plan Sheet Set (Design Build projects).
•
3D – RVTs, NWCs, NWD Federated Model, including the Site Model, Context Model,
Construction Models and Coordination Model.
• 4D – NWD including simulation of Construction Schedule.
• 7D – Assets data as defined in the Information Delivery Plan document (IDP)
Depending on context, the 3D “Construction Model” may refer to:
• A single composite Model, e.g., the Navisworks NWF/NWD files.
• Several Models, e.g., the aggregate of the Revit and Civil 3D native files; or
• A single trade model (e.g., the electrical Construction Model).

DISCLAIMER:
Design Models provided by the Authority (when available) to Contractors are for visual
information only. The Contractor/s shall use those as reference. Design Models may be used as a
starting point for trade Construction Models at the Contractor’s own risk. The PANYNJ may not be
held accountable for measurements, quantifications, coordination or any other activities and
assumptions made based on the Design Models. It is strongly suggested that, if the Contractor
decides to use them for the processes and deliverables described in this Standard, they are
thoroughly validated with all Contract information first (drawings, specifications, etc.).

7.4.1 CONSTRUCTION STATUS BREAKDOWN AND MILESTONES

Since the Construction Model is to correlate to the construction itself, different development status will
coexist in the same model. It is not possible to state that the Construction Model is at a singular stage of
construction and development.
To facilitate a common understanding of actual progress, the PANYNJ breaks down the CM under two
concepts: Construction Model Milestones and Areas of Interest (AOIs).
These can be considered as a Construction Model division in time. Model milestones will typically be the
same for every project and follow logical construction sequence. For that purpose, the Authority has
defined a parameter called “PA-CONSTRUCTIONSTATUS”, to track the construction status of each
element in the BIM model.
In general terms, milestones are defined as follows:
• Basis of Design (BOD): Models have been prepared as per Contract Documentation, including
any variation requested from or approved by the Authority (PACCs, returned RFIs, approved
Change requests). Regarding coordination, the location of elements is approximate, not final.
• Coordination Sign-off: Discipline models have reached the required LOD, and all elements are
in their final position. The CM is considered a “single source of truth” and used for coordination
purposes. As part of the sign-off process, all parties agree to install layouts as shown on the
model.
• As-Constructed (AC): Elements identified in the models have been updated as per field-verified
locations. Additionally, information relevant to the Enterprise Asset Management (EAM) System

2025 V.5 Last Updated: 03/01/2025

Page | 76
 Engineering BIM Standards

has been incorporated to each Discipline Revit models, as per required in the Information
Delivery Plan document ( “Project, Common, and Detailed” parameters).
Refer to the image below for a simplified flow chart showing the main Construction Model milestones,
their related processes and relevant information exclusively for spatial coordination.
For simplicity only one flow is shown. In practice, this will be repeated for each Area of Interest.

Figure 7-2 - Simplified Construction Models workflow

7.4.2 AREAS OF INTEREST (AOIS)

AOIs are the geographic/spatial division of the project into areas. These are defined by the Contractor
and stated in the BIM Execution Plan. Definition is typically influenced by the construction sequence, but
other factors may become relevant as well. As a general rule, defined AOIs must include all disciplines
occupying that space.
Examples of AOIs are entire Construction Zones, complete or partial Floors, Mechanical rooms,
Generator/Electrical Rooms, Risers, Restrooms, single rooms of particular importance, etc.

7.4.2.1 DEFINING AOIS

As mentioned before, the Contractor shall propose in the BEP the areas that the Construction Model will
be broken into. AOIs are subject to approval by the Authority.
A few aspects to consider for this purpose:
• Each AOI will be considered by the Authority as a BIM partial deliverable. Reporting from the
Contractor will be AOI based. (Refer to Appendix C: BIM Progress Report Template).
• Naturally, the sum of the AOIs needs to contain the full scope of the Work.
• AOIs will go through each Model Milestones independently.
• There is no limitation of how big or small a AOI needs to be in terms of square footage.
• There is no minimum or maximum amount of AOIs that a project needs to have.
• It is often helpful to think “backwards in time”. For example, to identify zones that will need shop
drawings first, so in-depth BIM coordination can begin sooner on said areas.

NOTE:
The Authority may request at its sole discretion that all AOIs are submitted for the BOD milestone at the
same time. This may be the case for relatively small and simple projects like parking garages, simple
concrete bridges, small Ad-Hoc buildings, etc.

2025 V.5 Last Updated: 03/01/2025

Page | 77
 Engineering BIM Standards

7.4.2.2 RELATION BETWEEN MILESTONES, AOIS AND IDP

The Information Delivery Plan (IDP) is closely related to the Construction Milestones, since it defines the
LOD that is expected for each one of them (See Model Element Table > Stage IV column). As mentioned
before, each of the AOIs will typically go through the Milestone sequence independently and will be
considered as a partial delivery of the whole.
NOTE:
The LOD stated for each category on each column, is the minimum accepted for that milestone. The
Contractor may at his sole discretion, chose to model beyond the requested LOD.
Strictly speaking, LOD definition includes coordination status, as it often refers to location of elements.
For example, it is not correct to describe a pipe segment as LOD350 if it has outstanding interferences
related to it, because it is likely that the element is not on its final position.

7.5 BIM COORDINATION MODEL - CONSTRUCTION

7.5.1 BIM COORDINATION PROCESS

The Authority will only take a monitoring approach on BIM spatial coordination aspects. It is up to the
Contractor to define the best approach for each specific project. The specifics of the Contractor’s
coordination process will be defined in the BIM execution plan. However, there are some guidelines that
the Contractor and Subcontractors must adhere to, specifically:
• Proposed spatial coordination process cannot contradict this standard unless approved on writing
by the Authority. That includes the roles and responsibilities as defined in the requirements.
• It is the Contractor’s responsibility to ensure all parties remain collaborative and diligent
throughout the coordination process.
• Situations identified as conflict or potential issues must always have: Responsible Party, Specific
Action Item, and a Due Date.
• Areas of Interest must always be signed-off prior to any installation to occur. Refer to Section
7.5.3 BIM Coordination Sign-Off for sign-off procedures and documentation.

7.5.1.1 POTENTIAL SCENARIOS AND BASIC WORKFLOWS

Depending on the project specific requirements and the different Subcontractors BIM capabilities and
maturity, many different processes may be possible. For practical purposes, this standard defines two
main scenarios based on traditional coordination practices, since most of the remaining possibilities can
be considered as a combination of the two.

SCENARIO A: CONTRACTOR CONCENTRATE ALL MODELING EFFORTS ON A SINGLE PARTY

In this case, all Construction Model updates are responsibility of the Contractor either directly, or via a
third-party consultant (BIM Subcontractor). Subcontractors are still to participate on coordination meetings
and are responsible for validating the model and provide feedback based on their expertise to help
ensure that Coordination Sign-off Model is in fact, constructible and efficient. Contractor is to agree on a
model validation workflow with each sub (model sharing, joint review, etc.).

2025 V.5 Last Updated: 03/01/2025

Page | 78
 Engineering BIM Standards

Figure 7-3 - BIM Coordination Scenario A

SCENARIO B: EACH SUBCONTRACTOR IS IN CHARGE OF EACH DISCIPLINE MODEL AUTHORING

The Contractor’s BIM Manager Coordinators act as liaison between Subcontractors BIM Coordinators
and communicate action items to each Sub’s model authoring team. Individual discipline models are
shared by means defined and provided by the Contractor, at intervals defined by the BEP. Subcontractors
typically define their internal process for Model validation and trade best practices.

Figure 7-4 - BIM Coordination Scenario B

2025 V.5 Last Updated: 03/01/2025

Page | 79
 Engineering BIM Standards

7.5.2 BIM COORDINATION MEETINGS

This Standard uses the concept of Coordination Meeting in the broader sense, not referring only to the
spatial coordination aspects, but also to any meeting where Contractor and Subcontractors gather to
discuss on model status and agree on specific action items. For example, if one of the Subcontractors’
Model is not meeting the IDP requirements, a meeting between the BIM Manager and the Sub’s BIM
Coordinator to review, discus and agree on corrective actions, is considered a Coordination Meeting.
As mentioned before, it is the Contractor’s responsibility to define the appropriate methodology for this
type of meetings. Frequency, attendees, typical meeting agenda and action items tracking mechanism,
among other topics, must all be recorded in the BEP and submitted to the Authority for review and
comment.
However, there are certain requirements that provide a framework for the process to guarantee the
outcome is the one desired by the PANYNJ. Specifically:
• Meetings need to occur frequently enough to ensure Coordination sign-off dates for each AOI, as
stated in the BEP, are met.
• At meeting conclusion, every issue addressed must have a specific action item, a responsible
party, and a due date. Contractor must track these items, and be able to provide evidence to the
Authority, if it so requires it.
• If a Subcontractor is not the direct author of the Discipline Model, the Contractor must define a
Model validation mechanism. For example, by hosting one-to-one (Contractor + Single Sub) or
one-to-many (Contractor + All Subs) model joint review sessions. Means and methods for Model
validation shall be stated in the BEP.
• The VDC Engineer representative/s may be required to attend these meetings, as an observer
only.
• Other requirements may be defined in the BIM Kick-off Meeting, for specific projects.

7.5.3 BIM COORDINATION SIGN-OFF

Once a Model achieves this condition (for a particular Area of interest), it becomes the single source of
truth for spatial coordination. This is relevant because if any conflict arises during construction or
installation, the sign-off Model will be the first stop to open a discussion and determine the reasons, and
the responsible party, behind the problem.

7.5.3.1 CONDITIONS FOR SIGN-OFF ELIGIBILITY

Essentially, two requirements must be met:
• Geometry must meet the LOD requirements stated in the IDP; the intended location of the
modeled elements may be affected by changes in geometry, connection points of equipment, etc.
• Acceptable interference resolution: a “clash-free” model, though desired, may not always be
possible or practical to pursue. Model may have open items at the time of sign off, under the
condition that they all have a responsible party assigned that acknowledges them in the sign-off
documentation provided to the Authority. The PANYNJ may still reject the claim for sign-off status
if the open items reported are considered of relevance and action items are not satisfactory.
Examples of clashes approvable by the Contractor or Subcontractors:
• Slight insulation clashes (requires trade specialist/Subcontractor to approve).
• MEP interferences with basic walls, where penetrations are not necessarily modeled.
• Intentional MEP interferences with floating ceiling, such as sprinklers, lighting fixtures, electrical
devices, etc.

2025 V.5 Last Updated: 03/01/2025

Page | 80
 Engineering BIM Standards

Example of clashes that may require additional approval by the PANYNJ:

• Any interference that is left to be resolved in the field.
• Interference with access zones or clearances, where this may difficult operation and maintenance
of equipment.
Other as ruled by the Resident Engineer.

7.5.3.2 PROCESS AND RECORD

Regardless of the final methodology and process followed for spatial coordination, it is mandatory that all
participants (Contractor and Subcontractors) formally sign-off on a coordinated Model prior to any
installation.
The actual wording of the document may be rewritten to fit the necessities of each project, on the
condition that the language includes the following:
• Statement of conformity regarding coordination status.
• Acknowledgement of any outstanding open items (if any), their recommended actions and their
potential implications. These items must be listed, each with their responsible party and expected
action.
• Expressed commitment to perform any construction and installation works as close to the signed
off Model as possible, and to immediately report any field deviations that may impact future
works, specially to other trades.

7.5.4 SPECIFIC REQUIREMENTS

It is the Contractor’s responsibility to append all trade models to an NWF file and develop it to the project
specific needs so they remain compliant with this standard.
Project specific NWF settings, folder structure, search sets, etc., shall be stated in the BEP. The process
of obtaining an efficient Federated Model setting may imply some trial-and-error, and more so on the
earliest stages of a project. The BEP template may contain a specific Appendix for this purpose.
The following requirements are mandatory solely for the Federated Models as submitted to the Authority.
Contractor and Subcontractors are free to manage internal files as per each Company’s standard or
common practice, unless ruled otherwise by the Contractor in the BEP.
Having multiple active NWF files with repeated information may result in miscommunication between
stakeholders.
Regardless of the process that the Contractors decides to follow, the only official Models are those
submitted to the Authority by the formal channels.

No claims or justification of work based on other Models than the ones

officially submitted to the PANYNJ will be accepted. This is particularly
important for work based on shop drawings developed from other models
that the ones submitted to the Authority.

2025 V.5 Last Updated: 03/01/2025

Page | 81
 Engineering BIM Standards

7.5.4.1 GROUPING CLASHES

The BIM Manager shall determine how to group clashes to better reflect the status at any given time. For
internal reports (e.g., to Contractor or Subcontractors), this may be done with whatever criteria the BIM
Manager sees fit. However, when reporting to the PANYNJ the following shall be considered:
• As the first general criteria, coordination should move in a direction that allows for groups to be
assigned specific action items from specific parties.
• This practice may not be entirely possible at the very early stages but should always be pursued.
• “Contractor XXX to submit RFI”, “Subs YYY and ZZZ to work on a solution”, “Sub AAA to move 6”
south”; are all examples of specific actions from specific people. Aversely, “All trades to improve
coordination in this area” is an example of a poor directive and group assignment.
• Grouping criteria may change during the coordination process, but always from larger to smaller
areas, and from higher to lower quantity of elements involved.
• For example: whilst it is acceptable to group all Fire range pipe clashes for an AOI into a single
clash while the Model is being populated, it will not be acceptable once the Fire Main has been
coordinated with the other trades and is likely on its final position. Following the example, group
may contain hundreds of individual clashes at first, but will have to eventually be broken down
into smaller groups.
• If the same action will solve multiple individual clashes, these may be grouped as a single
situation, regardless of the area span of clashes.
• For example: moving a pipe main and reconnecting branches, accordingly, will solve multiple
clashes across the entire AOI. These may all be under a single group until said change is made.
Then smaller groups will have to be created for the remaining situations.
• “False” clashes may be grouped as a single situation, within reason.

7.5.4.2 TECHNICAL REQUIREMENTS

All Federated Models submitted to the Authority must comply with the following minimum requirements to
be approved. All these requirements are necessary and vital for a correct and complete analysis of the
current BIM process performed by the contractor.
Technical Requirement list includes:
• File Name (All files must be named as per Standard, Revit files, Navisworks files, Cache files)
• Project Coordinates (Federated Model must follow Site Coordinates)
• Site context (Context Model must be included on Federated Model showing all project Context)
• Appended files (All Disciplines Models must be included on the Federated Model as NWC Files)
• Search Sets (Search Sets must be Created for all BIM Activities and All Construction Milestones)
• Color Scheme (Disciplines must be Colored as defined on Section 7.5.4.5 Color Scheme)
• Rooms (No Rooms Geometries must be included on Federated Model)
• 2D Elements (No 2D elements must be included on Federated Model)
• Clash Tests and Results (Clash Tests Must Be Correctly Setup, and Results managed properly
as per Standard requirements)
• Construction Status Parameter (All items must contain a Parameter that Reflects the Current
Construction Milestone achieved for that item BOD, AS, AC)
• Viewpoints (Viewpoints must be included to directly show, all AOI, all Open issues, All RFIs, all
closed issues, all Conflictive Areas, A comprehensive folder Structure must be created and used
for Viewpoints management)

2025 V.5 Last Updated: 03/01/2025

Page | 82
 Engineering BIM Standards

7.5.4.3 REFERENCE VIEWPOINTS

The NWF provided by the Authority will have starter viewpoints, that will need to be reoriented and
updated once the NWCs are added. This process shall have a consistent outcome throughout all
Federated Models created by the Contractor.
Additional requirements as follows:
• Element Color, Hide/Isolate attributes and Sectioning configuration must be saved as a property
of the Viewpoint. Regardless of the visibility or scope that it is being used, they should always
reset when selecting the Viewpoint.
• For ease of navigation and quick reference, each Federated Models shall have at minimum:
• Viewpoint of the entire project (or AOIs contained in that Federated Model), from a convenient
top-side view
• Isometric side and front views
• Viewpoints other than the ones referred to above, shall be saved in an appropriate folder,
containing issues of similar nature.
• Federated models must be purged of redundant or useless viewpoints prior to submission to the
PANYNJ.

7.5.4.4 SEARCH SETS

Because of the monitoring activities that the Authority will perform over the modes, as an owner, it is of
paramount importance that Sets are created and maintained throughout the lifespan of the Construction
Model. This will allow any questioning to the Model to be made in a relatively seamless and consistent
fashion.
Search Sets are, for most uses, preferred over Selection Sets. This is due to the ability of the former to
remain always current without human action. BIM Coordinator shall whenever possible, follow this
general rule for locating elements in the model.
NWF Template as provided by the Authority, will contain basic predefined Search Sets in a proposed
folder Structure. BIM Coordinator will define the Sets as appropriate for the project, and state them in the
corresponding BEP Annex.

7.5.4.5 COLOR SCHEME

The following color scheme is used to promote consistency and easy identification across all users when
generating Clash Reports.

DISCIPLINE COLOR
Architectural Cyan
Electrical Yellow
Electronics White
Corrosion Protection Orange
HVAC Green
Plumbing Magenta
Fire Protection Red
Vertical Circulation Pink
Structural Blue

2025 V.5 Last Updated: 03/01/2025

Page | 83
 Engineering BIM Standards

NOTE:
Depending on the project needs further breakdown can be set either by level or by system. Contact the
VDC Group if you need to create new Color Scheme.

7.5.4.6 APPEARANCE PROFILER

Different uses of the Federated Model may require different visibility settings. For instance, visualization
of construction status (Basis of Design, As per Shop Drawings, As Constructed) implies different grouping
and coloring than the one used to identify trades.
For consistency across the project, and to be able to quickly switch from one visualization configuration to
the next, Appearance Profilers should work in close tandem with Search Sets (Selection Sets are not
recommended).
The BIM Coordinator may choose to categorize or represent elements differently than the Authority’s
standard coloring, for many numbers of reasons (e.g., for identifying different Piping systems, or a
subdivision in trades like Mechanical dry and wet systems, etc.).
Contractor is welcomed to create and maintain different profilers as deemed appropriate, as long as they
are:
• Detailed in the BEP, with sets and coloring scheme in use, and intended purpose.
• Consistent throughout the different Federated Models submitted to the Authority, if more than
one.

7.5.4.7 RFI TRACKING

The Contractor shall keep viewpoints to visually support any Request for Information to the Authority,
whenever possible.

Figure 7-5 - RFI Folder structure

For new RFIs, the BIM Manager shall proceed as follows:

1. Create a new folder with the following naming convention, in the “Open” directory:

*RFI Number*-*Location and Room number if available*-*Brief Description of the issue*

For Example: 061-1st Floor NW Corridor 103-Insufficient overhead space
2. Create one or many Viewpoints, as needed to fully describe the situation.

3. Log Comments using the same viewpoint, to record any novelties regarding this situation.
Particularly, when specific action items are assigned and when the issue is closed.

2025 V.5 Last Updated: 03/01/2025

Page | 84
 Engineering BIM Standards

Figure 7-6 - Sample RFI Comment log

4. Once RFI is closed, move to the Closed folder.

7.6 4D SIMULATION MODEL

A four-dimensional Model is commonly accepted and referred to in the industry as the integration
between three-dimensional geometry (length-width-depth) and the dimension of time, represented in most
cases by the project schedule.
Construction schedule is one of the most important aspects to be considered when coordinating
interdisciplinary work as well as phasing where portions of a facility undergoing remodeling must be kept
operational, since it defines what work needs to be done, where, when and by whom. If schedule is cost
loaded, the potential for analysis is even greater (e.g., facilitates Earned Value analysis or Cash-Flow)
For the PANYNJ as an owner, it allows to monitor one of the most important aspects for construction: that
the project will meet its intended completion date. For this specific reason, 4D Model becomes one of the
most important BIM deliverables from the Contractor to the Authority.

4D is considered by the PANYNJ as a visualization tool. It is meant to

complement, not replace, any of the Schedule obligations the
Contractor has with the Authority. In the same sense, BIM
requirements made herein are secondary to those made in terms of
Scheduling. If there is any contradiction, the latter shall prevail.

7.6.1 GOALS AND USES

There are many scheduling software and methodologies that have the potential to obtain a 4D simulation.
The main objective of this standard on this regard, is to provide the minimum requirements the Contractor
must meet, as well as to suggest a set of guidelines for the approved software in use by PA to produce
other BIM deliverables.
In this spirit, Contractor may propose an alternative workflow and software on the project’s BEP, as long
as it allows for the Authority to benefit from the uses of the 4D Model. These alternates shall be subject to
approval of the Authority, as part of the BEP original submission. Contractor shall also validate with the
PANYNJ the 4D simulation software to use at the BIM Kick-off meeting.
The PANYNJ will use the Schedule simulation or 4D Model for the following:
• Visualization of Baseline Schedule
• Visualization of all Progress Schedule updates
• Simulation of each Progress Schedule update versus original Baseline Schedule
• Visualization of other site activities, involving elements other than finished or installed work
• Site logistics Model Requirements
• Basic cost analysis

2025 V.5 Last Updated: 03/01/2025

Page | 85
 Engineering BIM Standards

7.6.2 4D MODEL REQUIREMENTS

The following properties are required in the Construction Model as stated in the Information Delivery Plan:
• Construction Status: represented by three YES/NO parameters which will indicate in general
terms the level of definition for a particular element.
o Basis of Design (BOD): Object or element has been dimensioned based on Contract
documentation (Drawings, specifications, etc.), best modeling practices, and meets the
LOD and data as specified in the project specific IDP corresponding to the Basis of
Design milestone.
o As per Shop Drawing: Element geometry has been upgraded based on Manufacturer
content, drawings, cut-sheets, etc., and meets the LOD and data as specified in the
project specific IDP corresponding to the Coordination Sign-Off column of the Model
Element Table.
o As Constructed: Element location and orientation has been field verified and adjusted in
the model to a level of accuracy in accordance with the LOA2 column on the IDP. Refer
to Section 7.8.3 "Level of Accuracy" for clarification on LOA values.
• Activity ID: Every element in the models is to relate to a Construction activity. The value of this
parameter, for each element, shall match the unique identifier for the associated activity, as
defined by the project’s Work Breakdown Structure (WBS) and stated in the approved baseline
schedule.
Modeling practices: In addition to complying with the appropriate LOD for every milestone or stage, it is
critical that modeling efforts are carried out considering the 4D simulation application, in particular
regarding model granularity. This is important so components can be properly associated to
tasks/activities without creating logic violations or misrepresentations in the construction sequence.

7.6.2.1 SCHEDULE SETUP

Whilst it is not the purpose of this section to rule on any aspects of the Construction Schedule
development, it is worth mentioning that due to the close relation with the 4D Model and simulation, some
level of collaboration and coordination will most certainly be necessary between these seemingly
separate efforts.
As an example, there is a known limitation that occurs in Navisworks when multiple activities in the
Schedule relate to the same geometry. To better reflect the construction sequence, some “grouping” of
activities may be necessary in the scheduling Software. This, however, should not affect the duration,
logic, sequence, and overall structure of said schedule. Before modifying the schedule in any way,
Contractor shall confirm with PANYNJ this will not cause violations or non-compliances in future Schedule
submissions.

7.6.2.2 4D ANIMATION
With every 4D Model submission, Contractor shall provide a video file showing an animated simulation of
the Construction sequence. Video shall be exported from the software used to prepare the simulation,
and its minimum requirements are as follow:
• When the purpose of the submission is to show Baseline vs Progress schedule comparison, both
sequences shall be shown running in parallel in the same video file, either side to side or top to
bottom, in such way that they both appear to run in the same timeline.
• When the main purpose of the video is to allow for visually appreciation of every element start
and end dates, both planned and actual. Contractor shall take every precaution to facilitate this,
which may include rotating, sectioning, changing camera position, etc. Temporarily hiding finished

2025 V.5 Last Updated: 03/01/2025

Page | 86
 Engineering BIM Standards

elements or making them more transparent for visibility purposes (e.g., finished walls or slabs
concealing work in the interior) are acceptable.
• Text wise, animation/s shall display, at minimum:
o Dynamic timeline (dates in MM/DD/YYYY format preferable).
o Active tasks (progress between 1% and 99%).
o Percentages of completion for active tasks.
o Percentage of completion for project.
• Length of the video shall be such that allows for analysis of dates and overall sequence. 60
seconds per year of project is typically an acceptable first approximation.
• Video format/file extension shall be agreed on the BIM kick-off meeting.

7.6.3 4D MODEL ASSEMBLY

Since Autodesk Navisworks is the PANYNJ default software for spatial coordination and other BIM
related requirements, and considering this platform contains a built-in construction sequence simulator
(referred to as TimeLiner), a workflow is presented as a proof of concept.
The process detailed is only of suggestive nature, and the Contractor may propose a different approach.
The final methodology for geometry and Schedule integration shall be recorded on the BEP and
submitted for approval of the PANYNJ.

7.6.3.1 NATIVE MODELS PREPARATION

Every discipline Model as well as the Context Model needs first to incorporate the Activity ID parameter
as described. Parameter values should be an exact match with the Activity code value representing the
task ID.
Every model will also be exported as a single separate *.nwc (Navisworks Cache) file.
Each exported file should comply with the following:
• Only 3D elements should be exported.
• All the parameters are carried over from the native to the cache file.
• No linked files should be exported.
• NWC file name should follow Revit file naming convention.

7.6.3.2 FEDERATED MODEL ASSEMBLY

The Navisworks File set needs to be generated using the Navisworks template provided by the Authority.
This file will contain the base appearance profiler and basic set ups.
All NWC files need to be appended directly from its correct location on the folder structure to maintain a
correct path with the NWC file.

7.6.3.3 PRIMAVERA P6 INCORPORATION

Primavera P6 schedule information can be incorporated in many ways to the federated model.
Methodology for using Comma Separated Value file (*.csv) is explained herein:
• From Primavera P6, export columns containing the following information to an Excel spreadsheet:
o Activity ID
o Task name
o Task Type
o Start Date (Baseline)
o End Date (Baseline)
o Start Date (Progress Schedule)

2025 V.5 Last Updated: 03/01/2025

Page | 87
 Engineering BIM Standards

o End Date (Progress Schedule)

• Actual column names may differ depending on personal or corporate scheduling practices from
the Contractor.
• In Navisworks, set up task types in the TimeLiner Configure tab. Some types are included in the
PANYNJ template, but alterations may be in order to match Primavera Task types or project
specific needs.
• From the Data Source tab, import the *.cvs file obtained from P6 and manually map the Column
fields (Navisworks) to External Field Name (*.csv file) as needed.

7.6.3.4 TASKS AND GEOMETRY LINK

To enable a 4D Simulation, a link must exist between tasks or Activities on the schedule and the
geometric elements on each trade and Context Model. The following steps explain one possible
methodology to achieve this:
• Create a series of Search-Sets that enables the selection of the elements using the incorporated
Activity ID parameter value for each element (some commercial and free add-ons allow for
automated Search Set creation).
• From the Task tab, use the Auto-attach Using Rules feature, creating a custom rule to map the
Time-Liner Tasks Name to Search sets with the same name. The Activity ID parameter should
act as the nexus between platforms.
• The Find Items feature in the TimeLiner Tasks tab should be used for checking, amongst other
things, that no model element has failed to associate to a task (Unattached/Uncontained items).

7.7 AS-CONSTRUCTED MODEL

The As-Constructed Model is considered as the final version of the Construction Model, as submitted to
the Authority for final approval as part of the project handover. The As-Constructed model is meant to
represent the final as-built conditions and with that it should have the required LOD, be also validated with
Laser Scanning and contain the correspondent Asset Data incorporated on each modeled element.

7.7.1 GOALS AND USES

As-Constructed model is considered of the utmost importance for the PANYNJ as an owner and operator
of its facilities. It is meant to provide reliable and accurate information of the finished Work.
As-Constructed Model will be used for:
• As design reference for future expansions and/or renovations made to the facility.
• Provide Asset information for the Authority to export to the Facility Management software in use.

7.7.2 REAL WORLD REPRESENTATION

This manual considers two types of actual or “real-world” conditions:
• Existing conditions: they are considered as the aggregate of all material objects or element that
Contractor must work with and around of, to execute the Work. Existing conditions may or may
not remain at the end of the project (e.g., due to Demolition or decommissioning activities).
Requirements for modeling of existing conditions are defined in the Project Model Development
Spec.
• As-Constructed conditions: final condition of all completed Work. Unless specified differently in
the Contract, this refers to final Work only (no temporary). Requirements for the As-Constructed
Model(s) are defined in the IDP.

2025 V.5 Last Updated: 03/01/2025

Page | 88
 Engineering BIM Standards

7.7.3 ASSET DATA REQUIREMENTS

The Authority recognizes two primary types of information:
1. Geometrical: Relates to the size, shape, quantity, location, and orientation of elements.
2. Assets: Involves specific data related to elements of interest, typically including (but not limited to)
equipment details such as manufacturer, model, and make. Asset information must be
incorporated into the Construction Model as it becomes available and will be reviewed by the
Authority throughout the project. The Contractor is required to use the IDP to identify the Asset-
specific Revit Categories—the list of categories that require asset data in the BIM models—and
populate the following parameters:
• PA-ASSETFLAG: A Yes/No instance parameter used to identify assets within the 3D model.
This parameter must be flagged once the assets list is defined.
• PA-ADSCODE: A code created by combining the Hierarchy Code, Subsystem Code, Asset
Code, and Child Asset Code, as detailed in the ADS Structure sheet.
• PA-ASSETTAG: A unique 16-digit identifier assigned to each specific asset in the model. This
number, which may also be represented as a QR code, is linked to the asset's data and will be
physically represented by an "asset tag" attached to the corresponding element during
installation. Once the asset is delivered and on-site, the asset's 16-digit identifier must be entered
into the Asset Tag parameter within the BIM model.

2025 V.5 Last Updated: 03/01/2025

Page | 89
 Engineering BIM Standards

7.8 REALITY CAPTURE

Reality Capture is the used term to describe the process of scanning a build, natural environment, asset
or object at a point in time using images or laser scanning devices. The output from the scanning process
is the creation of a digital 3D representations of the target, commonly referred to in the industry as “Point
Clouds”.

As part of the contractual requirements, Contractors must typically provide a record of the final
installed/constructed conditions to the Authority. Additionally, depending on the project, there may be a
requirement to capture and record Existing Conditions as well as part of the work. The Contractor may
also choose to capture and record any temporary work.

2025 V.5 Last Updated: 03/01/2025

Page | 90
 Engineering BIM Standards

Figure 7-7 - Laser Scanning Workflow

7.8.1 LASER SCANNING

Laser Scanning, sometimes referred to as LiDAR (Light Detection and Raging), is a surveying method
that measures distance to a target by illuminating the target with pulsed laser light and measuring the
reflected pulses with a sensor. Differences in laser return times and wavelengths can then be used to
make digital 3D representations of the target, commonly referred to in the industry as “Point Clouds”.

The purpose of this section is to describe BIM requirements and workflows using this technology.
For specific Laser Scanning guidelines and information refer, to the Laser Scanning Standard.

7.8.2 GOALS AND USES

The Authority encourages the use of Laser Scanning technologies even if not required by Contract. The
Contractor may use this for the following:
• Adjust the Construction Model geometry to the surveyed information.
• Keep record of Construction progress and Site conditions.
• As record for otherwise hidden items in walls, floors, and ceilings.
• Record the final As-Constructed conditions.

7.8.3 LEVEL OF ACCURACY (LOA)

The PANYNJ adopts the LOA specifications as stated in the latest U.S. Institute of Building
Documentation (USIBD) LOA Specification, as publicly available on https://usibd.org.
Extending on this specification, this manual further defines the following two different types of LOAs:
• LOA1: referring to how accurately an element’s geometric information has been captured.
• LOA2: referring to how accurately an element’s geometric features has been represented in the
model.
LOA values, when applicable, are recorded in the IDP for each Uniformat line item. LOA values shall only
refer to intended dimensions, unless specified otherwise.

2025 V.5 Last Updated: 03/01/2025

Page | 91
 Engineering BIM Standards

7.8.4 LASER SCANNING REQUIREMENTS

Contractor must define and explain what the process, frequency and technology will be implemented for
the project to comply with the contractual requirements, such definitions and descriptions should be
incorporated in the BIM Execution Plan and submitted for review and approval.
The Contractor should typically work in the following sequence:
• Planning Requirements
• Data Capture
• Data Registration
• Data Control and Assurance
• Data Delivery and Handover

7.8.4.1 PLANNING REQUIREMENTS

Related to geometrical information: The Contractor shall deliver to the Authority an “Existing” and “As-
Constructed" Conditions Survey Plan. This document will cover the following items, at minimum:

• Detailed plan of subdivision of survey Areas and identification of all elements to be surveyed at
any given stage.
• Detailed list of position and coordinates of Control Point and control lines to be used as reference
on the survey Process.
• Detailed Schedule on survey activities and correlation with Construction schedule. Schedule must
include dates on which Point Clouds (or approved equivalent) will be submitted to the Authority.
• Proposed equipment to execute the work, considering it needs to comply with LOA project
requirements.
• Description of the process that will be utilized to incorporate surveyed information to the model,
as well as the control methods to be implemented to guarantee that the final model complies with
the project LOA requirements.
These Survey Plans shall be submitted to the Authority for review and comment. Once approved, they
shall be incorporated as an Annex to the BEP.

7.8.4.2 DATA CAPTURE

Geometric information: In order to achieve the required LOA, the Contractor must use specific
equipment to guarantee quality and accuracy is met. It is necessary to follow the detailed plan in order to
ensure that all necessary information is captured during the Laser Scanning process.

• Considering the Authority’s requirements for LOA values, it is likely that the only methodologies
that can meet them are the ones using some form of Laser Scanner (LiDAR) survey, often in
combination with Total Station (TST) survey. For this reason, this Standard refers to these types
of equipment and known associated processes (Point cloud generation, incorporation to models,
etc.).
• Only when LiDAR is not specifically required by contract, the Contractor may propose alternate
ways of obtaining the required accuracy. Contractor shall in this case, submit the proposed
equipment and methodology as part of the Existing and As-Constructed Conditions Survey Plan,
and include proof that LOA requirements can be met. Evidence may consist of Manufacturer
information, calibration certificates, white papers from or endorsed by a recognized entity, etc.

2025 V.5 Last Updated: 03/01/2025

Page | 92
 Engineering BIM Standards

7.8.4.3 DATA CONTROL AND ASSURANCE

As part of the review process, the VDC Engineer assigned to the project will audit and provide comments
for every Point Cloud delivered as part of the submission process.

7.8.4.4 DATA DELIVERY AND HANDOVER

Final deliverables must be provided by the constructor following the Laser Scanning milestones
established within the project BIM contract.
Refer to Section 2.8 of the Laser Scanning Standards to see the required deliverables.
Depending on the survey method used, the Contractor should provide one of the following:

If Total Station (TST) is used:

• The contractor must provide a table showing the following information for every surveyed point:
o Point identification number.
o X, Y, Z coordinates.
o Identification Comment.
• Floor Plan drawing showing the schematic position of the surveyed points, for ease of
identification.
If LiDAR equipment is used:
• Unified RCS Point Cloud files with shared coordinates system.
• Structure RCP Point Cloud files with shared coordinates system.
• LGS files with shared coordinates system
• A table like the one described for TST survey, but for control Points used to reference the Point
Cloud to the project coordinate system.

7.9 CONSTRUCTION DELIVERABLES

This section contains a description of the main deliverables expected from the Contractor.

7.9.1 CONTEXT MODEL SUBMISSION

Digital 3D representation of the work containing information regarding Construction activities other than
the finished and final work (e.g., Fencing, Traffic Control where applicable, excavation works, Job trailer
location, crane positions, etc.). Definitions and requirements are separated for practical and applicability
purposes, but this model may or may not be integrated with the Construction Model.

7.9.1.1 FIRST SUBMISSION

The Contractor must submit the Model for comment at a date to be defined during the BIM Kick-Off
meeting. Given the low complexity of the Model and the benefits it can provide on the early stages of
construction; an early submission will be required by the PANYNJ (i.e., before the Discipline Models).

7.9.1.2 MONTHLY UPDATES

The Contractor will submit the Context Model with every regular Construction Model submission as stated
on the BEP. Regardless of the CM being submitted “For Record Only”, the VDC group reserves the right
to request a submission for approval, if the Contractor fails to observe basic model quality and BIM
management good practices (e.g., naming convention, size of families imported to the model, appropriate
model categories, etc.).

2025 V.5 Last Updated: 03/01/2025

Page | 93
 Engineering BIM Standards

7.9.2 CONSTRUCTION SUBMISSIONS

Digital 3D representation of the Work mostly containing information about final and finished work,
although some temporary elements may be represented as well if found convenient (e.g., for coordination
purposes) by the Contractor. The Contractor will be responsible for continually updating this model
throughout construction, so it always reflects the latest information available, including but not limited to:
Shop Drawings, Approved Submittals and cut-sheets, field verification, Post Awards Contract Changes
(PACCs).

7.9.2.1 BASIS OF DESIGN SUBMISSION

Within 30 calendar days (or as defined) after the initial BIM kick-off meeting, the BIM Manager shall
prepare the Construction model developed from and based on the contract drawings. Geometry shall be
modeled in a way that mimics how the objects represented will be constructed.

7.9.2.2 MONTHLY PROGRESS UPDATES

Contractor or BIM Manager shall update the construction model and submit it on a monthly basis.
Updated Construction models shall include all approved shop drawings, RFIs, PACCs and any other
information available on the construction process.

7.9.3 4D SIMULATION SUBMISSION

Digital representation of the Work, integrating the Construction Model with the cost-loaded construction
Schedule. With each schedule update submitted to the Authority, the Contractor shall also submit an
updated 4D Simulation Model based on the latest version of the Construction Model and the revised
schedule.

7.9.4 LASER SCANNING SUBMISSION

Registered Point Clouds, when required by Contract, shall also be delivered to the Authority on intervals
that are project specific. Whilst Point Cloud data may be submitted several times during the duration of
Work, a final deliverable is expected.

2025 V.5 Last Updated: 03/01/2025

Page | 94
 Engineering BIM Standards

7.9.5 AS-CONSTRUCTED MODEL SUBMISSION

The As-Constructed Model represents the final version of the Construction Model, integrating both field-
verified locations and geometry for all model components, along with Asset information as required by the
Authority.
This Model will be submitted only once at the project's completion for review and approval. This Model is
of paramount importance to the Authority, and its approval is a mandatory requirement for achieving
project close-out and handover.
Previous submissions of the Construction Model, which contain incomplete information or only partially
meet the requirements outlined, do not qualify as an As-Constructed Model submission.

7.9.5.1 SUBMISSION REQUIREMENTS

• The Project Engineer has confirmed that construction has reached substantial completion.
• All required Asset information has been incorporated to the trade models by the Contractor (or
Subcontractors).
• The As-Constructed conditions have been accurately replicated to meet the LOA2 requirements.
• Target Levels of Development (LOD) as specified in the IDP have been achieved.
• All outstanding BIM-related issues have been closed.

The Contractor must submit for approval all native files (e.g., Revit Discipline models, Civil 3D models)
along with the federated Navisworks NWD* file.

NOTE:
The NWD file must be a data-rich model. Prevision must be taken by the BIM Manager to ensure that the
individual files composing the NWD are exported from their native platforms in a way that preserves all
relevant parameters and their corresponding values when transferred to Navisworks.

7.9.5.2 APPROVAL PROCESS

The Authority’s VDC Support Group and Asset Management team will conduct a thorough review of the
Models for accuracy, and compliance with these Standards. If the deliverables are deemed
unsatisfactory, the Authority may reject them. In such cases, the Contractor must meet with the PANYNJ
to address non-compliances, revise the Models, and resubmit them for approval within an agreed
timeframe (typically between two and four weeks, depending on the complexity and severity of the
issues).
This review cycle will continue, and project closure cannot occur until BIMs are approved. Regular Model
and data validation during the Construction phase, as required by these Standard, should help minimize
the likelihood of such delays.

2025 V.5 Last Updated: 03/01/2025

Page | 95
 Engineering BIM Standards

8.0 BIM COMPLIANCE REVIEW

To ensure accuracy, completeness, and adherence to the PANYNJ BIM Standards, all discipline models
must undergo BIM compliance reviews.
• During the Design phase (Stages I to III) is the Project Principal (PP) responsibility to submit and
request the compliance review.
• During the Construction phase (Stage IV) is the Resident Engineer’s (RE) responsibility to
submit and request the compliance review.
The VDC Group has developed specific reports that will be used to assess BIM Standards Compliance at
each stage of the project. These reports will be provided as feedback to the project teams.
The reviews will be conducted at an agreed-upon frequency and apply to all types of projects, including
those managed internally, by consultants, or by contractors, covering design contracts, construction, and
even work orders..

8.1 REVIEW MILESTONES AND REQUIREMENTS

BIM Compliance Reviews are mandatory for the following:

• Revit models used to produce report drawings (Stage I).
• Revit models used to produce contract drawings (Stage I to III).
• Navisworks files used for 3D Coordination (All Stages).
• Navisworks or Synchro files used for 4D Simulation (All Stages).
• BIM Execution Plan (All Stages).
• Revit models used during Construction (Stage IV Submittal).
• As-Constructed model (Final Stage IV Submittal).

Review Milestones:
• Design Phase: BIM compliance reviews are required at the 25%, 50%, and 100% project
milestones, in addition to any other milestones determined by the Project Principal. If no official
interim milestones exist before each official submission, reviews are still required.
• Construction Phase: BIM compliance reviews are required on a monthly basis, or as otherwise
specified by the Resident Engineer (RE).

Additional Requirements:
• The request for review must be initiated by the Project Principal or RE via SharePoint request
form.
• Reports will be distributed to the Assistant Chiefs, Principals, Project Principal, Task Leaders, and
RE. It is the responsibility of these individuals to ensure the results are communicated to the
contractor.
• A two-week period is allocated for addressing the issues reported and correcting any non-
compliant model files.

2025 V.5 Last Updated: 03/01/2025

Page | 96
 Engineering BIM Standards

8.2 REQUEST FOR VDC (BIM/CAD) REVIEW

As mentioned before, to formally initiate the VDC BIM Compliance Review process, the Project Principal
(PP) or Resident Engineer (RE) is required to submit the designated form via the official link:
REQUEST FOR VDC (BIM/CAD) REVIEW

The form is divided into two main sections for clarity and ease of use:
• Project Information (blue): Includes essential details about the project, including the project title,
facility name, stage, lead discipline, and responsible parties.
• Request Details (yellow): Focuses on the review specifics, such as file submission requirements
(which files were submitted, their location, naming, and size), the list of discipline models to be
reviewed, and any comments or notes to be shared with the VDC team prior to the review
process.

Figure 8-1 - Request for VDC (BIM/CAD) Review Sample Form

2025 V.5 Last Updated: 03/01/2025

Page | 97
 Engineering BIM Standards

To ensure an effective and thorough review, the form must be completed accurately and
comprehensively, allowing the VDC engineer to fully understand the request.
List of items and steps that must be duly completed:
1. Review Type: Select the applicable review type or project milestone from the following options:
o Interim
o PA Wide Review
o As-Advertised
o Addendum
o PACC
o Drawing of Record
o Conformed
o Work Order
o Stage IV Submittal
o As-Constructed (Final Stage IV Submittal)

2. Submittal Percentage/Number: For projects in the Design phase, indicate the completion
percentage (%). For projects in the Construction phase, provide the latest Submittal Number.

3. PID: Select the project PID and the following information will be automatically populated:
o Facility Name*
o Contract Number*
o Project Title*
o Stage*
o Confidentiality Level*
o Lead Discipline*
o LEA* (If not automatically populated, enter the name/email of the Project Principal).
o RE* (If not automatically populated, provide the name/email of the Resident Engineer -for
Construction projects only-).

4. Delivery Method: Specify whether the project follows a "Design-Build" or "Design-Bid-Build"

delivery method.
5. Charge Code: Indicate the charge code assigned to the project under review.

6. Folder Path: Copy and paste the path to the location where the files have been saved.

The next portion of this form is crucial, as only the disciplines listed will be reviewed. Any
discipline not included will be excluded from the review, and no feedback or results will be
provided by the VDC team.

7. Discipline: List all relevant discipline files (e.g., Architectural, Structural, 3D Coordination, 4D
Simulation) and/or document files (e.g., BIM Execution Plan) involved in the current request.

8. Group: Indicate whether each file requires review for CAD compliance, BIM compliance, or both.

9. Task Leader: Applicable only for Design Stages.

10. Consultant/Contractor: Indicate the responsible company from the dropdown list. For in-house
production, select "In-House" (located at the end of the list).

2025 V.5 Last Updated: 03/01/2025

Page | 98
 Engineering BIM Standards

NOTE:
Use the (+) symbol to add more files or disciplines as needed for review.
11. Add Comments/Notes to be considered during the review.

12. Save/submit your BIM Compliance Review Request.

8.3 BIM COMPLIANCE REPORTS

This section provides an overview of the VDC reports and highlights the key components evaluated
during each Compliance Review. Each item included in these BIM Compliance Reports represents a
fundamental element of the model’s configuration, organization, or data accuracy. The VDC team will
evaluate these components to ensure that the BIM project files adhere to the established BIM Standards.

8.3.1 DISCIPLINE COMPLIANCE REPORT

The main purpose of this report is to verify that each model discipline adheres to the BIM standards for
file naming, model accuracy, and drawing consistency. This report is divided into 5 sections:

Figure 8-2 - Project Information Sample

Figure 8-3 - Pre-Audit Sample

Figure 8-4 - Pre-Audit Sample

2025 V.5 Last Updated: 03/01/2025

Page | 99
 Engineering BIM Standards

Figure 8-5 - Drawing Performance Sample

8.3.1.1 DETAILED DISCIPLINE ITEMS SUMMARY

PRE-AUDIT:

ITEM DESCRIPTION
Files Location Submitted files are stored in the correct location within the PA server.
Files Submitted All necessary project files have been submitted.
Files Naming
File names are following the Standards.
Convention
Files size should be less than 650MB. First warning will be indicated when file
Files Size
exceeds 300MB.
Revit version of the file is correlative to the version established in the BEP of
Software Version
the project.
PROJECT SETUP:

ITEM DESCRIPTION
Project Coordinates need to be acquired coordinate from the SM provided,
Project Coordinates
and consistent across all Disciplines.
Project Information Project Information parameters should be completed.
All Views within the Project Browser must be assigned to the proper Sub-
Project Browser
Discipline and View Classification.
Project Levels Levels are copy/monitored to ensure consistency across all Disciplines
Project Grids Grids are copy/monitored to ensure consistency across all Disciplines.
Project Units set up in the project are consistent with the ones provided within
Project Units
the PA templates.
AutoCAD Links All AutoCAD Files used should be linked and pinned.
All Project Revit files should be linked and pinned into each other, including
Revit Links
the Site Model.
Point Clouds Links All point clouds should be pinned.
Project Phases and settings to be established by Architecture or Lead
Phase Settings Discipline. Other disciplines should recreate the Phases settings to ensure
consistency.
NAMING CONVENTION:

ITEM DESCRIPTION
Families in use are following the PA Naming Convention.
Families o Model Families: CATEGORY-MANUFACTURER-
DESCRIPTION/MODEL NUMBER

2025 V.5 Last Updated: 03/01/2025

Page | 100
 Engineering BIM Standards

o Annotation Families: CI-CATEGORY-DESCRIPTION1-

DESCRIPTION2
Worksets are following the Standard Naming Convention. Default Worksets
should be maintained. Worksets naming convention:
Worksets
o DISCIPLINECODE-DESCRIPTION
Views are following the PA Naming Convention. Views naming convention:
Views
VIEW-LEVEL/LOCATION/SEQUENCE-DESCRIPTION
Sheet Name Sheets are following the PA Naming Convention.
Sheet Number Sheets Numbers are following the PA Naming Convention.

MODEL INTEGRITY:

ITEM DESCRIPTION
Phases Elements are assigned to phases properly.
Worksets Elements are assigned to Worksets properly.
Rooms Setup There should be no duplicated or floating rooms in the model.
Views Category Views are assigned to the correct Category based on their use.
Sheets Category Sheets are assigned to the correct Category based on their use.
All Schedules in the Project are smart, meaning created by bringing
Schedules
information from the model.
Overlaps/Duplicates There are no Clashes or Duplicated elements within the model.
Object Hosting All elements are hosted.
Floating Content No element is loose or floating
By preference, Generic Models should not be used, but if needed those
Object Category
should be renamed and re-categorized accordingly.
Parameter
All required parameters are completed.
Assignment
Revit Models must be cleaned before every official submission by purging,
Model Cleanup
deleting temporary views, etc.
PLAN SET PREPARATION:

ITEM DESCRIPTION
PA Official Title Sheet should be used and placed inside the Lead Discipline
Title Sheet (Lead)
Revit Model.
Contract Border PA Official Contract Border family should be used.
Drawing Information Drawing Information has been completed at all sheets.
Consultant
Consultant information must be included in the Contract Border.
Information
No Linework in Sheets Objects other than the Viewports, North Arrow and Graphic Scales are not
allowed directly on Sheets; Other objects must be included in either separate
Drafting Views, or in the Design Views that they belong to.
PDFs Setup PDFs have been exported in full size and in Black and White.

2025 V.5 Last Updated: 03/01/2025

Page | 101
 Engineering BIM Standards

STYLES:

ITEM DESCRIPTION
Texts in use are per the ones defined in the template. Or additional styles
Text
follow PA Naming Standards.
Dimensions Dimensions in use are per the ones defined in the template.
Lines in use are per the ones defined in the template. Or additional styles
Lines
follow PA Naming Standards.
Symbols in use are per the ones defined in the template. Or additional
Symbols
annotations follow PA Naming Standards.
Tags Tags in use are per the ones defined in the template.
Fill regions in use are per the ones defined in the template. Or additional
Fill Regions
Regions follow PA Naming Standards.

NOTE:
The "Drawings Performance Summary" section, which includes the review of Plan Set Preparation and
Styles, is applicable only during the Design Stages. For projects in the Construction Phase, this section
will be marked as N/A.

8.3.2 3D COORDINATION REPORT

The main purpose of this report is to assess the alignment and clash detection of 3D models across
disciplines, ensuring a coordinated and conflict-free or minimal conflict design. This report is divided into 4
sections:

Figure 8-8 - 3D Coord. Project Information Sample

Figure 8-9 - 3D Coord. Pre-Audit Sample

2025 V.5 Last Updated: 03/01/2025

Page | 102
 Engineering BIM Standards

Figure 8-10 - 3D Coord. Performance Summary Sample

8.3.2.1 DETAILED 3D ITEMS SUMMARY

BIM 3D Coordination Review Report checks for compliance in the submitted NWD/NWF files in the
following fields among others:

PRE-AUDIT:

ITEM DESCRIPTION
Files Submitted All necessary project files have been submitted.
Submitted files are stored in the correct location within the PA
Files Location
server.
File names are following the Standards. NWD & NWF should follow:
Files Naming Convention
PID-3D
All necessary information related to the progress deliverables have
BIM Progress Report
been outlined in the BIM Progress Report.
Navisworks version of the file is correlative to the version
Software Version
established in the BEP of the project.
PROJECT SETUP:

ITEM DESCRIPTION
All trade models and Site Model are appended to the Federated
All Links
model.
Appended Files Format All native models should be imported in NWC format.
All elements should be grouped using Search Sets by Milestones and
Search Sets
Activities ID.
All defined Areas of Interest must have at least one Viewpoint that
Areas of Interest
shows the area in detail.
NAMING CONVENTION:

ITEM DESCRIPTION
Appended Files Name NWCs should follow the native Revit Model naming convention.

2025 V.5 Last Updated: 03/01/2025

Page | 103
 Engineering BIM Standards

MODEL INTEGRITY:

ITEM DESCRIPTION
All appended files are showing aligned to each other based on their
Models Alignment
coordinates.
All PA Federated Models must follow the BIM Standard Color
Color Scheme
Scheme.
Room geometries should not be exported in the NWC files in order to
Rooms
avoid interferences while running clash detection tools.
2D Elements should not be exported in the NWC files to avoid
2D Elements
interferences while running clash detection tools.
COORDINATION

ITEM DESCRIPTION
Clash Tests must be created on the Federated model, the file must
Clash Tests contain at least one test for each combination of two separate NWCs
files appended.
Clash Settings Clash settings should be set as per template.
Clash Grouping must be present on each clash test to allow users to
Clash Grouping manage all individual issues that contain 2 or more single
interferences.
All clashes must be classified with their correspondent status at the
Clash Status
moment of the submission (New, Active, Resolved, etc.)
All Viewpoints must be grouped and managed in an organized
Viewpoints Folder Structure
manner for ease of use.

8.3.3 4D SIMULATION REPORT

The 4D Simulation Report is intended to validate the integration of 3D models with project schedules,
ensuring accurate construction sequencing, task alignment, and timeline consistency. This report is
divided into 4 main sections:

Figure 8-11 - 4D Sim. Project Information Sample

2025 V.5 Last Updated: 03/01/2025

Page | 104
 Engineering BIM Standards

Figure 8-12 - 4D Sim. Pre-Audit Sample

Figure 8-13 - 4D Sim. Performance Summary Sample

8.3.3.1 DETAILED 4D ITEMS SUMMARY

BIM 4D Simulation Review Report checks for compliance in the submitted Navisworks or Synchro files in
the following fields among others:

PRE-AUDIT:

ITEM DESCRIPTION
Files Submitted All necessary project files have been submitted.
Submitted files are stored in the correct location within the PA
Files Location
server.
File names are following the Standards. NWD & NWF or Synchro
Files Naming Convention
should follow: PID-4D
All relevant information to the progress deliverables has been
BIM Progress Report
outlined in the BIM Progress Report.
Navisworks/Synchro Pro version of the file is correlative to the
Software Version
version established in the BEP of the project.

2025 V.5 Last Updated: 03/01/2025

Page | 105
 Engineering BIM Standards

PROJECT SETUP:

ITEM DESCRIPTION
Timeliner (or Synchro) Appearance should be setup based on the
Appearance Profiler
BIM Standards.
Data Source file must correspond to latest Schedule Submission
Schedule Data Source
and must be defined on the monthly submission Report.
Data Source files must correspond to latest BIM files Submission
3D Models Data Source
and must be defined on the monthly submission Report.
MODEL INTEGRITY:

ITEM DESCRIPTION
Site Context Model should be created in order to include site context
Site Context information such as: site topography, project limits, adjacent
building, roads, sidewalks, among others.
Task Names All Activities on Schedule must have a Name assigned.
All Activities on the Schedule must have an Activity Identification
Task Activity IDs
Number.
All Schedule Activities must contain Planned Dates, Start and Finish,
Planned Dates
as per Baseline Schedule.
All Schedule Activities must contain Actual Dates, Start and Finish,
Actual Dates
as per most current Schedule Update.
All Geometrical elements must be attached to their specific Activities
Attached by Sets
using the correspondent search set.
Attached by Explicit Selection Elements attached by explicit selection are not allowed.
Unattached items All Geometrical elements must be attached to one BIM Activity.
Items in Multiple Tasks All Geometrical elements must be attached to only one BIM Activity.
Items in Overlapping Tasks All Geometrical elements must be attached to only one BIM Activity.

2025 V.5 Last Updated: 03/01/2025

Page | 106
 Engineering BIM Standards

8.3.4 BIM EXECUTION PLAN REPORT

The purpose of this BIM Execution Plan Compliance Report is to assess and ensure project adherence to
company BIM standards, workflows, and deliverable requirements. The report is divided into

Figure 8-14 - BEP Project Information Sample

Figure 8-15 - BEP Pre-Audit Sample

Figure 8-16 - BEP Performance Summary Sample

2025 V.5 Last Updated: 03/01/2025

Page | 107
 Engineering BIM Standards

8.3.4.2 DETAILED BEP ITEMS SUMMARY

PRE-AUDIT:

ITEM DESCRIPTION
BEP Template Ensure available PA Templates have been used.
Overall document structure and organization is done based on project
Document Integrity
size and needs.
INFORMATION:

ITEM DESCRIPTION
Project Information Complete table showing all Project Information.
Scope Describe project scope, detailing phases, add images, others.
Complete all project contacts including Port Authority staff and all
Contacts
external stakeholders.
Project Schedule Detail project duration and add specific dates for main milestones.

GENERAL:

ITEM DESCRIPTION
Model Breakdown Include list of all models to be developed and submitted.
Other Deliverables Breakdown Include list of all files to be developed and submitted.
Detail all content and workflow for the development of the Site Context
Site Context Model
model.
Add the specific project coordinates to be used throughout all project
Project Coordinates
model files.
Add, describe all Revit Phases that will be included as part of the
Project Phases
model files.
Include table describing the LOD to be used based on the project
Level of Development
needs and the IDP.
Include list of parameters that will be included in the models and data
Model Data
to be captured as per the IDP.
Software and Templates Include list of Software, templates, and versions to be used.
Add any other project specific requirement not mentioned anywhere
Specific Requirements
else.
COMMUNICATION:

ITEM DESCRIPTION
Add description for all BIM meetings including the goal, frequency, and
Meetings
owner.
Add the Exchange platform to be used, include list of deliverables,
Information Exchange
frequency of delivery, etc.
If implemented, include list of members that need to be invited to the
Autodesk Construction Cloud
ACC project hub.

2025 V.5 Last Updated: 03/01/2025

Page | 108
 Engineering BIM Standards

MODELS DEVELOPMENT:

ITEM DESCRIPTION
Design Workflow
Add the description of the Revit models development including the
Construction Workflow workflow, stakeholders, coordination process, data insertion, LOD
validation, and any other relevant information.
As-Constructed Workflow

3D COORDINATION:

ITEM DESCRIPTION
Add the description of the Coordination models development including
Coordination Workflow the workflow, stakeholders, coordination process, and any other
relevant information.
Complete table with the AOI depending on the project needs and
Areas of Interest
scope.
Clash report should include all relevant information to ensure clash is
Clash Report
able to be identified, analyzed, assigned and status is updated.
4D SIMULATION:

ITEM DESCRIPTION
Add the description of the Schedule Simulation model development
Simulation Workflow including the workflow, stakeholders, simulation process, and any other
relevant information.
LASER SCANNING:

ITEM DESCRIPTION
Add the description of the Laser Scanning development including the
Scanning Workflow workflow, stakeholders, scanning process, and any other relevant
information.
Scanning Schedule Add the scanning plan based on the project schedule.

2025 V.5 Last Updated: 03/01/2025

Page | 109
 Engineering BIM Standards

APPENDIX A: CONFIDENTIAL & CONFIDENTIAL PRIVILEGE PROJECTS

Confidential and Confidential Privilege Projects are those in which unique circumstances may require
different guidelines be followed in order to comply with the BIM Standards. The contents of this document
will be followed in addition to the ones already specified in the BIM Standards, unless specifically
instructed otherwise within this section.

PURPOSE

The Port Authority C & CP Standard Compliance outlined is established to provide guidance for the
preparation of the EAD Division of the Port Authority of New York and New Jersey’s contract documents
that contain Confidential and Confidential Privilege.
This document is intended for use by both in-house personnel as well as outside consultants involved in
creating construction documents for the Port Authority. It establishes requirements and procedures for the
preparation and submission of BIM based drawings throughout the project life cycle. Adherence to this
standard ensures that the E/A Design Division and the Construction Division of the PANYNJ will receive
and produce data in a consistent format.
For more information on practices and procedures on protected information projects it can be found on
Engineering Department Protected Information Practices and Procedures.

CONFIDENTIAL PROJECTS

Confidential Projects contain highly sensitive information that if lost or made public could seriously
damage or compromise the Port Authority and/or public safety and security. Confidential information
includes, but is not limited to, methods utilized to mitigate vulnerabilities and threats, such as identity,
location, design construction and fabrication of security systems.
For that reason, if aspects being worked on as part of a project drawing are considered Confidential, they
will need to be handled differently than standard contract drawings.
If information on a drawing is Confidential, then that model drawing is to be stored in the Model_C,
Model_3D_C folders. Any plotsheet drawing that contains Confidential information must be stored in the
Plotsheets_C folder. It is permitted to reference non-Confidential information from outside the
Confidential folder into a Confidential project. If a model file that has been deemed Confidential needs to
be shared across disciplines, then the file is to be copied to the Publish_C folder.
The Warning Sign is displayed below:

Figure 9-1 - Confidential Information Warning Sign

2025 V.5 Last Updated: 03/01/2025

Page | 110
 Engineering BIM Standards

Cover sheets shall be used to divide the complete set into Unmarked, Confidential and Confidential
Privileged drawings, the cover sheet files are found inside the Contract Border folder of the standardize
files. If a project contains any Confidential sheets, then they must be separated out into their own
set with its own Cover Sheet. The Confidential Stamp markings at the top, bottom and right side of the
pages must be displayed, identifying the project as Confidential. This is accomplished by turning on
and thawing the “GN-ANNO-TTLB-CONF” layer. Confidential Cover Sheet doesn’t require the use of
the Warning stamp.
All interior Confidential pages within the set must also be marked Confidential at the top, bottom, and right
side of the page. Sets of documents that are folded or rolled must be marked so that the marking is
visible on the outside of the set once folded or rolled. This is accomplished by inserting the “Drawing_Info
– Stamp_Cbar.dwg” block into paper space of the Plotsheet drawing containing the Confidential
information. The “Drawing_Info – Stamp_Cbar.dwg” block is to be inserted with an insertion point of 0,0,0
on layer 0 and is not to be exploded or modified in any way. All of the Confidential Markings are displayed
in following images.

Figure 9-2 - Example of Confidential Projects Title sheet

On the Drawing Index sheet, names of Confidential drawings should be listed and should take the form:
"<Drawing Title> (Protected Information)", where <Drawing Title> is the title of a Confidential drawing.

2025 V.5 Last Updated: 03/01/2025

Page | 111
 Engineering BIM Standards

All interior Confidential pages within the set must also be marked Confidential at the top, bottom, and right
side of the page. Sets of documents that are folded or rolled must be marked so that the marking is
visible on the outside of the set once folded or rolled. The Warning Sign and Confidential markings can
be set to display by setting a check mark in the box next to the "Warning Sign" parameter and the
"Confidential Sheet" parameter, respectively, in the properties set for the Contract border.
All the Confidential Markings for interior pages are displayed in the following image:

Figure 9-3 - Example of Interior Confidential Page

NOTE:
For more information on the handling and submitting of Confidential projects, refer to “The Port Authority
of New York & New Jersey Information Security Handbook”.

Confidential and Unmarked drawings will be separated into two sets. On the Drawing Index sheet, names
of Confidential drawings shall be listed to inform the viewer that additional drawings have protected
information. This drawing shall take the form "<Drawing Title> (Confidential)", where <Drawing Title> is
the title of a Confidential drawing, as shown in the image below.

2025 V.5 Last Updated: 03/01/2025

Page | 112
 Engineering BIM Standards

Figure 9-4 - Index of Drawings

For more information on the handling and submitting of Confidential projects refer to “The Port Authority
of New York & New Jersey Information Security Handbook”.

CONFIDENTIAL PRIVILEGED PROJECTS

Confidential Privileged Projects contain extremely sensitive security or public safety information that if lost
or made public could seriously damage or compromise the Port Authority and/or public safety and
security. Confidential Privileged information includes, but is not limited to, any information identifying
vulnerabilities, capabilities, threats, operational methodologies and/or security related design criteria.
For that reason, if aspects being worked on as part of a project drawing are considered Confidential
PRIVILEGED, they will need to be handled differently than standard contract drawings.
If information on a drawing is Confidential Privileged, then that model drawing is to be stored in the
Model_CP, Model_3D_CP folders. Any plotsheet drawing that contains Confidential Privileged
information must be stored in the Plotsheets_CP folder. It is permitted to reference non-Confidential
information from outside the CP folder into a Confidential Privileged plotsheet drawing. If a model file that
has been deemed Confidential Privileged needs to be shared across disciplines, then the file is to be
copied to the Publish_CP folder.
Cover sheets shall be used to divide the contract set into Unmarked, Confidential and Confidential
Privileged drawings; the cover sheet files are found inside the Contract Border folder of the standardize
files. If a project contains any Confidential Privileged sheets, then they must be separated out into
their own set with its own Cover Sheet. The Confidential Information Warning Sign (CP -
WARNING.dwg) must be displayed on the Cover Sheet of the Confidential Privileged set, along with
markings at the top, bottom and right side of the page identifying the project as Confidential Privileged.
This is accomplished by turning on and thawing the “GN-ANNO-TTLB-CP__” layer.

2025 V.5 Last Updated: 03/01/2025

Page | 113
 Engineering BIM Standards

The Title Sheet setup for Confidential Privileged projects is shown in the following image:

Figure 9-5 - Title Sheet setup of Confidential Privileged projects

All interior pages within the set must also be marked at the top, bottom, and right side of the page. Sets
of documents that are folded or rolled must be marked so that the marking is visible on the outside of the
set once folded or rolled. The Confidential Privileged markings can be set to display by setting a check
mark in the box next to the "Confidential Privileged Sheet" parameter (for instructions regarding the setup
of the CP Number parameter, see above). All the Confidential Privileged Markings for interior pages are
displayed in the following image.

2025 V.5 Last Updated: 03/01/2025

Page | 114
 Engineering BIM Standards

Figure 9-6 - Interior pages of Confidential Privileged Projects

For more information on the handling and submitting of Confidential Privileged projects, refer to “The Port
Authority of New York & New Jersey Information Security Handbook”.

2025 V.5 Last Updated: 03/01/2025

Page | 115
 Engineering BIM Standards

APPENDIX B: BIM EXECUTION PLAN TEMPLATES

DESIGN BID BUILD - TEMPLATE FOR DESIGN

To download the BEP Template for Design, follow the link below:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 116
 Engineering BIM Standards

DESIGN BID BUILD- TEMPLATE FOR CONSTRUCTION

To download the BEP Template for Construction, follow the link below:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 117
 Engineering BIM Standards

DESIGN BUILD - TEMPLATE FOR DESIGN & CONSTRUCTION

To download the BEP Template for Design Build, follow the link below:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 118
 Engineering BIM Standards

APPENDIX C: BIM PROGRESS REPORT TEMPLATE

To download the BIM Progress Report Template, follow the link below:
Engineering Available Documents > VDC Requirements and Standards (BIM/CAD) > BIM Standard >
BIM Support Files

2025 V.5 Last Updated: 03/01/2025

Page | 119
 Engineering BIM Standards

DOCUMENT CHANGE CONTROL TABLE

N Date V. Approver Section Update Description

1.4 Acronyms and Section was relocated and acronyms were
1 12/2023 2023 v1 Turner, Ashley-Dojn
Abbreviations added.
Section name changed from BIM
2 12/2023 2023 v1 Turner, Ashley-Dojn 2.0 VDC Engagement Workflows to VDC Engagement. Content
within Section was re-organized.
3 12/2023 2023 v1 Turner, Ashley-Dojn 2.2 BIM Objectives Sub-Section was added.
2.3 BIM Dimensions
4 12/2023 2023 v1 Turner, Ashley-Dojn Image updated.
Applications
2.4 BIM Models
5 12/2023 2023 v1 Turner, Ashley-Dojn Image updated.
Expectations
6 12/2023 2024 v1 Turner, Ashley-Dojn 2.5 BIM Models Lifecycle Image updated.
2.6 VDC Roles and Sub-Section was added
7 12/2023 2024 v1 Turner, Ashley-Dojn
Responsibilities
8 12/2023 2024 v1 Turner, Ashley-Dojn 5.2 Files Ownership Section title changed
Old “Level of Development”, section
5.4 Information Delivery
9 12/2023 2024 v1 Turner, Ashley-Dojn renamed, and new subsections and
Plan
information added.
10 12/2023 2024 v1 Turner, Ashley-Dojn 6.3 Design Site Model Section updated.
11 12/2023 2024 v1 Turner, Ashley-Dojn 7.8 Reality Capture Section updated.
8.6 BIM – BIM Execution New Section added.
12 01/2024 2024 v2 Turner, Ashley-Dojn
Plan Report
13 01/2024 2024 v2 Turner, Ashley-Dojn 7.8 Reality Capture Workflows images have been added.
Updated the document look and feel and
14 05/2024 2024 v3 Turner, Ashley-Dojn All Sections
content format.
Image updated, added Program
15 1/2025 2025 v1 Turner, Ashley-Dojn 1.2 Document Hierarchy
Requirements.
1.3 Acronyms and
16 1/2025 2025 v1 Turner, Ashley-Dojn PP and SDE roles added.
Abbreviations
17 1/2025 2025 v1 Turner, Ashley-Dojn 3.3 Revit Templates 2024 Templates have been added.
As-Constructed stamp replaced by
18 1/2025 2025 v1 Turner, Ashley-Dojn 3.4.3 Stamps
Record Drawings.
3.5 Autodesk
19 1/2025 2025 v1 Turner, Ashley-Dojn Section content updated.
Construction Cloud
4.3.4 Sheet Set
20 1/2025 2025 v1 Turner, Ashley-Dojn Sub-Section added.
numbering
21 1/2025 2025 v1 Turner, Ashley-Dojn 5.1 Software Changed current version in use to 2024.
22 1/2025 2025 v1 Turner, Ashley-Dojn 5.3 Coordinate Systems Section updated.
23 1/2025 2025 v1 Turner, Ashley-Dojn 6.2 Folder Structure Executive folder added.
24 1/2025 2025 v1 Turner, Ashley-Dojn 6.5.17 Schedules New predefined schedules added.
25 1/2025 2025 v1 Turner, Ashley-Dojn 6.5.20 View Templates Sub-Section added.
26 1/2025 2025 v1 Turner, Ashley-Dojn 6.5.21 QTO Process Sub-Section added.
6.5.22 Sustainability
27 1/2025 2025 v1 Turner, Ashley-Dojn Sub-Section added.
Analysis
28 1/2025 2025 v1 Turner, Ashley-Dojn 6.6 Addendum Models Sub-Section added.
29 1/2025 2025 v1 Turner, Ashley-Dojn 6.7 PACC Models Sub-Section added.
30 1/2025 2025 v1 Turner, Ashley-Dojn 6.9 Design Deliverables Sub-Sections content updated.
7.7 As-Constructed Sub-Sections restructure and content
1/2025 2025 v1 Turner, Ashley-Dojn
Model updated.
8.0 BIM Compliance
31 1/2025 2025 v1 Turner, Ashley-Dojn Images updated.
Review
32 1/2025 2025 v1 Turner, Ashley-Dojn All document LEA replaced by PP.

2025 V.5 Last Updated: 03/01/2025

Page | 120