The Relational Process Structure

Using data-centric process paradigms, small processes such as artifacts, object lifecycles, or Proclets have become an alternative to large, monolithic models. In these paradigms, a business process arises from the interactions between small processes. However, many-to-many relationships may exist between different process types, requiring careful consideration to ensure that the interactions between processes can be purposefully coordinated. Although several concepts exist for modeling interrelated processes, a concept that considers both many-to-many relationships and cardinality constraints is missing. Furthermore, existing concepts focus on design-time, neglecting the complexity introduced by many-to-many relationships when enacting extensive process structures at run-time. The knowledge which process instances are related to which other process instances is essential. This paper proposes the relational process structure, a concept providing full support for many-to-many-relationships and cardinality constraints at both design- and run-time. The relational process structure represents a cornerstone to the proper coordination of interrelated processes

Towards Object-aware Process Support in Healthcare Information Systems

The processes to be supported by healthcare information systems are highly complex, and they produce and consume a large amount of data. Besides, they require a high degree of flexibility. Despite their widespread adoption in industry, however, traditional process management systems (PrMS) have not been broadly used in healthcare environments so far. One major reason for this is the missing integration of processes with business data; i.e., business objects (e.g., medical orders or reports) are usually outside the control of a PrMS. By contrast, our PHILharmonicFlows framework offers an object-aware process management approach, which tightly integrates business objects and processes. In this paper, we use this framework to support a breast cancer diagnosis scenario. We discuss the lessons learned from this case study as well as requirements from the healthcare domain that can be effectively met by an object-aware process management system

Coordinating Large Distributed Relational Process Structures

Representing a business process as a collaboration of interacting processes has become feasible with the emergence of data-centric business process management paradigms. Usually, these interacting processes have relations and, thereby, form a complex relational process structure. The interactions of processes within this relational process structure need to be coordinated to arrive at a meaningful overall business goal. However, relational process structures may become arbitrarily large. With the use of cloud technology, they may additionally be distributed over multiple nodes, allowing for scalability. Coordination processes have been proposed to coordinate relational process structures, where processes may have one-to-many and many-to-many relations at run-time. This paper shows how multiple coordination processes can be used in a decentralized fashion to more efficiently coordinate large, distributed process structures. The main challenge of using multiple coordination processes is to effectively realize the coordination responsibility of each coordination process. Key components of the solution are the subsidiary principle and the hierarchy of the relational process structure. Finally, an implementation of the coordination process concept based on microservices was developed, which allows for fast and concurrent enactment of multiple, decentralized coordination processes in large, distributed process structures

Object-aware Process Support in Healthcare Information Systems: Requirements, Conceptual Framework and Examples

The business processes to be supported by healthcare information systems are highly complex, producing and consuming a large amount of data. Besides, the execution of these processes requires a high degree of flexibility. Despite their widespread adoption in industry, however, traditional process management systems (PrMS) have not been broadly used in healthcare environments so far. One major reason for this drawback is the missing integration of business processes and business data in existing PrMS; i.e., business objects (e.g., medical orders, medical reports) are usually maintained in specific application systems, and are hence outside the control of the PrMS. As a consequence, most existing PrMS are unable to provide integrated access to business processes and business objects in case of unexpected events, which is crucial in the healthcare domain. In this context, the PHILharmonicFlows framework offers an innovative object-aware process management approach, which tightly integrates business objects, functions, and processes. In this paper, we apply this framework to model and control the processes in the context of a breast cancer diagnosis scenario. First, we present the modeling components of PHILharmonicFlows framework applied to this scenario. Second, we give insights into the operational semantics that governs the process execution in PHILharmonicFlows. Third, we discuss the lessons learned in this case study as well as requirements from the healthcare domain that can be effectively handled when using an object-aware process management system like PHILharmonicFlows. Overall, object-aware process support will allow for a new generation of healthcare information systems treating both data and processes as first class citizens

Automated team selection and compliance checking in business processes

Plenty of activities in many business contexts must be performed collaboratively, e.g., in a hospital or when organising a conference. Tasks such as team composition and allocation are usually performed manually and on the ground of limited criteria such as individual skills, a.o. because adequate automatic support is missing. This paper addresses this shortcoming. We present an approach for team selection and compliance checking in business processes, which includes (i) a language for describing teams; (ii) a way to de- ne team selection conditions and policies related to team composition; and (iii) a mechanism for the automatic resolution of the team selection conditions and for team-related compliance checking based on formal ontologies.Austrian Research Funding Association (FFG) 845638 (SHAPE)Ministerio de Ciencia e Innovación TIN2009-07366 (SETI)Ministerio de Economía y Competitividad TIN2012-32273 (TAPAS)Junta de Andalucía TIC-5906 (THEOS

Object-aware Business Processes: Fundamental Requirements and their Support in Existing Approaches

Despite the increasing maturity of process management technology not all business processes are adequately supported by it. In particular, support for unstructured and knowledge-intensive processes is missing, especially since they cannot be straight-jacketed into predefined activities. A common characteristic of these processes is the role of business objects and data as drivers for process modeling and enactment. This paper elicits fundamental requirements for effectively supporting such object-aware processes; i.e., their modeling, execution and monitoring. Based on these requirements, we evaluate imperative, declarative, and data-driven process support approaches and investigate how well they support object-aware processes. We consider a tight integration of process and data as major step towards further maturation of process management technology