ERP Implementation Fundamentals It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM ERP Implementation Fundamentals Richard Byrom Oracle Consultant, Speaker and Author http://www.richardbyrom.com Me and where I am from This presentation has been put together based on my experiences I have had whilst implementing systems over the last 8 years and it is my hope that by relating some of these experiences to you I can help you implement your systems more effectively. Prepared by : Richard Byrom - RPC Data

Why implement an ERP system? How should ERP systems be implemented? It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM Agenda What is an ERP System? Why implement an ERP system? How should ERP systems be implemented? Conclusion Questions and Answers Prepared by : Richard Byrom - RPC Data

What is an ERP System – definitions It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM 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) Point 1 Enterprise means organisation wide Resource refers to all the resources at your disposal – customers Planning means looking at the long term view rather than just current and Prepared by : Richard Byrom - RPC Data

Historical system architectures It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM 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. Perhaps mention best of breed. Prepared by : Richard Byrom - RPC Data

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.

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.

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.

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

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.

Typical architectural components It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM Typical architectural components Web Internet Mobile Wireless e-Mail Call Center ICM/Telephony Interaction Channels Marketing Intelligence Sales Intelligence Customer Intelligence Call Center Intelligence Analytical Applications Marketing Sales eCommerce OSS HR Business Applications Installed Base Resources Territories Assignment Engine CRM Foundation Tasks Notes Calendar 1-to-1 Fulfillment Common Data and Object Models, Security, Interfaces, Globalisation E-Business Foundation TCA Escalations Interaction History Universal Work Q E-business Platform Tech Stack Prepared by : Richard Byrom - RPC Data

Tech Stack - Internet Computing Architecture It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM Tech Stack - Internet Computing Architecture Application 2 Tier X Database Application Server Application 3 Tier Browser Java Move from 2 tier two three tier architecture. Simplified Deployment Other advantages of this architecture become apparent when we look at application deployment. In client server environments, you would need to install the application on each desktop. If you add new users, you need to install the application. If you want to upgrade.... you need to install the application. If we’ve learned one thing from Y2K compliance, it’s that upgrading 100’s or 1000’s of desktops is a challenge best avoided. The true, three-tier architecture avoids this pitfall. By storing the application on the middle tier, the ICA requires you to upgrade only the servers. Clients upgrade themselves. As soon as the browser detects that a new application version exists, it’s downloaded automatically. Even some “web” tools use plug ins that load windows components as opposed to IC architecture. These can be as difficult to uninstall as typical windows applications. Prepared by : Richard Byrom - RPC Data

Why implement an ERP System? It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM 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 Point 1 There must be a value proposition, return on investment, total cost of ownership. Point 2-4 Often these can be part of your business goals as well. Prepared by : Richard Byrom - RPC Data

How should we implement ERP systems It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM How should we implement ERP systems It’s all really about control, it’s about aligning your people process and technology so that they master the raging waters of your high volume transactional system. People who have experienced Process You have to row in a certain way Technology You have to have a decent boat Obtain the right mix of people, processes and technology!! Prepared by : Richard Byrom - RPC Data

How should we implement ERP Systems? It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM 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 Insert the white water rafting video. Prepared by : Richard Byrom - RPC Data

1. Definition and Analysis It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM 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 Phasing is important Scoping is also important Prepared by : Richard Byrom - RPC Data

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

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

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

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

It is a means to an end, not the end It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM 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 Prepared by : Richard Byrom - RPC Data

It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM 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 Prepared by : Richard Byrom - RPC Data

A Q &

e-mail : richard@richardbyrom.com It's month end, now comes the reconciliation crunch Appsworld January 2004 2/2/2019 8:34:33 PM Speaker Information Name : Richard Byrom e-mail : richard@richardbyrom.com Web Site : http://www.richardbyrom.com Please do not hesitate to contact me. Prepared by : Richard Byrom - RPC Data