Skip to main content

Project BIM Requirements (PBR) Standard

Summary

Project BIM Requirements (PBR) define the ways that BIM will be used on a project. For those with capital programs, owner organizations may create a general BIM Requirements document that defines standards that meet the owner organization's needs for planning, design, construction, and operations. For owners who only manage the occasional construction project, they may develop BIM requirements for a single project. This standard supports both types of BIM Requirements by defining the elements that should be addressed in the Owner Project Requirements (OPR) documentation for a viable BIM project through the planning, design, construction, and operations of built environment assets. The National Institute of Building Sciences defines viable BIM as: the use of BIM in order to achieve the objectives of an owner organization in capital projects, including processes, infrastructure, standards, and execution.

Why is this standard important?

By developing a standard for Project BIM Requirements, the project and project team members can achieve the following value:

Ultimately, the entire team will gain value through the increased level of planning by reducing the unknowns in the implementation process, thereby reducing the overall risk to all parties and the project.

Who is the Audience?

The primary audiences of the Project BIM Requirements module are the owner and the project delivery team members for all projects that plan to implement BIM at any stage of the delivery process. The standard and resources are developed to support various project types, from buildings to infrastructure. Industry organizations that define project BIM requirements would also benefit from using the standard to assure that their contracts and templates address all requirement elements in the BIM requirements sections of their products.

When should this module be used?

The Project BIM Requirements standard and resources can be implemented during the owner's pre-planning phase and updated as new activities are planned throughout the project life cycle.

There are two types of BIM requirements that an owner organization may define: 1) The Organization's general BIM requirements standard and 2) specific Project BIM Requirements. This standard applies to both types of requirements. First, if an owner organization has a capital project portfolio with repeated construction projects, it is recommended that the owner organization develop a general standard for their organization's BIM Requirements. This can incorporate their data needs for operations and maintenance as well as create standards for project management during planning, design, and construction activities. Second, an owner organization will want to include Project BIM Requirements when developing project specific requirement documents, often called the Owner Project Requirements (OPR). If the owner organization has a general BIM requirements document, they can use it as the basis for a Project BIM Requirements documentation. An owner who does not do construction routinely should also develop a Project BIM Requirements document as part of the contract. See the Example Language in the resources section for supporting materials.

What is contained in the module?

This module includes the following items:

How should this module be used?

The owner can leverage this module to clearly document their Project BIM Requirements on a project. This Standard also references the BIM Execution Planning, BIM Uses, and COBie modules. The owner can also leverage the example language to develop a customized Project BIM Requirements document that complies with the standard.

How was this version of the PBR module developed?

The Planning Committee of the National BIM Standard formed a workgroup charged with creating Project BIM Requirements for a minimally viable BIM supported project. This workgroup included industry representatives from multiple sectors with a variety of professional experience with BIM. The workgroup, with the support of the University of Washington team, reviewed existing standards (national, international, state, local) that define BIM project requirements. It was found that all of the standards were missing some key elements needed for viable BIM projects. From these industry examples, the workgroup compiled a list of required elements that should be addressed in a Project BIM Requirements document. The definition of terms and descriptions of each element in the standard was discussed and debated within the workgroup first, and then with the NBIMS Planning Committee. Terms and definitions were also debated across the modules in V4. The goal was to create a National BIM Standard that was internally consistent and aligned with industry best practices. The Project BIM Requirements standard is broadly applicable to the planning, design, construction, and operations of built environment assets of all kinds from buildings to infrastructure.

Foreword

Project BIM Requirements is a foundational document to define the implementation strategy for BIM on a project. This is the first version of a Project BIM Requirements Standard in the U.S. National BIM Standard.

This document was prepared by the Project BIM Requirements (PBR) Workgroup of the National BIM Standard Project. In addition to this standard, NBIMS-US includes a Project BIM Requirements Standard User's Guide, a Guideline for Project BIM Requirements, and Project BIM Requirements example language.

Introduction

This Project BIM Requirements Standard defines elements that an owner should include when defining their Project BIM requirements for the delivery team members. This Standard is for all participants supporting BIM use on a project. While the term Owner is used here, this standard could be used for any party who seeks to establish BIM requirements for a project.

The Project BIM Requirements can be developed as general requirements at an organizational level, and they can also be developed for a specific project. The Project BIM Requirements should address each of the elements defined in the standard.

The Project BIM Requirements Workgroup also developed example language for each of the clauses. This example language can support the user's understanding of each element. Owners may also use the example language and adapt it to their own organizational and project context.

1 Scope  

