|
Define Subprocesses in the MPM EventLogGeneration Apps |
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.
The standard lead time that is calculated reaches from the start of a case until 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 sub-process level. The subprocess feature provides the possibility to define partial processes 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 partial process and their respective classes.
To define subprocesses, perform the following steps:
1.Navigate to the tab 2A. Grouping
2.Set a qualifier. This will be used as a prefix for the calculated fields.
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: Payment Process|Record Goods Receipt |
5.Define, if the start activity should be in- or excluded into the subprocess 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.
| 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 |
Payment Process, |
Record Service Entry|Record Goods Receipt, |
y, |
Max, |
Pay Invoice, |
n, |
Min, |
60, |
< |
WIP, |
Take in charge ticket, |
y, |
Min, |
Wait, |
n, |
Max, |
45, |
> |
];
The CaseTimes table will be enhanced by a new row per case that includes the sub process.
