Custom KPI Views are additional KPIs that can bee displayed in the Process Explorer.
You should already be familiar with the default KPIs of the Process Explorer, which are available by default in all Celonis 4 installations.
Choose the KPI views in the same place where you switch between the frequency Process Explorer and the Throughput Time Explorer: 
To add a custom KPI, choose 
at the button of the drop-down menu, listing all existing KPIs.
In a KPI view, the analyst has to define activity KPIs and connection KPIs.
Add a new KPI view with: 
.
You will see all possible configuration options in the right field.
Configure Custom KPIs
Activity KPIs
Connection KPIs
Click on the "Add" button to add a custom activity KPI.
Click on the "New connection KPI" button to create a new connection KPI.
Enter your PQL query in the "Edit Formula" field on the left side. You can make use of the KPI Builder, in order to prevent errors that may arise through misspelling.
This sample activity KPI will show the automatisation rate for each activity, given that there is a generic user in the database (called 'batch') that is used when a process has been automated.
The following PQL query has been used:
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
AVG(CASE WHEN "_CEL_P2P_ACTIVITIES"."USER_TYPE" = 'Batch' THEN 1.0 ELSE 0.0) |
If this activity has been automated, the KPI compiler will return 1.0, if not 0.0. After an iteration over all activities, this query will return a value between 0.0 and 1.0 for all activities.
This sample connection KPI will provide the maximum duration of any case passing the connection (= the maximum throughput time).
The following PQL query has been used:
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
MAX(1.0*DATEDIFF(dd, SOURCE("_CEL_P2P_ACTIVITIES"."EVENTTIME"),TARGET("_CEL_P2P_ACTIVITIES"."EVENTTIME"))) |
This statement again iterates over all cases and compares for every connection the timestamp of the first activity with the timestamp of the last activity. For each connection, the maximum duration is selected and returned.
You can furthermore name your formula, and define formats and units:
Click on 
to proceed.
| Tip | ||
|---|---|---|
| ||
For every custom KPI view, you can add multiple activity KPIs and/or connection KPIs. Simply repeat the instructions above. |
Threshold value
To allow further restrictions on your KPI, you can add Threshold values.
Your activities or your connections can be colored according to definable thresholds.
Let's color all activities, that have an automatisation rate (see above) > 0.5 green.
Save your threshold setting with 
.
| Tip | ||
|---|---|---|
| ||
You can add multiple thresholds. |
Title & Format
You can name your new custom KPI view. This name will be shown in all process explorers throughout this analysis document.
Furthermore, you can select a symbol for your KPI view
Both activity and connection KPIs can be added with the add button. When you add a new KPI or edit it by clicking on the Custom KPI Editor will open:
On the bottom left the formula title and format option can be found. On the right the KPI Builder helps the analyst to quickly add columns from your dataset.
It is possible to add multiple KPIs to the KPI view. These KPIs will be separated by "|" when they are displayed in the process graph:
You can choose between different icons that will be displayed in the Process Explorer afterwards:
Save your changes with .
The process nodes and connections can be formatted according to the custom KPIs. The analyst can define thresholds for the colors based on a formula in the custom KPIs:
Useful activity KPIs could be:
Name | Example |
|---|---|
Last Timestamp | MAX(ROUND_MONTH("EVENTLOG"."EVENTTIME")) |
Automatisation | AVG(CASE WHEN "EVENTLOG"."USERTYPE"='Batch' THEN 1.0 ELSE 0.0 END) |
Value flow | ROUND(SUM("EVENTLOG"."ACT_Wert"),0) |
Useful connection KPIs could be:
Name | Example |
|---|---|
Duration | AVG(1.0*DATEDIFF(dd, SOURCE("EVENTLOG"."EVENTTIME"), TARGET("EVENTLOG"."EVENTTIME"))) |
Automatization | AVG(CASE WHEN TARGET("EVENTLOG"."USERTYPE")='Batch' THEN 1.0 ELSE 0.0 END) |
Value flow | ROUND(SUM(TARGET("EVENTLOG"."ACT_Wert")),0) |