This standard defines the elements of project BIM requirements that the owner (also known as the Appointing Party in ISO 19650-2 (2018) would include in the Owner Project Requirements (OPR). It is intended for an owner to use to define Project BIM Requirements for delivery team members (also known as the Appointed Party in ISO 19650-2 (2018)). This standard is intended to define the minimum requirements for a viable BIM project. An owner may extend requirements beyond the scope of this standard to include other BIM uses or BIM implementation.

2 Terms and Definitions  

Appointed Party

The entity that is contracted for and provides information concerning works, goods, or services.

[Source: ISO 19650-1:2018(en), modified – added 'the entity that is contracted for and provides']

[Also known as contractor, designer, consultant, architect, engineer, subcontractor, subconsultant]

Appointing Party

The entity that holds the contract and receives information concerning works, goods, or services.

[Source: ISO 19650-1:2018(en), modified – added 'the entity that is contracted for and receives']

[Also known as owner, client]

Attribute

A single unit of data that in a certain context is considered indivisible.

[Source: ISO/TS 21089:2018(en), 3.44, modified from term 'data attribute' to 'attribute']

BIM Deliverable

Data and/or model information to be provided to a party in connection with a BIM Use.

[Source: NBIMS-US™ Version 3, modified – revised "a BIM - related service over the facility's life-cycle" to "BIM Use"]

[Also known as Data Deliverable or Model Deliverable]

BIM Execution Plan

A plan that explains how the information management aspects of a project will be carried out by the project team.

[Source: ISO 19650-2:2018(en), 3.1.3.1 – modified 'delivery team' to 'project team']

See Appointment BIM Execution Plan (ABEP) and Project BIM Execution Plan (PBEP).

BIM Use

The purpose for applying BIM. BIM Use includes name, definition, and related terms.

[Source: BIM Use Definitions Module, NBIMS- US, V4]

BIM Use Case

A specific methodology and outcome achieved when applying a BIM Use on a project(s) or within an organization(s). A BIM Uses Case includes a BIM Use name, followed by the method, followed by the outcome.

[Source: BIM Use Definitions Module, NBIMS-US, V4]

Building Information Management

Functions of controlling the acquisition, analysis, retention, retrieval, and distribution of built environment asset information all within an information processing system

[Source: ISO/IEC 20944-1:2013(en), modified term – added "building" to specify information about built environment assets, and modified the definition – added 'built environment asset' to the definition of Information Management to clarify the specific management of 'building' information.]

Note: Within the term, 'building' refers to the process of building a built environment asset, not a specific type of facility. BIM is a function that can be implemented across all types of built environment assets, including buildings, bridges, highways, tunnels, process plants, landscape, and other infrastructure and facility types.

Building Information Model

A shared digital representation of physical and functional characteristics of a built environment asset.

[Source: NBIMS-US™ Version 3, modified – added the word 'shared' and added the words 'and built asset' – see Note 2 and Note 3]

Note 1: NBIMS-US™ Version 3 also included "As such it serves as a shared knowledge resource for information about a facility, forming a reliable basis for decisions during its life cycle from inception onwards."

Note 2: Added the word 'shared' to the definition to be more consistent with ISO/TS 12911:2012(en) definition. The ISO definition uses the term 'built object' instead of 'facility' and adds facility types including 'buildings, bridges, roads, process plant'.

Note 3: Added the words 'built environment assets' to specify that a building information model can include representations of buildings, roads, bridges, plants, and other built assets.

Building Information Modeling

Generating and using a shared digital representation of a built environment asset to facilitate design, construction, and operation processes to form a reliable basis for decisions.

[Source: ISO 19650-1:2018(en), 3.3.14, modified – revised 'Use' to 'Generating and using']

Common Data Environment

An agreed source of information for any given project or asset, for collecting, managing and disseminating each information container through a managed process.

[Source: ISO 19650-2:2018(en), modified - added 'An' as the first word]

Note: A CDE workflow describes the processes to be used and a CDE solution can provide the technology to support those processes.

Component

The individual instances of the products and equipment defined in the Type data table.

[Source: COBie Module, NBIMS-US™ V4]

Delivery Phase

Part of the life cycle, during which an asset is conceived, designed, constructed, and commissioned.

[Source: ISO 19650-2:2018(en), modified - added ‘conceived’]

Delivery Team

The collection of entities who are contracted or appointed for works, goods, or services.

[Source: NBIMS-US™ V3, modified – added "or appointed" and the note]

Note: Delivery team includes all appointed parties for the planning, design, and construction of a project.

Delivery Team Member

The entity that is contracted for and provides information concerning works, goods, or services.

Federated Model

A system of models consisting of linked but distinct components derived from multiple data sources that do not lose their identity or integrity.

Information Accuracy

A specification or method to define how close the geometric asset and spatial information is to an actual or planned requirement.

Information Detail

A specification or method to define the extent and granularity of the required geometric asset and spatial information.

Information Exchange

Act of satisfying an information requirement or part thereof through storing, accessing, transferring, and archiving information.

[Source: ISO 19650-1:2018(en), 3.3.7 – added ‘through storing, accessing, transferring, and archiving information’]

Metadata

Data that defines and describes other data.

[Source: ISO 1087-1:2000, 3.2.18]

Model Element

A portion of the model(s) representing a component, assembly, or construction entity (part) which, in itself or in combination with other parts, fulfills a predominating function of a construction entity.

Owner

The entity that holds the contract and receives information concerning works, goods, or services.

[Source: ISO 19650-1:2018(en) defined as appointing party, added ‘the entity that is contracted for and receives’]

[Also known as appointing party*]

*Note: NBIMS-US™ recognizes the term appointing party, but uses the term owner in the standard documents as it is recognized as the common term used in the US market. These should be considered interchangeable.

Owner Project Requirements

A written document that details the ideas, concepts, and criteria required by the appointing party, and the requirements upon which works, goods, and services are based.

Note: Appointing Party's Project Requirements (APPR) is an alternative term.

Process

A sequence or flow of activities in an organization with the objective of carrying out work.

[Source: Business Process Model and Notation (BPMN) Version 2.0.2, Object Management Group, December 2013]

Project BIM Execution Plan

A collaborative plan that explains how the information management aspects of the project delivery process will be carried out by the delivery team.

Note: Adapted from ISO 19650 definition for BIM Execution Plan to describe the collaborative plan at a project level, instead of an appointment level plan.

Project Milestone

A discrete point in time associated with a project outcome.

Project Team

Owner [Appointing Party] and all delivery teams.

[Source: ISO 19650-1:2018(en), added "owner"]

Quality Management

A set of processes that involve Quality Planning, Quality Assurance, and Quality Control as applied to the management of information.

3 Reference Documents  

The following documents are referenced throughout this standard:

  • BIM Execution Plan Standard Version 4, U.S. National BIM Standard, 2023
  • BIM Use Definitions Standard Version 4, U.S. National BIM Standard, 2023
  • COBie, Version 3, U.S. National BIM Standard Version 4, 2023
  • ISO 19650-1: Organization and Digitization of Information about Buildings and Civil Engineering Works, Including Building Information Modeling (BIM)-Information Management using Building Information Modeling. Part 1. (ISO 2018a)
  • ISO 19650-2: Organization and Digitization of Information about Buildings and Civil Engineering Works, Including Building Information Modeling (BIM)-Information Management using Building Information Modeling. Part 2. (ISO 2018b).

4 Project BIM Requirements Development Process  

On a typical building or infrastructure construction project, the owner (also known as the Appointing Party in ISO 19650-2 (2018) develops Project BIM Requirements as part of the contract with the delivery team (also known as Appointed Parties within ISO 19650-2 (2018)). This standard for Project BIM Requirements defines the required topics to be included in Owner Project Requirements. See the Example Language resource for examples of Project BIM Requirements for each section of the standard. Owners may create a general Project BIM Requirements document that is used and referenced over a variety of projects. This standard for Project BIM Requirements can be used to define these generalized BIM requirements that owner publish prior to specific project contracting processes and are used as their organization’s standard.

5 Project BIM Requirements  

Each section of this standard for Project BIM Requirements contains: 1) Title of the requirement, and 2) Definition of the requirement. The standard is divided into three sections: Executive, Management, and Working/Technical.

5.1 EXECUTIVE  
5.1.1 Deliverables  
5.1.1.1 Required Deliverables

The Owner Project Requirements (OPR) shall identify all deliverables required by the Standard for Project BIM Requirements.

5.1.1.2 BIM Quality Plan

A BIM Quality Plan shall be documented in the Project BEP and could be incorporated or referenced in a Project Quality Plan. The OPR shall define when the BIM Quality Plan should be delivered and by which delivery team member(s). See: BIM Quality Plan

5.1.1.3 Security Plan Deliverable

If a Security Plan is not being provided to the delivery team member, then the OPR shall define when the Security Plan should be delivered and by which delivery team member(s) it should be delivered. See: Security

5.1.1.4 BIM Execution Plan (BEP) Deliverables

The OPR shall define when a Project BEP should be delivered and which delivery team member(s)should be involved in the development and delivery of the BEP (see BIM Execution Plan Module for details).

5.1.1.5 Model Deliverable(s)

The OPR shall specify the deliverable format for each BIM Use. For each Model Deliverable, the owner shall provide a Model Requirement (See: Model Requirements) expectation.

5.1.1.6 Data Deliverable(s)

The OPR shall specify the delivery format for any required data deliverable. Each data deliverable shall be delivered using either an industry standard format (e.g., COBie) or a format defined by the owner. (See: Data Requirements)

5.1.2 Quality Management Strategy  
5.1.2.1 BIM Quality Plan

The OPR shall direct the delivery team member(s) to follow the BIM Quality Plan provided by the owner. If no plan is provided the delivery team member(s) will provide a BIM Quality Plan. In both cases the delivery team member(s) shall document compliance with the BIM Quality Plan in the BEP.

5.1.2.2 Deliverable Quality

The OPR shall indicate all quality procedures that deliverables must conform with.

5.1.2.3 Verification / Validation Requirements

The OPR shall reference any verification / validation procedures that the owner will perform for quality checking of the deliverables.

5.1.2.4 Collaboration and Data Sharing

The OPR shall specify procedures for sharing and using documents pending quality approval and all parties shall identify areas of collaboration in the BIM Execution Plan.

5.1.3 Intellectual Property (IP) Rights  
5.1.3.1 Ownership

The OPR shall indicate the ownership of Intellectual Property (IP). If IP is defined in a contract, the OPR shall reference the contract.

5.1.3.2 Grant of License

The OPR shall indicate any licenses granted.

5.1.3.3 License Entitlements

The OPR shall indicate all entitlements granted by license to project team.

5.1.3.4 License Limitations

The OPR shall indicate any limitations of licenses granted to project team

5.1.3.5 Collaboration and Data Sharing

The OPR shall specify procedures for sharing and using IP-protected information and all parties shall identify areas of collaboration or information exchange in the BIM Execution Plan.

5.1.4 Security  
5.1.4.1 Data Separation

The OPR shall require all members of the delivery team to identify areas of collaboration (what data is shared) or data separation (what data is not shared) in the BEP.

