<!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>An Approach to Forming Dashboards for Business Process Indicators Analysis using Fuzzy and Semantic Technologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andrii Kopp</string-name>
          <email>kopp93@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dmytro Orlovskyi</string-name>
          <email>orlovskyi.dm@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>National Technical University “KhPI”</institution>
          ,
          <addr-line>Kyrpychova str. 2, 61002 Kharkiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This article considers development of the approach to forming dashboards for business process indicators analysis. The approach idea is based on the dashboard design problem, outlined in analyzed works, which propose a lot of recommendations and best practices, but have a lack of formal approaches to dashboard design definition for specific business process indicators. This study considers application of fuzzy and semantic technologies in order to provide description and analysis of relations between analyzed business process indicators, indicator's types, and visualization tools. It also considers event log processing of a workflow system, used to execute business processes, which indicators are measured. As a result of implementation and application of the proposed approach, recommendations for a dashboard's design, based on specific business processes and their performance indicators to be analyzed, can be obtained and implemented. The theoretical essentials, workflow scheme, and early results of the proposed approach are given, future research is outlined.</p>
      </abstract>
      <kwd-group>
        <kwd>Key Performance Indicator</kwd>
        <kwd>Dashboard</kwd>
        <kwd>Fuzzy Semantic Network</kwd>
        <kwd>Event Log Processing</kwd>
        <kwd>Business Intelligence</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        As an extremely popular organizational management approach, Business Process
