Tuesday, February 5, 2008

Should I recommend implementing an ERP?

A friend of mine is taking a Management Consulting Class as part of his MBA curriculum and he asked me an interesting question:

"My client has not upgraded their IT systems in over 15 years, and in fact, they do not even have a CIO. Should I recommend to implement an ERP system? Do we tell them to rip out the old system?"

This is a classic consulting problem. A majority of my consulting experience is in SAP ERP implementation consulting, so I have seen a number of fresh installations; some good and some bad...

So the short answer is, yes you should recommend implementing an ERP system, if you can find a good ROI on the investment. Furthermore, a good consultant will know how to stage the implementation so that the impact to the business is minimal.

In a case like this, it appeared that there were a lot of home-grown applications, and many outdated systems. It leaves me to think that there are probably a lot of "IT Application Kings" in the IT organization. An IT Application King is basically the original creator of the software application, and has been gradually improving it and maintaining it over the years. This is pretty common in many businesses of all sizes. Basically, everything needs to go through the IT Application King, and he is invincible. He cannot be laid off, and in many instances he cannot take much time off. The program and documentation on these systems resides in the creator's mind, and if something were to happen to them (i.e. they get hit by a bus), this could potentially create a huge loss to the business, especially if it is a business critical application, such as an inventory control software or a sales order entry system.

So to these Kings, the thought of implementing a "Vanilla ERP" system is like a death sentence. So a consultant will need to be prepared for severe pushback from this group.

Furthermore, an ERP implementation is a HUGE expense. Can you gain enough efficiencies in business processes to get a reasonable ROI? This topic has been heavily debated, so a few things to look for in an organization before even thinking of recommending an ERP implementation are:

  1. How many people are maintaining the current homegrown applications?
  2. How much time is being spent on financial month end close?
  3. How much time is spent maintaining the interfaces between the disparate systems?
  4. Can this business fit in a relatively uncustomized ERP solution from SAP or Oracle?
  5. If the company grew through acquisitions, how good is the transparency between the separate systems? For example, is it easy to pull together a consolidated financial statement?
  6. Are there opportunities to save in taxes if we put the whole company on a single system and reported financials through a country with lower taxes? Caviot: This implies that a majority of the sales and business happen in this country you are considering.
  7. Are there Sarbanes-Oxley (SOX) requirements that the company needs to meet? If so, what is the cost of applying SOX principles to their existing system versus implementing a new ERP system?
  8. Are there other legal or regulatory reasons for implementing the new ERP system?
  9. Will the ERP system improve operations? For example, will it take less time to enter in a sales order? Or, will it take less people to execute a business process chain?
  10. Will the ERP enable more efficient flows with suppliers/vendors and customers?
  11. Can an ERP help improve supply and demand forecasts?
  12. Can you reduce inventories by utilizing a new ERP?
  13. If the company is interested in doing business in many emerging markets, will the ERP system help manage the documentation/forms required to sell to these markets?

For now, that is what I can think of to answer my friend's question. I'll add more to this blog as I think of more reasons to implement an ERP system.

First Blog

Hello everyone, this is my first blog! After reading so much about blogging and web 2.0, I thought I would try to make my contribution. Here is a little info on me:

I've been consulting for the past six years, and decided to take a break to persue my MBA. I thought that six years was a good breaking point, and I knew that I always wanted to get my MBA, and I'm quite glad about my decision.

I was a consultant for one of the largest consulting companies in the world, and to a certain degree, I feel like I got my first MBA from this company. I've been very fortunate to learn as much as I did. Of course I didn't realize this as I was working for this company, but now that I am able to take a step back and reflect, I now realize that working for this company has really given me a leg up in the second MBA I'm persuing right now.

As I'm getting close to finishing my MBA, the consulting itch is back again, and I thought I would use this blog as a tool to talk about "A Consultant's Adventure." I will talk about the highs and lows of being a consulting, some tricks I learned down the way in successful consulting, travel guidance, and to talk about some of the crazy adventures I've had.

Also, a number of my classmates have asked me about consulting, so I thought this could be a forum to answer these questions, so that more people can benefit from it.