How fit is your organizational culture for business process management?

While business transformations often primarily focus on technological and methodological solutions, there is consensus that having the right organizational culture is critical for the successful change of business processes.

Business process management : an introduction to the special focus issue

The management and improvement of business processes are a core topic of the information systems discipline. The persistent demand in corporations within all industry sectors for increased operational efficiency and innovation, an emerging set of established and evaluated methods, tools, and techniques as well as the quickly growing body of academic and professional knowledge are indicative for the standing that Business Process Management (BPM) has nowadays. During the last decades, intensive research has been conducted with respect to the design, implementation, execution, and monitoring of business processes. Comparatively low attention, however, has been paid to questions related to organizational issues such as the adoption, usage, implications, and overall success of BPM approaches, technologies, and initiatives. This research gap motivated us to edit a corresponding special focus issue for the journal BISE/WIRTSCHAFTSINFORMATIK. We are happy that we are able to present a selection of three research papers and a state-of-the-art paper in the scientific section of the issue at hand. As these papers differ in the topics they investigate, the research method they apply, and the theoretical foundations they build on, the diversity within the BPM field becomes evident. The academic papers are complemented by an interview with Phil Gilbert, IBM’s Vice President for Business Process and Decision Management, who reflects on the relationship between business processes and the data flowing through them, the need to establish a process context for decision making, and the calibration of BPM efforts toward executives who see processes as a means to an end, rather than a first-order concept in its own right.

Slice, mine and dice : complexity-aware automated discovery of business process models

Automated process discovery techniques aim at extracting models from information system logs in order to shed light into the business processes supported by these systems. Existing techniques in this space are effective when applied to relatively small or regular logs, but otherwise generate large and spaghetti-like models. In previous work, trace clustering has been applied in an attempt to reduce the size and complexity of automatically discovered process models. The idea is to split the log into clusters and to discover one model per cluster. The result is a collection of process models -- each one representing a variant of the business process -- as opposed to an all-encompassing model. Still, models produced in this way may exhibit unacceptably high complexity. In this setting, this paper presents a two-way divide-and-conquer process discovery technique, wherein the discovered process models are split on the one hand by variants and on the other hand hierarchically by means of subprocess extraction. The proposed technique allows users to set a desired bound for the complexity of the produced models. Experiments on real-life logs show that the technique produces collections of models that are up to 64% smaller than those extracted under the same complexity bounds by applying existing trace clustering techniques.

Which cultural values matter to business process management? Results from a global Delphi study

Purpose – Business process management (BPM) requires a holistic perspective that includes managing the culture of an organization to achieve objectives of efficient and effective business processes. Still, the specifics of a BPM-supportive organizational culture have not been examined so far. Thus, the purpose of this paper is to identify the characteristics of a cultural setting supportive of BPM objectives. Design/methodology/approach – The paper examines the constituent values of a BPM-supportive cultural setting through a global Delphi study with BPM experts from academia and practice and explore these values in a cultural value framework. Findings – The paper empirically identifies and defines four key cultural values supporting BPM, viz., customer orientation, excellence, responsibility, and teamwork. The paper discusses the relationships between these values and identifies a particular challenge in managing these seemingly competing values. Research limitations/implications – The identification and definition of these values represents a first step towards the operationalization (and empirical analysis) of what has been identified as the concept of BPM culture, i.e. a culture supportive of achieving BPM objectives. Practical implications – Identifying these cultural values provides the basis for developing an instrument that can measure how far an existing cultural context is supportive of BPM. This, in turn, is fundamental for identifying measures towards achieving a BPM culture as a necessary, yet not sufficient means to obtain BPM success. Originality/value – The paper examines which cultural values create an environment receptive for BPM and, thus, specifies the important theoretical construct BPM culture. In addition, the paper raises awareness for realizing these values in a BPM context.

Normative requirements for business process compliance

Norms regulate the behaviour of their subjects and define what is legal and what is illegal. Norms typically describe the conditions under which they are applicable and the normative effects as a results of their applications. On the other hand, process models specify how a business operation or service is to be carried out to achieve a desired outcome. Norms can have significant impact on how business operations are conducted and they can apply to the whole or part of a business process. For example, they may impose conditions on the different aspects of a process (e.g., perform tasks in a specific sequence (control-flow), at a specific time or within a certain time frame (temporal aspect), by specific people (resources)). We propose a framework that provides the formal semantics of the normative requirements for determining whether a business process complies with a normative document (where a normative document can be understood in a very broad sense, ranging from internal policies to best practice policies, to statutory acts). We also present a classification of normal requirements based on the notion of different types of obligations and the effects of violating these obligations.

