The license Free is intended for all customers who want to test BIMQ over a longer period of time. Basically, this is a free license, which can be applied for by any user without specific requirements.
The license Free is suitable for extensive testing of the BIMQ functionalities as well as the planning of exchange requirements. Since this is a free license, all exports are not allowed. However, it is possible to have access to the content of the publicly available catalog templates and migrate it into your own project. The validity of the license is exactly 1 year after activation and can be easily reapplied for after expiration. A transfer of the project to another license is not possible. Each Free license has a maximum of one user access and one project. You can choose between different project templates, which are filled with different content. Alternatively, it is also possible to choose a completely new project, without any content. Questions, customer requests or suggestions for improvement will be forwarded free of charge via our e-mail support and processed promptly by our team. For more information about functionality and prices of the different license models, please click here.
Organization of user rights
Each license is linked to an Organisation, which is represented by the company name or institution name. The user accesses defined in the license are in turn assigned to an organisation. All users stored here, have access to BIMQ and can be assigned to the various projects. Which employee of the organization gets access to BIMQ can be defined in the settings. This is done exclusively by the Organisation Manager, who stores the clear name and the e-mail address of the user. Depending on how many user accesses are activated, these can be managed and exchanged here. Each user can then be invited to one or more projects. Furthermore, this user is assigned a specific role in the project. Each role has different usage rights, which influence the available functionalities and the visibility of individual areas in BIMQ. The different roles in a project are:
The roles shown are listed according to their relevance and the associated user rights. The role Reviewer represents the role with the lowest user rights, while the role Manager has the highest possible rights. A superordinate role automatically also always has the rights assigned to the subordinate role. Thus, the rights management in BIMQ is hierarchically structured. If an assigned role has restricted usage rights, this is displayed in the workflow diagram of the BIMQ Project Overview. The corresponding work steps and areas are then grayed out and cannot be selected.
Each role assigned to the user is project-specific. Thus, it is possible that the user is also assigned to a different role in another project. Furthermore, the different roles depend on the scope of services of the respective license.
User Roles in License Free
The user rights of the role Reviewer are very limited in the BIMQ rights management. Basically, he is not allowed to make any changes in the project and is therefore only authorized to read. Furthermore, he has no access to certain areas such as the Model Components or to the area Assign Discipline Models. He is only allowed to view and comment on the assignments and mapping definitions in the area Project Requirements. Comments can be stored in the column provided for this purpose, including name and time stamp.
Participants who do not belong to the organization can be invited to the respective project with the role Reviewer. However, the role Reviewer cannot itself assign new participants to a project.
The role User has the same rights and restrictions as the role Reviewer in the Free license. He is also only allowed to view and comment on assignments and mapping definitions in the area Project Requirements.
Like the Reviewer, persons who do not belong to the organization can also be invited to the respective project with the role User. Exports are not permitted in the license Free. The role User is also not allowed to assign new participants to a project by himself.
The role Configurator is also not allowed to make changes to the content of the project. He also has only limited access to the various areas and is not able to view or edit the areas Model Components, Assign Discipline Models or Project Settings. In addition to the comment function, he is allowed to define the different combinations of Milestones and Use Cases in the area Project Requirements. These define which exchange requirements are required and should be exported. However, exports are generally not permitted in the license Free. The role Configurator cannot invite new participants to a project.
The user role Developer is able to define and specify exchange requirements. This is only allowed in the area Project Requirements. The structuring as well as the assignment of properties, geometries or property groups to elements and to a specific discipline model also takes place in this area. Furthermore, the mapping to a specific software, IFC format, classifications or languages is enabled. The requirements defined here, can in turn be linked to the various combinations of milestones and use cases. The role Developer does not have access to the areas Model Components and Assign Discipline Models. Project settings are visible but cannot be edited. However, it is possible to link use cases to project phases. The Developer is authorized to invite participants with limited user rights (Reviewer, User). Exports are generally not permitted in the license Free.
The Coordinator is able to define and specify exchange requirements. The area Model Components, which can basically be understood as a kind of library, is also available to him for this purpose. Here, all data requirements can be defined once and provided with additional information, such as mapping to IFC, software, classification or languages. The data stored here can then be used multiple times in the area Project Requirements. The assignment of properties, geometries or property groups to elements and to a specific discipline model is done easily and efficiently via the compartment area Assign Discipline Models. Furthermore, the Coordinator is authorized to access the contents of publicly accessible catalogs or assigned projects. Project Settings can be viewed and edited. Creating new projects or copying them is not allowed. The role Coordinator is only authorized to invite participants with limited user rights (Reviewer, User). Exports are generally not permitted in the license Free.
The role Manager has the greatest possible user rights in the BIMQ rights management. He has access to all functionalities and areas available in BIMQ if these are supported by the license. The Manager is authorized to invite participants who do not belong to the Organisation with limited user rights (Reviewer, User) or BIMQ users with maximum Manager rights. Exports are generally not permitted in the license Free. This also applies to copying or creating new projects.