1 / 24

ERP Implementation Fundamentals

ERP Implementation Fundamentals. Richard Byrom Oracle Consultant, Speaker and Author http://www.richardbyrom.com. ERP Implementation Fundamentals. Richard Byrom Oracle Consultant, Speaker and Author http://www.richardbyrom.com. Agenda. What is an ERP System? Why implement an ERP system?

vivianr
Télécharger la présentation

ERP Implementation Fundamentals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ERP Implementation Fundamentals Richard Byrom Oracle Consultant, Speaker and Author http://www.richardbyrom.com

  2. ERP Implementation Fundamentals Richard Byrom Oracle Consultant, Speaker and Author http://www.richardbyrom.com

  3. Agenda • What is an ERP System? • Why implement an ERP system? • How should ERP systems be implemented? • Conclusion • Questions and Answers

  4. What is an ERP System – definitions Simplistic Definition ERP - Enterprise Resource Planning Detailed Definition “a business strategy and set of industry-domain-specific applications that build customer and shareholder communities value network system by enabling and optimising enterprise and inter-enterprise collaborative operational and financial processes”(Source: Gartner’s Research Note SPA-12-0420)

  5. Historical system architectures Historically, companies created “islands of automation”. A hodge-podge of various systems that operated or managed various divergent business processes. Sometimes these systems were integrated with each other and sometimes they weren’t. Sometimes they were loosely interfaced and sometimes they were more tightly interfaced.

  6. What is an ERP – Key Characteristics Integration seamless integration of all the information flowing through a company – financial and accounting, human resource information, supply chain information, and customer information.

  7. What is an ERP – Key Characteristics Packages Enterprise systems are not developed in-house • IS life cycle is different • Mapping organisational requirements to the processes and terminology employed by the vendor and • Making informed choices about the parameter setting. • Organisations that purchase enterprise systems enter into long-term relationships with vendors. Organisations no longer control their own destiny.

  8. What is an ERP – Key Characteristics Best Practices • ERP vendors talk to many different businesses within a given industry as well as academics to determine the best and most efficient way of accounting for various transactions and managing different processes. The result is claimed to be “industry best practices”. • The general consensus is that business process change adds considerably to the expense and risk of an enterprise systems implementation. Some organisations rebel against the inflexibility of these imposed business practices.

  9. What is an ERP – Key Characteristics Some Assembly Required Only the software is integrated, not the computing platform on which it runs. Most companies have great difficulty integrating their enterprise software with a package of hardware, operating systems, database management systems software, and telecommunications suited to their specific needs. • Interfaces to legacy systems • Third-party bolt-on applications • Best of Breed Strategy

  10. What is an ERP – Key Characteristics Evolving Enterprise Systems are changing rapidly • Architecturally: Mainframe, Client/Server, Web-enabled, Object-oriented, Componentisation • Functionally: front-office (i.e. sales management), supply chain (advanced planning and scheduling), data warehousing, specialised vertical industry solutions, etc.

  11. Interaction Channels Web Internet Mobile Wireless e-Mail Call Center ICM/Telephony MarketingIntelligence SalesIntelligence CustomerIntelligence Call CenterIntelligence Analytical Applications E-Business Foundation Common Data and Object Models, Security, Interfaces, Globalisation Tech Stack E-business Platform Typical architectural components Marketing Sales eCommerce OSS HR Business Applications Installed Base Resources Territories Assignment Engine CRM Foundation Tasks Notes Calendar 1-to-1 Fulfillment TCA Escalations Interaction History Universal Work Q

  12. Application Application Application Application Application Application Database Application Application Browser Java Application Server Browser Tech Stack - Internet Computing Architecture 2 Tier X 3 Tier

  13. Why implement an ERP System? • To support business goals • Integrated, on-line, secure, self-service processes for business • Eliminate costly mainframe/fragmented technologies • Improved Integration of Systems and Processes • Lower Costs • Empower Employees • Enable Partners, Customers and Suppliers

  14. How should we implement ERP systems Obtain the right mix of people, processes and technology!!

  15. How should we implement ERP Systems? • People • Project Structure • Should be aligned to processes • Process • Implementation Process (outlined in detail) • Adapt your processes to those of the ERP. • Technology • Hardware • Software • Integrated Systems

  16. Process 1. Definition and Analysis • Hold discussions with various functional personnel to establish the actual number of systems operating at client site, what they are used for, why and how often • Produce the Project Scoping Document outlining current situation, proposed solution and budgeted time Challenge : REQUISITE EXPERTISE - No two clients are the same

  17. Process 2. Design • Prepare various functional reports - specifies current scenario and wish list • Prepare Design document which specifies how the system is going to work • Prepare test scripts to be followed on system testing • Map out the interface paths to various modules Challenge : INFORMATION SHARING - Availability of staff

  18. Process 3. Build • Configure system as per set up document specifications i.e. transfer conceptual model into reality • Test system to verify accuracy (preliminary tests) Challenge : TECHNICAL ENVIRONMENT - System functionality

  19. Process 4. Transition • Train users on their specific areas • Assist in test data compilation and system testing by users • Finalise the Live system and captured opening balances Challenge : USER RESISTANCE Understanding and acceptance data preparation

  20. Process 5. Production • Official hand holding • Effectiveness assessment • Business and Technical Direction recommendations

  21. Technology • Technology is an enabler, not the driver (it is there to assist the organisation to achieve business goals) • It is a means to an end, not the end

  22. Conclusion • ERP systems provide a mechanism for implementing systems where a high degree of integration between applications is required • The Business Case or Value Proposition for implementation must be outlined • To successfully implement a proper mix of people, processes and technology should be maintained

  23. Q & A

  24. Speaker Information Name : Richard Byrom e-mail : richard@richardbyrom.com Web Site : http://www.richardbyrom.com

More Related