<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Capturing Resource Behaviour From Event Logs</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marijke Swennen</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Niels Martin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gert Janssenswillen</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mieke Jans</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>t Depaire</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>An Caris</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Koen Vanhoof</string-name>
          <email>koen.vanhoofg@uhasselt.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Hasselt University</institution>
          ,
          <addr-line>Agoralaan Bldg D, 3590 Diepenbeek</addr-line>
          ,
          <institution>Belgium Research Foundation Flanders (FWO)</institution>
          ,
          <addr-line>Egmontstraat 5, 1060 Brussels</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
      </contrib-group>
      <fpage>130</fpage>
      <lpage>134</lpage>
      <abstract>
        <p>Process mining mainly focuses on the retrieval of process models from event logs. As these discovery algorithms make assumptions, performance analyses based on these models can present a biased view. In literature, algorithm-agnostic process metrics have been introduced. Given the critical importance of resources in the light of continuous process improvement, this paper extends the process metrics framework towards the resource perspective. New metrics are added and existing metrics are adapted. Using the extended framework, organisations can retrieve useful insights in resource behaviour.</p>
      </abstract>
      <kwd-group>
        <kwd>Process mining</kwd>
        <kwd>Operational excellence</kwd>
        <kwd>Resource behaviour</kwd>
        <kwd>Logbased process metrics</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Process mining aims to retrieve valuable insights in business processes from event logs.
