<!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>Defining and Analysing Resource-Aware Process Performance Indicators?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Adela del-Río-Ortega</string-name>
          <email>adeladelrio@us.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Manuel Resinas</string-name>
          <email>resinas@us.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Cristina Cabanillas</string-name>
          <email>cristinacabanillas@us.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Antonio Ruiz-Cortés</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Universidad de Sevilla</institution>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A key aspect to identify improvement points of the business processes (BP) of an organisation is to conduct performance management, which involves defining appropriate PPIs (Process Performance Indicators). Up to date, existing approaches to define and analyse PPIs usually focus on time and control flow aspects, leaving disregarded the organisational perspective. In this paper we extend PPINOT, a PPI metamodel, to support the definition of resource-aware PPIs in BPs enriched with resource information. Furthermore, leveraging the formal foundation of PPINOT, we introduce automated operations that relate PPIs to the people that may have an influence on them.</p>
      </abstract>
      <kwd-group>
        <kwd>Performance Management</kwd>
        <kwd>Key Performance Indicator</kwd>
        <kwd>Process Performance Indicator</kwd>
        <kwd>Resource Aware Business Process</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1 Introduction</p>
    </sec>
    <sec id="sec-2">
      <title>EXTERNAL COMMITTEE</title>
      <sec id="sec-2-1">
        <title>Resolution</title>
      </sec>
      <sec id="sec-2-2">
        <title>Proposal</title>
      </sec>
      <sec id="sec-2-3">
        <title>Create a resolution proposal draft</title>
        <p>P
A
A
I</p>
      </sec>
      <sec id="sec-2-4">
        <title>Tech. IAAP</title>
        <p>[Position]</p>
      </sec>
      <sec id="sec-2-5">
        <title>Resolution</title>
      </sec>
      <sec id="sec-2-6">
        <title>Proposal</title>
      </sec>
      <sec id="sec-2-7">
        <title>Request</title>
        <p>report to</p>
      </sec>
      <sec id="sec-2-8">
        <title>Consultative</title>
      </sec>
      <sec id="sec-2-9">
        <title>Board</title>
      </sec>
      <sec id="sec-2-10">
        <title>Request</title>
        <p>report to
DepLaergtmalent</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>LEGAL DEPARTMENT</title>
      <sec id="sec-3-1">
        <title>Report CB</title>
      </sec>
      <sec id="sec-3-2">
        <title>Analyse reports</title>
        <p>[TPeocshit.ioLnD] ReInstoelruntaioln</p>
      </sec>
      <sec id="sec-3-3">
        <title>Data warehouse</title>
      </sec>
      <sec id="sec-3-4">
        <title>Secretary [Position]</title>
      </sec>
      <sec id="sec-3-5">
        <title>Resolution</title>
      </sec>
      <sec id="sec-3-6">
        <title>Proposal</title>
      </sec>
      <sec id="sec-3-7">
        <title>Sign, store and notify resolution</title>
      </sec>
      <sec id="sec-3-8">
        <title>Secretary [Position]</title>
        <p>Unfortunately, to the best of our knowledge, no proposal is able to define them,
probably because the organisational perspective in BPs has been much less addressed in
literature than others like, for instance, control flow.</p>
        <p>
          In this paper, we address this issue as follows. On the one hand, we extend PPINOT,
