| The pa_process_variants Table | Scroll Previous Topic Top Next Topic More | 
This table contains information on each process variant that has been detected by the MPM Process Mining methods.
| Field name | Explanation | 
|---|---|
| ProcessPathUniqueNo (Key) | Unique Number for a process variant, used to link the table to the pa_activity_log_Helpdesk. | 
| ProcessStartsWithActivityTypeID | ActivityTypeID for the first activity of a variant, can be used as a filter. | 
| ProcessStartsWithActivityType | Activity Type name for the first activity of a variant, can be used as a filter. | 
| ProcessEndWithActivityTypeID | ActivityTypeID for the last activity of a variant, can be used as a filter. | 
| ProcessEndWithActivityType | Activity Type name for the last activity of a variant, can be used as a filter. | 
| For each activity there is a field with the ActivityName. The values are 0 and 1. The field is used to filter on variants that include(1)/exclude(0) that activity (e.g. Insert ticket -> 1, filter all variants with Insert Ticket). | |
| pathVariant_Counter | Field to efficiently calculate the distinct number of process variants. | 
| ParetoPercentage | Cumulative number of cases covered by the process variant and the more frequent variants. | 
| ParetoClassVariant | The field has three different values: A, B and C. These values describe the process variants by ABC-Analysis. A-variants are the most common process variants that make up 80 percent of all cases. B-variants are those variants that cover the next 15% of cases and the last 5% of cases are covered by the C-variants. | 
| VariantComposition | The variant composition describes by which activity types a process variant is composed. The possible values are A; A,B ; A,B,C ; A,C ; B; BC and C. | 
| AVGWaitingTimeOnNextActivity | Field from the process path continuation calculation. Avg waiting time for the next activity, if the process is not finished. |