Before beginning to model, we need to ask why we are going to use BIM in this project. The most visible uses should be clear if you are interested in BIM:
Rethink this part, look at the introduction for BIM uses by plan BIM chile or UK
By defining BIM uses before starting with the project modeling, it is possible to ensure effective planning, efficient collaboration, efficient project management, and quality.
Examples of BIM uses, Plan BIM Chile
In fact it should be the client who establishes the uses, which respond to their company and project requirements (this is written in a document called Exchange Information Requirements or EIR).
My experience is that unfortunately many architecture offices use BIM by their own decision and not because it is a client requirement. In this cases it is still crucial that we decide what uses we will retain and which ones are not applicable for the project.
Once we establish the uses, they will guide us in outlining the framework for the documents we'll generate.
The straightforward answer is: yes, they should be documented.
In scenarios where BIM is explicitly included in the contract, and the uses of BIM are responding to an Employer's Information Requirements (EIR), documentation becomes not only beneficial but necessary. The BIM Execution Plan (BEP) plays a critical role here. It serves as a detailed document that outlines how the BIM processes will be integrated into the project, aligning with the EIR to meet the employer's information needs.
However, the importance of documenting BIM uses extends beyond projects where BIM is a contractual requirement. Even in cases where the contract does not specifically mention BIM, choosing to document BIM uses can significantly enhance project management by ensuring that all team members are on the same page.
Missing: how to document the uses? mini BEP?