View source: R/processing_time.R
processing_time | R Documentation |
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.
processing_time(
log,
level = c("log", "trace", "case", "activity", "resource", "resource-activity"),
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"),
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"),
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"),
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"),
append = deprecated(),
append_column = NULL,
units = c("auto", "secs", "mins", "hours", "days", "weeks"),
sort = TRUE,
work_schedule = NULL,
eventlog = deprecated()
)
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.
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
.
Swennen, M. (2018). Using Event Log Knowledge to Support Operational Exellence Techniques (Doctoral dissertation). Hasselt University.
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()
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.