5.1.4.2 Security and Cybersecurity

The OPR shall direct the delivery team member(s) to follow the security plan provided by the owner. If no plan is provided the delivery team member(s) will provide a security plan. In both cases the delivery team member(s) shall document compliance with the security plan in the BEP.

5.1.4.3 Data Storage Requirements

The OPR shall include the physical location, governance, provenance, and lineage needs regarding the data for the project. If the owner is not providing these requirements the delivery team member(s) shall be required to include these items in their Security Plan.

5.1.4.4 Continuation of Operations and Disaster Recovery

The OPR shall require the Security Plan to include continuation of operations and disaster recovery plans.

5.1.4.5 Use of Security Standards

The OPR shall indicate if the owner has security standards and how they will be employed on the project.

5.1.4.6 Security Restrictions

The requirements shall indicate if any working restrictions will be employed on the project.

5.1.4.7 Confidential, Controlled Unclassified, or Sensitive Information

The OPR shall indicate if confidential, controlled unclassified, or sensitive information will be present on the project. If there is confidential, controlled unclassified, or sensitive information present on the project, the information and its classification status shall be identified by the requirements.

5.1.5 Legal Considerations  
5.1.5.1 Contract Documents

The OPR shall indicate the order of precedence Model Deliverables hold in relationship to other contract documents.

5.1.5.2 BIM Standards

The OPR shall require the use of the owner’s BIM standards and requirements for the creation of all contract documents created using BIM workflows.

5.1.5.3 Waivers

The OPR shall specify how and under what conditions project teams can request waivers from use of the owner’s BIM Requirements or parts of the owner’s BIM Requirements. For a viable BIM-enabled project, the Deliverables defined in section 5.1.1 shall not be waived.

5.1.5.4 Responsibility for Product

The OPR shall include the expectation that contributors are responsible for their contribution.

5.1.5.5 Indemnification Clause

The OPR shall include an indemnification clause regarding damages due to shared BIM data.

5.2 Management  
5.2.1 BIM Execution Plan (BEP)  
5.2.1.1 Purpose of Document

The OPR shall include a description of why the BEP is required for the project.

5.2.1.2 Requirement of Use and Participation

The OPR shall require the delivery team to participate in the creation of the BEP and execute the process defined within.

5.2.1.3 Required Inclusions

The OPR shall indicate, or make reference to, all information that is required for inclusion in the BEP. The BEP required information can be referenced to either an industry standard format (e.g., BEP Standard, NBIMS US v.4) or a standard defined by the owner.

5.2.1.4 BEP Accountability

The OPR shall include mechanisms to hold accountable delivery team member(s) that fail to adhere to BEP requirements or the Project BEP deliverable.

5.2.1.5 BEP Deliverable Approval Process

The OPR shall define an approval process for how the owner will review and approve the BEP deliverables.

5.2.2 Roles & Responsibilities  
5.2.2.1 Required Documentation

The OPR shall require the delivery team to document roles and responsibilities of the team in the BEP. It shall also indicate which information about the Roles and Responsibilities should be included.

5.2.2.2 Defined Roles

The OPR shall include which BIM roles are required. For each BIM role required the OPR shall define the responsibilities.

5.2.3 Common Data Environment (CDE)  
5.2.3.1 Requirement for Participation

The OPR shall require the use of a CDE for the project.

5.2.3.2 Restrictions / Limitations

The OPR shall indicate any restrictions or limitations to the CDE.

5.2.3.3 Capabilities

The OPR shall indicate what functions a CDE shall be capable of performing. In the case that the owner is not capable of defining the capabilities, the delivery team shall be responsible for defining the capabilities of the CDE in the BEP.

5.2.3.4 Document Metadata

The OPR shall indicate specific metadata that shall be attached to documents stored within the CDE. In the case that the owner is not capable of defining the metadata, the delivery team shall be responsible for defining the metadata of the CDE in the BEP.

5.2.3.5 CDE Framework Documentation

The OPR shall require the CDE framework to be documented in the BEP if not provided by the owner. The OPR shall also indicate which party is responsible for the management of the CDE during the project.

5.2.4 Collaboration Requirements  
5.2.4.1 Specification of Collaboration Requirements

The OPR shall specify the owner’s collaboration requirements. Also, the OPR shall require the delivery team member(s) to specify any collaboration requirements.

5.2.4.2 Collaboration Procedures Documentation

The OPR shall require all collaboration procedures and meetings to be recorded in the BEP.

5.2.4.3 Information Exchange Procedures

The OPR shall specify procedures for sharing and using the following types of information:

5.2.4.4 Kick-Off Meeting

The OPR shall require delivery team member(s) to take part in a Kick-Off Meeting(s) for the purpose of gathering the information necessary to create the BEP.

5.2.4.5 Team Co-location

The OPR shall indicate if delivery team member(s) are required to co-locate on the project.

5.2.4.6 Coordination Meetings

The OPR shall require the delivery team to regularly meet to conduct BIM coordination and quality checks

5.2.4.7 Quality Control Activities

The OPR shall require that the delivery team member(s) must define and perform focused, scheduled quality checks throughout the project delivery process.

5.2.4.8 Required Quality Control Documentation

The OPR shall require the delivery team to document quality control activities of the team in the BEP.

5.2.4.9 Quality Control Report

The OPR shall require the delivery team member(s) to deliver a Quality Control Report (QCR) in conjunction with the delivery of any deliverable required.

5.2.4.10 Constructability Checks

If within the scope of the project, the OPR shall require the delivery team to conduct constructability reviews of their contributions prior to their submission.

5.2.4.11 Coordinate Design and Construction Checks

The OPR shall require the delivery team to coordinate models prior to their submission.

5.2.4.12 Model Integrity Checks

The OPR shall require the delivery team member(s) to conduct model integrity checks to ensure the model has no missing, undefined, incorrectly defined, or underdeveloped elements. The delivery team member(s) shall be required to document all elements in the QCR that are found to be noncompliant.

5.2.4.13 Metadata

The OPR shall require the delivery team to append metadata to all files stored in the CDE. The metadata shall be defined using either an industry standard format or a format defined by the owner or the Project Team.

5.2.4.14 Federated Model Checks

The OPR shall require that the delivery team is responsible for the review of the model(s) provided for federation. Federated model checks are used to ensure the model(s) have no misaligned or duplicated elements. The responsible party for the review should be defined in the BEP.

5.2.4.15 Data Compliance Checks

The OPR shall require the delivery team to conduct reviews of the data standards and their application to Model Deliverables and Data Deliverables. The delivery team member(s) shall be required to document all compliant/noncompliant elements in the QCR.

5.3 Working/Technical  
5.3.1 BIM Uses  
5.3.1.1 List of Required and Additional BIM Uses

The OPR shall state which BIM uses are required and which are optional for the delivery team member(s). [See BIM Use Definitions Standard, NBIMS-US v.4] The defined BIM Uses shall be required to be documented in the BEP.

5.3.2 Model Requirements (Finished Product)  
5.3.2.1 Model Element Breakdown (MEB)

The OPR shall include a list of all elements to be included in the scope of work and defined in the Model Element Table (MET) in the Project BEP. The MEB shall be organized using either an industry standard format or a format defined by the owner. The MEB shall be established by the owner as a template.

5.3.2.2 Model Progression Specification (MPS)

The OPR shall require the owner to provide a Model Progression Specification (MPS) to the delivery team that indicates the minimum desired Information accuracy and information detail of model elements for each milestone deliverable. Information accuracy and information detail can be defined using either an industry standard (eMVD or IDS) or a standard indicated by the owner.

5.3.3 Modeling Requirements (Creation Requirements)  
5.3.3.1 Owner Specific Requirements

