|
Define Custom Lead Times in the MPM EventLogGeneration Apps |
Scroll Previous Topic Top Next Topic More |
The CustomLeadTimes inline table is used to define sub-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 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 sub-process level. The custom lead times feature provides the possibility to define custom 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 custom lead time as well as the average sum of activity durations and waiting times for each subprocess and their respective classes.
To define custom lead times, perform the following steps:
1.Navigate to the tab 2A. Grouping & Custom Lead Times
2.Set a qualifier. 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: 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 custom lead time, 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. |
CustomLeadTimes:
Load * Inline [
Qualifier, |
StartActivity, |
IncludeStartActivity, |
MinMaxStartActivtiy, |
EndActivity, |
IncludeEndActivity, |
MinMaxEndActivity |
WIP, |
Take in charge ticket|Insert ticket, |
y, |
Max, |
Wait|Require upgrade, |
n, |
Min |
WIP_old, |
Take in charge ticket, |
y, |
Min, |
Wait, |
n, |
Max |
];
The CaseTimes table will be enhanced by six new fields for each custom lead time. The custom lead time will be calculated between the start and end activities. If there are some cases that don’t have both of these activities, the calculated fields will be null(). The fields below belong to the beforehands defined custom lead time "WIP":
1.WIP_StartDate
2.WIP_EndDate
3.WIP_LeadTime
4.WIP_FormatCLT
5.WIP_LeadTimeClass
6.WIP_formatted_LeadTime
Further information can be found here: Learn how to Use Custom Lead Times in the Analysis.
