Towards Run-time Flexibility for Process Families: Open Issues and Research Challenges

The increasing adoption of process-aware information systems and the high variability of business processes in practice have resulted in process model repositories with large collections of related process variants (i.e., process families). Existing approaches for variability management focus on the modeling and configuration of process variants. However, case studies have shown that run-time configuration and re-confifiguration as well as the evolution of process variants are essential as well. Effectively handling process variants in these lifecycle phases requires deferring certain configuration decisions to the run-time, dynamically re-configuring process variants in response to contextual changes, adapting process variants to emerging needs, and evolving process families over time. In this paper, we characterize these flexibility needs for process families, discuss fundamental challenges to be tackled, and provide an overview of existing proposals made in this context

Approach for the development and application of target process module sets

The implementation of agile frameworks, such as SAFe, in large companies causes conflicts between the overall product development process with a rigid linkage to the calendar cycles and the continuous agile project planning. To resolve these conflicts, adaptive processes can be used to support the creation of realistic target-processes, i.e. project plans, while stabilizing process quality and simplifying process management. This enables the usage of standardisation methods and module sets for design processes. The objective of this contribution is to support project managers to create realistic target-processes through the usage of target-process module sets. These target-process module sets also aim to stabilize process quality and to simplify process management. This contribution provides an approach for the development and application of target-process module sets, in accordance to previously gathered requirements and evaluates the approach within a case study with project managers at AUDI AG (N=21) and an interview study with process authors (N=4) from three different companies

Enabling Process Variants and Versions in Distributed Object-Aware Process Management Systems

Business process variants are common in many enterprises and properly managing them is indispensable. Some process management suites already offer features to tackle the challenges of creating and updating multiple variants of a process. As opposed to the widespread activity-centric process modeling paradigm, however, there is little to no support for process variants in other process support paradigms, such as the recently proposed artifact-centric or object-aware process support paradigm. This paper presents concepts for supporting process variants in the object-aware process management paradigm. We offer insights into the distributed object-aware process management framework PHILharmonicFlows as well as the concepts it provides for implementing variants and versioning support based on log propagation and log replay. Finally, we examine the challenges that arise from the support of process variants and show how we solved these, thereby enabling future research into related fundamental aspects to further raise the maturity level of data-centric process support paradigms

Business Process Model Reuse In A Multi-Channel / Multi-Product Environment–Problem Identification And Tentative Design

Business Process Modeling has become a common activity in organisations. However, as the number of process models increases, so too does the number of duplicated models increase and the level of process model reuse has been found to be surprisingly low. In organisations which operate in an environment with multiple channels, products and customer types, complete process model reuse becomes especially challenging. Without a well-defined approach, such an environment could easily result in dozens of slight variations of what is essentially the same process which will lead to future model and repository management challenges. In response to this problem this paper reviews the literature of complete business process reuse in a multi-channel / multi-product environment. We find that there is a clear gap in the literature in terms of practical solutions that address the problem described but were able to distil five practices that can increase complete model reuse. This review and the practices described will help practitioners grappling with these challenges and paves the way for further needed research on this problem

Business process model customisation using domain-driven controlled variability management and rule generation

Business process models are abstract descriptions and as such should be applicable in different situations. In order for a single process model to be reused, we need support for configuration and customisation. Often, process objects and activities are domain-specific. We use this observation and allow domain models to drive the customisation. Process variability models, known from product line modelling and manufacturing, can control this customisation by taking into account the domain models. While activities and objects have already been studied, we investigate here the constraints that govern a process execution. In order to integrate these constraints into a process model, we use a rule-based constraints language for a workflow and process model. A modelling framework will be presented as a development approach for customised rules through a feature model. Our use case is content processing, represented by an abstract ontology-based domain model in the framework and implemented by a customisation engine. The key contribution is a conceptual definition of a domain-specific rule variability language

Business process model customisation using domain-driven controlled variability management and rule generation

