The CustomLeadTimes inline table is used to define sub-processes for which the lead time and other time related measures will be calculated. Using the module Custom Lead Times 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 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 inline table CustomLeadTimes_$(mvProcessDescription).

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 |

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.

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.

 

CustomLeadTimes: 

Load * Inline [

];

 

 

 

 

Further information can be found here: Learn how to Use Custom Lead Times in the Analysis.

 

Tutorial

 

Start the video below to see a short tutorial about how to use the sheet.