Incorporating Technology Acceptance and IS Success Frameworks into a System Dynamics Conceptual Model: A Case Study in the ERP Post-Implementation Environment

Incorporating Technology Acceptance and IS Success Frameworks into a System Dynamics Conceptual Model: A Case Study in the ERP Post-Implementation Environment

Meg Fryling
Copyright: © 2012 |Pages: 16
DOI: 10.4018/jitsa.2012070103
OnDemand:
(Individual Articles)
Available
$37.50
Current Special Offers
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Like any IT project, the intricacy of Enterprise Resource Planning (ERP) implementations brings with it high risks to the organization because of high upfront costs and low success rates. ERP implementations are not simply software installations but a radical integration and transformation of an organization’s business practices. System acceptance and perceptions of success weight heavily on non-technical forces such as people, processes, policies, and organizational culture. This study employs system dynamics techniques to elicit perceptions regarding system acceptance and success in an ERP post-implementation case study setting. A conceptual model was developed based on various literature streams and structure validation was conducted with ERP experts via semi-structured interviews. The resulting model includes technology acceptance and information system success model concepts as well as theories from related literature. Interview findings and methodology reflections are also discussed in this paper.
Article Preview
Top

Literature Review

There are unique implications to technology acceptance and information system (IS) success concepts in the ERP environment because the software is implemented by a team comprised of both technical and functional participants (Frantz, Southerland, & Johnson, 2002). Since ERP systems are very different from home-grown legacy information systems and they have their own unique challenges with regard to user acceptance and IS success. Unlike information systems of the past, ERP requires technical and functional communication, collaboration, and active project participation (Appleton, 1997).

Complete Article List

Search this Journal:
Reset
Volume 17: 1 Issue (2024)
Volume 16: 3 Issues (2023)
Volume 15: 3 Issues (2022)
Volume 14: 2 Issues (2021)
Volume 13: 2 Issues (2020)
Volume 12: 2 Issues (2019)
Volume 11: 2 Issues (2018)
Volume 10: 2 Issues (2017)
Volume 9: 2 Issues (2016)
Volume 8: 2 Issues (2015)
Volume 7: 2 Issues (2014)
Volume 6: 2 Issues (2013)
Volume 5: 2 Issues (2012)
Volume 4: 2 Issues (2011)
Volume 3: 2 Issues (2010)
Volume 2: 2 Issues (2009)
Volume 1: 2 Issues (2008)
View Complete Journal Contents Listing