We develop and test a theoretical model to investigate the assimilation of enterprise systems in the post-implementation stage within organizations. Specifically, this model explains how top management mediates the impact of external institutional pressures on the degree of usage of enterprise resource planning (ERP) systems. The hypotheses were tested using survey data from companies that have already implemented ERP systems. Results from partial least squares analyses suggest that mimetic pressures positively affect top management beliefs, which then positively affects top management participation in the ERP assimilation process. In turn, top management participation is confirmed to positively affect the degree of ERP usage. Results also suggest that coercive pressures positively affect top management participation without the mediation of top management beliefs. Surprisingly, we do not find support for our hypothesis that top management participation mediates the effect of normative pressures on ERP usage, but instead we find that normative pressures directly affect ERP usage. Our findings highlight the important role of top management in mediating the effect of institutional pressures on IT assimilation. We confirm that institutional pressures, which are known to be important for IT adoption and implementation, also contribute to post-implementation assimilation when the integration processes are prolonged and outcomes are dynamic and uncertain.

/pdf/assimilation-of-enterprise-systems-the-effect-of-4bilo1zpw7.pdf

Assimilation of enterprise systems: the effect of institutional pressures and the mediating role of top management

Enterprise resource planning (ERP) systems have emerged as the core of successful information management and the enterprise backbone of organizations. The difficulties of ERP implementations have been widely cited in the literature but research on the critical factors for initial and ongoing ERP implementation success is rare and fragmented. Through a comprehensive review of the literature, 11 factors were found to be critical to ERP implementation success – ERP teamwork and composition; change management program and culture; top management support; business plan and vision; business process reengineering with minimum customization; project management; monitoring and evaluation of performance; effective communication; software development, testing and troubleshooting; project champion; appropriate business and IT legacy systems. The classification of these factors into the respective phases (chartering, project, shakedown, onward and upward) in Markus and Tanis’ ERP life cycle model is presented and the importance of each factor is discussed.

Critical factors for successful implementation of enterprise systems

The critical success factors for ERP implementation: an organizational fit perspective

Enterprise resource planning (ERP) systems and other complex information systems represent critical organizational resources. For such systems, firms typically use consultants to aid in the implementation process. Client firms expect consultants to transfer their implementation knowledge to their employees so that they can contribute to successful implementations and learn to maintain the systems independent of the consultants. This study examines the antecedents of knowledge transfer in the context of such an interfirm complex information systems implementation environment. Drawing from the knowledge transfer, information systems, and communication literatures, an integrated theoretical model is developed that posits that knowledge transfer is influenced by knowledge-related, motivational, and communication-related factors. Data were collected from consultant-and-client matched-pair samples from 96 ERP implementation projects. Unlike most prior studies, a behavioral measure of knowledge transfer that incorporates the application of knowledge was used. The analysis suggests that all three groups of factors influence knowledge transfer, and provides support for 9 of the 13 hypotheses. The analysis also confirms two mediating relationships. These results (1) adapt prior research, primarily done in non-IS contexts, to the ERP implementation context, (2) enhance prior findings by confirming the significance of an antecedent that has previously shown mixed results, and (3) incorporate new IS-related constructs and measures in developing an integrated model that should be broadly applicable to the interfirm IS implementation context and other IS situations. Managerial and research implications are discussed.

https://www.jstor.org/stable/pdfplus/25148668.pdf

Antecedents of knowledge transfer from consultants to clients in enterprise system implementations

This paper reports on a comparative case study of 13 industrial firms that implemented an enterprise resource planning (ERP) system. It compares firms based on their dialectic learning process. All firms had to overcome knowledge barriers of two types: those associated with the configuration of the ERP package, and those associated with the assimilation of new work processes. We found that both strong core teams and carefully managed consulting relationships addressed configuration knowledge barriers. User training that included both technical and business processes, along with a phased implementation approach, helped firms to overcome assimilation knowledge barriers. However, all firms in this study experienced ongoing concerns with assimilation knowledge barriers, and we observed two different approaches to address them. In a piecemeal approach, firms concentrated on the technology first and deferred consideration of process changes. In a concerted approach, both the technology and process changes were undertaken together. Although most respondents clearly stated a preference for either piecemeal or concerted change, all firms engaged in practices that reflected a combination of these approaches.

