Project Components

Project component is a generic term for the following component types: Actors, Project Phases and BIM Use Cases. 

Actors

Actors are responsible for the delivery of a special model. A corresponding actor can be defined on the tab Project Components > Actors.

Project Phases

Project phases are the phases carried out in the project, e.g. according to the German HOAI, the American ISO or the RIBA work plan in Great Britain. The corresponding project phases can be defined under the tab Project Components > Project Phases.

BIM Use Cases

BIM Use Cases define different application scenarios in a project. These can be created or selected under the tab Project Components > Use Cases.

Functionality of a default use case

In BIMQ it is possible to define a Default Usecase. This is used to meet minimum data requirements for each selected Project Phase. Additional use cases can optionally be set so that they meet additional data requirements.

Note: The Default Usecase can only be selected once. It is then no longer possible to delete, edit or define any other Default Usecase. 

In the example shown, the “Minimum Requirements” use case is defined as the Default Usecase. This is indicated in the overview window by a bold font.

In the menu Project Components > Use Case Assignment, the Default Usecase can be assigned to the differently defined Project Phases. 

The use of a Default Usecase supports the user in defining minimum requirements or requirements that should always be set for each project phase. This application influences the export of reports, software templates or checking rules. In the example shown, various setting scenarios are explained and the influence they have on the export of documentation (reports, software templates, checking rules) is shown. The individual scenarios are identified by different colors: 

1. The Default Usecase “Minimum Requirements” is set for the project phases P02, P05 and P09. The requirements defined in the Default Usecase are kept for these project phases. 

2. For the project phase “P02”, the Default Usecase “Minimum Requirements” and the use case “Visualization” are set. When exporting data (reports, software templates, checking rules), all requirements of the Default Usecase and additional requirements of the use case "Visualization" are transported. 

3. In the third scenario, only the use case “Surveying” is set for the project phase “P03”. Only the requirements for this use case are considered in the export. 

4. For the project phase “P05”, the Default Usecase “Minimum Requirements”, the use case “Existing Conditions Modelling” and the use case “Surveying” are set. When data is exported (reports, software templates, checking rules), all requirements of the Default Usecase and additional requirements of the use case "Surveying" are transported. The selection of the use case “Existing Conditions Modelling” is indicated by a circle symbol  O. This means that this use case is defined but not used for additional data requirements. The information is only passed on for the generation of reports.  

5. In the fifth scenario, no use cases are defined for the "P08" project phase. The Default Usecase “Minimum Requirements” is also not set. As a result, no requirements can be defined and therefore no data can be exported. 

6. For the project phase “P09”, the Default Usecase “Minimum Requirements”, the use case “Existing Conditions Modelling” and the use case “Surveying” are set. The use cases “Existing Conditions Modelling” and “Surveying” are defined, but are not used for additional data requirements. In this scenario only the requirements of the Default Usecase are exported.