Identification of Necessary Factors for Successful Implementation of ERP Systems

  • Anne N. Parr
  • Graeme Shanks
  • Peta Darke
Part of the IFIP — The International Federation for Information Processing book series (IFIPAICT, volume 20)


The identification of factors which are necessary for successful implementation of enterprise resource planning (ERP) systems is of great importance to many organizations. ERP systems have to be configured and implemented, often by a team of business analysts and consultants over a period of months or years. The process is lengthy and expensive, and may include extensive business process re-engineering. Given that the investment in these systems, including both the package and associated implementation costs, is measured in millions of dollars, failure to meet deadlines and budgets may result in substantial company loss. However, the literature on the ERP implementation process, and the factors which either facilitate or impede its progress, is not extensive. This research reports the first stage of a research program which seeks to understand successful implementation of ERP systems. The objective, of the first phase was to identify what factors are necessary for successful ERP implementation, where success is understood as adherence to time and budgetary constraints. To accomplish this objective the authors studied 42 implementation projects by interviewing 10 senior members of multiple’ ERP implementation teams. Based on these interviews, 10 candidate necessary factors for successful implementation of ERP systems are identified. Of these 10, three are of paramount importance. They are management support of the project team and of the implementation process, a project team which has the appropriate balance of business and technical skills, and commitment to the change by all stakeholders. The next phase of the research will involve in-depth case studies to explore the relationship between these factors and broader contextual and process issues.


