Manufacturing management programs : are developing economies bridging the strategic gap?

Over the past decade there have been a large number of significant innovations in manufacturing which have resulted in more flexible and cost efficient methods and higher quality products, as manufacturers have set about upgrading their processes, systems and performance. This study compares the use of technologies and improvement programs between OECD and Non-OECD countries, and also between small and large firms, and examines differences in the use and outcomes across the economies and different sized firms. The empirical analysis provides an opportunity to test whether the ‘capabilities’ or strengths of a firm can be linked to these activities and examines if developing economies are using technology or management programs such as quality management and business process re-engineering to catch up to manufacturers in developed economies. The analysis utilises data from the second International Manufacturing Strategy Survey (IMSS), which encompasses 703 firms in 23 countries.

Service identification through value chain analysis and prioritization

In a resource constrained business world, strategic choices must be made on process improvement and service delivery. There are calls for more agile forms of enterprises and much effort is being directed at moving organizations from a complex landscape of disparate application systems to that of an integrated and flexible enterprise accessing complex systems landscapes through service oriented architecture (SOA). This paper describes the deconstruction of an enterprise into business services using value chain analysis as each element in the value chain can be rendered as a business service in the SOA. These business services are explicitly linked to the attainment of specific organizational strategies and their contribution to the attainment of strategy is assessed and recorded. This contribution is then used to provide a rank order of business service to strategy. This information facilitates executive decision making on which business service to develop into the SOA. The paper describes an application of this Critical Service Identification Methodology (CSIM) to a case study.

Analyzing requirements and approaches for sourcing software based services

Increasingly, software is no longer developed as a single system, but rather as a smart combination of so-called software services. Each of these provides an independent, specific and relatively small piece of functionality, which is typically accessible through the Internet from internal or external service providers. To the best of our knowledge, there are no standards or models that describe the sourcing process of these software based services (SBS). We identify the sourcing requirements for SBS and associate the key characteristics of SBS (with the sourcing requirements introduced). Furthermore, we investigate the sourcing of SBS with the related works in the field of classical procurement, business process outsourcing, and information systems sourcing. Based on the analysis, we conclude that the direct adoption of these approaches for SBS is not feasible and new approaches are required for sourcing SBS.

Analyzing requirements and approaches for sourcing software based services

Increasingly, software is no longer developed as a single system, but rather as a smart combination of so-called software services. Each of these provides an independent, specific and relatively small piece of functionality, which is typically accessible through the Internet from internal or external service providers. There are no standards or models that describe the sourcing process of these software based services (SBS). The authors identify the sourcing requirements for SBS and associate the key characteristics of SBS (with the sourcing requirements introduced). Furthermore, this paper investigates the sourcing of SBS with the related works in the field of classical procurement, business process outsourcing, and information systems sourcing. Based on the analysis, the authors conclude that the direct adoption of these approaches for SBS is not feasible and new approaches are required for sourcing SBS.

The design environment

This chapter provides an overview of the Editor, which is the core modeling component of the YAWL system. Specifically, it shows how to specify control-flow, data and resourcing requirements in a YAWL workflow model. Moreover, it describes the error reporting capabilities of the Editor and the features of its interchange format.

Open source software for workflow management : the case of YAWL

"This column is distinguished from previous Impact columns in that it concerns the development tightrope between research and commercial take-up and the role of the LGPL in an open source workflow toolkit produced in a University environment. Many ubiquitous systems have followed this route, (Apache, BSD Unix, ...), and the lessons this Service Oriented Architecture produces cast yet more light on how software diffuses out to impact us all." Michiel van Genuchten and Les Hatton Workflow management systems support the design, execution and analysis of business processes. A workflow management system needs to guarantee that work is conducted at the right time, by the right person or software application, through the execution of a workflow process model. Traditionally, there has been a lack of broad support for a workflow modeling standard. Standardization efforts proposed by the Workflow Management Coalition in the late nineties suffered from limited support for routing constructs. In fact, as later demonstrated by the Workflow Patterns Initiative (www.workflowpatterns.com), a much wider range of constructs is required when modeling realistic workflows in practice. YAWL (Yet Another Workflow Language) is a workflow language that was developed to show that comprehensive support for the workflow patterns is achievable. Soon after its inception in 2002, a prototype system was built to demonstrate that it was possible to have a system support such a complex language. From that initial prototype, YAWL has grown into a fully-fledged, open source workflow management system and support environment

Strategy content analysis for service identification : a case study on government agencies

In a resource constrained business world, strategic choices must be made on process improvement and service delivery. There are calls for more agile forms of enterprises and much effort is being directed at moving organizations from a complex landscape of disparate application systems to that of an integrated and flexible enterprise accessing complex systems landscapes through service oriented architecture (SOA). This paper describes the analysis of strategies to detect supporting business services. These services can then be delivered in a variety of ways: web-services, new application services or outsourced services. The focus of this paper is on strategy analysis to identify those strategies that are common to lines of business and thus can be supported through shared services. A case study of a state government is used to show the analytical method and the detection of shared strategies.

