number_of_repetitions: Metric: Number of repetitions
In gertjanssenswillen/edeaR: Exploratory and Descriptive Event-Based Data Analysis

Description Usage Arguments Details Methods (by class) References

Provides information statistics on the number of repetitions

number_of_repetitions(eventlog, type, level, append, ...)

## S3 method for class 'eventlog'
number_of_repetitions(eventlog, type = c("all",
  "repeat", "redo"), level = c("log", "case", "activity", "resource",
  "resource-activity"), append = FALSE, append_column = NULL,
  sort = TRUE, ...)

## S3 method for class 'grouped_eventlog'
number_of_repetitions(eventlog,
  type = c("repeat", "redo"), level = c("log", "case", "activity",
  "resource", "resource-activity"), append = F, append_column = NULL,
  sort = TRUE, ...)

`eventlog`	The dataset to be used. Should be a (grouped) eventlog object. `eventlog`.
`type`	The type of repetitions, either repeat or redo.
`level`	Level of granularity for the analysis: log, case, activity, resource or resource-activity. For more information, see `vignette("metrics", "edeaR")`
`append`	Logical, indicating whether to append results to original event log. Ignored when level is log or trace.
`...`	Deprecated arguments
`append_column`	Which of the output columns to append to log, if append = T. Default column depends on chosen level.
`sort`	Sort output on count. Defaults to TRUE. Only for levels with frequency count output.

A repetition is an execution of an activity within a case while that activity has already been executed before, but one or more other activities are executed in between.Similar to the self-loop metric, a distinction should be made between repeat and redo repetitions. Repeat repetitions are activity executions of the same activity type that are executed not immediately following each other, but by the same resource. Redo repetitions are activity executions of the same activity type that are executed not immediately following each other and by a different resource than the first activity occurrence of this activity type.

The number of repetitions can be calculated on the level of the complete event log. This metric shows the summary statistics of the number of repetitions within a case, which can provide insights in the amount of waste in an event log. Each combination of two or more occurrences of the same activity, executed not immediately following each other, by the same resource is counted as one repeat repetition of this activity.
On case level, this metric provides the absolute and relative number of repetitions in each case.
On the level of specific activities, this metric shows which activities occur the most in a repetition. The absolute and relative number of both repeat and redo repetitions is provided by this metric, giving an overview per activity.
When looking at the different resources executing activities in the event log, it can be interesting to have an overview of which resources need more than one time to execute an activity in a case or which resources need to have an activity redone later on in the case by another resource. This metric provides the absolute and relative number of times each resource appears in a repetition.
Finally, the same metric can be looked at on the level of specific resource-activity combinations, providing the company with specific information about which activities and which resources are involved in the repetitions. For this metric the absolute and relative number of repeat and redo repetitions is provided. Again two difierent relative numbers are provided, one relative to the total number of executions of the activity in the complete event log, and one relative to the total number of executions performed by the resource throughout the complete event log.

eventlog: Apply metric on event log
grouped_eventlog: Apply metric on grouped eventlog

Swennen, M. (2018). Using Event Log Knowledge to Support Operational Exellence Techniques (Doctoral dissertation). Hasselt University.

gertjanssenswillen/edeaR documentation built on July 22, 2019, 7:08 p.m.