If the owner has specific modeling requirements, the OPR shall indicate the Delivery Teams requirement to use them. These requirements shall include but are not limited to: Model Tolerances and Dimensioning, Structure of the Model, Naming conventions, Coordinate Systems, Linking and Referencing Procedures, Model Views, Data Schema (e.g. Shared Parameters, Item Types, etc.).

5.3.4 Data Requirements  
5.3.4.1 File Metadata

The OPR shall require all files and database sources stored in the Common Data Environment to include metadata using either an industry standard or a standard supplied by the owner.

5.3.4.2 Data Attribution Requirement

The OPR shall require that all delivery team members add data attributes to model elements in compliance with the Information Detail requirements.

5.3.4.3 Data Standard Reference

The OPR shall require that model objects include specific data attributes using either an industry standard or a data standard supplied by the owner. The requirements or the referenced standard shall clearly indicate which objects should carry data attributes and what data attributes shall be required on each model object type.

5.3.4.4 Inclusion in BIM Execution Plan

The OPR shall indicate that any deviation from provided standards should be documented within the BEP.

5.3.4.5 Existing Facilities Dataset

The OPR shall indicate if an existing dataset will be included in the owner furnished material provided to the delivery team. The existing dataset shall represent all existing assets relevant to the project and will include their data attributes and indicate the format of the provided materials.

Executive Summary

The National Institute of Building Sciences (NIBS) presents the Project BIM Requirements, a module of the BIMS-US™ V4 Standard, in an effort to define the elements required in a Building Information Management (BIM) supported construction project in the United States of America. NIBS defines Building Information Management (BIM) as the "functions of controlling the acquisition, analysis, retention, retrieval, and distribution of built environment asset information all within an information processing system." The Project BIM Requirements Standard establishes a comprehensive standard for owners outlining the requirements for achieving viable BIM implementation on construction projects - the use of BIM to achieve the objectives of an owner organization in capital projects, including processes, infrastructure, standards, and execution (as defined in NIBS’ National BIM Guide for Owners). This is intended to provide a framework for owners in crafting their Owner’s Project Requirements (OPR). The Project BIM Requirements can support an owner defining the BIM requirements for all stakeholders, ranging from designers to contractors. While this standard sets a baseline, owners are encouraged to expand requirements beyond the Project BIM Requirements to accommodate various unique and specific BIM uses on individual projects. NIBS’ goal in developing the Project BIM Requirements is to foster the creation of a standardized structure and content for project BIM requirements which can increase interorganizational compliance, enhancing nationwide standardization and establishing a minimum threshold for BIM-enabled projects. By aligning with this standard, owners can collectively achieve viable BIM projects that fulfill their goals while adhering to quality standards and conditions of satisfaction for BIM-enabled projects.

The Project BIM Requirements provides a structured list of requirements that owners need to define for specifying the oversight, creation, and management of BIM on a construction project. The divisions of the Project BIM Requirements are outlined below:

  1. Scope
  2. Terms and Definitions
  3. Reference Documents
  4. Project BIM Requirements Development Process
  5. Project BIM Requirements
    1. 5.1 - Executive
    2. 5.2 - Management
    3. 5.3 - Working/Technical

Authors and Contributors

A team of individuals within the National Institute of Building Sciences developed the Project BIM Standard. Principal authors of the Standard include:

  • Connor Christian, NBIMS Chair, Kiewit Building Group
  • Dr. Carrie Sturts Dossick, Planning Committee Liaison, University of Washington
  • Alireza Borhani Ph.D, Secretary, Former Graduate Research Assistant, MacDonald Miller
  • Daniel Dimitrov Ph.C, Graduate Research Assistant, University of Washington
  • Lisa Benjamin M.S., Graduate Research Assistant, University of Washington
  • Dr. Tammy McCuen, Member, Professor of Construction Science, University of Oklahoma
  • Brad Brown, member, Overtur, Allegion, PLC
  • Deke Smith, Member, DKS Information Consulting
  • Joaquim Nunes, Member, ENEL North America
  • Gary Younger, Member, Northeastern University
  • Joe Manganelli, Member, Xplr Design, Kent State University
  • Stephanie Sneary, Staff, National Institute of Building Sciences
  • Nicholas Nisbet, Member, AEC3 UK ltd

Acknowledgements

The research team would like to thank the planning committee and BIM Council Board of Directors for their support in the development of the Project BIM Requirements Standard. The team also wishes to thank the students at the University of Washington who have contributed to portions of this guide, as well as the industry members who have participated in surveys, interviews, and case studies related to the project.

  • Rachel Riopel, BOD Chair, HDR, Inc.
  • Dr. John Messner, NBIMS Chair, The Penn State University
  • Andrew Steele M.S., Graduate Research Assistant, University of Washington
  • Dr. Jennifer Lather, ASHRAE Liaison, Assistant Professor, University of Nebraska
  • Abe Morris, Observer, SSR
  • Chuck Hixon, Observer, Digital Construction Works
  • Dominique Fernandez, Staff, National Institute of Building Sciences
  • Roger Grant, Staff, National Institute of Building Sciences
  • Stephanie Sneary, Staff, National Institute of Building Sciences
  • Johnny Fortune, Staff, National Institute of Building Sciences
  • Robert Glover, Secretary, Barton Malow Builders
  • Russell Manning, PhD, LEED AP, CEFP, CRL, NIBS BOD Liaison, ICC
  • Paul Audlsley, Assoc. AIA, Member, NBBJ
  • Ivan Jaramillo, Member, Autodesk, Inc.
  • Frank Moore, Member, Autodesk, Inc.
  • Edmund Newman, Member, GSA
  • Andy Smith, Member, Bentley Systems
  • Van Woods, Member, U.S. Army Corps of Engineers (USACE)

0.) What are Project BIM Requirements?

As the industry develops Building Information Management (BIM) for planning, design, construction, and operations, there is a need for owner organizations to document the expectations for BIM Uses on a project. To do this, owners can document these expectations in Project BIM Requirements that is often incorporated into the Owner Project Requirements (OPR) documentation.

There are two types of BIM requirements that an owner organization may define: 1) An owner organization’s Organizational BIM requirements standard and 2) A project specific BIM Requirements document (See Figure 1). This Project BIM Requirements Standard applies to both types of requirements. First, if an owner organization has a capital project portfolio with repeated construction projects, it is recommended that the owner organization develop a comprehensive standard for their organization's BIM Requirements. This can incorporate their data needs for operations and maintenance as well as create standards for project management during planning, design, and construction activities. Second, an owner organization will want to include Project BIM Requirements when developing project specific requirements documents. If the owner organization has an Organizational BIM Requirements Standard, they can use it as the basis for the Project BIM Requirements document(s). An owner who does not do construction routinely should develop a Project BIM Requirements document as part of the contract and this Standard, Guideline, and the Example Language can all support the owner in authoring Project BIM Requirements. See the Template and Example Language for supporting materials in the resources section. Also see the ANSI/ASHRAE/NIBS Standard 224-2023 Standard Application of Building Information Modeling as a basis for what an owner should do to develop Organizational and BIM Requirements. See below for more information on Standard 224-2023.

Figure 1. Info graphic displaying three levels of BIM requirements. Top level is named NBIMS and lists the Project BIM Standard. Second level is named Owner Organization and lists Owner General BIM Requirements. Third level is named Project and lists Project BIM Requirements and Owner Project Requirements (OPR)


Figure 1. The types of BIM Requirements documents and their relationships

The Project BIM Requirements defined in this standard relates to other NBIMS modules in that it sets the basis for what needs to be defined to achieve a BIM-enabled project (See Figure 2). Once an owner defines the Project BIM Requirements, the project team then develops BIM Execution Plan(s) to define appropriate model uses, responsibilities, and processes. The project team can use the BIM Uses Definitions to define their preferred BIM Uses. An owner can use the COBie Standard to define the Data Deliverable exchange structures and requirements.

