Developing ERP Systems Success Model for the Construction Industry
Publication: Journal of Construction Engineering and Management
Volume 135, Issue 3
Abstract
Recently, a significant number of major construction companies embarked on the implementation of integrated information technology solutions such as enterprise resource planning (ERP) systems to better integrate various business functions. However, these integrated systems in the construction sector present a set of unique challenges, different from those in the manufacturing or other service sectors. There have been many cases of failure in implementing ERP systems in the past, so it is critical to identify and understand the factors that largely determine the success or failure of ERP implementation in the construction industry. This paper presents the process of developing an ERP systems success model to guide a successful ERP implementation project and to identify success factors for ERP systems implementation. The paper identifies factors associated with the success and failure of ERP systems, and develops a success model to analyze the relationships between key factors and the success of such systems. The proposed ERP systems success model adapts the technology acceptance model and DeLone and McLean’s information systems success model and integrates those with key project management principles. The goal of the ERP systems success model is to better evaluate, plan, and implement ERP projects and help senior managers make better decisions when considering ERP systems in their organization.
Get full access to this article
View all available purchase options and get full access to this article.
References
Ajzen, I., and Fishbein, M. (1980). Understanding attitudes and predicting social behavior, Prentice-Hall, Englewood Cliffs, N.J.
Akkermans, H., and Helden, K. V. (2002). “Vicious and virtuous cycles in ERP implementation: A case study of interrelations between critical success factors.” Eur. J. Inf. Syst., 11, 35–46.
Barclay, D., Thompson, R., and Higgin, C. (1995). “The partial least squares (PLS) approach to causal modeling: Personal computer adoption and use as an illustration.” Tech. Stud., 2(2), 285–309.
Chung, B., Skibniewski, M. J., Lucas, H. C., Jr., and Kwak, Y. H. (2008). “Analyzing enterprise resource planning (ERP) systems implementation success factors in the engineering-construction industry.” J. Comput. Civ. Eng., 22(6), 373–382.
Davis, F. D. (1989). “Perceived usefulness, perceived ease of use, and user acceptance of information technology.” MIS Q., 13(3), 318–340.
Davis, F. D., Bagozzi, R. P., and Warshaw, P. R. (1989). “User acceptance of computer technology: A comparison of two theoretical models.” Manage. Sci., 35(8), 982–1003.
Davis, G. B., and Olson, M. H. (1985). Management information systems: Conceptual foundations, structure, and development, McGraw-Hill, New York.
DeLone, W. H., and McLean, E. R. (1992). “Information systems success: The quest for the dependent variable.” Entrepreneurship Theory Pract., 3(1), 60–95.
Ewusi-Mensah, K. (1997). “Critical issues in abandoned information systems development projects.” Commun. ACM, 40(9), 74–80.
Ferratt, T. W., Ahire, S., and De, P. (2006). “Achieving success in large projects: Implications from a study of ERP implementations.” Interfaces, 36(5), 458–469.
Fishbein, M., and Ajzen, I. (1975). Belief, attitude, intention, and behavior: An introduction to theory and research, Addison-Wesley, Reading, Mass.
Gargeya, V. B., and Brady, C. (2005). “Success and failure factors of adopting SAP in ERP system implementation.” Bus. Process Manage. J., 11(5), 501–516.
George, D., and Mallery, P. (2007). SPSS for Windows step by step: A simple guide and reference 14.0 update, Allyn and Bacon, Boston, Mass.
Hartwick, J., and Barki, H. (2001). “Communication as a dimension of user participation.” IEEE Trans. Prof. Commun., 44(1), 21–36.
Kaplan, R. M., and Saccuzzo, D. P. (1993). Psychological testing: Principles, applications and issues, Brooks/Cole Publishing, Pacific Grove, Calif.
Keil, M., Cule, P. E., Lyytinen, K., and Schmidt, R. C. (1998). “A framework for identifying software project risks.” Commun. ACM, 41(11), 76–83.
Koch, C. (2002). “ABC: An introduction to ERP: Getting started with enterprise resource planning (ERP).” CIO.
Legris, P., Ingham, J., and Collerette, P. (2003). “Why do people use information technology? A critical review of the technology acceptance model.” Inf. Manage., 40, 191–204.
Lucas, H. C., and Spitler, V. K. (1999). “Technology use and performance: A field study of broker workstations.” Decision Sci., 30(2), 291–311.
Moore, G. C., and Benbasat, I. (1991). “Development of an instrument to measure the perceptions of adopting an information technology innovation.” Entrepreneurship Theory Pract., 2(3), 192–222.
Pinto, J. K., and Slevin, D. P. (1987). “Critical factors in successful project implementation.” IEEE Trans. Eng. Manage., EM34(1), 22–27.
Shenhar, A. J., Tishler, A., Dvir, D., Lipovetsky, S., and Lechler, T. (2002). “Refining the search for project success factors: A multivariate, typological approach.” R&D Manage, 32(2), 111–126.
Shi, J. J., and Halpin, D. W. (2003). “Enterprise resource planning for construction business management.” J. Constr. Eng. Manage., 129(2), 214–221.
Umble, E. J., and Umble, M. M. (2002). “Avoiding ERP implementation failure.” Ind. Manage., 44(1), 25–33.
Venkatesh, V., and Davis, F. D. (2000). “A theoretical extension of the technology acceptance model: Four longitudinal field studies.” Manage. Sci., 46(2), 186–204.
Information & Authors
Information
Published In
Journal of Construction Engineering and Management
Volume 135 • Issue 3 • March 2009
Pages: 207 - 216
Copyright
© 2009 ASCE.
History
Received: Feb 13, 2008
Accepted: Sep 16, 2008
Published online: Mar 1, 2009
Published in print: Mar 2009
Authors
Metrics & Citations
Metrics
Citations
Download citation
If you have the appropriate software installed, you can download article citation data to the citation manager of your choice. Simply select your manager software from the list below and click Download.