Specifying information systems for business process integration : a management perspective

Supply chain management and customer relationship management are concepts for optimizing the provision of goods to customers. Information sharing and information estimation are key tools used to implement these two concepts. The reduction of delivery times and stock levels can be seen as the main managerial objectives of an integrative supply chain and customer relationship management. To achieve this objective, business processes need to be integrated along the entire supply chain including the end consumer. Information systems form the backbone of any business process integration. The relevant information system architectures are generally well-understood, but the conceptual specification of information systems for business process integration from a management perspective, remains an open methodological problem. To address this problem, we will show how customer relationship management and supply chain management information can be integrated at the conceptual level in order to provide supply chain managers with relevant information. We will further outline how the conceptual management perspective of business process integration can be supported by deriving specifications for enabling information system from business objectives.

Personal processes interface mock up

Situated on Youtube, and shown in various locations. In this video we show a 3D mock up of a personal house purchasing process. A path traversal metaphor is used to give a sense of progression along the process stages. The intention is to be able to use console devices like an Xbox to consume business processes. This is so businesses can expose their internal processes to consumers using sophisticated user interfaces. The demonstrator was developed using Microsoft XNA, with assistance from the Suncorp Bank and the Smart Services CRC. More information at: www.bpmve.org

A methodological evaluation of business process compliance management frameworks

Existing compliance management frameworks (CMFs) offer a multitude of compliance management capabilities that makes difficult for enterprises to decide on the suitability of a framework. Making a decision on the suitability requires a deep understanding of the functionalities of a framework. Gaining such an understanding is a difficult task which, in turn, requires specialised tools and methodologies for evaluation. Current compliance research lacks such tools and methodologies for evaluating CMFs. This paper reports a methodological evaluation of existing CMFs based on a pre-defined evaluation criteria. Our evaluation highlights what existing CMFs offer, and what they cannot. Also, it underpins various open questions and discusses the challenges in this direction.

Cost-aware business process management: A research agenda

Organisations are constantly seeking cost-effective improvements for their business processes. Business process management (BPM) provides organisations with a range of methods, techniques and tools for analysing, managing, and optimising their business operations. However, BPM initiatives within organisations tend to focus on investigating time and resource utilisation inefficiencies, rather than directly on cost inefficiencies. As a result, high-level cost-based managerial decisions are still being made separately from process related decisions. This position paper describes a research agenda that envisages a holistic approach to managing the cost of business operations in a structured manner, by making an explicit link between cost and processes in all phases of the business process management life cycle. We discuss a number of research challenges that need to be addressed in order to realise such an approach as well as findings from some of the initial research outcomes. It is envisioned that the research outcomes will enable organisations to make operational and strategic decisions with confidence based on accurate and real-time cost information about their operations.

Business continuity management in airports : securing continuity in the face of crisis

This thesis investigated both the potential for Business Continuity Management to enhance organisational reliability, and appropriate levels of Business Continuity Management capability resident in a number of Australian international and regional airports. Findings indicated that a host of regulatory and business processes including Business Continuity Management can assist in creating reliability in aviation infrastructure systems in Australia. Further, the thesis developed a multi-level maturity assessment framework for defining the depth of implementation of Business Continuity Management capabilities in airports, along with other recommendations to improve functional reliability of airport operations.

Applying Enterprise Architecture to Business Networks

