BIMQ 2.5

The BIMQ user interface has been further improved with the upcoming update to version BIMQ V2.5 This includes an optimization of design and functionality across all areas. The BIMQ development team attaches particular importance to a functional and intuitive way of working. This made it possible to improve the efficiency of the workflow and to simplify work processes.

Login Page

The login area has been fundamentally revised in the version BIMQ V2.5 and adapted to the new and currently used design. The new login page is divided into two functional areas. On the left side is the actual login area, in which the e-mail address required for registration and the password stored for this purpose can be entered. On the right side, the user will find interesting and helpful news about BIMQ. This concerns, among other things, experience reports from different companies or projects in which BIMQ is used, newly created articles in the knowledge database or information about new functionalities that have been released. 


Figure 1: Login page with registration and news area.

All news are displayed in separate tiles and can be called up separately. Further information is then directly linked or offered for download in different data formats.

BIMQ user interface

The BIMQ user interface has also been fundamentally revised and improved. This is the case for the project overview page as well as for all functional areas in BIMQ. The former provides a detailed overview of the available projects and the license model used. The additional display of logos facilitates the project-internal clarity and thus enables easier administration. 


Figure 2: Overview of all available projects.

All function areas and menu tabs available in BIMQ were also completely revised visually and adapted to the new design. The BIMQ development team focused here primarily on a practical and intuitive implementation. The display of tables and function areas has been improved and supplemented by additional tooltips. These are displayed as a mouse over and serve as useful assistance for the user. By optimizing the space required, more information can be displayed in a structured and clear manner. This enables a more effective way of working and increases the performance of the work processes.  


With the update to version BIMQ V2.5, the performance has been decisively improved. This is essentially reflected in the speed of page loading or the execution of commands. The performance thus has a direct influence on the efficiency and effectiveness of the work processes. The BIMQ development team is constantly working to further improve and optimize server performance. But also your own settings and an adapted way of working can contribute to a performance improvement.

Project Overview

As part of the general revision of the BIMQ user interface, the project overview has also been adapted and optimized. This can be called up under the menu item Settings > Project Overview. In the overview, all general information about the project is displayed on the left side. In addition, the user's own role in the project and the associated rights can be seen here.

The right side of the overview shows the newly revised workflow diagram. This describes step by step the correct handling and working method with the data management software BIMQ. If a user does not have the authorization to use individual areas or functionalities, the relevant work step is shown grayed out. Detailed information on the individual steps of the workflow diagram are linked to the knowledge base and can be accessed by clicking on the short description highlighted in blue. Clicking on the work step highlighted in turquoise takes you directly to the corresponding work step in BIMQ.


Figure 3: Project overview with general project information, access and rights management and workflow diagram.

Requirements Import

With the update to version BIMQ V2.5, the functionality of importing from other projects has been added for the area Project Requirements. This functionality is called "Requirement Import" and can be called under the tab of the same name. The method has already been implemented for the area Component Templates. It's called "Template Import" and describes the possibility to migrate different components from other projects into your own project, or to update already existing components.

The functionality "Requirement Import" in the area Project Requirements differs fundamentally in its generated result from the functionality "Template Import", which can be found in the area Component Templates.

With the method "Template Import", components from other projects can be migrated or updated in your own project. This concerns the complete area of Component Templates, thus the library available in BIMQ, in which components can be defined once and used several times.

The difference to the method "Requirement Import" is that here already existing links of components from external projects can be migrated or updated into the own project. This reflects the function of the area Project Requirements, in which various properties and property groups are assigned to an element and this in turn is assigned to a discipline model. Thus, entire discipline models can be imported or updated here if desired.

Both methods, "Template Import" and "Requirement Import", have been completely revised and adapted to the new design as part of the update to version BIMQ V2.5. The working methods have been optimized and are structured very similarly for both methods.

The function "Requirement Import" in the area Project Requirements can basically be divided into five functional areas:

  • Project selection 

  • discipline model selection 

  • Identify method 

  • Merge strategy 

  • Requirement Settings


Figure 10: Overview of the functional area "Requirement Import" in the section Project Requirements.

1.) In the project selection, all available projects are displayed in a drop-down list. Here you can select the project from which the information is to be imported.

