scispace - formally typeset
Open AccessJournal ArticleDOI

The maintenance implications of the customization of ERP software

Ben Light
- 14 Nov 2001 - 
- Vol. 13, Iss: 6, pp 415-429
Reads0
Chats0
TLDR
In this paper, the authors present two case studies of ERP projects where customizations have been performed and show that while customization can give true organizational benefits, careful consideration is required to determine whether a customization is viable given its potential impact upon future maintenance.
Abstract
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.

read more

Content maybe subject to copyright    Report

Citations
More filters
Journal ArticleDOI

Critical Success Factors for Enterprise Resource Planning Implementation and Upgrade

TL;DR: A case study of two organizations that had implemented and upgraded ERP systems adopted Markus and Tanis' four-phase model and compared the importance of these critical success factors across the phases of ERP implementation and upgrade.
Journal ArticleDOI

Enterprise Resource Planning (ERP): a review of the literature

TL;DR: The literature is analysed under six major themes and nine sub-themes and will serve as a comprehensive bibliography of the articles published during the period between January 2000 and May 2006.
Posted Content

ERP Systems and the University as a 'Unique' Organisation

TL;DR: Analysis of the rollout of an ERP system in one particular institution in the UK is provided, the particular focus being on how the development, implementation and use of both generic and university specific functionality is mediated and shaped by a fundamental and long standing tension within universities.
Journal Article

Critical Success Factors in International ERP Implementations: A Case Research Approach

TL;DR: An increased emphasis upon the determination of clear goals and objectives at the project outset, and the provision by international vendors of added value in terms of new business practice knowledge and enhanced project team capability are found.
Journal ArticleDOI

ERP modeling: a comprehensive approach

TL;DR: A generic reverse engineering process, aimed at developing a model that captures the available alternatives at different application levels of an Enterprise Resource Planning (ERP) system, and develops criteria for evaluating modeling languages for this purpose.
References
More filters
Book

Case Study Research: Design and Methods

Robert K. Yin
TL;DR: In this article, buku ini mencakup lebih dari 50 studi kasus, memberikan perhatian untuk analisis kuantitatif, membahas lebah lengkap penggunaan desain metode campuran penelitian, and termasuk wawasan metodologi baru.
Book

Qualitative Data Analysis: An Expanded Sourcebook

TL;DR: This book presents a step-by-step guide to making the research results presented in reports, slideshows, posters, and data visualizations more interesting, and describes how coding initiates qualitative data analysis.
Book

The art of case study research

TL;DR: In this article, an intensive study of case study research methods is presented, focusing on the Unique Case Research Questions and the Nature of Qualitative Research Data Gathering Analysis and Interpretation Case Researcher Roles Triangulation.
Journal ArticleDOI

Putting the enterprise into the enterprise system

TL;DR: The author discusses the pros and cons of implementing an enterprise system, showing how a system can produce unintended and highly disruptive consequences and cautions against shifting responsibility for its adoption to technologists.
Related Papers (5)