Causes of ERP Failures

Here is an article that zooms right into the reasons for why ERP implementations fail:

Causes of ERP Failures
by: Bruce Zhang

ERP is the acronym of Enterprise Resource Planning. Multi-module ERP software integrates business activities across various functional departments, from product planning, parts purchasing, inventory control, product distribution, to order tracking. ERP has transformed the way multi-billion dollar corporations conduct their businesses. Successful implementation of ERP systems could save tens of millions of dollars and increase employee satisfactions, customer satisfactions and sustain competitive advantages in every-changing marketplace. Corporate executives are often perplexed by the stories that how reputable corporations (Hershey Foods) have failed miserably and lost ten of millions of dollars in their ERP endures.

The failures of ERP projects are preventable if we can identify the common causes of the failures regardless the companies and industries that implement them.

An ERP system is the combination of ERP software, the business processes that the ERP transforms, the users of the ERP system, and the computer systems that run the ERP applications. The failures of a ERP project is often the result of the failures in one or more of those four components. The failures in computer systems (hardware and operating systems) are much easier to identify and to fix, so we’ll examine the failures in software implementation, business process and user acceptance.

Failure of ERP Software Implementation

Module-based ERP software is the core of ERP systems. Most ERP projects involve significant amount of customizations. Packaged ERP software modules have built-in functionality that work in a standard and simplified enterprise environment. However, every organization is unique in data requirements and business processes. It is the customizations that transform packaged ERP software into ERP software that meets organizations’ individual business processes and operations. Long and expensive customization efforts often result the pass of release deadline and budget overrun. Customizations may make the software more fragile and harder to maintain when it finally goes to production. Major changes may be required in the later stage of the implementation as a result of incomplete requirements and power struggles within organizations

Why New Systems Fail: An Insider’s Guide to Successful IT Projects

