Conformance checking

Note:

Depending on the process, a process-specific name is displayed to identify Cases, for example, Purchase order items, or Incidents.

The Conformance checking dashboard contains information that will help you determine whether the process complies with the Discover process model or the Import BPMN model. It enables you to detect inefficiencies, compliance issues, process enhancement opportunities, and discrepancies between the actual process and the reference process model.

Note:

The Conformance checking dashboard is only available for apps that are using a process model. Which means process apps that were created using the Discover process model or the Import BPMN model.

Creating an app using the Discover process model or the Import BPM model

Create a new process app
In the Select the process model step, select Discover process model or Import process model.

See also Working with Discover process models and Import BPMN models.

Deviation types

See the following overview of available deviation types and a related example deviation.

Deviation type	Example deviation	Description
Activity retry	"Activity <activity A> is repeated"	Activity was repeated multiple times in a row.
Exclusive choice violation	"Activity <activity A> is followed by activity <activity B>"	Multiple activities from the exclusive choice block were executed when only one was expected.
Skip	"Activities <activity A> and <activity B> are skipped"	Activity was skipped. This can mean that the activity is skipped altogether or done out of order.
Incomplete parallel bloc	"Activities <activity A> and <activity B> are skipped"	Not all activities in the parallel block were executed.
Invalid activity	"Activity <activity A> is an undesired activity"	Activity was not expected to happen at all.
Invalid start	"Activity <activity A> is executed as start activity"	Activity was not expected to start the process.
Invalid end	"Activity <activity B> is executed as end activity"	Activity was not expected to end the process.
Loop back	"Case loops back from activity <activity A> to activity <activity B>"	Activity unexpectedly loops back to a previous one.
Unknown	Unknown non-conforming behavior from activity <activity A> to activity <activity B>"	Behavior does not conform to the model and is not recognized.

Displaying the Conformance checking dashboard

Follow this step to display the Conformance checking dashboard.

Select Conformance checking in the menu on the left of the dashboard.

The Conformance checking dashboard is displayed.

KPIs

The different KPIs display values for both non-conforming cases (left) and conforming cases (right). This enables you to assess the impact of deviations in comparison with conforming cases.

Below is a description of the KPIs that are displayed at the top Conformance checking dashboard.

KPI	Description
Number of variants	The total number of process variants.
Number of cases	The total number of cases.
Average throughput time	The average time it takes to execute the end-to-end process.
Average event cost	The average cost of executing events for cases created within the selected period.

Note:

The KPIs are computed for conforming and non-conforming cases. A non-conforming case is a case that has at least one deviation.

Dashboard charts

See the following overview of the available charts on the Conformance checking dashboard.

Chart	Description
Deviations	A bar chart showing the detected deviations, deviation types, and the number of cases where every deviation appears.
Conformance rate	A line chart showing the conformance rate over time. Note: Conformance rate is the percentage of cases that conform to the reference model. A higher conformance rate means there is a greater degree of conformance to the reference model.
Deviations over time	A line chart showing the total number of deviations over time.

Process graph

The Conformance checking process graph shows the discrepancies between the reference process model (discovered or imported) and the actual process. The following table describes the types of process graph discrepancies that are highlighted in the process graph.

Note: If the process graph is not visible, make sure you optimize your app.

Type	Description
Conforming	The activity/edge is conforming, being present both in the reference model and in the actual process. This means that activities are executed in the exact order specified in the model.
Non-conforming log only	The activity/edge is unexpected, being present in the data but not in the reference model. This means that there is either an unexpected activity that is executed or there is an unexpected edge between two activities.
Non-conforming model only	The activity/edge is missing in the selected cases, being present in the reference model but not in the data. This means that an activity is skipped altogether from the process, or that a transition between two activities is not happening.