Risk
10/30/2009
08:21 AM
Bob Evans
Bob Evans
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Global CIO: SAP Eliminates All-Up-Front Payment Requirement

In a striking move, SAP is extending to 580 very large customers a plan allowing them to spread payment across multiple years instead of making one big capital-expense payment up front.

In a striking move that reflects customers' needs and shows desire to lead the market, SAP is extending to 580 very large customers a payment plan that will allow them to spread their payments across the duration of their multiyear license instead of having to pay that entire capital expense up front.

The move comes as SAP released disappointing third-quarter results with revenue from new licenses down significantly—company CEO Leo Apotheker called it a "tough spending environment" as CIOs continue their reluctance to commit huge chunks of their challenged IT budgets to single projects.

(For more insights and analysis on SAP, be sure to check out the "Recommended Reading" list at the end of this column.)

It also reflects the feeling among an increasing number of CIOs and their CEOs that the traditional all-up-front capital expense for a multiyear license was a fabulous arrangement for SAP but not nearly so wonderful for the customer. The new approach, Apotheker said in a low-key statement released with the quarterly numbers, is intended to restore better balance to that seller-buyer equation:

"Despite the continued tough spending environment, we are pleased to see further progress in the evolution of our volume business as a result of smaller deals," said Apotheker. "In addition, we are driving more multi-year agreements, where customers buy and consume software over many periods, which we believe is a positive transition for both SAP and our customers.

"We have the benefit of many years of experience in facilitating the purchase of our software in this manner, including the success we had in signing multi-year, Global Enterprise Agreements with our largest customers. We have now started to leverage this approach with a bigger group of customers."

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.

While offering a bit of insight, that statement was still so vague, so oracular (the one at Delphi, not Redwood City), that I went back to SAP for more detail, asking what specific changes will these customers experience? What is the "evolution" Apotheker refers to? We know that customers "consume" SAP products over multiple years, but what does it mean to "buy" over time like that?

Here are excerpts of the reply I got from an SAP spokesperson:

"We see that deal volume will be the main driver going forward, rather than big up-front commitments. This means more sustainable, more predictable and long-term partnerships. . . . Customers want greater flexibility and to phase-in their software use. We’ve seen this trend from the start and are leading the adjustment. . . . Our Global Enterprise Agreements with companies like BMW, Colgate, Exxon and Hitachi are examples of the kind of relationships we are crafting with our blue-chip customer base—we are now also entering the same type of strategic, multi-year relationships with a larger group of customers.

"These partnerships provide customers with the flexibility and strategic relationships they want, and SAP benefits from a more stable source of recurring revenue. In practice, for example, this means that payment of a five-year license agreement will be paid in increments over those five years rather than requiring the up-front capital expense all at once."

That last sentence—"paid in increments over those five years rather than requiring the up-front capital expense all at once"—seemed to break through the fog and offer a real look at what SAP intends to accomplish with this evolving model. I again asked for more details from SAP and got this response:

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.