The integration of ERP systems (http://www.sysoptima.com/erp/erp_integration.php) with the IT infrastructures also challenges ERP project teams. The use of appropriate implementation methodologies can often make or break a ERP project. (http://www.sysoptima.com/erp/implementation_methodologies.php)

Failure of Accommodating Evolution of Business Processes

According to Anthony, R. A, business processes fall into three levels – strategic planning, management control and operational control. Organizations continuously realign their business processes of all levels in response to the ever-changing market environment. Many ERP systems aren’t flexible enough to accommodate evolution of business processes. many ERP system need a major overhaul in every a couple of years.

Failure of User Acceptance

The users of ERP systems are employees of the organizations at all levels. ERP projects usually modify the company’s business processes which create extra workload for employees who use them initially. They may not think that the workflow embedded in the software are better than the ones they currently use. Ongoing end-user involvement and training may ease the difficult in organization’s adaptation of new systems and new business processes.

About The Author

Bruce Zhang has over 10 years experiences in developing and implementing ecommerce and ebusiness systems in various industries.

He operates a website http://www.sysoptima.com that automatically aggregates the news and new articles in e-business (ERP, CRM,

Supply Chain Management and Knowledge Management) from over 50 sources daily (http://www.sysoptima.com/newsbot/) to help corporate executives, professionals and consultants to keep up with the latest development in enterprise software market. The website offers a knowledge base for understanding business software from a systems perspective.

How to Negotiate and Purchase Your ERP System

ERP Negotiations Explained

There are many sources of information on how to select and implement software, but there is little information on how to negotiate and make the purchase of the software. The uninformed can spend thousands of dollars more than they need too by walking into ERP negotiations unprepared. Those that know the “tricks” of the trade can save themselves enough to pay for several modules or a good chunk of the implementation costs.

The first thing in ERP Negotiations to keep in mind is timing. When you buy the system timing is key. As this article is being written, the clock is ticking down to the end of the year. This is an opportune time to purchase a system. Even more advantageous is making the purchase at the end of the software vendor’s fiscal year. Vendors are hungry for the deal. The need to make the numbers for the year. They want to do whatever it takes to boost their sales figures and show a successful quarter. Actually, any quarter end will do, but year end is the time when bonuses are given and certain sales incentives are taunting the software salesperson.

The next thing to do in ERP Negotiations is to keep your options open. Even if you find the best whizzbang system that does exactly what you need, there are probably several systems that will work for you. Keeping your options open and communicating that to the salesperson will only make them work harder for the deal. Even if you know you will buy their software, let them know how much better or cheaper the competition is. Give them a reason to work for the deal.

ERP Negotiations around software pricing

When negotiating software pricing, keep in mind that you may not need all of the licenses up front. You can delay purchasing the entire suite of user seats until you are ready to go live. Get enough to cover your testing and implementation phases and be sure to lock in the pricing for a year or for the planned duration of the implementation.

Don’t forget that the implementation and how it will occur is negotiable. The terms of payment are negotiable. Who will be on the project from the vendor’s side is also a point of discussion and can be changed. There are many things that you can plan out and ask of the software provider or reseller.

Considerations for ERP Negotiations

Remember that most everything is negotiable. Software price, implementation rates, duration, and sometimes even annual maintenance contracts (those these are usually the most difficult). Perhaps negotiating when the maintenance begins will be possible. If you are splitting the user seats, have the maintenance pro-rated during the implementation phase.

Unlike the year 2000 preparations, there usually isn’t an absolute deadline as to when you need to purchase, so if you must, hold off for a month or two, if it is to your advantage. Or, tell the salesperson that you plan on doing so, so what can he/she do now?

Properly planned, the negotiation will more than pay for the time spent doing it correctly. Following the vendor’s lead will lead you to an overpriced system. Keep the money in your company’s bank, not the software company’s. Some negotiation strategies will work and some will not. The key is to remember that you are driving the sale. Get what you want at the price and terms that is fair to you.

Additional resources:
http://www.managingautomation.com/maonline/channel/exclusive/read/4063236

http://dealarchitect.typepad.com/deal_architect/enterprise_software_negotiationsbest_practices/index.html

File as: ERP Negotiations

Causes of ERP Failures

by Bruce Zhang

The failures of ERP projects are preventable if we can identify the common causes of the failures regardless the companies and industries that implement them.

: Image by Behrooz Nobakht via Flickr

ERP Failures -Software Implementation

ERP Failures – Failure of Accommodating Evolution of Business Processes

According to Anthony, R. A, business processes fall into three levels – strategic planning, management control and operational control. Organizations continuously realign their business processes of all levels in response to the ever-changing market environment. Many ERP systems aren’t flexible enough to accommodate evolution of business processes. Many ERP system need a major overhaul in every a couple of years.

ERP Failures – Failure of User Acceptance

Bruce Zhang has over 10 years experiences in developing and implementing ecommerce and ebusiness systems in various industries. He operates a website www.sysoptima.com that automatically aggregates the news and new articles in e-business (ERP, CRM, Supply Chain Management and Knowledge Management) from over 50 sources daily (www.sysoptima.com/newsbot/) to help corporate executives, professionals and consultants to keep up with the latest development in enterprise software market. The website offers a knowledge base for understanding business software from a systems perspective.

Another Related ERP Failures post

Causes of ERP Failures

Software as a Service

From ManagingAutomation.com:

One of the most frustrating aspects of today’s IT-dependent manufacturing environment is the challenge of deploying and maintaining enterprise applications ranging from enterprise resource planning (ERP) and supply chain management (SCM) to customer relationship management (CRM) software. A significant proportion of new application deployments fail to achieve their original objectives, and even successful deployments can often cost far more to maintain than expected.

Depending on the complexity of the deployment, enterprise applications can take months or even years to implement, and they can consume the majority of the IT staff’s time just to keep them up and running. And, most major upgrades typically require additional investments in new servers, storage and other IT infrastructure upgrades.

Manufacturers trying to keep pace with escalating competition can no longer afford the extended lag-time of lengthy application deployment cycles. They can also ill-afford the ongoing infrastructure and staff costs to simply maintain their existing applications.

These frustrations have made the manufacturing industry ripe for a new approach to applications called Software-as-a-Service (SaaS). Read More about software as a Service