Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Fritz Nelson

Fritz Nelson

Vice President, Editorial Director InformationWeek Business Technology Network

Jury Decides: SAP To Pay Oracle $1.3 Billion

Oracle wins its landmark copyright infringement case in a landslide, as the jury awards an unprecedented figure. The case is likely to be appealed, and its outcome will linger for years.

Three years of legal due diligence, packed into three weeks of trial, and finally we have a verdict after less than a day of jury deliberation: SAP owes Oracle $1.3 billion for copyright infringement in a landmark judgment that will likely drag on through appeals. But this case promises to reach further -- into the tenuous world of third-party support, into law school classrooms for decades to come, and quite possibly into a world of shareholder lawsuits and justice department investigation.

After watching almost every minute of this trial unfold, it was impossible to predict such an outcome, which intellectual property consultant Sam Wiley called "the largest ever" copyright infringement award. Third-party software support provider TomorrowNow, which SAP acquired at the beginning of 2005, downloaded millions of Oracle files, including software, source code and support materials. SAP knew about it before the acquisition, and the practice continued long after, until Oracle filed suit in 2007. The acquisition of TomorrowNow took place just as Oracle was completing its hostile takeover of PeopleSoft (which included JD Edwards).

SAP claimed to have put out an edict to stop the illegal downloading. During the trial, some SAP executives said that they had assumed this put a stop to the practice, but nobody ever followed up, at least according to their testimony. SAP admitted liability, copping to contributory liability just days before the trial began; this form of liability meant that SAP wasn't just taking accountability for TomorrowNow's actions, but included its own negligence in the matter.

The jury had to decide between two methods of determining damages. First, a hypothetical negotiation that would have taken place on the day SAP acquired TomorrowNow, with both sides having full knowledge of each others' intentions. Oracle, then, would have known that SAP's business assumptions included a three-year plan to entice PeopleSoft and JD Edwards customers to TomorrowNow support, get them to purchase other SAP software (like NetWeaver), and then convert them to SAP ERP and other enterprise applications. SAP planned to make almost $900 million over three years through this plan, called Safe Passage.

SAP executives called those assumptions "marketing plans" in an attempt to downplay them (during the trial, both sides displayed the $900 million document countless times, and it became known as The Zieman Document, for its creator, SAP services chief, Thomas Zieman). Instead, SAP wanted the jury to consider a "lost profits" scenario, whereby its damage expert calculated the money Oracle lost in customer conversions, and the profit SAP accrued through its use of Oracle's software. Both sides agreed that 358 customers left Oracle through Safe Passage, and 86 of them became SAP customers. From there, the sides disagreed about pretty much every customer's reason for leaving Oracle.

Oracle's hypothetical negotiation numbers totaled "at least" $1.66 billion; that number had been limited by Judge Phyllis Hamilton during the course of the trial. Oracle's damage expert also calculated a lost profits number of $409 million. SAP's damage expert put the number at about $40 million. Obviously, the final jury verdict was much closer to Oracle's number -- perhaps not a surprise to some, given the excessiveness of the infringement.

In an official statement, Oracle President Safra Catz said: "For more than three years, SAP stole thousands of copies of Oracle software and then resold that software and related services to Oracle's own customers. Right before the trial began, SAP admitted its guilt and liability; then the trial made it clear that SAPs most senior executives were aware of the illegal activity from the very beginning. As a result, a United States Federal Court has ordered SAP to pay Oracle $1.3 billion. This is the largest amount ever awarded for software piracy."

William Wohl, VP of SAP Global Communications also responded to the verdict: "We are, of course, disappointed by this verdict and will pursue all available options, including post-trial motions and appeal if necessary. This will unfortunately be a prolonged process and we continue to hope that the matter can be resolved appropriately without more years of litigation. The mark of a leading company is the way it handles its mistakes. As stated in court, we regret the actions of TomorrowNow, we have accepted liability, and have been willing to fairly compensate Oracle. Throughout this matter, our customers, employees and partners have stood by us and, for that, we are grateful. Our focus now is looking forward, helping our customers be best run businesses, and extending our legacy of industry leadership well into the future. We thank the jury for its diligent service through this lengthy trial and the Court for its supervision of this complex case."

Experts I spoke with believe that there will be a complicated series of motions and appeals that will extend this case indefinitely. Judges are also known to lower awards that they deem excessive; Judge Hamilton has not indicated yet whether she will do that, and it seems unlikely.

There will be some long-lasting outcomes.

 1 | 2  | Next Page »


Related Reading


More Insights




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.