<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1 20151215//EN" "http://jats.nlm.nih.gov/publishing/1.1/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.1">
<front>
<journal-meta>
<journal-id journal-id-type="pmc">CMC</journal-id>
<journal-id journal-id-type="nlm-ta">CMC</journal-id>
<journal-id journal-id-type="publisher-id">CMC</journal-id>
<journal-title-group>
<journal-title>Computers, Materials &#x0026; Continua</journal-title>
</journal-title-group>
<issn pub-type="epub">1546-2226</issn>
<issn pub-type="ppub">1546-2218</issn>
<publisher>
<publisher-name>Tech Science Press</publisher-name>
<publisher-loc>USA</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">14201</article-id>
<article-id pub-id-type="doi">10.32604/cmc.2021.014201</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>On Computing the Suitability of Non-Human Resources for Business Process Analysis</article-title>
<alt-title alt-title-type="left-running-head">On Computing the Suitability of Non-Human Resources for Business Process Analysis</alt-title>
<alt-title alt-title-type="right-running-head">On Computing the Suitability of Non-Human Resources for Business Process Analysis</alt-title>
</title-group>
<contrib-group content-type="authors">
<contrib id="author-1" contrib-type="author" corresp="yes">
<name name-style="western">
<surname>Sohail</surname>
<given-names>Abid</given-names>
</name>
<xref ref-type="aff" rid="aff-1">1</xref>
<email>abidbhutta@cuilahore.edu.pk</email>
</contrib>
<contrib id="author-2" contrib-type="author">
<name name-style="western">
<surname>Shahzad</surname>
<given-names>Khurram</given-names>
</name>
<xref ref-type="aff" rid="aff-2">2</xref></contrib>
<contrib id="author-3" contrib-type="author">
<name name-style="western">
<surname>Dominic</surname>
<given-names>P. D. D.</given-names>
</name>
<xref ref-type="aff" rid="aff-3">3</xref></contrib>
<contrib id="author-4" contrib-type="author">
<name name-style="western">
<surname>Butt</surname>
<given-names>Muhammad Arif</given-names>
</name>
<xref ref-type="aff" rid="aff-2">2</xref></contrib>
<contrib id="author-5" contrib-type="author">
<name name-style="western">
<surname>Arif</surname>
<given-names>Muhammad</given-names>
</name>
<xref ref-type="aff" rid="aff-4">4</xref></contrib>
<contrib id="author-6" contrib-type="author">
<name name-style="western">
<surname>Tariq</surname>
<given-names>Muhammad Imran</given-names>
</name>
<xref ref-type="aff" rid="aff-5">5</xref></contrib>
<aff id="aff-1"><label>1</label><institution>Department of Computer Science, COMSATS University Islamabad</institution>, <addr-line>Lahore</addr-line>, <country>Pakistan</country></aff>
<aff id="aff-2"><label>2</label><institution>Punjab University College of Information Technology, University of the Punjab</institution>, <addr-line>Lahore</addr-line>, <country>Pakistan</country></aff>
<aff id="aff-3"><label>3</label><institution>Universiti Teknologi PETRONAS, Bandar Seri Iskandar</institution>, <addr-line>Tronoh Perak</addr-line>, <country>Malaysia</country></aff>
<aff id="aff-4"><label>4</label><institution>School of Computer Science, Guangzhou University</institution>, <addr-line>Guangzhou, 510006</addr-line>, <country>China</country></aff>
<aff id="aff-5"><label>5</label><institution>Department of Computer Science and Information Technology, Superior University</institution>, <addr-line>Lahore</addr-line>, <country>Pakistan</country></aff>
</contrib-group>
<author-notes><corresp id="cor1">&#x002A;Corresponding Author: Abid Sohail. Email: <email>abidbhutta@cuilahore.edu.pk</email></corresp></author-notes>
<pub-date pub-type="epub" date-type="pub" iso-8601-date="2020-11-09">
<day>09</day>
<month>11</month>
<year>2020</year>
</pub-date>
<volume>67</volume>
<issue>1</issue>
<fpage>303</fpage>
<lpage>319</lpage>
<history>
<date date-type="received">
<day>05</day>
<month>09</month>
<year>2020</year>
</date>
<date date-type="accepted">
<day>27</day>
<month>10</month>
<year>2020</year>
</date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2021 Sohail et al.</copyright-statement>
<copyright-year>2021</copyright-year>
<copyright-holder>Sohail et al.</copyright-holder>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This work is licensed under a <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="TSP_CMC_14201.pdf"></self-uri>
<abstract>
<p>Business process improvement is a systematic approach used by several organizations to continuously improve their quality of service. Integral to that is analyzing the current performance of each task of the process and assigning the most appropriate resources to each task. In continuation of our previous work, we categorize resources into human and non-human resources. For instance, in the healthcare domain, human resources include doctors, nurses, and other associated staff responsible for the execution of healthcare activities; whereas the non-human resources include surgical and other equipment needed for execution. In this study, we contend that the two types of resources (human and non-human) have a different impact on the process performance, so their suitability should be measured differently. However, no work has been done to evaluate the suitability of non-human resources for the tasks of a process. Consequently, it becomes difficult to identify and subsequently overcome the inefficiencies caused by the non-human resources to the task. To address this problem, we present a three-step method to compute a suitability score of non-human resources for the task. As an evaluation of the proposed method, a healthcare case study is used to illustrate the applicability of the proposed method. Furthermore, we performed a controlled experiment to evaluate the usability of the proposed method. The encouraging response shows the usefulness of the proposed method.</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>Business process management</kwd>
<kwd>business process improvement</kwd>
<kwd>process warehouse</kwd>
<kwd>data warehouse</kwd>
<kwd>resource suitability component</kwd>
<kwd>resource suitability</kwd>
<kwd>health care</kwd>
<kwd>artificial intelligence</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>Organizations continually strive to improve the execution of processes for delivering quality services to its customers. In this context, Business Process Management (BPM) has established itself as a vital instrument [<xref ref-type="bibr" rid="ref-1">1</xref>] because it offers a structured, coherent, and consistent way of modeling, executing, and analyzing business operations [<xref ref-type="bibr" rid="ref-2">2</xref>]. However, it is widely acknowledged that there are two reasons for inefficiencies in the execution of business processes [<xref ref-type="bibr" rid="ref-3">3</xref>,<xref ref-type="bibr" rid="ref-4">4</xref>]: (i) Structural weakness in the process models, and (ii) Inappropriate resource assignment. Corresponding to these two reasons, there are two ways to continuously improve the performance of processes, process redesign and resource management. Where, process redesign deals with altering the structure of a process, and resource management deals with rearranging the resources associated with activities of a process.</p>
<p>In the BPM lifecycle, historic analysis of resources (formally, posterior analysis) refers to the post-process enactment analysis, as it requires an execution log that is generated during the enactment of a process. The execution log is widely acknowledged as a very useful data source for various purposes, such as compliance checking [<xref ref-type="bibr" rid="ref-5">5</xref>]. However, the provision of effective information to support the analysis is a challenging task due to the following reasons: (a) Log files are maintained for a very short span of time, and (b) It is not optimized to support performance analysis. An alternative to that is the use of a process-oriented data warehouse, called Process Warehouse (PW). PW is a specialized warehouse that is similar to the classical data warehouse as it captures data in a multi-dimensional structure [<xref ref-type="bibr" rid="ref-6">6</xref>], whereas, it is materialized by the integrating three data sources, workflow objects, business objects, and process execution log [<xref ref-type="bibr" rid="ref-7">7</xref>]. Several studies have identified that a key challenge associated with the use of PW is that it contains large volume of information which may not be necessarily relevant for every analysis [<xref ref-type="bibr" rid="ref-8">8</xref>,<xref ref-type="bibr" rid="ref-9">9</xref>]. Consequently, the presence of excessive information complicates the task of the process analysis for inexperienced decision-makers [<xref ref-type="bibr" rid="ref-10">10</xref>]. Therefore, a method is desired that can provide access to relevant data and also facilitate the way resource analysis is performed.</p>
<p>Our existing effort to business process analysis [<xref ref-type="bibr" rid="ref-11">11</xref>&#x2013;<xref ref-type="bibr" rid="ref-16">16</xref>] has categorized resources into two types, human and non-human resources. The studies have established that the two types of resources (human and non-human resources) have different behaviors and thus they have a different impact on process performance. This is aligned with other established studies [<xref ref-type="bibr" rid="ref-4">4</xref>], which has argued that human and non-human resources collectively optimize the process performance. However, it is observed that the behavior of the two types of resources is not similar. Furthermore, Ouyang et al. [<xref ref-type="bibr" rid="ref-14">14</xref>] has also argued that living beings and non-living beings, such as surgical equipment, do not have similar behaviors. It is because, &#x2018;non-living beings&#x2019; are static and do not affect process performance due to any subjective interest or skill [<xref ref-type="bibr" rid="ref-17">17</xref>]. Therefore, the performance of both classes should be evaluated differently using different parameters.</p>
<p>To that end, in a previous study, we developed an Integrated Resource Classification Framework (IRCF) [<xref ref-type="bibr" rid="ref-11">11</xref>]. According to the framework, true optimization of process performance requires an in-depth analysis of human and non-human resources. Subsequently, other studies were conducted that to developing methods for the performance analysis of human resources [<xref ref-type="bibr" rid="ref-18">18</xref>&#x2013;<xref ref-type="bibr" rid="ref-20">20</xref>]. However, no study has been conducted to develop methods for the performance analysis of the non-human resources. The specific aim of this study is <italic>to propose a method for evaluating the suitability of non-human resources using PW</italic>. In particular, we first propose a theoretical suitability model to identify the various factors which should be considered for evaluating the suitability of non-human resources for a given task. Subsequently, the theoretical model is used as a basis for developing a novel method for the suitability of non-human resources. A key benefit of the method is that it can be used by domain experts having limited knowledge of PW.</p>
<p>The rest of the paper is organized as follows: Section 2 provides an overview of the Integrated Resource Classification Framework, Section 3 presents the suitability model for non-human resources which serves as a basis for the proposed method presented in Section 4. Illustration of the method for a healthcare case study and the details of the controlled experiments are presented in Sections 5 and 6 respectively. The paper concludes in Section 7.</p>
</sec>
<sec id="s2">
<label>2</label>
<title>Integrated Resource Classification Framework (IRCF)</title>
<p>Organizations are continuously striving to improve their processes through the appropriate assignment of resources. Resources include human agents (human resources) and devices (non-human resources) which are coupled to execute activities of a process. While, several studies, such as [<xref ref-type="bibr" rid="ref-4">4</xref>], have acknowledged that resources play a pivotal role in the optimal execution of processes, some studies argue that &#x201C;the two types of resources have a different impact on the performance of a process. Therefore, their performance should be evaluated differently, i.e., the same criteria should not be used for the evaluation of both types of resources&#x201D; [<xref ref-type="bibr" rid="ref-11">11</xref>,<xref ref-type="bibr" rid="ref-12">12</xref>]. Therefore, to evaluate the performance of the two types of resources, we previously introduced a framework, called Integrated Resource Classification Framework (IRCF) [<xref ref-type="bibr" rid="ref-11">11</xref>]. The framework is composed of three different types of relationships that should be considered for resource management. <xref ref-type="fig" rid="fig-1">Fig. 1</xref> shows the three types of relationships between a task and the two types of resources, human and non-human resources. A brief overview of the three types of relationships are as follows:
<list list-type="bullet">
<list-item><p>The relationship between human resources and a given task should be determined in terms of the ability of the human resource to perform the task, which is termed as <italic>competency</italic>. It determines how well a human resource can perform the task.</p></list-item>
<list-item><p>The relationship between a non-human resource and a task is determined in terms of its appropriateness for the task, which is termed as <italic>suitability</italic>. It determines how well-fitting a non-human resource is for a task.</p></list-item>
<list-item><p>The relationship between human and non-human resources is determined in terms of the inclination of human agents to use certain non-human resources for a specific task, which is termed as <italic>preference</italic>. Where, the preference defines how comfortable human resources are to use a given non-human resource for a given task.</p></list-item>
</list></p>
<fig id="fig-1">
<label>Figure 1</label> 
<caption>
<title>Integrated resources classification framework [<xref ref-type="bibr" rid="ref-11">11</xref>] 
</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-1.png"/>
</fig>
<p>In our previous work [<xref ref-type="bibr" rid="ref-18">18</xref>&#x2013;<xref ref-type="bibr" rid="ref-20">20</xref>], we focused on developing a method for the performance analysis of analyses human resources. However, no study has been conducted to develop a method for the performance analysis of non-human resources. To that end, firstly, we have proposed a theoretical model to evaluate the suitability of non-human resources, and subsequently use it to propose a method for evaluating the suitability of non-human resources.</p>
</sec>
<sec id="s3">
<label>3</label>
<title>The Suitability Metamodel</title>
<p>A model is used to describe <italic>&#x2018;something from the real world&#x2019;</italic> and metamodel is &#x2018;<italic>a surrogate model that describes what can be modeled&#x2019;</italic> [<xref ref-type="bibr" rid="ref-21">21</xref>]. In this section, we present a metamodel to evaluate the suitability of non-human resources for a given task. The metamodel represents the concepts that should be used to evaluate the suitability of non-human resources for a given task. We contend that the evaluation of non-human resources with respect to the task is represented by the degree of appropriateness of non-human resources for the task.</p>
<p><italic>Why suitability</italic>. Zur Muehlen [<xref ref-type="bibr" rid="ref-4">4</xref>] argued that a role provides the privilege boundaries and capabilities for human resources during the execution of activities. For instance, a nurse may gain the skill to operate on a patient but she is not allowed to lead an <italic>operation</italic> because this task is solely bound to the doctor&#x2019;s role. Due to the access privilege boundary, the support for this feature is available in business process management systems, such as Bizagi BPM Suite [<xref ref-type="bibr" rid="ref-22">22</xref>]. However, the support for assigning suitable non-human resources to tasks is not available in BPMS. In this study, we contend that non-human resources also have a non-trivial impact on process performance. Thus, without the appropriate combination of optimal non-human and human resources, process execution cannot be improved. This is in-line with Heravizadeh et al. [<xref ref-type="bibr" rid="ref-23">23</xref>] who has argued that the optimal execution of a <italic>task</italic> requires a <italic>suitable set of non-human resources</italic> matched with the <italic>competent human resources</italic>. It is also widely acknowledged that assigning a task to the domain expert (most competent) human resources optimizes process execution. However, it has also been observed that even a domain expert cannot improve process performance without the availability of an appropriate set of non-human resources. For example, if an unsuitable syringe is provided to a skilled nurse, she may not execute the task appropriately. Hence, the identification of suitable non-human resources is essential in the evaluation of the resource&#x2019;s performance.</p>
<p><italic>Essentials of Suitability:</italic> According to Heravizadeh et al. [<xref ref-type="bibr" rid="ref-23">23</xref>] and Loucopoulos et al. [<xref ref-type="bibr" rid="ref-24">24</xref>], suitability is categorized as a basic quality function for the measurement of process performance through non-human resources. In our context, it is the appropriateness of non-human resources for a task. We contend that reliability, accuracy, and completeness are three essential ingredients for measuring the appropriateness of non-human resources. Where, <italic>reliability</italic> refers to the ability of the non-human resources to perform the task. It is also defined as &#x201C;the ability to maintain a specified level of performance when used under specified conditions&#x201D; [<xref ref-type="bibr" rid="ref-23">23</xref>] and can be measured as a function of failure and success frequencies [<xref ref-type="bibr" rid="ref-24">24</xref>,<xref ref-type="bibr" rid="ref-25">25</xref>].</p>
<p><italic>Completeness</italic> is defined as the ability to fulfill the requirements of the given task i.e., the minimum and maximum criteria sets for successfully executing a task. Completeness stems from Heravizadeh&#x2019;s et al. [<xref ref-type="bibr" rid="ref-23">23</xref>] quality dimension of a robust totality and is defined as &#x201C;the degree to which a function can function correctly even in the presence of invalid, incomplete or conflicting inputs.&#x201D;</p>
<p><italic>Accuracy</italic> measures the degree of success of the task completion with the device that is used for it. It is also defined as &#x201C;the right or agreed results or effects with the needed degree of precision&#x201D; [<xref ref-type="bibr" rid="ref-23">23</xref>].</p>
<p>The metamodel of the evaluation of suitability is presented below in <xref ref-type="fig" rid="fig-2">Fig. 2</xref>. The figure shows the relationship between the three concepts (reliability, accuracy, and completeness) and an ordinal scale of 1 to 5 on which these values can be measured. Where, the value 1 represents that the non-human resource is completely unsuitable for the task, and value 5 represents that non-human resource is most suitable for the task.</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>Resource suitability metamodel</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-2.png"/>
</fig>
</sec>
<sec id="s4">
<label>4</label>
<title>Suitability Evaluation Method</title>
<p>In this section, we present a method that can guide the suitability analysis of non-human resources for a given task. That is, the method calculates the suitability score of non-human resources for a task based on the resource suitability metamodel introduced in the preceding section. Specifically, the method consists of three steps, where the input to the first step is the role whose corresponding resource-task suitability needs to be evaluated, and the output of the third step is the suitability score of a non-human resource for the task. The steps and their relationships are shown below in <xref ref-type="fig" rid="fig-3">Fig. 3</xref>, followed by an discussion of each step of the method.</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>The suitability evaluation method 
</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-3.png"/>
</fig>
<sec id="s4_1">
<label>4.1</label>
<title>Task History Identifications</title>
<p>The first step aims at identifying the history of tasks performed by a role and the used resources. The input to this step is a role whose tasks are under consideration for computing suitability. To generate the input tasks for this step, we rely on an SQL query. The algebraic query to extract the tasks list for a specific role is as follows:
<disp-formula id="eqn-1">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-1.png"/>
<tex-math id="tex-eqn-1"><![CDATA[$$\begin{eqnarray*}
\pi_{\mathrm{(TaskID,\_Task\_name, Role)}}\sigma_{\mathrm{between}}(\mathrm{t1,\;t2})\&\mathrm{role}= \mathrm{``r'' G (role)}
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-1" display="block"><mml:mrow><mml:msub><mml:mrow><mml:mi>&#x03C0;</mml:mi></mml:mrow><mml:mrow><mml:mstyle mathvariant="normal"><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mi>T</mml:mi><mml:mi>a</mml:mi><mml:mi>s</mml:mi><mml:mi>k</mml:mi><mml:mi>I</mml:mi><mml:mi>D</mml:mi><mml:mo>,</mml:mo><mml:mstyle><mml:mtext>_</mml:mtext></mml:mstyle><mml:mi>T</mml:mi><mml:mi>a</mml:mi><mml:mi>s</mml:mi><mml:mi>k</mml:mi><mml:mstyle><mml:mtext>_</mml:mtext></mml:mstyle><mml:mi>n</mml:mi><mml:mi>a</mml:mi><mml:mi>m</mml:mi><mml:mi>e</mml:mi><mml:mo>,</mml:mo><mml:mi>R</mml:mi><mml:mi>o</mml:mi><mml:mi>l</mml:mi><mml:mi>e</mml:mi></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mstyle></mml:mrow></mml:msub><mml:msub><mml:mrow><mml:mi>&#x03C3;</mml:mi></mml:mrow><mml:mrow><mml:mstyle mathvariant="normal"><mml:mi>b</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mi>w</mml:mi><mml:mi>e</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi></mml:mstyle></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mstyle mathvariant="normal"><mml:mi>t</mml:mi><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mspace width="2.77695pt"/><mml:mi>t</mml:mi><mml:mn>2</mml:mn></mml:mstyle></mml:mrow><mml:mo>)</mml:mo></mml:mrow><mml:mo>&#x0026;</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>r</mml:mi><mml:mi>o</mml:mi><mml:mi>l</mml:mi><mml:mi>e</mml:mi></mml:mstyle><mml:mo>=</mml:mo><mml:mstyle mathvariant="normal"><mml:mo>&#x201C;</mml:mo><mml:msup><mml:mrow><mml:mi>r</mml:mi></mml:mrow><mml:mrow><mml:mo>&#x2033;</mml:mo></mml:mrow></mml:msup><mml:mi>G</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mi>r</mml:mi><mml:mi>o</mml:mi><mml:mi>l</mml:mi><mml:mi>e</mml:mi></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mstyle></mml:mrow></mml:math></alternatives></disp-formula>
</p>
<p>Consider that we are interested in evaluating the suitability of the tasks performed by <italic>&#x2018;Nurse&#x2019;</italic>. The query can be formulate as follows:</p>
<table-wrap>
<table>
<tbody>
<tr>
<td><monospace>SELECT TaskID, TaskName, Role</monospace></td></tr>
<tr><td><monospace>FROM dim_task, dim_WFO, dim_time</monospace></td></tr>
<tr><td><monospace>WHERE dim.taskid=dim_WFO.taskid</monospace></td></tr>
<tr><td><monospace>AND dim_WFO.taskid=dim_time</monospace></td></tr>
<tr><td><monospace>AND Time &#x003E; = &#x2018;1-1-2015&#x2019;</monospace></td></tr>
<tr><td><monospace>AND Time = &#x003C; &#x2018;1-1-2015&#x2019;</monospace></td></tr>
<tr><td><monospace>AND Role=&#x2018;nurse&#x2019;</monospace></td></tr>
<tr><td><monospace>GROUP BY Role;__</monospace></td></tr>
</tbody>
</table>
</table-wrap>
<p>The output of this query is the list of tasks of the given role. Using the task list as input, the first algorithm of our method extracts the instances of process execution in which the task was used. Also, the methods extracts start time, end time, the non-human resources used, and the status of the task, i.e., whether the task is in progress, completed, or paused. The output of this algorithm is a two-dimensional structure for each task which contains the output in a two-dimensional structure.</p>
<p>The two-dimensional structure <inline-formula id="ieqn-1"><alternatives><inline-graphic xlink:href="ieqn-1.png"/><tex-math id="tex-ieqn-1"><![CDATA[$\beta_{t1}$]]></tex-math><mml:math id="mml-ieqn-1"><mml:msub><mml:mrow><mml:mi>&#x03B2;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub></mml:math></alternatives></inline-formula> for a task <italic>t1</italic> contains the identities of execution cases, the status of the task, whether it is successful, pending, or unsuccessful, and the status of each resource for the task, whether the resource was used or not used. In relational algebra, it can be represented as follows:
<disp-formula id="eqn-2">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-2.png"/>
<tex-math id="tex-eqn-2"><![CDATA[$$\begin{eqnarray*}
\beta = \beta_{t1}, \beta_{t1},\ldots,\beta_{tn}
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-2" display="block"><mml:mrow><mml:mi>&#x03B2;</mml:mi><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>&#x03B2;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mrow><mml:mi>&#x03B2;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:msub><mml:mrow><mml:mi>&#x03B2;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mi>n</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></alternatives></disp-formula>
 such that, <inline-formula id="ieqn-2"><alternatives><inline-graphic xlink:href="ieqn-2.png"/><tex-math id="tex-ieqn-2"><![CDATA[$\{t1, t2, \ldots , tn\}$]]></tex-math><mml:math id="mml-ieqn-2"><mml:mrow><mml:mo>{</mml:mo><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mi>t</mml:mi><mml:mn>2</mml:mn><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:mi>t</mml:mi><mml:mi>n</mml:mi></mml:mrow><mml:mo>}</mml:mo></mml:mrow></mml:math></alternatives></inline-formula> represents the list of tasks for the role, and
<disp-formula id="eqn-3">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-3.png"/>
<tex-math id="tex-eqn-3"><![CDATA[$$\begin{eqnarray*}
\beta_{t1}= \pi_{(\mathrm{CaseID}, \mathrm{Status}, \mathrm{R1}, \mathrm{R2}, \ldots, \mathrm{Rm})}
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-3" display="block"><mml:mrow><mml:msub><mml:mrow><mml:mi>&#x03B2;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>&#x03C0;</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mstyle mathvariant="normal"><mml:mi>C</mml:mi><mml:mi>a</mml:mi><mml:mi>s</mml:mi><mml:mi>e</mml:mi><mml:mi>I</mml:mi><mml:mi>D</mml:mi></mml:mstyle><mml:mo>,</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>S</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>u</mml:mi><mml:mi>s</mml:mi></mml:mstyle><mml:mo>,</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>R</mml:mi><mml:mn>1</mml:mn></mml:mstyle><mml:mo>,</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>R</mml:mi><mml:mn>2</mml:mn></mml:mstyle><mml:mo>,</mml:mo><mml:mo lspace='0pt' rspace='0pt'>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>R</mml:mi><mml:mi>m</mml:mi></mml:mstyle></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:math></alternatives></disp-formula>
 where, R<sub>1</sub>, R<inline-formula id="ieqn-3"><alternatives><inline-graphic xlink:href="ieqn-3.png"/><tex-math id="tex-ieqn-3"><![CDATA[$_{2}, \ldots , \mathrm{R}_{m}$]]></tex-math><mml:math id="mml-ieqn-3"><mml:msub><mml:mrow></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:msub><mml:mrow><mml:mstyle mathvariant="normal"><mml:mi>R</mml:mi></mml:mstyle></mml:mrow><mml:mrow><mml:mi>m</mml:mi></mml:mrow></mml:msub></mml:math></alternatives></inline-formula> represents the list of resources used in the task.</p>
</sec>
<sec id="s4_2">
<label>4.2</label>
<title>Suitability Evaluation Sheet Creation</title>
<p>The input to this step is the two-dimensional structures generated in the preceding step, and this step aims to create a suitability evaluation sheet for each task in the task list. This particular step uses the suitability evaluation metamodel presented in <xref ref-type="fig" rid="fig-2">Fig. 2</xref>. Recall, in Section 4 we established that the suitability score of a non-human resource is an aggregation of reliability, completeness, and the accuracy scores.</p>
<p>In the second step of the method, the reliability scores of a resource is computed by extracting data from the fact table of PW and using the extracted values in the equations for reliability, completeness, and accuracy. The reliability is defined as follows:
<disp-formula id="eqn-4">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-4.png"/>
<tex-math id="tex-eqn-4"><![CDATA[$$\begin{eqnarray*}
R_{L}= (U_{C}/T_{C})\ast 100(a)
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-4" display="block"><mml:mrow><mml:msub><mml:mrow><mml:mi>R</mml:mi></mml:mrow><mml:mrow><mml:mi>L</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>U</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub><mml:mo>/</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo>)</mml:mo></mml:mrow><mml:mo>*</mml:mo><mml:mn>1</mml:mn><mml:mn>0</mml:mn><mml:mn>0</mml:mn><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mi>a</mml:mi></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:math></alternatives></disp-formula>
</p>
<p>In the equation, <italic>R<sub>L</sub></italic> represents the reliability of non-human resources for a task, <italic>T<sub>C</sub></italic> represents the total number of cases (in all task executions) in which the resource r was utilized, and <italic>U<sub>C</sub></italic> represents the total number of cases in which the specific resource was utilized in different instances;
<disp-formula id="eqn-5">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-5.png"/>
<tex-math id="tex-eqn-5"><![CDATA[$$\begin{eqnarray*}
C_{P}= (T_{S}/U_{C})\ast 100(b)
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-5" display="block"><mml:mrow><mml:msub><mml:mrow><mml:mi>C</mml:mi></mml:mrow><mml:mrow><mml:mi>P</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>S</mml:mi></mml:mrow></mml:msub><mml:mo>/</mml:mo><mml:msub><mml:mrow><mml:mi>U</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo>)</mml:mo></mml:mrow><mml:mo>*</mml:mo><mml:mn>1</mml:mn><mml:mn>0</mml:mn><mml:mn>0</mml:mn><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mi>b</mml:mi></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:math></alternatives></disp-formula>
</p>
<p>In the above equation, <italic>C<sub>P</sub></italic> represents the completeness of non-human resources for a task, <italic>and T</italic><sub><italic>S</italic></sub> represents the total number of times the task was successfully completed.
<disp-formula id="eqn-6">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-6.png"/>
<tex-math id="tex-eqn-6"><![CDATA[$$\begin{eqnarray*}
A_{C}= (1- (T_{C}-A_{TC})/T_{C})\ast100 (c)
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-6" display="block"><mml:mrow><mml:msub><mml:mrow><mml:mi>A</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mn>1</mml:mn><mml:mo>-</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub><mml:mo>-</mml:mo><mml:msub><mml:mrow><mml:mi>A</mml:mi></mml:mrow><mml:mrow><mml:mi>T</mml:mi><mml:mi>C</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo>)</mml:mo></mml:mrow><mml:mo>/</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo>)</mml:mo></mml:mrow><mml:mo>*</mml:mo><mml:mn>1</mml:mn><mml:mn>0</mml:mn><mml:mn>0</mml:mn><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mi>c</mml:mi></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:math></alternatives></disp-formula>
</p>
<p>In the above equation, <italic>A<sub>C</sub></italic> represents the percentage accuracy of a non-human resource for a task, and <italic>A<sub>TC</sub></italic> represents the total number of accurately executed instances.</p>
<p>The three equations (<italic>a, b, and c</italic>) are used in Algorithm 2 to create a suitability evaluation sheet. The outcome of this algorithm is a two-dimensional structure <inline-formula id="ieqn-4"><alternatives><inline-graphic xlink:href="ieqn-4.png"/><tex-math id="tex-ieqn-4"><![CDATA[$\varrho_{t1}$]]></tex-math><mml:math id="mml-ieqn-4"><mml:msub><mml:mrow><mml:mi>&#x03F1;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub></mml:math></alternatives></inline-formula> for task t1 that contains the resources used in the task, reliability score, completeness score, and the accuracy score for each resource in the contest of the task.</p>
<p>The two-dimensional structure <inline-formula id="ieqn-5"><alternatives><inline-graphic xlink:href="ieqn-5.png"/><tex-math id="tex-ieqn-5"><![CDATA[$\varrho_{t}$]]></tex-math><mml:math id="mml-ieqn-5"><mml:msub><mml:mrow><mml:mi>&#x03F1;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub></mml:math></alternatives></inline-formula> for a task t1 contains the identities of execution cases, the resources used for the task (R<sub>1</sub>, R<inline-formula id="ieqn-6"><alternatives><inline-graphic xlink:href="ieqn-6.png"/><tex-math id="tex-ieqn-6"><![CDATA[$_{2}, \ldots, \mathrm{R}_{m}$]]></tex-math><mml:math id="mml-ieqn-6"><mml:msub><mml:mrow></mml:mrow><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:msub><mml:mrow><mml:mstyle mathvariant="normal"><mml:mi>R</mml:mi></mml:mstyle></mml:mrow><mml:mrow><mml:mi>m</mml:mi></mml:mrow></mml:msub></mml:math></alternatives></inline-formula>), reliability score, completeness score, and accuracy score for the resource. In relational algebra, it becomes:
<disp-formula id="eqn-7">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-7.png"/>
<tex-math id="tex-eqn-7"><![CDATA[$$\begin{eqnarray*}
\varrho = \varrho_{t1},\quad \varrho_{t1}\ldots\varrho_{tn}
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-7" display="block"><mml:mrow><mml:mi>&#x03F1;</mml:mi><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>&#x03F1;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mspace width="1em"/><mml:msub><mml:mrow><mml:mi>&#x03F1;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>&#x2026;</mml:mo><mml:msub><mml:mrow><mml:mi>&#x03F1;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mi>n</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></alternatives></disp-formula>
 where, <inline-formula id="ieqn-7"><alternatives><inline-graphic xlink:href="ieqn-7.png"/><tex-math id="tex-ieqn-7"><![CDATA[$t1, t2\ldots tn$]]></tex-math><mml:math id="mml-ieqn-7"><mml:mi>t</mml:mi><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mi>t</mml:mi><mml:mn>2</mml:mn><mml:mo>&#x2026;</mml:mo><mml:mi>t</mml:mi><mml:mi>n</mml:mi></mml:math></alternatives></inline-formula> represents the list of tasks for the role, and
<disp-formula id="eqn-8">
<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-8.png"/>
<tex-math id="tex-eqn-8"><![CDATA[$$\begin{eqnarray*}
\varrho_{t1}= \pi_{\text{(CaseID, ResrouceID, Reliability, Completeness, Accuracy)}}
\end{eqnarray*}$$]]></tex-math>
<mml:math id="mml-eqn-8" display="block"><mml:mrow><mml:msub><mml:mrow><mml:mi>&#x03F1;</mml:mi></mml:mrow><mml:mrow><mml:mi>t</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>&#x03C0;</mml:mi></mml:mrow><mml:mrow><mml:mstyle><mml:mtext>(CaseID,&#x00A0;ResrouceID,&#x00A0;Reliability,&#x00A0;Completeness,&#x00A0;Accuracy)</mml:mtext></mml:mstyle></mml:mrow></mml:msub></mml:mrow></mml:math></alternatives></disp-formula></p>
<fig id="fig-9">
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-9.png"/>
</fig>
<fig id="fig-10">
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-10.png"/>
</fig>
</sec>
<sec id="s4_3">
<label>4.3</label>
<title>Suitability Calculation</title>
<p>This step aims to generate the suitability score of each resource-task pair by taking input the set of two-dimensional structures (<inline-formula id="ieqn-8"><alternatives><inline-graphic xlink:href="ieqn-8.png"/><tex-math id="tex-ieqn-8"><![CDATA[$\varrho$]]></tex-math><mml:math id="mml-ieqn-8"><mml:mi>&#x03F1;</mml:mi></mml:math></alternatives></inline-formula>) generated from the preceding step. The algorithm in this step takes the suitability evaluation sheet as input, normalizes the score to a range of 1&#x2013;5, and represent it as a matrix. The x-axis in the matrix represents the list of resources used in a task and the y-axis represents the suitability scores of the resource, i.e., normalized completeness, accuracy, and reliability scores. Subsequently, a weighting scheme is used to generate a suitability score of each resource in terms of completeness, accuracy, and reliability. The aim of the weighting scheme is to provide flexibility to the user to adjust the effect of each behavior. The rules for weight assignments are as follows:
<list list-type="bullet">
<list-item><p>Weights of suitability behaviors (reliability, completeness, and accuracy) shall vary between 0 and 1 in such a way that the total score of the three behaviors remain between 0 and 1.</p></list-item>
<list-item><p>The default weight is 0 to nullify the effective of a behavior on the overall suitability score.</p></list-item>
</list></p>
<p>The algorithm then takes a dot product of the two matrix, and row-wise summation will produce suitability for the resource-task pair which represents the suitability of each resource for a task.</p>
<fig id="fig-11">
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-11.png"/>
</fig>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Method Illustration</title>
<p>In this section, we illustrate the use of our proposed method for a healthcare process. However, it requires a materialized PW which is typically not publicly available due to confidentiality reasons. As an alternative to that we designed a PW and used synthetic data to populate it. More specifically, firstly, we designed a process model of &#x2018;maternity regular visit&#x2019; using BPMN, which is the standard process modeling language, and designed the PW. Subsequently, we implemented a PLG V1.0 to generate synthetic data. The reason for implementing a new log generated is that the existing models, such as Burattin&#x2019;s PLG [<xref ref-type="bibr" rid="ref-26">26</xref>], merely generates event logs of the process models in Petri nets, whereas we used BPMN for designing our process model. A key feature of the PLG V1.0 is that it can be used to populate a log of five different patterns. The patterns are presented in <xref ref-type="table" rid="table-1">Tab. 1</xref> and a screenshot of the implementation is shown presented in <xref ref-type="fig" rid="fig-4">Fig. 4</xref>.</p>
<table-wrap id="table-1">
<label>Table 1</label>
<caption>
<title>All possible case instance scenarios &#x2018;maternity regular visit&#x2019;</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Case pattern</th>
<th>Complete case execution pattern</th>
</tr>
</thead>
<tbody>
<tr>
<td>CP_1</td>
<td><inline-formula id="ieqn-9"><alternatives><inline-graphic xlink:href="ieqn-9.png"/><tex-math id="tex-ieqn-9"><![CDATA[$T_{A}\rightarrow \mathrm{END}$]]></tex-math><mml:math id="mml-ieqn-9"><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>A</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>E</mml:mi><mml:mi>N</mml:mi><mml:mi>D</mml:mi></mml:mstyle></mml:math></alternatives></inline-formula></td>
</tr>
<tr>
<td>CP_2</td>
<td><inline-formula id="ieqn-10"><alternatives><inline-graphic xlink:href="ieqn-10.png"/><tex-math id="tex-ieqn-10"><![CDATA[$T_{A}\rightarrow T_{B}\rightarrow\;$]]></tex-math><mml:math id="mml-ieqn-10"><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>A</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>B</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:mspace width="2.77695pt" class="tmspace"/></mml:math></alternatives></inline-formula> .. Continue to other process.. END</td>
</tr>
<tr>
<td>CP_3</td>
<td><inline-formula id="ieqn-11"><alternatives><inline-graphic xlink:href="ieqn-11.png"/><tex-math id="tex-ieqn-11"><![CDATA[$T_{A}\rightarrow T_{C}\rightarrow T_{D}\rightarrow T_{E}\rightarrow T_{F}\rightarrow T_{G}\rightarrow T_{H}\ldots \mathrm{Continue}$]]></tex-math><mml:math id="mml-ieqn-11"><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>A</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>D</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>E</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>F</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>G</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>H</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2026;</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>C</mml:mi><mml:mi>o</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>n</mml:mi><mml:mi>u</mml:mi><mml:mi>e</mml:mi></mml:mstyle></mml:math></alternatives></inline-formula></td>
</tr>
<tr>
<td>CP_4</td>
<td><inline-formula id="ieqn-12"><alternatives><inline-graphic xlink:href="ieqn-12.png"/><tex-math id="tex-ieqn-12"><![CDATA[$T_{A}\rightarrow T_{C}\rightarrow T_{D}\rightarrow T_{E}\rightarrow T_{F}\rightarrow T_{G}\rightarrow T_{H}\rightarrow T_{I}\rightarrow T_{J}\rightarrow T_{K}\rightarrow T_{L}\rightarrow T_{O}\rightarrow T_{P}\rightarrow \mathrm{END}$]]></tex-math><mml:math id="mml-ieqn-12"><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>A</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>D</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>E</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>F</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>G</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>H</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>I</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>J</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>K</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>L</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>O</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>P</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>E</mml:mi><mml:mi>N</mml:mi><mml:mi>D</mml:mi></mml:mstyle></mml:math></alternatives></inline-formula></td>
</tr>
<tr>
<td>CP_5</td>
<td><inline-formula id="ieqn-13"><alternatives><inline-graphic xlink:href="ieqn-13.png"/><tex-math id="tex-ieqn-13"><![CDATA[$T_{A}\rightarrow T_{C}\rightarrow T_{D}\rightarrow T_{E}\rightarrow T_{F}\rightarrow T_{G}\rightarrow T_{H}\rightarrow T_{I}\rightarrow T_{J}\rightarrow T_{M}\rightarrow T_{N}\rightarrow T_{O}\rightarrow T_{P}\rightarrow \mathrm{END}$]]></tex-math><mml:math id="mml-ieqn-13"><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>A</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>C</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>D</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>E</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>F</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>G</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>H</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>I</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>J</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>M</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>O</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:msub><mml:mrow><mml:mi>T</mml:mi></mml:mrow><mml:mrow><mml:mi>P</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2192;</mml:mo><mml:mstyle mathvariant="normal"><mml:mi>E</mml:mi><mml:mi>N</mml:mi><mml:mi>D</mml:mi></mml:mstyle></mml:math></alternatives></inline-formula></td>
</tr>
</tbody>
</table>
</table-wrap>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>A screenshot of the process log generator (PLGV1.0) [<xref ref-type="bibr" rid="ref-10">10</xref>]</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-4.png"/>
</fig>
</sec>
<sec id="s6">
<label>6</label>
<title>Healthcare Business Process Model</title>
<p>For the illustration, we have selected a business process for maternity regular visits from a Malaysian hospital. In this section, we introduce the business process, whereas, in the next section, we use it for illustration. To make the illustration closer to the real world, we visited a maternity clinic and observed all activities and sequence of activities over a period of time. It was observed that whenever a patient wants to visit a doctor, she has to request an appointment. If the appointment is granted, the patient is allowed to visit the doctor otherwise she is asked to wait for the appointment confirmation. If a patient is granted an appointment, the nurse will perform an initial check. For the first time visitor, the nurse takes blood and urine samples and sends them to the laboratory for examination.</p>
<p>For subsequent visits, the nurse performs three activities, measuring weight, blood pressure, and diabetic sugar level, and record them in the patient history card. During the visit, the doctor can see the test reports along with the patient history and can also perform ultrasound. However, if the doctor assesses that patient is unstable and ready to deliver the child, the patient is admitted to the hospital. Alternately, she is prescribed medicines and the patient is passed to a second nurse, who is responsible for post checkup activities, such as injecting medicine and forwarding to the pharmacy. Finally, the patient goes to the payment counter and pays the bill. The BPMN diagram of the maternity process is shown in <xref ref-type="fig" rid="fig-5">Fig. 5</xref>.</p>
<fig id="fig-5">
<label>Figure 5</label> 
<caption>
<title>BPMN of &#x2018;maternity regular visit&#x2019; business process [<xref ref-type="bibr" rid="ref-10">10</xref>] 
</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-5.png"/>
</fig>
<p>The execution of the business process involves three nurses (n1, n2, n3) in role (r1) working at different positions (Senior Nurse, Junior Nurse), Doctor (n4) in role (r2) working as (lady doctor, surgeon), and a counter clerk in (r3) working at position (junior clerk). Besides that, the following non-human resources are involved, weight machine, blood pressure checker, urine test strips, ultrasound machine, injections, and medicines. One trace of an event log from PLG v1.0 for Case pattern 1 is shown in <xref ref-type="table" rid="table-2">Tab. 2</xref>. The generated traces cover two types of events, start event and end event, where TaskID <italic>T<sub>A</sub></italic> represents &#x2018;Appointment with a doctor.&#x2019; Each entry in the process log is uniquely identified by Data_Record filed value. The values for CaseID and TasksID will remain the same for start and end, event types. For the experiment, the PLG v1.0 generated 780 traces to populate the execution log.</p>
<table-wrap id="table-2">
<label>Table 2</label>
<caption>
<title>One instance of PLG 1.0 generated log for pattern1 (event Log)</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
<col/>
<col/>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Case_ID</th>
<th>Task_ID</th>
<th>Task_name</th>
<th>Event_type</th>
<th>SnE_date</th>
<th>Generator</th>
<th>Data_record</th>
</tr>
</thead>
<tbody>
<tr>
<td>Instance_CP1_1</td>
<td>A</td>
<td>Appointment</td>
<td>Start</td>
<td>30-12-2010:11.02</td>
<td>PLG V1.0</td>
<td>CP1_1A_S</td>
</tr>
<tr>
<td>Instance_CP1_1</td>
<td>A</td>
<td>Appointment</td>
<td>Unsuccessful end</td>
<td>30-12-2010:11.04</td>
<td>PLG V1.0</td>
<td>CP1_1B_E</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s7">
<label>7</label>
<title>Method Illustration</title>
<p>As discussed earlier, due the unavailability of real process log data, we generated synthetic data using PLG V1.0. That is, we used the following settings, <inline-formula id="ieqn-14"><alternatives><inline-graphic xlink:href="ieqn-14.png"/><tex-math id="tex-ieqn-14"><![CDATA[$\mathrm{Pattern1 = 10}$]]></tex-math><mml:math id="mml-ieqn-14"><mml:mstyle mathvariant="normal"><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>n</mml:mi><mml:mn>1</mml:mn><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mn>0</mml:mn></mml:mstyle></mml:math></alternatives></inline-formula>, <inline-formula id="ieqn-15"><alternatives><inline-graphic xlink:href="ieqn-15.png"/><tex-math id="tex-ieqn-15"><![CDATA[$\mathrm{Pattern2 = 50}$]]></tex-math><mml:math id="mml-ieqn-15"><mml:mstyle mathvariant="normal"><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>n</mml:mi><mml:mn>2</mml:mn><mml:mo>=</mml:mo><mml:mn>5</mml:mn><mml:mn>0</mml:mn></mml:mstyle></mml:math></alternatives></inline-formula>, <inline-formula id="ieqn-16"><alternatives><inline-graphic xlink:href="ieqn-16.png"/><tex-math id="tex-ieqn-16"><![CDATA[$\mathrm{Pattern3 = 20}$]]></tex-math><mml:math id="mml-ieqn-16"><mml:mstyle mathvariant="normal"><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>n</mml:mi><mml:mn>3</mml:mn><mml:mo>=</mml:mo><mml:mn>2</mml:mn><mml:mn>0</mml:mn></mml:mstyle></mml:math></alternatives></inline-formula>, <inline-formula id="ieqn-17"><alternatives><inline-graphic xlink:href="ieqn-17.png"/><tex-math id="tex-ieqn-17"><![CDATA[$\mathrm{Pattern4 = 76}$]]></tex-math><mml:math id="mml-ieqn-17"><mml:mstyle mathvariant="normal"><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>n</mml:mi><mml:mn>4</mml:mn><mml:mo>=</mml:mo><mml:mn>7</mml:mn><mml:mn>6</mml:mn></mml:mstyle></mml:math></alternatives></inline-formula>, and <inline-formula id="ieqn-18"><alternatives><inline-graphic xlink:href="ieqn-18.png"/><tex-math id="tex-ieqn-18"><![CDATA[$\mathrm{Pattern5 = 35}$]]></tex-math><mml:math id="mml-ieqn-18"><mml:mstyle mathvariant="normal"><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>n</mml:mi><mml:mn>5</mml:mn><mml:mo>=</mml:mo><mml:mn>3</mml:mn><mml:mn>5</mml:mn></mml:mstyle></mml:math></alternatives></inline-formula>. As a result, 3386 records were generated with two different start and end event types. We used the MSQL Server 2008 to store and retrieve the process log. Below, we illustrate each step of the method.</p>
<sec id="s7_1">
<label>7.1</label>
<title>Task History Identifications</title>
<p>The task history identification step explores the list of tasks and non-human resources used in those tasks against a set of roles. The query and an excerpt of the output are shown in <xref ref-type="table" rid="table-3">Tab. 3</xref>. The query extracted 1693 records, however, due to space limitation, we have selected the &#x2018;injection insulin&#x2019; task to explore the expected results from the method. This task was instantiated 76 times. For these instances, the output of the first step is shown in <xref ref-type="table" rid="table-4">Tab. 4</xref>.</p>
<table-wrap id="table-3">
<label>Table 3</label>
<caption>
<title>Identifications of the task list for the role of &#x2018;Nsurse&#x2019;</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Example query S1</th>
<th colspan="3">Output of query S1</th>
</tr>
<tr>
<th></th>
<th>Task instance</th>
<th>Task identity</th>
<th>Role identity</th>
</tr>
</thead>
<tbody>
<tr>
<td>Select [Case_ID], [Task_Name] as &#x201C;Task Identity,&#x201D; [HR Role] as &#x201C;[Role Identity]&#x201D; From [PLG].[dbo].[Health_Care] where [SnE_Date] between &#x2018;30-12-2000:11.06&#x2019; and &#x2018;30-12-2013:11.06&#x2019; Group by Role = &#x2018;Nurse&#x2019;</td>
<td>Instance_CP4_1_K</td>
<td>Injection insulin</td>
<td>Nurse</td>
</tr>
<tr>
<td/>
</tr>
<tr>
<td/>
</tr>
<tr>
<td/>
<td>Instance_CP4_2_K</td>
<td>Injection insulin</td>
<td>Nurse</td>
</tr>
<tr>
<td/>
<td>Instance_CP4_3_K</td>
<td>Injection insulin</td>
<td>Nurse</td>
</tr>
<tr>
<td/>
<td><inline-formula id="ieqn-19"><alternatives><inline-graphic xlink:href="ieqn-19.png"/><tex-math id="tex-ieqn-19"><![CDATA[$\ldots$]]></tex-math><mml:math id="mml-ieqn-19"><mml:mo>&#x2026;</mml:mo></mml:math></alternatives></inline-formula></td>
<td><inline-formula id="ieqn-20"><alternatives><inline-graphic xlink:href="ieqn-20.png"/><tex-math id="tex-ieqn-20"><![CDATA[$\ldots$]]></tex-math><mml:math id="mml-ieqn-20"><mml:mo>&#x2026;</mml:mo></mml:math></alternatives></inline-formula></td>
<td>Nurse</td>
</tr>
<tr>
<td/>
<td>Instance_CP2_9_B</td>
<td>Blood sampling</td>
<td>Nurse</td>
</tr>
<tr>
<td/>
<td>Instance_CP2_11_B</td>
<td>Blood sampling</td>
<td>Nurse</td>
</tr>
<tr>
<td/>
<td><inline-formula id="ieqn-21"><alternatives><inline-graphic xlink:href="ieqn-21.png"/><tex-math id="tex-ieqn-21"><![CDATA[$\ldots$]]></tex-math><mml:math id="mml-ieqn-21"><mml:mo>&#x2026;</mml:mo></mml:math></alternatives></inline-formula></td>
<td><inline-formula id="ieqn-22"><alternatives><inline-graphic xlink:href="ieqn-22.png"/><tex-math id="tex-ieqn-22"><![CDATA[$\ldots$]]></tex-math><mml:math id="mml-ieqn-22"><mml:mo>&#x2026;</mml:mo></mml:math></alternatives></inline-formula></td>
<td><inline-formula id="ieqn-23"><alternatives><inline-graphic xlink:href="ieqn-23.png"/><tex-math id="tex-ieqn-23"><![CDATA[$\ldots$]]></tex-math><mml:math id="mml-ieqn-23"><mml:mo>&#x2026;</mml:mo></mml:math></alternatives></inline-formula></td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="table-4">
<label>Table 4</label>
<caption>
<title>Task history of &#x2018;injection insulin&#x2019;</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
<col/>
<col/>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Case ID</th>
<th>Task ID</th>
<th>U-100 (R1)</th>
<th>Typical syringe (R2)</th>
<th>Injection medicine (R3)</th>
<th>Injection mix (R4)</th>
<th>Status</th>
</tr>
</thead>
<tbody>
<tr>
<td>CP4_1_K</td>
<td>Injection insulin (&#x2018;K&#x2019;)</td>
<td>Used</td>
<td>Not used</td>
<td>Used</td>
<td>Not used</td>
<td>Successful</td>
</tr>
<tr>
<td>CP4_10_K</td>
<td/>
<td>Not used</td>
<td>Used</td>
<td>Used</td>
<td>Not used</td>
<td>Successful</td>
</tr>
<tr>
<td>CP4_11_K</td>
<td/>
<td>Used</td>
<td>Not used</td>
<td>Used</td>
<td>Not used</td>
<td>Unsuccessful</td>
</tr>
<tr>
<td>CP4_12_K</td>
<td/>
<td>Used</td>
<td>Not used</td>
<td>Used</td>
<td>Not used</td>
<td>Successful</td>
</tr>
<tr>
<td>CP4_13_K</td>
<td/>
<td>Not used</td>
<td>Used</td>
<td>Used</td>
<td>Used</td>
<td>Successful</td>
</tr>
<tr>
<td>CP4_14_K</td>
<td/>
<td>Not used</td>
<td>Used</td>
<td>Used</td>
<td>Not used</td>
<td>Successful</td>
</tr>
<tr>
<td>CP4_14_K</td>
<td/>
<td>Not used</td>
<td>Used</td>
<td>Used</td>
<td>Used</td>
<td>Unsuccessful</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s7_2">
<label>7.2</label>
<title>Suitability Evaluation Sheet Creation</title>
<p>The second step aims to produce values for suitability behavior, in terms of reliability, completeness, and accuracy. An excerpt from the suitability evaluation sheet for the &#x2018;Injection insulin&#x2019; task is shown in <xref ref-type="table" rid="table-5">Tab. 5</xref>.</p>
<table-wrap id="table-5">
<label>Table 5</label>
<caption>
<title>Task suitability evaluation sheet for one instance</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Instance</th>
<th>Resource</th>
<th colspan="3">Summarized suitability attributes values for task &#x2018;inject insulin&#x2019;</th>
</tr>
<tr>
<th></th>
<th></th>
<th>Reliability</th>
<th>Completeness</th>
<th>Accuracy</th>
</tr>
</thead>
<tbody>
<tr>
<td>Ins_CP4_1_K</td>
<td>R<sub>1</sub></td>
<td>100</td>
<td>100</td>
<td>100</td>
</tr>
<tr>
<td/>
<td>R<sub>2</sub></td>
<td>NA</td>
<td>NA</td>
<td>NA</td>
</tr>
<tr>
<td/>
<td>R<sub>3</sub></td>
<td>40</td>
<td>40</td>
<td>20</td>
</tr>
<tr>
<td/>
<td>R<sub>4</sub></td>
<td>NA</td>
<td>NA</td>
<td>NA</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s7_3">
<label>7.3</label>
<title>Suitability Calculations</title>
<p>The output from the preceding step, the suitability evaluation sheet, is taken as the input of this step. The values are then normalized to a range of 1&#x2013;5 and represented as a matrix in <xref ref-type="fig" rid="fig-6">Fig. 6</xref>. The matrix for one task is represented as SDS1, whereas, the weighting scheme given as input by the user is shown as the SWD matrix. The dot product of the two products leads to generating SDS. Finally, row-wise summation produces suitability for the resource-task pair. In the figure, the total suitability score for each resource (R<sub>1</sub>, R<sub>2</sub>, <inline-formula id="ieqn-24"><alternatives><inline-graphic xlink:href="ieqn-24.png"/><tex-math id="tex-ieqn-24"><![CDATA[$\ldots$]]></tex-math><mml:math id="mml-ieqn-24"><mml:mo>&#x2026;</mml:mo></mml:math></alternatives></inline-formula> R<sub>4</sub>) is represented by S.</p>
<fig id="fig-6">
<label>Figure 6</label>
<caption>
<title>Suitability&#x2019;s calculations of task &#x2018;Injection insulin&#x2019; (procedure S3, an example output) 
</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-6.png"/>
</fig>
<p>For each reading, the final output of the suitability evaluation method is shown in <xref ref-type="table" rid="table-6">Tab. 6</xref>, which is annotated with linguistic terms that vary from strongly suitable to strongly unsuitable.</p>
<table-wrap id="table-6">
<label>Table 6</label>
<caption>
<title>Resource suitability evaluation final output</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
<col/>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Time</th>
<th>Task</th>
<th>Non-human resource</th>
<th>Suitability value</th>
<th>Suitability scale</th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<td>&#x2018;30-12-2000:11.06&#x2019; to &#x2018;30-12-2013:11.06&#x2019;</td>
<td>Injection insulin</td>
<td>R1</td>
<td>4.8</td>
<td>Strongly suitable</td>
<td/>
</tr>
<tr>
<td/>
<td/>
<td>R2</td>
<td>2.58</td>
<td>Between unsuitable &#x0026; neither unsuitable nor suitable</td>
<td/>
</tr>
<tr>
<td/>
<td/>
<td>R3</td>
<td>2.9</td>
<td>Neither unsuitable nor suitable</td>
<td/>
</tr>
<tr>
<td/>
<td/>
<td>R4</td>
<td>4.82</td>
<td>Strongly suitable</td>
<td/>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec id="s8">
<label>8</label>
<title>Method Evaluation</title>
<p>For the evaluation of the proposed method, we have used Hong&#x2019;s Technology Acceptance Model [<xref ref-type="bibr" rid="ref-27">27</xref>] due to two reasons: (a) The model is based on the famous Technology Acceptance Model [<xref ref-type="bibr" rid="ref-28">28</xref>] and the IS Success Model [<xref ref-type="bibr" rid="ref-29">29</xref>], and (b) The model is customized to adjust the factors affecting data warehouse success [<xref ref-type="bibr" rid="ref-30">30</xref>]. For the experimentation, eleven respondents with computing and data warehousing knowledge were randomly selected from the University of Technology Petronas, Malaysia. The participants include faculty members, graduate students, and undergraduate students. For the study, the participants were asked to analyze the suitability of non-human resources for the maternity process, without any additional help. Subsequently, we presented our method and demonstrated the use of our method using small examples. Thereafter, participants were asked to use our proposed method for repeating the same task.</p>
<p>The results of the post task survey are presented in <xref ref-type="fig" rid="fig-7">Fig. 7</xref>. It can be observed from the figure that our method successfully presents relevant information to the user but the granularity is minimum which makes the information level strictly relevant with less flexibility. Although it reduces the freedom to use PW, however, we argue that the user always has the option to make use of the classical approach to use PW. Thus, we further advocate that the two approaches supplement each other and hence increases the usability of PW.</p>
<fig id="fig-7">
<label>Figure 7</label>
<caption>
<title>Information quality comparison, with and without our method</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-7.png"/>
</fig>
<p>For analysis of the responses, faculty members, as well as the PhD students, were considered experts. Whereas, graduate students enrolled in a course on business process management were considered intermediate respondents, whereas, the undergraduate students were considered novice respondents. Accordingly, our study participants include three expert, four intermediate, and four novice respondents. <xref ref-type="fig" rid="fig-8">Fig. 8</xref> shows a comparison of the survey results using our proposed method and without using our proposed method. From the graph, it can be observed that no significant differences were observed between all three response groups indicating that each group had equally perceived all variables while using our method.</p>
<fig id="fig-8">
<label>Figure 8</label>
<caption>
<title>Comparison of respondent groups</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="fig-8.png"/>
</fig>
</sec>
<sec id="s9">
<label>9</label>
<title>Conclusions</title>
<p>Analysis of process execution is very much desired because it serves as a base for taking improvement decisions. There are two major types of business process analyses, structural and resource level. The structural analysis deals with analyzing the arrangement of activities and corresponding improvement deals with rearranging healthcare activities. On the other hand, resource analysis deals with analyzing the resources associated with each activity of the process, and the corresponding improvement deals with reassigning resources to activities.</p>
<p>In this study, we contend that there are two types of resources, human and non-human resources and they differ in terms of their behavior and impact on process performance. Thus they should be analyzed differently. However, no work has been done on evaluating the suitability of non-human resources in processes. Consequently, it becomes difficult to identify and subsequently overcome the inefficiencies caused by the non-human resources in delivering services to the customer. To address this problem, we have presented a three-step method that can be used to evaluate the suitability of the resource-task pair. The method is rooted in a suitability model that includes the different concepts which should be considered for the suitability analysis of task-resource pair.</p>
<p>Particularly, the method can guide the use of process warehouse for identifying non-human resource deficiencies in business processes. Applicability of the proposed method is demonstrated with a healthcare case study and an empirical study to evaluate the usability of the proposed method. The encouraging results of the study reflect the usefulness of the proposed method.</p></sec>
</body>
<back>
<fn-group><fn fn-type="other"><p><bold>Funding Statement:</bold> The author(s) received no specific funding for this study</p></fn>
<fn fn-type="conflict"><p><bold>Conflicts of Interest:</bold> The authors declare that they have no conflicts of interest to report regarding the present study.</p></fn></fn-group>
<ref-list content-type="authoryear">
<title>References</title>
<ref id="ref-1"><label>[1]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>W. M. P.</given-names> <surname>Van der Aalst</surname></string-name></person-group>, &#x201C;<article-title>Business process management: A comprehensive survey</article-title>,&#x201D; <source>ISRN Software Engineering</source>, vol. <volume>2013</volume>, no. <issue>1</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>37</lpage>, <year>2013</year>.</mixed-citation></ref>
<ref id="ref-2"><label>[2]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Weske</surname></string-name></person-group>, <chapter-title>Business process management architectures</chapter-title>. In: <source>Business Process Management SE-7</source>. 2<inline-formula id="ieqn-25"><alternatives><inline-graphic xlink:href="ieqn-25.png"/><tex-math id="tex-ieqn-25"><![CDATA[$^{\mathrm{nd}}$]]></tex-math><mml:math id="mml-ieqn-25"><mml:msup><mml:mrow></mml:mrow><mml:mrow><mml:mstyle mathvariant="normal"><mml:mi>n</mml:mi><mml:mi>d</mml:mi></mml:mstyle></mml:mrow></mml:msup></mml:math></alternatives></inline-formula> ed., <publisher-loc>Berlin Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>, pp. <fpage>333</fpage>&#x2013;<lpage>371</lpage>, <year>2012</year>.</mixed-citation></ref>
<ref id="ref-3"><label>[3]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>L. C. L.</given-names> <surname>Chen</surname></string-name>, <string-name><given-names>T. X. T.</given-names> <surname>Xue</surname></string-name> and <string-name><given-names>A. Y. A.</given-names> <surname>Yang</surname></string-name></person-group>, &#x201C;<article-title>Business process continuous improvement system based on workflow mining technology</article-title>,&#x201D; in <conf-name>Proc. World Congress on Computer Science and Information Engineering</conf-name>, Los Angeles, CA, USA, pp. <fpage>414</fpage>&#x2013;<lpage>418</lpage>, <year>2009</year>.</mixed-citation></ref>
<ref id="ref-4"><label>[4]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Zur Muehlen</surname></string-name></person-group>, &#x201C;<article-title>Organizational management in workflow applications&#x2013;-issues and perspectives</article-title>,&#x201D; <source>Information Technology and Management</source>, vol. <volume>5</volume>, no. <issue>3</issue>, pp. <fpage>271</fpage>&#x2013;<lpage>291</lpage>, <year>2004</year>.</mixed-citation></ref>
<ref id="ref-5"><label>[5]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Sohail</surname></string-name> and <string-name><given-names>D. D.</given-names> <surname>Dominic</surname></string-name></person-group>, &#x201C;<article-title>A unified framework for business process intelligence</article-title>,&#x201D; in <conf-name>Proc. of the First Int. Conf. on Advanced Data and Information Engineering (DaEng-2013)</conf-name>, Batu Pahat, Johor, Malaysia, pp. <fpage>437</fpage>&#x2013;<lpage>444</lpage>, <year>2014</year>.</mixed-citation></ref>
<ref id="ref-6"><label>[6]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>D.</given-names> <surname>Grigori</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Casati</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Castellanos</surname></string-name>, <string-name><given-names>U.</given-names> <surname>Dayal</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Sayal</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Business process intelligence</article-title>,&#x201D; <source>Computers in Industry</source>, vol. <volume>53</volume>, no. <issue>3</issue>, pp. <fpage>321</fpage>&#x2013;<lpage>343</lpage>, <year>2004</year>.</mixed-citation></ref>
<ref id="ref-7"><label>[7]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Zur Muehlen</surname> </string-name></person-group>, &#x201C;<article-title>Process-driven management information systems combining data warehouses and workflow technology</article-title>,&#x201D; in <conf-name>Proc. of the Int. Conf. on Electronic Commerce Research (ICECR-4)</conf-name>, Dallas, USA, pp. <fpage>550</fpage>&#x2013;<lpage>566</lpage>, <year>2001</year>.</mixed-citation></ref>
<ref id="ref-8"><label>[8]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Sohail</surname></string-name>, <string-name><given-names>P. D. D.</given-names> <surname>Dominic</surname></string-name> and <string-name><given-names>K.</given-names> <surname>Shahzad</surname></string-name></person-group>, &#x201C;<article-title>A Process warehouse based resource suitability evaluation method for business process improvement</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Computer, Communications, and Control Technology (I4CT)</conf-name>, Kedah, Malaysia, pp. <fpage>75</fpage>&#x2013;<lpage>79</lpage>, <year>2014</year>.</mixed-citation></ref>
<ref id="ref-9"><label>[9]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>M. K.</given-names> <surname>Shahzad</surname></string-name></person-group>, &#x201C;<article-title>Improving business processes using process-oriented data warehouse</article-title>,&#x201D; <comment>Ph.D. dissertation</comment>, <publisher-name>KTH Royal Institute of Technology</publisher-name>, <publisher-loc>KTH Sweden</publisher-loc>, <year>2012</year>.</mixed-citation></ref>
<ref id="ref-10"><label>[10]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Sohail</surname></string-name></person-group>, &#x201C;<article-title>Process warehouse based resource evaluation approach for business process analysis</article-title>,&#x201D; <comment>Ph.D. dissertation</comment>, <publisher-name>Universiti Teknology PETRONAS</publisher-name>, <publisher-loc>UTP, Malaysia</publisher-loc>, <year>2015</year>.</mixed-citation></ref>
<ref id="ref-11"><label>[11]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Sohail</surname></string-name>, <string-name><given-names>P. D. D.</given-names> <surname>Dominic</surname></string-name> and <string-name><given-names>K.</given-names> <surname>Shahzad</surname></string-name></person-group>, &#x201C;<article-title>Business process analysis: A process warehouse based resource preference evaluation method</article-title>,&#x201D; <source>International Journal of Business Information Systems</source>, vol. <volume>21</volume>, no. <issue>2</issue>, pp. <fpage>137</fpage>&#x2013;<lpage>161</lpage>, <year>2016</year>.</mixed-citation></ref>
<ref id="ref-12"><label>[12]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Sohail</surname></string-name>, <string-name><given-names>P. D. D.</given-names> <surname>Dominic</surname></string-name> and <string-name><given-names>K.</given-names> <surname>Shahzad</surname></string-name></person-group>, &#x201C;<article-title>A process warehouse based resource performance evaluation method for business processes improvement</article-title>,&#x201D; in <conf-name>Proc. of the Int. Conf. on Computer and Information Sciences (ICCOINS)</conf-name>, Kuala Lumpur, Malaysia, pp. <fpage>1</fpage>&#x2013;<lpage>6</lpage>, <year>2014</year>.</mixed-citation></ref>
<ref id="ref-13"><label>[13]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Z.</given-names> <surname>Huang</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Lu</surname></string-name> and <string-name><given-names>H.</given-names> <surname>Duan</surname></string-name></person-group>, &#x201C;<article-title>A task operation model for resource allocation optimization in business process management</article-title>,&#x201D; <source>Systems, Man and Cybernetics, Part A: Systems and Humans, IEEE Transactions on</source>, vol. <volume>42</volume>, no. <issue>5</issue>, pp. <fpage>1256</fpage>&#x2013;<lpage>1270</lpage>, <year>2012</year>.</mixed-citation></ref>
<ref id="ref-14"><label>[14]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>C.</given-names> <surname>Ouyang</surname></string-name>, <string-name><given-names>M. T.</given-names> <surname>Wynn</surname></string-name>, <string-name><given-names>C.</given-names> <surname>Fidge</surname></string-name>, <string-name><given-names>A. H. M.</given-names> <surname>Ter Hofstede</surname></string-name> and <string-name><given-names>J. C.</given-names> <surname>Kuhr</surname></string-name></person-group>, &#x201C;<article-title>Modelling complex resource requirements in business process management systems</article-title>,&#x201D; in <conf-name>Proc. of the ACIS 2010</conf-name>, Brisbane, Australia, pp. <fpage>1</fpage>&#x2013;<lpage>12</lpage>, <year>2010</year>.</mixed-citation></ref>
<ref id="ref-15"><label>[15]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Sohail</surname></string-name>, <string-name><given-names>P. D. D.</given-names> <surname>Dominic</surname></string-name> and <string-name><given-names>K.</given-names> <surname>Shahzad</surname></string-name></person-group>, &#x201C;<article-title>A process warehouse based resource suitability evaluation method for business process improvement</article-title>,&#x201D; in <conf-name>IEEE Int. Conf. on Computer, Communications, and Control Technology</conf-name>, <publisher-loc>Langkawi, Malaysia</publisher-loc>, pp. <fpage>75</fpage>&#x2013;<lpage>79</lpage>, <year>2014</year>.</mixed-citation></ref>
<ref id="ref-16"><label>[16]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Erasmus</surname></string-name>, <string-name><given-names>I.</given-names> <surname>Vanderfeesten</surname></string-name>, <string-name><given-names>K.</given-names> <surname>Traganos</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Jie-A-Looi</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Kleingeld</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>A method to enable ability-based human resource allocation in business process management systems</article-title>,&#x201D; in <conf-name>IFIP Working Conf. on The Practice of Enterprise Modeling</conf-name>, <publisher-loc>Vienna, Austria</publisher-loc>, <publisher-name>Springer, Cham</publisher-name>, pp. <fpage>37</fpage>&#x2013;<lpage>52</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-17"><label>[17]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>I.</given-names> <surname>Ajzen</surname></string-name></person-group>, &#x201C;<article-title>The theory of planned behavior</article-title>,&#x201D; <source>Organizational Behavior and Human Decision Processes</source>, vol. <volume>50</volume>, no. <issue>2</issue>, pp. <fpage>179</fpage>&#x2013;<lpage>211</lpage>, <year>1991</year>.</mixed-citation></ref>
<ref id="ref-18"><label>[18]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Xu</surname></string-name>, <string-name><given-names>C.</given-names> <surname>Liu</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Zhao</surname></string-name> and <string-name><given-names>Z.</given-names> <surname>Ding</surname></string-name></person-group>, &#x201C;<article-title>Incorporating structural improvement into resource allocation for business process execution planning</article-title>,&#x201D; <source>Concurrency and Computation: Practice and Experience</source>, vol. <volume>25</volume>, no. <issue>3</issue>, pp. <fpage>427</fpage>&#x2013;<lpage>442</lpage>, <year>2013</year>.</mixed-citation></ref>
<ref id="ref-19"><label>[19]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Macris</surname></string-name>, <string-name><given-names>E.</given-names> <surname>Papadimitriou</surname></string-name> and <string-name><given-names>G.</given-names> <surname>Vassilacopoulos</surname></string-name></person-group>, &#x201C;<article-title>An ontology-based competency model for workflow activity assignment policies</article-title>,&#x201D; <source>Journal of Knowledge Management</source>, vol. <volume>12</volume>, no. <issue>6</issue>, pp. <fpage>72</fpage>&#x2013;<lpage>88</lpage>, <year>2008</year>.</mixed-citation></ref>
<ref id="ref-20"><label>[20]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Kumar</surname></string-name>, <string-name><given-names>R.</given-names> <surname>Dijkman</surname></string-name> and <string-name><given-names>M.</given-names> <surname>Song</surname></string-name></person-group>, &#x201C;<chapter-title>Optimal resource assignment in workflows for maximizing cooperation</chapter-title>, &#x201D; in <source>Business Process Management</source>, <publisher-loc>Beijing, China</publisher-loc>, <publisher-name>Springer, Berlin, Heidelberg</publisher-name>, pp. <fpage>235</fpage>&#x2013;<lpage>250</lpage>, <year>2013</year>.</mixed-citation></ref>
<ref id="ref-21"><label>[21]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><given-names>O. M. G.</given-names> <surname>OMG</surname></string-name></person-group>, &#x201C;<article-title>Common warehouse metamodel (CWM) specification</article-title>,&#x201D; <year>2003</year>. <comment>[Online]. <uri>https://www.omg.org/spec/CWM/1.1/PD</uri>.</comment></mixed-citation></ref>
<ref id="ref-22"><label>[22]</label><mixed-citation publication-type="other"><person-group person-group-type="author"><collab>Bizagi</collab></person-group>, &#x201C;<article-title>Business process management (BPM) solutions</article-title>. <comment>[Online]. Available: <uri>http://www.bizagi.com/</uri>.</comment></mixed-citation></ref>
<ref id="ref-23"><label>[23]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Heravizadeh</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Mendling</surname></string-name> and <string-name><given-names>M.</given-names> <surname>Rosemann</surname></string-name></person-group>, &#x201C;<article-title>Dimensions of business processes quality (QoBP)</article-title>,&#x201D; in <conf-name>Int. Conf. on Business Process Management</conf-name>, <publisher-loc>Ulm, Germany</publisher-loc>, <publisher-name>Springer, Berlin, Heidelberg</publisher-name>, pp. <fpage>80</fpage>&#x2013;<lpage>91</lpage>, <year>2009</year>.</mixed-citation></ref>
<ref id="ref-24"><label>[24]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>P.</given-names> <surname>Loucopoulos</surname></string-name> and <string-name><given-names>F.</given-names> <surname>Heidari</surname></string-name></person-group>, &#x201C;<chapter-title>Evaluating quality of business processes</chapter-title>,&#x201D; in <source>Modelling and Quality in Requirements Engineering, Essays Dedicated to Martin Glinz on the Occasion of His 60th Birthday</source>, <publisher-loc>MV-Wissenschaft Munster,Germany</publisher-loc>, pp. <fpage>61</fpage>&#x2013;<lpage>73</lpage>, <year>2012</year>.</mixed-citation></ref>
<ref id="ref-25"><label>[25]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>L.</given-names> <surname>Feng</surname></string-name>, <string-name><given-names>L.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Dai</surname></string-name>, <string-name><given-names>L.</given-names> <surname>Yang</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Identifying game processes based on private working sets</article-title>,&#x201D; <source>Computers, Materials &#x0026; Continua</source>, vol. <volume>65</volume>, no. <issue>1</issue>, pp. <fpage>639</fpage>&#x2013;<lpage>651</lpage>, <year>2020</year>.</mixed-citation></ref>
<ref id="ref-26"><label>[26]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Burattin</surname></string-name> and <string-name><given-names>A.</given-names> <surname>Sperduti</surname></string-name></person-group>, &#x201C;<article-title>PLG: A framework for the generation of business process models and their execution logs</article-title>,&#x201D; in <conf-name>Int. Conf. on Business Process Management Workshops</conf-name>, <publisher-loc>Berlin, Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>, pp. <fpage>214</fpage>&#x2013;<lpage>219</lpage>, <year>2010</year>.</mixed-citation></ref>
<ref id="ref-27"><label>[27]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Hong</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Katerattanakul</surname></string-name>, <string-name><given-names>S. K.</given-names> <surname>Hong</surname></string-name> and <string-name><given-names>Q.</given-names> <surname>Cao</surname></string-name></person-group>, &#x201C;<article-title>Usage and perceived impact of data warehouses: A study in Korean financial companies</article-title>,&#x201D; <source>International Journal of Information Technology &#x0026; Decision Making</source>, vol. <volume>5</volume>, no. <issue>2</issue>, pp. <fpage>297</fpage>&#x2013;<lpage>315</lpage>, <year>2006</year>.</mixed-citation></ref>
<ref id="ref-28"><label>[28]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>F. D.</given-names> <surname>Davis</surname></string-name></person-group>, &#x201C;<article-title>A technology acceptance model for empirically testing new end-user information systems: Theory and results</article-title>,&#x201D; <comment>Ph.D. dissertation</comment>, <publisher-name>Massachusetts Institute of Technology</publisher-name>, <publisher-name>USA</publisher-name>, <year>1985</year>.</mixed-citation></ref>
<ref id="ref-29"><label>[29]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>W. H.</given-names> <surname>DeLone</surname></string-name> and <string-name><given-names>E. R.</given-names> <surname>McLean</surname></string-name></person-group>, &#x201C;<article-title>Information systems success: The quest for the dependent variable</article-title>,&#x201D; <source>Information Systems Research</source>, vol. <volume>3</volume>, no. <issue>1</issue>, pp. <fpage>60</fpage>&#x2013;<lpage>95</lpage>, <year>1992</year>.</mixed-citation></ref>
<ref id="ref-30"><label>[30]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>B. H.</given-names> <surname>Wixom</surname></string-name> and <string-name><given-names>H. J.</given-names> <surname>Watson</surname></string-name></person-group>, &#x201C;<article-title>An empirical investigation of the factors affecting data warehousing success</article-title>,&#x201D; <source>MIS Quarterly</source>, vol. <volume>25</volume>, no. <issue>1</issue>, pp. <fpage>17</fpage>&#x2013;<lpage>41</lpage>, <year>2001</year>.</mixed-citation></ref>
</ref-list>
</back>
</article>