Establish a (pre-appointment) BIM Execution Plan

00:01

Welcome to the second objective of this course

00:04

where we will discuss the need to establish a (pre-appointment) BIM Execution Plan.

00:16

This is where we are in the workflow.

00:18

Once the information required by the Exchange Information Requirements is confirmed,

00:22

we can move to the next item in the workflow.

00:25

The definition of the Project implementation plan.

00:29

The pre-appointment BIM Execution Plan must demonstrate that each task team have both the capability

00:35

and capacity to produce and manage the information and in line with the exchange information requirements.

00:42

Capability means having the necessary experience, skill and technical resources to perform a given activity.

00:50

Capacity means having the resources required to complete an activity within the time necessary.

00:57

In doing this, each task team shall assess their capability

01:02

and capacity to deliver information per the appointing party's Exchange Information Requirements.

01:08

There are a variety of methods that can be adopted when undertaking an assessment.

01:14

This could be a proforma that each task team completes, an online tool

01:18

which may be more effective and easier to collate or a full independent audit.

01:25

Following the assessments of the capability and capacity of each task team.

01:29

The prospective Lead Appointed Party should establish the delivery team's capability and capacity.

01:35

This is done by aggregating the assessments undertaken by each task team.

01:40

The result will summarize the delivery teams capability to manage and produce information and its capacity for timely delivery.

01:50

The Mobilization Plan allows the Delivery Team to verify that they have the people,

01:55

processes and technology to deliver the information.

01:60

Therefore, the prospective Lead Appointed Party shall establish the Delivery Team's proposed Mobilization Plan

02:06

that will be initiated and implemented during mobilization.

02:11

In doing this.

02:12

The prospective Lead Appointed Party should consider their approach,

02:15

timescales and responsibilities for testing and documenting the proposed information Production Methods and Procedures.

02:24

Testing the Information Exchanges between task teams.

02:28

Testing the Information Delivery to the Appointing Party.

02:32

Configuring and testing the Project's Common Data Environment.

02:36

Configuring and testing the Delivery Team's distributed Common Data Environment

02:41

and its connectivity to the Project's Common Data Environment if applicable.

02:46

Procuring, implementing, configuring and testing additional Software, Hardware and IT Infrastructure.

02:53

Developing other Shared Resources to be used by the Delivery Team.

02:57

Developing and delivering Education to Delivery Team members.

03:03

Developing and providing Training to the Delivery Team members.

03:08

Recruiting Additional Delivery Team Members to achieve the necessary capacity

03:13

and Supporting Individuals and Organizations that joined the Delivery Team during the appointment.

03:23

This is where we are in the workflow.

03:26

In this step we look at the Project goals for collaboration and information.

03:32

The projects information standard is documented within the appointing party's Exchange Information Requirements.

03:38

The pre-appointment BIM Execution Plan allows the prospective delivery team to identify any additions or amendments

03:44

to the project's information standard.

03:47

For example,

03:48

this could be a room or space referencing system.

03:51

The goal is to ensure a consistent approach for structuring and classifying information most appropriate for the project.

03:59

The pre-appointment BIM Execution Plan may set out a proposed standard for the exchange of information between the task teams.

04:06

The distribution of information to External Parties and the delivery of information to the Appointing Party.

04:18

This is where we are in the workflow.

04:20

In this step, we will discuss the Major project milestones.

04:26

As a part of the tender response.

04:29

The prospective Lead Appointed Party should nominate individuals from within its organization

04:36

to undertake the information management function.

04:40

Alternatively, the prospective Lead Appointed Party can appoint a prospective appointed party

04:48

or third party to undertake all or part of the information management function.

04:55

In doing this,

04:56

the prospective Lead Appointed Party shall consider the Delivery Team's High-level Responsibility Matrix,

05:04

The RACI chart.

05:07

Raci stands for responsible, accountable, consulted and informed.

05:14

This Matrix lists all appropriate elements within the information model,

05:20

identifies a responsible party and the key deliverables associated with each element.

05:27

The Matrix establishes what information will be produced, when and by which task team.

05:36

The goal is to improve collaboration amongst the delivery team through clearly defined and communicated responsibilities.

05:46

The High-level Responsibility Matrix is later developed into a Detailed Responsibility Matrix,

05:53

the DRM, upon successful tender response.

05:57

In addition to the High-level Responsibility Matrix,

06:00

the prospective Lead Appointed Party shall create the delivery team's Risk Register.

06:07

The register identifies all risks associated with timely information delivery,

06:14

following the Appointing Party Exchange Information Requirements

06:18

and how the Delivery Team intends to manage these risks.

06:24

In doing this,

06:25

the prospective Lead Appointed Party should consider risk associated with assumptions.

06:32

The delivery team has made about the appointing party's Exchange Information Requirements.

06:38

Meeting the appointing party's project information delivery milestones,

06:45

the contents of the project information protocol,

06:49

achieving the proposed information delivery strategy,

06:54

adopting the project's information standards and information production methods and procedures,

07:01

inclusion or non inclusion of proposed amendments to the project Information standard.

07:10

And the mobilization of the delivery team to achieve the required capability and capacity.

07:18

This is a sample of a High-level Responsibility Matrix and Risk Register.

07:30

In this step,

07:31

we move on to defining the Project Information Model and the Delivery Strategy.

07:37

Following the ISO 19650 standard,

07:40

the prospective Lead Appointed Party shall develop a proposed information delivery strategy,

07:46

covering within the pre-appointment BIM Execution Plan.

07:52

This strategy should contain the delivery team's approach to meeting the Exchange Information Requirements,

07:58

including the level of information need, the acceptance criteria and delivery dates as well as the objective and goals,

08:10

known as the Use Cases to produce collaborative information.

08:20

In addition, the organizational structure and commercial relationships of the delivery team should be defined

08:28

and the delivery team split into task teams.

08:34

The task team is a team or an individual responsible for performing specific tasks in producing and managing information.

08:44

Task teams are often created around a discipline,

08:48

civil design, geo-technical, structural design or electrical.

08:56

The often multiple task teams within the delivery team.

09:02

The proposed Federation strategy is a higher level description of how

09:08

and why the information model is being divided via a model breakdown structure.

09:16

The federation strategy and information breakdown structure provide the rules

09:20

for combining and segregating information models.

09:25

The goal is to make the production and management of the information easier for the delivery team.

09:33

For example, it should define the maximum file size,

09:37

practical for upload and download with the specified IT Infrastructure.

09:43

For example 500 MB.

09:47

It should also define how and when to subdivide an information model if it breaches that limit.

09:56

To ensure that all delivery team members can access the information model,

10:01

it is necessary to standardize Software, Hardware, and IT Infrastructure.

10:09

The delivery team should provide a schedule of Software(including versions), Hardware and IT Infrastructure.

10:21

This is important to enabling collaboration and interaction between task teams,

10:26

delivery teams and the appointing party,

10:29

being a fundamental consideration for interoperability.

10:36

That is all we have to cover in this objective.

10:39

I will see you in the third objective of this course.