Enterprise resource planning success factors system implementation ERP implementation. 


  1. Adams-Webber, J. R. Personal Construct Theory: Concepts and Applications. Chichester, United Kingdom: Wiley, 1979.Google Scholar
  2. Alter, S., and Ginzberg, M. “Managing Uncertainty in MIS Implementation,” Sloan Management Review (20:1), 1978, pp. 23–31.Google Scholar
  3. Ambrosio J. “Experienced SAP Users Share Ideas with Newbies,” Online News Story August 27, 1997.Google Scholar
  4. Ang, J.; Sum, C.; and Yang, K. “MRP 11 Company Profile and Implementation Problems: A Singapore Experience, ” International Journal of Production Economics (34), 1994, pp. 3545.Google Scholar
  5. Appleton, E. L. “How to Survive ERP,” Datamation (43: 3 ), March 1997, pp. 50–53Google Scholar
  6. Bailey, J., and Pearson, S. “Development of a Tool for Measuring and Analyzing Computer User Satisfaction,” Management Science (29:5), 1983, pp. 530–545.Google Scholar
  7. Bancroft, N. Implementing SAP R/3. Greenwich, CT: Manning Publications, 1996.Google Scholar
  8. Bancroft, N.; Seip, H.; and Sprengel, A. Implementing SAP R/3, 2nd ed., Greenwich, CT: Manning Publications, 1998.Google Scholar
  9. Barki, H., and Hartwick, J. “Rethinking the Concept of User Involvement, MIS Quarterly (13:1), 1989, pp. 53–63.Google Scholar
  10. Barki, H., and Hartwick, J. “Measuring User Participation, User Involvement, and User Attitude,” MIS Quarterly, March 1994, pp. 59–79.Google Scholar
  11. Baroudi, J.; Olson, M.; and Ives, B. “An Empirical Study of the Impact of User Involvement on System Usage and Information Satisfaction,” Communications of the ACM (29:3), 1986, pp. 232–238.Google Scholar
  12. Beath, C. “Supporting the Information Technology Champion,” MIS Quarterly September 1991, pp. 355–371.Google Scholar
  13. Benbasat, I., and Dexter, A. S. “An Investigation of the Effectiveness of Color and Graphical Presentation Under Varying Time Constraints,” MIS Quarterly (10:1), March 1986, pp. 5984.Google Scholar
  14. Boose, J. H., and Bradshaw, J. M. “Expertise Transfer and Complex Problems: Using AQUINAS as a Knowledge Acquisition Workbench for Knowledge-based Systems,” International Journal of Man-Machine Studies (26), 1987, pp. 3–28.Google Scholar
  15. Bowman, I. “ERP `Coned Off’ Expect Delays,” Manufacturing-Computer-Solutions (3:1), 1997, pp. 32–3.Google Scholar
  16. Bussen, W., and Myers, M. “Executive Information Systems Failure: A New Zealand Case Study,” Journal of Information Technology (12:2), 1996, pp. 145–153.Google Scholar
  17. Caldwell, B. “GTE Goes Solo on SAP R/3,” Information Week,June 8, 1998, p. 150Google Scholar
  18. Curran, T., and Keller, G. SAP R/3 Business Blueprint: Understanding the Business Process Reference Model. Englewood Cliffs, NJ: Prentice Hall, 1998.Google Scholar
  19. Davis, F. D.; Bagozzi, R. P.; and Warshaw, P. R. “User Acceptance of Computer Technology: A Comparison of Two Theoretical Models, ” Management Science, August 1989, pp. 982–1003.Google Scholar
  20. DeLone, W. H., and McLean, E. R. “The Quest for the Dependent Variable,” Information Systems Research (3: 1 ), 1992, pp. 60–95.Google Scholar
  21. Duchessi, P., Schaninger, C.; Hobbs, D.; and Pentak, L. “Determinants of Success in Implementing material Requirements Planning (MRP),” Journal of Manufacturing and Operations Management (1:3), 1998, pp. 263–304.Google Scholar
  22. Duchessi, P.; Schaninger, C.; and Hobbs, D. “Implementing a Manufacturing Planning and Control Information System,” California Management Review, Spring 1989, pp. 75–90.Google Scholar
  23. Eckhouse, J. “Money Pours Into ERP,” Information Week, June 15, 1998, p. 220.Google Scholar
  24. Ettlie, J. “R-and-D and Global Manufacturing Performance,” Management Science (44: 1 ), 1998, pp. 1–11.Google Scholar
  25. Fine, D. “Managing the Cost of Client-server,” InfoWorld (17:11), 1995, p. 62.Google Scholar
  26. Gaines, B., and Shaw, M. “Knowledge Acquisition Tools Based on Personal Construct Psychology,”, 1988.Google Scholar
  27. Gartner Group. “Implementing SAP R/3: Avoiding Becoming a Statistic,” http://www.gartner. com/, 1998.Google Scholar
  28. Ginzberg, M. J. “Early Diagnosis of MIS Implementation Failure: Promising Results and Unanswered Questions,” Management Science (27: 4 ), April 1981, pp. 459–478.Google Scholar
  29. Greiner, L. M. “Patterns of Organizational Change,” Harvard Business Review (45), 1967, pp. 119–130Google Scholar
  30. Greiner, L. M., and Barnes, L. B. “Organizational Change and Development in Organizational Behavior and Administration,” in P. R. Lawrence, L. Barnes, and J. Lorsch (eds.), Homewood, IL: Richard D. Irwin, 1976, pp. 625–636.Google Scholar
  31. Gross, P., and Ginzberg, M. “Barriers to the Adoption of Application Software Packages,” Systems, Objectives, Solutions (4), 1984, pp. 227–234.Google Scholar
  32. Hecht, B. “Choose the Right ERP Software,” Datamation (43:3), March 1997, pp. 50–53.Google Scholar
  33. Horwitt, E. “Enduring a Global Rollout—and Living to Tell About It,” Computerworld (32:14), April 6, 1998, pp. 8–12.Google Scholar
  34. Ives, B., and Olson, M. H. “User Involvement and MIS Success: A Review of the Research,” Management Science, (30:5), May 1984, pp. 586–603.Google Scholar
  35. Ives, B.; Olson, M. H.; and Baroudi, J. J. “The Measurement of User Information Satisfaction,” Communications of the ACM (26: 10 ), 1983, pp. 785–793.Google Scholar
  36. Kanter, R. M. The Change Masters. New York: Simon and Schuster, 1983.Google Scholar
  37. Keil, M., and Erran, C. “Customer-developer Links in Software Development,” Communications of the ACM (38:5), 1995, pp. 33–50.Google Scholar
  38. Kelly, G. A. The Psychology of Personal Constructs. New York: W. W. Norton, 1955. Landvater, D. Control of the Business Newsletter. Newbury, NH: The Oliver Wright Companies, 1985.Google Scholar
  39. Langnau, L. “Glitz and Hype Signal Caution, ” Material Handling Engineering (53:5), May 1998 53: 5Google Scholar
  40. Lawrence, M., and Low, G. “Exploring Individual User Satisfaction within User-led Development,” MIS Quarterly (2), 1993, pp. 195–208.Google Scholar
  41. Leavitt, H. J. “Applied Organizational Changes in Industry: Structural, Technological, and Heuristic Approaches,” in Handbook of Organizations, J. G. March (ed.). New York: Rand McNally, 1965, pp. 1144–1170.Google Scholar
  42. Levin, R.; Mateyaschuk, J.; and Stein, T. “Faster ERP Rollouts,” Information Week, July 13, 1998.Google Scholar
  43. Lucas, H. “Management Information Systems,” Management Accounting,(61:6), 1979, pp. 8, 63.Google Scholar
  44. Lucas, H. Implementation, The Key to Successful Information Systems. New York: Columbia, 1981.Google Scholar
  45. Lucas, H.; Walton, E.; and Ginzberg, M. “Implementing Packaged Software,” MIS Quarterly, December 1988, pp. 537–549.Google Scholar
  46. Lynch, R. “Implementing Packaged Application Software: Hidden Costs and Challenges,” Systems, Objectives, Solutions (4), 1984, pp. 227–234.Google Scholar
  47. Martin, M. “An Electronics Firm Will Save Big Money by Replacing Six People with One and Lose All the Paperwork, Using Enterprise Resource Planning Software. But Not Every Company Has Been So Lucky,” Fortune (137:2), 1998, pp. 149–151.Google Scholar
  48. McKie, S. “Packaged Apps for the Masses,” DBMS. (10:11), October 1997, pp. 64–66, 68.Google Scholar
  49. Nandhakumar, J. “Design for Success? Critical Success Factors in Executive Information Systems Development,” European Journal of Information Systems (5), 1996, pp. 62–72.Google Scholar
  50. Newman, M., and Robey, D. “A Social Process Model of User-Analyst Relationships,” MIS Quarterly (16:2), 1992, pp. 249–266.Google Scholar
  51. Piszczalski, M. “Lessons Learned from Europe’s SAP Users,” Production (109:1), January 1997, pp. 54–56.Google Scholar
  52. Reich, B. H., and Benbasat, I. “An Empirical Investigation of Factors influencing the Success of Customer-Oriented Strategic Systems,” Information Systems Research (1:3), September 1990, 325–347.Google Scholar
  53. Rivard, S., and and Huff, S. “User Developed Applications: Evaluation of Success from the DP Department Perspective,” MIS Quarterly (8:1), 1984, pp. 39–50.Google Scholar
  54. Robey, D. “User Attitudes and Management Information Use, ” Academy of Management Journal, September 1979, pp. 527–538.Google Scholar
  55. Rogers, E. M. The Diffusion of Innovations, 3`d ed. New York: Free Press, 1983.Google Scholar
  56. Stedman, C. “Business Application Rollouts Still Difficult,” Computerworld (32:28, November 2, 1998a, pp. 53, 56.Google Scholar
  57. Stedman, C. “ERP User Interfaces Drive Workers Nuts,” Computerworld (32:44), November 2, 1998b, pp. 1, 24.Google Scholar
  58. Steen, M. “Enterprise Resource Planning Teams Learn by Doing as Well as Training,” Info World (20:45), November 9, 1998.Google Scholar
  59. Steinbart, P. J., and Nath, R. “Problems and Issues in the Management of International Data Communications Networks: The Experiences of American Companies,” MIS Quarterly (16:1), 1992, pp. 55–76.Google Scholar
  60. Swanson, E. B. “Management Information Systems: Appreciation and Involvement,” Management Science (21: 2 ), 1974, pp. 178–188.Google Scholar
  61. Swanson, E. B. “Information Channel Disposition and Use,” Decision Sciences (18: 1 ), 1987, pp. 131–145.Google Scholar
  62. Tebbe, M. “War Stories Outnumber Successes When It Comes to Implementing SAP,” (19:27), July 7, 1997, p. 120.Google Scholar
  63. White, E. M.; Anderson, J.; Schroeder, R., and Tupy S. “A Study of the MRP Implementation Process,” Journal of Operations Management, 1982, pp. 145–154.Google Scholar
  64. Woodward, J. Industrial Organization: Theory and Parts. London: Oxford University Press, 1965.Google Scholar
  65. Wrenden, N. “Model Business Processes,” Information Week, September 1998, pp. 1A - 8A.Google Scholar

Copyright information

© IFIP International Federation for Information Processing 1999

Authors and Affiliations

  • Anne N. Parr
    • 1
  • Graeme Shanks
    • 2
  • Peta Darke
    • 1
  1. 1.Monash UniversityAustralia
  2. 2.University of MelbourneAustralia

Personalised recommendations