Data for Mobile Distributed Processes in BPM (Extended Abstract)

Abstract

value in businesses. The combination of IoT and BPM enables new possibilities for the utilization of contextual information during the modeling and execution of process models. This paper presents a novel approach to using mobile devices for process execution, opening new avenues for harnessing IoT devices and data to create We address shortcomings in current BPM tool support by providing a method to directly model spatial information into BPMN models, thus coupling mobile interactive interfaces with the dynamic structure of business processes, utilizing inherent location data from said devices.

Keywords

• Abstract)

1. Introduction

Business processes are a series of actions taken to achieve specific business outcomes [ 1 ]. They can be represented by business process models consisting of instructions on how the encompassed activities should be executed. The combination of the Internet of Things (IoT) and Business Process Management (BPM) can lead to new possibilities for value creation [ 2 ], supporting actors during the execution of activities by providing additional information and automating non-value-adding tasks.

Distributed mobile processes involve multiple participants engaged in sequential tasks at various locations, their execution being inherently linked to specific contexts [ 3 ]. Compared to classical IT environments, this brings new challenges to the forefront, and spatial dependency necessitates a greater focus on the process participants and their orchestration.

To address the representation of location-specific concerns in the de-facto standard Business Process Model and Notation (BPMN), we introduced various modeling elements as part of the BPMN extension LABPMN [ 4 ]. These elements include location data objects, support for location events, and the automatic allocation and assignment of one or multiple tasks to a specific actor based on their current location.

This paper presents our tool TRADEmark for utilizing location data in BPM1. Leveraging the BPMN extension for location-awareness, we introduce comprehensive tool support for modeling and executing processes with a strong emphasis on location information. Our tool facilitates process execution, backed by mobile devices used by actors as sources of location data and by providing information about current tasks for execution. Additionally, it incorporates a back-ofice application that provides valuable contextual information about actors, customers, and other process resources. The presented tool serves as an initial approach to dynamically adjusting mobile applications for actors working at diferent locations, solely based on the modeled and executed business process.

The remainder of this introduction is structured as follows: In section 2 we give a short overview of the system architecture and the included parts, followed by a concise description of the diferent parts of the tool in section 3. Finally, section 4 describes a currently running use case, followed by current shortcomings and future implementation tasks.

2. System Overview

The tool at hand adheres to a standard web-based approach and consists of the location-aware modeler, a backend including a database and the Business Process Management System (BPMS), as well as the back-ofice web-application and the mobile application (see fig. 1).

The backend employs a conventional layered MVC (Model-View-Controller) architecture with Spring Boot2 as its technological framework. It provides a REST interface for the mobile application and HTML web pages for human users. These interfaces enable common use cases, such as the storage and querying of tools, locations, or projects, and the handling of user tasks. We employ a SQL database (PostgreSQL3) with an extension for geographic data (PostGIS4) for data storage. To accommodate a wide array of mobile devices (Android and iOS, with the possibility to also deploy as a web application) and enable access to native device features, such as Bluetooth communication or location services, we have selected Flutter5 as the mobile development framework. 3. TRADEmark – Innovations and Features As previously mentioned, TRADEmark currently comprises diferent components primarily focused on the modeling and execution of business processes. In line with the architecture presented earlier, we divide the tool into three main parts: Modeler, Mobile Application and Backend with Web application (see fig. 2). This also shows the approach of moving BPMS functionality like the tasklist and diferent needed forms from static web applications towards dynamic mobile approaches, suiting the actors’ needs. 1A demonstration environment can be accessed via https://pcinf00037.uni-regensburg.de:8443 (User: test, Password: Test!2023). Supplementary information, including a brief demonstration video, is accessible on GitHub at https: //github.com/LeoPoss/demo-trademark. 2https://spring.io/projects/spring-boot 3https://www.postgresql.org/ 4https://postgis.net/ 5https://flutter.dev/ BPMS Process Model Repository

BPMN Extension(s) . . .

Modeler

SpringBoot Camunda Execution

Engine ReactApplication bpmn.js diagram.js

REST

REST LABPMN – Location-aware Process Modeling The first appliance is based on the BPMN extension published in [ 4 ]. The implementation of the modeling aspect of the extension is built upon the open-source implementation bpmn.js6, which integrates well into the BPMS.

