Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

1/15/2010
08:41 AM
Bob Evans
Bob Evans
Commentary
50%
50%

Global CIO: SAP Blows Huge Opportunity With Timid Support Changes

SAP is overblowing its new support plan, which gives customers only marginally more choice.

Business is all about opportunities, and SAP just blew a big one. After summoning the institutional will to address its ancient pricing structure in light of today's dramatically different customer requirements and desires, SAP missed a golden opportunity to establish itself as the clear market leader over Oracle as SAP chose to make only minimal changes in its support pricing.

Yes, SAP deserves some credit for offering its customers and prospects a second option for support and maintenance—any alternative, however humble, is far more than Oracle's one-size-fits-all approach. But after all the melodrama of the past several months—user-group revolts over SAP's earlier plan for monolithic price increases, followed by peace talks that promised KPI-driven price changes to be announced in December, followed by a postponement for a month so that SAP could reconsider its reconsiderations—it's hard not to feel underwhelmed by SAP's new plan.

That new plan involves two versions of support: the company's traditional and much-loved Enterprise Support, and the newly arrived but clearly unloved stepchild called Standard Support. I say "clearly unloved" because if SAP itself can't be excited about the product, how the heck can it expect customers to get all whipped into a lather? To prove my point, check out this less than ringing endorsement for Standard from the SAP executive whose team is responsible for it:

"Standard Support is really a reactive offering for our customers; if they've got a problem, we'll fix it," said Janet Wood, vice president of maintenance.

Steady there, Janet, steady—you keep pumping up your products with that type of passionate enthusiasm and the customers will be beating your door down. (And for extensive background on SAP and its support policies and corporate strategies, please be sure to check out our "Recommended Reading" list at the end of this column.)

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our new online community and information resource for CIOs operating in the global economy.

You can learn the full details of the announcement in this excellent news analysis by my colleague Doug Henschen, who's editor-in-chief of our sister site Intelligent Enterprise. Doug's analysis includes the above comment from SAP's Wood, who went on to contrast the "reactive" Standard option with the "proactive" Enterprise option:

"Standard Support also includes enhancement packages and new releases but the Enterprise Support offering is proactive, so it's about working with customers to see issues before they experience a problem," said Woods.

In addition, Doug offers this insight about what the new SAP support offerings mean for CIOs:

Bowing to customer complaints about economic hardships, SAP also has frozen prices for existing Enterprise Support contracts at the 2009 level of 18.36%. The plan to gradually increase that rate will resume in 2011, bringing Enterprise contracts to 22% by 2016 instead of 2015, as previously planned. . . .

The change is a victory for SAP customers, user groups and the many who complained bitterly about the application vendor's July 2008 decision to increase maintenance and support fees from 17% to 22% over five years. But it's not a complete victory in that the Standard Support option—which was available only in Germany, Austria and Switzerland in 2009 but will be reintroduced worldwide—is set at 18%, a 1% increase from 2008 rates. What's more, Standard Support will be subject to inflationary price increases—a common practice but one that does not apply to Enterprise Support through 2016.

Those numbers underscore my contention that this minimalist approach allows SAP to put a check-mark in the box that says "customers say they want more support and maintenance options" without really advancing the long-term interests of its customers. Technically, SAP now offers tiered support options; practically, customer options are extremely limited.

It's as if McDonald's rolled out a new soft-drink policy along these lines: "We now have two and only two drink sizes and prices: Sumptuously Supreme and Not As Good. Here are the descriptions:

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...