The Project BIM Requirements are also closely related to the new ANSI/ASHRAE/NIBS Standard 224-2023 Standard Application of Building Information Modeling. Both the Project BIM Requirements and the Standard 224-2023 originate from the National BIM Guide for Owners. Standard 224-2023 was developed by a joint ASHRAE NIBS Committee that took the National BIM Guide for Owners and converted it into an ANSI level standard. Standard 224-2023 is specifically for owners to identify requirements for implementing BIM on projects for the owner and the project team. Standard 224-2023 is targeted at providing the minimum requirements for the application of building information modeling/management (BIM) to the planning, design, construction, and operation of facilities, including both buildings and infrastructure. In so doing, it references NBIMS for further direction on implementation. Standard 224-2023 defines how to incorporate BIM requirements as identified in the NBIMS Project BIM Requirements in owners’ design, construction, and operations services contracts.

These standards were developed in parallel. As a result, some coordination in their alignment may still be required and will be addressed in subsequent versions of the standards and supporting guidelines as both become available and are used in practice.

Infographic listing the modules and standards for NBIMS-US; first BIM Process and Requirements Modules which lists Project BIM Requirements, BEP Standard, and BIM Use Definitions, next the Information Exchange Module which lists COBie. Finally, ASHRAE/NIBS 224 is listed as the Standard.


Figure 2. NBIMS-US Modules and Standards

1.) Overview of the Project BIM Requirements Standard

Mission/Scope:

The mission of the National Institute of Building Sciences (NIBS) BIMS-US V4 is to develop a BIM Requirements Standard that defines the required elements that should be specified for a viable BIM-enabled construction project and that the owner should include in the Owner’s Project Requirements (OPR). It is intended for an owner to use the PBR Standard to define Project BIM Requirements for delivery team members including designers and builders (referenced in this document as the delivery team). Owners may extend requirements beyond the scope of this standard to include other BIM Uses.

On a typical building or infrastructure construction project, the owner (also known as the Appointing Party in ISO 19650-2 (2018)) develops Project BIM Requirements as part of the contract with the delivery team (also known as Appointed Parties within ISO 19650-2 (2018)). This Project BIM Requirements Standard defines the required elements to be included in Owner Project Requirements (OPR). See the Template and Example Language for examples of Project BIM Requirements for each section of this standard. Owners may create an Organizational Project BIM Requirements document that is used and referenced over a variety of projects. This Project BIM Requirements Standard can be used to define these generalized BIM requirements that owners publish prior to specific project contracting processes and are used as their organization’s standard.

What is Building Information Management and what will this standard help an Organization Achieve?

The National Institute of Building Sciences defines Building Information Management (BIM) as the "functions of controlling the acquisition, analysis, retention, retrieval, and distribution of built environment asset information all within an information processing system." This Project BIM Requirements Standard aims to outline the requirements of a BIM project while achieving the highest levels of quality and conformance to the proper conditions of satisfaction. Therein, the Project BIM Requirements Standard will ensure that all BIM model(s) and element(s) shall be created to a level of completeness and quality as required to perform an analysis appropriate for the given stage and requirements. In other words, quality should be delivered parallel to and/or aligned within other processes while following this standard.

Furthermore, using this standard across the industry will support consistency across the sector. This standard sets up expectations as to what should be addressed in a Project BIM Requirements document so that all parties, the owner and the delivery team members, have shared understanding around the expectations for BIM oversight, management, and delivery.

What is a "Viable BIM"?

The National Institute of Building Sciences defines viable BIM as: the use of BIM to achieve the objectives of an owner organization in capital projects, including processes, infrastructure, standards, and execution. (National BIM Guide for Owners) This supports the project team in the planning, design, construction, and operations of built environment assets.

2.) How to use the Project BIM Requirements Standard

This section of the Project BIM Requirements Guidelines focuses on how to use the Project BIM Requirements Standard, including a description of the document structure, the divisions within it, and the ways information is organized. The Project BIM Requirements Standard describes the required elements for defining BIM requirements that an owner would include in the OPR, therefore an overview of the document layout and structure is critical.

Document Structure:

The Project BIM Requirements Standard is broken down into 5 sections, beginning with a brief description of scope, followed by terms and definitions, reference documents, and an overview of the project BIM requirements development process.

  1. Scope
  2. Terms and Definitions
  3. Reference Documents
  4. Project BIM Requirements Development Process
  5. Project BIM Requirements:
    1. 5.1 - Executive
    2. 5.2 - Management
    3. 5.3 - Working/Technical

Beyond sections 1-4, the Standard is divided into three major sections that define the scope of the individual requirements within each section. These divisions were developed based on ISO 12911 which defines three levels: Executive, Management, and Working/Technical. The Project BIM Requirements Standard’s divisions mirror that of ISO 12911. These sections are described below:

  1. Executive: The Executive level is meant to define the broader outcomes of a BIM-enabled project. This section includes deliverables, quality management strategy, Intellectual property (IP) rights, security, and legal considerations.
  2. Management: The Management level describes the controls and management processes and oversight necessary for a BIM-enabled project. This section includes the BIM Execution Plan (BEP), Roles and Responsibilities, Common Data Environment (CDE), and collaboration requirements.
  3. Working/Technical: The Working/Technical level describes the technical requirements and inputs necessary for a BIM-enabled project. This section includes BIM Uses, Model Requirements (finished product), Modeling Requirements (creation requirements), and Data Requirements.

Within each of the three above sections are the minimum BIM requirements that an owner would include as part of the OPR. Each of the three sections contains unique requirements that when sufficiently addressed can provide the basis for a viable BIM-enabled construction project. Each of the three major categorical divisions are further broken down into smaller sections containing individual project BIM Requirements. These sub-divisions are briefly described below:

  1. Division - 5.1 Executive:
       5.1.1 Deliverables
       5.1.2 Quality Management Strategy
       5.1.3 Intellectual Property (IP) Rights
       5.1.4 Security
       5.1.5 Legal Considerations

  2. Division - 5.2 Management:
       5.2.1 BIM Execution Plan (BEP)
       5.2.2 Roles and Responsibilities
       5.2.3 Common Data Environment (CDE)
       5.2.4 Collaboration Requirements

  3. Division - 5.3 Working/Technical:
       5.3.1 BIM Uses
       5.3.2 Model Requirements (Finished Product)
       5.3.3 Modeling Requirements (Creation Requirements)
       5.3.4 Data Requirements

Within each sub-division of sections 5.1, 5.2, and 5.3 exist the individual elements which compose the body of the Project BIM Requirements Standard. Each individual element within the above sections contains:

  1. Title of the requirement
  2. Definition of the requirement

An example is provided below of the requirements structure from section 5.2.4.6, within the Collaboration Requirements (5.2.4) of the Management (5.2) section.

5.2.4.6: Coordination Meetings

The OPR shall require the Delivery Team to regularly meet to conduct BIM coordination and quality checks.

An owner seeking to create an Organizational Project BIM Requirements document that may be used or referenced over a variety of projects can then tailor their individual organization and its unique operations around each requirement within the Project BIM Requirements Standard. Using the example above, 5.2.4.6 Collaboration Meetings, an owner would be aware of the requirement to have regular BIM coordination meetings and quality checks throughout the project and may tailor this requirement to their unique organization and include it in their OPR. As described above, following the Project BIM Standard document can then lead to a standardized Organizational Project BIM Requirements document which can be applied to all BIM projects. This can then be further tailored to specific projects and their unique BIM requirements to create individual project specific BIM requirements.

3.) Development Process of the Project BIM Requirements Standard

The workgroup with the support of the University of Washington team reviewed existing standards (national, international, state, local) that define BIM project requirements and developed an interim report to support the development of this Project BIM Requirements language. This included example language from the existing standards. This workgroup then developed the candidate module language for ballot.

