Determinants of SaaS ERP Systems Adoption

ERP systems are now offered on the cloud under Software as a Service (SaaS) model. For small and medium sized enterprises (SMEs), this is considered the best opportunity to take advantage of the capabilities of an Enterprise Resource Planning (ERP) system without the investment and management costs associated with the on-premise model. This study investigates the factors influencing the adoption of SaaS ERP system by SMEs. Using a cross-sectional field study conducted across four major case study organizations and software vendors, this study identifies the determinants for the adoption decision and analyses benefits and challenges. According to study, low total cost of ownership, low initial investment costs, potential willingness of the vendor to participate in co-creation of value for customers, continuous improvement of the product offerings and generic benefits of implementing an integrated ERP system are determinants of SaaS ERP adoption decisions by SMEs. Competitive pressures faced by the enterprise, external factors, concerns on the security and integrity of data have no influence on adoption decision, according to this study. Instead, SaaS ERP vendor’s long term reputation, promised shorter deployment time, total cost of ownership, willingness to listen and continuously improve the product, vendor’s ability and willingness to support customers throughout the product life cycle are the factors that would attract SMEs towards SaaS ERP systems

Strategic Predictors of Successful Enterprise Systems Deployment

Purpose The delivered wisdom to date has enterprise system purchase and implementation as one of the most hazardous projects any organization can undertake. The aim was to reduce this risk by both theoretically and empirically finding those key predictors of a successful enterprise system deployment. Design/methodology/approach A representative sample of 60 firms drawn from the Fortune 1000 that had recently (1999-2000) adopted enterprise resource planning (ERP) systems was used to test a model of adoption performance with significant results. Findings Leadership (social learning theory), business process re-engineering (change the company not the technology) and acquisition strategy (buy, do not make) were found to be significant predictors of adoption performance (final model R 2=43 percent, F=5.5, pp Originality/value The “four factor” model we validate is a robust predictor of ERP adoption success and can be used by any organization to audit plans and progress for this undertaking

Strategic Predictors of Successful Enterprise Systems Deployment

Purpose The delivered wisdom to date has enterprise system purchase and implementation as one of the most hazardous projects any organization can undertake. The aim was to reduce this risk by both theoretically and empirically finding those key predictors of a successful enterprise system deployment. Design/methodology/approach A representative sample of 60 firms drawn from the Fortune 1000 that had recently (1999-2000) adopted enterprise resource planning (ERP) systems was used to test a model of adoption performance with significant results. Findings Leadership (social learning theory), business process re-engineering (change the company not the technology) and acquisition strategy (buy, do not make) were found to be significant predictors of adoption performance (final model R 2=43 percent, F=5.5, pp Originality/value The “four factor” model we validate is a robust predictor of ERP adoption success and can be used by any organization to audit plans and progress for this undertaking

Enterpise resource planning deplozment guide

The deployment of an Enterprise Resource Planning system (briefly ERP) is a global project, of strategic importance for the companies. It is equally a project for the reorganization of the business processes. A guide for the deployment involves all that is necessary for the counseling for the start up of an ERP system: conceptual matters, basic rules, managers' expectations, success factors, associated risks and good practices.enterprise resource planning systems (ERP), ERP deployment, success factors, basic rules, ERP deployment associated risks, best practices

An Empirical Study of Operational Performance Parity Following Enterprise System Deployment

This paper presents an empirical investigation into whether the implementation of packaged Enterprise Systems (ES) leads to parity in operational performance. Performance change and parity in operational performance are investigated in three geographically defined operating regions of a single firm. Order lead time, the elapsed time between receipt of an order and shipment to a customer, is used as a measure of operational performance. A single ES installation was deployed across all regions of the subject firm\u27s operations.Findings illustrate parity as an immediate consequence of ES deployment. However, differences in rates of performance improvement following deployment eventually result in significant (albeit smaller than pre-deployment) performance differences. An additional consequence of deployment seems to be an increased synchronization of performance across the formerly independent regions

Linking design and manufacturing domains via web-based and enterprise integration technologies

The manufacturing industry faces many challenges such as reducing time-to-market and cutting costs. In order to meet these increasing demands, effective methods are need to support the early product development stages by bridging the gap of communicating early design ideas and the evaluation of manufacturing performance. This paper introduces methods of linking design and manufacturing domains using disparate technologies. The combined technologies include knowledge management supporting for product lifecycle management (PLM) systems, enterprise resource planning (ERP) systems, aggregate process planning systems, workflow management and data exchange formats. A case study has been used to demonstrate the use of these technologies, illustrated by adding manufacturing knowledge to generate alternative early process plan which are in turn used by an ERP system to obtain and optimise a rough-cut capacity plan

Model-driven Enterprise Systems Configuration

Enterprise Systems potentially lead to significant efficiency gains but require a well-conducted configuration process. A promising idea to manage and simplify the configuration process is based on the premise of using reference models for this task. Our paper continues along this idea and delivers a two-fold contribution: first, we present a generic process for the task of model-driven Enterprise Systems configuration including the steps of (a) Specification of configurable reference models, (b) Configuration of configurable reference models, (c) Transformation of configured reference models to regular build time models, (d) Deployment of the generated build time models, (e) Controlling of implementation models to provide input to the configuration, and (f) Consolidation of implementation models to provide input to reference model specification. We discuss inputs and outputs as well as the involvement of different roles and validation mechanisms. Second, we present an instantiation case of this generic process for Enterprise Systems configuration based on Configurable EPCs

ERP project’s internal stakeholder network and how it influences the project’s outcome

So far little effort has been put into researching the importance of internal ERP project stakeholders’ mutual interactions, realizing the project’s complexity, influence on the whole organization, and high risk for a useful final outcome. This research analyzes the stakeholders’ interactions and positions in the project network, their criticality, potential bottlenecks and conflicts. The main methods used are Social Network Analysis, and the elicitation of drivers for the individual players. Information was collected from several stakeholders from three large ERP projects all in global companies headquartered in Finland,together with representatives from two different ERP vendors, and with two experienced ERP consultants. The analysis gives quantitative as well as qualitative characterization of stakeholder criticality (mostly the Project Manager(s), the Business Owner(s) and the Process Owner(s)) , degree of centrality, closeness , mediating or bottleneck roles, relational ties and conflicts (individual, besides those between business and project organizations) , and clique formations. A generic internal stakeholder network model is established as well as the criticality of the project phases. The results are summarized in the form of a list of recommendations for future ERP projects to address the internal stakeholder impacts .Project management should utilize the latest technology to provide tools to increase the interaction between the stakeholders and to monitor the strength of these relations. Social network analysis tools could be used in the projects to visualize the stakeholder relations in order to better understand the possible risks related to the relations (or lack of them).ERP; Social networks ; Enterprise resource planning; Stakeholders