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.

Blackberry goes ERP

Now that everyone is breathing a sigh of relief after RIM’s legal settlement:
Blackberry goes ERP
by Cliff Saran
Tuesday 7 March 2006

Research in Motion has given its Blackberry Enterprise Server (BES) support for web services to enable wireless access to enterprise systems such as SAP.

The company’s aim with the 4.1 release of BES is to move Blackberry beyond push e-mail. It has introduced a development tool called MDS 4.1 to help businesses create links…Blackberry goes ERP

Manufacturers raid piggybanks for ERP and RFID – Applications – Breaking Business and Technology News at silicon.com

This is an older article, but has some good points on how RFID and ERP will be used in the coming year. The key point that it makes is that middle ware is one of the stepping stones that will link the two systems together.

Currently middle ware or the software between the RFID system and the ERP is the weakest link. This will get better but that is where the dollars are being spent to make the integration happen.

—-

Analyst house Datamonitor has found that by 2010, the market for radio frequency identification will top $6bn, as pharmaceutical, consumer packaged goods and automotive industries start to spend on tracking their products.

Datamonitor predicts the boom will really take off at the latter half of next year, as initial pilots are wound up, results analysed and full-scale rollouts started.

The UK and Germany will be leading the way on RFID spending at least until 2010.
Manufacturers raid piggybanks for ERP and RFID – Applications – Breaking Business and Technology News at silicon.com
Manufacturing CIOs will be spending their budgets on RFID and ERP this year.

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

ERP Overview

This ERP Overview covers What is ERP, Brief history of ERP, Why is it necessary, Market Leaders and the future of ERP. What is ERP? Enterprise Resource Planning or ERP is an industry term for integrated, multi-module application software packages that are designed to serve and support multiple business functions. An ERP system can include software for manufacturing, order entry, accounts receivable and payable, general ledger, purchasing, warehousing, transportation and human resources. Evolving out of the manufacturing industry, ERP implies the use of packaged software rather than proprietary software written by or for one customer. ERP modules may be able to interface with an organizations own software with varying degrees of effort, and, depending on the software, ERP modules may be alterable via the vendors proprietary tools as well as proprietary or standard programming languages.

Brief History of ERP The focus of manufacturing systems in the 1960s was on Inventory control. Most of the software packages then (usually customized) were designed to handle inventory based on traditional inventory concepts. In the 1970s the focus shifted to MRP (Material Requirement Planning) systems that translated the Master Schedule built for the end items into time-phased net requirements for the sub-assemblies, components and raw materials planning and procurement.

In the 1980s the concept of MRP-II (Manufacturing Resources Planning) evolved which was an extension of MRP to shop floor and Distribution management activities. In the early 1990s, MRP-II was further extended to cover areas like Engineering, Finance, Human Resources, Projects Management etc i.e. the complete gamut of activities within any business enterprise. Hence, the term ERP (Enterprise Resource Planning) was coined.

Why is it Necessary? By becoming the integrated information solution across the entire organization, ERP systems allow companies to better understand their business. With ERP software, companies can standardize business processes and more easily enact best practices. By creating more efficient processes, companies can concentrate their efforts on serving their customers and maximizing profit.

Market Leaders The top five ERP vendors, SAP, Oracle Corporation, Peoplesoft, Inc. (now Oracle Corp.), JD Edwards & Company, and Baan International, account for 64 percent of total ERP market revenue. These vendors continue to play a major role in shaping the landscape of new target markets, with expanded product functionality, and higher penetration rates. SAP dominates the $6.7 billion ERP applications market in Europe with 39% market share. Oracle and PeopleSoft come second and third respectively, followed by SAGE Group and Microsoft Business Solutions.

The Future of ERP Industry analysts expect that every major manufacturing company will buy the software, which ranges in cost — with maintenance and training — from hundreds of thousands of dollars for a small company to millions for a large company. AMR Research of Boston says consolidation among the major players will continue and intensify. ERP vendors are expected to put more effort into e-commerce, CRM and SCM initiatives, with leaders redirecting between 50% and 75% of their R&D budget to these projects.

