Analyse the start activities in the process.
start_activities(
log,
level = c("log", "case", "activity", "resource", "resource-activity"),
sort = TRUE
)# S3 method for eventlog
start_activities(
log,
level = c("log", "case", "activity", "resource", "resource-activity"),
sort = TRUE
)
# S3 method for grouped_eventlog
start_activities(
log,
level = c("log", "case", "activity", "resource", "resource-activity"),
sort = TRUE
)
# S3 method for activitylog
start_activities(
log,
level = c("log", "case", "activity", "resource", "resource-activity"),
sort = TRUE
)
# S3 method for grouped_activitylog
start_activities(
log,
level = c("log", "case", "activity", "resource", "resource-activity"),
sort = TRUE
)
log: Object of class log or derivatives (grouped_log, eventlog, activitylog, etc.).
character (default "log"): Level of granularity for the analysis: "log" (default),
"case", "activity", "resource", or "resource-activity". For more information,
see vignette("metrics", "edeaR") and 'Details' below.
logical (default TRUE): Sort output on count. Only for levels with frequency count output.
start_activities(eventlog): Computes the start activities for an eventlog.
start_activities(grouped_eventlog): Computes the start activities for a grouped_eventlog.
start_activities(activitylog): Computes the start activities for an activitylog.
start_activities(grouped_activitylog): Computes the start activities for a grouped_activitylog.
Argument level has the following options:
On "log" level, this metric shows the absolute and relative number of activities that are the first activity
in one or more of the cases.
On "case" level, this metric provides an overview of the start activity of each case.
On "activity" level, this metric calculates for each activity the absolute and relative number of cases
that start with this activity type. Similar to the end_activities metric, the relative number is calculated
as a portion of the number of cases, being the number of "opportunities" that an activity could be the start activity.
The cumulative sum is added to have an insight in the number of activities that is required to cover a certain part of the total.
On "resource" level, an overview of which resources execute the first activity per case are provided.
On "resource-activity" level, this metric shows for each occurring resource-activity combination the absolute
and relative number of times this resource executes this activity as an start activity in a case.
Swennen, M. (2018). Using Event Log Knowledge to Support Operational Exellence Techniques (Doctoral dissertation). Hasselt University.
end_activities
Other metrics:
activity_frequency(),
activity_presence(),
end_activities(),
idle_time(),
number_of_repetitions(),
number_of_selfloops(),
number_of_traces(),
processing_time(),
resource_frequency(),
resource_involvement(),
resource_specialisation(),
throughput_time(),
trace_coverage(),
trace_length()