The mobilisation period follows an appointment where the delivery team mobilises resources and information technology systems. During mobilisation, the delivery team will have the opportunity to review their people, processes, and technology and if they are suitable to deliver the information requirements. This stage is broken down into a series of activities that will need to be completed in accordance with clause 5.5 of I.S. EN ISO 19650-2.

Mobilise Resources

At this stage, the lead appointed party (with contribution from task team(s) / appointed parties) shall mobilise the resources that were defined in the delivery team’s mobilisation plan (clause 5.3.5 of I.S. EN ISO 19650-2).

Mobilisation of resources will allow the lead appointed party to: confirm the resource availability of each task team, develop and deliver education on topics such as the project’s scope, EIR and delivery milestones (knowledge required) to delivery team members, and develop and deliver training (skills required) to the delivery team members[1]. This activity should take place before any information is generated within a task team.

Mobilise Information Technology

In addition to the mobilisation of resources, the mobilisation of information technology shall also take place as defined in the mobilisation plan.

By doing this, the lead appointed party shall: procure, implement, configure, and test software, hardware, and IT infrastructure; configure and test the project’s CDE; configure and test the delivery team’s (distributed) CDE and its connectivity to the project CDE (if applicable), test the information exchanges between task teams, and test the information delivery to the appointing party[1]. This activity should take place before any information is generated within a task team.

Test the project’s information production methods and procedures

Lastly, the lead appointed party shall test the project’s information production methods and procedures as defined within the delivery team’s mobilisation plan.

By doing this, the lead appointed party shall have: tested and documented the project’s information production methods and procedures, refined and verified that the proposed information container breakdown structure is workable, developed shared resources to be used by the delivery team, and communicate the project’s information production methods and procedures to task teams[1]. This activity should take place before any information is generated within a task team.

Summary

To ensure projects start well and increase the probability of ending well, it is crucial to plan for mobilisation as early as possible once all resources have been identified and made available. All members of the delivery team must make an effort to successfully test and mobilise all relevant resources while allowing sufficient time for training if necessary.

[1]Organisation and digitization of information about buildings and civil engineering works, including building information modelling (BIM) - Information management using building information modelling - Part 2: Delivery phase of the assets (I.S. EN ISO 19650-2:2018)

  • Links to helpful resources here.