<!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>Automated Process (Re-)Design</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Maximilian Roglinger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christopher van Dun</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dominik A. Fis</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>ng Kr</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>FIM Research Center, Universities of Augsburg and Bayreuth</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Project Group Business &amp; Information Systems Engineering of the Fraunhofer FIT</institution>
          ,
          <addr-line>Bayreuth</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Research Problem Problem Description Along the BPM lifecycle, many data-driven methods have recently emerged. Enabled by the increasing volume of data, process mining techniques have been developed to identify and discover process models based on process logs [2]. Predictive and prescriptive process monitoring techniques nowadays allow for</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Business process management (BPM) continuously attracts academia and
practice, as it is known to drive organizational performance [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Especially process
(re-)design entails signi cant economic value by introducing innovation, reducing
costs, as well as improving quality, productivity, and customer experience [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ].
Thus, it is considered an essential phase in the BPM lifecycle [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>
        Today, organizations must overthink their business processes at an
increasingly fast pace, consider continuously rising customer needs, create novel
processbased value propositions, and engage in innovation to stay successful [
        <xref ref-type="bibr" rid="ref13 ref15 ref7">7, 13, 15</xref>
        ].
Technological developments are rapidly gaining momentum, processes are at
drift, and ever more players enter the global market, resulting in the
organizational environment becoming more volatile, uncertain, complex, and ambiguous
(VUCA) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Even though this poses pressure on organizations, it also o ers a
wide range of opportunities.
      </p>
      <p>
        While automation is prevalent in other BPM lifecycle phases (e.g., in process
execution) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], process (re-)design commonly requires manual activities such as
traditional creativity techniques [
        <xref ref-type="bibr" rid="ref15 ref22">15, 22</xref>
        ], making it time-consuming and
laborintensive. Thus, automated process (re-)design holds high yet unexploited
potential for long-term corporate success since it could accelerate process (re-) design
and make it more e cient as well as less dependent on human creativity.
2.1
under
      </p>
      <p>Automated</p>
      <p>process
(re-)design</p>
      <p>Manual
process
(re-)design</p>
      <p>Automated Improvement
Incrementally improve an existing
process automatically</p>
      <p>Automated Innovation
Radically create a new process</p>
      <p>automatically</p>
      <p>Manual Improvement
Incrementally improve an existing
process manually</p>
      <p>Manual Innovation
Radically create a new process</p>
      <p>manually</p>
      <p>Incremental
process improvement</p>
      <p>
        Radical
process innovation
acquiring real-time insights into future behavior and results of running process
instances and provide recommendations for optimizing process control [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ].
      </p>
      <p>
        Driven by the recent \hyperautomation" trend [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] and the widespread
adoption of process-aware information systems, organizations increasingly aspire to
leverage automation potential in the context of process operations [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Whereas
process mining and monitoring primarily focus on (partially) automated process
control, robotic process automation (RPA) has become the new \technological
star" for the lightweight automation of process execution [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. Although some
research obstacles still need to be overcome, ever more organizations adopt RPA
to reduce manual e orts when performing speci c tasks in processes [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ].
      </p>
      <p>Despite all these automation e orts, it is remarkable that the BPM lifecycle
phase process (re-)design remains a manual task with a high level of cognitive
e ort. To illustrate the level of automation in the context of process (re-)design,
we propose a 2x2 matrix along two continua (Table 1). The rst continuum
concerns the degree of automation (manual to automated process (re-)design), the
second concerns the scope of process (re-)design (incremental process
improvement to radical process innovation). In the following, we describe the state-of-art
of process (re-)design within the introduced quadrants.</p>
      <p>
        With a lens on incremental process improvement, various collections of
process redesign patterns and methods have been developed [
        <xref ref-type="bibr" rid="ref12 ref8">8,12</xref>
        ]. These collections
reduce the cognitive e ort and guide process stakeholders in process
improvement. However, they neither replace manual e ort nor do they leverage the
potential of tools in the redesign process. Initial approaches for semi-automated
process improvement have been developed (see [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]). Yet, these methods are at
the lower end of automation, as they generally guide improving processes in a
user-interactive way. Thus, there is still great potential to increase the level of
automation. Research is already striving to further automate process
improvement, enabling automatic exploration of bene cial process changes [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        Focusing on radical process innovation, e orts also have been made to
develop guidance for creating new processes with new value propositions [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. For
instance, Grisold et al. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] created the \Five Diamond" method, which aims
to guide organizations in identifying opportunities from business and
technology trends and integrating them into processes with novel value propositions.
Nonetheless, equivalent to manual improvement, the introduced method does
not support replacing manual e orts with automation. While automating
process improvement seems easier to realize, the automation of process innovation
proves to be an unsolvable problem to date. There is certainly still huge potential
in the area of automated innovation that has barely been exploited.
      </p>
      <p>Overall, we conclude that process (re-)design is still predominantly a manual
task. The automation of process (re-)design, especially with a focus on process
innovation, undoubtedly remains a major hurdle to overcome.
2.2</p>
      <p>Challenges to Overcome
Several characteristics of business processes and the complexity of the process
(re-)design task itself make the BPM lifecycle phase of process (re-)design stand
out and, therefore, prevent or at least complicate its automation. Such
characteristics are described here in broad strokes:</p>
      <p>Process (re-)design requires creativity. Process (re-)design often requires
breaking with existing structures and routines within the process to create
something new. Falling back on existing concepts might be a good idea for
evolutionary process improvements. Still, radical (re-)design relies on going beyond
what has already been there and exploring the whole solution space of (possibly
unknown) process (re-)design opportunities. In contrast to data-based
improvement, such explorative and innovative e orts mostly rely on \creativity", i.e., the
use of imagination or original ideas to create something new. Creativity is often
described as an inherently human capability. Therefore, automating (re-)design
e orts requires advances in computational creativity.</p>
      <p>
        Processes are multi-dimensional. (Re-)designing processes is not as
straightforward as simply rearranging the sequence of activities within the investigated
process. Business processes are commonly conceptualized using ve
fundamental perspectives [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. Besides the above-mentioned control- ow or behavioral
perspective, these perspectives relate to the functional elements of a process
(functional perspective), the assignment of tasks to human participants
(organizational view), the implementation of atomic activities (operational perspective),
and the information entities handled during individual tasks (informational
perspective). All perspectives have to be considered in automated (re-)design e orts.
      </p>
      <p>
        Processes are executed in context. Business processes are often part of an
organization's process landscape and, therefore, situated within a complex
network of dependencies such as restricted resources, logical relationships [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], and
domain-speci c characteristics [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. This makes it very hard to consider process
(re-)design as a clearly delimited activity and, thus, complicates automation.
      </p>
      <p>
        Processes are socio-technical. Processes are sets of activities in which humans
and technology co-create value [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Automated approaches in every phase of the
BPM lifecycle are constricted by what data is available on these activities.
Process mining can, e.g., only discover processes when their activities have left traces
in the involved information systems or have otherwise been recorded [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] and
when these traces are of high quality [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In return, this data represents only the
technical perspective on the process. Process and domain knowledge of human
agents participating in or being responsible for the process is essential in guiding
any (re-)design e ort, making full automation impractical, if not unfeasible.
      </p>
      <p>
        Processes are at drift. All organizational concepts are subject to unintentional
change, i.e., the deviation from their planned purpose over time. In a VUCA
world, processes are no exception, constantly su ering from gradual and
incremental changes over time called process or concept drift [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] or being radically
changed by disruptive shocks [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. This impacts automated process (re-)design
activities twofold: First, due to such drift, processes are dynamic, constantly
changing, and event-driven artifacts that are di cult to fully capture, de ne, and
reinvent using high-level process models. Second, in a dynamic and changing
environment, attempting to (re-)design business processes is \subject to resistance,
deals, side e ects, and the properties of the IT landscape" [6, p. 193].
3
      </p>
    </sec>
    <sec id="sec-2">
      <title>Directions Towards a Solution</title>
      <p>
        Initial ideas towards a solution may involve approaches that leverage advances
in computational creativity, e.g., evolutionary computation [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] or generative
machine learning [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Further, to accelerate process (re-)design, organizations could
automatically incorporate feedback into design suggestions to shorten reaction
cycles, e.g., via arti cial intelligence-enabled process improvement tools and
complex predictive models that capture trends from data.
      </p>
      <p>
        These initial ideas are beset with challenges themselves. For example, relying
on historical data could lead to new processes already being outdated at the time
of implementation. This demonstrates the need to address ancillary issues such
as real-time data deployment [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. A fully automated work ow environment would
also be necessary to implement new process designs without delay. Additionally,
arti cial intelligence often works as a black box and lacks explainability.
      </p>
      <p>In conclusion, automated process (re-)design remains a relevant research gap
that should be explored further. However, even if fully automated process
(re)design became feasible, new challenges would arise since organizations could
then easily develop new processes. The focus of competition could move from
talent to access to data or to the best forecasting models estimating the impact
of changes on the future or identifying the next relevant time for re-evaluation.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          :
          <article-title>Business process management: A comprehensive survey</article-title>
          .
          <source>ISRN Softw Eng</source>
          <year>2013</year>
          ,
          <volume>1</volume>
          {
          <fpage>37</fpage>
          (
          <year>2013</year>
          ). https://doi.org/10.1155/
          <year>2013</year>
          /507984
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          : Process mining: Data Science in Action. Springer, Berlin, Heidelberg (
          <year>2016</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>662</fpage>
          -49851-4
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. A erbach, P.,
          <string-name>
            <surname>Hohendorf</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manderscheid</surname>
          </string-name>
          , J.:
          <article-title>Design it like darwin - a value-based application of evolutionary algorithms for proper and unambiguous business process redesign</article-title>
          .
          <source>Inf Syst Front</source>
          <volume>19</volume>
          (
          <issue>5</issue>
          ),
          <volume>1101</volume>
          {
          <fpage>1121</fpage>
          (
          <year>2017</year>
          ). https://doi.org/10.1007/s10796-016-9715-1
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Andrews</surname>
            , R., van Dun,
            <given-names>C.G.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wynn</surname>
            ,
            <given-names>M.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kratsch</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          , Roglinger, M.K.E.,
          <string-name>
            <surname>ter Hofstede</surname>
            ,
            <given-names>A.H.M.</given-names>
          </string-name>
          :
          <article-title>Quality-informed semi-automated event log generation for process mining</article-title>
          .
          <source>Decis Support Syst</source>
          <volume>132</volume>
          (
          <year>2020</year>
          ). https://doi.org/10.1016/j.dss.
          <year>2020</year>
          .113265
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Bennett</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lemoine</surname>
            ,
            <given-names>G.J.</given-names>
          </string-name>
          :
          <article-title>What a di erence a word makes: Understanding threats to performance in a vuca world</article-title>
          .
          <source>Bus Horiz</source>
          <volume>57</volume>
          (
          <issue>3</issue>
          ),
          <volume>311</volume>
          {
          <fpage>317</fpage>
          (
          <year>2014</year>
          ). https://doi.org/10.1016/j.bushor.
          <year>2014</year>
          .
          <volume>01</volume>
          .001
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Beverungen</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Exploring the interplay of the design and emergence of business processes as organizational routines</article-title>
          .
          <source>Bus Inf Syst Eng</source>
          <volume>6</volume>
          (
          <issue>4</issue>
          ),
          <volume>191</volume>
          {
          <fpage>202</fpage>
          (
          <year>2014</year>
          ). https://doi.org/10.1007/s12599-014-0335-3
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Beverungen</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buijs</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Di</given-names>
            <surname>Ciccio</surname>
          </string-name>
          , C.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bartelheimer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          , et al.:
          <article-title>Seven paradoxes of business process management in a hyper-connected world</article-title>
          .
          <source>Bus Inf Syst Eng</source>
          <volume>63</volume>
          (
          <issue>2</issue>
          ),
          <volume>145</volume>
          {
          <fpage>156</fpage>
          (
          <year>2021</year>
          ). https://doi.org/10.1007/s12599-020-00646-z
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. vom Brocke, J.,
          <string-name>
            <surname>Baier</surname>
            ,
            <given-names>M.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmiedel</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stelzl</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , Roglinger,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Wehking</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          :
          <article-title>Context-aware business process management: Method assessment and selection</article-title>
          .
          <source>Bus Inf Syst Eng</source>
          (
          <year>2021</year>
          ). https://doi.org/10.1007/s12599-021-00685-0
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Process mining in 2021 and beyond (</article-title>
          <year>2020</year>
          ), https://www.linkedin. com/pulse/process-mining
          <article-title>-2021-beyond-marlon-dumas</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Reijers</surname>
          </string-name>
          ,
          <string-name>
            <surname>H.A.</surname>
          </string-name>
          :
          <source>Fundamentals of Business Process Management</source>
          . Springer (
          <year>2018</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>662</fpage>
          -56509-4
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Elgammal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elhoseiny</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mazzone</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>CAN: Creative adversarial networks, generating art by learning about styles and deviating from style norms</article-title>
          .
          <source>arXiv:1706.07068v1 [cs.AI]</source>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Fellmann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koschmider</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laue</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schoknecht</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vetter</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Business process model patterns: state-of-the-art, research classi cation and taxonomy</article-title>
          .
          <source>Bus Process Manag J</source>
          <volume>25</volume>
          (
          <issue>5</issue>
          ),
          <volume>972</volume>
          {
          <fpage>994</fpage>
          (
          <year>2019</year>
          ). https://doi.org/10.1108/BPMJ-01-2018- 0021
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Grisold</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gross</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , Roglinger,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Stelzl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>vom Brocke</surname>
          </string-name>
          , J.:
          <article-title>Exploring explorative bpm - setting the ground for future research</article-title>
          .
          <source>In: Business Process Management</source>
          , pp.
          <volume>23</volume>
          {
          <fpage>31</fpage>
          . Springer, Cham (
          <year>2019</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>030</fpage>
          - 26619-6 4
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Grisold</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gro</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stelzl</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>vom Brocke</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , Roglinger,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Rosemann</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.:</surname>
          </string-name>
          <article-title>The ve diamond method for explorative business process management</article-title>
          .
          <source>Bus Inf Syst Eng</source>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Gross</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stelzl</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grisold</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , Roglinger, M.,
          <string-name>
            <surname>vom Brocke</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The business process design space for exploring process redesign alternatives</article-title>
          .
          <source>Bus Process Manag J</source>
          (
          <year>2021</year>
          ). https://doi.org/10.1108/BPMJ-03-2020-0116
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Kratsch</surname>
            , W., Konig,
            <given-names>F.</given-names>
          </string-name>
          , Roglinger, M.:
          <article-title>Shedding light on blind spots: Developing a reference architecture to leverage video data for process mining</article-title>
          . arXiv:
          <year>2010</year>
          .
          <article-title>11289 [cs</article-title>
          .CV] (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Kratsch</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manderscheid</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , Rei ner, D., Roglinger,
          <string-name>
            <surname>M.</surname>
          </string-name>
          :
          <article-title>Data-driven process prioritization in process networks</article-title>
          .
          <source>Decis Support Syst</source>
          <volume>100</volume>
          ,
          <volume>27</volume>
          {
          <fpage>40</fpage>
          (
          <year>2017</year>
          ). https://doi.org/10.1016/j.dss.
          <year>2017</year>
          .
          <volume>02</volume>
          .011
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pentland</surname>
            ,
            <given-names>B.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Recker</surname>
          </string-name>
          , J.:
          <article-title>Building a complementary agenda for business process management and digital innovation</article-title>
          .
          <source>Eur J Inf Syst</source>
          <volume>29</volume>
          (
          <issue>3</issue>
          ),
          <volume>208</volume>
          {
          <fpage>219</fpage>
          (
          <year>2020</year>
          ). https://doi.org/10.1080/0960085X.
          <year>2020</year>
          .1755207
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Panetta</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Gartner top strategic technology trends for 2021 (</article-title>
          <year>2020</year>
          ), https://www.gartner.com/smarterwithgartner/ gartner-top
          <article-title>-strategic-technology-trends-for-2021/</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          :
          <article-title>Business process management: The evolution of a discipline</article-title>
          .
          <source>Comput Ind</source>
          <volume>126</volume>
          (
          <year>2021</year>
          ). https://doi.org/10.1016/j.compind.
          <year>2021</year>
          .103404
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Teinemaa</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Maggi</surname>
          </string-name>
          ,
          <string-name>
            <surname>F.M.</surname>
          </string-name>
          :
          <article-title>Outcome-oriented predictive process monitoring: Review and benchmark</article-title>
          .
          <source>ACM Trans Knowl Discov Data</source>
          <volume>13</volume>
          (
          <issue>2</issue>
          ),
          <volume>1</volume>
          {
          <fpage>57</fpage>
          (
          <year>2019</year>
          ). https://doi.org/10.1145/3301300
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Vanwersch</surname>
            ,
            <given-names>R.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vanderfeesten</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rietzschel</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          :
          <article-title>Improving business processes</article-title>
          .
          <source>In: Business Process Management</source>
          . pp.
          <volume>3</volume>
          {
          <fpage>18</fpage>
          . Springer, Cham (
          <year>2016</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          -23063-4 1
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Zeising</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Schonig,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Jablonski</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          :
          <article-title>Towards a common platform for the support of routine and agile business processes</article-title>
          .
          <source>In: 10th IEEE International Conference on Collaborative Computing</source>
          (
          <year>2014</year>
          ). https://doi.org/10.4108/icst.collaboratecom.
          <year>2014</year>
          .257269
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>