Conformance Violations
The Conformance Violation tool allows you to define rules for classifying cases as conforming or non-conforming. This tool is essential in process mining for ensuring that the actual process execution aligns with the predefined process model. A conforming case involves mapped events that occur in the correct sequence. These cases follow the expected process flow without any deviations and are crucial for validating that the process is being executed as intended. Conversely, a non-conforming case includes events that are not mapped, occur out of sequence, or have incorrect start or end events. Non-conforming cases highlight deviations from the expected process model.
The introduction of the Conformance Violations feature enables you to define which activities are non-conforming by adding violations, which can be of three types:
- Incorrect Start: An activity that was not expected to start the process is executed as the start activity.
- Incorrect End: An activity that was not expected to end the process is executed as the end activity.
- Incorrect Sequence: Activities are performed in an order different from the specified sequence in the process model.
Conformance violations can be created and edited by clicking the icon on the application toolbar. After the violations are defined, the Conformance widget can be used for conformance checking and visualization. In the widget, for each rendered variant, you can see violations by looking at the red highlights. You can click the status icons to see detailed information about violations for each highlighted event or connection.