Discovery, one of three types of process mining, aims to discover process models from
event data. Related to control- ow, a plethora of algorithms have been developed [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
which all make particular assumptions and have a representational bias. Carrying out
process performance analyses using such a process model entails the risk of presenting
a biased view on the underlying process.
      </p>
      <p>
        In this respect, the need for unbiased, algorithm-agnostic information retrieved
from event logs is advocated in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Hence, a set of metrics, related to time and
structuredness of the process, is identi ed. These unbiased insights in process behaviour
can support performance measurement [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] and continuous process improvement [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]
which is related to methodologies such as lean management and Six Sigma.
      </p>
      <p>
        A classi cation of resources in the domain of project management can be found in
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. However, this paper focuses on process participants, software systems or equipment,
as resources are de ned in the eld of BPM [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. The importance of resources is not yet
recognised in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Nevertheless, resources are a source of process variability and their
behaviour is essential in the light of continuous process improvement [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Consequently,
this dimension should be taken into account to convey a more comprehensive picture
on process behaviour to organisations. This is consistent with the research
recommendation in [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] as it targets the resource perspective in process mining.
      </p>
      <p>
        Given the need to include the resource perspective, this paper extends the work in
[
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] to include resource-related process insights. To this end, new metrics are proposed
and existing metrics are rede ned or complemented with additional analysis levels.
Within the context of quantifying the resource perspective using event logs, metrics
that mainly focus on the relationship between resources are proposed by [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. While
the latter speci es metrics with the purpose of mining organisational models, [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and
[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] focus on de ning resource behaviour measures. The current paper complements
this as well as the recently introduced resource availability metrics [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Besides the
general contribution of providing algorithm-agnostic resource insights to organisations,
the extension of [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] can also support organisations in performing knowledge
management, for instance when creating a knowledge map [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], or project management with
applications such as resource levelling or resource allocation [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
    </sec>
    <sec id="sec-2">
      <title>Resource metrics</title>
      <p>
        Next to three new metrics concerning the concept of resource behaviour, adaptations
to existing metrics in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] are presented. Levels of analysis currently presented are the
log level, trace level, and activity level. New levels of analysis related to resources are
the resource level, representing characteristics of the resources executing the activities,
and the resource-activity level in which resource-activity combinations are considered
as introduced in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. All metrics have been implemented as functions in the R-package
edeaR, which is available on the Comprehensive R Archive Network [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. An overview
of all metrics presented in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] extended with the new work presented in the paper at
hand is provided in Figure 1.
2.1
      </p>
      <sec id="sec-2-1">
        <title>Running example</title>
        <p>The metrics presented in this paper will be illustrated by applying them to the running
example introduced in Figure 2. The latter visualises an event log for ve patients
undergoing ve di erent medical activities executed by six distinct sta members of a
hospital. The duration of activities is presented by their length.
2.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>New resource metrics</title>
        <p>Resource frequency. The frequency of resources executing activities in a business
process can be insightful, e.g. during company restructuring. In Figure 2, a resource
is associated to on average 5.167 activity executions, with a minimum of 1 (resource
R6) and a maximum of 8 (resource R4), implying that R4 is probably more active and
fundamental for this process. At trace level, this metric is less informative because,
even though the sequence of activities is the same, the resources executing them can
di er. Other analysis levels are activities, resources and resource-activity combinations.
For the latter, both the resource perspective and activity perspective can be useful for
the relative number. R4 executes a surgery four times, representing 50 % of the total
number of executions by R4 and 57.14 % of the total number of surgeries.</p>
        <p>Resource involvement. The involvement of resources in cases can be of interest
to, e.g., decide how \indispensable" they are. R5, for instance, only helps three patients,
while R3 is involved in the process of 100 % of the patients. On the resource-activity
level, the involvement of speci c resource-activity combinations in cases is provided.</p>
        <p>
          Resource specialisation. Finally, the specialisation level of resources in a
company demonstrates which resources are performing certain activities more than others.
This information can be used to tackle challenges such as team selection or brain drain,
as presented in [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. Next to the log level, the resource level shows the absolute and
relative number of distinct activities that each resource executes. R1 only executes two
types of activities, examinations and radiotherapy, while he executes these activities six
times in total. At the level of distinct activities, we nd that examinations are always
executed by the same resource, while radiotherapy is executed by everyone.
2.3
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>Adaptations to existing metrics presented in [16]</title>
        <p>Looking at the processing time per case on the resource level provides a company
an overview of the amount of time each resource spends on a case and which resources
spend more time on cases than others. R3 spends on average around ve times more
time per patient than R5. However, comparing di erent resources or activities can be
more insightful at the resource-activity level.</p>
        <p>Extra levels of analysis can also be added to the structuredness metrics regarding
start and end activities in a process. Which resources execute the rst or last activity
per case can be of interest for a company. Probably this person is the contact person
for the patient or customer or is responsible for all communication.</p>
        <p>Moreover, resource information was not taken into account in the metrics regarding
rework. The metrics presenting self-loops and repetitions should take into account if
the activity is redone by the same resource or by another one. Therefore, these metrics
are rewritten according to four concepts, presented in Figure 3. A repeat self-loop is
found in case 5, where radiotherapy is executed twice immediately after each other by
R4. Case 2 holds a redo self-loop, where R4 executes radiotherapy after R3 executed
it. Case 2 also holds a redo repetition, i.e. surgery is executed by R3 and R4 (but not
immediately after each other). Finally, a repeat repetition is present in case 4 where R3
executes chemotherapy twice with an execution of radiotherapy in between.</p>
        <p>Same Resource</p>
        <p>Di erent resource</p>
        <p>Immediately following
Repeat self-loop Redo self-loop
Repeat repetition Redo repetition</p>
        <p>Not immediately following
of metric values over time and examining the combined evolution of metrics can provide
valuable knowledge. For instance, a decrease in processing time at resource-activity level
combined with an increase in rework over the same time period might not be desirable
for organisations.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>van der Aalst</surname>
          </string-name>
          , W.:
          <article-title>Process mining: data science in action</article-title>
          . Springer, Heidelberg (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. van Assen,
          <string-name>
            <given-names>M.F.</given-names>
            :
            <surname>Position</surname>
          </string-name>
          paper - Operational
          <source>Excellence for Services</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Creemers</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jans</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Social mining as a knowledge management solution</article-title>
          .
          <source>CEUR Workshop Proceedings</source>
          <volume>1612</volume>
          ,
          <issue>57</issue>
          {
          <fpage>64</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Reijers</surname>
          </string-name>
          ,
          <string-name>
            <surname>H.A.</surname>
          </string-name>
          :
          <article-title>Fundamentals of business process management</article-title>
          . Springer, Heidelberg (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xudong</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huilong</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Resource behavior measure and application in business process management</article-title>
          .
          <source>Expert Systems with Applications</source>
          <volume>39</volume>
          (
          <issue>7</issue>
          ),
          <volume>6458</volume>
          {
          <fpage>6468</fpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Janssenswillen</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Swennen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Depaire</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jans</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Enabling event-data analysis in r: Demonstration</article-title>
          .
          <source>CEUR Workshop Proceedings</source>
          <volume>1527</volume>
          ,
          <issue>189</issue>
          {
          <fpage>198</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Jugdev</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mathur</surname>
          </string-name>
          , G.:
          <article-title>Classifying project management resources by complexity and leverage</article-title>
          .
          <source>International Journal of Managing Projects in Business</source>
          <volume>5</volume>
          (
          <issue>1</issue>
          ),
          <volume>105</volume>
          {
          <fpage>124</fpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Kerzner</surname>
          </string-name>
          , H.:
          <article-title>Project Management: A Systems Approach to Planning, Scheduling, and</article-title>
          <string-name>
            <surname>Controlling. John Wiley</surname>
          </string-name>
          &amp; Sons (Feb
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Martin</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bax</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Depaire</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Caris</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Retrieving resource availability insights from event logs</article-title>
          .
          <source>Proceedings of the 2016 IEEE International Conference on Enterprise Distributed Object</source>
          Computing pp.
          <volume>69</volume>
          {
          <issue>78</issue>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Martin</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Swennen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Depaire</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jans</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Caris</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vanhoof</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Batch processing: de nition and event log identi cation</article-title>
          .
          <source>CEUR Workshop Proceedings</source>
          <volume>1527</volume>
          ,
          <issue>137</issue>
          {
          <fpage>140</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Melnyk</surname>
            ,
            <given-names>S.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stewart</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Swink</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Metrics and performance measurement in operations management: dealing with the metrics maze</article-title>
          .
          <source>Journal of Operations Management</source>
          <volume>22</volume>
          ,
          <issue>209</issue>
          {
          <fpage>217</fpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Neely</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gregory</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Platts</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Performance measurement system design: a literature review and research agenda</article-title>
          .
          <source>International Journal of Operations &amp; Production Management</source>
          <volume>25</volume>
          (
          <issue>12</issue>
          ),
          <volume>1228</volume>
          {
          <fpage>1263</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Pika</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wynn</surname>
            ,
            <given-names>M.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fidge</surname>
            ,
            <given-names>C.J.</given-names>
          </string-name>
          , ter
          <string-name>
            <surname>Hofstede</surname>
            ,
            <given-names>A.H.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leyer</surname>
          </string-name>
          , M.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.:</given-names>
          </string-name>
          <article-title>An extensible framework for analysing resource behaviour using event logs</article-title>
          .
          <source>Lecture Notes in Computer Science</source>
          <volume>8484</volume>
          ,
          <issue>564</issue>
          {
          <fpage>579</fpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Recker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The state of the art of business process management research as published in the BPM conference</article-title>
          .
          <source>Business &amp; Information Systems Engineering</source>
          <volume>58</volume>
          (
          <issue>1</issue>
          ),
          <volume>55</volume>
          {
          <fpage>72</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Song</surname>
          </string-name>
          , M.,
          <string-name>
            <surname>van der Aalst</surname>
          </string-name>
          , W.:
          <article-title>Towards comprehensive support for organizational mining</article-title>
          .
          <source>Decision Support Systems</source>
          <volume>46</volume>
          (
          <issue>1</issue>
          ),
          <volume>300</volume>
          {
          <fpage>317</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Swennen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janssenswillen</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jans</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Depaire</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vanhoof</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Capturing process behavior with log-based process metrics</article-title>
          .
          <source>Tech. rep. (</source>
          <year>2015</year>
          ), http://hdl.handle.net/
          <year>1942</year>
          /20239
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>