resource_specialisation.RdAnalyses whether resources specialise in specific activities
resource_specialisation(eventlog, level, append, ...) resource_specialization(eventlog, level, append, ...) # S3 method for eventlog resource_specialisation(eventlog, level = c("log", "case", "activity", "resource"), append = F, ...) # S3 method for grouped_eventlog resource_specialisation(eventlog, level = c("log", "case", "activity", "resource"), append = F, ...)
| eventlog | The dataset to be used. Should be a (grouped) eventlog object.
|
|---|---|
| level | Level of granularity for the analysis: log, case, or resource.
For more information, see |
| append | Logical, indicating whether to append results to original event log. Ignored when level is log or trace. |
| ... | Deprecated arguments |
This can give a company an overview of which resources are performing certain activities more than others, and which resources are responsible for containing all knowledge or capabilities on one topic.
On the level of the complete event log, this metric provides summary statistics on the number of distinct activities executed per resource.
On the level of the cases, this metric provides the number of distinct activities that are executed within each case together with the summary statistics of the distinct activities executed per resource in each case.
On the level of the distinct activities, this metric provides an overview of the absolute and relative number of different resources executing this activity within the complete event log. This will give a company insights in which activities resources are specialised in.
Finally, the resource specialisation can also be calculated on the resource level, showing the absolute and relative number of distinct activities that each resource executes.
eventlog: Resource specialization for eventlog
grouped_eventlog: Resource specialization for grouped eventlog
Swennen, M. (2018). Using Event Log Knowledge to Support Operational Exellence Techniques (Doctoral dissertation). Hasselt University.