Your SlideShare is downloading. ×
0
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
PPT
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

PPT

790

Published on

1 Comment
0 Likes
Statistics
Notes
  • thanks for this nice presentation............................
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total Views
790
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
17
Comments
1
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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.
  • 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
  • Perhaps mention best of breed.
  • 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.
  • 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.
  • 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
  • Insert the white water rafting video.
  • Phasing is important Scoping is also important
  • Please do not hesitate to contact me.
  • Transcript

    • 1. ERP Implementation Fundamentals Richard Byrom Oracle Consultant, Speaker and Author http://www.richardbyrom.com
    • 2. Agenda <ul><li>What is an ERP System? </li></ul><ul><li>Why implement an ERP system? </li></ul><ul><li>How should ERP systems be implemented? </li></ul><ul><li>Conclusion </li></ul><ul><li>Questions and Answers </li></ul>
    • 3. What is an ERP System – definitions <ul><li>Simplistic Definition </li></ul><ul><li>ERP - Enterprise Resource Planning </li></ul><ul><li>Detailed Definition </li></ul><ul><li>“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) </li></ul>
    • 4. Historical system architectures <ul><li>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. </li></ul>
    • 5. What is an ERP – Key Characteristics <ul><li>Integration </li></ul><ul><li>seamless integration of all the information flowing through a company – financial and accounting, human resource information, supply chain information, and customer information. </li></ul>
    • 6. <ul><li>Packages </li></ul><ul><li>Enterprise systems are not developed in-house </li></ul><ul><li>IS life cycle is different </li></ul><ul><ul><li>Mapping organisational requirements to the processes and terminology employed by the vendor and </li></ul></ul><ul><ul><li>Making informed choices about the parameter setting. </li></ul></ul><ul><li>Organisations that purchase enterprise systems enter into long-term relationships with vendors. Organisations no longer control their own destiny. </li></ul>What is an ERP – Key Characteristics
    • 7. <ul><li>Best Practices </li></ul><ul><li>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”. </li></ul><ul><li>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. </li></ul>What is an ERP – Key Characteristics
    • 8. <ul><li>Some Assembly Required </li></ul><ul><li>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. </li></ul><ul><li>Interfaces to legacy systems </li></ul><ul><li>Third-party bolt-on applications </li></ul><ul><li>Best of Breed Strategy </li></ul>What is an ERP – Key Characteristics
    • 9. <ul><li>Evolving </li></ul><ul><li>Enterprise Systems are changing rapidly </li></ul><ul><li>Architecturally: Mainframe, Client/Server, Web-enabled, Object-oriented, Componentisation </li></ul><ul><li>Functionally: front-office (i.e. sales management), supply chain (advanced planning and scheduling), data warehousing, specialised vertical industry solutions, etc. </li></ul>What is an ERP – Key Characteristics
    • 10. Typical architectural components CRM Foundation Marketing Sales eCommerce Business Applications Interaction History Universal Work Q 1-to-1 Fulfillment Assignment Engine Escalations TCA Installed Base Tasks Notes Resources Calendar Territories OSS HR E-business Platform Tech Stack Web Internet Mobile Wireless e-Mail Call Center ICM/Telephony Interaction Channels Common Data and Object Models, Security, Interfaces, Globalisation E-Business Foundation Marketing Intelligence Sales Intelligence Customer Intelligence Call Center Intelligence Analytical Applications
    • 11. Tech Stack - Internet Computing Architecture X 2 Tier 3 Tier Database Application Application Application Application Application Application Browser Browser Java Application Server Application Application
    • 12. Why implement an ERP System? <ul><li>To support business goals </li></ul><ul><ul><li>Integrated, on-line, secure, self-service processes for business </li></ul></ul><ul><ul><li>Eliminate costly mainframe/fragmented technologies </li></ul></ul><ul><li>Improved Integration of Systems and Processes </li></ul><ul><li>Lower Costs </li></ul><ul><li>Empower Employees </li></ul><ul><li>Enable Partners, Customers and Suppliers </li></ul>
    • 13. How should we implement ERP systems <ul><li>Obtain the right mix of people, processes and technology!! </li></ul>
    • 14. How should we implement ERP Systems? <ul><li>People </li></ul><ul><ul><li>Project Structure </li></ul></ul><ul><ul><li>Should be aligned to processes </li></ul></ul><ul><li>Process </li></ul><ul><ul><li>Implementation Process (outlined in detail) </li></ul></ul><ul><ul><li>Adapt your processes to those of the ERP. </li></ul></ul><ul><li>Technology </li></ul><ul><ul><li>Hardware </li></ul></ul><ul><ul><li>Software </li></ul></ul><ul><ul><li>Integrated Systems </li></ul></ul>
    • 15. Process <ul><li>1. Definition and Analysis </li></ul><ul><li>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 </li></ul><ul><li>Produce the Project Scoping Document outlining current situation, proposed solution and budgeted time </li></ul><ul><li>Challenge : REQUISITE EXPERTISE - No two clients are the same </li></ul>
    • 16. Process <ul><li>2. Design </li></ul><ul><li>Prepare various functional reports - specifies current scenario and wish list </li></ul><ul><li>Prepare Design document which specifies how the system is going to work </li></ul><ul><li>Prepare test scripts to be followed on system testing </li></ul><ul><li>Map out the interface paths to various modules </li></ul><ul><li>Challenge : INFORMATION SHARING - Availability of staff </li></ul>
    • 17. Process <ul><li>3. Build </li></ul><ul><li>Configure system as per set up document specifications i.e. transfer conceptual model into reality </li></ul><ul><li>Test system to verify accuracy (preliminary tests) </li></ul><ul><li>Challenge : TECHNICAL ENVIRONMENT - System functionality </li></ul>
    • 18. Process <ul><li>4. Transition </li></ul><ul><li>Train users on their specific areas </li></ul><ul><li>Assist in test data compilation and system testing by users </li></ul><ul><li>Finalise the Live system and captured opening balances </li></ul><ul><li>Challenge : USER RESISTANCE Understanding and acceptance </li></ul><ul><li>data preparation </li></ul>
    • 19. Process <ul><li>5. Production </li></ul><ul><li>Official hand holding </li></ul><ul><li>Effectiveness assessment </li></ul><ul><li>Business and Technical Direction recommendations </li></ul>
    • 20. Technology <ul><li>Technology is an enabler, not the driver (it is there to assist the organisation to achieve business goals) </li></ul><ul><li>It is a means to an end, not the end </li></ul>
    • 21. Conclusion <ul><li>ERP systems provide a mechanism for implementing systems where a high degree of integration between applications is required </li></ul><ul><li>The Business Case or Value Proposition for implementation must be outlined </li></ul><ul><li>To successfully implement a proper mix of people, processes and technology should be maintained </li></ul>
    • 22. A Q &
    • 23. Speaker Information <ul><li>Name : Richard Byrom </li></ul><ul><li>e-mail : [email_address] </li></ul><ul><li>Web Site : http://www.richardbyrom.com </li></ul><ul><li> </li></ul>

    ×