Exploring deviations between your process and the target process
Open your target model.
Click Deviation Explorer
.The Deviation Explorer panel opens.
Note
The Conformance Rate shows the percentage of events in your actual process that conform to the target model process for each object type. If the Conformance Rate is 100%, for example, your actual process conforms exactly to the target model. The color key for the process graph is shown in the Deviation Explorer panel.
In the process graph, click a colored line to select the object type you want to explore.
In Actual behavior, view the:
Event where the deviation occurs.
Percentage of objects the deviation occurs in.
Impact on the throughput time caused by this deviation.
Object type where this deviation occurs.
Click the Filter on this behavior button for any deviation to see flows that contain that specific deviation.
Click any deviation in Actual behavior to view more details about that deviation.
The dashed line shows where the deviation occurred. Here, this is the location of the missing events.
Click the Breakdown of dimensions button to view a table that displays the object attributes and values that are most frequently related to the selected deviation.
Understanding deviation categories
Deviation category | Description |
|---|---|
Missing event | An event that is required in the target model but does not occur. |
Occurred too often | An event that should only happen once in the target model but occurs multiple times. This could be because of a loop or duplicates. |
Occurred out of sequence | An event that was required in the target model but occurs in the wrong place in the process flow. |
Violated exclusive gateway | Two possible events occur at a point in the process where only one event should occur.orOne or more events that should occur sequentially do not occur at all. |
Deviation category examples
The Create Customer Invoice event or a neighboring event is missing from the Sales Order Item object.
 |
In the first deviation shown, events are missing between the Create Sales Order Item and End events in this process, with Create Customer Invoice missing for 444.9K Sales Order Items, causing an 18-day reduction in the overall throughput time.
In the second deviation shown, the Create Customer Invoice event is missing between the Create Delivery Header and End events in this process for 173.3K Sales Order Items, reducing the overall TPT by nine days.
The Create Sales Order Schedule Line event for the Sales Order Item object (light purple) occurred too often for 5.27% of objects and resulted in a longer process completion time of 20 days on average.
 |
In the first deviation below, Create Sales Order Schedule Line occurred repeatedly after itself (in a loop) between 1 and 83 times. This caused an average delay of 17 days in throughput time.
In the second deviation, Create Sales Order Schedule Line occurred repeatedly after the Create Customer Invoice event between 1 and 35 times.
 |
The Create Customer Invoice event for the Sales Order Item object occurred out of sequence for 0.01% of objects and had an impact on the throughput time of 342 days.
 |
The Occurred out of sequence details card provides the scenarios from your process data, where the Create Customer Invoice event occurred at the wrong sequence for the Sales Order Item (light purple) object.
The Create Customer Invoice event occurred unexpectedly after the Create Sales Order event, instead of the Create Delivery Header event as shown in the process graph.
The Approve Sales Order event for the Sales Order Delivery object violated an exclusive gateway design for 3.25% of objects and resulted in an increased throughput time of five days.
 |
The Violated exclusive gateway card then provides the scenarios based on your process data, where the Approve Sales Order event violated the exclusive gateway design for the Sales Order object (dark purple).