According to Gartner research group, the rapid evolution of ERP has already lead to a new corporate must-have, ERP II, which is supposed to help businesses gain more competitive edge in the future. The major difference is that ERP II involves collaborative commerce, which enables business partners from multiple companies to exchange information posted on eCommerce exchanges.

In the next tutorial we will talk about popular ERP Products and the Modules and Application related to them.

For more visualization of this article along with the screen shots and more visit with step by step instructions, http://www.exforsys.com/content/category/17/260/342/

Exforsys is a community of developers specializing in C, C++, C#, Java, J2EE, .NET, PeopleSoft, SAP, Siebel, Oracle Apps., Data warehousing, Oracle/SQL Server/DB2 and Testing. Please visit http://www.exforsys.com for more tutorials and for Interview questions http://www.geekinterview.com is an open database.

ERP is in the picture for midsize manufacturers

Small and midsize manufacturers are increasing IT investment because they don’t have the IT architecture needed to compete in a demand-driven world. For many, this means going back to the basics: an ERP system that standardizes business processes, extends the company’s reach, and reduces overhead.

In a 2005 study of more than 550 companies’ ERP investment plans, only 27 percent of small companies “those with fewer than 500 employees” currently …more… (requires registration)

ERP Tiers: What Tier are you in?

ERP vendors and consultants are always trying to classify you as a company into distinct ERP tiers. What is your vertical industry? What is your revenue? How many employees? These are all questions of where you fit within their offering. Others talk about ERP Tiers. What are tiers? ERP Tiers are classifications of software by the size of the company the fit. Let’s break it down:

ERP Tiers: Tier 1 ERP

Tier 1 ERP software is software for the large enterprise. This includes multi-site, multi-national corporations. Typically the Tier 1 customer is a company with revenues in excess of $200 million dollars and has several sites, probably geographically dispersed and in multiple companies. There used to be what was known as JBOPS. JD Edwards, Baan, Oracle, People Soft, and SAP. Now that Oracle purchased People Soft, who had just prior purchased JD Edwards, the map has left the three primary ERP vendors: SAP, Oracle and Baan. These are your Tier 1 ERP players. Although not yet quite a Tier 1 ERP player, Microsoft with their Axapta (now called Dynamics AX) is pushing to be a Tier 1 software system.

ERP Tiers: Tier 2 ERP

The Tier 2 market is the largest of all the tiers in terms of the number of potential customers. This is the mid-sized tier. The customers of Tier 2 software usually are in the $20 million to $200 million dollars. They are usually just a few localized sites. For example a company that has a main office in California, with a manufacturing facility in Ohio and a distribution outlet in Texas would be a typical Tier 2 client. Often though, Tier 2 customers are single site. The main indication is the size of the company by revenue. This is important in that you probably will not find more than a couple hundred users all said and done. More likely though it is less than 100 users. Some references to the Tier classifcation refer to the number of employees. This is really not a good indicator as sometimes smaller companies with labor intensive processes may only have a few computer users.

Software in this class includes QAD, Infor’s Syteline, Microsoft Navision (Dynamics NV), ABAS, Glovia, Best’s MAS500, Epicor Vantage, and a host of others.

The problem that the Tier 2 vendors are facing is that the Tier 1 players are pushing down into this space. The market in the Tier 1 arena is small and to continue to expand their businesses, the Tier 1 players are reducing cost, simplifying transaction sets, and offering outsourced hosting and other incentives to allow a medium sized company to have the broad features of the Tier 1 package.

ERP Tiers: Tier 3 ERP

Tier 3 software is designed for single site customers of under $40 million dollars. These are companies with 5 to 30 users and have less demanding needs. Often these companies have just grown out of the Tier 4 packages and are looking to expand their capabilities. These companies tend to be the family run or small corporations.

Software in this market space includes Lily’s Visual Manufacturing, Intuitive Manufacturing, Microsoft Great Plains (Dynamics GP), DBA Software and Best’s MAS200.

ERP Tiers: Tier 4

Tier 4 software is your basic accounting systems. These include Peach Tree, Accpac and Quickbooks. This is the startup to $2 Million dollar software.

