The maintenance implications of the customization of ERP software

Enterprise resource planning (ERP) software is a dominant approach for dealing with legacy information system problems. In order to avoid invalidating maintenance and development support from the ERP vendor, most organizations reengineer their business processes in line with those implicit within the software. Regardless, some customization is typically required. This paper presents two case studies of ERP projects where customizations have been performed. The case analysis suggests that while customizations can give true organizational benefits, careful consideration is required to determine whether a customization is viable given its potential impact upon future maintenance. Copyright © 2001 John Wiley & Sons, Ltd.

[1]  August-Wilhelm Scheer,et al.  Enterprise resource planning: making ERP a success , 2000, CACM.

[2]  M. Lynne Markus,et al.  Learning from adopters' experiences with ERP: problems encountered and success achieved , 2000, J. Inf. Technol..

[3]  Henry C. Lucas,et al.  Implementing Packaged Software , 1987, MIS Q..

[4]  Edward Toomer,et al.  Qualitative Methods in Management Research , 1989 .

[5]  J. Gill,et al.  Research Methods For Managers , 1991 .

[6]  C. Holland,et al.  Enterprise Resource Planning Systems: Impacts and Future Directions , 2000 .

[7]  Ned Chapin,et al.  Types of software evolution and software maintenance , 2001, J. Softw. Maintenance Res. Pract..

[8]  R. Stake.  The art of case study research , 1995 .

[9]  Janet Butler.  Risk Management Skills Needed in A Packaged Software Environment , 1999, Inf. Syst. Manag..

[10]  L. Willcocks,et al.  Second-Wave Enterprise Resource Planning Systems: The Role of the CIO and IT Functions in ERP , 2000 .

[11]  Meir M. Lehman.  Programs, life cycles, and laws of software evolution , 1980 .

[12]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[13]  Ben Light,et al.  Focus issue on legacy information systems and busines process engineering: a business perspective of legacy information systems , 1999 .

[14]  Ben Light,et al.  Global enterprise resource planning implementation , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[15]  A. Scheer,et al.  Making ERP a Success. , 2000 .

[16]  David Silverman,et al.  Qualitative research: meanings or practices? , 1998, Inf. Syst. J..

[17]  Marinos Themistocleous,et al.  ERP and application integration: Exploratory survey , 2001, Bus. Process. Manag. J..

[18]  Mary Sumner,et al.  Risk factors in enterprise-wide/ERP projects , 2000, J. Inf. Technol..

[19]  Michael Hammer,et al.  Reengineering Work: Don’t Automate, Obliterate , 1990 .

[20]  Michael Rosemann,et al.  What is ERP? , 2000, Inf. Syst. Frontiers.

[21]  Judy E. Scott,et al.  Enhancing functionality in an enterprise software package , 2000, Inf. Manag..

[22]  Young-Gul Kim.  Improving Legacy Systems Maintainability , 1997, Inf. Syst. Manag..

[23]  W. Stephen Adolph,et al.  Cash Cow in the Tar Pit: Reengineering a Legacy System , 1996, IEEE Softw..

[24]  Keith H. Bennett,et al.  Legacy Systems: Coping with Success , 1995, IEEE Softw..

[25]  Prasad Bingi,et al.  Critical Issues Affecting an ERP Implementation , 1999, Inf. Syst. Manag..

[26]  Ben Light,et al.  A Critical Success Factors Model for ERP Implementation , 1999, IEEE Softw..

[27]  Matthew B. Miles,et al.  Qualitative Data Analysis: An Expanded Sourcebook , 1994 .

[28]  Leslie P. Willcocks,et al.  Enterprise resource planning: the role of the CIO and it function in ERP , 2000, CACM.

[29]  Matthew Turk,et al.  Perceptual user interfaces , 2000 .

[30]  Sia Siew Kien,et al.  Enterprise resource planning: cultural fits and misfits: is ERP a universal solution? , 2000, CACM.

[31]  Ben Light,et al.  ERP and best of breed: a comparative analysis , 2001, Bus. Process. Manag. J..

[32]  T. Davenport.  Putting the enterprise into the enterprise system. , 1998, Harvard business review.

[33]  Ben Light,et al.  A business perspective of legacy systems , 1999 .