BI Shows

BI shows 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

Updated: 09.10.2024 | Adapted to Vertec 6.7.0.10.

In order to display the data in the Business Intelligence (BI) view, so-called BI shows must be defined. These can be found in the folder Settings > BI Shows:

Each of these BI shows represents an evaluation in the BI module:

A BI display 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 is No Role, the same display can be used for both individual objects and lists.

Selection

The selection defines where the display is displayed.

Classes

Defines for which class(s) this display is defined, i.e. where evaluations are available.

Expression

An expression is required if the selected class does not have KPI 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 Kpi.

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 display come from, not how they are displayed.

Grouping

The grouping defines BY WHAT the numbers in this display are GROUPED.

Month	If a report 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 Kpi are simply grouped according to the available objects, in the example above according to your own projects. The class specified here must be available as a dimension on the Kpis 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 it is now specified as OCL expression `customer`. This refers to the model (detail): this means that in this case the project figures are displayed 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 editor location. To do this, we group the display by project users and select the keyword folder “User by location” as the folder: In the evaluation, a tab “By location” appears, which groups the numbers accordingly:

Creating a projection

As an example, we use a Service Categories folder structure. 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 display. Since we want to show the projection on users, we select users as selection. When grouping, we select the class that we have assigned in the folder structure. In our case, these are project phases.

If an user or a list of users is selected in the BI view, the evaluation called Service Categories appears, in which all the 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 editor lists and individual users.
All defined KPI 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 subfolders property must be set.
The folder must have at least one subfolder.
The subfolders may be a “normal folder,” SQL folder (from version 6.7.0.10) or Expression folder (from version 6.7.0.10), but not a Query folder.
All subfolders must have the same class.

WHAT is shown, i.e. which numbers, is defined by the BI KPI. This does not have to be specified when defining the display.

Standard BI Shows

A variety of predefined BI shows are supplied by Vertec as standard.

Classes	designation	Expression	Grouping / Expression	Significance
address	Time series	`projects`	Month	On individual objects: Total project values for this customer, per month.
address	Overview	`projects`	Project / `customer`	Total project values per customer.
address	Projects as a customer	`projects`	project	Values per project of the individual customer) in the list. Corresponds to the project overview.
address	user	`projects`	user	Values per user on projects of the individual customer or customers in the list.
address	Service types	`projects`	Servicetype	Values per service type on projects of each customer or customers in the list.
address	Phases	`projects`	Phase	Values per project phase of projects of the individual customer) in the list.
address	Time series	`projects`	Month	On lists: Aggregate values across all customers on the list, per month.
project	Time series		Month	On individual objects: Sum values for this project, per month.
project	Overview		project	Values per project
project	Customers		Project / `customer`	Values grouped by customers
project	user		user	Values grouped by users
project	Service types		Servicetype	Values grouped by service type
project	Phases		Phase	Values grouped by phases
project	Time series		Month	On List: Aggregate values across all projects in the list, per month.
user	Time series		Month	On individual objects: Sum values for this user, per month.
user	Overview		user	Values per user
user	Projects		project	Editor values grouped by projects
user	Customers		Project / `customer`	Editor values grouped by customers
user	for project leaders		Project `manager`	Editor values grouped by project leader
user	for key users		Project / `Keyuser`	Editor values grouped by key user
user	Service types		Servicetype	Editor values grouped by service type
user	Own projects	`own projects`	project	Numbers of the user’s own projects, grouped by projects
user	Users own projects	`own projects`	user	Numbers of the user’s own projects, grouped by user
user	Time series		Month	On List: Aggregate values across all list users per month
Phase	Time series		Month	On individual objects: Sum values for this project phase, per month
Phase	Overview		Phase	Values per project phase
Phase	service type		Servicetype	Project phase values grouped by service type
Phase	project		project	Project phase values grouped by project
Phase	user		user	Project phase values grouped by user
Phase	Time series		Month	On lists: Total values across all project phases of the list per month
Servicetype	Time series		Month	On individual objects: Sum values for this service type, per month
Servicetype	Overview		Servicetype	Values per service type
Servicetype	user		user	Activity values grouped by user
Servicetype	project		project	Activity values grouped by project
Servicetype	Customers		Project / `customer`	Activity values, grouped by customers
Servicetype	Time series		Month	On lists: Aggregate values for all service types on the list per month