Business process models are abstract descriptions and as such should be applicable in different situations. In order for a single process model to be reused, we need support for configuration and customisation. Often, process objects and activities are domain-specific. We use this observation and allow domain models to drive the customisation. Process variability models, known from product line modelling and manufacturing, can control this customisation by taking into account the domain models. While activities and objects have already been studied, we investigate here the constraints that govern a process execution. In order to integrate these constraints into a process model, we use a rule-based constraints language for a workflow and process model. A modelling framework will be presented as a development approach for customised rules through a feature model. Our use case is content processing, represented by an abstract ontology-based domain model in the framework and implemented by a customisation engine. The key contribution is a conceptual definition of a domain-specific rule variability language

Modelos de características para la gestión de la variabilidad en las perspectivas de los procesos de negocio

[EN] Construir modelos de Procesos de Negocio (PN) implica grandes retos, especialmente cuando los PN varían. Además, éstos pueden verse desde diferentes perspectivas, e.g., la perspectiva de comportamiento (i.e., control de flujo), la organizacional (i.e., distribución de recursos), o la informacional (i.e., flujo de datos). Dependiendo del contexto en el que el PN se lleva a cabo, es posible encontrar variabilidad en cualquiera de estas perspectivas. A pesar de que existen propuestas para modelar la variabilidad en los PN, éstas están muy ligadas al lenguaje de modelado para el que fueron concebidas y, además, se centran principalmente en la perspectiva de comportamiento. Para gestionar la variabilidad en todas las perspectivas de los PN de una manera más flexible, este trabajo presenta una propuesta basada en modelos de características. Estos modelos no sólo mejoran la expresividad de la variabilidad en los PN, sino también el mantenimiento y la comprensión de los modelos de PN resultantes.The authors would like to thank Generalitat Valenciana and MICINN (Spanish Government) for its financial support under projects GV/2009/007 and TEC2010-21520-C04-01.Ayora Esteras, C.; Torres Bosch, MV.; Pelechano Ferragud, V. (2012). Modelos de características para la gestión de la variabilidad en las perspectivas de los procesos de negocio. Novática. (219):36-41. http://hdl.handle.net/10251/38298S364121

Lifecycle Management for Business Process Variants

This chapter deals with advanced concepts for the configuration and management of business process variants. Typically, for a particular business process, different variants exist. Each of them constitutes an adjustment of a master process (e.g., a reference process) to specific requirements building the process context. Contemporary Business Process Management tools do not adequately support the modeling and management of such process variants. Either the variants have to be specified in separate process models or they are expressed in terms of conditional branches within the same process model. Both methods can result in high model redundancies, which make model adaptations a time-consuming and error-prone task. In this chapter, we discuss advanced concepts of our Provop approach, which provides a flexible and powerful solution for managing business process variants along their lifecycle. Such variant support will foster more systematic process configuration as well as process maintenance

A template-based approach for responsibility management in executable business processes

Process-oriented organisations need to manage the different types of responsibilities their employees may have w.r.t. the activities involved in their business processes. Despite several approaches provide support for responsibility modelling, in current Business Process Management Systems (BPMS) the only responsibility considered at runtime is the one related to performing the work required for activity completion. Others like accountability or consultation must be implemented by manually adding activities in the executable process model, which is time-consuming and error-prone. In this paper, we address this limitation by enabling current BPMS to execute processes in which people with different responsibilities interact to complete the activities. We introduce a metamodel based on Responsibility Assignment Matrices (RAM) to model the responsibility assignment for each activity, and a flexible template-based mechanism that automatically transforms such information into BPMN elements, which can be interpreted and executed by a BPMS. Thus, our approach does not enforce any specific behaviour for the different responsibilities but new templates can be modelled to specify the interaction that best suits the activity requirements. Furthermore, libraries of templates can be created and reused in different processes. We provide a reference implementation and build a library of templates for a well-known set of responsibilities

Alamprotsessidest, protsesside variatsioonidest ja nendevahelisest koosmõjust: Integreeritud “jaga ja valitse” meetod äriprotsesside ja nende variatsioonide modelleerimiseks

