This document provides an overview of enterprise resource planning (ERP) systems, including their history and evolution. ERP systems integrate internal and external management of information across an entire organization, including functions like finance, manufacturing, sales, and customer relationship management. The document discusses leading ERP providers like SAP, Oracle, and Infor. It also examines factors that can cause ERP implementations to fail, such as employee resistance, lack of management commitment, unrealistic expectations, and extensive customization. The document analyzes FoxMeyer's failed ERP implementation in the 1990s as a case study, highlighting risks like unrealistic scope, poor execution, and a challenging environment. Lessons are provided around planning, implementation, testing, and change management
The presentation is about ERP Implementation failure case study of the Famous Choclate manufacturing brand Heshey's. What went wrong and what could have been done? is explaind!
A Successful ERP Implementation in an Ethiopian CompanyMayuree Srikulwong
My students' presentation of a paper "A Successful ERP Implementation in an Ethiopian Company" by Boltena et. al. (2012). It provides a summary of ERP implementation successful case study of a company in Ethiopia.
The presentation is about ERP Implementation failure case study of the Famous Choclate manufacturing brand Heshey's. What went wrong and what could have been done? is explaind!
A Successful ERP Implementation in an Ethiopian CompanyMayuree Srikulwong
My students' presentation of a paper "A Successful ERP Implementation in an Ethiopian Company" by Boltena et. al. (2012). It provides a summary of ERP implementation successful case study of a company in Ethiopia.
Enterprise Resource Planning (ERP) is made to automate any task. With ERP, it is easy to manage every department under one single database.
This consumes not much time and is easy and fast way to do work with.
The 12 cardinal sins of erp implementationPoonam pandey
Introduction
Enterprise Resources Planning (ERP) is an outgrowth of Product Requirements Planning (MRP) initiated in the 1970's as a new computer-based technique to planning and scheduling of material requirements and inventory, featuring the time-phased order point. MRP developed to MRP II (Material Resources Planning) the "closed loop" procedure, to Business Requirements Planning (BRP) and eventually to ERP. As MRPII entered into vogue in the late 1970's and early 1980's, software companies began to establish software packages around MRPII principles.
I, BIPIN BHARDWAJ, Hereby declare that this MUP report is the record of authentic work carried out and has not been submitted to any other University or Institute for the award of any degree / diploma etc.
A detailed presentation related to ERP Systems in Oracle. It is very popular for any firm/organization to work in their platform and solve the business work and provide solution. Software development processes helps to built software using Agile models.
A complete guide of Oracle ERP System. It is the most advanced system of current market scenario. A brief written content with the help of researchers, scientists and engineers. Oracle is targeting the current ERP market and increasing their productivity and providing a better solution for Organizations to improve there business.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
AI Genie Review: World’s First Open AI WordPress Website CreatorGoogle
AI Genie Review: World’s First Open AI WordPress Website Creator
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-genie-review
AI Genie Review: Key Features
✅Creates Limitless Real-Time Unique Content, auto-publishing Posts, Pages & Images directly from Chat GPT & Open AI on WordPress in any Niche
✅First & Only Google Bard Approved Software That Publishes 100% Original, SEO Friendly Content using Open AI
✅Publish Automated Posts and Pages using AI Genie directly on Your website
✅50 DFY Websites Included Without Adding Any Images, Content Or Doing Anything Yourself
✅Integrated Chat GPT Bot gives Instant Answers on Your Website to Visitors
✅Just Enter the title, and your Content for Pages and Posts will be ready on your website
✅Automatically insert visually appealing images into posts based on keywords and titles.
✅Choose the temperature of the content and control its randomness.
✅Control the length of the content to be generated.
✅Never Worry About Paying Huge Money Monthly To Top Content Creation Platforms
✅100% Easy-to-Use, Newbie-Friendly Technology
✅30-Days Money-Back Guarantee
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIGenieApp #AIGenieBonus #AIGenieBonuses #AIGenieDemo #AIGenieDownload #AIGenieLegit #AIGenieLiveDemo #AIGenieOTO #AIGeniePreview #AIGenieReview #AIGenieReviewandBonus #AIGenieScamorLegit #AIGenieSoftware #AIGenieUpgrades #AIGenieUpsells #HowDoesAlGenie #HowtoBuyAIGenie #HowtoMakeMoneywithAIGenie #MakeMoneyOnline #MakeMoneywithAIGenie
Understanding Nidhi Software Pricing: A Quick Guide 🌟
Choosing the right software is vital for Nidhi companies to streamline operations. Our latest presentation covers Nidhi software pricing, key factors, costs, and negotiation tips.
📊 What You’ll Learn:
Key factors influencing Nidhi software price
Understanding the true cost beyond the initial price
Tips for negotiating the best deal
Affordable and customizable pricing options with Vector Nidhi Software
🔗 Learn more at: www.vectornidhisoftware.com/software-for-nidhi-company/
#NidhiSoftwarePrice #NidhiSoftware #VectorNidhi
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
Atelier - Innover avec l’IA Générative et les graphes de connaissancesNeo4j
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...Globus
Large Language Models (LLMs) are currently the center of attention in the tech world, particularly for their potential to advance research. In this presentation, we'll explore a straightforward and effective method for quickly initiating inference runs on supercomputers using the vLLM tool with Globus Compute, specifically on the Polaris system at ALCF. We'll begin by briefly discussing the popularity and applications of LLMs in various fields. Following this, we will introduce the vLLM tool, and explain how it integrates with Globus Compute to efficiently manage LLM operations on Polaris. Attendees will learn the practical aspects of setting up and remotely triggering LLMs from local machines, focusing on ease of use and efficiency. This talk is ideal for researchers and practitioners looking to leverage the power of LLMs in their work, offering a clear guide to harnessing supercomputing resources for quick and effective LLM inference.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
2. Contents
Introduction – What / Why / When
ERP History and Evolution
Leading ERP Providers
Prerequisites of ERP
Factors that cause an ERP to Fail
Case Study
Lessons Learned
Conclusion
3. ERP – What is it ??
Enterprise resource planning (ERP) systems integrate internal and
external management of information across an entire organization—
embracing finance/accounting, manufacturing, sales and
service, customer relationship management, etc. ERP systems
automate this activity with an integrated software application. ERP
facilitates information flow between all business functions inside the
organization, and manages connections to outside stakeholders.
Enterprise system software is a multi-billion dollar industry that
produces components that support a variety of business functions.
IT investments have become the largest category of capital
expenditure in United States-based businesses over the past
decade. Enterprise systems are complex software packages that
offer the potential of integrating data and processes across
functions in an enterprise.
4. ERP – Why is it needed ??
Separate systems were being maintained during 1960/70 for traditional business
functions like Sales & Marketing, Finance, Human Resources, Manufacturing, and
Supply Chain Management. These systems were often incongruent, hosted in
different databases and required batch updates. It was difficult to manage business
processes across business functions e.g. procurement to pay and sales to cash
functions. ERP system grew to replace the islands of information by integrating
these traditional business functions.
Successful implementation of an ERP system will have following advantages
1. Business integration and Improved Data Accuracy
2. Planning and MIS
3. Improved Efficiency and Productivity
4. Establishment of Standardized Procedures
5. Flexibility and technology
5. ERP – When ??
In 1990 Gartner Group first employed the acronym ERP as an
extension of material requirements planning (MRP),
later manufacturing resource planning and computer-
integrated manufacturing. Without supplanting these terms,
ERP came to represent a larger whole, reflecting the evolution
of application integration beyond manufacturing. Not all ERP
packages were developed from a manufacturing core. Vendors
variously began with accounting, maintenance, and human
resources. By the mid–1990s ERP systems addressed all core
functions of an enterprise. Beyond corporations, governments
and non–profit organizations also began to use ERP systems.
6. ERP - History
MRP II (From the 80's& 90’s) includes ALL
Manufacturing Resources for "What If" Pro-Active
Process Simulations
• MRP - (From the 60's& 70’s) includes only
Material Planning Projections
• ERP (From the 80's& 90’s) includes ALL Business
Management Systems, Philosophies and
Performance Evaluation at All Levels
7. ERP System Evolution Course
1970s 1980s 1990s 2000s
Market
Characteristics
Mass Market Market Segments Niche Market Individuals
Demand Focus Cost Quality Feasibility Timelines
Manufacturing
Method
Mass production of
limited product lines
Small-scale production
of various product
lines
Mass production of
various product lines
Mass production of
customized products
Structured Centralized Decentralized Centralized Virtual
Management System MRP II JIT/TQC ERP + SCM EERP + SCM
Management Focus Focuses on sales,
production,
materials, and
financial
management,
planning and
implementation of
manufacturing
material integration.
Focuses on cost,
quality, efficiency, and
promptness of material
supply.
Focuses on research and
development, sales,
production allocation and
distribution, service,
integration and optimal
utilization of internal
financial resources.
Focuses on a global
operating model that
combines internal
and external
customers and
manufacturers.
Application Tertiary Large area Large area Worldwide Worldwide
Operation Cycle Periodic Periodic Periodic / Ad hoc Ad hoc
9. Leading ERP Providers
ERP now………………Extended ERP
Market Share of ERP in 2012
Market Size - 24.5 Billion USD
Growth of 2.2 % over 2011
SAP
25%
ORACLE
13 %
Sage
6 %
INFOR
6 %
MICROSOFT
5 %
10. Factors that cause an ERP to Fail
Employee Resistance
Lack of Top Management Commitment
Inadequate Training and education
Inadequate Requirement Definition
Inadequate Resources
Unrealistic Expectations of Benefits and ROI
Poor ERP package Selection
11. Factors that cause an ERP to Fail
Extensive Customization
Change Management
User Acceptance
Going Live is not the end of journey
Anticipation of performance dip after live
Failure of accommodating evolution of Business Process
Companies should anticipate a temporary dip in
performance after going live
13. Background of FoxMeyer
Business - FoxMeyer was the fifth largest drug wholesaler in the United States
(1995) with annual sales of about 5 billion US$ and daily shipments of over 500,000
items. The business of the company was principally in healthcare services.
Distribution - The company had 25 distribution centers located throughout
USA. It conducted business mainly through two operating units: FoxMeyer Corp.
and Ben Franklin Retail Stores, Inc. The latter was engaged in franchising and
wholesaling to the franchised stores; while the former was engaged in the
distribution to the individual units and chain stores and in the provision of
managed care and information-based services.
14. What others say about the
Failure
According to Christopher Cole, chief operating officer at
Pinnacle, the FoxMeyer mess was "not a failure of
automation. It was not a failure of commercial software
per se. It was a management failure". Perhaps
management had unrealistic expectations.
Did management expect technology to be a "magic
bullet"? In reality, it was the opposite.
FoxMeyer was driven to bankruptcy in 1996, and the
trustee of FoxMeyer announced in 1998 that he is suing
SAP, the ERP vendor, as well as Andersen Consulting, its
SAP integrator, for $500 million each.
15. Project -Details
With the goal of using technology to increase efficiency,
the Delta III project began in 1993.
FoxMeyer conducted market research and product
evaluation and purchased SAP R/3 in December of that
year.
FoxMeyer also purchased warehouse-automation from a
vendor called Pinnacle, and chose Andersen Consulting to
integrate and implement the two systems.
Implementation of the Delta III project took place during
1994 and 1995.
16. Project Risks
Customer Mandate A definite morale problem among the
warehouse employees. This was not surprising, since the
project's Pinnacle warehouse automation integrated with
SAP R/3 threatened their jobs of FoxMeyer employees.
This distrust grew so large that disgruntled workers
damaged inventory, and orders were not filled, and
mistakes occurred as the new system struggled with the
volume of transactions $34 million worth of inventory
were lost.
17. Project Risks Continued….
Risky Scope – FoxMeyer was an early adopter of SAP R/3.
After the project began, FoxMeyer signed a large contract
to supply University Health System Consortium (UHC).
This event exacerbated the need for an unprecedented
volume of R/3 transactions. Although, prior to the
contract, testing seemed to indicate that R/3 on HP9000
servers would be able to cope with the volume of
transactions, in 1994 R/3 could process only 10,000
customer orders per night, compared with 420,000 under
FoxMeyer's original mainframe system
18. Project Risks Continued….
Execution - of the project was an issue due to the
shortage of skilled and knowledgeable personnel.
FoxMeyer did not have the necessary skills in-house and
was relying on Andersen Consulting to implement R/3
and integrate the ERP with an automated warehouse
system from Pinnacle. Although at the height of the
project there were over 50 consultants at FoxMeyer,
many of them were inexperienced and turnover was
high.
19. Project Risks Continued….
Environment - FoxMeyer must have realized the project
was in trouble, its perceived dependence on consultants
and vendors prevented it from seeing how it could gain
control. Since FoxMeyer was competing on price, it
needed a high volume of transactions to be profitable. Yet
with the UHC contract "the focus of the project
dramatically changed", contributing to rising project costs
(eventually over $100 million), lowering FoxMeyer's
already narrow margins and erasing the profitability.
21. Factors Responsible - Planning
Poor selection of the Software -SAP R/3 was originally designed for
manufacturing companies and not for wholesalers, especially those doing large number of
transactions. R/3 has never been used by a distributor until that time. It lacked many
requirements needed for successful wholesale distribution.
No consideration of other consultants’ advice— FoxMeyer did
not listen to other consultants’ advice in the early stage of the project, A Chicago-based
consultant firm warned FoxMeyer that SAP would not be able to deliver what FoxMeyer
needed. FoxMeyer selected SAP mainly because of its reputation.
Lack of contingency planning—there was no contingency planning to deal
with changes in the business operations. For example, a major customer, Phar- Mor Inc. that
accounted for more than 15% of FoxMeyer’s business, declared bankruptcy shortly after
FoxMeyer’s launched SAP. Much of the Phar-Mor business was gone to competitors.
No end user involvement—The project was done using a top-down
approach.
22. Factors Responsible - Implementation
No restructuring of the business process was done—SAP was not
fully integrated because FoxMeyer was incapable of reengineering their business processes in order
to make the software more efficient.
Insufficient Testing—Due to the rushed schedule, some modules testing was skipped.
Besides, the system was not properly tested to identify its shortcoming
in handling large amounts of orders. There was inadequate testing and insufficient time to debug the
system to ensure its functionality.
Over-ambitious project scope— the project team members and information
system staff were unfamiliar with the R/3 hardware, systems software and application software. The
project scope was enlarged with simultaneous implementation of a $18m computerized warehouse
project.
Dominance of IT specialists’ personal interest—since the project was
new for the wholesaling industry, the IT specialists wanted to learn the system and secure their
employment in the SAP technology business. They placed their personal interest of getting
experience in SAP implementation over the company’s interest in getting suitable software
technology.
23. Factors Responsible - Implementation
Poor Management support—initially management were supportive and
committed to the project. However, once the implementation started, management was
reluctant to acknowledge the system problems. Management failed to understand the
complexity and risks in the process and agreed to have 90 days early implementation although
the system was not fully tested. Management failed to recognize the timelines and resources
required in the implementation process.
Lack of end-user cooperation—the user requirements were not fully
addressed and there was no training for end users. Employees had no chance to express their
priorities and business needs. Workers especially at the warehouses were threatened by the
implementation. The automated warehouse created many problems. Employee morale was
low because of the layoffs. They knew their jobs were soon to be eliminated. As the end users
were not fully involved, they felt they didn’t have the ownership for the project and did not
work closely with the IT specialists to solve problems.
24. Other Factors
Social Factors - It is likely that Andersen Consulting and SAP needed to
externally justify the Delta project. They probably did not consider de-
escalating the project since abandonment would not be good publicity.
Moreover their "norms for consistency" were such that perseverance with
project problems usually paid off for them.
Organizational Factors - Both FoxMeyer's CEO and CIO were strong
advocates of the project. However in February 1996, Thomas Anderson,
FoxMeyer Health's president and CEO (and champion of the company's
integration/warehouse-automation projects) was asked to resign due to
delays in the new warehouse and realizing the SAP system's projected
savings. A change in management is often needed for de-escalation. But it
was too late for FoxMeyer.
25. Impacts of ERP Failure
Less Production
Thomas Anderson, FoxMeyer Health's president and CEO was
asked to resign due to delays in the new warehouse and
realizing the SAP system's projected savings.
FoxMeyer was driven to bankruptcy in 1996, and the trustee
of FoxMeyer announced in 1998 that he is suing SAP, the ERP
vendor, as well as Andersen Consulting, its SAP integrator, for
$500 million each (Caldwell 1998, Stein 1998).
26. Lessons Learned: Planning
Software Selection:
Project steering committee should have a high level of technical and
operational expertise in software selection process
Contingency Plan:
Develop contingency plan of how to survive in case of system failure
Stipulate clearly the roll back procedures in case of deploying any new
system
Stakeholder’s Involvement:
An ERP project should get involvement of all stakeholders, including the
end users and customers
All stakeholders should understand the goals and expectations of the
project and needs to be encouraged to voice-up their opinion
Impact analysis should be done to determine the nature and extent to
which different units will be affected.
27. Lessons Learned : Implementation
Inclusion of the necessary business process reengineering
ERP cannot be expected to improve profits without the prior accomplishment of improved
supply chain planning systems, enterprise optimization systems, customer relations
management, transportation and logistics management and warehouse management
ERP installation is not the end process;
Thorough testing
Develop an organized comprehensive testing plan, encourage user participation in the testing,
and make sure adequate testing scenarios are conducted to the new system.
Realistic project scope
Scope should be clearly identified with realistic time targets.
Close Monitoring of project status
Top management and the implementation team should have a close communication with the
software vendor, consulting firms and IT people, ensuring that the project progress is running
on the right track, and the project goals are continuously adhered to.
Seek end user support
Employees should be well trained in software.
Identify the change agents and create a high morale to meet the new challenges.
Post implementation review
Develop quality assurance and control programs to ensure system checks are in place.
Develop business metrics to measure project’s intended benefits versus what has actually been
achieved,
28. Conclusion
Is this an extreme case? Clearly. Is this unusual? Sadly, no.
• Implementations of ERP systems are struggling throughout the
world.
• They take too long, cost too much and fail to deliver the promised
benefits of competitive advantage and cost reduction.
• Despite high investment required to implement ERP systems,
statistics show that more than 70 percent of ERP implementations,
whether self-created or designed by established ERP software
vendors, fail to achieve their corporate goals.
29. Conclusion .. continued
In a landmark study, the Standish Group, a market research company specializing in software
and electronic commerce, looked at implementations in companies with more than $500
million in revenues. The study found that the average cost overrun was 178 percent; the
average schedule overrun was 230 percent of original expectations, and the average slide in
functional improvements was an astonishing 59 percent deficit.