2.) In the field discipline model selection, the desired discipline model is selected from which element links (Elements are assigned to different property sets incl. properties or base quantity sets incl. base quantities), are to be imported into the own project or existing links are to be updated.

3.) In the function area Identify method, the data to be imported can be filtered according to different criteria. Here it is possible to distinguish between filtering from Name & Code or only for the Name.

4.) The Merge strategy describes how the data will be imported. Here, a distinction can be made between two selection settings. In the first method "Add components from other project requirements", existing content is retained and new content is added separately. In the second Merge strategy "Update of existing components only ", it is possible to overwrite existing content. Here, a comparison of the existing and new content is made using the Identify method, i.e. Name & Code or just the Name. If there is a match here, a checkbox in the preview table can be used to select whether the content in question should be overwritten or retained.

4.1) Merge strategy: Add components from other project requirements 

In the first Merge strategy "Add components from other project requirements", you can simply import new components, including their links (property sets, properties, base quantity sets, geometries...) from the selected project into the current project.

In the work table, the area "Requirement Import" is displayed on the left side. Here all information of the project is displayed, which can be imported into the current project. The data is further filtered according to the selected discipline model and is displayed in a hierarchical structure.

On the right-hand side of the work table is the area "Own Requirement" marked in turquoise. The current project into which the import is to take place is also displayed here in a hierarchical structure.

In both areas, the respective Project Details continue to be displayed. Here, information to the used Software, IFC Schema, Languages or Classifications can be viewed. If a specific format, for example "IFC 4 Add2" is available in the external project, which is not available in the own project, this is displayed crossed out. This means that no information can be imported for it. For a successful import, the format "IFC 4 Add2" would have to be added in the own Project Settings beforehand.

If new components are to be added to the current project, they must be selected in the table "Requirement Import". This is done simply by selecting the corresponding checkbox. Components that are crossed out cannot be selected because they already exist in the current project and would otherwise create a duplicate.

Additional information can be accessed by right-clicking on a specific component. Thus, Name, Code, Description, IFC Mapping or mapping to a Software application are displayed in a separate window. For all components that are crossed out, the location can still be displayed in the area Component Templates.


Figure 11: Additional information displayed for the property "Pitch Angle".

Once all the components that are to be transferred have been selected, they can simply be moved from the area "Requirement Import" to the area "Own Requirement" using the drag & drop function. The user can individually define the component group in which the data is to be stored. The data can be rearranged at any time. All newly added components are also created in the area Component Templates, i.e. the library managed in BIMQ.


Figure 12: Transfer of the marked elements from the external project "Catalog templates - English" to the own project "Demo Project - BIMQ 2.5".

4.2.) Merge strategy: Update of existing components only

The second Merge strategy "Update of existing components only" is selected if existing information of the own project is to be updated. The table structure is the same here, which was already explained in point "4.1) Merge strategy: Add components from other project requirements". If information is to be updated, it must first be selected in the left table "Requirement Import". All components, which are crossed out, cannot be used for an update, since these do not exist in the own project. With this merge strategy it is therefore important that the information which is to be updated is identical in the identification, i.e. name and code.

Additional information can be accessed by right-clicking on a specific component. Thus, Name, Code, Description, IFC Mapping or mapping to a Software application are displayed in a separate window. For all components in the table "Requirement Import" that are not crossed out, the location of the existing component can still be displayed in the area Component Templates.

If all components to be updated have been selected, this must still be confirmed by clicking on the update icon. Subsequently, all selected data in the own project have been updated.

Note: Updating the data is not reversible.


Figure 13: Update of the marked properties from the external project "Catalog templates - English" into the own project "Demo Project - BIMQ 2.5".

5.) If components are assigned to different Milestones and Use Cases in an external project, these assignments can also be transferred to your own project. The functional area "Import Requirement Settings" is used for this purpose, in which it can be decided whether assignments to the various combinations of milestones and use case are to be transferred or not. If this is desired, it is necessary to ensure that the corresponding combination from the external project is also present in the own project.

6.) Clicking on the preview icon opens the corresponding import dialog. On the left side there is the table "Requirement Import", in which all information of the selected project are displayed. The table is displayed in a hierarchical structure and can be filtered according to the specific discipline models.

On the right side there is the table "Own Requirement" in a hierarchical structure. This is marked with a turquoise background and shows all information of the own project.