Perform Conformance Checking on Your Process Mining Data |
Scroll Previous Topic Top Next Topic More |
Conformance Checking is an optional module in MPM and will unlock the analysis in the sheet Conformance. To execute the Conformance Checking algorithm two input options are provided. A BPMN model can be imported via the MPM BPMN Import Connector or the happy paths are created and entered manually. When using several self-defined happy paths, the table HappyPathTable must be adjusted in the data load editor in the MPM App.
Do the following steps to enable the conformance checking module:
1.Go to the script editor of the MPM Template App.
2.Go to the script tab 4. Conformance_Checking.
3.In the script tab you will find the three sections
a)Use the BPMN Import Wizard (Option 1a - recommended for BPMN import since August 2021) --> then please refer to Use the BPMN Import Wizard
b)Use the BPMN Import connector (Option 1b) --> then please refer to the conformance checking documentation of release prior to August 2021
c)CREATE HAPPY PATHS MANUALLY (Option 2)
You can use BPMN-models and self-made happy paths combined - just follow the steps of the BPMN import and the steps below. |
Do the following steps to create valid happy paths manually (happy paths can be entered even if bpmn-import is used):
4.Open the Process Modeler worksheet.
5.Define a Happy Path with the MPM ProcessModeler and click Save.
6.Press the Edit button.
7.Click on the ProcessModeler.
8.Open the settings area on the right in the properties and copy the Resulting HappyPath.
9.Insert the ProcessPath into the HappyPathTable: HappyPathUniqueNo, HappyPaths.
10.Insert a HappyPathDescription for the happy path
11.If you want the conformance checking algorithm to consider the happy path, then set the column Selected to y
12.If the Process Path is valid only for a data subset, e.g. a specific company code and a purchase organization, enter a valid where filter in the field RelatedDimensions.
13.The dimensions used in the where filters need to be in the case context table, which is indicated in the field RelatedDimensionTable.
14.If some happy paths are related to a dimension and some not, those which do not provide a where filter will be applied to every case which is not included by non of the RelatedDimension filters.
15.Leave the fields "RelatedDimensions" and "RelatedDimensionTable" empty, if you do not need them.
HappyPathTable:
load * inline
[Selected, HappyPathUniqueNo, HappyPathDescription, HappyPaths, RelatedDimensions, RelatedDimensionTable
y, 0, Process for Purchase Organization E12, 0-103-101-118-119-126-99999999, CompanyCode = '1000' and PurchaseOrganization = 'E12', CaseInformation
y, 1, Process for Purchase Organization A20, 0-103-104-118-119-126-99999999, CompanyCode = '1000' and PurchaseOrganization = 'A20', CaseInformation
y, 2, Process for other Purchase Organizations, 0-102-103-117-119-126-190-99999999,
];
16.Repeat steps 4 to 10 for each wanted happy path.
The next time the app is loaded, a conformance check is automatically performed on the new happy paths. The results are available for analysis in the sheet Conformance.