A look at current projects shows that – despite the advantages of the model-based approach (BIM) – there have been and still are some “information exchange dilemmas” in its application. From the perspective of those involved, it is important to define the prerequisite, i.e. the goal and purpose, as a first step for targeted project management. It must be clear why, when and who needs what information. Precise answers are essential here. For economic reasons, too, “as much as necessary” and not “as much as possible” makes sense; the provision of unnecessary information should be avoided in order to concentrate the resources in a project on the important tasks. To ensure this, the second step, namely the description of the information requirements, must be based on a broadly supported method. This method is set out in the standard SN EN 17412-1:2020 “Building information modeling – Depth of information requirements – Part 1: Concepts and principles”.
In recent years, it has become established in the cooperation that the level of information need (LOIN) of the information recipients is answered with the declaration of the information delivery in the gradations LOG (geometry) and LOI (alphanumerics) as well as the further documents (delivery objects).
Practical experience shows that the acronyms “LOG and LOI” and the definitions for the “100-500” levels are not really suitable for precisely describing an expected delivery object. If definitions are adopted to regulate cooperation, this has so far been done without the requirement to derive and record the process and responsibilities in relation to the use case. This can lead to contradictions in the coordination of the parties involved and opens up scope for interpretation of the regulations made. This means that the information required for a building cannot be provided reliably and without contradictions.
Project organization and participants
BIM projects face various challenges in the provision and use of information: Time and cost pressure, increasing requirements, diverging business models, complicated project organizations, complex decision-making processes. And this in a situation in which roles and forms of cooperation are changing significantly and real and data-based collaboration is becoming increasingly relevant.
The basic and additional services as well as the types of remuneration are defined in the established regulations for planning and construction processes. The planning phases are described in the regulations of the Swiss Society of Engineers and Architects (SIA): In SIA 112 “Model Construction Planning”, in order 101 “Services provided by the client” and in orders 102, 103 and 108 for services and fees (LHO). However, the necessary depth of information required and the differentiation in the type of information in relation to a specific point in time is not defined. This is assumed to be generally known in the context of the building, the components, features, characteristics and documents in standard construction practice to date. When using the BIM method, essential things are therefore missing, such as plan derivation from the model, quantity determination for the verification of space efficiency, the determination of construction costs and gray energy (CO2) or model-based collaboration and coordination. Working methods, collaboration and use cases must be redefined and previous practice must be gradually translated into model-based working methods. However, the advantages cannot be transferred 1:1. The processes must be jointly defined and coordinated in order to reap the full benefits.
The depth of information required must be guaranteed along the project schedule and the defined milestones in the corresponding phases in order to ensure the coordination of those involved, the modeling plan and ultimately the success of the project. A concept, a method and a vocabulary are needed that enable quick and easy communication.
The following findings are currently being made in practice:
- The project participants have different information requirements at different times, based on their application objectives.
- In the case of roles, there are those who provide information and those who will use the information as part of their applications.
- The use of the delivery object must be clearly defined, which requires an outline structure, e.g. element plan, classifications or schemas.
Planners, companies and organizations have created their own “standards”, which are often not uniform. Even within a company, requirements are sometimes adapted to the specific needs of a project.
In order to strengthen targeted project management, clear prerequisites must be created. It must be clear why (purpose), when (time), who (parties involved), what (type) of information is required. This document, based on SN EN 17412-1:2020, serves to create these prerequisites.
Copyright
This document is licensed under a “Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License” as Attribution-NonCommercial-ShareAlike under the same conditions
