Guy G. Gable

What is ERP

Though enterprise resource planning (ERP) has gained some prominence in the information systems (IS) literature over the past few years and is a significant phenomenon in practice, through (a) historical analysis, (b) meta-analysis of representative IS literature, and (c) a survey of academic experts, we reveal dissenting views on the phenomenon. Given this diversity of perspectives, it is unlikely that at this stage a broadly agreed definition of ERP can be achieved. We thus seek to increase awareness of the issues and stimulate further discussion, with the ultimate aim being to: (1) aid communication amongst researchers and between researchers and practitioners; (2) inform development of teaching materials on ERP and related concepts in university curricula and in commercial education and training; and (3) aid communication amongst clients, consultants and vendors. Increased transparency of the ERP-concept within IS may also benefit other aligned fields of knowledge.

Factors and measures of business process modelling: model building through a multiple case study

Business process modelling has gained widespread acceptance as a valuable design and management technique for a variety of purposes. While there has been much research on process modelling techniques and corresponding tools, there has been little empirical research into the success factors of effective process modelling, and the post hoc evaluation of process modelling success. This paper reports on the first attempt to identify process modelling success factors and measures, as empirically evidenced in case studies of nine process modelling projects in three leading Australian organizations.

Knowledge Management Competence for Enterprise System Success

This study conceptualizes, operationalises and validates the concept of Knowledge Management Competence as a four-phase multidimensional formative index. Employing survey data from 310 respondents representing 27 organizations using the SAP Enterprise System Financial module, the study results demonstrate a large, significant, positive relationship between Knowledge Management Competence and Enterprise Systems Success (ES-success, as conceived by Gable et al., 2008); suggesting important implications for practice. Strong evidence of the validity of Knowledge Management Competence as conceived and operationalised, too suggests potential from future research evaluating its relationships with possible antecedents and consequences.

Consultant engagement for computer system selection: a pro-active client role in small businesses

Abstract Because of their limited number of senior positions and fewer alternative career paths, small businesses have a more difficult time attracting and retaining skilled information systems (IS) staff and are thus dependent upon external expertise. Small businesses are particularly dependent on outside expertise when first computerizing. Because small businesses suffer from severe financial constraints, it is often difficult to justify the cost of custom software. Hence, for many small businesses, engaging a consultant to help with identifying suitable packaged software and related hardware, is their first critical step toward computerization. This study explores the importance of pro-active client involvement when engaging a consultant to assist with computer system selection in small businesses. Client involvement throughout consultant engagement is found to be integral to project success and frequently lacking due to mis-conceptions of small businesses regarding their role. Small businesses often overestimate the impact of consultant and vendor support in achieving succesful computer system selection and implementation. For consultant engagement to be successful, the process must be viewed as being directed toward the achievement of specific organizational results where the client accepts responsibility for direction of the process.

Strategic information systems research: An archival analysis

The Journal of Strategic Information Systems (JSIS) has been an international outlet for Information Systems research that focuses on strategic issues since 1991. This paper reports on an analysis of the research published in JSIS to date. The paper presents a preliminary classification system for research topics related to Strategic Information Systems into which all 316 JSIS research papers as at end 2009 are classified. Discussion on changing emphases in topics over time is provided, in the context of the editorial philosophy of the journal. The paper seeks to stimulate discussion on future directions for research in Strategic Information Systems.

An ERP maintenance model

Enterprise resource planning (ERP) maintenance and upgrade activities are receiving much attention in ERP-using organizations. Annual maintenance costs approximate 25% of initial ERP implementation costs, and upgrade costs as much as 25-33% of the initial ERP implementation. Still, the area of ERP maintenance and upgrade is relatively new and understudied as compared to ERP implementation issues. Many organizations lack experience and expertise in managing ERP maintenance and upgrade effectively. This situation is not helped by the lack of a standard ERP maintenance model that could provide practitioners with guidelines on planning, implementing and upgrading an ERP. Although software maintenance model standards exist, they have been found in a recent study to be insufficient for ERP maintenance and upgrade processes. In order to bridge this gap in literature and practice, this study proposes a preliminary ERP maintenance model, reflecting fundamental ERP maintenance and upgrade activities. A detailed case study was conducted to gather empirical data for developing such an ERP maintenance model. Data analysis identified (potential) benefits of the maintenance model to ERP-using organizations generally, and to the case firm in particular.

Large packaged application software maintenance: a research framework

This paper seeks to stimulate research on large application package software maintenance by presenting a tentative framework for future research in the area, partially instantiating that framework with examples from the papers in this special issue of the Journal of Software Maintenance and Evolution, highlighting other specific areas of research need and neglect, and posing a long list of related research questions. The user-organization-centric research framework captures relevant and interacting factors that can impact maintenance strategy, including software-source, support-source, and organizational and environmental contexts. These are viewed from the perspectives of four key stakeholders in the new distributed maintenance arrangement. In addition to the user-organization, stakeholders include the software vendor, third-party service providers, and society. Key messages from the paper include: maintenance generates benefits as well as costs; all stakeholders must have a lifecycle-wide view of maintenance costs and benefits; there is value in understanding all stakeholder perspectives; various software and related support sourcing alternatives have substantial maintenance incidence implications (incidence of costs, benefits, and responsibilities); and maintenance knowledge sourcing decisions should be made in the light of lifecycle-wide maintenance knowledge requirements.

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.

A design science research roadmap

This paper proposes and synthesizes from previous design science (DS) methodological literature a structured and detailed DS Roadmap for the conduct of DS research. The Roadmap is a general guide for researchers to carry out DS research by suggesting reasonably detailed activities. Though highly tentative, it is believed the Roadmap usefully inter-relates many otherwise seemingly disparate, overlapping or conflicting concepts. It is hoped the DS Roadmap will aid in the planning, execution and communication of DS research, while also attracting constructive criticism, improvements and extensions. A key distinction of the Roadmap from other DS research methods is its breadth of coverage of DS research aspects and activities; its detail and scope. We demonstrate and evaluate the Roadmap by presenting two case studies in terms of the DS Roadmap.

A Comparative Analysis of Major ERP Life Cycle 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.