OM in the News: 3 Rules of Thumb for ERP Implementation

ERP-GraphicIn our discussion of ERP in Chapter 14, we write: “ERP systems are expensive, full of hidden issues, and time-consuming to install.”  Adds Apptricity (Sept. 16, 2013):  “ERP implementations too often turn into their own little hellish experiences for companies large and small.” Getting all of a company’s various data systems to talk to each other efficiently, accurately and instantly share data makes great sense. But many companies still don’t have effective and efficient ERP systems in place. So what can a firm that do to successfully implement an ERP system?

Apptricity provides these 3 old adages:

  1. Look Before Your Leap.  ERP systems are complex, touching on every department, worker, business activity, form, and data set. That means that every need, contingency, possibility, and potential barrier must be addressed in the planning process. Failure to do that invariably leads to frustrating and expensive delays.
  2. Too Many Cooks Spoil the Broth. Managing an ERP implementation presents similar challenges. If there are too many chefs involved in development of the ERP system, the end result is likely to be system that can do lots of things only moderately well – and often at a much higher cost than anticipated. But if the planning doesn’t include the CEO, CFO, and CIO, the result is likely to be a system with gaping holes. It is critical that these execs properly define the scope and budget of an implementation and then assemble a team that includes the right workers.
  3. Be careful what you ask for. Many companies choose a vendor to design and install a system based on the dual promise that what it is being bought is a proven, bolt-on system that can still be customized to meet the company’s needs. The problem is that instead of bolting on a proven system and customizing only 15-20% of it, what typically happens is that 50-85% of the bolt-on ERP system ends up being customized. That dramatically inflates the cost of the project and creates lengthy delays.

It all goes back to the planning process. Once a company determines what its scope and budget for an ERP system should be, management should firmly commit the company to staying within that scope and budget.

Classroom discussion questions:

1. Why are ERP systems important?

2. Why are the systems hard to implement, and why do they fail to deliver so often?