|
Define Subprocesses |
Scroll Previous Topic Top Next Topic More |
The subprocesses inline table is used to define partial processes for which the lead time and other time related measures will be calculated. Using the module "Subprocesses" is an optional feature, so its configuration is placed on the script tab 2A. Advanced Customization.
The standard lead time that is calculated reaches from the start of a case till its end, independently of the occurring activities. Thus, it gives a good overview on the case's overall lead time but is not the perfect choice if you need to compare cases on a subprocess level. The subprocess feature provides the possibility to define customized lead times between a specified start- and end-activity. This can be used to calculate a main lead time with specified start and end or to calculate certain subprocess' lead times. The algorithm will calculate the subprocess as well as the average sum of activity durations and waiting times for each subprocess and their respective lead time classes.
To define subprocesses, perform the following steps:
1.Navigate to the inline table SubprocessDefinition_$(mvProcessDescription).
2.Set a qualifier. Will be used as a prefix for the calculated fields.
|
When setting the qualifier, no spaces are allowed. |
3.Set the start and end activity for the sub-process into the fields StartActivity and EndActivity.
4.If several activities can be the start or the end activity, seperate the different values by a |
| Example: Take in charge ticket|Insert ticket |
5.Define, if the start activity should be in- or excluded into the custom lead time by setting "IncludeStartActivity to "y" for yes or "n" for no.
| The same can be done for the end activity in the field IncludeEndActivity. |
6.To define if the first or last of the start activities (in case of several events beeing found) should be used to calculate the subprocess set MinMaxStartActivity to Min for using the first or to Max for using the last event's timestamp.
6. The same can be done for the end activity in the field MinMaxEndActivity.
7.Enter a number that represents your target time, or target goal, in the column TargetTime.
8.In the last column, TargetTimeOperator, enter an operator symbol such as greater than or less then.
| For example, if your goal was to get your payment process lead times to under 60 days, then you would enter a 60 in the Target Time column, and a less than symbol in the Target Time Operator column. |
[SubprocessDefinition_$(mvProcessDescription]:
Load * Inline [
Qualifier, |
StartActivity, |
IncludeStartActivity, |
MinMaxStartActivity, |
EndActivity, |
IncludeEndActivity, |
MinMaxEndActivity, |
TargetTime, |
TargetTimeOperator |
WIP, |
Take in charge ticket|Insert ticket, |
y, |
Max, |
Wait|Require upgrade, |
n, |
Min, |
60, |
< |
WIP_old, |
Take in charge ticket, |
y, |
Min, |
Wait, |
n, |
Max, |
45, |
> |
];
Further information can be found here: Learn how to Use Subprocesses in the Analysis.
