Free cookie consent management tool by TermsFeed Variants [Process Mining v5.9]
Page not found in the selected version; redirected to the home page.
Variants
Process Mining is deprecated with Appian 24.2 and will no longer be available in an upcoming release.

Instead, we encourage customers to use Process HQ to explore and analyze business processes and data.

This page introduces the concept of a variant in Process Mining, discusses why they're useful, and explains how to interpret variants within a process.

What is a variant?

Under ideal circumstances, a process is completed from start to end in the same way every time. Activities are performed in the same order, take the same amount of time, and lead to the same outcome. But circumstances are rarely the same every time, which means that the process might not happen the same way each time.

A variant is a unique occurrence of a process. For example, consider a hotel check-in process:

  1. Locate the reservation in the system.
  2. Request the guest's credit card and identification.
  3. Look for and assign an available room to them.
  4. Provide the guest with keys and directions on how to find their room.

These four steps comprise the ideal process from start to finish. But what happens if there is no available room? Now there's another step:

  1. Locate the reservation in the system.
  2. Request the guest's credit card and identification.
  3. Look for an available room.
  4. Adjust the reservation to include a lower priced room that's available immediately.
  5. Assign the room to them.
  6. Provide the guest with keys and directions on how to find their room.

Now there are two additional steps in the process that cost both time and money. The front desk worker must spend more time to locate an available room and negotiate with the guest to determine if the change is acceptable. This also costs money by requiring a price adjustment for a room that's cheaper than the one reserved originally.

This adjust process completed successfully, but it's not the ideal version. The second version of this process, with the additional steps, is an example of a variant.

View variants

The variant page displays all your process variants. You can use filters or the search function to change the variants and information that appear on this page. If not all variants appear, you can adjust the settings in the Number of Variant Groups filter.

List of variants

This page displays information such as:

  • The variant
  • The number of cases that pass through this variant
  • The average lead time
  • The individual activities in the order they were processed

Click the column headers to change how the data is sorted.

If a target model is available, the activities are highlighted to indicate how they relate to the target process:

  • Additional Work: This activity is repeated or doesn't appear in the target model.
  • Skipped: This activity didn’t occur.
  • Switched (Target): Expected position this activity should occur.
  • Switched (Actual): Actual position this activity occurred.

If not all activities of the process are displayed in the panel, you can scroll left or right through the process to see the remaining activities.

Tip:  Sometimes the Activities column displays fewer activities than exist in your process. Activities are omitted for a couple reasons:

  • When an activity only exists in the target model and no cases.
  • When activities are skipped at the end of the sequence, the case is assumed to not be finished yet.

To download the list of variants, open the Export Menu in the toolbar. Click Export CSV. The file downloads to your computer.

Export CSV option in Export menu

How variants appear in a target model

Deviations and variants are related concepts in Process Mining. A deviation is a change in an activity, and a variant is a unique execution of a process. A variant may contain one or more deviations, or it could contain none at all.

Deviations and variants are two entry points to analyze your processes. Deviations appear in the Target Model. Variants appear in the Target Model as well, but may exist even if no Target Model is defined.

Deviations and variants are represented in the Target Model using these icons:

Icon Deviation type Description Related variants
Additional Work This activity is repeated or doesn't appear in the target model. For example, because there is a loop in the process.
  • Insert
  • Approved insert
Skipped This activity didn't occur.
  • Skip
  • Approved skip
Switched This activity occurred at an unexpected position.
  • Switch insert
  • Switch skip
  • Approved switch insert
  • Approved switch skip

View all cases of a variant

To see a list of all cases that have run through a process variant, click the variant name.

Show cases for variant

The list includes details such as:

  • case ID
  • start and end time
  • case duration
  • duration of the entire event
  • total waiting time

For cases with many attributes, use the scroll bar at the bottom to view more information.

A case attribute is a piece of data that is true for the whole execution. Attributes are independent from the executed activities. For example, if your business produces cars, the engine type or the side of the steering wheel would be attributes. Values for a case attribute can change from case to case.

The arrow in the upper left-hand corner of the screen takes you back to the previous view (variant overview).

View an individual case

To view detailed information about specific case, click the case name.

pm-show-events

The list shows:

  • activity names
  • start and end times
  • resulting activity duration
  • option to display the attributes of the case
  • duration of wait time between activities

pm-view-events

To view more information about the attributes, click Show all attributes next to the number in the Attributes column. Click Hide attributes to collapse this information.

An event attribute is a piece of data in a single event that is true for only one execution of this event. Due to this, the count of an event attribute can be higher than the case count of the log. For example, the employee who executed the event or the system where the event occurred would be event attributes. Values for an event attribute can change from event execution to event execution.

To navigate the pages in the list, use the options below the list. 10 activities appear on each page by default, but you can change this value. The arrow in the upper left-hand corner of the screen takes you back to the previous view (list of cases).

To export the list, click the download icon in the top right corner and select Export case table. The list is exported as a CSV file containing all the variants selected by the current filters.

Analyze specific variants

To help focus your analysis, you can filter the variants to display only graphics, statistics, or metrics for the selected variants.Use the checkboxes to select the variants of interest.

To add a variant as a filter:

  1. Select the checkbox next to a variant.
  2. Click ADD AS FILTER.

pm-variant-filter-banner

Variants

FEEDBACK