Mapping factors influencing EAI adoption in the local government authorities on different phases of the adoption lifecycle

Abstract

Several private and public organisations have adopted Enterprise Application Integration (EAI), however, its application in the Local Government Authorities (LGAs) is limited. Although, there exist few EAI adoption models, these models mainly focus on a number of different factors (e.g. benefits, barriers, cost) influencing the decision making process for EAI adoption. Moreover, these models do not illustrate which factor(s) influence the decision making process for EAI adoption on the adoption lifecycle phases. Literature indicates that the adoption process involves a sequence of phases an organisation passes through before taking the decision for adoption. This exemplifies that LGAs may also have to pass through several adoption phases before taking the decision to adopt EAI. However, due to the: (a) multiplicity of diverse EAI adoption factors and (b) not able to recognise which factor(s) influence EAI on adoption lifecycle phases, it may not be easy for LGAs to take decisions to adopt EAI by merely focusing on different factors. This may impede the decision making process for EAI adoption in LGAs. Notwithstanding, the implications of EAI have yet to be assessed, leaving scope for timeliness and novel research. Therefore, it is of high importance to investigate this area within LGAs and result in research that contributes towards successful EAI adoption. This paper makes a step forward as it: (a) investigates and proposes four adoption lifecycle phases, (b) validates the adoption lifecycle phases and (c) mapping the factors influencing EAI adoption on the adoption lifecycle phases, through a case study. Hence, it significantly contributes to the body of knowledge and practice. In doing so, providing sufficient support to the decision makers for speeding up the decision making process for EAI adoption in LGAs.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 9 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.