The development process for the Project BIM Requirements Standard was a collaborative effort between the NIBS workgroup and a research team at the University of Washington. An extensive literature review was conducted of existing BIM standards and guidelines in an effort to produce the Project BIM Requirements Standard. This effort included the review and assessment of each of these individual standards to ensure that the NBIMS Project BIM Standard is in conformance with each preceding existing BIM standardization and guideline document. This included an extensive qualitative coding procedure in which requirements from each existing standard were coded for similarity and overlap in content. Multiple iterations of coding went into this effort to ensure conformance and interoperability with existing standards both nationwide and internationally. The standards and guidelines which were reviewed during the development process of the Project BIM Requirements Standard are listed below.

Reviewed Documents
AEC (UK) BIM Protocol Project BIM Execution Plan, Version 2.0, 2012
A Guide for Validating and Checking BIM Submittals, Version 10, Massachusetts Port Authority, 2019
A Guide to BIM & VDC on TAA Projects, Massachusetts Port Authority, 2020
AIA Document G203TM – 2023, BIM Execution Plan
AIA Document E203TM – 2023, BIM and Digital Data Exhibit for Broadly Sharing BIM with Project
Appendix A. MPA BIM Uses, Massachusetts Port Authority, 2015
Australia and New Zealand BIM Best Practices Guidelines, NZIQS, 2018
BIM Guidelines for Vertical and Horizontal Construction, Version 1.2, Massachusetts Port Authority, 2015
BIM Essential Guide for BIM Execution Plan, Building and Construction Authority, 2013
BIM User Guide, Version 1.0.6, The Pennsylvania State University, 2019
BIM Execution Plan Standard Version 4, U.S. National BIM Standard, 2023
BIM Use Definitions Standard Version 4, U.S. National BIM Standard, 2023
BIM Standards, Northeastern University, 2020
BIM Guidelines, Version 5, Smithsonian Facilities, 2021
BIM Particular Conditions, Version 2, Building and Construction Authority, 2015
Building Information Management (BIM) Employer’s Information Requirements, Version 2.0, Rail Baltica, 2018
Building Information Modeling (BIM) Management Requirements, Agency BIM Program, 2021, Department of State, Bureau of Overseas Building Operations
Building Information Modeling (BIM) Universal Addendum, Version 3.2, The Penn State University, 2017
Building Information Modeling (BIM) Protocol, Second Edition, Construction Industry Council, 2018
Building Information Modelling (BIM) for Transport and Main Roads, DTMR, 2017
Building Information Modelling for Asset Management (BIM-AM) Standards and Guidelines, version 2.0, EMSD, 2019
Building Information Modeling Standards (BIMs), Version 2.0, TN OSA, 2020
ANSI/ASHRAE/NIBS 224-2023, Standard for the Application of Building Information Modeling, 2023
COBie, Version 4, U.S. National BIM Standard, 2023
Common BIM Requirements 2012, series 1-13, BuildingSMART, 2012
Digital Facilities and Infrastructure Design Standards Manual, Denver International Airport, 2020
E/A Design Division BIM Standard, Version 3.0, The Port Authority of NY & NJ, 2019
Information Management according to BS EN ISO 19650, Guidance Part 1: Concepts, 2nd Edition, UK BIM Alliance, 2019
Information Management according to BS EN ISO 19650, Guidance Part 2: Parties, teams and processes for the delivery phase of the assets, 5th Edition, UK BIM Framework, 2019
Information Management according to BS EN ISO 19650, Guidance Part 3: Operational phase of the asset life-cycle, 1st Edition, UK BIM Framework, 2020
Information Management according to BS EN ISO 19650, Guidance Part A-F, 1st Edition, UK BIM Framework, 2020
ISO 19650-1, Part 1: Concepts and Principles, 1st Edition, ISO, 2018
ISO 19650-2, Part 2: Delivery Phase of the Assets, 1st Edition, ISO, 2018
GSA Building Information Modeling (BIM) Guide 07, Version 1, U.S. General Services Administration, 2016
DoD MHS Minimum BIM Requirements, Version 2.2, United States Department of Defense, 2020
VA BIM Standard, BIM Manual Version 2.2, U.S. Department of Veterans Affairs, 2017
HRSD Building Information Model (BIM) Requirements, Section 7, HRSD, 2020
National BIM Guide for Owners, National Institute of Building Sciences, 2017
NASA Building Information Modeling Scope of Services and Requirements for Architects and Engineers, Version 1, NASA, 2020
National Guidelines for Digital Modelling, CRC Construction Innovation, 2009
NATSPEC National BIM Guide, Version 1.0, NATSPEC, 2016
NATSPEC BIM Project Inception Guide, Version 1.0, NATSPEC, 2014
NATSPEC BIM Paper - BIM and LOD, Version 1.0, NATSPEC, 2013
Singapore BIM Guide, Version 2, Building and Construction Authority, 2013
UDOT Model Development Standards Manual, UDOT, 2020
USACE Advanced Modeling Project Execution Plan, Version 4.0, USACE, 2020
Unified Facilities Guide Specifications, Section 01 33 16.00 10, USACE, 2015

With the review in hand, the members of the workgroup established a table of contents, determined the elements, defined these elements, and compiled example and template language. These were systematically reviewed line by line by the workgroup over a series of meetings over a period of 9 months.

4.) Comparison of the Project BIM Requirements Standard with ISO 19650

The ISO 19650 Standard is an international standard for managing information over the lifecycle of a built asset using Building Information Management (BIM). The development of the Project BIM Standard was done following an extensive review and analysis of the ISO 19650 document series in order to ensure compliance between the standards. This section will review how following the Project BIM Standard will ensure alignment with ISO 19650 and provide a detailed overview of both standards and where alignment between them can be found.

The largest difference between these standards lies in the fact that ISO 19650 provides a standard for managing information over the entire lifecycle of a built asset using BIM, while the Project BIM Standard focuses specifically on the delivery phase of the build asset’s life cycle. The ISO 19650 Standard is separated into 5 sections which individually focus on a particular life-cycle phase of a built asset. ISO 19650-1: Concepts and Principles, ISO 19650-2: Delivery Phase of the Assets, and ISO 19650-5: Security-minded approach to information management are where the Project BIM Standard and the ISO 19650 Standard overlap most optimally in content and goal, with the majority of alignment present in ISO 19650-2. Below is a detailed overview of the alignment between the Project BIM Standard and the ISO 19650 document series separated by sections within the Project BIM Standard. This begins with the Executive section of requirements, followed by the Management and Working/Technical section of requirements. For each individual Project BIM Standard requirement, the section of ISO alignment is listed along with a brief explanation of alignment.

Infographic of Mapping BIM requirements over the project lifecycle defined in ISO 19650-2- starting with the Procure phase are Assessment and Need, Invitation to Tender, and Tender Response; next the Information Planning Phase includes Appointment and Mobilization; finally Information Production Phase includes Collaborative Production of Information, Information Model Delivery, and finally Project Close-out.


Figure 3. Map of the Project BIM Requirements over the project life cycle as defined in the ISO 19650 Standard

5.1 Executive
Project BIM Standard ISO Alignment Brief Explanation
5.1 Executive
5.1.1 Deliverables
5.1.1.1 Required Deliverables

ISO 19650-2: 5.1.4 Establish the project’s information standard

ISO 19650-2: 5.2.1 Establish the appointing party’s exchange information requirements

ISO 19650-2: 5.4.3 Establish the lead appointed party’s exchange information requirements, b-c

ISO 19650 and the BIM Standard require specific and standardized information requirements. However, ISO's project information standard, exchange information requirements, and information delivery strategy serve as umbrella categorical requirements within which the BIM Standards’ specific deliverable requirements are addressed.
5.1.1.2 BIM Quality Plan
5.1.1.3 Security Plan Deliverable
5.1.1.4 BIM Execution Plan (BEP) Deliverable
5.1.1.5 Model Deliverable(s)
5.1.1.6 Data Deliverable(s)
Project BIM Standard ISO Alignment Brief Explanation
5.1 Executive
5.1.2 Quality Management Strategy
5.1.2.1 BIM Quality Plan