The next time you hear a vendor referring to a Tier 2 client, you will understand now that they are referring to a midsized company with just a couple plants. It is amazing how in the IT industry acronyms and categories spring up and every assumes they know what the other is referring to.

An interesting article is the segmentation of ERP into two tiers. You can read more in this publication: The rise of two-tier ERP: what it is and what it means.(TECHNOLOGY)(enterprise resource planning ): An article from: Strategic Finance

ERP Tiers

ERP and Lean

Chris Shaul

Today, many ERP vendors are offering Lean Manufacturing modules in their solutions. These modules propose to assist companies in their lean effort. The real question is to what degree will these modules be used. Can a traditional manufacturer going to a lean model utilize a lean software tool immediately? When implementing an ERP system, process redesign is a must. The change that must occur in order to support an ERP system can be tremendous. But can a company bite off and digest all of the changes? Which should be done first, lean or ERP? These are all some of the questions that a typical manufacturing manager who is about to embark on an ERP implementation might ask.

First, lets define a few things. Lean is the removal of waste within a process and the concept of pulling items to a demand. It is also known as the Toyota Production system as it was developed and refined by Toyota in Japan. ERP is a business process enabled by software tools. It is not a software project! ERP streamlines your information flow such that it parallels your process flow. ERP works to build product to a forecast and then execute a production plan and inventory purchases synchronized to meet the predicted and actual demand. Lean, on the other hand, uses a pull system to meet an actual customer requirement. Lean uses the philosophy of smaller batches and reduction in non-value-added activities to create a much shorter lead time, thus delivering faster to a customer. ERP does not by its’ nature drive efficiencies in the production process. It only provides planners with information on what is going on and allows them to plan faster. If the process is broken, then automating it with the use of ERP will only highlight the problems.

What is the answer? The answer for many is to implement lean as part of an ERP intiative. Some would say that it should be a predecessor to an ERP initiative. Lean purists will argue that you do not need MRP and MPS to drive the production. ERP folks will argue that MRP and MPS are essential to having parts in-house and suppliers coordinated with the production. The answer for most companies is a hybrid solution, where lean is driving waste from the production and supply chain process (although also in the above-the-shop-floor activities too), while ERP is being implemented, such that you are automating value added processes and not trying to replicated waste processes in your new system. MRP can be used to plan longer lead time items, or items with higher value, whereas a Kanban can be setup for the faster turning and less expensive items.

Working from the perspective of a hybrid model, lean principles and practices can be implemented just prior to the ERP initiative. Then during the ERP implementation, the lean concepts must be considered and utilized in the setup of the new system. Tools such as Value Stream Mapping can define areas for quick improvements. Then once those improvements are made, a process flow based on the future state model can be applied to the ERP system. For example, a production cell might be setup for a particular product line with kanban inventory control. This would change how you would define your production process in the ERP system. Better ERP systems can run in this hybrid mode of traditional MRP and modern Lean concepts. Some product lines might be more suited to the MRP/MPS method because of supply chain issues or because of the long lead times that are associated with the products. Other product lines might be easy to immediately switch to flow manufacturing. Because of this, you want a system that can handle both methods.

Using a hybrid model, you select and position the ERP system to work alongside your lean initiatives. By leaning out processes (above and below the shop floor), you are avoiding “automating the mess.” Doing so will shorten lead times, reduce inventory, reduce production costs, improve employee moral and streamline your ERP implementation. Be sure to choose an implementation partner that is familiar with lean and is able to work in a hybrid manner. What order should these two tranforming intiatives occur? It might be best to have the lean initiative lead the ERP intiative by a few months. Then begin to implement the system. But do not stop the lean transformation. That should now be an ongoing philosophy of continual improvement. Use it to your advantage during the ERP implementation. Doing so will only help you on go-live day.

References:

http://www.advancedmanufacturing.com/September00/informationtech.htm

http://www.lean-manufacturing-info.com

http://www.qad.com/company/newsroom/lean_value.html

http://www.mapics.com/software/EE/SyteLine/sl7-aps.asp

http://www.cmtc.com/

http://www.inventoryinc.com/complimentary.html

Chris Shaul is a Sr. IT Consultant and specializes about ERP selections and implementations.