Skip to contents

Processing Time

Source: R/processing_time.R
processing_time.Rd

Provides summary statistics about the processing time of the process.

In contrast to the throughput_time() of the cases in a log, the metrics concerning the active time or the actual processing time provide summary statistics on the processing time of events on the level of the complete log, the specific cases, traces, the activities, and the resource-activity combinations.

Usage

processing_time(
  log,
  level = c("log", "trace", "case", "activity", "resource", "resource-activity",
    "activity-instance"),
  append = deprecated(),
  append_column = NULL,
  units = c("auto", "secs", "mins", "hours", "days", "weeks"),
  sort = TRUE,
  work_schedule = NULL,
  eventlog = deprecated()
)

# S3 method for class 'eventlog'
processing_time(
  log,
  level = c("log", "trace", "case", "activity", "resource", "resource-activity",
    "activity-instance"),
  append = deprecated(),
  append_column = NULL,
  units = c("auto", "secs", "mins", "hours", "days", "weeks"),
  sort = TRUE,
  work_schedule = NULL,
  eventlog = deprecated()
)

# S3 method for class 'grouped_eventlog'
processing_time(
  log,
  level = c("log", "trace", "case", "activity", "resource", "resource-activity",
    "activity-instance"),
  append = deprecated(),
  append_column = NULL,
  units = c("auto", "secs", "mins", "hours", "days", "weeks"),
  sort = TRUE,
  work_schedule = NULL,
  eventlog = deprecated()
)

# S3 method for class 'activitylog'
processing_time(
  log,
  level = c("log", "trace", "case", "activity", "resource", "resource-activity",
    "activity-instance"),
  append = deprecated(),
  append_column = NULL,
  units = c("auto", "secs", "mins", "hours", "days", "weeks"),
  sort = TRUE,
  work_schedule = NULL,
  eventlog = deprecated()
)

# S3 method for class 'grouped_activitylog'
processing_time(
  log,
  level = c("log", "trace", "case", "activity", "resource", "resource-activity",
    "activity-instance"),
  append = deprecated(),
  append_column = NULL,
  units = c("auto", "secs", "mins", "hours", "days", "weeks"),
  sort = TRUE,
  work_schedule = NULL,
  eventlog = deprecated()
)

Arguments

log

log: Object of class log or derivatives (grouped_log, eventlog, activitylog, etc.).

level

character (default "log"): Level of granularity for the analysis: "log" (default), "trace", "case", "activity", "resource", or "resource-activity". For more information, see vignette("metrics", "edeaR") and Details below.

append

logical (default FALSE) [Deprecated]: The arguments append and append_column have been deprecated in favour of augment.
Indicating whether to append results to original log. Ignored when level is "log" or "trace".

append_column

[Deprecated] The arguments append and append_column have been deprecated in favour of augment.
Which of the output columns to append to log, if append = TRUE. Default column depends on chosen level.

units

character (default "auto"): The time unit in which the processing times should be reported. Should be one of the following values: "auto" (default), "secs", "mins", "hours", "days", "weeks". See also the units argument of difftime().

sort

logical (default TRUE): Sort on decreasing processing time. For "case" level only.

work_schedule

A schedule of working hours. If provided, only working hours are counted as processing time.

eventlog

[Deprecated]; please use log instead.

Details

Argument level has the following options:

  • At "log" level, this metric calculates the summary statistics of the actual processing time per case, summarised over the complete event log.

  • On "trace" level, the summary statistics of processing time can be calculated for each possible sequence of activities that appears in the event log.

  • On "case" level, a list of cases with their processing time are provided.

  • On "activity" level, an overview of the average processing time -or the service time- of each activity can be calculated.

  • At "resource" level, this metric calculates the processing time per resource.

  • On "resource-activity" level, the efficiency of resources by looking at the combination of each resource with each activity can be investigated.

Methods (by class)

  • processing_time(eventlog): Computes processing time for an eventlog.

  • processing_time(grouped_eventlog): Computes processing time for a grouped_eventlog.

  • processing_time(activitylog): Computes processing time for an activitylog.

  • processing_time(grouped_activitylog): Computes processing time for a grouped_activitylog.

References

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

See also

idle_time(),throughput_time(),difftime()

Other metrics: activity_frequency(), activity_presence(), end_activities(), idle_time(), number_of_repetitions(), number_of_selfloops(), number_of_traces(), resource_frequency(), resource_involvement(), resource_specialisation(), start_activities(), throughput_time(), trace_coverage(), trace_length()