Planning for 'drift'?: implementation process of enterprise resource planning systems

This paper reports the findings of a large-scale case study of implementing enterprise resource planning systems (ERP) in a long-established multinational company within the telecommunication sector. The company has recently streamlined its operations through an ambitious business process redesign initiative and introduced an ERP system. The study examines the process of change enacted during the implementation of the ERP system over time. The findings indicate that much of the changes emerged as the project team sought to improvise technological features and changes to the context of use to overcome embedded constraints in the existing system, organizational context and in the ERP system itself. The team also took advantage of evolving capabilities and emerging opportunities to continuously enact changes as an ongoing process of project life. The paper argues that the process of technology-related change may be seen as a form of a 'drift' involving a series of purposeful actions with unplanned outcomes.

[1]  Yoris A. Au Design Science I: The Role of Design Science in Electronic Commerce Research , 2001, Commun. Assoc. Inf. Syst..

[2]  Jeanne W. Ross Dow Corning Corporation: business processes and information technology , 1999, J. Inf. Technol..

[3]  Andrew Pickering,et al.  The mangle of practice : time, agency, and science , 1997 .

[4]  A. Adam Whatever happened to information systems ethics? Caught between the devil and the deep blue sea , 2004 .

[5]  Marie-Claude Boudreau,et al.  Organizational transition to enterprise resource planning systems: theoretical choices for process research , 1999, ICIS.

[6]  W. Orlikowski,et al.  An Improvisational Model of Change Management: The Case of Groupware Technologies , 1996 .

[7]  Henk Sol,et al.  Proceedings of the 54th Hawaii International Conference on System Sciences , 1997, HICSS 2015.

[8]  K. Lewin Field theory in social science , 1951 .

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

[10]  A. Giddens The Constitution of Society , 1985 .

[11]  A. Pettigrew The Awakening Giant , 1985 .

[12]  Jan Weglarz,et al.  Interpreting Information Systems in Organizations , 1993 .

[13]  S. Hirt,et al.  Adopting SAP at Siemens Power Corporation , 1998, ICIS '98.

[14]  Joan Antoni Pastor,et al.  Enterprise Resource Planning Systems Research: An Annotated Bibliography , 2001, Commun. Assoc. Inf. Syst..

[15]  Majed Al-Mashari,et al.  Constructs of Process Change Management in ERP Context: A Focus on SAP R/3 , 2000 .

[16]  Hartwig Brand SAP R/3 Implementation With ASAP : The Official SAP Guide , 1999 .

[17]  Daniel Robey,et al.  Perceptions of Conflict and Success in Information Systems Development Projects , 1993, J. Manag. Inf. Syst..

[18]  E. Shils The Constitution Of Society , 1982 .

[19]  Larry Press,et al.  International perspectives: computing at the top of the world , 2000, CACM.

[20]  Ben Light,et al.  Enterprise resource planning: a business approach to systems development , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[21]  Carol V. Brown,et al.  ERP implementation approaches: toward a contingency framework , 1999, ICIS.

[22]  Fabio Vitali,et al.  Web information systems , 1998, CACM.

[23]  Wanda J. Orlikowski,et al.  Improvising Organizational Transformation Over Time: A Situated Change Perspective , 1996, Inf. Syst. Res..

[24]  Amany R. Elbanna,et al.  From Control to Drift: The Dynamics of Corporate Information Infrastructures , 2001 .

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