Igat organisatsiooni võib vaadelda kui süsteemi, mis rakendab äriprotsesse väärtuste loomiseks. Suurtes organisatsioonides on tavapärane esitada äriprotsesse kasutades protsessimudeleid, mida kasutatakse erinevatel eesmärkidel nagu näiteks sisekommunikatsiooniks, koolitusteks, protsesside parendamiseks ja infosüsteemide arendamiseks. Arvestades protsessimudelite multifunktsionaalset olemust tuleb protsessimudeleid koostada selliselt, et see võimaldab nendest arusaamist ning haldamist erinevate osapoolte poolt. Käesolev doktoritöö pakkudes välja integreeritud dekompositsioonist ajendatud meetodi äriprotsesside modelleerimiseks koos nende variatsioonidega. Meetodi kandvaks ideeks on järkjärguline äriprotsessi ja selle variatsioonide dekomponeerimine alamprotsessideks. Igal dekompositsiooni tasemel ning iga alamprotsessi jaoks määratletakse esmalt kas vastavat alamprotsessi tuleks modelleerida konsolideeritud moel (üks alamprotsessi mudel kõikide või osade variatsioonide jaoks) või fragmenteeritud moel (üks alamprotsess ühe variatsiooni jaoks). Sel moel kasutades ülalt-alla lähenemist viilutatakse ja tükeldatakse äriprotsess väiksemateks osadeks. Äriprotsess viilutatakse esmalt tema variatsioonideks ning seejärel tükeldatakse dekompositsioonideks kasutades kaht peamist parameetrit. Esimeseks on äri ajendid variatsioonide jaoks – igal äriprotsessi variatsioonil on oma juurpõhjus, mis pärineb ärist endast ja põhjustab protsesside käivitamisel erisusi. Need juurpõhjused jagatakse viide kategooriasse – ajendid kliendist, tootest, operatiivsetest põhjustest, turust ja ajast. Teine parameeter on erinevuste hulk viisides (tegevuste järjekord, tulemuste väärtused jms) kuidas variatsioonid oma väljundit toodavad. Käesolevas töös esitatud meetod on valideeritud kahes praktilises juhtumiuuringus. Kui esimeses juhtumiuuringus on põhirõhk olemasolevate protsessimudelite konsolideerimisel, siis teises protsessimudelite avastamisel. Sel moel rakendatakse meetodit kahes eri kontekstis kahele üksteisest eristatud juhtumile. Mõlemas juhtumiuuringus tootis meetod protsessimudelite hulgad, milles oli liiasust kuni 50% vähem võrreldes tavapäraste meetoditega jättes samas mudelite keerukuse nendega võrreldes enamvähem samale tasemele.Every organization can be conceived as a system where value is created by means of business processes. In large organizations, it is common for business processes to be represented by means of process models, which are used for a range of purposes such as internal communication, training, process improvement and information systems development. Given their multifunctional character, process models need to be captured in a way that facilitates understanding and maintenance by a variety of stakeholders. This thesis proposes an integrated decomposition-driven method for modeling business processes with variants. The core idea of the method is to incrementally construct a decomposition of a business process and its variants into subprocesses. At each level of the decomposition and for each subprocess, we determine if this subprocess should be modeled in a consolidated manner (one subprocess model for all variants or for multiple variants) or in a fragmented manner (one subprocess model per variant). In this manner, a top-down approach of slicing and dicing a business process is taken. The process model is sliced in accordance with its variants, and then diced (decomposed). This decision is taken based on two parameters. The first is the business drivers for the existence of the variants. All variants of a business process has a root cause i.e. a reason stemming from the business that causes the processes to have differences in how they are executed. The second parameter considered when deciding how to model the variants is the degree of difference in the way the variants produce their outcomes. As such, the modeling of business process variations is dependent on their degree of similarity in regards to how they produce value (such as values, execution order and so on). The method presented in this thesis is validated by two real-life case studies. The first case study concerns a case of consolidation existing process models. The other deals with green-field process discovery. As such, the method is applied in two different contexts (consolidation and discovery) on two different cases that differ from each other. In both cases, the method produced sets of process models that had reduced the duplicity rate by up to 50 % while keeping the degree of complexity of the models relatively stable