Learning to Implement Enterprise Systems: An Exploratory Study of the Dialectics of Change

173 For some 20 years after John Dearden wrote these words, history proved him right. Today, however, there is a booming market for software packages claiming to provide a total, integrated solution to companies’ information-processing needs. Even companies that choose not to adopt such packages are pursuing aggressive strategies of systems integration by redeveloping custom software and adopting technologies such as data warehousing. Integrated enterprise systems deserve serious research attention because of their great potential for financial, technical, managerial, human, and strategic benefits, costs, and risks. This chapter provides a theoretical framework for analyzing, both retrospectively and prospectively, the business value of enterprise systems. We first describe the historical context in which enterprise systems emerged. Next we identify the key characteristics of enterprise systems, discuss the reasons companies do and do not adopt them, and summarize arguments about why enterprise systems are an important topic for research. We then analyze enterprise systems in terms of the concept of success. We argue that the many facets of success create difficulties for

/pdf/the-enterprise-system-experience-from-adoption-to-success-10l5kl8tae.pdf

The Enterprise System Experience— From Adoption to Success

Enterprise resource planning (ERP) packages touch many aspects of a company's internal and external operations. Consequently, successful deployment and use of ERP systems are critical to organizational performance and survival. This paper presents the results of a study of the problems and outcomes in ERP projects which was conducted under the sponsorship of an ERP systems vendor. Two basic research questions were addressed. First, how successful are companies at different points in time in their ERP experiences and how are different measures of success related? (That is, can early success be followed by failure and vice versa?) Second, what problems do ERP adopters encounter as they implement and deploy ERP and how are these problems related to outcomes? The findings showed that the success of ERP systems depends on when it is measured and that success at one point in time may only be loosely related to success at another point in time. Companies experience problems at all phases of the ERP system life cycle and many of the problems experienced in later phases originated earlier but remained unnoticed or uncorrected. These findings suggest that researchers and companies will do well to adopt broad definitions and multiple measures of success and pay particular attention to the early identification and correction of problems.

https://link.springer.com/content/pdf/10.1080%2F02683960010008944.pdf

Learning from Adopters’ Experiences with ERP: Problems Encountered and Success Achieved:

Multisite ERP Implementations.

H istorically, ERP systems evolved from MRP II systems, which are designed to manage a production facility’s orders, production plans, and inventories. ERP systems integrate inventory data with financial, sales, and human resources data, allowing organizations to price their products, produce financial statements, and manage the resources of people, materials, and money. Implementing ERP systems can be quite straightforward when organizations are simply structured and operate in one or a few locations. But when organizations are structurally complex and geographically dispersed, implementing ERP systems involves difficult, possibly unique, technical and managerial choices and challenges. The complexities of what are often called “multisite” ERP implementations are discussed here. Like all computer-based information systems, multisite ERP implementations can be analyzed in terms of levels or layers (logical versus physical, hardware versus software). At each level there are different choices to make and different criteria for evaluating the alternatives. However, the layers are interdependent: Choices at one level may limit the available choices or affect the performance of the system at another level. Therefore, organizations are generally advised to start planning multisite ERP implementations at the strategic level before proceeding to the technical (software and hardware) levels. In practice, however, the sheer size and scale of such implementations may encourage organizations to tackle the layers MULTISITE ERP IMPLEMENTATIONS

Cornelis Tanis

Papers

The Enterprise System Experience— From Adoption to Success

Learning from Adopters’ Experiences with ERP: Problems Encountered and Success Achieved:

Multisite ERP Implementations.

Enterprise resource planning: multisite ERP implementations

Second-Wave Enterprise Resource Planning Systems: Learning from Adopters' Experiences with ERP: Problems Encountered and Success Achieved