BI views
BI views for displaying the data in the business intelligence view
Product line
Standard
|Expert
Operating mode
CLOUD ABO
|ON-PREMISES
Modules
Services & CRM
Budget & Phases
Purchases
Resource Planning
Business Intelligence
Created: 22.04.2020
Machine translated
Updated: 09.10.2024
|
Terminology “subfolder” adapted.
In order to be able to display the data in the business intelligence (BI) view, so-called BI views must be defined. These can be found in the folder Settings > BI views:
Each of these BI views represents a view in the BI module:
A BI view has the following properties:
| designation | The designation of the evaluation is shown as a label for the tabs in the BI view.
 This is an MLString field. |
| Active |
Defines whether an evaluation is shown in the BI view. |
| Order |
Defines the order in which the tabs are displayed in the BI view. |
| Applied to individual object / list |
Defines whether the evaluation is available on individual objects and / or on lists of objects. Shows that have defined the same class under selection and grouping make little sense on individual objects, as they then only show a single bar for themselves. If certain evaluations are to be displayed on lists in a different order than on individual objects, they must be defined once for individual objects and once for lists:  If the order does not play a role, the same view can be used for both individual objects and lists. |
Selection
The selection defines where the view is displayed.
| Classes |
Defines for which class(es) this view is defined, i.e. where evaluations are available. |
| Expression |
An expression is required if the selected class does not have measures that can be evaluated. This is the case for addresses, for example. In this case, an OCL expression must be specified, the result of which is an object (or a list of objects) that has measures. This does not refer to WHAT is shown in the evaluation. This is what defines the grouping. So it is only about where the numbers for the view come from, not how they are displayed. |
Grouping
The grouping defines BY WHAT the numbers in this view are GROUPED.
| Month |
If a view is grouped by month, it is displayed as a time series. In this case, the following grouping options are hidden. |
| Classes |
This specifies the classes by which the numbers are grouped. For the overview here in the example, the numbers are grouped by project, i.e. by the same class that is also specified in the selection. If no expression is specified, the measures are simply grouped according to the available objects, in the example above according to the owned projects. The class specified here must be available as a dimension on the measures to be displayed. |
| Expression | With this expression, the grouping can be further refined. It is applied to the result objects according to “Class”. The results are then grouped and displayed using this expression. Here as an example the evaluation “Customers”. The grouping class is also a project, but unlike the overview, the OCL expression kunde is now specified here.
 This refers to the model (detail):  this means that in this case the project numbers are grouped by customer address.  |
| folder |
Instead of an expression, a folder can be specified. In this case, the numbers are grouped by subfolders of the specified folder (“projection”). The folder or its subfolders must contain objects of the classes specified as the grouping. In the following example, we want to display the project numbers grouped by user location. To do this, we group the view by project users and select the folder keyword “user by location” as the folder:  In the evaluation, a tab “By location” appears, which groups the numbers accordingly: 
|
Create a projection
As an example, we use a folder structure Dienstleistungskategorien. A hierarchy level is supported, so we define the structure as follows:
In our example, the service categories contain project phases. Now we define a new BI view. Since we want to show the projection on users, we select Bearbeiter as selection. When grouping, we select the class that we have assigned in the folder structure. In our case, these are Projektphasen.
If a user or a list of users is selected in the BI view, the evaluation named Dienstleistungskategorien appears in which all performance figures of the users are grouped according to service categories:
- Any calculated class can be projected, no longer just project phases.
- The “Projection” is automatically available on all objects of the selected class, so in our example not only on the “User” folder, but on all user lists and individual users.
- All defined measures are automatically available on the new evaluation.
Folder Comparisons
If a folder is selected in the BI view, which contains subfolders with BI-selectable objects, a comparison view automatically appears on it, which shows the data grouped according to the folders in which they are located. There is no need to create a BI view. The first hierarchy level is taken into account.
The following conditions must be met for a folder comparison to take place:
- The Allow subfolder property must be set.
- The folder must have at least one subfolder.
- The subfolders must be normal Folder , as of Vertec 6.7.0.10 Sql folder , Expression Folder and Query Folder are also allowed.
- All subfolders must have the same class.
WHAT is displayed, i.e. which numbers, is defined by the BI measures. This does not have to be specified when defining the view.
Standard BI Views
A variety of predefined BI views are supplied by Vertec as standard.
| Classes | Designation | Expression | Grouping / Expression | Significance |
| address | Time series | projekte |
Month | On individual objects: Total project values for this customer, per month. |
| address | Overview | projekte |
Project / kunde |
Total project values per customer. |
| address | Projects as a customer | projekte |
project | Values per project of the individual customer or customers in the list.
Corresponds to the project overview. |
| address | user | projekte |
user | Values per project user on projects of the individual customer or customers in the list. |
| address | Types of services | projekte |
Servicetype | Values per type of service on projects of the individual customer or customers in the list. |
| address | Phases | projekte |
ProjectPhase | Values per project phase of projects of the individual customer or customers in the list. |
| address | Time series | projekte |
Month | On Lists: Aggregate values across all customers on the list, per month. |
| project | Time series | Month | On individual objects: Summed values for this project, per month. | |
| project | Overview | project | Values per project | |
| project | Customers | Project / kunde |
Values grouped by customer | |
| project | user | user | Values grouped by users | |
| project | Types of services | Servicetype | Values grouped by type of services | |
| project | Phases | ProjectPhase | Values grouped by phases | |
| project | Time series | Month | On Lists: Aggregate values across all projects in the list, per month. | |
| user | Time series | Month | On individual objects: Summed values for this user, per month. | |
| user | Overview | user | Values per project user | |
| user | Projects | project | Editor values grouped by projects | |
| user | Customers | Project / kunde |
Processor values grouped by customer | |
| user | for project leaders | Project / projektleiter |
Editor values grouped by project leader | |
| user | for key users | Project / hB |
User values grouped by main user | |
| user | Types of services | Servicetype | Editor values grouped by service type | |
| user | Own projects | eigprojekte |
project | Numbers of the user’s own projects, grouped by projects |
| user | Users own projects | eigprojekte |
user | Numbers of the user’s own projects, grouped by user |
| user | Time series | Month | On Lists: Aggregate values across all users of the list per month | |
| ProjectPhase | Time series | Month | On individual objects: Summed values for this phase of the project, per month | |
| ProjectPhase | Overview | ProjectPhase | Values per project phase | |
| ProjectPhase | service type | Servicetype | Project phase values grouped by type of service | |
| ProjectPhase | project | project | Project phase values grouped by project | |
| ProjectPhase | user | user | Project phase values grouped by user | |
| ProjectPhase | Time series | Month | On lists: Aggregate values across all phases of the list per month | |
| Servicetype | Time series | Month | On individual objects: Summed values for this type of service, per month | |
| Servicetype | Overview | Servicetype | Values per type of service | |
| Servicetype | user | user | Activity values grouped by user | |
| Servicetype | project | project | Activity values grouped by project | |
| Servicetype | Customers | Project / kunde |
Activity values grouped by customer | |
| Servicetype | Time series | Month | On lists: Aggregate values for all types of services on the list per month |