Earlier this month, Waste Management (WM) upped the ante in its lawsuit against SAP to $500 million. The root of WM’s claim is that it was allegedly deceived and defrauded by SAP during the ERP selection and implementation phases.
If your organization is planning to implement ERP software without restructuring its operations, you can stop reading right now. In fact, you may as well take the money you’re planning to spend on the project and throw it in the bin.
ERP implementation projects are major cross-functional undertakings. Most failures can be attributable to ineffective project teams and poor testing. Learn best-practices to establish effective governance structures and rigorous piloting.
ERP implementation failure is a pretty easy topic to write about – fresh material is delivered to my door almost daily. Consider, for example, the California County of Marin’s recent $30 million lawsuit against Deloitte Consulting LLP.
In that case, Marin County hired Deloitte to implement an SAP ERP system. Marin spent $18.6 million on system and implementation costs. For all of that money, what did it get? A malfunctioning system, administrative lock-ups and headaches.
Last week, I introduced you to using Milestone Deliverables – our firm’s proprietary ERP project management methodology – to drive ERP implementation success. We covered the importance of ERP project planning, business process mapping and systems testing.
Our firm developed the Milestone Deliverables ERP implementation project management methodology over a 33-year period. It is now used to deliver ERP success in more than 40 countries.
This short series of articles is designed to introduce you to the key components of our methodology – the components that are necessary to drive ERP implementation success. This first article focuses on the importance of project planning, business process mapping and system testing.
Imagine waking up one day to find out that your company’s supply chain has ground to a halt, making it impossible to fulfill $100 million worth of orders. For Hershey’s confectionary manufacturing and distribution operations, this nightmare came true in 1999. Read this case study on Hershey’s ERP implementation failure. Learn about the importance of ERP system testing and project scheduling.
There are four key team and governance causes of ERP implementation failure. If you wait until implementation to mitigate these risks, you might already be too late. Many take months
Multi-company and enterprise-wide implementations bring their own unique challenges and requirements. When planning a project, it’s important to map how the data and processes will (or will not) flow across entities. It’s also important to define cross-divisional teams that might need to provide input.
Read-on to learn the keys to successfully managing a multi-company ERP implementation project.