Rework analyses
Rework analyses help you to identify inefficiencies, redundancies, and non-compliant behavior in your business processes. For example, if you want to find out which activities in your company cause the most rework effort, you can take a look at the number of reworks to determine which activities are repeated most often.
Rework is defined as repetition of the same activity within a single case. The repetition of activities usually manifests itself in loops, repetitive activity sequences, or the repetition of previous steps.
In a typical invoice approval process, a high-performing process completes in 3 steps:
Receive invoice (A) > Review invoice (B) > Approve invoice (C)
In some cases, however, the Review invoice step appears multiple times due to issues with the invoice data, lack of documentation, or human error.
If you look at the deviating process with the sequence of activities A > B > C > B > C > B, activities B and C are performed multiple times within the process, that is, the process differs from the ideal target process.
A rework analysis can, for example:
highlight that 28% of cases have more than one "Review" step.
show that cases with rework take 2.4x longer on average.
help the company identify the root cause of problems (for example, poor-quality vendor data).
To perform rework analyses, ARIS Process Mining provides special fields and operators that you can use to create calculated fields using the script editor:
Various special rework operators at the activity level.
In addition, the Activity index field and Count rework operator are available.
The Activity index field determines the index of an activity. The field is a standard field in the analysis model.
The Count rework operator at the case level counts the number of activities that match a specified filter condition.