<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">A Tool for Assisted Business Process Redesign</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Tobias</forename><surname>Fehrer</surname></persName>
							<email>tobias.fehrer@fim-rc.de</email>
							<affiliation key="aff0">
								<orgName type="department">Research Center Finance &amp; Information Management</orgName>
								<orgName type="institution">University of Bayreuth</orgName>
								<address>
									<settlement>Bayreuth</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">Branch Business &amp; Information Systems Engineering</orgName>
								<orgName type="institution">Fraunhofer FIT</orgName>
								<address>
									<settlement>Bayreuth</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Dominik</forename><forename type="middle">A</forename><surname>Fischer</surname></persName>
							<email>dominik.fischer@fim-rc.de</email>
							<affiliation key="aff0">
								<orgName type="department">Research Center Finance &amp; Information Management</orgName>
								<orgName type="institution">University of Bayreuth</orgName>
								<address>
									<settlement>Bayreuth</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">Branch Business &amp; Information Systems Engineering</orgName>
								<orgName type="institution">Fraunhofer FIT</orgName>
								<address>
									<settlement>Bayreuth</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sander</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
							<email>s.leemans@bpm.rwth-aachen.de</email>
							<affiliation key="aff2">
								<orgName type="institution">RWTH University</orgName>
								<address>
									<settlement>Aachen</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Maximilian</forename><surname>Röglinger</surname></persName>
							<email>maximilian.roeglinger@fim-rc.de</email>
							<affiliation key="aff0">
								<orgName type="department">Research Center Finance &amp; Information Management</orgName>
								<orgName type="institution">University of Bayreuth</orgName>
								<address>
									<settlement>Bayreuth</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">Branch Business &amp; Information Systems Engineering</orgName>
								<orgName type="institution">Fraunhofer FIT</orgName>
								<address>
									<settlement>Bayreuth</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Moe</forename><forename type="middle">T</forename><surname>Wynn</surname></persName>
							<email>m.wynn@qut.edu.au</email>
							<affiliation key="aff3">
								<orgName type="institution">Queensland University of Technology</orgName>
								<address>
									<settlement>Brisbane</settlement>
									<country key="AU">Australia</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">A Tool for Assisted Business Process Redesign</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">D322A1ECB59D8E88675C04043171B225</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T03:59+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Business Process Redesign, User Guidance, Simulation (M. T. Wynn) 0000-0002-8798-5724 (T. Fehrer)</term>
					<term>0000-0002-5218-6463 (D. A. Fischer)</term>
					<term>0000-0002-5201-7125 (S. J.J. Leemans)</term>
					<term>0000-0003-4743-4511 (M. Röglinger)</term>
					<term>0000-0002-7205-8821 (M. T. Wynn)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The continuous optimization of business processes remains a critical success factor for companies. The assisted business process redesign (aBPR) concept guides users in improving business processes based on redesign patterns. Depending on the process data at hand, it generates four types of recommendations that differ in their level of automation. This paper presents a tool implementation of the aBPR concept as a stand-alone desktop application that has been successfully used in several case studies. The aBPR tool uses BPMN diagrams, redesign best practices, and simulation experiments to guide the user to improved process designs in a modeling application.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Transforming business processes at an accelerating pace is essential for companies to meet increasing competition and customer needs <ref type="bibr" target="#b0">[1]</ref>. Business process redesign (BPR) is concerned with improving business processes <ref type="bibr" target="#b1">[2]</ref>. It is considered an essential phase in the business process management (BPM) lifecycle since it entails significant economic value by introducing innovation, reducing costs, as well as improving quality, productivity, and customer experience <ref type="bibr" target="#b2">[3,</ref><ref type="bibr" target="#b3">4]</ref>. Despite its importance, BPR lacks clear guidance and often "happens in a black box" ( <ref type="bibr">[5, p. 217]</ref>). Often, organizations conduct workshops with consultants and stakeholders to analyze process challenges as well as opportunities and manually generate options for process improvements <ref type="bibr" target="#b4">[5]</ref>. Even when supported by data-driven approaches such as process mining, the quality and the effectiveness of BPR depend on the creativity and the expertise of the project team to find valuable solutions, which is both time-consuming and costly. Automation of process redesign could thus hold great potential for long-term organizational success, as it could be more efficient with less dependence on human creativity. Several approaches have already dealt with how partial aspects of process improvement can be automated. However, to the best of our knowledge, there is no holistic approach that provides end-to-end support and integrates the user into the decision-making process where necessary.</p><p>The assisted business process redesign (aBPR) tool was developed as a stand-alone desktop application that guides users in improving process models using an assisted approach and redesign recommendations. Focusing on incremental process improvement, it facilitates the popular method of process redesign patterns and a four-step procedure to generate redesign options: step 1) select suitable redesign patterns, step 2) identify suitable process parts, step 3) create alternative models, and step 4) evaluate the performance of these alternative models. Executing these four steps leads to redesign options that, after thorough evaluation, may be suitable for improving the process under investigation. The presented aBPR tool integrates this four-step procedure. The literature shows that individual steps and combinations of these steps can be (partially) automated, leaving the finalization of the redesign options with the human user <ref type="bibr" target="#b5">[6]</ref>. This is by no means a weakness of related work in this area, but often because the approaches work with assumptions for which data may be missing in the execution. From the possible combinations of automatable and manual steps, four types can be defined with an increasing automation level (AL). The aBPR tool supports this typology so that increasingly specific recommendations for process improvement are proposed to the user, who can adopt them whole or finalize them manually, depending on their type.</p><p>In the remainder of this manuscript, we present the aBPR tool with its innovation and characteristics in Section 2, discuss its maturity by describing the measures and outcomes used to evaluate the tool (in Section 3), and conclude in Section 4.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Innovation and characteristics</head><p>In the aBPR tool, a blank canvas can be used as a starting point to model a process or an existing business process modeling and notation (BPMN) diagram can be imported. The process model is the central starting point for process improvement and can therefore be enriched with far-reaching information that provides a comprehensive picture of the as-is state. The aBPR tool provides support for interactively editing the process model and integrates improvement recommendations for the generation of redesign options. A four-step procedure is repeated until satisfaction with the process is achieved and the improved process model is exported. Because of its good usability, we used the Camunda Modeler<ref type="foot" target="#foot_0">1</ref> , which is widely used in research and practice, as a starting point for tool development. Figure <ref type="figure" target="#fig_0">1</ref> shows the tool's GUI.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Modeling and simulation</head><p>In addition to traditional control flow descriptions and considering events, documents, organizations, and lanes, a custom extension of the BPMN metamodel captures simulation configuration, performance data, and aBPR-specific annotations. This allows information to be stored consistently in the model and imported and exported as a . simubpmn file. When importing a basic BPMN diagram, event arrival rates, resources with their costs and timetables, activity durations, routing probabilities, resource timetables, and further properties are initialized with a default configuration to ensure valid models and a convenient experience for the user. The available element shapes in the process modeler are restricted to a set supported by the redesign handlers. Via static model analysis, the tool identifies modeling errors, detects misconfigurations or missing properties, and provides visual feedback to fix the model. The simulation package Scylla <ref type="bibr" target="#b6">[7]</ref> is embedded in the aBPR tool and facilitates the simulation of the as-is process model and redesign options. The results of the simulation experiments can be compared side by side to estimate the effects.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Redesign recommendations</head><p>After modeling the initial process model and validating its real-world fidelity with initial simulation studies, a redesign performance objective, such as time, cost, flexibility, or quality, is selected. Using the process model and the performance objective as an input, the tool then generates redesign recommendations by invoking recommendation providers that contain the logic to execute (parts of) the four-step procedure for applying redesign patterns. A recommendation provider may return more than one recommendation and several recommendation providers might provide recommendations for the same redesign pattern. In the graphical user interface (GUI), each recommendation is characterized with its corresponding process aspect, the pattern category, a distinct name, a description, and, optionally, the expected impact and affected process elements. How a recommendation can be applied varies per AL. The aBPR tool supports all patterns from Reijers and Mansar <ref type="bibr" target="#b7">[8]</ref> in varying automation levels (AL). The triage and activity automation patterns are implemented on AL3, the parallelism, and extra resources patterns are implemented on AL4, whereas the remaining are implemented as AL1 and AL2 recommendations. In case of full automation (AL4), the aBPR tool generates process models in the background with feasible implemented redesign options, such as parallelized task: The developed heuristic checks whether sequential activities can be parallelized or are interdependent (see Figure <ref type="figure" target="#fig_1">2 b</ref>). The different models are then simulated simultaneously to reveal effects on performance. The result of this simulation is then integrated into the recommendation and shown to the user. In contrast, at the lowest level, only a general recommendation is made that a redesign pattern can help achieve a performance goal. In the intermediate levels (AL2&amp;3), user input is requested in addition to the automated checks to determine, for example, the applicability of the triage pattern (see Figure <ref type="figure" target="#fig_1">2 a</ref>): After selecting activities that are potentially suitable for triage, the user models the new process manually or is guided by a wizard.</p><p>To diversify good recommendations in terms of their estimated impact and place them on top of the list of recommendations a 𝐴* heuristic is implemented. Users can accept or reject recommendations and evaluate their impact via simulation experiments and own judgment.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Tool maturity &amp; evaluation</head><p>The stand-alone aBPR tool can be downloaded <ref type="foot" target="#foot_1">2</ref> for Windows PCs and tried, e.g., with a sample process provided in a tutorial <ref type="foot" target="#foot_2">3</ref> . The aBPR tool is the result of a design science research (DSR) project <ref type="bibr" target="#b5">[6]</ref> and has been evaluated in terms of operationality, feasibility, and applicability in artificial and naturalistic settings. During the development phase, the tool was interactively demonstrated in eight expert interviews to evaluate the aBPR's feasibility and operationality, based on an artificial service request process that is also demonstrated in a screencast of the tool's functionality <ref type="foot" target="#foot_3">4</ref> . In a second evaluation, we conducted two case studies with professionals engaged in real-world BPR projects in an artificial setting. In the first case, we involved three consultants from a process consulting firm. For the second case, we involved a consultant and a process owner. In a real-world case study with Germany-based industrial automation solutions provider KUKA, the aBPR tool was tested in a workshop where the prototype was utilized to develop process improvement ideas that reduce cycle time by 30 %. Further details on the case studies and the evaluation of the aBPR tool can be found in Fehrer et al. <ref type="bibr" target="#b5">[6]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Conclusion</head><p>In this paper, we introduced the aBPR tool that supports practitioners in improving business processes by guiding them to creating process redesign options and simulating the impact of process changes. The tool is available for download and can be extended with additional redesign heuristics. In future research, we plan to enhance the tool by (a) implementing further redesign heuristics in advanced levels of automation, (b) improving the guidance through the act of process redesign, and (c) integrating additional sources for developing an understanding of the as-is business process, such as event logs.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: General tool overview with the major GUI components (1) the diagram editor and lint tab, (2) the performance objective selection, and (3) the list of recommendations.</figDesc><graphic coords="3,89.29,84.19,416.70,223.56" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Implementation of two redesign patterns</figDesc><graphic coords="4,89.29,84.19,416.69,104.26" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://github.com/camunda/camunda-modeler</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">download: https://dtdi.github.io/assisted-bpr-modeler/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">tutorial: https://github.com/dtdi/assisted-bpr-modeler/blob/gh-pages/aBPR%20Tutorial.pdf</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">screencast: https://www.youtube.com/watch?v=HwXtz2mDHLw</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Seven paradoxes of business process management in a hyper-connected world</title>
		<author>
			<persName><forename type="first">D</forename><surname>Beverungen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">C</forename><surname>Buijs</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Becker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Di Ciccio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">M P</forename><surname>Van Der Aalst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Bartelheimer</surname></persName>
		</author>
		<idno type="DOI">10.1007/s12599-020-00646-z</idno>
	</analytic>
	<monogr>
		<title level="j">Business &amp; Information Systems Engineering</title>
		<imprint>
			<biblScope unit="volume">63</biblScope>
			<biblScope unit="page" from="145" to="156" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A critical evaluation and framework of business process improvement methods</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">J B</forename><surname>Vanwersch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Shahzad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Vanderfeesten</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Vanhaecht</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Grefen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Pintelon</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mendling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">G</forename><surname>Van Merode</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">A</forename><surname>Reijers</surname></persName>
		</author>
		<idno type="DOI">10.1007/s12599-015-0417-x</idno>
	</analytic>
	<monogr>
		<title level="j">Business &amp; Information Systems Engineering</title>
		<imprint>
			<biblScope unit="volume">58</biblScope>
			<biblScope unit="page" from="43" to="53" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">The Business Process Design Space for exploring process redesign alternatives</title>
		<author>
			<persName><forename type="first">S</forename><surname>Gross</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Stelzl</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Grisold</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mendling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Röglinger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Brocke</surname></persName>
		</author>
		<idno type="DOI">10.1108/BPMJ-03-2020-0116</idno>
	</analytic>
	<monogr>
		<title level="j">Business Process Management Journal</title>
		<imprint>
			<biblScope unit="volume">27</biblScope>
			<biblScope unit="page" from="25" to="56" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Dumas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rosa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mendling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">A</forename><surname>Reijers</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-662-56509-4</idno>
		<title level="m">Fundamentals of Business Process Management</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
	<note>2 ed</note>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">A structured evaluation of business process improvement approaches</title>
		<author>
			<persName><forename type="first">G</forename><surname>Zellner</surname></persName>
		</author>
		<idno type="DOI">10.1108/14637151111122329</idno>
	</analytic>
	<monogr>
		<title level="j">Business Process Management Journal</title>
		<imprint>
			<biblScope unit="volume">17</biblScope>
			<biblScope unit="page" from="203" to="237" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">An assisted approach to business process redesign</title>
		<author>
			<persName><forename type="first">T</forename><surname>Fehrer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">A</forename><surname>Fischer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J</forename><surname>Leemans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Röglinger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">T</forename><surname>Wynn</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.dss.2022.113749</idno>
	</analytic>
	<monogr>
		<title level="j">Decision Support Systems</title>
		<imprint>
			<biblScope unit="volume">156</biblScope>
			<biblScope unit="page">113749</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Design of an extensible bpmn process simulator</title>
		<author>
			<persName><forename type="first">L</forename><surname>Pufahl</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">Y</forename><surname>Wong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Weske</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-319-74030-0_62</idno>
	</analytic>
	<monogr>
		<title level="m">Business Process Management Workshops</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page" from="782" to="795" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics</title>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">A</forename><surname>Reijers</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">Limam</forename><surname>Mansar</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.omega.2004.04.012</idno>
	</analytic>
	<monogr>
		<title level="j">Omega</title>
		<imprint>
			<biblScope unit="volume">33</biblScope>
			<biblScope unit="page" from="283" to="306" />
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
