Enterprise System Spectator blog: ERP and enterprise system vendor evaluation, selection, and implementation.

The Enterprise System Spectator

Tuesday, July 20, 2010

Countering aggressive software maintenance terms

There are two developments this week on the analyst front, dealing with the issue of software maintenance contracts. First, Gartner issued what it calls a "code of conduct" for vendors in crafting maintenance contracts. Second, my fellow Enterprise Advocate Ray Wang wrote a hard-hitting blog post dealing with what he calls "all-or-nothing" vendor maintenance agreements.

Code of Conduct
Gartner's press release on its code of conduct is quite detailed, outlining specific points that vendors should address in software contracts. In short, Gartner addresses the following points:
  • The right to regular, appropriate, predictable updates to software products
  • The right to clearly defined response times and stratified IT support levels based on application criticality and other business factors
  • The right to reasonable, predictable percentage ranges for yearly maintenance fee increases--or decreases--as well as long-term caps on increases in maintenance costs
  • The right to end or change support at any time for products that are not in use
  • The right to reasonable, predictable levels of support throughout product and contract life cycles
  • The right to reasonable, clearly defined maintenance and support for legacy systems
  • The right to explicit statement and approval of support details at the line-item level
There's not much to argue with in Gartner's recommendations. They provide a common-sense checklist for evaluating any software vendor maintenance relationship.

If I see any lack in Gartner's code of conduct, it is that it fails to mention the third-party maintenance option. Gartner is completely silent on this point. Some vendors these days are attempting to preclude customers from seeking service and support from third-parties. A customer-friendly maintenance contract should explicitly allow customer the right to go to a third-party provider for software maintenance, without jeopardizing warranties or future support.

"All-or-Nothing" Tactics
Ray's post drills down more deeply on one tactic that he sees vendors adopting these days--that is, forcing customers to put all software licenses under contract, and paying up any back maintenance, when buying new licenses.

Ray writes:
Conversations with 11 enterprise apps customers in the past two months indicate stricter enforcement of vendor "All or Nothing" maintenance policies. “All or Nothing” maintenance policies often require customers to put all licenses on maintenance or receive no maintenance from the vendor. These policies also prevent customers from reducing the number of licenses covered by maintenance. The rationale for these policies – customers could potentially apply the patches, bug fixes, and upgrades for covered licenses to the uncovered licenses.
At first glance, it all sounds fair and reasonable. But Ray points out four cases where such clauses can cost an organization dearly. For example, one division of a large company may drop maintenance on a software product. When another division then goes to buy additional seats for the same software product, the vendor invokes the contract to demand that the entire company pay up all maintenance, or forgo buying new seats. Read Ray's entire post to see how easily an organization can run afoul of such contracts.

Ray has some good advice for negotiating hard against such tactics, and--in contrast to Gartner--includes consideration of third-party maintenance options as a counter-tactic.

My take
Ray and I and other Enterprise Advocates Vinnie Mirchandani and Dennis Howlett, have been beating the drum for years on this issue of software maintenance contracts (see the Related Posts at the end of this post for a sample). The situation over these many years has not gotten better. In fact it could be getting worse. As traditional vendors see new license revenues shrinking in the current IT spending recession they become even more adamant at pursuing revenue from their installed customer base. This motivates them to push maintenance fees even harder. There are a few exceptions, such as RightNow's Cloud Services Agreement, Infor's Flex program, and Microsoft Dynamics' separation of maintenance fees from support fees. But the big players--SAP and Oracle in particular--show no signs of softening their approach.

I am coming to the conclusion that there are only two things that will ultimately shift the balance of power to something that is more equitable between vendors and customers. Unfortunately, both of them involve the legal system.
  1. A thriving third-party software maintenance industry. As long as customers have no choice in maintenance providers, there can be no competition. But the best existence proof for third-party maintenance--Rimini Street--is now mired in a lawsuit by Oracle. Oracle fired the first shot, but Rimini Street appears to be itching for a battle by filing an aggressive counter-suit. That's good news. Hopefully this case will be decided in a way that provides legal precedent for the right of third-parties to offer software maintenance that does not infringe on the OEM's intellectual property rights.

  2. Antitrust rulings by the US Department of Justice and the European Union. Although the enterprise software marketplace is not a monopoly, when a customer commits to a certain vendor the vendor-client relationship at that point becomes less of a free market. The customer has committed enormous amounts of time, effort, and business process design that is now intricately linked to that vendor. Undoing such a decision is expensive--even prohibitive. Therefore, there needs to be some legal protections for customers once they commit to a vendor relationship. The tech industry is no stranger to such antitrust rulings in the past (e.g. the ruling against IBM, forcing it to unbundle mainframe hardware from operating systems, which provided the legal framework for the plug-compatible industry comes to mind). A legal requirement for vendors to unbundle software licenses from maintenance services and maintenance services from support services is one area crying out for similar rulings.