ISO 19650-1: 6.3.3 Information verification and validation
ISO 19650-2: 5.4.3 Establish the lead appointed party's exchange information requirements, c
ISO 19650-2: 5.4.5 Establish the master information delivery plan

ISO 19650 and the Project BIM Standard require that a quality plan be developed and followed on BIM-enabled projects. Procedures to ensure quality are set and followed on projects.
5.1.2.2 Deliverable Quality ISO 19650-2: 5.2.1 Establish the appointing party's exchange information requirements, c-d ISO 19650 specifies that the acceptance criteria for each information requirement must be established in addition to all supportive information that the prospective lead Appointed Party might need. This aligns with the Project BIM Standard's requirement to establish all quality procedures that deliverables shall conform with.
5.1.2.3 Verification/Validation Requirements

ISO 19650-2: 5.3.3 Assess task team capability and capacity< br /> ISO 19650-2: 5.6.3 Undertake quality assurance check
ISO 19650-2: 5.6.4 Review information and approve for sharing

ISO 19650 specifies procedures in assessing team capacity and capability in addition to quality assurance check requirements and a mandatory review of information before an approval for sharing. These align with the Project BIM Standard’s requirement for verification/validation procedures on a BIM-enabled project.
5.1.2.4 Collaboration and Data Sharing

ISO 19650-2: 5.6 Information management process — Collaborative production of information
ISO 19650-2: 5.6.6 Activities for collaborative production of information
ISO 19650-1: 9. Information container-based collaborative working

Both ISO 19650 and the Project BIM Standard specify the requirement to develop procedures for sharing and using documents pending quality approval activities. In addition, both specify areas of collaboration and standards for the use of shared documentation.
Project BIM Standard ISO Alignment Brief Explanation
5.1 Executive
5.1.3 Intellectual Property (IP) Rights
5.1.3.1 Ownership

ISO 19650-1: 9 Information container-based collaborative working

ISO 19650-2 5.1.8 Establish the project’s information protocol

Within ISO 19650-2 5.1.8 Establish the project’s information protocol, ISO addresses the intellectual property rights information in a more umbrella statement. The BIM Standard goes into more detail and specificity in the area of intellectual property rights. However, similar requirements are addressed by both standards around licensing, IP rights, and collaboration.

5.1.3.2 Grant of License
5.1.3.3 License Entitlements
5.1.3.4 License Limitations
5.1.3.5 Collaboration and Data Sharing
Project BIM Standard ISO Alignment Brief Explanation
5.1 Executive
5.1.4 Security
5.1.4.1 Data Separation ISO 19650-1: 9. Information container-based collaborative working, a,f In ISO 19650-1: 9 Information container-based collaborative working, requirements around sharing and managing data are outlined. Similar to the Project BIM Standard, this requirement helps to identify areas of collaboration and data separation.
5.1.4.2 Security and Cybersecurity

ISO 19650-5: 7 Developing a security management plan< br /> ISO 19650-5: 7.5 Monitoring and Auditing, 7.5.1
ISO 19650-2: 5.3.6 Establish the delivery team’s risk register

Both ISO 19650 and the Project BIM Standard require team members to follow a security plan provided by the owner and ensure compliance to the security management plan.
5.1.4.3 Data Storage Requirements

ISO 19650-5: B.4 Information security
ISO 19650-5: 6.3 Developing risk mitigation measures, 6.3.2

ISO 19650 and the Project BIM Standard emphasize the requirement that the organization(s) must consider personnel, physical, and technical security controls and requirements around the management of information.
5.1.4.4 Continuation of Operations and Disaster Recovery ISO 19650-5: 8.1-8.4 Developing a security breach/incident management plan Both ISO 19650 and the Project BIM Standard outline the requirement to develop procedures for the continuation of operations and disaster recovery plans.

5.1.4.5 Use of Security Standards ISO 19650-5: 7. Developing a security management plan, 7.1.3 Both ISO 19650 and the Project BIM Standard require the use of security standards on BIM-enabled projects.
5.1.4.6 Security Restrictions ISO 19650-5: 7.3 Logistical security, 7.3.1 Both ISO 19650 and the Project BIM Standard contain the requirement to indicate if any working restrictions will be employed on the project around issues such as sensitive assets.
5.1.4.7 Confidential, Controlled Unclassified, or Sensitive Information ISO 19650-5: 7 Developing a security management plan, 7.1.3 c Both ISO 19650 and the Project BIM Standard contain security information requirements detailing sensitive information and policies around its use, distribution, etc.
Project BIM Standard ISO Alignment Brief Explanation
5.1 Executive
5.1.5 Legal Considerations
5.1.5.1 Contract Documents

ISO 19650-2: 5.4.6 Complete lead appointed party's appointment documents

ISO 19650-2: 5.4.7 Complete appointed party's appointment documents

ISO19650 and the Project BIM Standard address the contract documents and requirements. ISO 19650 mentions information exchange requirements specifically, while the Project BIM Standard references the owner’s BIM Standard.
5.1.5.2 BIM Standards
5.1.3.3 Waivers ISO 19650-2: 5.3.2 Establish the delivery team’s (pre-appointment) BIM execution plan, e ISO 19650 and the Project BIM Standard have procedures around any proposed additions or amendments to the project Bim requirements.
5.1.5.4 Responsibility for Product ISO 19650-2: 5.4.2 Establish detailed responsibility matrix ISO 19650 and the Project BIM Standard include expectations that contributors are responsible for their contributions to the project. In ISO 19650 this comes in the form of a detailed responsibility matrix.
5.1.5.5 Indemnification Clause ISO 19650-1: 10.1 Information Delivery Planning- Principles Although an indemnification clause is not explicitly outlined in ISO 19650, ISO sets out strict rules around the structure and delivery of information in order to address indemnification in case of errors in shared data.
5.2 Management
Project BIM Standard ISO Alignment Brief Explanation
5.2 Management
5.2.1 BIM Execution Plan (BEP)
5.2.1.1 Purpose of Document ISO 19650-1: 6.3.1 General Principles ISO 19650 and the Project BIM Standard address why a BEP is required and describe the purpose behind its requirement.
5.2.1.2 Requirement of Use and Participation ISO 19650-2: 5.3.2 Establish the delivery team’s (pre-appointment) BIM execution plan, a-g Both ISO 19650 and the Project BIM Standard contain requirements around the use and participation of a BIM Execution Plan and require that the OPR references all information that must be included in the BEP.
5.2.1.3 Required Inclusions
5.2.1.4 BEP Accountability

ISO 19650-2: 5.3.3 Assess task team capability and capacity
ISO 19650-2: 5.3.4 Establish the delivery team’s capability and capacity
ISO 19650-2: 5.4.2 Establish the delivery team’s detailed responsibility matrix

Both ISO 19650 and the Project BIM Standard contain requirements to include mechanisms to hold delivery team members accountable. ISO 19650 contains requirements around the use of a detailed responsibility matrix as well as assessments of individual capabilities and capacities during the formation of delivery groups.
5.2.1.5 BEP Deliverable Approval Process

ISO 19650-2: 5.6.3 Undertake quality assurance check
ISO 19650-2: 5.6.4 Review information and approve for sharing

Both ISO 19650 and the Project BIM Standard require the inclusion of an approval process for deliverables to ensure quality, accuracy, and conformance.
Project BIM Standard ISO Alignment Brief Explanation
5.2 Management
5.2.2 Roles and Responsibilities
5.2.2.1 Required Documentation

ISO 19650-2: 5.4.2 Establish the delivery team’s detailed responsibility matrix
ISO 19650-2: 5.3.4 Establish the delivery team’s capability and capacity

