PMIS 435: PMIS to Support Developing the Building Information Model (BIM) Execution Plan

With the growing requirements to adopt Building Information Model (BIM) in capital projects, project team members who will be responsible for authoring, reviewing, approving and sharing the BIM models must develop the BIM Execution Plan (BIM EP) in accordance with the project owner BIM Project Delivery Standard. When approved, this execution plan will be adopted by BIM project team in delivering the project BIM scope of work.

The BIM Execution Plan will usually include sections for Project Information, Project Schedule and Milestones, Project BIM Deliverables by Project Stage, BIM Participants, Roles and Responsibility Matrix, Project BIM Goals, BIM Model Software, BIM Model Collaboration, Transmission and Permitted Use Strategies, BIM Meetings, BIM Model Structure and Naming Conventions among others.

Project Management Information Systems (PMIS) like PMWeb can be used to create the BIM Execution Plan by capturing the content for the different sections of the BIM EP. Starting with the project information for which the details will be extracted from the PMWeb project module. The data that will be captured could include Project Name, Project Number, Project Manager, Primary A/E, Project Address, Project Gross Square Footage, Number of Floors Above Ground, Number of Floor Below Ground, Project Type (New Construction or Renovation), Project Delivery Method and Project Scope of Work.

BIM Schedule and Milestones

The project schedule, this will usually include the milestone dates for the project stages as well as the planned dates for the BIM deliverables. PMWeb scheduling module will be used to create this schedule or if this schedule is already created in Oracle Primavera P6 or MS Project, it can be imported to PMWeb.

BIM Deliverables

PMWeb stage gate module will be used to monitor, evaluate and report on the execution of the BIM deliverables. For each project stage, the list of BIM deliverables will be added along with their due date and other relevant details. When work progress, the status of each deliverable will be updated to reflect its current status.

BIM Participants, Roles and Responsibility Matrix

The resources that will have a role in authoring, reviewing, approving and using the BIM models must be added to PMWeb resources module with their relevant details as well as the entity they work for. This will help in maintaining a single repository for all resources that could have an involvement in BIM models across all projects that the organization is involved with. Those could include Project Owner (PO), Architect (A), Structural Engineer (SE), Plumbing Engineer (PE), HVAC Engineer (HE), Fire Protection Engineer (FE), Electrical Engineer (EE), Technology Engineer (TE), Site/Civil Engineer (CE), Landscape Architect (LA), Construction Manager (CM), General Contractor (GC), Structural Contractor (SC), Design Builder (DB), Plumbing Contractor (PC), HVAC Contractor (HC), Fire Protection Contractor (FC) and Electrical Contractor (EC).

Using PMWeb organization chart module, the project team can define the BIM organization chart that could differ from one project stage to another. The organization chart will detail the role that each BIM team member is playing on the project including the identification of the different model element authors.

Similar to the project responsibility assignment matrix (RAM), PMWeb form builder will be used to create the BIM Project Objectives and Responsibility Matrix (ORM). The matrix will list the different BIM project objectives for each project lifecycle stage and the project team members who will be involved in fulfilling the objective. The responsibility for each project team member could be either a model author (A), model reviewer (R) or a model user (U).

BIM Meetings

During the project lifecycle stages, there will be a number of BIM related meetings that need to be attended by the project owner, project management consultant, engineering consultant, contractors, facility managers among others. Some of those meetings will be held once while the others will be held based on pre-agreed schedule. The BIM related meetings include BIM Kick-off, BIM Execution Plan Review, Model Review, Stakeholder Review, Clash Prevention Meetings, Clash Detection Meetings, Coordination Signoff Meeting, Conformed Design Intent BIM Development, Conformed Design Intent BIM Turnover, Record Construction BIM Turnover and COBie Worksheet Turnover.

PMWeb Meetings Calendar and Meetings modules will be used to support those BIM meeting requirements. The Meeting Calendar module will be used to plan the dates for those meetings depending on the BIM Execution Plan.

Whereas the Meetings module will be used to capture the details of business items discussed during those meetings with the assigned responsibility and due date for each along with the actual conclusion date of the business item. This will enable the BIM project team of tracking of all actions and tasks identified in those meetings.

Other Information Needed for the BIM Execution Plan

The BIM Execution Plan will include a number of tables to capture the additional needed information. For example, there will be table to identify which BIM use cases will be implemented on the project along with a brief description of their intended application. This will be grouped into Design and Construction BIM use cases. In addition, there will be another table for the BIM Model Software applications that will be used on the project. This table will show for each BIM use case, the software to be used, native file format and the software version. Further, there will be another table for the Design and Construction Model Managers to identify how and when digital data will be shared between Model Element Authors (sender) and what the Permitted Use of that information is by the Model User (receiver).

All of these tables will be created using PMWeb form builder in a similar format to was done for the BIM Project Objectives and Responsibility Matrix (ORM). This will enable the BIM Project Management team to formalize the capturing of this important information with the option of adding a workflow for each form to formalize the submit, review, approval and final approval process for this captured information.