Workflow automation was first applied for structured processes, for processes which were determined at design time. Decades later case management emerged, workflows which were determined at runtime. Decisions in case management are made by human actors. Case management processing is very labor intensive. How could case management be transferred to a Straight-through processing type workflow which reduces involvement of human actors? This paper focuses on merger of case management with real time analytics which helps to replace human decision makers in the case management process with automated real time decision making while preserving non-deterministic nature of the workflow. Merger of case management with real time big data analytics could be next step in the evolution of the case management. Reference architecture for case management and real time analytics merger is defined. Also a case study is presented which implements defined reference architecture.

SOA has been seen as one of the main approaches for managing "system of systems" (SoS) i.e. Large scale IT landscapes. The extension of SOA to include the concept of process orientation could be the next evolutionary step for SOA. Before starting to define reference architectures for process-oriented SOA in SoS it would be advantageous to learn more about the current state of process handling in a SoS. The objective of the current paper is to describe the different approaches to implementing processes in a SoS. The term processing chain is introduced as an abstract representation of processes in SoS. A classification of processing chains is defined and an approximate distribution of different "processing chains" is presented in a case study based on the analyzed SoS. Also, the paper addresses the question which processing chain type would be appropriate in a certain context based on the underlying requirements.

Automation of workflows has been the focus of much research for more than three decades. There has also been significant research about the evolution of workflows. In this paper we describe how to achieve automation of workflows, not only in a single application but in an entire landscape of applications. How can distinctive types of workflow applications be built in an IT landscape? How can the SOA and BPM perspectives be combined in a very large scale system of systems context? We define a platform based approach for the automation of workflows which is in contrast with the classical single application based approach for workflow automation. Furthermore, we describe the core concepts of our workflow execution platform and provide an overview of the results.

Research about process instance migration covers mainly changes in process models during the process evolution and their effects on the same runtime environment. But what if the runtime environment - a legacy Business Process Execution (BPE) platform - had to be replaced with a new solution? Several migration aspects must be taken into account. (1) Process models from the old BPE platform have to be converted to the target process definition language on the target BPE platform. (2) Existing Business Process Management (BPM) applications must be integrated via new BPE platform interfaces. (3) Process instances and process instance data state must be migrated. For each of these points an appropriate migration strategy must be chosen. This paper describes the migration methodology which was applied for the BPE platform renewal in Credit Suisse.