BIMKIT – Use cases

The goal of BIMKIT is the automated generation of digital models of existing structures. The application goals provide an overview of the purposes for which the generated models from the BIMKIT ecosystem can be used.

The application goals are based on the current demand for the use of existing models in practice. For this purpose, a survey was conducted in the construction industry. In addition, extensive discussions with our associated partners provided important insights for the definition of the application goals.

In the planning area of infrastructure construction, two application targets are considered. For bridge structures, all structural information relevant for the demolition planning of the supporting structure is extracted and fed into the as-built model. For roadway structures, the repair of noise barriers is also fixed as a usage target and all necessary information is extracted for this purpose as well.

In the field of building construction, the maintenance of technical building equipment, the optimization of space utilization and the optimization of energy consumption have also been identified as application targets.

LOIN tables

In order to be able to specify the basic functioning of the BIMKIT ecosystem, the requirements for the processes have been defined.

Depending on the intended use (application goal) of the as-built models, the requirements for the models to be delivered also change. The requirements were recorded in LOIN tables (level of information need). They represent all the information that must be recorded on a component and use case basis in order to ensure the complete information content of the models.

The content of the information need is conditioned by four factors:  In addition to the application goal of the as-built model, the “What for?”, the milestone of model delivery (“When?”), the acting supplier of the model (“Who?”) and the scope of delivery (“What?”) are also decisive.

In the BIMKIT project, this results in the structure picked up in the LOIN tables:

  • Delivery of the as-built model takes place at the end of the as-built process
  • Application target corresponds to the subsequent use case
  • Actor transfers the inventory model
  • Object classes include their respective requirement depths in terms of geometry, semantics and documentation