In the meantime, customers need to fight back. Gartner's list and Ray's recent post provide good ammunition.

Related posts
Rimini Street, SAP, and the future of third-party maintenance
Rimini Street to provide third-party support for SAP
Legal basis for third-party ERP support industry
Flash: SAP backs down on 22% maintenance fees
SAP postpones its maintenance fee price hike
Enterprise software: who wants to be the low-cost leader?
Attacking and defending software vendor maintenance fees
SAP and third-party maintenance: good for me but not for thee
SAP maintenance fees: where is the value?
Mad as hell: backlash brewing against SAP maintenance fee hike
Why vendors resist negotiating software maintenance fees
Pushing back on software vendor maintenance fees
SAP under the spotlight for "broken promises"
Vendor software maintenance programs: top 10 wish list
Mad as hell: backlash brewing against SAP maintenance fee hike
Oracle confirms: maintenance fees are virtually all profit
Oracle profits strong, thanks to your maintenance payments
Vendor maintenance fees: just say no
High software maintenance fees and what to do about them

by Frank Scavo, 7/20/2010 09:55:00 AM | permalink | e-mail this!

Subscribe!

Read/post comments!
(0) Links to this post

Powered by Blogger

(c) 2002-2014, Frank Scavo.

Independent analysis of issues and trends in enterprise applications software and the strengths, weaknesses, advantages, and disadvantages of the vendors that provide them.

About the Enterprise System Spectator.

Frank Scavo Send tips, rumors, gossip, and feedback to Frank Scavo at .

I'm interested in hearing about best practices, lessons learned, horror stories, and case studies of success or failure.

Selecting a new enterprise system can be a difficult decision. My consulting firm, Strativa, offers assistance that is independent and unbiased. For information on how we can help your organization make and carry out these decisions, write to me.

For reprint or distribution rights for content published on the Spectator, please contact me.


Go to latest postings

Custom Search

Join over 1,700 subscribers on the Spectator email list!
Max. 1-2 times/month.
Easy one-click to unsubscribe anytime.

Follow me on Twitter
My RSS feed

AddThis Feed Button


Computer Economics
ERP Support Staffing Ratios
Outsourcing Statistics
IT Spending and Staffing Benchmarks
IT Staffing Ratios
IT Management Best Practices
Worldwide Technology Trends
IT Salary Report
IT Help Desk/Service Desk Management

Get these headlines on your site, free!


Awards

2013 Best ERP Writer - Winner

Alltop. We're kind of a big deal.
 
Constant Contact 2010 All Star Technobabble Top 100 Analyst Blogs


Blog Roll and Favorite Sites
Strativa: ERP software vendor evaluation, selection, and implementation consultants, California
StreetWolf: Digital creative studio specializing in web, mobile and social applications
Vinnie Mirchandani: The Deal Architect
Oliver Marks' Enterprise 2.0 Blog
Si Chen's Open Source Strategies
diginomica
CISO Handbook


Spectator Archives
May 2002
June 2002
July 2002
August 2002
September 2002
October 2002
November 2002
December 2002
January 2003
February 2003
March 2003
April 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009
August 2009
September 2009
October 2009
November 2009
December 2009
January 2010
February 2010
March 2010
April 2010
June 2010
July 2010
August 2010
September 2010
October 2010
November 2010
December 2010
January 2011
February 2011
March 2011
April 2011
May 2011
July 2011
August 2011
September 2011
October 2011
November 2011
December 2011
January 2012
February 2012
March 2012
April 2012
May 2012
June 2012
July 2012
September 2012
October 2012
December 2012
January 2013
February 2013
March 2013
May 2013
June 2013
July 2013
September 2013
October 2013
December 2013
January 2014
February 2014
March 2014
April 2014
Latest postings