Management (BPM) includes a set of methods, techniques and tools, used for
modeling, execution, and analysis of organization’s business processes [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        One of the important aspects of BPM lifecycle (which includes business process
identification, discovery, analysis, redesign, implementation, monitoring and control)
is the continuous analysis of business process indicators. This activity is focused on a
set of Key Performance Indicators (KPI) and their target values, based on
organization’s business goals. Hence presentation of these KPIs, using various types of
Business Intelligence (BI) dashboards and reports, provides visualization of business
performance [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        Usually, BI dashboards present KPIs in visual form using diagrams or plain
images, such as using images of measuring tools (e.g. charts, gauges, graphs etc.). At the
same time, it’s necessary to choose data visualization techniques, which are clear,
easy interpretable, space efficient, attractive, and legible [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ].
      </p>
      <p>
        Hence, the KPIs dashboard design problem becomes relevant, because it requires
placing various visualization tools in a small space, while keeping them accessible
and easy to understand [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ]. Therefore, in this study we propose the approach to
forming dashboards for business process KPIs analysis.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>This section briefly discusses the existing body of other works, related to the
dashboard design problem.</p>
      <p>
        Author of [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] proposed two main principles, which define the choice of one or
another visualization tool:
 It has to be the best tool for displaying data of a certain type on a dashboard.
 It has to be capable of serving its purpose even when its size is changed in order to
place it into a small place.
      </p>
      <p>
        Besides the recommendations above, work [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] notes the basic mistakes of
dashboard design. The most common errors are associated with the choice of inappropriate
visualization tools.
      </p>
      <p>
        Eckerson and Hammond [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] outlined, that the most appropriate visualization tools,
used to create dashboards, are bar charts, line charts, pie charts, and gauges.
      </p>
      <p>
        Another research [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] also notes that bar charts, line charts, and gauges are the most
efficient visualization tools, which are proper for a quick comparison.
      </p>
      <p>
        KPIs, which are used to measure business performance, are often grouped into the
categories of quality, time, flexibility, and cost [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. To illustrate KPIs values of each
category, it’s recommended to use considered visualization tools, such as bar charts,
line charts, gauges etc [
        <xref ref-type="bibr" rid="ref4 ref7">4, 7</xref>
        ].
      </p>
      <p>
        In the best practice of dashboard design [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] Briggs proposed four types of KPIs:
 Quantitative. These are KPIs with a very specific number and where knowing this
number is critical (e.g. number of orders, number of sales).
 Directional. These are KPIs where the direction that values are trending is more
important than comparing these values (e.g. time spent to fulfill order).
 Category. These are KPIs that display a distribution of various categories within an
entire value (e.g. sales by product).
 Actionable. These KPIs have target values associated with them, as well as actions
that happen if actual values go up or down beyond this target values (e.g.
department costs, supply costs).
      </p>
      <p>
        Despite various recommendations for visualization tools usage [
        <xref ref-type="bibr" rid="ref6 ref7 ref8 ref9">6-9</xref>
        ], the dashboard
design still depends on individual users’ preferences, which are quite subjective.
      </p>
      <p>Therefore, the dashboard design problem should be formalized, and the approach
to forming dashboards for business process KPIs analysis should be elaborated.</p>
      <p>
        Earlier we’ve proposed the approach to forming dashboards for business process
state analysis [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], which formalizes a dashboard design procedure with considering
various visualization tools and their impact on the dashboard’s informativeness.
However in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] we didn’t consider the impact of relations between analyzed KPIs, KPI
types, and various visualization tools on the dashboard’s design.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Proposed Approach</title>
      <p>According to the proposed approach, the relations between analyzed KPIs, KPI types,
and visualization tools could be represented using a fuzzy semantic network.</p>
      <p>
        A semantic network is a graph structure for representing knowledge in patterns of
interconnected nodes and edges [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. In semantic networks concepts and relations are
appeared at nodes and edges respectively. In fuzzy semantic networks considered in
[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] relations are augmented by a fuzzy membership function   0,1 .
      </p>
      <p>Therefore, the set of nodes includes subsets of analyzed indicators KPI i  KPIs ,
KPI types KPIType j  KPITypes , and visualization tools VisTool k VisTools .</p>
      <p>Network’s edges represent following fuzzy relations between KPIs, KPI types, and
visualization tools (see figure 1):
 “type is” relation,  KPI i , KPIType j : KPIs  KPITypes  0,1 .
 “displayed by” relation,  KPIType j ,VisTool k : KPITypes VisTools  0,1 .</p>
      <p>
        Values  KPIType j ,VisTool k  represent individual user’s preferences for using
certain visualization tools. They also may be based on the best practice [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], where for
the each KPI type the ideal chart is defined.
      </p>
      <p>
        Values  KPI i , KPIType j  depend on the specific values of KPI and information
it communicates (according to the four types of KPIs outlined above) in the following
manner:
 If the value of KPI i is scalar, and it goes up or down beyond a target value [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], its
type KPIType j should be Actionable. Otherwise its type KPIType j should be
Directional, in order to display the direction of change [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
 If the value of KPI i is vector, which components represent parts of a 100% [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], its
type KPIType j should be Category. Otherwise its type KPIType j should be
Quantitative, in order to display the comparable quantitative data effectively [
        <xref ref-type="bibr" rid="ref6 ref9">6, 9</xref>
        ].
      </p>
      <p>
        Therefore, changes of the indicator KPI i of business process, which is performed
using a BPM system, could be described using following event [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]:
      </p>
      <p>event  eventID, caseID, KPI i , timeStamp , eval , KPIType j  ,
where eventID – the unique identifier of the event; caseID – the unique identifier
of the business process instance; timeStamp – the timestamp of the event occurrence;
eval – the value of KPI i .</p>
      <p>According to the event log structure (1), values  KPI i , KPIType j  could be
defined using event log processing by the following formula:
 KPIi , KPITypej  </p>
      <p>count KPITypej 
maxcount KPITypel 
l1, p
,
where count KPIType j  – the number of records in event log, where KPI i type is
KPIType j ; p – the number of types KPITypel related to KPI i in event log.</p>
      <p>Thereby, degrees of membership  KPI i , KPIType j  and, hence, the dashboard’s
design may change in time, depending on the current content of the event log.</p>
      <p>The relation between KPIs and visualization tools is defined by the following
maxmin composition of fuzzy relations “type is” and “displayed by”:
 KPIi ,VisToolk   max min  KPIi , KPITypej , KPITypej ,VisToolk ,
j1,m
(3)
where m – the number of nodes, which represent KPI types.</p>
      <p>Thus, to define the set of visualization tools, used to build the dashboard, the
following optimization problem should be solved:
n q
   KPIi ,VisToolk  xik  max,
i1 k1
q
 xik  1, i 1, n,
k 1
n q
  sk  xik  1,
i1 k 1
xik  0,1, i 1, n, k 1, q,
where s k – the preferable part of the dashboard’s space, where the visualization
tool VisTool k should be placed, s k  0,1; xik – the binary value, that demonstrates
whether the visualization tool VisTool k is selected to represent the KPI i .
(1)
(2)
(4)</p>
      <p>The workflow scheme of forming dashboard for business process KPIs analysis
using proposed approach is shown in figure 2 in the form of BPMN diagram. Besides
development of the tool, which implements the proposed approach, and integration
with the BPM system and BI dashboards tool, the structure of BPM system’s event
log should be customized according to the proposed event structure (1).
0,38
0,20
1,00
0,22
0,75
1,00
0,86
0,22
1,00
0,60
0,43
0,78</p>
      <p>
        This section outlines the example of application of the proposed approach. The
example values  KPIType j ,VisTool k  , obtained with accordance to the best practice [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ],
 KPIType j ,VisTool k 
Quantitative
Directional
Category
Actionable
0,38
0,20
0,57
1,00
      </p>
      <p>
        Let’s assume that we’ve already processed the event log and obtained values (see
table 2)  KPI i , KPIType j  for some KPIs of the product supply business process,
according to the Supply-Chain Operations Reference (SCOR) model [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
 KPI i , KPIType j 
Orders Supplied in Full (OSF%)
Cost to Supply (CS)
Supply Cycle Time (SCT)
0,42
1,00
0,67
      </p>
      <sec id="sec-3-1">
        <title>Quantitative</title>
        <p>Now, using the formula (3), we can easily define the values  KPI i ,VisTool k  ,
outlined in table 3, and solve the optimization problem (4).
 KPI i ,VisTool k 
OSF%
CS
SCT</p>
      </sec>
      <sec id="sec-3-2">
        <title>Gauge</title>
        <p>As a result, the following recommendations for the dashboard’s design have been
obtained:
 Use the gauge to represent OSF% (takes about 15% of the dashboard space);
 Use the bar chart to represent CS (takes about 25% of the dashboard space);
 Use the line chart to represent SCT (takes about 60% of the dashboard space).</p>
        <p>The possible dashboard design, which is corresponding to the obtained results, is
shown in figure 3.
In this paper, we’ve presented the approach to forming dashboards for business
process KPIs analysis. This approach considers the impact of relations between analyzed
KPIs, KPI types, and various visualization tools on the dashboard’s design. It’s based
on application of fuzzy semantic network in order to describe and analyze relations
between KPIs, KPI types, and various visualization tools. To obtain recommendations
for the dashboard’s design, we’ve proposed the optimization problem (4), which
solution depends on the relations between the fuzzy semantic network’s concepts.</p>
        <p>Implementation of the proposed approach requires integration with the BPM
system, customization and processing (2) of the BPM system’s event log according to the
proposed event structure (1). It’s also required to elaborate the approach to provide
integration and interoperability with various BI Dashboard tools.</p>
        <p>Future study includes additional considerations on the dashboard’s design, which
may change in time and its history of changes should be traceable and accessible for
the further analysis, selection of the BPM system and BI dashboards tool to be
customized and integrated, implementation and application of the proposed approach,
obtained results analysis and discussion.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Business process management: concepts, languages, architectures</article-title>
          . Springer Publishing Company, Incorporated (
          <year>2010</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          -28616-2
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Wetzstein</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leitner</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosenberg</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brandic</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dustdar</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leymann</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Monitoring and analyzing influential factors of business process performance</article-title>
          .
          <source>Enterprise Distributed Object Computing Conference</source>
          ,
          <year>2009</year>
          , pp.
          <fpage>141</fpage>
          -
          <lpage>150</lpage>
          . IEEE International. IEEE (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Eckerson</surname>
          </string-name>
          , W. W.:
          <article-title>Performance dashboards: measuring, monitoring, and managing your business</article-title>
          . John Wiley &amp; Sons (
          <year>2010</year>
          ).
          <source>doi: 10.1002/9781119199984</source>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Pappas</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whitman</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Riding the technology wave: Effective dashboard data visualization. Human Interface and the Management of Information</article-title>
          .
          <source>Interacting with Information</source>
          , pp.
          <fpage>249</fpage>
          -
          <lpage>258</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Kopp</surname>
            ,
            <given-names>A. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orlovskyi</surname>
            ,
            <given-names>D. L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuka</surname>
            ,
            <given-names>D. O.:</given-names>
          </string-name>
          <article-title>An approach to forming dashboards for business processes state analysis</article-title>
          .
          <source>Bulletin of NTU "KhPI"</source>
          . Series:
          <article-title>System analysis</article-title>
          ,
          <source>control and information technology</source>
          , vol.
          <volume>51</volume>
          , pp.
          <fpage>44</fpage>
          -
          <lpage>52</lpage>
          . NTU “KhPI”,
          <string-name>
            <surname>Kharkiv</surname>
          </string-name>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Few</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Information dashboard design.</article-title>
          <string-name>
            <surname>O'Reilly Media</surname>
          </string-name>
          (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Eckerson</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hammond</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Visual Reporting and Analysis: Seeing Is Knowing: Asset Page. TDWI - The Data Warehousing Institute (</article-title>
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Vera-Baquero</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Colomo-Palacios</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Molloy</surname>
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Real-time business activity monitoring and analysis of process performance on big-data domains</article-title>
          .
          <source>Telematics and Informatics</source>
          , vol.
          <volume>33</volume>
          , no.
          <issue>3</issue>
          , pp.
          <fpage>793</fpage>
          -
          <lpage>807</lpage>
          . (
          <year>2016</year>
          ). doi:
          <volume>10</volume>
          .1016/j.tele.
          <year>2015</year>
          .
          <volume>12</volume>
          .005
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Management</given-names>
            <surname>Reports</surname>
          </string-name>
          &amp;
          <article-title>Dashboard Best Practice</article-title>
          . https://www.targetdashboard.com/site/ kpi-dashboard
          <article-title>-best-practice</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Dash</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Subudhi</surname>
            ,
            <given-names>B</given-names>
          </string-name>
          . (eds.):
          <source>Handbook of Research on Computational Intelligence Applications in Bioinformatics. IGI Global</source>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Weidlich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ziekow</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Günther</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Desai</surname>
          </string-name>
          , N.:
          <article-title>Event-based monitoring of process execution violations</article-title>
          .
          <source>BPM</source>
          , vol.
          <volume>11</volume>
          , pp.
          <fpage>182</fpage>
          -
          <lpage>198</lpage>
          . (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>