Rework

When looking at the structure of a process, an interesting aspect to look at is rework. Rework happens when the same activity is repeated within a single case, which often points towards time and resources which are wasted, and typically a mistake which has to be rectified.

We can distinguish between two different types of rework: 1) immediate rework, we are also known as self-loops of activities, and 2) rework which surfaces later in the process, which we call repetitions. In this exercise, we will focus on the latter.

The number_of_repetitions is a metric which can be calculated for

the whole event "log",
each "case",
each "activity",
each "resource", or
each "resource-activity" pair.

Use the number_of_repetitions() metric with the appropriate level argument to answer each question for the sepsis process.

What are the minimum, maximum and average number of repetitions in the process over the whole event log?
Who is most responsible for repetitions, i.e. which resource?
Which activity has the most repetitions?

Take Hint (-30 XP)

Exercise

Rework

Instructions