mpmX Help Documentation

 

 

Switching the mpmX Template App to object-centric Process Mining is done easily by following this fast-track guide.

 

1.On the tab 0B. OCPM Config set the variable mvIsOCPM to 1. It is set to 0 for traditional process mining.

SET mvIsOCPM =  1;

 

2.On the tab 0B. OCPM Config set the colors you would like your objects to have. The objects will get numbered by the mpmX algorithms and thus matched by the colors in the color map. To change the default colors or add more objects to the map, just fill in the column color with your preferred colors' hex-codes and the column No with the ongoing number.

 

Colors:

mapping load * inline [

 

3.When loading the event log on tab 1C. Load EventLog you only need to add the three OCPM fields: ObjectType, PrincipalObjectType, and ActivityOriginID. You learned in section How to Create an Event log for OCPM how to create these fields in your event log. Your event log should then look somewhat like this:

EventLog: //Log table name: "EventLog"

LOAD

//ProcessAnalyzer information

 CaseID,

 "ActivityName" as ActivityType,

 

 Timestamp(ActivityStartTimestamp) as ActivityStartTimestamp,

 Timestamp(ActivityEndTimestamp) as ActivityEndTimestamp,

//OCPM information        obligatory

 ObjectType,

 PrincipalObjectType,

 ActivityOriginID

 

4.When loading the case information table on tab  1C. Load EventLog add the OCPM field Link to the case information table. You learned in section How to Create an Event log for OCPM how to create this field. Your case information table should then contain the standard case information and the link field and look more or less like this.

Left Keep(EventLog)

[CaseInformation_$(mvProcessDescription)]:

LOAD distinct

 CaseID,

//OCPM information        obligatory

 Link,

//context information

 CaseDimension1,

 CaseDimension2

FROM [lib://helpdesk/HelpdeskEventlog.qvd] (qvd);

 

5.Now you are able to load the mpmX Template App and have a first glance at your object-centric log.

6.Optional: if you would like to define when your process is finished, we recommend creating a field in your event log that contains a finished-or-not information per object type. Then this new field can be used in the process-finished definition. In the example below you see the new field ObjectFinished which was created custom for the given process.

 

EventLog: //Log table name: "EventLog"

LOAD

//ProcessAnalyzer information

 CaseID,

 "ActivityName" as ActivityType,

 

 Timestamp(ActivityStartTimestamp) as ActivityStartTimestamp,

 Timestamp(ActivityEndTimestamp) as ActivityEndTimestamp,

//OCPM information        obligatory

 ObjectType,

 PrincipalObjectType,

 ActivityOriginID,

//OCPM information        for further app configuration

 ObjectFinished //contains information for every CaseID if it is finished or not

 

 

SET mvProcessFinished = ObjectFinished = 1;

 

7.Optional: if you configure conformance checking for OCPM, we recommend to use related dimension to align happy paths with objects and speed up the calculation time. To relate happy paths and objects you can use the fiel CaseObjectType which is created by the mpmX algorithms in the case information table. See the example below:.

 

HappyPathTable:

load * inline 

];

 

8.Optional: If you use an multilanguage app and want the objects types to be translated add the translation on tab 7. Data Model Translation.

ObjectTypeTranslation:

load * inline 

];