A hiccup or a rift? ERP implementation success in Jordan

Like many other developing countries, Jordan is adopting Enterprise Resource Planning (ERP) systems in both its public and private sectors. Jordan's emerging private sector has historically close ties to the public sector, though a global market orientation requires a shift in its organisational culture. ERPs however embed business processes which do not necessarily fit with traditional cultural practices, and implementation success is not assured.. This study looks at the perceptions of both public and private sector ERP implementations in Jordan and assesses these on various measures of success. There were few differences between public and private sectors, but the benefits actually realized in Jordanian ERPs fell short of claims made for the technology in other cultures. Considerable customisation was required in both sectors, and the traditional style of management in Jordan did not fit well with the requirements for successful implementation. This is consistent with recent studies from various countries that show cultural fit is a particularly neglected factor in assessing ERP success.

A critical success factors model for ERP implementation

An effective IT infrastructure can support a business vision and strategy; a poor, decentralized one can break a company. More and more companies are turning to off-the-shelf ERP (enterprise resource planning) solutions for IT planning and legacy systems management. The authors have developed a framework to help managers successfully plan and implement an ERP project

Identifying critical success factors of ERP Systems at the higher education sector

In response to a range of contextual drivers, the worldwide adoption of ERP Systems in Higher Education Institutions (HEIs) has increased substantially over the past decade. Though the difficulties and high failure rate in implementing ERP systems at university environments have been cited in the literature, research on critical success factors (CSFs) for ERP implementations in this context is rare and fragmented. This paper is part of a larger research effort that aims to contribute to understanding the phenomenon of ERP implementations and evaluations in HEIs in the Australasian region; it identifies, previously reported, critical success factors (CSFs) in relation to ERP system implementations and discusses the importance of these factors.

A critical success factors model for enterprise resource planning implementation

Enterprise Resource Planning (ERP) systems are integrated enterprise-wide standard information systems that automate all aspects of an organisations’ business processes. The ERP philosophy is that business systems incorporating sales, marketing, manufacturing, distribution, personnel and finance modules can be supported by a single integrated system with all of the company’s data captured in a central database. The ERP packages of vendors such as SAP, Baan, J.D. Edwards and Intentia represent more than a common systems platform for a business. They prescribe information blueprints of how organisation’s business processes should operate. In this paper, the scale and strategic importance of ERP systems is identified and the problem of ERP implementation is defined. Five company examples are analysed using a Critical Success Factors (CSFs) theoretical framework. The paper offers a framework for managers which provides the basis for developing an ERP implementation strategy. The case analysis identifies different approaches to ERP implementation, highlights the critical role of legacy systems in influencing the implementation process, and identifies the importance of business process change and software configuration in addition to factors already cited in the literature such as top management support and communication. The implications of the results and future research opportunities are outlined.

The waves in business transformation management: a conceptualization of how IT-enabled Business Transformations Unfold

We examine IT-enabled Business Transformations (ITBT) based on three case studies of successful, multi-year ERP implementation programs. Given the inconsistencies in segmenting the different key periods in ITBTs in both literature and our cases, we sought to consolidate the common events or critical incidents in such initiatives. We label those key periods as waves, and the emergence of triggers and reactions thereunto in the management of business transformations. We show that business transformations unfold in four distinct waves: Wave 1 Concept Development, Wave 2 Blueprint Design, Wave 3 Solution Delivery and Wave 4 Post-Transformation. These waves are characterized by the occurrence of strategic- and program-level triggers to which organizations respond by invoking different management services. Our interpretive research provides a new conceptualization of ITBTs based on a service-oriented view of such initiatives. This view draws attention to managerial capabilities as a service to transformations, and how and when these capabilities are required to respond to triggering incidents. We outline propositions and recommendations for business transformation management.

A comparative analysis of major ERP lifecycle implementation, management and support issues in Queensland Government

This paper reports on a study of ERP lifecycle major issues from the perspectives of individuals with substantial and diverse involvement with SAP Financials in Queensland Government. A survey was conducted of 117 ERP system project participants in five closely related state government agencies. A modified Delphi technique identified, rationalized and weighed perceived major issues in ongoing ERP life cycle implementation, management and support. The five agencies each implemented SAP Financials simultaneously using a common implementation partner. The three survey rounds of the Delphi technique, together with coding and synthesizing procedures, resulted in a set of 10 major issue categories with 38 sub-issues. Relative scores of issue importance are compared across government agencies, roles (client vs implementation partner) and organizational levels (strategic, technical and operational). Study findings confirm the importance of this finer partitioning of the data, and distinctions identified reflect the circumstances of ERP lifecycle implementation, management and support among the stakeholder groups. The study findings should also be of interest to stakeholders who seek to better understand the issues surrounding ERP systems and to better realise the benefits of ERP.

