If a factory and shift calendar is provided, the process times can be displayed as "net process times" in the front end. You can decide to only use these net times in the app or to have both types of time representation in the app and switch the whole app from gross to net process times and back with a button.

 

Gross process time is the interval between two timestamps by just calculating their delta while the net process time is the delta between two timestamps expressed in working hours only. Breaks, holidays, weekends or shift-ends are subtracted. The mpmX Template App provides a factory and shift calendar template for easy reuse. The steps are explained below. Of course, the template can be replaced by a custom calendar, provided, that the format of the custom calendar is adapted as explained in step 5.

 

Please note, that every time-related measure is provided as net time if the factory and shift calendar is used, except for the ProcessStepDuration: This time measure is not converted to net, because times outside of the shifts cannot be calculated. Therefore, if overtime would have worked, it would not be recorded. Instead NetProcessStepDuration is set to ProcessStepDuration and an overtime flag is calculated, which shows whether this process time has been worked outside of the shifts, i.e. in overtime. It is assumed that the process step times are recorded in such a way that the process time counts as net time (i.e. breaks, shift ends are booked out). Should this not be the case, the total net process time may be a bit too high.

 

When using the factory and shift calendar a new PPI AVG/Med Workdays becomes available. This PPI counts the workdays where the case was open, which gives a more accurate measure on the net work days than the net days shown by the PPI AVG/Med Lead Time:

 

 

To provide a factory and shift calendar, perform the following steps. If the shift calendar is set, all time-related values are expressed as net time:

 

1.Go to the tab 2B. Factory and Shift Calendar in front of tab 3. Initiate Mining Algorithms.

2.Adjust the Data Model's Net and Gross Time Setting.

 

Let mvNetAndGrossTimes = 0;

3.Adjust process step duration settings.

 

Let mvCalculateNetProcessStepDuration = 0;

 

4.Choose if the event calender is calculated.

Choose if you like to calculate the event calender (1) or not (0). Keep in mind: if the calender is calculated, the script performance will be slower. The event Calendar is needed for displaying in which shift an event took place, but this is not the case in most process mining projects. Therefore, the default is 0.

 

Let mvCalculateEventCalender = 0;

 

5.Adjust holiday settings.

If you like to eliminate holidays from the process times, set the variable mvEliminateHolidays to 1.

 

Let mvEliminateHolidays = 1;

 

If you would like to ingore holidays, set  the variable mvEliminateHolidays to 0.

 

Let mvEliminateHolidays = 0;

 

 

6.Choose a holiday calendar.

a)For German holidays: Decide between the 16 German regions or German national holidays only.

Change the values in the variable mvHolidayCalender to the required region. The following values can be set (multiple values can be used, separated by comma):

Bundesweit, Sachsen, Sachsen-Anhalt, Brandenburg,Thüringen, Rheinland-Pfalz, Saarland, Nordrhein-Westfalen, Niedersachsen, Mecklenburg-Vorpommern, Schleswig-Holstein, Hamburg, Bremen, Bayern, Baden-Württemberg, Berlin

 

 

 

Let mvHolidayCalender = chr(39) & 'Bundesweit' & chr(39) & 'Baden-Württemberg' & chr(39);

 

 

b)If you would like to use another holiday calender than the template, refer to the calender-file by the variable mvHoldidayCalenderFile.

 

 

Let mvHolidayCalenderFile = '$(LangAndMasterItemsConnection)/HolidayCalendar_Germany.csv';

 

 

7.Optional: If you do not use the mpmX Template Factory and Shift Calendar, change the calendar-table name.

•Provide the calendar as resident-table before calling the mining algorithms in step three.

•Change the calendars name in the variable mvFactoryShiftCalender. (Default is 'MPMTemplateAppFactoryAndShiftCalender'.)

 

Let mvFactoryShiftCalender = 'MPMTemplateAppFactoryAndShiftCalender';

 

•A calendar to calculate the net process times needs to provide the following information:

 

 

8.If the mpmX Template App Factory and Shift Calendar is used, define the shifts. If you use a custom factory and shift calender then go to step 5.

Several shifts per day can be created by copying the line with the weekday from the inline table and increasing the shift ID in the column "shift".

 

 

Examples:

•If you work around the clock, enter shift "1" and enter "00:00" to "23:59" in startTime. See Tuesday in the table below.

•If, for example, two shifts are worked, startTime and endTime are maintained for one line with shift = 1 and one line with shift = 2 for each weekday. There may be breaks between shifts. See Wednesday or Thursday in the example below.

•If a shift extends beyond midnight, the shift must be split into two shifts: Day 1 from shift start to midnight and day 2 from midnight to shift end. See Friday second shift to Saturday first shift.

 

ShiftTimes:

load * inline [weekday_Event, shift, startTime, endTime