|
mpmX Event Log has not been created with mpmX EventLogGeneration Apps |
Scroll Previous Topic Top Next Topic More |
In case that you provide a self-made event log that has not been created by the mpmX EventLogGeneration Apps, MEHRWERK ProcessMining contains a clearly understandable data model with 2 template tables:
Event Log |
Case Information |
|---|---|
Observe minimum requirements for Process Mining (the ActivityID, the ActivityName and the ActivityTimeStamp) |
Additional information that relates to an entire case (e.g. a vendor, a factory, a material, ...) |
Further information that relates exactly to ONE event |
To fill the Template App with Process Mining data, adjust the table fields of the two mentioned template tables and set some variables in the following steps:
1.First of all, open the script editor and make sure that the tab 1B. Load EventLog and the tab 3. Initiate Mining Algorithms are placed behind 0. Init (in the "Mandatory" section) and that the tab 1,2,3. Data Load (with ETL) is placed behind the exit script tab (in the Optional section). Your script tabs then should look like this:
2.Select the data from the data connection
3.Reuse the event log template to define your event log
4.Reuse the event information and case information template to define your process related context data. To find out more, go to the Reuse the Context Information Template page.
7.Define when your process is completed
8.Use the factory and shift calendar template
9.Calculate the process path continuation
10.Perform conformance checking on your process data
11.Use root cause analysis on your data
12.Create translations for parts of the data model
|
All table fields can be reused as master items. |
