Page 117 -

4.2 Event Logs 99

Table 4.1 A fragment of some event log: each line corresponds to an event
Case id Event id Properties
Timestamp Activity Resource Cost ...

1 35654423 30-12-2010:11.02 Register request Pete 50 ...
35654424 31-12-2010:10.06 Examine thoroughly Sue 400 ...
35654425 05-01-2011:15.12 Check ticket Mike 100 ...
35654426 06-01-2011:11.18 Decide Sara 200 ...
35654427 07-01-2011:14.24 Reject request Pete 200 ...
2 35654483 30-12-2010:11.32 Register request Mike 50 ...
35654485 30-12-2010:12.12 Check ticket Mike 100 ...
35654487 30-12-2010:14.16 Examine casually Pete 400 ...
35654488 05-01-2011:11.22 Decide Sara 200 ...
35654489 08-01-2011:12.05 Pay compensation Ellen 200 ...

3 35654521 30-12-2010:14.32 Register request Pete 50 ...
35654522 30-12-2010:15.06 Examine casually Mike 400 ...
35654524 30-12-2010:16.34 Check ticket Ellen 100 ...
35654525 06-01-2011:09.18 Decide Sara 200 ...
35654526 06-01-2011:12.18 Reinitiate request Sara 200 ...
35654527 06-01-2011:13.06 Examine thoroughly Sean 400 ...
35654530 08-01-2011:11.43 Check ticket Pete 100 ...
35654531 09-01-2011:09.55 Decide Sara 200 ...
35654533 15-01-2011:10.45 Pay compensation Ellen 200 ...
4 35654641 06-01-2011:15.02 Register request Pete 50 ...
35654643 07-01-2011:12.06 Check ticket Mike 100 ...
35654644 08-01-2011:14.43 Examine thoroughly Sean 400 ...
35654645 09-01-2011:12.02 Decide Sara 200 ...
35654647 12-01-2011:15.44 Reject request Ellen 200 ...
... ... ... ... ... ... ...

Figure 4.2 shows the tree structure of an event log. Using this figure, we can list
our assumptions about event logs.

• A process consists of cases.
• A case consists of events such that each event relates to precisely one case.
• Events within a case are ordered.
• Events can have attributes. Examples of typical attribute names are activity, time,
costs, and resource.
Not all events need to have the same set of attributes, However, typically, events
referring to the same activity have the same set of attributes.