Surmounting BPM challenges : the YAWL story

The field of Business ProcessManagement (BPM) has evolved considerably over the past decade. Many proposals for business process modelling and/or execution have emerged and some of these have faded into oblivion again. The Workflow Patterns Initiative aimed at achieving a more structured approach to language comparison and development. The patterns that were distilled served as the basis for YAWL (Yet AnotherWorkflow Language). In this paper YAWL is positioned with respect to historical developments in BPM and current challenges in the field.

Designing a workflow system using coloured petri nets

Traditional workflow systems focus on providing support for the control-flow perspective of a business process, with other aspects such as data management and work distribution receiving markedly less attention. A guide to desirable workflow characteristics is provided by the well-known workflow patterns which are derived from a comprehensive survey of contemporary tools and modelling formalisms. In this paper we describe the approach taken to designing the newYAWL workflow system, an offering that aims to provide comprehensive support for the control-flow, data and resource perspectives based on the workflow patterns. The semantics of the newYAWL workflow language are based on Coloured Petri Nets thus facilitating the direct enactment and analysis of processes described in terms of newYAWL language constructs. As part of this discussion, we explain how the operational semantics for each of the language elements are embodied in the newYAWL system and indicate the facilities required to support them in an operational environment. We also review the experiences associated with developing a complete operational design for an offering of this scale using formal techniques.

newYAWL : Towards Workflow 2.0

The field of workflow technology has burgeoned in recent years providing a variety of means of automating business processes. It is a great source of opportunity for organisations seeking to streamline and optimise their operations. Despite these advantages however, the current generation of workflow technologies are subject to a variety of criticisms, in terms of their restricted view of what comprises a business process, their imprecise definition and their general inflexibility. As a remedy to these potential difficulties, in this paper we propose a series of development goals for the next generation of workflow technology. We also present newYAWL, a formally defined, multi-perspective reference language for workflow systems.

Of ivory towers and boundary spanners

We all live in a yellow submarine… When I go to work in the morning, in the office building that hosts our BPM research group, on the way up to our level I come by this big breakout room that hosts a number of computer scientists, working away at the next generation software algorithms and iPad applications (I assume). I have never actually been in that room, but every now and then the door is left ajar for a while and I can spot couches, lots (I mean, lots!) of monitors, the odd scientist, a number of Lara Croft posters, and the usual room equipment you’d probably expect from computer scientists (and, no, it’s not like that evil Dennis guy from the Jurassic Park movie, buried in chips, coke, and flickering code screens… It’s also not like the command room from the Nebuchadnezzar, Neo’s hovercraft in the Matrix movies, although I still strongly believe these green lines of code make a good screensaver).

Re-engineering project planning processes : a best practice model for managing project phase integration issues

Competitive markets are increasingly driving new initiatives for shorter cycle times resulting in increased overlapping of project phases. This, in turn, necessitates improving the interfaces between the different phases to be overlapped (integrated), thus allowing transfer of processes, information and knowledge from one individual or team to another. This transfer between phases, within and between projects, is one of the basic challenges to the philosophy of project management. To make the process transfer more transparent with minimal loss of momentum and project knowledge, this paper draws upon Total Quality Management (TQM) and Business Process Re-engineering (BPR) philosophies to develop a Best Practice Model for managing project phase integration. The paper presents the rationale behind the model development and outlines its two key parts; (1) Strategic Framework and (2) Implementation Plan. Key components of both the Strategic Framework and the Implementation Plan are presented and discussed.

Workflow support for scheduling in surgical care processes

Real-world business processes rely on the availability of scarce, shared resources, both human and non-human. Current workflow management systems support allocation of individual human resources to tasks but lack support for the full range of resource types used in practice, and the inevitable constraints on their availability and applicability. Based on past experience with resource-intensive workflow applications, we derive generic requirements for a workflow system which can use its knowledge of resource capabilities and availability to help create feasible task schedules. We then define the necessary architecture for implementing such a system and demonstrate its practicality through a proof-of-concept implementation. This work is presented in the context of a real-life surgical care process observed in a number of German hospitals.

A critical analysis of global BPM demand

Business Process Management is accepted globally as an organisational approach that can be used to enhance productivity and drive cost efficiencies. Whilst there are numerous research articles that discuss this management approach, none clearly articulate the preferred BPM capabilities sought across geographic regions. This study aims to address this through a structured content analysis of leading on-line recruitment websites, supported by essential BPM capabilities - identified through leading academic BPM capability frameworks. Whilst the skills of process modelling, documentation and improvement were commonly sought, Enterprise level factors such as strategic alignment and process governance were less frequently mentioned. In addition, there are geographical differences in the BPM skill set requirements with an emphasis on process governance and organisational culture in European countries. This analysis can be used by prospective and current BPM professionals to understand organisational requirements globally, and academics to structure BPM education to suit these differing geographic demands.