You are on page 1of 2

Summary of Coursera Process Mining.

Week 2 Lecture 1: Event Logs and Process Models


Created by Ariadna73 using a beta version of EASY+

(Please click, and share the video. Thank you, Ari!)

Focus: Process Discovery


Recall: Play out: Generate behavior from a model (simulation)
Recall: Play in: look at the behavior and generate the model
Our focus: Process Discovery: learning what really happens.
Replay: With model and behavior, we confront model and reality

Event log
Collection of cases.
Each case is one or more rows
Each row has attributes of different types
Case
Event
Mandatory fields
- Case ID
- Activity type
- Time stamp
The fields are not always clearly defined
For example, when sorting e-mail, which fields correspond to the activity? Which to the case?
There are different mappings that we could select from
- For example, group the emails by subject
- Or make the Sender the Case Id
Event data may come from many different sources
Transactional information
Start
Complete
Suspend
Resume
Abort
E-mail, student records, etc
Accepted standard: xes (eXtensible Event Stream)
Used by prom and DISCO
More info: www.xes-standard.org
____________________________________________________________________________________
Created by Ariadna73 using a beta version of EASY+ (Please click, and share the video. Thank you, Ari!)
Page 1 of 2

Summary of Coursera Process Mining. Week 2 Lecture 1: Event Logs and Process Models
Created by Ariadna73 using a beta version of EASY+

(Please click, and share the video. Thank you, Ari!)

Process models
First one we are going to analyze: Control flow (Petri nets)
Representation is important for two different purposes
Search space: Capturing reality well
Visualization: For the end users
There are many notations
BPMN (Business Process model and notation)
UML-activity diagrams
C-nets
Markov
Fuzzy
- Example: this is used by Disco
YAWL
There are many other perspectives
Control flow
Data flow
Time
Resources
Cost
Risk
Our two class tools
PROM
Open source
Difficult to use (we shall see)
Difficult to install
- I had to install the Java 1.7 machine and then go to the PROM directory, look for the .bat file and
change "Java" with the entire path to where the 1.7 machine was
- Then, I had to change the word -Xm4G with -Xm1G to have it using only 1G of cache memory and
it seems to work now (but don't quote me on that one)
Disco
Very easy to install. Asked for a license and an activation code. Obtained them by typing my email address, and the program opened with certain data volume restrictions
The teacher says that it is very easy to use - We shall see

____________________________________________________________________________________
Created by Ariadna73 using a beta version of EASY+ (Please click, and share the video. Thank you, Ari!)
Page 2 of 2

You might also like