The impact of organisational culture on ERP systems implementation : lessons from Jordan

Jordan is adopting Enterprise Resource Planning (ERP) systems in both its public and private sectors. Jordan's emerging private sector has historically close ties to the public sector; though a global market orientation requires a shift in its organisational culture. ERPs however embed business processes which do not necessarily fit with traditional cultural practices, and implementation success is not assured. This study looks at the perceptions of both public and private sector ERP implementations in Jordan and assesses these on various measures of success. There were few differences between public and private sectors, but the benefits actually realised in Jordanian ERPs fell short of claims made for the technology in other cultures.

ERP systems implementation and organizational culture : the case of Jordan

Jordan is adopting Enterprise Resource Planning (ERP) systems in both its public and private sectors. Jordan's emerging private sector has historically close ties to the public sector; though a global market orientation requires a shift in its organizational culture. ERPs however embed business processes which do not necessarily fit with traditional cultural practices, and implementation success is not assured. This study looks at the perceptions of both public and private sector ERP implementations in Jordan and assesses these on various measures of success. There were few differences between public and private sectors, but the benefits actually realized in Jordanian ERPs fell short of claims made for the technology in other cultures.

Maintaining ERP packaged software : a revelatory case study

For many organizations, maintaining and upgrading enterprise resource planning (ERP) systems (large packaged application software) is often far more costly than the initial implementation. Systematic planning and knowledge of the fundamental maintenance processes and maintenance-related management data are required in order to effectively and efficiently administer maintenance activities. This paper reports a revelatory case study of Government Services Provider (GSP), a high-performing ERP service provider to government agencies in Australia. GSP ERP maintenance-process and maintenance-data standards are compared with the IEEE/EIA 12207 software engineering standard for custom software, also drawing upon published research, to identify how practices in the ERP context diverge from the IEEE standard. While the results show that many best practices reflected in the IEEE standard have broad relevance to software generally, divergent practices in the ERP context necessitate a shift in management focus, additional responsibilities, and different maintenance decision criteria. Study findings may provide useful guidance to practitioners, as well as input to the IEEE and other related standards.

Fraud detection in ERP systems using scenario matching

ERP systems generally implement controls to prevent certain common kinds of fraud. In addition however, there is an imperative need for detection of more sophisticated patterns of fraudulent activity as evidenced by the legal requirement for company audits and the common incidence of fraud. This paper describes the design and implementation of a framework for detecting patterns of fraudulent activity in ERP systems. We include the description of six fraud scenarios and the process of specifying and detecting the occurrence of those scenarios in ERP user log data using the prototype software which we have developed. The test results for detecting these scenarios in log data have been verified and confirm the success of our approach which can be generalized to ERP systems in general.

Going beyond ‘misfit’ as a reason for ERP package customisation

In an attempt to deal with the potential problems presented by existing information systems, a shift towards the implementation of ERP packages has been witnessed. The common view, particularly the one espoused by vendors, is that ERP packages are most successfully implemented when the standard model is adopted. Yet, despite this, customisation activity still occurs reportedly due to misalignment between the functionality of the package and the requirements of those in the implementing organisation. However, it is recognised that systems development and organisational decision-making are activities influenced by the perspectives of the various groups and individuals involved in the process. Thus, as customisation can be seen as part of systems development, and has to be decided upon, it should be thought about in the same way. In this study, two ERP projects are used to examine different reasons why customisation might take place. These reasons are then built upon through reference to the ERP and more general packaged software literature. The study suggests that whilst a common reason for customising ERP packages might be concerned with functionality misfits, it is important to look further into why these may occur, as there are clearly other reasons for customisation stemming from the multiplicity of social groups involved in the process.

Efficiency of knowledge integration in enterprise systems implementation

Recent literature has emphasized the pivotal role of knowledge integration in Enterprise Systems (ES) success. This research-in-progress paper, building upon Knowledge Based Theory of the firm (KBT), examines the efficiency of knowledge integration in the context of ES implementation and identifies the factors contributing to its enhancement. The proposed model in this paper suggests that the efficiency of knowledge integration in an ES implementation process depends upon the level of common knowledge and the level of coordination in the ES adopting organization. It further suggests that the level of common knowledge can be enhanced by proper training, improving ES users’intrinsic and extrinsic motivations and business process modeling and the level of coordination can be improved by articulating a clear unified organizational goal for the ES adoption in the organization, forming a competent ES team, enhancing interdepartmental communication and the cross-functionality in the organization structure.