The various introduced elements can be selected either directly from the context menu or after assigning a specific location-aware event type or distance type to the element within the properties panel. TRADEmark – Mobile Application for BPM with Location Information To enhance eficiency and efectiveness in process execution, we also ofer a mobile application for actors responsible for carrying out the tasks of the business process. This application includes functionalities such as accessing current tasks (both assigned and unassigned), initiating and completing tasks, accessing attached forms, and working with them. It also supports the initiation of process instances and provides easy access to the actor’s current location via the mobile device’s geolocation services. Additionally, it can connect to other IoT devices, such as reading sensor values or accessing Bluetooth Low Energy (BLE) tags.

Backend and Web Application – Further Leveraging Location Data The backend comprises the BPMS (in this case, Camunda7), a SpringBoot application that integrates and manages all components, and the mandatory database. This component not only provides access to all standard BPMS features but also extends its functionality with location-specific features. This includes displaying customer locations and the current locations of items such as tools on a map. It also supports the incorporation of additional contextual information for existing customers.

4. Maturity

The tool we are introducing is a part of a larger ongoing research project. While it’s still actively in development, the individual components we’ve presented can be used separately or combined to facilitate the utilization of IoT data, primarily location data, in BPM. To support seamless development progress, we adhere to best practices, including the integration of unit tests that are automatically executed in our CI/CD pipeline.

Conversely, to facilitate feedback and the actual use of the tool from our application partners, we place a significant emphasis on UI and UX. This includes providing localization in both English and German, ensuring accessibility and user-friendliness through simplicity. User Study To present the current status of our tool, we provide a real-world example that initially motivated its development. The business process for this demonstration is outlined in ifg. 3 and incorporates the BPMN extension elements for location from [ 4 ]. The process initiates with an incoming order, whereupon a worker is promptly assigned to the task, proceeds to the customer’s location, performs the required work, and subsequently returns. Following the creation of an invoice, the job is marked as completed, thereby concluding the process instance.

An adapted version of this process and our tool are currently undergoing testing at a research partner’s company, evaluating the interaction between the various tool components that support the use of location in diferent phases of the BPM lifecycle.

Future Work As previously mentioned, TRADEmark is an integral part of an ongoing research project, and our development eforts continue. From a technical standpoint, our future tasks encompass several key aspects: (i) Monitoring and DevOps: We recognize the need for robust

Worker's Locations

Location-Aware Sub Process Worker behind Schedule

Inform Customer about Delay Distance < 5km

Inform Customer aboutArrival Approach Customer

Replace

Heating Worker arrived at

Customer

Drive to Depot

Create Invoice Worker arrived at

Depot

Job performed monitoring features for the deployed software, as well as the integration of various DevOps tasks such as CI/CD, (ii) Standardizing BPM Forms: We are actively working on standardizing the BPM forms used for activities or developing the capability to parse standard Camunda forms. This will ensure compatibility for both the web and mobile applications.

Conceptually, we are focused on enhancing contextual information usage. We are actively exploring additional methods to incorporate contextual information into BPM processes. We are also committed to addressing ethical considerations and adhering to regulatory conditions related to the use of actors’ locations.

These eforts reflect our dedication to advancing the capabilities of TRADEmark while also ensuring its alignment with evolving technical and ethical standards.

Acknowledgments

This work is funded by the “Bayrische Forschungsstiftung (BFS)” within the project IoT-basiertes Daten- und Prozessmanagement im Handwerk (TRADEmark).

References

[1] M. Dumas , M. L. Rosa , J. Mendling , et al., Fundamentals of Business Process Management , Springer Berlin Heidelberg, 2018 .

[2] C. Janiesch , A. Koschmider , M. Mecella , et al., The internet of things meets business process management: A manifesto , IEEE Systems, Man, and Cybernetics Magazine 6 ( 2020 ) 34 - 44 .

[3] L. Poss , S. Schönig , A generic approach towards location-aware businessprocess execution , in: H. van der Aa , D. Bork, H. Proper , R. Schmidt (Eds.), Enterprise, Business-Process and Information Systems Modeling , Springer International Publishing, Cham, 2023 , pp. 103 - 118 .

[4] L. Poss , L. Dietz , S. Schönig, LABPMN: Location-aware business process modeling and notation , in: M. Sellami , M.-E. Vidal , B. van Dongen , W. Gaaloul , H. Panetto (Eds.), Proceedings of the International Conference on Cooperative Information Systems (CoopIS) 2023 , 2023 .