A clear brief and an understanding of the constraints associated with a project have always been essential prerequisites for a successful project. The same principles apply to formulating requirements for the use of BIM on a project:
Take the time to understand your needs:
- Make a realistic assessment of capabilities and capacities.
- Define the scope of service.
- Manage expectations and risk.
- Apportion reward commensurate with effort and responsibility.
It is strongly recommended that you define the BIM requirements for your project with a structured approach that involves the client and project team. This should be instigated as early as possible.
Mastering BIM on a project
The Project BIM Brief will define the BIM model creation and sharing process, and hence it is imperative that the decision to use either Design-Bid-Build (DBB) or Design and Construct (D&C), methods be determined at the initial stage of the project so that BIM can be properly structured and managed to support the Building and Construction Procurement strategy. The project contract i.e NEC4 (often sees BIM as a secondary option in the contract. ) This will define the integration or separation of risk and responsibilities for the design and construction contracting entities, while, the Level of Development (LOD) and division of BIM responsibilities and BIM Assessments will be defined within the BIM Execution Plan.
Where the BIM model(s) is to be used for design and construction, the BIM Execution Plan (BEP) should address how the model(s) can be migrated between stages effectively with the minimum effort.
Clients often require the interoperability of data as a strategic management issue to ensure their access to building information over the life of the capital asset. Therefore, any software and file format that meets the client’s interoperability standards is acceptable for use on their projects, subject to their approval. It is also critical that available Project standards and protocols are used in developing the models so that information within the data drop handover can be read and normalised for the client’s management purposes. The Common Data Environment (CDE) assigned for the project shall be used to maintain workflows and manage all relevant data and information that needs to be shared with various parties involved through the life cycle of the project