Globalization, financial deregulation, economic turmoil, and technology breakthroughs are profoundly exposing organizations to business networks. Engaging these networks requires explicit planning from the strategic level down to the operational level of an organization, which significantly affects organizational artefacts such as business services, processes, and resources. Although enterprise architecture (EA) aligns business and IT aspects of organizational systems, previous applications of EA have not comprehensively addressed a methodological framework for planning. In the context of business networks, this study seeks to explore the application of EA for business network planning where it builds upon relevant and well-established prescriptive and descriptive aspects of EA. Prescriptive aspects include integrated models of services, business processes, and resources among other organizational artefacts, at both business and IT levels. Descriptive aspects include ontological classifications of business functionality, which allow EA models to be aligned semantically to organizational artefacts and, ultimately higher-level business strategy. A prominent approach for capturing descriptive aspects of EA is business capability modelling. In order to explore and develop the illustrative extensions of EA through capability modelling, a list of requirements (capability dimensions) for business network planning will be identified and validated through a revelatory case study encompassing different business network manifestations, or situations. These include virtual organization, liquid workforce, business network orchestration, and headquarters-subsidiary. The use of artefacts, conventionally, modelled through EA will be considered in these network situations. Two general considerations for EA extensions are explored for the identified requirements at the level of the network: extension of artefacts through the network and alignment of network level artefacts with individual organization artefacts. The list of requirements provides the basis for a constructivist extension of EA in the following ways. Firstly, for descriptive aspects, it offers constructivist insights to guide extensions for particular EA techniques and concepts. Secondly, for prescriptive aspects it defines a set of capability dimensions, which improve the analysis and assessment of organization capabilities for business network situations.

A business perspective of legacy systems

Abstract Legacy information systems evolved incrementally in response to changes in business strategy and information technology. Organizations are now being forced to change much more radically and quickly than previously and this change places new demands on information systems. Legacy information systems are usually considered from a technical perspective, addressing issues such as age, complexity, maintainability, design and technology. We wish to demonstrate that the business dimension to legacy information systems, represented by the organisation structure, business processes and procedures that are bound up in the design and operation of the existing IT systems, is also significant. This paper identifies the important role of legacy information systems in the formation of new strategies. We show that the move away from a stable to an unstable business environment accelerates the rate of change. Furthermore, the gap between what the legacy information systems can deliver and the strategic vision of the organization widens when the legacy information systems are unable to adapt to meet the new requirements. An analysis of fifteen case studies provides evidence that legacy information systems include business and technical dimensions and that the systems can present problems when there is a misalignment between the strategic vision of the business, the IT legacy and the old business model embodied in the legacy.

Event interval analysis: Why do processes take time?

Through the application of process mining, valuable evidence-based insights can be obtained about business processes in organisations. As a result the field has seen an increased uptake in recent years as evidenced by success stories and increased tool support. However, despite this impact, current performance analysis capabilities remain somewhat limited in the context of information-poor event logs. For example, natural daily and weekly patterns are not considered. In this paper a new framework for analysing event logs is defined which is based on the concept of event gap. The framework allows for a systematic approach to sophisticated performance-related analysis of event logs containing varying degrees of information. The paper formalises a range of event gap types and then presents an implementation as well as an evaluation of the proposed approach.

Fast and accurate business process drift detection

Business processes are prone to continuous and unexpected changes. Process workers may start executing a process differently in order to adjust to changes in workload, season, guidelines or regulations for example. Early detection of business process changes based on their event logs – also known as business process drift detection – enables analysts to identify and act upon changes that may otherwise affect process performance. Previous methods for business process drift detection are based on an exploration of a potentially large feature space and in some cases they require users to manually identify the specific features that characterize the drift. Depending on the explored feature set, these methods may miss certain types of changes. This paper proposes a fully automated and statistically grounded method for detecting process drift. The core idea is to perform statistical tests over the distributions of runs observed in two consecutive time windows. By adaptively sizing the window, the method strikes a trade-off between classification accuracy and drift detection delay. A validation on synthetic and real-life logs shows that the method accurately detects typical change patterns and scales up to the extent it is applicable for online drift detection.

Liquid Business Process Model Collections

Many organizations realize that increasing amounts of data (“Big Data”) need to be dealt with intelligently in order to compete with other organizations in terms of efficiency, speed and services. The goal is not to collect as much data as possible, but to turn event data into valuable insights that can be used to improve business processes. However, data-oriented analysis approaches fail to relate event data to process models. At the same time, large organizations are generating piles of process models that are disconnected from the real processes and information systems. In this chapter we propose to manage large collections of process models and event data in an integrated manner. Observed and modeled behavior need to be continuously compared and aligned. This results in a “liquid” business process model collection, i.e. a collection of process models that is in sync with the actual organizational behavior. The collection should self-adapt to evolving organizational behavior and incorporate relevant execution data (e.g. process performance and resource utilization) extracted from the logs, thereby allowing insightful reports to be produced from factual organizational data.