a metamodel to define PPIs described in [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] (cf. Section 3), to allow the definition of
resource-aware PPIs (Cf. Section 4) in BPs enriched with resource information
modelled with RAL (Resource Assignment Language) [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. On the other hand, we leverage
the formal foundation of both PPINOT and RAL to introduce two automated
operations that relate PPIs to the people that may have an influence on them (Cf. Section 5).
The final result is a holistic approach that provides insight, not only on the control-flow
performance or the resources, but the combinations and interrelations between them.
        </p>
        <p>CRISTINA CABANILLAS MACÍAS 1 of 1 01.10.2011
2</p>
        <p>Use Case
The process depicted in Figure 1 takes place in the Andalusian Institute of Public
Administration (IAAP) and represents the procedure to create and process a resource
resolution proposal (RRP) for hiring people. Since we focus on resource-aware PPIs, the
BP must also contain information regarding the resource assignments to its activities.
Note that assigning several resources to an activity means any of them can execute it,
e.g. activity Review resolution proposal can be done by a Technician of the IAAP, a
Technician of the Consultative Board or a Technician of the Legal Department. These
Hacienda OM
!</p>
        <sec id="sec-3-8-1">
          <title>IAAP</title>
        </sec>
        <sec id="sec-3-8-2">
          <title>Alex</title>
        </sec>
        <sec id="sec-3-8-3">
          <title>Lydia</title>
        </sec>
        <sec id="sec-3-8-4">
          <title>Business</title>
        </sec>
        <sec id="sec-3-8-5">
          <title>Manager</title>
          <p>TecthheniIcAiaAnPof</p>
        </sec>
        <sec id="sec-3-8-6">
          <title>Assistant of the IAAP</title>
        </sec>
        <sec id="sec-3-8-7">
          <title>Mario</title>
        </sec>
        <sec id="sec-3-8-8">
          <title>Secretary</title>
        </sec>
        <sec id="sec-3-8-9">
          <title>Samuel</title>
        </sec>
        <sec id="sec-3-8-10">
          <title>Carol</title>
          <p>DepLaergtmalent</p>
        </sec>
        <sec id="sec-3-8-11">
          <title>Technician of the Legal</title>
        </sec>
        <sec id="sec-3-8-12">
          <title>Department</title>
        </sec>
        <sec id="sec-3-8-13">
          <title>Assistant of</title>
          <p>the Legal</p>
        </sec>
        <sec id="sec-3-8-14">
          <title>Department</title>
        </sec>
        <sec id="sec-3-8-15">
          <title>Lucas</title>
        </sec>
        <sec id="sec-3-8-16">
          <title>Chris</title>
        </sec>
        <sec id="sec-3-8-17">
          <title>Anna</title>
          <p>ConBsoualtradtive</p>
        </sec>
        <sec id="sec-3-8-18">
          <title>Technician of the</title>
        </sec>
        <sec id="sec-3-8-19">
          <title>Consultative Board</title>
        </sec>
        <sec id="sec-3-8-20">
          <title>Assistant of the</title>
        </sec>
        <sec id="sec-3-8-21">
          <title>Consultative Board</title>
        </sec>
        <sec id="sec-3-8-22">
          <title>David</title>
        </sec>
        <sec id="sec-3-8-23">
          <title>Daniel</title>
        </sec>
        <sec id="sec-3-8-24">
          <title>Diana</title>
          <p>TTTBeeeucccshhhinnnneiiicccssiiiaaaMnnnoooanfffatttPhhhgoeeeesrILCitAeioogAnnasPluDltaetpivaertmBoenartd PTAArecnoccacholeynussinsctRtiraaeobnsllepeonsible SAAAessscsssriiiesssttttaaaannnryttt ooofff ttthhhPeeeoICLsAieotigAnoasPnluDltaetpivaertmBoenartd TDDeooccchuunPmmioceesanniltttiaswosinsgriinstetearrnt
!
Fig. 2: Ex!cerpt of the organizational model of the IAAP. Orange rectangles are
organisational uRnOitLsE,S!yellow rectangles are positions, and dashed-line rectangles are resources
Document!Signer!2!Secretary!</p>
          <p>Technical!assistant!2!Assistoarngtsa!nisational model of the IAAP regarding Administrative
positions are defined in the
Resource DMocaumneangt!ewmriteern!2!tAdsseisptainctst!ed in Figure 2.</p>
          <p>To evaTleuchantiecian!2!Tepcehnrifcoiarnms! ance of this process, the following PPIs can be defined:</p>
          <p>the</p>
          <p>Analyst!2!Technicians!
– PPI1: Average time of report analysis</p>
          <p>Accountable!–!Business!Manageexr!ternal resolution out of resolved RRPs
– PPI2: RRPs that required
– PPI3:! Number of RRPs under review
– PPI4: Number of RRPs created per technician
– PPI5: Resources that review an RRP
– PPI6: Average lifetime of an RRP</p>
          <p>Note that PPI4 and PPI5 are resource-aware PPIs since they are related to the
resources involved in activities Create a resolution proposal draft and Review resolution
proposal, respectively.
3 Background on RAL and PPINOT
As detailed in the introduction, the approach we follow to define resource-aware PPIs
and to relate PPIs with the people that may have an influence on them are supported
by a language to define resource assignments and a PPIs metamodel called RAL and
PPINOT, respectively.</p>
          <p>
            RAL is an expressive DSL that allows defining the conditions that the members of the
organisation must fulfill in order to be assigned to the BP activities [
            <xref ref-type="bibr" rid="ref4">4</xref>
            ]. Specifically,
RAL expressions use the following concepts:
– The organisational model of the company, which in the case of RAL is based on
the organisational metamodel described in [
            <xref ref-type="bibr" rid="ref5">5</xref>
            ]. This involves selecting people with
a certain capability (HAS CAPABILITY Degree); belonging to a given group
resource2 (HAS POSITION Secretary); having a group resource in common with
Dr. CRISTIN2ATChAeBAtNeIrLmLASgroup resource refers to concepts1 tohfa1t represent group of persons, i.e., positions, 28.04.2013
roles or organisational units.
another person (SHARES SOME ROLE WITH Samuel); or people that report or can
delegate work to a given position (REPORTS TO Technician of the IAAP).
– The data and resource BP perspectives, e.g. to select the person responsible for
another activity (IS RESPONSIBLE FOR ACTIVITY Analyse Reports) or
someone specified in a data object (IS PERSON IN DATA FIELD RP.Analyser).
Furthermore, RAL is aware of the different duties that may be involved in a single
activity. In particular, it considers the five so-called RASCI roles [
            <xref ref-type="bibr" rid="ref6">6</xref>
            ], namely:
responsible, i.e., the person who performs the work; accountable, i.e., the person who
approves the work; support, i.e., the people who may assist in completing the
activity; consulted, i.e., the people whose opinion is sought while performing the work;
and informed, i.e., the people that are kept up-to-date about the results of the work.
          </p>
          <p>RAL expressions can be composed (AND/OR) and negated (NOT). For instance,
according to Figure 1, which only represents assignments for task duty responsible, the
RAL expression for activity Review resolution proposal is ((HAS POSITION Tech.
IAAP) OR (HAS POSITION Tech. CB.)) OR (HAS POSITION Tech. LD).</p>
          <p>
            PPINOT is a metamodel that has been created to allow the modelling of PPIs in a way
that is unambiguous and complete, understandable by technical and non-technical users,
traceable with the BP elements and amenable to automated analysis [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]. Figure 3
depicts an excerpt of PPINOT showing the main elements of a PPI definition and the types
of measure that can be used to define a PPI. These types are: Base, Derived and
Aggregated. A Base Measure is obtained directly from a single process instance and does
not require any other measure to be computed. It can be subdivided into four classes:
Time Measure, for the time duration between two time instants; Count Measure, for the
number of times something happens; Condition Measure, for the fulfillment of certain
condition referred to either a BPElement state (StateConditionMeasure) or a
DataObject restriction(DataPropertyConditionMeasure), in both running or finished process
instances; and Data Measure for the value of a certain part of a DataObject. A Derived
Measure is defined as a mathematical function over one or more measure definitions,
that can be single- (DerivedSingleInstanceMeasure) or multi-instance measures
(DerivedMultiInstanceMeasure). An Aggregated Measure aggregates one single-instance
measure in several process instances using an aggregation function (e.g. sum or
average). They can also be grouped by the content of a DataObject. For further detail, we
refer the reader to [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ].
4
          </p>
          <p>Definition of Resource-Aware PPIs
There are two different types of resource-aware PPIs. Next, we describe how the PPINOT
metamodel can be extended to support them (cf. Figure 3).</p>
          <p>Resource Measure. It measures the resources that perform certain task duty associated
to an activity. For instance: PPI5: Resources that review an RRP. This is modelled by
means of attribute measuresResource that selects the resource that is performer of
a task duty (attribute taskDuty) associated to an activity. As established above, five
o
T
s
r
e
f
e
r
ide na go re cca ifn co
V an</p>
          <p>g
re i</p>
          <p>n
u tr
s S
se * a
e :</p>
          <p>n
dM ito
e c
v n
ir fu
e
1</p>
          <p>D
e
r
u
s
a
e
M
e
c
n
a
t
s
n
iI
lt
u
M
d
e
v
i
r
e
D
e
r
u
s
a
e
M
e
c
n
a
t
s
n
I
e
l
g
n
i
S
d
e
v
i
r
e
D
M
e
c
r *
u
o
s
e
R
e *
r
u
s *
a
e
M
a
t
a
D
e
r
u
s *
a
e
M
n
o
i
it
d
n
o
C
e
r
u
s
a *
e
M
t
n
u
o
C
e
r *
u
s
a
e *
M
e
m
i</p>
          <p>T
t
n
i
re :</p>
          <p>y
u c
s n
a e
e</p>
          <p>u *
M q
d re
tae gF *y
g lin B
re p de
g m p
g a u
A s o
r</p>
          <p>e *</p>
          <p>G r
- is u</p>
          <p>s
* a
e
p
u
o
r
G
o
T
t
n
1 e</p>
          <p>e
m c
e r
l u
E o
s
e
R
s 1
e
r
u
s
a
e
m
n
o
it
c
n
u
F
n
o
it
a
g
e
r
g
g
a
e
r
u
s
a
e
M
e
s
a
B
n
io t
t c</p>
          <p>e
c * 1 j
e
l b
e
tS taa taO
n d a
te D
n
o
C 1
a
t
a
D
]
1
..
n [0 y
itco ing iittv
le tr * cA 1 ity
e S v
i
t
c
n
recS t:yu tIyu
sou ksD skaD
e a t
R T</p>
          <p>A
a
t
a
D
s
e
r
u
s
a
e
no m
iit
d
n
o
c n
e
rp iito
d
n
o
C
e
c
1 n
a
t
s
n
I
s
s
e
c
o
r
P</p>
          <p>S
n e
1 iito itm
d n</p>
          <p>u
n
o R
1 C :
t e
n t
1 tas tsa</p>
          <p>o
In T
e s</p>
          <p>e
im g
T n
a
h
c
e
t
a
t
t
n
e 1
m
e
l
E
P
B
n
e
h
w
e
r
u
s
a
e
M
e
m
i
T
r
a
e
n
i
L
n
o
i
t
* i</p>
          <p>d
o n
T o
s
e C
lil
p
a
s
t
e
e
m
o
t
m
o
fr
n
o
d is
n n</p>
          <p>e
e t
g x
e E
L
.
g
i
F
Measure type BP elements involved
Time (1) The elements that are executed between the start and the end of the time
measure and (2) the elements at the start or at the end if some of the time of their
execution is included in the time measure.</p>
          <p>Count (1) The element that is being counted and (2) the XOR gateways that have taken
the execution path to that element.</p>
          <p>Condition (1) The element used in the condition and (2) if the condition involves a data
object, the activities that can write in it.</p>
          <p>Data (1) The data object whose value is measured and (2) the activities that can modify
the data object.</p>
          <p>Resource The activity referred by the resource selection associated to the measure.</p>
          <p>Aggregated (1) The elements involved in the measure that it aggregates and (2) if it groups
results by some value, the data object that provides it.</p>
          <p>Derived The elements involved in the measures used by the mathematical function that
calculates the value of the measure.</p>
          <p>
            Table 1: Elements involved in a PPI as defined in [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ] extended with resource measures
possible task duties can be assigned: responsible, accountable, supported, consulted
and informed. In the case of PPI5, the task duty is responsible since we are
considering the person that actually does the review, not those that support her or approve it.
Furthermore, attribute activityPrecondition allows one to specify a state
condition that the activity must fulfill when the measure is taken (e.g., to be active), while
attribute resourcePrecondition allows the specification of further constraints
on the resource assignment of that activity (for instance, HAS ROLE Analyst) . In
addition, for aggregated measures that aggregate resource measures, the aggregation
function countDifferent should be used. It allows us to measure the different persons
that performed certain task duty associated to an activity, in several process instances.
Group by Resources. The other type of resource-aware PPI is based on grouping
aggregated measures by certain resource selection, e.g. PPI4: Number of RRPs created
per technician. For doing so attribute isGroupedBy of aggregated measures can be
defined by means of a ResourceSelection (the user must ensure that the activity
whose task duty is used to group coincides with the activity to which the PPI is applied).
5
          </p>
          <p>
            Automated Resource-Aware Analysis of PPIs
The automated analysis of PPIs is introduced in [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ] as a means to investigate properties
of PPI specifications and their relationships with other models. In particular, [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ] focus
on a relationship between PPIs and activities called involved in. An activity is involved
in a PPI when it has an influence in the value of the PPI [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]. The automated analysis of
this relationship is based on the idea that, although the activities involved in a PPI cannot
always be directly inferred without run-time information, it is possible to leverage the
definition of the PPI and the control flow of the BP to make a design-time estimation of
the BP elements that may have an influence on the PPI (cf. Table 1).
          </p>
          <p>In this paper, we build on this idea to define a new relationship called influenced
by that relates PPIs and resources. A PPI is potentially3 influenced by a person when
she is potentially responsible of an activity involved in that PPI, except for PPIs defined
on resource measures. In that case, the resources potentially influencing the PPI value
are those that perform the specified taskDuty in the activity specified by the measure
definition. For instance the resources potentially influencing the average lifetime of an
RRP (PPI6) are all the people that may perform duty responsible in the activities whose
duration make the average lifetime longer or shorter, i.e. activities Create RRP draft,
Request report to CB, Request report to LD, Analyse report, Request external
resolution, Review RRP, Sign, store &amp; notify resolution.</p>
          <p>On the basis of relationship influenced by, two analysis operations can be defined:
Resources potentially influencing a set of PPI(s) It takes a set of PPIs and the
corresponding resource-aware BP model as input and returns the set of resources
potentially influencing those PPIs.</p>
          <p>PPIs potentially influenced by a set of Resources It takes a set of resources (that can
be only one resource), the corresponding reource-aware BP model and the PPIs
model defined for that BP as input and returns the set of PPIs that are potentially
influenced by those resources. This operation is the opposite of the previous one,</p>
          <p>The former operation is useful to find out which the resources whose performance
have an influence in more PPIs are, or to identify those resources that are not being
taken into consideration by the current set of PPIs, i.e. those that are not influencing
any PPI. The latter operation can assist during the evolution of BPs. For instance, if
part of the organisational model evolves and is modified (e.g., a person is fired), this
operation allows one to identify which PPIs could be affected.</p>
          <p>
            These two operations can be automated using off-the-shelf DL reasoners by
leveraging the formal foundation based on description logics (DL) of both PPINOT and RAL.
On the one hand, in [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ], the relationship involved in is formalised as a DL role inv in
which inv(e; md) means that the BP element e is involved in the measure definition
md. On the other hand, in [
            <xref ref-type="bibr" rid="ref4">4</xref>
            ], for each activity A of the BP that has resources assigned,
a DL concept AssignmentA is defined. This concept represents the people assigned to
A and is obtained from the RAL expression assigned to it.
          </p>
          <p>On the basis of these two elements, a new role inf can be defined for each measure
definition md as follows:
– If md is a resource measure or aggregates a resource measure, then:
9resourceP recondition :fmdg
– Otherwise: 9inf:fmdg</p>
          <p>9isP otentialResponsible(9inv:fmdg)
Where isP otentialResponsible(p; a) means that P erson p can be responsible for
Activity a (i.e., 9isP otentialResponsible:fag AssignmentA).
3 We perform design-time analysis and before execution the actual activities’ performers are
unknown.</p>
          <p>Given inf , the relationship influenced by can be formalised as def inition inf v
inf luencedBy, where def inition(p; md) represents the relationship between a PPI p
and its measure definition md.</p>
          <p>Finally, role inf luencedBy allows expressing the aforementioned analysis
operations in terms of the DL reasoning operation individuals(C), which finds all
individuals that are instances of concept C. In particular:
– Finding the influencing resources of a set of PPIs P P I is the same as solving</p>
          <p>where inf luencedBy is the inverse role of inf luencedBy.
– Similarly, the influenced PPIs of a set of persons P is the same as solving:
individuals(9inf luencedBy :P P I)</p>
          <p>individuals(9inf luencedBy:P )
6</p>
          <p>
            Conclusions and Future Work
This paper presents an approach to support the definition and automated design-time
analysis of resource-aware PPIs. Its main benefit is the holistic view that provides to
performance evaluation, not only considering the resource-related information, but
relating it also to control-flow, time or data information.We build our approach on top of
two proposals vastly validated: PPINOT [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ] and RAL [
            <xref ref-type="bibr" rid="ref8">8</xref>
            ].
          </p>
          <p>As future work, we plan to validate this approach by applying it to real scenarios.</p>
          <p>Furthermore, the integration of these results into the existing software tools PPINOT
and CRISTAL is also part of our future work in this line.</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Kronz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Managing of Process Key Performance Indicators as Part of the ARIS Methodology</article-title>
          .
          <source>In: Corporate Performance Management: Aris in Practice</source>
          . Springer Berlin Heidelberg (
          <year>2006</year>
          )
          <fpage>31</fpage>
          -
          <lpage>44</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Chase</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosenberg</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Omar</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taylor</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>Rosing</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>Applying Real-World BPM in an SAP Environment</article-title>
          . SAP Press. Galileo Press (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>del Río-Ortega</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Resinas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cabanillas</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruiz-Cortés</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>On the Definition and Design-time Analysis of Process Performance Indicators</article-title>
          .
          <source>Inf. Syst</source>
          .
          <volume>38</volume>
          (
          <issue>4</issue>
          ) (
          <year>2013</year>
          )
          <fpage>470</fpage>
          -
          <lpage>490</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Cabanillas</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Resinas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruiz-Cortés</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Defining and Analysing Resource Assignments in Business Processes with RAL</article-title>
          . In: ICSOC. (
          <year>2011</year>
          )
          <fpage>477</fpage>
          -
          <lpage>486</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Russell</surname>
          </string-name>
          , N.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ter Hofstede</surname>
            ,
            <given-names>A.H.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edmond</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Workflow resource patterns: Identification, representation and tool support</article-title>
          . In: CAiSE. (
          <year>2005</year>
          )
          <fpage>216</fpage>
          -
          <lpage>232</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. Blog:
          <article-title>Lean Project Management Tool: RASCI. leanlogisticsblog</article-title>
          .leancor.com/
          <year>2013</year>
          /01/30/lean-project
          <string-name>
            <surname>-</surname>
          </string-name>
          management
          <string-name>
            <surname>-</surname>
          </string-name>
          tool-rasci/ (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Benavides</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Segura</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruiz-Cortés</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Automated analysis of feature models 20 years later: A literature review</article-title>
          .
          <source>Inf. Syst</source>
          .
          <volume>35</volume>
          (
          <issue>6</issue>
          ) (
          <year>2010</year>
          )
          <fpage>615</fpage>
          -
          <lpage>636</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Cabanillas</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Resinas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cortés</surname>
            ,
            <given-names>A.R.:</given-names>
          </string-name>
          <article-title>RAL: A High-Level User-Oriented Resource Assignment Language for Business Processes</article-title>
          . In: BPM Workshops.
          <article-title>(</article-title>
          <year>2011</year>
          )
          <fpage>50</fpage>
          -
          <lpage>61</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>