CALC_THROUGHPUT
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. The resulting column is temporarily added to the case table and returns the throughput time between the two specified activities per case.
Syntax
CALC_THROUGHPUT ( begin_range_specifier TO end_range_specifier, timestamps [, activity_table.string_column ] )
begin_range_specifier: FIRST_OCCURRENCE['activity'] | LAST_OCCURRENCE['activity'] | CASE_START | ALL_OCCURRENCE['']
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_OCCURRENCE['']: Has the same meaning as CASE_START. The string parameter is ignored, but has to be specified. [ DEPRECATED | Use CASE_START instead.]
end_range_specifier: FIRST_OCCURRENCE['activity'] | LAST_OCCURRENCE['activity'] | CASE_END | ALL_OCCURRENCE['']
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_OCCURRENCE['']: Has the same meaning as CASE_END. The string parameter is ignored, but has to be specified. [ DEPRECATED | Use CASE_END instead.]
timestamps: Integer column of an activity table, often REMAP_TIMESTAMPS is used to convert a TIMESTAMP column.
activity_table.string_column: A string column of the same activity table as provided in the timestamps column. By default, the activity column of this activity table is used. The range specifiers are evaluated based on this 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.
If the activity name used in FIRST_OCCURRENCE or LAST_OCCURRENCE does not exist, then a warning is displayed. In this scenario the result value will be null.
Use Cases
CALC_THROUGHPUTcan be used for Working Capital Optimization.
Examples
[1] The throughput is calculated for the first A activity and the first B activity. | |||||||||||||||||||||
| |||||||||||||||||||||
|
[2] 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. | |||||||||||||||||||||
| |||||||||||||||||||||
|
[3] 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. | ||||||||||||||||||
| ||||||||||||||||||
|
[4] The throughput is calculated for the last A activity and the last B activity. | |||||||||||||||||||||
| |||||||||||||||||||||
|
[5] The throughput is calculated for the first A activity and the last B activity. | |||||||||||||||||||||
| |||||||||||||||||||||
|
[6] The throughput is calculated for the first A1 activity and the last B1 activity with a custom activity expression. | |||||||||||||||||||||
| |||||||||||||||||||||
|
[7] The throughput is calculated from the beginning of the case till its end. | |||||||||||||||||||||
| |||||||||||||||||||||
|
[8] CALC_THROUGHPUT query using non-existing activity in FIRST_OCCURRENCE: Empty result and warning. | |||||||||||||||||||||||||||
| |||||||||||||||||||||||||||
|