Instructions: G203™–2022, BIM Execution Plan

Synopsis. 

AIA Document G203™–2022 is a framework from which Project Participants can create a Project-specific BIM Execution Plan. In this regard, G203-2022 contains multiple fill points and is intended to stimulate conversations and document decisions surrounding how the Project Participants will utilize BIM on their Project. All of the BIM exhibits contain language requiring the Parties to adhere to BIM Execution Plan. Although the BIM Execution Plan is not intended to be a contract exhibit, Parties are contractually obligated to adhere to its terms. G203-2022 is intended to be used in conjunction with a BIM exhibit, such as AIA Document E201-2022, E202-2022, E401-2022, or E402-2022. 

For all document details, see the summary »

Changes from the Previous Version. 

AIA Document G203-2022 is the indirect successor document to G202–2013 with many changes, as explained below and in the Digital Practice Documents Guide

Completing G203–2022.

Cover Page

BIM Execution Plan Version Number. Identify the version number of the BIM Execution Plan. Since the project BIM Execution Plan is intended to evolve throughout the project, this section allows the parties to identify the most recent BIM Execution Plan by version number.

Date. The date represents the date the BIM Execution Plan becomes effective.

Project Name. Identify the project by name and location.

Project Owner. Identify the project owner by name and address.

Exhibit Name. The BIM Execution Plan is intended to be used in correlation with a BIM exhibit, such as the E201-2022, E202-2022, E401-2022, or E402-2022. Therefore, in this fill point the parties can identify the BIM exhibit agreed to by the project participants.

Intended Goals for Models on the Project. Summarize the intended goals for models on the project, including model documentation, process, and workflow.

Article 1   General Provisions

Table 1.1, when completed, provides a complete listing of the project participants that are developing or using models on the project. It is incumbent on the project participants to keep this table updated and to issue revisions as each new project participant is added. The following is an example of how this table may be filled out:

Project Participant
(Firm or company name) 

Discipline or Trade 

Contact Name
(Insert individual name and Project role or title) 

Contact Information 

(Insert phone number, email address, and other contact information) 

Smith Associates

Architecture

Bill Jones, Project Architect

Email:  bill@smithassociates.com

