Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Fritz Nelson

Fritz Nelson

Vice President, Editorial Director InformationWeek Business Technology Network

Oracle-SAP Trial: Phillips Says SAP Owes "Billions," Oracle Can't Find Apotheker

In another day in court for Oracle and SAP, Oracle pushes its lofty damage desires even higher, the lawyers and witnesses do battle, and still nobody can find HP's CEO, a key figure in the proceedings. Still to come: Larry Ellison.

The Oracle-SAP trial continued to grow testy Thursday. Oracle's legal team said it has been unable to find a witness they'd like to subpoena -- one Leo Apotheker, who seems to have vanished despite having started his new job this week as CEO of one of the biggest technology providers in the world (HP). Meanwhile another newly-minted CEO, Charles Phillips, formerly co-President of Oracle, now CEO of Infor, flew in from Atlanta to provide testimony that finally began to hint at the damages Oracle is seeking.

If that weren't enough, the legal teams from both sides bickered openly about the amount of "context" Oracle should be allowed to reveal, debating one potentially damaging exhibit in particular--a document both sides clearly believe will also start to put a vast dollar figure on the award the jury is expected to decide.

(For an explanation of the trial, read this preview.)

SAP has already admitted liability, the result of TomorrowNow's excessive stockpiling of millions of Oracle files before, during and after SAP's purchase of the company in early 2005. The trial is now about the damages SAP will pay. Those damages will play out around the amount of money Oracle and SAP would have hypothetically agreed upon if they'd negotiated for the Oracle licenses at the time of the TomorrowNow acquisition. But that's where it gets interesting.

The court is using the precedent of Georgia Pacific v. United States Plywood (1970), which established a series of factors for determining royalties in an infringement suit. One of the main factors at issue is that the amount awarded would be what the two sides "would have agreed upon at the time the infringement began if they had reasonably and voluntarily tried to reach an agreement." The precedent also holds that the hypothetical negotiation would rely on both sides knowing exactly what each side was planning and thinking at that time.

Turns out, Oracle and SAP have spent the past three years gathering each others' thoughts, through e-mails and memos and board presentations. And it seems they'll spend the next few weeks summarizing the pertinent parts for the jury. Thursday's arguments, mostly from SAP's counsel, were about how much of this is really needed. Judge Shirley Hamilton noted that she'd already agreed on this, pointing out to Oracle: "At some point it becomes cumulative." She let Oracle press on, but we're likely to revisit this point daily.

There was one particular SAP board document at play here, and it turns out that late Wednesday night -- perhaps even in the wee hours of Thursday morning -- SAP's attorneys raised a formal objection to it. That document was a financial projection of what SAP thought it could achieve by turning PeopleSoft maintenance customers into TomorrowNow maintenance customers, and subsequently into more lucrative SAP application customers. The graphic depicted growth in maintenance revenue, cross-sell revenue, and "up-switch" revenue (the conversion), for a total of approximately $900m in upside revenue over three years. A far cry from the $40m number SAP threw around in its opening statement.

Of course, acquisitive companies regularly put together optimistic projections to bolster their desires to complete a deal (although a $900m growth rate on a $10m deal is stretching things, to put it mildly; so much for those conservative Germans), but Oracle is using these projections to establish how SAP might have valued its licenses at a time when the negotiation for them would have taken place.

SAP counsel also lodged a complaint about how Oracle had not stated a damage figure in its opening statement. The judge, perplexed about the necessity of the complaint, simply moved to bring in the jury, but the answer to counsel's complaint started revealing itself when Charles Phillips took the stand. The reed-thin former Oracle titan said that after paying $11.1b for PeopleSoft -- a figure he asserted surpassed any similar deal in the software industry, and one achieved in a variety of nasty legal battles with PeopleSoft shareholders -- he would have negotiated fiercely if faced with providing Oracle licenses to a company whose application software business was many times the size of Oracle's, and who would now be competing with him on several fronts.

Moreover, had he known the volume of Oracle documentation and code TomorrowNow had accumulated, he would have negotiated for even more. When presented with SAP's business case for $900m in growth, Phillips said: "that's a big number. If that's the impact, you'd pay multiples to get that." Meaning he would expect SAP, at license negotiation time, to pay a multiple of $900m to achieve that level of growth, especially since that growth would presumably continue past 2007. Factoring in the same scenarios for Oracle's acquisition of Siebel (and TomorrowNow's infringement of those copyrights as well), the figure goes even higher. "The number," Phillips said, "would have a 'b" on it. Billions."

The rest of the day's proceedings saw a host of other witnesses, from SAP service VP Thomas Zieman, who helped create the $900m slide scenario, to former SAP executive Shai Agassi, whose video deposition depicted him as dismissive and annoyed; the attorney had to ask him to put down his BlackBerry and answer questions.

John Zepecki, the former Peoplesoft employee, and now SAP exec, also took the stand. Zepecki had warned SAP's board about the precariousness of TomorrowNow's access to Oracle's software. Zepecki's testimony was especially tiresome, because he was questioned by the meticulous David Boies, notorious for his prosecution of Microsoft on behalf of the US Justice Department. Zepecki, for his part, sparred with Boies by wrapping just about every answer in a thin cocoon of deniability, while Boies slowly wore away at Zepecki, who, when he finally walked off the witness stand exhaled deeply.

All that Boies really established was that Zepecki knew something, sent the proper warning signals, and washed his hands of any responsibility. Worse, SAP board member Gerhard Oswald, in another tiring video deposition, claimed to either not remember a damn thing, or demonstrated that he didn't really pay much attention during board presentations. And for this, SAP pays Oswald a generous $5m, not including stock incentives.

One last, curious thing . . . In Thomas Zieman's video deposition he is asked a question at the bitter end -- a question about Seth Ravin leaving SAP (he was a TomorrowNow executive, and also has a history with PeopleSoft); only the question was heard, and not the answer. One might view this as a video editing oversight, but this high-powered and bountiful legal team leaves little to oversight. It's no coincidence that Seth Ravin went on to start and helm Rimini Street, another third-party software maintenance provider; and one also currently in litigation with Oracle.

Fritz Nelson is the editorial director for InformationWeek and the Executive Producer of TechWebTV. Fritz writes about startups and established companies alike, but likes to exploit multiple forms of media into his writing.

Follow Fritz Nelson and InformationWeek on Twitter, Facebook, YouTube and LinkedIn:

Twitter @fnelson @InformationWeek @IWpremium

Facebook Fritz Nelson Facebook Page InformationWeek Facebook Page

YouTube TechWebTV

LinkedIn Fritz Nelson on LinkedIn InformationWeek



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.