Skip to main content Accessibility help
×
Hostname: page-component-586b7cd67f-t7fkt Total loading time: 0 Render date: 2024-11-20T08:35:52.402Z Has data issue: false hasContentIssue false

9 - Designing ERP Systems: Should Business Processes or ERP Software Be Changed?

from PART THREE - ERP LIFE CYCLE

Published online by Cambridge University Press:  05 June 2012

Daniel E. O'Leary
Affiliation:
University of Southern California
Get access

Summary

As part of choosing ERP software, firms face a design “reengineering policy” decision regarding the amount of software customization and organizational reengineering that must be done. On one hand, since no software is likely to meet all of a firm's needs, some firms have chosen to substantially customize the software to fit their processes. On the other hand, many businesses have used adoption of new software as a chance to change their basic business processes, reengineering their organization to match the “best practice” processes in the ERP software. In order to clarify the extent to which different firms pursue different policies, Forrester Research conducted a survey (Lamonica 1998) and found the following percentage of firms following policies:

  • choose applications that fit their business and customize a bit – 37%;

  • customize applications to fit their business – 5%;

  • reengineer business to fit application – 41%;

  • no policy – 17%.

This chapter analyzes two basic questions.

  1. (1) How does the reengineering policy influence the software application choice process?

  2. (2) Should business processes or ERP software be changed?

How Does Reengineering Policy Influence Software Choice Processes: On the Relevance of “As Is” and “To Be” Modeling

The decision to modify software or reengineer business processes (or both) influences the relevance and use of “as is” and “to be” modeling.

Type
Chapter
Information
Enterprise Resource Planning Systems
Systems, Life Cycle, Electronic Commerce, and Risk
, pp. 117 - 140
Publisher: Cambridge University Press
Print publication year: 2000

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure [email protected] is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×