1 Przemysław Lech * Enterprise System Assimilation: phases, activities, and outcomes Introduction Enterprise systems (ES) are the backbone of most global manufacturing and service enterprises [Muscatello, Chen, 2008] and they continue to draw attention of the researchers [e.g., Hasan M. et al., 2011, Sammon, Adam, 2010; Silva, Fulk, 2012]. Enterprise Systems (ES) were formerly identified with Enterprise Resource Planning (ERP) applications [Sedera, Gable, 2010]. Rosemann  defines an ERP system as a customizable, standard application software which includes integrated business solutions for the core processes (e.g., production planning and control, warehouse management) and the main administrative functions (e.g., accounting, human resource management) of an enterprise. These systems have later evolved into even more sophisticated application suites, including, besides ERP, also Customer Relationship Management (CRM), Business Intelligence, Workflow Management, Content Management and other functionalities, which are required to support information and workflow in organizations. Generalizing the above definition, one can state that an Enterprise System is a standard, customizable application suite that includes integrated business solutions for the major business processes of an enterprise, with the ERP system remaining the central component of this suite. Though Enterprise Systems are among the most popular pieces of business software, enterprises around the globe are still facing problems while adopting them [Aloini et al., 2007; Wu et al., 2007]. Most of the research has therefore concentrated on the Enterprise Systems implementation success/failure factors [e.g., Dezdar, Sulaiman, 2009; Soja, Paliwoda-Pękosz, 2009]. Another important aspect, i.e. implementation process/methodology is omitted in the research since the early 2000 s. The aim of this paper is to examine the assimilation process of a big Enterprise System, basing on two case studies of SAP assimilation in Polish organizations. The phases of the * Prof. UG, Ph.D., hab., Department of Accounting, Faculty of Management, University of Gdańsk, Poland,
2 30 Przemysław Lech assimilation process will be determined, followed by activities, performed in each of the phase as well as resulting outcomes. 1. Enterprise Systems assimilation literature review The assimilation of an IT may be defined as: the process of acquisition and deployment of the IT in an organization [Bajwa et al., 2004]. The general IT assimilation model is presented in [Kwon, Zmud, 1987] and later altered in [Zmud, Apple, 1992]. It divides the IT assimilation process into six stages: 1. Initiation when a match is found between an IT solution and its application in the organization. 2. Adoption when a decision is reached to invest in an IT solution. 3. Adaptation during which the IT application is developed, installed and maintained. 4. Acceptance when the application is employed in organizational work. 5. Routinization the IT solution is perceived as something ordinary. 6. Infusion when increase in effectiveness is observed due to IT application usage in a more comprehensive manner. The first two stages represent the pre-implementation phase of the project, the two middle ones: implementation itself, while the last two: the post-implementation phase of IT assimilation. Regarding the assimilation process of a specific piece of business software, which is Enterprise Systems, and their predecessors Enterprise Resource Planning systems, the brief summary of early work is presented in Parr and Shanks . Basing on the previous research these authors propose an ERP assimilation model which comprises of three general phases: 1. Planning phase which includes the selection of an ERP, assembly of a steering committee, determination of high-level project scope and broad implementation approach, selection of a project team manager and resource determination; 2. Project phase which extends from the identification of ERP modules through to installation and cut-over; 3. Enhancement phase which includes the stages of system repair, extension and transformation. This approach is consistent with the view of Zmud and Apple, presented above in such a sense, that the assimilation process is divided into three
3 Enterprise System Assimilation: phases, activities, and outcomes 31 main sub-phases. Ahutiv et al.  make a proposal of four-stage ERP implementation process: Selection, Definition, Implementation and Operation. Bajwa et al.  altered this model by adding Awareness as the first stage and renaming Definition into Preparation. Ehie and Madsen (2005) concentrate on the project part of the assimilation and make a proposal of five stage model, i.e.: Project Preparation, Business Blueprint, Realization, Final Preparation, Go-Live and Support. The phases naming is consistent with that presented by SAP in ASAP implementation methodology, but the content of each phase differs. For example Ehie and Madsen suggest that Business Blueprint is the base of the system selection, whereas ASAP focuses on the implementation of already chosen system (SAP). Brief description of ASAP phases can be found in Esteves et al. . As ASAP is an ES project methodology, it takes the stance of a consulting enterprise, implementing the system, not the client. Thus the last activity is support of the operation, not operation itself. Comparing to the model of Bajwa et al., ASAP has both preparation and definition (business blueprint) phases and separates the final preparation from the implementation phase. Ehie and Madsen recognize the awareness phase which precedes the project by stating that: These phases are preceded by a critical look at a company s strategic enterprise architecture and surrounded by change management and business development components. Generalizing the above one can state that the assimilation process consists of three main phases, with different possible divisions into subphases: 1. Pre-implementation (planning) phase which includes building awareness of the necessity to invest in an ES, system selection, and definition of high-level project scope, schedule and budget. 2. Implementation (project) phase which involves detailed project planning, implementation of the system, and activities necessary to launch the new system; 3. Post-implementation (operation/enhancement) phase which involves system stabilization after go-live, its day-to-day use, as well as necessary repairs and enhancements. The assimilation process may be better understood by the examination of detailed activities, summarized in Table 1.
4 32 Przemysław Lech Table 1. Enterprise System Assimilation activities and outcomes Ahutiv et al.  Bajwa et al.  Ehie and Madsen  Esteves et al.  - Awareness: Evaluation of current situation Gathering facts and information to identifying reasons to change Pre-project: Driving implementation motive, Critical evaluation of internal/external aspects - Selection: Collection of information about the systems and implementations Needs analysis Collection of information about technological infrastructure Contract signing Design: Definition of scope Establishing implementation teams and timetables Training of the implementation teams Initial implementation of the system Selection: Definition of project objectives Collection of vendor consultant information Needs analysis Evaluation of vendor and consultant alternatives Evaluation of IT infrastructure Feasibility study Finalizing contracts Preparation: Definition of scope Establishment of implementation teams and timetables Training of implementation teams Initial prototyping Determination of implementation approach - - Project Preparation: Determination of project Steering Committee and team, Definition of scope, Creation of detailed project plan, Determination of responsibilities Project Preparation: Definition of project objectives and scope, Preparation of project plan, Definition of project team
5 Enterprise System Assimilation: phases, activities, and outcomes 33 Ahutiv et al.  Bajwa et al.  Implementation: Gap analysis, Business process reengineering, Identification of complementary solutions, Construction of prototype, Data conversion, Definition of work procedures, Full implementation of the system Training of users, Acceptance tests Operation: Establishing of support centers, Performance of changes and enhancements, Upgrading the system, System audit, Implementation: Detailed gap analysis, Business process reengineering, Identification of complementary solutions, Construction of prototype, Data conversion, Clarity of work procedures, Full implementation, User training, Acceptance tests, Operation: System use, Maintenance, Business integration Ehie and Madsen  Business Blueprint: Analysis of current business processes, Education on ERP systems, System selection, Education on a selected system: functionality and configuration, New processes design, Realization: Technical development: modifications, interfaces, data conversion, Prototyping and adjustments towards the final system Final preparation: Tuning and testing, Training Go-live and support: Bring ERP modules live, Improve and expand ERP system continually Esteves et al.  Business Blueprint: Detailed documentation of the organizational structure and business processess, Scope adjustment Realization: System configuration, Final preparation: Testing, User training, Cut over activities Go-live and support: Move from preproduction to production environment, Support organization set up for end-users,
6 34 Przemysław Lech Ahutiv et al.  Bajwa et al.  System termination Source: In the lead row. Ehie and Madsen  Esteves et al.  System performance improvement The assimilation process variants, derived from the literature will be now compared with the results of the 2 case studies of SAP implementation projects. 2. Case study 2.1. Research design A multiple case study was chosen as the research method. The unit of analysis was the assimilation process of an Enterprise System - SAP. Two cases were selected, differing in the circumstances of and approach to the system selection as well as in the implementation partner, conducting the implementation. The primary data collection method was analysis of the documentation, including project charters, blueprints, meeting minutes, schedules and protocols. The research questions posed were the following: RQ1: What were the phases of the assimilation process? RQ2: What activities were done in each of the phases and what where their outcome? 2.2. Case study results Company 1 Company 1 was free to choose any enterprise system available on the market. The reasons for the decision to change the legacy systems are not known to the researcher, as the available documentation starts from the selection process. Therefore the process of building awareness of the necessity to invest cannot be assessed in this study. After the company decided to change the system, a selection process was launched. An external consulting company was hired to facilitate this process. A three month selection project was launched, consisting of the following activities: 1. Business process analysis and modelling; current systems audit. 2. Requirements analysis and specification.
7 Enterprise System Assimilation: phases, activities, and outcomes High level gap-fit analysis of the systems on the market; creation of the short list; preparation of high level schedule; preparation of the request for proposal. The outcomes of this phase were the following: 1. Business processes map, 2. Requirements specification document, 3. Request for proposal, 4. Short list of Enterprise Systems that matched the requirements, 5. High level project schedule and budget. As a result, the SAP system was chosen as the optimal match for the company s requirements. The second stage was contract negotiations regarding both licence agreement with the vendor and implementation contract with the implementing consulting company. The requirements specification document, produced in the preceding phase was used as a basis for the scope definition in the implementation contract. Basing on that scope budget and schedule were defined and included in the contract. After the contract was signed, the implementation phase begun. It consisted of five stages, according to the ASAP methodology: 1. Project preparation with Project Charter being the main product. The Project Charter included: a. project scope and schedule (repeated from the contract), b. project organization, together with assignment of people to the organizational units (Steering Committee, Project Management Team, Implementation Teams for each functional area, consisting of key users and consultants), c. roles definition and split between the parties (client company and consulting company), d. project procedures: communication procedures, document templates, integration meetings general plan, work reporting by the consultants, e. description of the technical infrastructure of the project. 2. Business Blueprint phase during which a detailed analysis of business processes and requirements was made by functional consultants, who later designed the way these requirements would be reflected in the system. It consisted of analytical workshops, during which consultants interviewed business process owners and keyusers with regards to the detailed functional requirements. Basing on
8 36 Przemysław Lech that knowledge consultants prepared the system design. The result was a Business Blueprint document, containing specification of system configuration, master data, extensions, reports, forms and interfaces. Business Blueprint was a basis for configuration and programming work. 3. Realization - during that stage the system was actually configured, according to the design from the Business Blueprint, master data was prepared for migration from legacy systems and all needed programming work, regarding extensions, reports, interfaces and forms was performed. The outcome of this stage was the system ready for testing and end-user training. 4. Productive start preparation during that phase the system was tested and errors were corrected. All the configuration was transported to the productive system (from the development system through the test system). Master data were migrated to the productive system and key-users were trained. The product of this stage was system ready for go-live. 5. Go-live and support the system was launched productively. Consultants supported the users in their day-to-day activities and first month-end closing. All errors encountered in normal system usage were corrected. After that phase, the maintenance agreement was signed between the parties so that corrections and improvements could be made on a daily basis Company 2 The system change in Company 2 was imposed by the international holding of which it was part of. The company top management was however convinced that the change is necessary due to company growth which could not be supported by the current system any more. As the system was selected on the holding level, company 2 did not have to run the system selection process, however it was free to choose the implementation partner and had to negotiate the implementation contract with regards to detailed scope, budget and schedule. The implementation partner was pre-selected basing on the geographical proximity and informal research regarding the reliability of the companies available on the market. After that, the negotiations regarding project scope, budget and schedule took place. The implementation partner claimed that for the preparation of the fixed-price offer an analysis of requirements is needed.
9 Enterprise System Assimilation: phases, activities, and outcomes 37 Therefore a one-month analytical project was launched to prepare the requirements specification. Basing on that specification scope, budget and schedule was determined and contract signed. Although project 2 was led by a different consulting company, the project phases, together with activities and outcomes were exactly the same as in case Summary of the case study The two cases presented above differed with regards to the preimplementation phase due to different initial conditions, and were similar with regards to the implementation phase. The post-implementation phase was not examined in detail: both projects went-live and the systems were supported according to the maintenance agreement but no detailed analysis could be made for that phase on the basis of available documentation. The phases and activities were the following: 1. Pre-implementation (planning) phase, which included: Identification of the need for change (awareness): both companies were aware that the system had to be changed due to business reasons. However the process of identification could not be analysed basing on the available data sources, Analysis of business processes and requirements: which resulted in the definition of project scope for the system selection purposes in company 1. Company 2 did not perform this step as the system was imposed by the holding company. System selection: in company 1. Company 2 did not perform this step as the system was imposed by the holding company. Implementation partner selection: both companies run a process of preliminary selection of the implementation partner. Scope/schedule/budget determination - implementation contract preparation: both companies negotiated the contract with the implementation partner. Company 1 used the scope definition from the system selection phase as the starting point. Company 2 launched an analysis workshop on that stage to determine the scope of the implementation. Basing on the scope, the budget and schedule was determined in both companies and included in the implementation contract. 2. Implementation (project) phase, which consisted of the following stages:
10 38 Przemysław Lech 1) Project preparation with Project Charter being the main product. The Project Charter defined: project scope and schedule (repeated from the contract), project organization, together with assignment of people to the organizational units (Steering Committee, Project Management Team, Implementation Teams for each functional area, consisting of key users and consultants), roles definition and split between the parties (client company and consulting company), project procedures: communication procedures, document templates, integration meetings general plan, work reporting by the consultants, description of the technical infrastructure of the project. 2) Business Blueprint which resulted in the project design (Business Blueprint document), containing specification of system configuration, master data, extensions, reports, forms and interfaces. 3) Realization - during which the system was actually configured, according to the design from the Business Blueprint, master data was prepared for migration from legacy systems and all needed programming work, regarding extensions, reports, interfaces and forms was performed. 4) Productive start preparation during which the system was tested and errors were corrected. Master data were migrated to the productive system and key-users were trained. The product of this stage was system ready for go-live. 5) Go-live and support the system was launched productively and the system entered the post-implementation phase. 3. Post-implementation (operation/enhancement) phase: which involves system stabilization after go-live and its day-to-day use. This phase was not analysed in detail. Conclusion This paper presented the assimilation process of an ERP system in two Polish companies. It resulted in the following conclusions which are not stressed enough in the existing literature: 1) The system selection and implementation partner selection are two separate steps.
11 Enterprise System Assimilation: phases, activities, and outcomes 39 2) Requirements analysis phase is crucial not only for the system selection but also for the determination of scope, budget and schedule once the system is selected. 3) Requirements analysis has to be detailed during the project in the form of system design (in SAP implementations called Business Blueprint). The analysis performed in this paper also allowed to present a more detailed list of actions in the realization phase of the project, together with respective outcomes, comparing to the existing literature. References 1. Ahituv N., Neumann S., Zviran M. (2002), A system development methodology for ERP systems, Journal of Computer Information Systems, Vol. 42, No. 3, p Bajwa D., Garcia J., Mooney T. (2004), An integrative framework for the assimilation of enterprise resource planning systems: phases, antecedents, and outcomes, Journal of Computer Information Systems, Spring, p Aloini D., Dulmin R., Mininno V. (2007), Risk management in ERP project introduction: Review of the literature, Information & Management, Vol. 44, No.6, p Dezdar S., Sulaiman A. (2009), Successful enterprise resource planning implementation: taxonomy of critical factors, Industrial Management & Data Systems, Vol. 109, No. 8, p Ehie I., Madsen M. (2005), Identifying critical issues in enterprise resource planning (ERP) implementation, Computers in Industry, Vol. 56, No. 6, p Esteves J., Chan R., Pastor J. (2003), An Exploratory Study of Knowledge Types Relevance Along Enterprise Systems Implementation Phases in 4-th European Conference on Organizational Knowledge and Learning Capabilities, p Hasan M. et al. (2011), Implementation of ERP of the Australian manufacturing companies, Industrial Management & Data Systems, Vol. 11, No 1, p Kwon, Tae H., Zmud R. (1987), Unifying the Fragmented Models of Information Systems Implementation, in Critical Issues in Information Systems Research, Boland and Hirschheim (Eds), John Wiley, New York.
12 40 Przemysław Lech 9. Muscatello J., Chen I. (2008), Enterprise Resource Planning (ERP) Implementations: Theory and Practice, International Journal of Enterprise Information Systems, Vol. 4, No 1, p Parr A., Shanks G. (2000), A model of ERP project implementation, Journal of Information Technology, Vol. 15, No.4, p Rosemann M. (1999), ERP software characteristics and consequences, [in:] Proceedings of the 7th European Conference on Information Systems, Copenhagen. 12. Sammon D., Adam F. (2010), Project preparedness and the emergence of implementation problems in ERP projects, Information & Management,Vol. 47, No 1, p Silva L., Fulk H.K. (2012), From disruptions to struggles: Theorizing power in ERP implementation projects, Information and Organization, Vol. 22, No 4, p Sedera D., Gable G. (2010), Knowledge Management Competence for Enterprise System Success, Journal of Strategic Information Systems, Vol. 19, p Soja P., Paliwoda Pękosz G. (2009), What are real problems in enterprise system adoption?, Industrial Management and Data Systems, Vol. 109, No.5, p Wu J-H., Shin S-S., Heng M. (2007), A methodology for ERP misfit analysis, Information & Management, Vol. 44, p Zmud R., Apple L. (1992), Measuring technology incorporation/infusion, Journal of Product Innovation Management, Vol. 9, Iss. 2, p Enterprise System Assimilation: phases, activities, and outcomes (Summary) This paper examines the assimilation process of a big Enterprise System, basing on two case studies of SAP implementation in Polish organizations. The phases of the assimilation process are determined, followed by activities, performed in each of the phase as well as resulting outcomes. Keywords Enterprise Systems, ERP, project, implementation, methodology
Enterprise System Implementation from the Functional Consultants Perspective Przemysław Lech University of Gdańsk, Faculty of Management, Poland Przemyslaw.Lech@lst.com.pl Abstract: Although Enterprise
ERP Implementation Program Key phases of ERP implementation: Analysis of the company existing or designing new business process descriptions Inventory of the company s existing formal workflows or designing
Przemysław Lech * Enterprise System Selection Process in Polish organizations Introduction The selection of an Enterprise System is a complex and time consuming process (Wei and Wang, 2004), and a systematic
COMPARATIVE STUDY OF ERP IMPLEMENTATION METHODOLOGY CASE STUDY: ACCELERATED SAP VS DANTES & HASIBUAN METHODOLOGY M. Hilman, F. Setiadi, I. Sarika, J. Budiasto, and R. Alfian Faculty of Computer Science,
ERP Lifecycle Concepts Ronald E. Giachetti, Ph.D. Associate Professor Industrial and Systems Engineering Florida International University Duane P. Truex, Ph.D. Associate Professor Robinson College of Business
Development, Acquisition, Implementation, and Maintenance of Application Systems Part of a series of notes to help Centers review their own Center internal management processes from the point of view of
ERP Systems: Audit and Control Risks Jennifer Hahn Deloitte & Touche ISACA Spring Conference April 26, 1999 Session Learning Objectives At the end of this session, the participant should be able to: Understand
Knowledge Transfer Procedures From to Users in ERP Implementations Przemysław Lech University Gdańsk, Poland Przemysław.firstname.lastname@example.org Abstract: This paper focuses on the issue knowledge transfer from
TEN TIPS FOR A SUCCESSFUL INFOR IMPLEMENTATION Copyright 2015 Panorama Consulting Solutions. All Rights Reserved. 720.515.1377 Panorama- Consulting.com Successfully implementing an Infor ERP system involves
Model performance indicators ERP systems setare yaghubi student, Department of computer Zanjan Branch, Islamic Azad University Zanjan, Iran email@example.com Nasser modiri Assoc. Prof, Department
Application Services Portfolio Overview Injazat Application Services offer end-to-end solutions that align Enterprises business objectives with their IT goals. Our solutions focus on implementing, building
ASAP- Accelerated SAP Vanessa Hong What is ASAP? What is ASAP Methodology? ASAP, accelerated SAP implement, means to go through the SAP implementation process efficiently. Accelerated SAP Methodology is
iapps Consulting DWC LLC Fixed Scope Offering (FSO) For Taleo Recruit and On-Boarding Drive Transformation Create Value 18-05-2015 1 About Us We are a technology and business consulting firm, focused on
Software Licensing Workshop: Strategy Design & Architecture Development Service Brief Benefits Expedite the license planning and design process: by taking advantage of SafeNet s license consulting expertise
AN ALTERNATIVE MODEL OF ERP MAINTENANCE STRATEGY Muhammad Rofi IMTIHAN 1, Mohd. Salihin NGADIMAN, Habibollah HARON Department of Modelling and Industrial Computing Faculty of Computer Science and Information
Fixed Scope Offering for Oracle Taleo EE Saas Implementation Agenda Company Profile Business Challenges Business Objectives Solution Proposal Scope Modules and Functionalities Implementation Approach Project
Enterprise Systems Assessing and managing the benefits of enterprise systems: the business manager s perspective Group members: Rick Dennis Simon 1 Goal of the paper What benefits organizations achieve
Executive Board First Regular Session Rome, 8 11 February 2010 RESOURCE, FINANCIAL AND BUDGETARY MATTERS Agenda item 6 For information* FINAL UPDATE ON THE WINGS II PROJECT E Distribution: GENERAL WFP/EB.1/2010/6
Colorado Department of Health Care Policy and Financing Solicitation #: HCPFRFPCW14BIDM Business Intelligence and Data Management Services (BIDM) Appendix B BIDM Project Phases Tables The guidelines for
AN EFFECTIVE IMPLEMENTATION OF AN ERP SYSTEM WITH AN ASSESMENT IN A TURKISH FIRM Zeki Ayag 1, Rifat Gürcan Özdemir 2 and Bahar Yelken 3 Abstract In the light of both fast-growing achievements and advantages
E WO/PBC/21/12 ORIGINAL: ENGLISH DATE: JULY 1, 2013 Program and Budget Committee Twenty-First Session Geneva, September 9 to 13, 2013 PROGRESS REPORT ON THE IMPLEMENTATION OF A COMPREHENSIVE INTEGRATED
Request for Proposal for Application Development and Maintenance s for ML Store platforms Annex 4: Application Development & Maintenance Requirements Description TABLE OF CONTENTS Page 1 1.0 s Overview...
ASAP Implementation Roadmap Methodology why? ASAP Overview ASAP Roadmap Structure Project Management in ASAP ASAP Content Overview How to access Roadmap Projects from another perspective An estimated 68%
Technical Management Strategic Capabilities Statement Business Solutions for the Future When your business survival is at stake, you can t afford chances. So Don t. Think partnership think MTT Associates.
Agenda Executive Summary This presentation provides an overview of the fixed scope offering of Oracle s Fusion HCM Cloud solution from METSCON IT Systems METSCON is a key partner of Oracle in the HCM space
2015 ERP REPORT A Panorama Consulting Solutions Research Report Copyright 2015 Panorama Consulting Solutions. All rights reserved. No unauthorized reproduction without the author s written consent. All
SAP Implementation and Post Implementation Services Carmel Point, Road No. 12, Banjara Hills Hyderabad, INDIA - 500 034 h t t p : / / w w w. o p u s a s i a. c o m ENTERPRISE RESOURCE PLANNING The competitive
Chapter: 1 Enterprise Resource Planning Introduction Enterprise Resource Planning is the latest high end solution, information technology has lent to business application. The ERP solutions seek to streamline
1788 JOURNAL OF COMPUTERS, VOL. 8, NO. 7, JULY 2013 The Extent of ERP Customization towards User Satisfaction in Daily Operation for Manufacturing Companies Kasturi Kanchymalay Faculty of Information and
Performance Audit Concurrent Review: ERP Pre-Solicitation April 2002 City Auditor s Office City of Kansas City, Missouri 24-2001 April 10, 2002 Honorable Mayor and Members of the City Council: We conducted
EXECUTIVE SUMMARY This document provides an overview of the Systems Development Life-Cycle (SDLC) process of the U.S. House of Representatives. The SDLC process consists of seven tailored phases that help
ERP Purchase Decision at Benton Manufacturing Company Presented By Ahmad Ardiansyah Zein Araro Jireh Tulus Bambang Wijarnako Raja Badal Muda Sedang Bagus Tirtayasa The Content About Company ERP & Information
ERP Template Rollouts to China Joerg HEIL Guangzhou, 2013.10.17 1 Agenda About us local ERP solutions vs. SAP Rollout definition Rollout strategies Local requirements Project plan Success factors / Lessons
Project Managing Microsoft Dynamics AX, Microsoft Dynamics GP, and Microsoft Dynamics NAV Implementations with Microsoft Dynamics Sure Step 2010 80199: Project Managing Microsoft Dynamics AX, Microsoft
CAICT COMMUNICATIONS 2010/2 ERP Systems: Critical Factors in Theory and Practice Jonas Hedman 8 January 2010 ISBN 978-87-92524-08-9 Center for Applied ICT (CAICT) Copenhagen Business School - Howitzvej
CHAPTER ENTERPRISE RESOURCE PLANNING SYSTEMS This chapter introduces an approach to information system development that represents the next step on a continuum that began with stand-alone applications,
ARTICLE C.1. STATEMENT OF WORK This contract is designed to permit the Institutes and Centers (ICs) of NIH, the Department of Health and Human Services (DHHS), and all other federal agencies to acquire
Optimize Usage with Dashboards Requirements Optimize Design Operate Build and Test Deploy Centrally Control Your KPIs with Management Dashboards Management dashboards in SAP Solution Manager Display the
Implementing ERP-systems with accelerated ERP more efficient and quickly a best practice Yucel Yılmaz 1, Gurkan Ozcan 2 1 Department of Business Informatics, Marmara University, Turkey firstname.lastname@example.org
US ONSHORING OFFERS SUPERIOR EFFECTIVENESS OVER OFFSHORE FOR CRM IMPLEMENTATIONS Whitepaper Eagle Creek Software Services March 2015 Introduction CRM services are shifting from a focus on point solution
By, WWW.101ERPTEAM.COM Data Migration/Conversion to SAP from Legacy systems - Our Strategy Project Implementation Team ---------------------------------------- SAP Consulting Services - Implementation,
A SYSTEM DEVELOPMENT METHODOLOGY FOR ERP SYSTEM IN SMEs OF MALAYSIAN MANUFACTURING SECTORS 1 YOUSEF KHALEEL, 2 RIZA SULAIMAN 1 Student, Department of Industrial Computing, UKM, Selangor, Malaysia 2 Assoc.
Workshop 80054A: Project Managing Microsoft Dynamics CRM Implementations with Microsoft Dynamics Sure Step Length: 2 Day(s) Published: November 12, 2008 Language(s): Audience(s): English Developers Level:
International Management and E(lectronic)-Business Enterprise Resource Planning Systems (ERP) and E-business System Integration Prof. Michael H. Breitner (email@example.com) Dipl.-Ök. Nadine
0 UC Modernization Project Plan 1115 d 1 1 Phase I - Business Case Development and Competitive Procurement 205 d 2 1.1 Complete Initial Feasibility Study 55 d 3 1.2 Prepare and Issue LBR 30 d 2 4 1.3 Competitive
ERP IMPLEMENTATION BOOT CAMP The Manufacturing ERP Experience Sponsored by MetalForming Magazine April 8-9, 2014 Eric Kimberling Managing Partner and Founder Panorama Consulting Solutions www.panorama-consulting.com
CHAPTER 1 1 INTRODUCTION 1.1 Background of the Research Enterprise Resource Planning (ERP) has been widely used in developed countries to integrate the information and to support decision making to achieve
A LANDCSAPE OF ENTERPRISE RESOURCE PLANNING IMPLEMENTATION Marina Hassan 1, 2 and Marzanah A. Jabar 1 1 Universiti Putra Malaysia (UPM), Malaysia, firstname.lastname@example.org 1 Universiti Putra Malaysia (UPM),
Influence of Business Process on the ERP Project Effectiveness Jun-Der Leu*, Wen-Hsien Tsai*, Ping-Yu Hsu*, Julian Cheng*, Yi-Wen Fan** *Institute of Business Administration, National Central University
IT Asset Management - an Integral Part of an Overall Asset Management Strategy John E. Provo Business Development Manager NichExperts Why would an organization want to track, and effectively manage their
ERP SYSTEMS AND INTERNAL AUDIT Aditya Saharia, Fordham University, email@example.com Bruce Koch, Seattle University, firstname.lastname@example.org Robert Tucker, University of Florida, email@example.com
PAGE 6 of 51 SECTION C: DESCRIPTION/SPECIFICATIONS/WORK STATEMENT Article C.1 Statement of Work This contract is designed to permit the Institutes and Centers (ICs) of NIH, the Department of Health and
Ten Questions to Ask PLM Solution Suppliers What You Need to Know to Make an Informed Decision August 2010 A CIMdata White Paper Ten Questions to Ask PLM Solution Suppliers What You Need to Know to Make
Application Development Methodology The main objective of Enterprise Applications is to design, develop, and maintain quality software. This document out lines the requirements for requesting new systems,
Planning an ERP Implementation Project @ Small and Medium Enterprises 27 th Regional WIRC Conference 31 August 2012 Table of Contents What is an SME and ERP Why an ERP for the SME segment Assessing the
How to realize software evolution of existing BOSS via ZTE SEEM Zhan Zhang Abstract Due to long-term construction and accumulation for different purposes, telecom carriers normally have very complex IT
SCOPE OF WORK 1. Brief Scope of work The scope of work of Implementation Partner (IP) shall include the following: Supply and installation of ERP licenses including ATS ERP system implementation, Project
Enterprise Data Management for SAP Gaining competitive advantage with holistic enterprise data management across the data lifecycle By having industry data management best practices, from strategy through
SAP PPM as the standard for Portfolio and Project Management at NRB. Wim Hertenweg Luc Marin David Seifert SAPience.be User Day 15 1 Agenda Introduction NRB & Expertum Introduction PPM PPM Proof of concept
Knowledge Base Data Warehouse Methodology Knowledge Base's data warehousing services can help the client with all phases of understanding, designing, implementing, and maintaining a data warehouse. This
Last Name First Name Richter Klemens Address Kriemhildenstrasse 11 80639 München Germany Telephone Mobile Work Fax +49 173 8044082 +49 89 5676 3880 +49 1803 551841208 E-Mail Homepage firstname.lastname@example.org
Change Management Procedure Procedure # Description: Overview Outlines the steps for a Project Manager to manage change in an organization Objective To ensure that organizational change is managed in a
A Systems Implementation Project Planning Guide Solutions & Project Management Services for Systems & Operations Projects Business Requirements Analysis Overview Project Plan High-Level Detailed Design
Fixed Scope Offering for Implementation of Sales Cloud & Sales Cloud Integration With GTS Property Extensions Today s Business Challenges Adopt leading CRM practices and stream line processes Take advantage
SECTION A: DESCRIPTION/SPECIFICATIONS/WORK STATEMENT Article A.1 Introduction This contract is intended to provide IT solutions and services as defined in FAR 2.101(b) and further clarified in the Clinger-Cohen
Critical Success Factors for ERP System Implementation Jun Wu School of Economics and Management, Beijing University of Posts and Telecommunications, Beijing100876, China email@example.com Abstract.
Contents Preface From the Editor s Desk Evolving Trends in Core Banking Transformation (CBT) 01. Customer Expectations and Next Generation Banking 05 02. Survival Driving Core Banking Transformation (CBT)
A SAP ERP Upgrade Checklist Project Preparation Upgrade Project Phase Project Preparation Definition From the project perspective the project preparation phase includes: Learning about the new functionality
APDSI 2000 Full Paper (July, 2000) An Integrated Methodology for Implementing ERP Systems Su-Yeon Kim 1), Eui-Ho Suh 2), Hyun-Seok Hwang 3) 1) Department of Industrial Engineering, POSTECH, Korea (firstname.lastname@example.org)
SECTION C: DESCRIPTION/SPECIFICATIONS/WORK STATEMENT Article C.1 Introduction This contract is intended to provide IT solutions and services as defined in FAR 2.101(b) and further clarified in the Clinger-Cohen
Certified Information Systems Auditor (CISA ) Certification Course Description Our 5-day ISACA Certified Information Systems Auditor (CISA) training course equips information professionals with the knowledge
Accenture Human Capital Management Solutions Transforming people and process to achieve high performance The sophistication of our products and services requires the expertise of a special and talented
Kenan-Flagler Business School State of North Carolina Business Systems Infrastructure Study Phase II Blueprint for Selecting Improvement Approach Executive Summary January 5, 2004 Business Case www.osc.state.nc.us
Transforming Raw Data into Business Results In the rapid pace of today's business environment, businesses must be able to adapt to changing customer needs and quickly refocus resources to meet market demand.
The Current Business Intelligence Practice in Hong Kong By Dr. Raymond Y.K. Lau and Johnny C.F. So Department of Information Systems, City University of Hong Kong And Hong Kong Computer Society Business
Selecting and Implementing Treasury Technology From the Corporate Perspective Overview Treasury technology is now essential. Corporations demand (and require) current global information with sophisticated
IT Services Management Service Brief Capacity Management Prepared by: Rick Leopoldi May 25, 2002 Copyright 2002. All rights reserved. Duplication of this document or extraction of content is strictly forbidden.
Jeff Woods Research Managing Vice President This overview provides a high-level description of the ERP Key Initiative. IT leaders can use this overview to better understand what they need to do to prepare
Enterprise Data Management Data Factory as a Service (DFaS) Data Factory as a Service (DFaS) What is DFaS? DFaS offers a proven approach to deliver comprehensive services for end-to-end data conversion
Ontology for PLM Implementation to Facilitate Inorganic Growth for an Organization By Subbanarasaiah K.V.Akshintala, Ganeshraj Machandran and Pitchiah Ramaswamy Introduction Corporate mergers occur when
Industrial Rapid Implementation Methodology (InRIM) Introduction The path to improving asset effectiveness and productivity must be based on a firm foundation created from the interaction of three essential
The new ASAP Methodology Overview of the new ASAP Methodology for Implementation 7.x and ASAP Business Add-Ons Jan Musil Director, Global Project Management Office SAP Field Services Raimar Hoeliner Program
Capstone: Enterprise Applications 57C99904, fall 2015 (6 cr) Introduction to Enterprise Resource Planning (ERP) Systems Learning Objectives Understand the key terms related to Enterprise Resource Planning
Your consent to our cookies if you continue to use this website.