BUSINESS PROCESS CHANGE: Concepts, Methods and Technologies

Total Page:16

File Type:pdf, Size:1020Kb

BUSINESS PROCESS CHANGE: Concepts, Methods and Technologies BUSINESS PROCESS CHANGE: Concepts, Methods and Technologies By Varun Grover William J. Kettinger Center for Information Management and Technology Research College of Business Administration University of South Carolina IDEA GROUP PUBLISHING Harrisburg, USA • London, UK Senior Editor: Mehdi Khosrowpour Managing Editor: Jan Travers Printed at: Rose Printing Published in the United States of America by Idea Group Publishing Olde Liberty Square 4811 Jonestown Road, Suite 230 Harrisburg, PA 17109 Tel: 717-541-9150 Fax: 717-541-9159 and in the United Kingdom by Idea Group Publishing 3 Henrietta Street Covent Garden London WC2E 8LU Tel: 071-240 0856 Fax: 071-379 0609 Copyright © 1998 by Idea Group Publishing. All rights reserved. No part of this book may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without written permission from the publisher. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services. If legal advice or other expert assistance is required, the services of a competent professional person should be sought. From A Declaration of Principles jointly adopted by a committee of the American Bar Association and a committee of publishers. Printed in the United States of America Library of Congress Cataloging-in-Publication Data Grover, Varun, 1959- Business process change: reengineering concepts, methods, and technologies / Varun Grover, William J. Kettinger. p. 704 cm. Includes bibliographical references and index ISBN 1-878289-29-2 : $84.95 1. Organizational change--Management. 2. Information technology--Manage- ment. 3. Strategic planning. I. Kettinger, William J. II. Title. HD58.8.G77 1995 658.4'063--dc20 95-37 CIP To Anita and Lynda who’ve settled for only incremental change in each of us, and, to Ankit, Arjun, Lindsey and David who have wonderfully begun the process of life-long change. BUSINESS PROCESS CHANGE ...a business process is a set of logically related tasks that use the resources of an organization to achieve a defined business outcome. Business Process Reengineering (BPR), Process Improvement, Busi- ness Transformation, Process Innovation and Business Process Rede- sign are terms frequently used interchangeably to represent the phe- nomenon of “Business Process Change.” Popular competing definitions of Business Process Change propose that it is: “the fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in critical, contemporary measures of performance” “the analysis and design of team-based work flows and processes within and between organizations” “a methodological process that uses information technology to radically overhaul business process and thereby attain major business goals” “the reconfiguration of the business using IT as a central lever’ “the overhauling of business processes and organization structures that limit the competitiveness effectiveness and efficiency of the organi- zation” “the design of a company’s core processes to yield breakthrough levels of improvement, laying the basis for continuous improvement” “a strategy driven organizational initiative to (re)design business pro- cesses to achieve competitive breakthroughs in performance; differing in scope from process improvement to radical new process design, contingent upon the degree of socio-technical change required” This phenomenon is typically known to: involve CROSS FUNCTIONAL CORE PROCESSES but many improvement initiatives within narrower functional areas have also proved successful. focus on RADICAL/ONE TIME process changes but continuous improvement through stewardship of processes may be more beneficial in the long term. (iv) This phenomenon is typically known to: takes a CLEAN SLATE approach but most process change methodologies advocate documentation and analysis of existing “as is” processes and many firms are unwilling to commit resources for clean slate “revolutionary” implementation. be STRATEGY LED with initiatives from senior management but some bottom-up process change initiatives, with strong inputs from line workers and middle mangers, have proven successful. strive for BREAKTHROUGH PERFORMANCE GAINS but benchmarking and measurement of these gains can prove elusive and in many cases moderate gains more consistent with organiza- tional culture and orientation define success. be INFORMATION TECHNOLOGY ENABLED but numerous organizational innovations involving people, jobs, skills and structures can also facilitate new process oriented behaviors. be CUSTOMER DRIVEN with value defined as satisfaction but some scholars and practitioners advocate a longer-term and more strategic perspective to overcome the possible myopia of immediate customer demands in order to discover new ways to benefit future as well as present stakeholders. enhance individual capacities through EMPOWERMENT AND TEAMS but many process change projects are defended based on cost objectives achieved through downsizing and outsourcing with few opportuni- ties for retraining, team work or reallocation of decision rights. adapt a number of METHODS touted by armies of consultants but few standardized and structured approaches exist. (v) This phenomenon is typically known to: minimize redundancy, maximize concurrency toward a VIRTUAL SYSTEM but many successful process change efforts have benefited from simple efficiency improvements without fully exploiting or optimizing the best utilization of a virtual enterprise’s resources and knowledge. be run by OUTSIDERS such as consultants but the lack of concern for maintaining new business processes once reengineered has caused process management responsibilities to shift toward internal managers closer to the processes and more vested in the business. Thus, the (r)evolution of reengineering, the requirement to sustain and integrate process change, the need to reconcile alternative process improvement and management ap- proaches, and the recognition of organizational constraints to implementation, all serve to broaden the concept of BUSINESS PROCESS CHANGE, recognizing the need for the radical, the incremental, the continuous and the contin- gent. (vi) FOREWORD This book was conceived during a period of tumultuous change in the global business environment. Corporations were undergoing massive restructuring. Global competition, sluggish economies and the potential offered by emerging technologies were pushing firms to fundamentally rethink their business processes. Prominent consultants seeking to provide solutions to these problems prescribed Business Process Reengineering (BPR) as a means to restructure aging bureaucratized processes in an attempt to achieve the strategic objectives of increased efficiency, reduced costs, improved quality, and greater customer satisfaction. These consultants typically repackaged existing change theories and tech- niques of organizational structure, technology, operations, quality, and human resources in a new and exciting synthesis directed at dramatic improvements in business performance. BPR soon became the rage! Endless magazine articles heralded claims or tremendous payoffs resulting from process change. The popularity of BPR was in part fueled by claims of high pay-offs from early BPR projects. For example, Ford Motor Co. and AT&T reported major increases in productivity and decreases in staff after process reengineering and DEC was able to consolidate 55 accounting groups into five. Kodak reengineered its 1,500-employee black and white film operations by focusing on customer satisfaction and cut costs 15% below budget; cut response time in half; and dramatically reduced defects. Other early reengineering success stories include: Hallmark’s product development process, Bell Atlantic’s system billing process, an similar examples at GE, IBM’s Credit Corp., Capitol Holdings, Taco Bell, Wal-Mart, CIGNA RE, XEROX and Banc One. Ironically, while much has been discussed about BPR, most companies are still searching for theories and methods to better manage business process change. Academics are also now beginning to recognize the need to study this phenomenon, but precious little has been published. Basic questions lack consistent answers: • What does process change entail? • What are key enablers of process change? • Is there a process change methodology? • What techniques and tools have been found to successfully model and redesign business processes? • What is the role of information technology in this change? • What is the role of Information Systems personnel in changing business processes? • What is the role of people empowerment and team-based manage- (vii) ment in process change? • How do we best plan, organize and control process change efforts? • Under what conditions will BPR be most effective? Answers to these questions are not easy, nor direct. Pondering these same questions from our “steamy southern” vantage point in the Summer of 1993, we recognized there was little impartial and scholarly analysis of this compelling management trend. A book idea was born! But where should we look for quality contributions on this topic? Managers from firms that had actually undergone BPR? —These seasoned process “changees” certainly could provide important hands-on insights. But cursory descriptions of their experiences had been covered by the popular press. The time was right for moving beyond
Recommended publications
  • Business Modelling: UML Vs. IDEF
    Griffith University School of Computing and Information Technology Domain: Advanced Object Oriented Concepts Business Modelling: UML vs. IDEF available electronically at: http://www.cit.gu.edu.au/~noran © Ovidiu S. Noran Table of Contents. 1 Introduction....................................................................................................1 1.1 The objectives of this paper..............................................................................1 1.2 Motivation.........................................................................................................1 1.3 Some Important Terms.....................................................................................2 1.3.1 Models. .............................................................................................................. 2 1.3.2 Business Process Models.................................................................................. 2 1.3.3 Information Systems Support. ........................................................................... 3 1.3.3.1 The Business Model as a Base for Information Systems.......................... 3 1.3.3.2 'Legacy' Systems....................................................................................... 4 1.3.4 Business Improvement vs. Innovation............................................................... 4 1.4 Business Concepts...........................................................................................4 1.4.1 Business Architecture. ......................................................................................
    [Show full text]
  • Tools Used in Modeling of the Economic Processes Marian Pompiliu Cristescu
    EBEEC 2019 Economies of the Balkan and Eastern European Countries Volume 2019 Conference Paper Tools Used in Modeling of the Economic Processes Marian Pompiliu Cristescu Abstract The paper aims at identifying the economic process modeling languages, starting from the premise that the main beneficiaries of the resulting models are economists or decision-makers, respectively economic researchers. There are a large number of languages that have been developed with different objectives, but they have all been used to describe business processes. Languages have studied different aspects of business processes (dynamic, functional, organizational, informational) and may be more or less formal, depending on the intended use and audience. There is no easy way to classify these languages along a single dimension. However, the languages fall into four groups, clearly defined scientifically or professionally: traditional process modeling languages, object-oriented languages, dynamic process modeling Corresponding Author: languages, and the integration of languages. Economic processes are generally very Marian Pompiliu Cristescu complex and, therefore, different points can be formulated about their modeling. [email protected] Keywords: Formal language, model, simulation, algorithm, business processes. Received: 17 November 2019 Accepted: 6 January 2019 Published: 12 January 2020 Publishing services provided by Knowledge E Marian Pompiliu 1. Introduction Cristescu. This article is distributed under the terms of Business units are complex organizational forms that involve customers, business units, the Creative Commons Attribution License, which resources, and even systems. They extend over many different processes that interact in permits unrestricted use and a seemingly chaotic way. When trying to change business processes in an organization, redistribution provided that the original author and source are change is confronted and confused with great complexity.
    [Show full text]
  • IDEF5 Method Report
    Information Integration for Concurrent Engineering (IICE) IDEF5 Method Report Prepared for: Armstrong Laboratory AL/HRGA Wright-Patterson Air Force Base, Ohio 45433 Prepared by: Knowledge Based Systems, Inc. 1408 University Drive East College Station, Texas 77840 (409) 260-5274 Revision Date: September 21, 1994 Contract Number: F33615-C-90-0012 Information Integration for Concurrent Engineering (IICE) IDEF5 Method Report This document was prepared by the IDEF5 Method Development Team for the IICE Methods Engineering Thrust. Contributors: Perakath C. Benjamin, Ph.D. Christopher P. Menzel, Ph.D. Richard J. Mayer, Ph.D. Florence Fillion Michael T. Futrell Paula S. deWitte, Ph.D. Madhavi Lingineni Date: September 21, 1994 i Preface This document provides a comprehensive description of the IDEF5 Ontology Description Capture Method. The IDEF5 method was developed under the Information Integration for Concurrent Engineering (IICE) project, F33615-90-C-0012, funded by Armstrong Laboratory, Logistics Research Division, Wright-Patterson Air Force Base, Ohio 45433, under the technical direction of Captain JoAnn Sartor and Mr. James McManus. The prime contractor for IICE is Knowledge Based Systems, Inc. (KBSI), College Station, Texas. The authors wish to acknowledge and extend special thanks to the following people who helped compose this document: Julie Holden James MacDougall Richard McGuire ii Table of Contents Preface ............................................................................................................................................ii
    [Show full text]
  • Section 7.0 Data Collection for IDEF Modeling
    1 Section 6.0 Author’s Guide to Creating IDEF1 Diagrams 1:M Relation ATTRIBUTE CLASS M:N Relation 1:1 Relation ENTITY CLASS M:1 Relation 2 3 6.0 Author’s Guide To Creating IDEF1 Diagrams 6.1 Phase Zero - Context Definition The IDEF1 information model must somehow be described and defined in terms of both its limitations and its ambitions. The modeler is one of the primary influences in the development of the scope of the model. Together, the modeler and the project manager unfold the plan for reaching the objectives of Phase Zero. These objectives include: 1. Project definition – a general statement of “what” has to be done, “why” and “how” it will get done. 2. Source material – a plan for the physical compilation of source material, including the indexing and filing of it. 3. Author conventions – a fundamental declaration of the conventions (optional methods) by which the author chooses to make and manage the model. The products of these objectives, coupled with other descriptive and explanatory documents and information, become the products of the Phase Zero effort–the Phase Zero Kits. The purpose of these kits will be described more fully later in this section. 6.2 Project Definition 6.2.1 The Strategic Objective The first activity in the modeling project is to establish where the project is going, how, and, to some extent, why. In this process, the project manager will establish his authority and mandate for the project. Some rough guidelines establishing the scope of the project in terms of money, time, and breadth of effort will have been laid down, usually in a project manager’s authorizing documents.
    [Show full text]
  • Business Modelling: UML Vs. IDEF
    Griffith University School of Computing and Information Technology Domain: Modelling Languages Business Modelling: UML vs. IDEF available electronically at: http://www.cit.gu.edu.au/~noran © Ovidiu S. Noran 2000 © Ovidiu S. Noran Use of this document is permitted subject to proper reference to the author. Table of Contents. 1 Introduction....................................................................................................1 1.1 The objectives of this paper...............................................................................1 1.2 Motivation...........................................................................................................1 1.3 Some Important Terms. .....................................................................................2 1.3.1 Models. .............................................................................................................. 2 1.3.2 Business Process Models.................................................................................. 2 1.3.3 Information Systems Support. ........................................................................... 3 1.3.3.1 The Business Model as a Base for Information Systems.......................... 3 1.3.3.2 'Legacy' Systems....................................................................................... 4 1.3.4 Business Improvement vs. Innovation............................................................... 4 1.4 Business Concepts. ...........................................................................................4
    [Show full text]
  • IDEF5 Ontology Description Cap Ture Me Tho D TECHNICAL REPORT
    0 u_ _,_ c_ I U cO IDEF5 Ontology Description o Z 0 Cap ture Me tho d Concept Paper _D Christopher P. Menzel E Richard J. Mayer _-. 3) CL,F._. 4,. ¢_'L>,. V', _' _.J U_ C Knowledge Based Systems Laboratory (.._ C Texas A&M University E ,..jolt,. CU-_ 0 1990 __] 0. ,.-, CC_ ¢ _) ._ Cooperative Agreement NCC 9-16 Research Activity No. IM.06: LJ Methodologies for Integrated Information Management Systems e_. NASA Johnson Space Center Information Systems Directorate Information Technology Division Research Institute for Computing and Information Systems University of Houston-C/ear Lake TECHNICAL REPORT The RICIS Concept I The University of liouston-Clear Lake established the Research Institute for Computing and InformaUon Systems (RICIS) in 1986 to encourage the NASA Johnson Space Center (JSC] and local industry to actively support research in the computing and information sciences, As part of this endeavor, UHCL proposed a partnership with JSC to Jointly define and manage an integrated program of research in advanced data processing technology needed forJSC's main missions, including administrative, engineering and science responsi- biliUes. JSC agreed and entered into a continuing cooperative agreement with UHCL beginning in May 1986, to Jointly plan and execute such research through RIC[S. Addltionally, under CooperaUve Agreement NCC 9-16, computing and educational faciliUes arc shared by the two insUtutlons to conduct the research. The UHCL/RICIS mission is to conduct, coordinate, and disseminate research and professional level education in computing and information systems to serve the needs of the government, industry, community and academia.
    [Show full text]
  • IDEF Family of Methods for Concurrent Engineering and Business Re-Engineering Applications
    1 IDEF Family of Methods for Concurrent Engineering and Business Re-engineering Applications Richard J. Mayer, Ph.D. Knowledge Based Systems, Inc. One KBSI Place 1408 University Drive East College Station, TX 77840 (409) 260-5274 Capt. Michael K. Painter Armstrong Laboratory/ HRGA WPAFB, OH 45433 (513) 255-7775 Paula S. deWitte, Ph.D. Knowledge Based Systems, Inc. One KBSI Place 1408 University Drive East College Station, TX 77840 (409) 260-5274 “It must be remembered that there is nothing more difficult to plan, more doubtful of success, nor more dangerous to manage than the creation of a new system. For the initiator has the enmity of all who would profit by the preservation of the old institution and merely lukewarm defenders in those who would gain by the new ones” -- Machiavelli, “The Prince,” 1513 AD. Introduction In today’s environment, system implementors in Corporate Information Management (CIM), Concurrent Engineering (CE), and Computer Integrated Manufacturing face two overwhelming challenges. Besides their primary responsibility for introducing a new system into their engineering and manufacturing organizations, they also have an underlying need to introduce a new system of processes for developing these implementations. These new system development processes must employ an integrated frameworkof modeling methods. That is, the development process uses a structured collection of methods, rules, procedures, and tools to support the development and evolution of systems. The framework guides the user in applying the appropriate method Copyright © 1992, Knowledge Based Systems, Inc. 2 within the system development life-cycle. The goal of this paper is to provide some insight into the purpose of modeling, particularly from the perspective of a CIM or CE project manager/engineer who must select, use, and evaluate the results of modeling efforts in support of systems development.
    [Show full text]
  • Framework for Enterprise Systems Engineering Oscar Alejandro Saenz Florida International University
    Florida International University FIU Digital Commons FIU Electronic Theses and Dissertations University Graduate School 11-10-2005 Framework for Enterprise Systems Engineering Oscar Alejandro Saenz Florida International University DOI: 10.25148/etd.FI08081544 Follow this and additional works at: https://digitalcommons.fiu.edu/etd Recommended Citation Saenz, Oscar Alejandro, "Framework for Enterprise Systems Engineering" (2005). FIU Electronic Theses and Dissertations. 32. https://digitalcommons.fiu.edu/etd/32 This work is brought to you for free and open access by the University Graduate School at FIU Digital Commons. It has been accepted for inclusion in FIU Electronic Theses and Dissertations by an authorized administrator of FIU Digital Commons. For more information, please contact [email protected]. FLORIDA INTERNATIONAL UNIVERSITY Miami, Florida FRAMEWORK FOR ENTERPRISE SYSTEMS ENGINEERING A dissertation submitted in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY in INDUSTRIAL AND SYSTEMS ENGINEERING by Oscar Alejandro Saenz 2005 To: Dean Vish Prasad College of Engineering and Computing The dissertation, written by Oscar Alejandro Saenz, and entitled Framework for Enterprise Systems Engineering, having been approved in respect to style and intellectual content, is referred to you for judgment. We have read this dissertation and recommend that it be approved. ________________________________ Ronald Giachetti ________________________________ Paulette Johnson ________________________________ Shih-Ming Lee ________________________________ Martha A. Centeno, Co-Major Professor ________________________________ Chin-Sheng Chen, Major Professor Date of Defense: November 10, 2005 The dissertation of Oscar Alejandro Saenz is approved. ________________________________ Dean Vish Prasad College of Engineering and Computing ________________________________ Dean Douglas Wartzok University Graduate School Florida International University, 2005 ii Copyright 2005 by Oscar Alejandro Saenz All rights reserved.
    [Show full text]
  • UML Vs. IDEF: an ONTOLOGY-ORIENTED COMPARATIVE STUDY in VIEW of BUSINESS MODELLING
    UML vs. IDEF: AN ONTOLOGY-ORIENTED COMPARATIVE STUDY IN VIEW OF BUSINESS MODELLING Ovidiu Noran School of Computers and Information Technology, Griffith University Nathan (Brisbane) QLD 4111 Australia Keywords: Expressive power, modelling language, business modelling, UML, IDEF, ontologies, metamodels, modelling methodologies, Object-Oriented Analysis and Design. Abstract: The UML and IDEF sets of languages characterize typical modelling approaches of software engineering and computer integrated manufacturing, respectively. This paper presents a comparative analysis of these languages based on their ontologies and in view of their use in business modelling. A brief introduction to UML and IDEF is followed by a high-level comparison taking into account underlying paradigms and language structure. This is followed by a comparative assessment of the expressive power of the two groups of languages, based on the ontologies of their relevant components. The analysis is structured using a set of views deemed appropriate for the modelling domain (i.e. business). The key findings of this paper aim to provide an insight into the suitability of UML 'versus' that of IDEF in business modelling. 1 INTRODUCTION1 languages for developing business models. Also, the often-perceived failure of the software system to ac- The survival of businesses in today's demanding curately reflect the business that it supports has re- global market greatly depends on their agility, i.e. sulted in calls for the same set of languages to be their capability to respond adequately and timely to used in modelling both the business and its informa- changes in the environment. Agile businesses typi- tion system. cally thrive on such changes by implementing their This paper makes a contribution towards an own, continuous internal transformation processes.
    [Show full text]