Applies to: CELONIS 4.0 CELONIS 4.2 CELONIS 4.3 CELONIS 4.4
Description
Throughput is used to calculate, for each case, the time between two activities. From which activity the calculated throughput time should start and at which it should end can be configured through range specifiers.
Syntax
CALC_THROUGHPUT ( begin_range_specifier TO end_range_specifier, timestamps )
- begin_range_specifier: FIRST_OCCURRENCE['activity'] | LAST_OCCURRENCE['activity'] | CASE_START | ALL_OCCURENCE['']
- FIRST_OCCURRENCE['activity']: Throughput time starts at the first occurrence of the specified activity type.
- LAST_OCCURRENCE['activity']: Throughput time starts at the last occurrence of the specified activity type.
- CASE_START: Throughput time starts at the first activity of the case.
- ALL_OCCURENCE['']: Has the same meaning as CASE_START. The string parameter is ignored, but has to be specified.
- end_range_specifier: FIRST_OCCURRENCE['activity'] | LAST_OCCURENCE['activity'] | CASE_END | ALL_OCCURENCE['']
- FIRST_OCCURRENCE['activity']: Throughput time ends at the first occurrence of the specified activity type.
- LAST_OCCURRENCE['activity']: Throughput time ends at the last occurrence of the specified activity type.
- CASE_END: Throughput time ends at the last activity of the case.
- ALL_OCCURENCE['']: Has here the same meaning as CASE_END. The string parameter is ignored, but has to be specified.
- timestamps: Integer column, often REMAP_TIMESTAMPS is used to convert a TIMESTAMP column.
If start and end activity is conflicting, meaning the end activity is before the start activity the throughput calculation returns null for the conflicting case. Null is also returned if a case has only one activity.
Examples
The throughput is calculated for the first A activity and the first B activity.
Query
Column1
CALC_THROUGHPUT(FIRST_OCCURRENCE['A'] TO FIRST_OCCURRENCE['B'], REMAP_TIMESTAMPS("Table1"."TIMESTAMP", MINUTES))
Output
Result
| Column1 : INT |
|---|
1 |
Here there is an attempt to calculate the throughput between last B and last A. Since the starting activity (last B)
comes after the ending activity (last A), there is a conflict and NULL is returned.
Query
Column1
CALC_THROUGHPUT(LAST_OCCURRENCE['B'] TO LAST_OCCURRENCE['A'], REMAP_TIMESTAMPS("Table1"."TIMESTAMP", MINUTES))
Output
Result
| Column1 : INT |
|---|
null |
In the special case that start and end activity are the same, null is returned.
In this example start and end are the same because the first and last activity A are pointing to the same activity
log entry.
Query
Column1
CALC_THROUGHPUT(FIRST_OCCURRENCE['A'] TO LAST_OCCURRENCE['A'], REMAP_TIMESTAMPS("Table1"."TIMESTAMP", MINUTES))
Output
Result
| Column1 : INT |
|---|
null |
The throughput is calculated for the last A activity and the last B activity.
Query
Column1
CALC_THROUGHPUT(LAST_OCCURRENCE['A'] TO LAST_OCCURRENCE['B'], REMAP_TIMESTAMPS("Table1"."TIMESTAMP", MINUTES))
Output
Result
| Column1 : INT |
|---|
4 |
The throughput is calculated for the first A activity and the last B activity.
Query
Column1
CALC_THROUGHPUT(FIRST_OCCURRENCE['A'] TO LAST_OCCURRENCE['B'], REMAP_TIMESTAMPS("Table1"."TIMESTAMP", MINUTES))
Output
Result
| Column1 : INT |
|---|
7 |
The throughput is calculated from the beginning of the case till its end.
Query
Column1
CALC_THROUGHPUT(CASE_START TO CASE_END, REMAP_TIMESTAMPS("Table1"."TIMESTAMP", MINUTES))
Output
Result
| Column1 : INT |
|---|
7 |