ERP Implementations- Predictable Disasters!

02 August 2009 Internet, IT & e-Discovery Blog Blog
Authors: Peter Vogel

A recent review of a vendor’s proposed contracts for a new ERP (Enterprise Resource Program) system reminded me why so many implementations fail and lead to litigation – vendors generally underestimate the scope of the systems (on purpose to keep the price tag low, or just don’t know what they are doing) and as a result a large number of ERP implementations are failures. Actually Y2K may be the blame since as 2000 approached many companies decided to replace aging systems, many of which were silo applications systems did not share data (like HR not sharing data with accounting). So SAP, Oracle, PeopleSoft (now part of Oracle), and many others offered unified systems to allow companies to share data between all business operations and activities referred to as ERP systems.

The Ten Commandments of IT Contracts Apply

Since an ERP system includes software, hardware, implementation services, and on-going support clearly I believe that my Ten Commandments of IT Contracts apply. My Ten Commandments are based on negotiating and litigating hundreds of IT contracts:

1st Commandment No Computer Project is ever completed on time
2nd CommandmentNo Computer Project is ever complete
3rd CommandmentIf you cannot see the software, it does not exist
4th Commandment New versions of operating systems never work
5th Commandment There are no Industry Standards
6th CommandmentDo not buy brand new hardware
7th Commandment Do not buy brand new software
8th CommandmentSales people have answers to every question
9th Commandment Sales people know absolutely nothing
10th Commandment Individuals who negotiate contracts are never around later

After posting my blog on the Ten Commandment two clients offered Commandments 11 and 12:

11th CommandmentAny IT development project large enough to have its own acronym name (BEST, BIGGEST, CYCLONE, etc) will fail
12th CommandmentBefore every project, select a scapegoat and do not invite that person to meetings

Surely some readers may have others Commandments to offer, so please let me know.

What’s Different about ERP Implementations?

Often times a third party is responsible for the ERP implementation and on-going support, and the software vendor only offers a license. Depending on the software and vendors in any particular market this may be the norm. But the ideal circumstance is that the software vendor for the ERP system also does the implementation and on-going support, but prudent contract negotiations are still required.

The EPR vendor whose contracts I reviewed recently included two agreements, one a license and another for system implementation. However if the implementation does not go well, the customer should not be stuck with the software. So my advice to the customer is to sign one agreement for all software, implementation services, and on-going support. Other critical components were missing from this proposed vendor agreement – a schedule of events and a statement of work. Customers should never sign contracts to acquire ERP systems if there is no precise schedule of events and clear responsibilities of the parties in a statement of work. Detailed schedules and complete statements of work provide help because this forces the parties to think through what will happen, and payments can be based on the completion of major milestones in the schedule based on the statement of work.

With a little planning and foresight disastrous ERP implementation systems can be avoided, but it’s critical that customers user lawyers and consultants who have been through the wars to avoid major disasters.
 

This blog is made available by Foley & Lardner LLP (“Foley” or “the Firm”) for informational purposes only. It is not meant to convey the Firm’s legal position on behalf of any client, nor is it intended to convey specific legal advice. Any opinions expressed in this article do not necessarily reflect the views of Foley & Lardner LLP, its partners, or its clients. Accordingly, do not act upon this information without seeking counsel from a licensed attorney. This blog is not intended to create, and receipt of it does not constitute, an attorney-client relationship. Communicating with Foley through this website by email, blog post, or otherwise, does not create an attorney-client relationship for any legal matter. Therefore, any communication or material you transmit to Foley through this blog, whether by email, blog post or any other manner, will not be treated as confidential or proprietary. The information on this blog is published “AS IS” and is not guaranteed to be complete, accurate, and or up-to-date. Foley makes no representations or warranties of any kind, express or implied, as to the operation or content of the site. Foley expressly disclaims all other guarantees, warranties, conditions and representations of any kind, either express or implied, whether arising under any statute, law, commercial use or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Foley or any of its partners, officers, employees, agents or affiliates be liable, directly or indirectly, under any theory of law (contract, tort, negligence or otherwise), to you or anyone else, for any claims, losses or damages, direct, indirect special, incidental, punitive or consequential, resulting from or occasioned by the creation, use of or reliance on this site (including information and other content) or any third party websites or the information, resources or material accessed through any such websites. In some jurisdictions, the contents of this blog may be considered Attorney Advertising. If applicable, please note that prior results do not guarantee a similar outcome. Photographs are for dramatization purposes only and may include models. Likenesses do not necessarily imply current client, partnership or employee status.

Authors

Related Services