Sequence Identification in the Inductive Miner
For my master's thesis, I am evaluating process mining for modelling sequential data. As high fitness is a requirement in my case so I am using the base Inductive Miner. When using this miner during my experiments, I got results that I cannot explain, hence this question here on the form.
Below is the render of a part of my model (unrelated branches have been removed for simplicity). Green nodes indicate parallel gateways, and yellow nodes exclusive choice gateways.
Following this model, the tasks `resHJ|wireless`, `acctManip|wireless` and `ACE|wireless` are completely in parallel with the sequence `exfil|wireless, dManip|wireless, remoteexp|wireless, rPrivEsc|wireless`. However, in the dataset I am using, the seven tasks only appear in the same sequence:
- exfil|wireless dManip|wireless resHJ|wireless ACE|wireless remoteexp|wireless acctManip|wireless rPrivEsc|wireless
Of course, the model still gives perfect fitness as the sequence is still possible in the model shown, but there is no evidence in the underlying data to show a parallel relation between the tasks.
The way I see this, the directly-follows graph cannot contain any indication of parallelism between the resHJ, acctManip and ACE tasks and the four tasks which are in the sequence. Besides, following the paper on the Inductive Miner (https://www.win.tue.nl/~dfahland/publications/LeemansFA_2013_blockstructured.pdf), a sequential cut is always considered before a parallel cut, hence this can also not be explained by the miner favouring parallelism over sequentiality.
Hence my question: is this a known issue with the Inductive Miner, or is there something else going on which I am missing?
As a reference: I am generating these models using the code base used in "Automated Discovery of Process Models from Event Logs: Review and Benchmark" (Paper: https://arxiv.org/pdf/1705.02288.pdf, codebase: https://github.com/raffaeleconforti/ResearchCode).
Using ProM 6.10, I get the same models. Furthermore, the same pattern occurs when using the Inductive Miner-Infrequent with the default 20% setting, but to a lesser extend.
- 1.5K All Categories
- 45 Announcements / News
- 214 Process Mining
- 6 - BPI Challenge 2020
- 9 - BPI Challenge 2019
- 24 - BPI Challenge 2018
- 27 - BPI Challenge 2017
- 8 - BPI Challenge 2016
- 65 Research
- 961 ProM 6
- 371 - Usage
- 284 - Development
- 8 RapidProM
- 1 - Usage
- 6 - Development
- 54 ProM5
- 19 - Usage
- 185 Event Logs
- 30 - ProMimport
- 75 - XESame