Skip to main content
Version: v2.5

Define Subprocesses in the mpmX EventLogGeneration Apps

The subprocesses inline table is used to define partial processes for which customized lead times and other time‐related measures will be calculated. While the standard lead time (from the start to the end of a case) provides an overall view, it does not offer the granularity needed for comparing performance on specific parts of a process. By defining a subprocess with a specified start and end activity, you can calculate a more focused lead time as well as derive the average durations and waiting times for that segment.

Standard vs. Subprocess Lead Times​

  • Standard Lead Time:
    Calculated from the beginning of a case to its end, independent of individual activities.

  • Subprocess Lead Time:
    Defined between a specified start- and end-activity, allowing you to focus on particular segments of a process. This calculation can help you monitor performance and identify delayed cases within a subprocess. It 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.

How to Define Subprocesses​

To configure subprocesses, follow these steps:

  1. Navigate to the Configuration File:
    Open the inline table SubprocessDefinition_$(mvProcessDescription) located in
    mpmX_repository/[mvProcessDescription]/mpmX_config_repository.qvs.

  2. Set a Qualifier:
    This qualifier serves as a prefix for the calculated fields.

  3. Specify the Start and End Activities:

    • Enter the StartActivity and EndActivity values.
    • If several activities can serve as the start or end, separate the values with a pipe symbol (|).
      • Example 1: Record Service Entry|Record Goods Receipt
      • Example 2: Take in charge ticket|Insert ticket

  4. Include or Exclude Activities:
    For both the start and end activities, set:

    • IncludeStartActivity and IncludeEndActivity to "y" (yes) or "n" (no) depending on whether you want the activity included in the time calculation.

  5. Select the Event Occurrence:

    • Use MinMaxStartActivity to decide whether the first (Min) or last (Max) occurrence of the start activity should be used.
    • Likewise, set MinMaxEndActivity for the end activity.

  6. Optional Target Time Settings:

    • Enter a number in TargetTime that represents your goal (for instance, 60 days).
    • In TargetTimeOperator, enter an operator such as < or > to determine which subprocess runs are considered delayed.
      • Example: Setting a target time of 60 and an operator < means any subprocess taking 60 days or longer is flagged as delayed.
info

Fallback Defaults:

If TargetTime and TargetTimeOperator are left blank, the system will use the general variables (mvPercentageTimeLimit and mvPercentageTimeLimitOperator) defined in the file mpmX_scripts/[[version]]/customizing/[mvProcessDescription]/custom_variables.qvs. For example, if these variables are set to mvPercentageTimeLimit = 0.9 and mvPercentageTimeLimitOperator = <, then the fastest 90% of subprocess runs are marked as good while the slowest 10% are flagged as delayed.

  1. Outcome:
    Once defined, the CaseTimes table is enhanced by adding a new row per case that includes the subprocess data.

Example Inline Table Definitions​

Below are two example configurations. Choose or adapt the one that best fits your process:

// Example 1:
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,              >
];
// Example 2:
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,         >
];