ISO 19650 and the Project BIM Standard require the delivery team to document roles/responsibilities of the team in order to ensure accountability and reliability. In ISO 19650, this comes in the form of assessing the delivery team’s capability and capacity, and developing a detailed responsibility matrix.
5.2.2.2 Defined Roles

ISO 19650-2: 5.4.2 Establish the delivery team’s detailed responsibility matrix
ISO 19650-2: 5.4.1 Confirm the delivery team’s BIM execution plan

ISO 19650 and the Project BIM Standard include the requirement to outline BIM roles and define responsibilities within the OPR as to what information is to be produced, who is responsible for its production, who it is to be exchanged with, etc.
Project BIM Standard ISO Alignment Brief Explanation
5.2 Management
5.2.3 Common Data Environment
5.2.3.1 Requirement for Participation ISO 19650-2: 5.1.7 Establish the project’s common data environment Both ISO 19650 and the Project BIM Standard require the use of a common data environment on all BIM projects.
5.2.3.2 Restrictions/Limitations ISO 19650-1: 12.1 Principles ISO 19650 and the project BIM Standard address the restrictions and complexities of a CDE workflow and its use in an active organization.
5.2.3.3 Capabilities ISO 19650-2: 5.1.7 Establish the project’s common data environment Both ISO 19650 and the Project BIM Standard require that the OPR indicate the functions a CDE shall be capable of performing.
5.2.3.4 Document Metadata ISO 19650-2: 5.1.7 Establish the project’s common data environment, b-c ISO 19650-2: 5.1.7 requires that each information container has a unique ID based upon an agreed upon and documented convention, each field is assigned a value from an agreed and documented codification standard, and each information container contain specific assigned attributes, similar to the document metadata requirement in the Project BIM Standard.
5.2.3.5 CDE Framework Documentation

ISO 19650-2: 5.1.7 Establish the project’s common data environment
ISO 19650-1: 12.1 Principles

ISO 19650 and the Project BIM Standard require that a CDE framework/workflow be used and documented to manage the project.
Project BIM Standard ISO Alignment Brief Explanation
5.2 Management
5.2.4 Collaboration Requirements
5.2.4.10 Constructability Checks ISO 19650-2: 5.6.5 Information model review Although ISO 19650 does not specifically require constructability checks, both ISO 19650 and the Project BIM Standard require the delivery team to undertake a review of all models before sharing in accordance with the project's production methods and procedures.
5.2.4.11 Coordinate Design and Construction Checks ISO 19650-2: 5.6.5 Information model review Both ISO 19650 and the Project BIM Standard require the delivery team to coordinate models prior to their submission. In ISO 19650 this facilitates the continuous coordination of information across each element of the information model.
5.2.4.12 Model Integrity Checks

ISO 19650-2: 5.6.5 Information model review
ISO 19650-1: 12.3 The check/review/approve transition

Both ISO 19650 and the Project BIM Standard require the delivery team member(s) to conduct checks to ensure the model has no missing, undefined, incorrectly defined, or underdeveloped elements. In ISO 19650, this takes the form of the information model review process and the check/review/approve transition procedure.
5.2.4.13 Metadata ISO 19650-2: 5.1.7 Establish the project’s common data environment, b-c. ISO 19650-2: 5.1.7 requires that each information container has a unique ID based on an agreed upon and documented convention, each field is assigned a value from an agreed and documented codification standard, and each information container contain specific assigned attributes, similar to the document metadata requirement in the Project BIM Standard.
5.2.4.14 Federated Model Checks

ISO 19650-2: 5.3.2 Establish the delivery team’s (pre-appointment) BIM execution plan, c.
ISO 19650-1: 12.3 The check/review/approve transition
ISO 19650-1: 10.4 Defining the federation strategy and breakdown structure for information containers

In ISO 19650-2: 5.3.2, it is required that the prospective lead Appointed Party considers the proposed federation strategy in the project BEP that is adopted by the delivery team which can be defined in ISO 19650-1: 10.4. In addition to the check/review/approve transition process in ISO 19650-2, alignment between the Project BIM Standard's federated model checks deliverable, and ISO 19650 is present.
5.2.4.15 Data Compliance Checks

ISO 19650-2: 5.6.2 Generate information, a
ISO 19650-2: 5.6.3 Undertake quality assurance check

ISO 19650 and the Project BIM Standard require the delivery team to conduct reviews of the data standards and their application to Model Deliverables and Data Deliverables. In ISO 19650, this comes in the form of multiple iterations of quality assurance checks before information is approved for sharing.
5.3 Working/Technical
Project BIM Standard ISO Alignment Brief Explanation
5.3 Working/Technical
5.3.1 BIM Uses
5.3.1.1 List of Required and Additional BIM Uses

ISO 19650-1: 7.3 Project information management functions
ISO 19650-2: 5.1.4 Establish the project’s information standard

ISO 19650 and the Project BIM Standard require that required BIM Uses be established and outlined as part of the project. If unique BIM Uses will be employed on an individual project, the Appointing Party allocates responsibility for the delivery of information to the lead appointed parties as appropriate.
Project BIM Standard ISO Alignment Brief Explanation
5.3 Working/Technical
5.3.2 Model Requirements (Finished Product)
5.3.2.1 Model Element Breakdown (MEB) ISO 19650-2: 5.3.2 Establish the delivery team's (pre-appointment) BIM execution plan, d Although ISO 19650 does not specifically require the addition of a model element breakdown table, it does require that the prospective lead Appointed Party shall consider the delivery team’s high-level responsibility matrix, containing the allocated responsibility for each element of the information model and the key deliverables associated to each element.
5.3.2.2 Model Progression Specification (MPS)

ISO 19650-1: 12.2 The work in progress state
12.3 The check/review/approve transition

Although ISO 19650 does not specifically require an MPS, the work in progress state and check/review/approve transition complies to the requirements of an MPS by comparing the information container against the information delivery plan and against the agreed standards, methods, and procedures for producing information.
Project BIM Standard ISO Alignment Brief Explanation
5.3 Working/Technical
5.3.3 Model Requirements (creation Requirements
5.3.3.1 Owner Specification Requirements ISO 19650-2: 5.2.1 Establish the appointing party's exchange information requirements, c ISO 19650 and the Project BIM Standard require the establishment of the acceptance criteria for each information requirement. If the criteria is unique to an owner, then those standards are to be used on the project.
Project BIM Standard ISO Alignment Brief Explanation
5.3 Working/Technical
5.3.4 Data Requirements
5.3.4.1 File Metadata ISO 19650-2: 5.1.7 Establish the project’s common data environment, c ISO 19650-2: 5.1.7 requires that each information container has a unique ID based upon an agreed upon and documented convention, each field is assigned a value from an agreed and documented codification standard, and each information container contain specific assigned attributes, similar to the file metadata requirement in the Project BIM Standard.
5.3.4.2 Data Attribution Requirement
5.3.4.3 Data Standard Reference
5.3.4.4 Inclusion in BIM Execution Plan ISO 19650-2: 5.4.1 Confirm the delivery team’s BIM execution plan, d-e ISO 19650-2: 5.4.1 d-e state that the lead Appointed Party must confirm and document the delivery team's proposed information production methods and procedures, and agree with the Appointing Party any additions or amendments to the project’s information standard. This is in alignment with the Project BIM Standards Inclusion in BIM Execution Plan requirement.
5.3.4.5 Existing Facilities Dataset ISO 19650-2: 5.8.1 Archive the project information model Both ISO 19650 and the Project BIM Standard require that an existing dataset be included (if one exists) in the owner furnished material and passed on to operational groups.
Title Description  
Template and Example Lanugage The Template and Example Language document provides a template for project teams to use to develop project-specific requirement information. It also provides examples of information that would be inclulded for any given project. Download