In Process Mining, there are two additional concepts that enrich the data with business logic to support the analysis of a process:
Properties of cases, which indicate whether a case complies to a certain business rule. These are, for example, process KPI’s which are present in the business. Tags can be considered as unwanted behavior in the process.
Properties of events, which indicate whether an event is performed on time.
Each record in the tags table represents one tag that occurred in the data for a specific case. The mandatory attributes for this table are the
Case ID and the
Tag. These are mandatory, because you need to know which tag occurs for which case.
Below are some examples of case properties that can be considered a tag.
- An invoice is approved and paid by the same person.
- The time until approval is more than 10 days.
- The activity to check the invoice is skipped in the process.
Not all cases will have a tag and some cases may even have multiple tags. For example, when there are two cases: one case has two tags and the other case has one tag. The resulting tags table will have three records as displayed below.
Many tags will need the information about which events are executed for a case. Therefore, make sure that the event log is already created before the tags logic is defined.
Each record in the due dates table represents one due date for a certain event. The mandatory attributes for this table are the
Actual date, and
Expected date. With these mandatory attributes, you know to which event a certain due date belongs and what the actual and expected dates are. This also implies that when due dates are part of the data model, the
Event ID is also a mandatory attribute on the events table.
Example due dates are:
- a payment deadline for a payment event.
- an approval deadline for an approval event.
Similar as for tags, not all events will have a due date and some events may have multiple due dates. For example, when there are two events: one event has two due dates and the other event has one due date. The resulting due dates table will have three records as displayed below.
When comparing the actual and expected dates of these due dates, it works out that for event 1001-5 the due date payment deadline is made by 1 day. For the same event, the payment deadline with discount is late by 5 days.
Updated 3 months ago