Phone: (###) ###-####

 

  • 1.2 Project Schedule. The project schedule attached to the BEP should be coordinated and consistent with the schedule(s) listed in the project participants’ respective agreements. However, the schedule in the BEP should also include detail relative to the development of BIM for the project, including model portion designated delivery milestones for collaboration and coordination, and final delivery dates for each project milestone. Parties may use any format to develop project schedules that clearly memorialize the key dates related to the development of all model portions for the project. The schedule should be updated to reflect changes in the overall project schedule and to incorporate input from new project participants as they are added to the table in Section 1.1. Each revision to the referenced schedule should be published in an updated BEP with a new version number and date.
  • 1.3 Existing Data. The BIM Execution Plan should clearly reference all pre-existing digital files that are to be incorporated into or used to develop the project models. These existing files may include surveys, digital scans, photographs, and drawing files completed as part of pre-design services for the project. They may also include standards developed by project participants that are to be incorporated into the project models. Each file should include the following information, in addition to any other information the parties deem appropriate:

-    File name;

-    Description;

-    Location (including a link or information necessary to retrieve file for use); and

-    Author or provider of file (including contact information).

ARTICLE 2   DESIGNATED MODEL PORTION DELIVERY MILESTONES

  • 2.1 Designated Model Portion Delivery Milestones. As set forth above, the BIM exhibit sets forth requirements related to designated model portion delivery milestones. Section 2.1 of the BEP is where parties can insert or make reference to an attached delivery schedule for the project, which will identify designated model version delivery milestones. Alternatively, a Model Element Table can accomplish this task, in which case reference should be made here to Article 7 (Levels of Development). Milestones can be as simple as scheduled deliverables by project phase, such as “Schematic Design,” “Design Development,” and “Construction Documents.” Other possible milestone examples may include partial phase deliverables, such as “50% Design Development,” or specific packages for “GMP pricing,” “Building Permit,” or anything the team might require as a pre-planned deliverable. The project participants should review their respective agreements, consider the overall project schedule, and consult with one another to determine the reasonable number of specific, planned deliverables. It is worth noting that interim deliverables may also be used on the project; however, the rules for authorizing reliance on any interim deliverable are different, as set forth in the BIM Exhibit (See, e.g., E201-2022 Section 2.5.4).

ARTICLE 3   SOFTWARE AND FILE EXCHANGE PROTOCOL

  • 3.1 Modeling Software. Software is often not compatible with other software, and sometimes is not compatible with other versions of the same software. Therefore, it is important to define the software that will be used at the beginning of the project. Typically, the architect will define the primary modeling software and version that would be utilized (“Revit R20,” for example). Then, other design team members can be aware of this software requirement prior to beginning work and can confirm they have this release or ability for compatibility, or can upgrade as needed.
  • 3.1.1 Modeling Software Updates. Since different versions of the same software may not be compatible, all parties should agree to update software releases and confirm that there are no issues in the models prior to updating. Typically, the architect or model manager will discuss this concept during the design process, and the parties’ agreement on how to obtain uniformity in software updating is set forth in the BEP.
  • 3.2 Other Software Tools. These might include tools like solar, energy, structural, clash modeling tools, or other coordination tools that might be required during the design/construction process. Examples could include: Bluebeam, Comcheck, Navisworks, Revitzo, PlanGrid, Procore, Box, DropBox, etc.
  • 3.3 File Exchange Protocols. How project team intends to share models is an important issue to define early. Various options are provided but the rules, file naming, and frequencies surrounding file exchanges are critical.
  • 3.3.1.1 Cloud-Based Collaboration. If cloud-based tools are to be utilized on the project, then all project participants should understand and acknowledge this structure ahead of time. The project participants should discuss and agree upon which of them will be responsible for the cost of licensing the software. In addition to licensing fees, the project participants should also discuss and agree upon who will host the project models, who will manage user access, how folders will be structured, and what information beyond models is to be hosted.
  • 3.3.1.2 Separate Model Collaboration. The method of separate model collaboration could describe an older FTP Site, Newforma Shared Folder, or DropBox storage site, where individual files or models are uploaded and downloaded by the various project participants. User access and privileges can also be defined and controlled, depending on who is hosting these sites.
  • 3.3.1.3 Other. For many project teams, there could be multiple cloud-based collaboration tools, which could include one location for the models and other locations or tools for various project related documents (emails, the project program, meeting minutes, memos, action items, submittals, request for information, issued packages, change orders, etc.). If the parties are using this type of structure, then selecting 3.3.1.3 could be appropriate.

ARTICLE 4   DATA SECURITY MEASURES. Although the AIA’s BIM exhibits contain a fill-point for data security, if the parties wish to provide additional granularity with respect to their project’s data security measures, then they can include those measures in the fill point in Article 4 of the BEP.

ARTICLE 5   MODELING PROTOCOLS. Article 5 is where the project participants will indicate the details and specifics as to how they will develop their Models. The different topics that comprise this list of protocols are set forth below.   

  • 5.2 Model Data Subdivisions. Models may be subdivided to manage the size of the data groups, or to divide the effort amongst different team members. The more a model is divided, the greater will be the effort will be to bring them together to coordinate the project. Here, the project participants agree to reasonably minimize the subdivision of their model portion(s). Any changes to subdivided model portions must be communicated to all project participants to inform them they must make a change as to how they would overlay newly subdivided portions with the entire model.
  • 5.3 Parameters. In Section 5.3, project participants indicate software and object parameters that are intended to be shared for sheet indices and model coordination.
  • 5.4 Phasing. Some projects may be designed and developed in phases, with some areas of the overall model advancing ahead of others. If the project includes phases, then the project participants would indicate the phases in Section 5.4 so that consistency can be maintained amongst all the project participants. If additional phases, or modifications to phases, are required at a later time, then all project participants should agree in advance to use the new or modified phases.
  • 5.5 Sheets. Assuming the project model will be used to develop traditional two-dimensional output(s), the project participants should list in Section 5.5. any requirements they may have, such as sheet sizes for the project, title block format, and requirements regarding how to name, number, and identify each deliverable.
  • 5.6 Design Options. Some modeling software allows for developing design options within a single model. Alternatively, some team members may prefer to develop design options in a separate file. Whether the project participants use internal modeling options or external, separate models, some effort will be required to manage the necessary coordination between the project participants. Therefore, in Section 5.6 the project participants should indicate their preference (or lack of preference) and the protocols for addressing or exploring design options.
  • 5.7 File Naming Conventions. Many files will be exchanged and overlayed over the life of the project, so file naming should be consistent and unchanged. In Section 5.7, project participants should indicate the protocols for naming each type of file for each separate software used.
  • 5.8 Standards. If there will be specific modeling standards that apply to all project participants, these should be indicated in Section 5.8., either by completing the fill point in the BEP or referencing by a separate document that can be attached. If the Owner has modeling standards, those should be included.

ARTICLE 6   MODEL MANAGEMENT PROTOCOLS

  • 6.1 Responsibility. In Section 6.1, the project participants define individual roles and responsibilities for model management. The following is a list of model management responsibilities that should be considered:
  • Overall BIM management
  • Archiving
  • Design-level system coordination
  • Construction-level system coordination
  • Model quality control
  • Model element table compliance
  • Model element table updating

 

Which person or entity is assigned these responsibilities depends on a number of factors, such as the project delivery model and the skill and capacity of the various project participants. Often, these assignments can change as the project progresses; for example, overall BIM management responsibility may be with the prime architect at project inception and pass to the prime contractor at start of construction.

  • 6.2 BIM Planning Meetings. An example as to how to complete Table 6.2 is below:

Meeting Type

Project Stages or Phases

Frequency

BIM Requirements Kick-off       

Phase 1

Weekly, as needed

BIM Execution Plan Distribution

Phase 1

Weekly, as needed

Design Coordination

Phase 2

Weekly 

Construction Coordination

Phase 3

Weekly 

Construction Progress Reviews   

Phase 3

Bi-Weekly 

 

  • 6.3 Quality Control and Model Health. Section 6.3 outlines the various responsibilities and agreements related to quality control for the model, and model health. Section 6.3.1 generally states that “Each Project Participant is responsible for producing quality Model Portions that can be used and opened effectively by all other Project Participants.” The project participants are also required, pursuant to Section 6.3.1, to perform the various model checks listed in Section 6.3.1.1, including visual checks, interference checks, modeling protocols checks, model integrity checks, and any others that the parties add.

ARTICLE 7   LEVELS OF DEVELOPMENT

  • 7.1 Level of Development Definitions. As explained above, Section 7.1 reiterates that the LOD definitions are set forth in the BIM exhibit.

ARTICLE 8   RELIANCE AUTHORIZATION PROTOCOLS. Throughout a project, one project participant may need to obtain another project participant’s model portion for some reason. These instances of model sharing are known as “interim deliverables.” Section 2.5.4 of E201-2022 sets forth the parties’ agreement with respect to reliance on model versions at interim deliverables. For designated delivery milestones, the E201-2022 provides in Section 2.5.3 that the Parties can use a “Model Element Table or another method” to determine reliance. Interim deliverables, however, are more sporadic and ad-hoc as compared to designated delivery milestones and, therefore, the amount of reliance placed upon a model portion shared as an interim deliverable will need to vary with the circumstances of that instance. As a result, sharing deadlines and levels of reliance cannot be anticipated and set forth in a Model Element Table such as the G204-2022 or G205-2022. Section 2.5.4 of E201-2022 requires that model authors “describe the extent of authorized reliance on its Interim Deliverable.” 

Article 8 of G203-2022 is the place where model authors determine how they will “describe the extent of authorized reliance…” Specifically, the fill point in Article 8 instructs parties to “[d]efine the means of authorization, whether described within the Model Version or in a separate document, or both. If appropriate, attach the authorization text or form as an exhibit.” In this space, parties can describe how they will authorize reliance on their model portions when issued as interim deliverables. For example, parties can choose to embed the authorization information within the model portion, or send or attach a document with authorization text to the other project participant(s) when the model portion is transmitted.

ARTICLE 9      IDENTIFICATION OF A MODEL OR MODEL PORTIONS. Once a Model becomes a deliverable that can be relied upon, or may be enumerated as a Contract Document, it is critical that there be a way to identify it—so that the user knows what it is. This is an essential tenet of document control; no different from the obvious need to name, number, date, and otherwise identify a two-dimensional drawing. There are any number of ways to name/number/date/identify a model, either through the digital data external to the file, or within the model once it has been opened. The AIA BIM exhibits set forth reliance provisions for models and model elements that vary depending upon whether the model version in question is a designated milestone deliverable or an interim deliverable. If the model version has been identified or labelled as designated deliverable, and labelled or named as such, then the project participants may rely on the model elements as set forth in Article 7 of this BIM Execution Plan. If a model version has been identified or labelled an interim deliverable, however, then it falls upon the model author to indicate the extent to which they are authorizing reliance on their version. In either case, it is incumbent on the model author to identify or label what their model version is at the time it is being issued, and in the case of an interim deliverable to further specify the reliance provisions that they are permitting related to how it can be used.

The fill point in Article 9 is where the project participants will state how they will identify or label a model or model portion at the time it is issued, whether internal to the model, or in the form of a separate document, such as a transmittal. Knowing that models can be separated from transmittals, the user of this BEP would be well advised to develop an identification process that travels with, and cannot be separated from, the model version upon which they are allowing others to use and rely. For example, the parties could choose to use a form that either accompanies or is used internal to a model, which should indicate key document control information, such as:

  • Project Name;
  • Model Author;
  • Model Version Name;
  • Deliverable name (Milestone or Interim); and
  • For Interim Only: the extent of permitted reliance.

 

Other information may be provided, such as date/time, though this might be best left to the file data, which is automatically generated when the file is saved. The project participants may also wish to include any specific rules or limits for reliance here, or make reference to other coordinated documents, such as the BIM exhibit, this BIM Execution Plan, or even the agreement, which may contain pertinent provisions for model ownership or licensed/permitted use—information that might travel with the model wherever it goes, and into whoever's hands it may fall.

ARTICLE 10   OTHER BIM OR MODELING PROVISIONS. The AIA’s BIM Execution Plan G203-2022 is intended to be a standardized form to cover the BIM needs for the majority of projects. However, there may be other provisions that are appropriate to add according to the unique circumstances of a project. In this event, parties can insert other provisions related to BIM or modeling within the fill point in Article 10.

ARTICLE 11   EXHIBITS AND ATTACHMENTS. If parties wish to add exhibits or attachments to their BIM Execution Plan, they can do so in Article 11. For example, if the parties have developed a form to use to describe authorized reliance on model portions at interim deliverables, or if the parties wish to reference the BIMForum Level of Development (LOD) Specification, they can list it in Article 11.

Notes.

Modifications. Particularly with respect to professional or contractor licensing laws, building codes, taxes, monetary and interest charges, arbitration, indemnification, format and font size, AIA Contract Documents may require modification to comply with state or local laws. Users are encouraged to consult an attorney before completing or modifying a document.

Reproductions. This document is a copyrighted work and may not be reproduced or excerpted from without the express written permission of the AIA. There is no implied permission to reproduce this document, nor does membership in The American Institute of Architects confer any further rights to reproduce this document. For more information, see the document footer and the AIA Contract Documents® Terms of Service.

Was this article helpful?
0 out of 0 found this helpful
Have more questions?
Submit a request