Oracle Corporation et al v. SAP AG et al

Filing 727

TRIAL BRIEF Defendants' Trial Brief by SAP AG, SAP America Inc, Tomorrownow Inc. (Froyd, Jane) (Filed on 8/5/2010)

Download PDF
Oracle Corporation et al v. SAP AG et al Doc. 727 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Robert A. Mittelstaedt (SBN 060359) Jason McDonell (SBN 115084) Elaine Wallace (SBN 197882) JONES DAY 555 California Street, 26th Floor San Francisco, CA 94104 Telephone: (415) 626-3939 Facsimile: (415) 875-5700 ramittelstaedt@jonesday.com jmcdonell@jonesday.com ewallace@jonesday.com Tharan Gregory Lanier (SBN 138784) Jane L. Froyd (SBN 220776) JONES DAY 1755 Embarcadero Road Palo Alto, CA 94303 Telephone: (650) 739-3939 Facsimile: (650) 739-3900 tglanier@jonesday.com jfroyd@jonesday.com Scott W. Cowan (Admitted Pro Hac Vice) Joshua L. Fuchs (Admitted Pro Hac Vice) JONES DAY 717 Texas, Suite 3300 Houston, TX 77002 Telephone: (832) 239-3939 Facsimile: (832) 239-3600 swcowan@jonesday.com jlfuchs@jonesday.com Attorneys for Defendants SAP AG, SAP AMERICA, INC., and TOMORROWNOW, INC. UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA OAKLAND DIVISION ORACLE USA, INC., et al., Plaintiffs, v. SAP AG, et al., Defendants. Case No. 07-CV-01658 PJH (EDL) DEFENDANTS' TRIAL BRIEF SVI-83531v1 DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) Dockets.Justia.com 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 VI. V. B. C. I. II. III. IV. TABLE OF CONTENTS Page INTRODUCTION ............................................................................................................... 1 DEFENDANTS' PROPOSAL TO STREAMLINE ISSUES FOR TRIAL ........................ 1 FACTUAL BACKGROUND .............................................................................................. 3 PLAINTIFFS' IMPROPER DAMAGES CLAIMS ............................................................ 7 A. Legal Standards Applicable to Damages ................................................................. 7 1. Copyright Damages...................................................................................... 8 2. Damages under Plaintiffs' Non-Copyright Claims .................................... 10 Plaintiffs Are Attempting to Avoid the Court's Sanctions Order .......................... 11 Plaintiffs' Damage Theories Are Flawed............................................................... 12 1. Plaintiffs' Cannot Meet Their Burden of Proof with Respect to Their Infringer's Profits Claim, and Their Expert's Methodology Is Defective .................................................................................................... 12 2. Plaintiffs' Lost Support Profits Claim Is Inflated and Fails to Address the Causation of Damages Requirement...................................... 14 3. Plaintiffs' Fair Market Value Damage Claim Is Based on a Defective Methodology and Unduly Speculative ...................................... 15 4. Plaintiffs' "Saved Development Costs" Theory Is Legally Defective and Factually Absurd................................................................. 16 DEFENSES TO LIABILITY............................................................................................. 17 A. B. C. D. Preemption ............................................................................................................. 17 Statute of Limitations, Laches, and Waiver ........................................................... 18 SAP Is Not Directly or Indirectly Liable for TomorrowNow's Conduct .............. 20 Defenses to Specific Causes of Action .................................................................. 20 1. Copyright Infringement.............................................................................. 21 2. Computer Fraud and Abuse Act/CDAFA .................................................. 21 3. Breach of Contract ..................................................................................... 21 4. Intentional/Negligent Interference ............................................................. 22 5. Unfair Competition .................................................................................... 22 6. Trespass to Chattels.................................................................................... 23 7. Unjust Enrichment/Restitution................................................................... 23 8. An Accounting ........................................................................................... 23 PLAINTIFFS ARE NOT ENTITLED TO PUNITIVE DAMAGES ................................ 24 -iDEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) SVI-83531v1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 SVI-83531v1 TABLE OF CONTENTS (continued) VII. Page CONCLUSION .................................................................................................................. 24 - ii - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Cases TABLE OF AUTHORITIES Page(s) AccuImage Diagnostics Corp. v. Terarecon, Inc., 260 F. Supp. 2d 941 (N.D. Cal. 2003) ....................................................................................... 10 Alberghetti v. Corbis Corp., No. CV 09-5735 SVW (CWX), 2010 WL 2016853 (C.D. Cal. Apr. 29, 2010)........................ 20 Avago Techs. U.S., Inc. v. Venture Corp. Ltd., No. C 08-03248 JW, 2008 WL 5383367 (N.D. Cal. Dec. 22, 2008)......................................... 22 Big Seven Music Corp. v. Lennon, 554 F.2d 504 (2d Cir. 1977)......................................................................................................... 9 Bourne v. Walt Disney Co., 68 F.3d 621 (2d Cir. 1995)......................................................................................................... 21 Chip-Mender, Inc. v. Sherwin-Williams Co., No. C 05-3465 PJH, 2006 WL 13058 (N.D. Cal. Jan. 3, 2006)................................................. 23 Creative Computing v. Getloaded.com LLC, 386 F.3d 930 (9th Cir. 2004)...................................................................................................... 10 Data Gen. Corp. v. Grumman Sys. Support Corp., 36 F.3d 1147 (1st Cir. 1994) ...................................................................................... 9, 10, 13, 14 Frank Music Corp. v. Metro-Goldwyn-Mayer, Inc., 772 F.2d 505 (9th Cir. 1985).................................................................................................... 8, 9 Goldberg v. Cameron, 482 F. Supp. 2d 1136 (N.D. Cal. 2007) ..................................................................................... 20 Golden West Ref. Co. v. SunTrust Bank, 538 F.3d 1233 (9th Cir. 2008).................................................................................................... 19 Harper & Row Publishers, Inc. v. Nation Enters., 471 U.S. 539 (1985)............................................................................................................... 8, 10 Henderson v. Security Nat'l Bank, 140 Cal. Rptr. 388 (Cal. Ct. App. 1977) .................................................................................... 24 In re S.B., 32 Cal. 4th 1287 (Cal. Ct. App. 2004) ....................................................................................... 19 Intel Corp. v. Hamidi, 30 Cal. 4th 1342 (2003) ............................................................................................................. 23 Jarvis v. K2 Inc., 486 F.3d 526 (9th Cir. 2007).................................................................................................... 8, 9 Kling v. Hallmark Cards Inc., 225 F.3d 1030 (9th Cir. 2000).................................................................................................... 19 Laws v. Sony Music Entm't, 448 F.3d 1134 (9th Cir. 2006).................................................................................................... 17 Lucent Techs., Inc. v. Gateway, Inc., 580 F.3d 1301 (Fed. Cir. 2009).................................................................................................. 16 Mackie v. Rieser, 296 F.3d 909 (9th Cir. 2002).................................................................................................... 8, 9 SVI-83531v1 - iii - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Statutes TABLE OF AUTHORITIES (continued) Page(s) Netbula, LLC v. Bindview Dev. Corp., 516 F. Supp. 2d 1137 (N.D. Cal. 2007) ..................................................................................... 21 NLFC, Inc. v. Devcom Mid-America, Inc., No. 93 C-0609, 1993 U.S. Dist. LEXIS 16459 (N.D. Ill. Nov. 16, 1993)................................. 21 Parrish v. Nat'l Football League Players Ass'n, 534 F. Supp. 2d 1081 (N.D. Cal. 2007) ..................................................................................... 24 Polar Bear Prods., Inc. v. Timex Corp., 384 F.3d 700 (9th Cir. 2004)............................................................................................... passim Rano v. Sipa Press, Inc., 987 F.2d 580 (9th Cir. 1993)...................................................................................................... 21 RD Legal Funding, LLC v. Erwin & Balingit, LLP, No. 08cv597-L(RBB), 2009 WL 2579230 (S.D. Cal. Aug. 19, 2009) ...................................... 21 RealNetworks, Inc. v. DVD Copy Control Ass'n, 641 F. Supp. 2d 913 (N.D. Cal. 2009) ....................................................................................... 21 Reudy v. Clear Channel Outdoors, Inc., 693 F. Supp. 2d 1091 (N.D. Cal. 2010) ..................................................................................... 22 S.F. Bay Area Rapid Transit Dist. v. Spencer, 358 F. App'x 793 (9th Cir. 2009) .............................................................................................. 23 Shaffer v. Debbas, 21 Cal. Rptr. 2d 110 (Cal. Ct. App. 1993) ................................................................................. 10 Shapiro, Bernstein & Co. v. 4636 S. Vermont Ave., Inc., 367 F.2d 236 (9th Cir. 1966)........................................................................................................ 8 Sparaco v. Lawler, Matusky, Skelly Engineers LLP, 313 F. Supp. 2d 247 (S.D.N.Y. 2004)........................................................................................ 10 Sully-Jones Contractors, Inc. v. Am. Safety Indem. Co., No. 08-CV-1976 BEN (AJB), 2010 WL 1839114 (S.D. Cal. May 6, 2010)............................. 24 Theme Promotions, Inc. v. News Am. Mktg. FSI, 546 F.3d 991 (9th Cir. 2008)...................................................................................................... 22 Ticketmaster Corp. v. Tickets.com, Inc., No. CV99-7654-HLH (VBKx), 2003 U.S. Dist. LEXIS 6483 (C.D. Cal. Mar. 7, 2003).......... 23 Youst v. Longo, 43 Cal. 3d 64 (2003) .................................................................................................................. 10 17 U.S.C. § 102 .............................................................................................................................. 17 17 U.S.C. § 103 .............................................................................................................................. 17 17 U.S.C. § 106 .............................................................................................................................. 17 17 U.S.C. § 504 ................................................................................................................ 8, 9, 12, 13 17 U.S.C. § 507 .............................................................................................................................. 20 SVI-83531v1 - iv - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 SVI-83531v1 TABLE OF AUTHORITIES (continued) Page(s) 18 U.S.C. § 1030 ...................................................................................................................... 20, 21 Cal. Bus. & Prof. Code § 17208 (2010)......................................................................................... 20 Cal. Civ. Code 3333 ....................................................................................................................... 10 Cal. Civ. Proc. Code § 337 (2010) ................................................................................................. 20 Cal. Civ. Proc. Code § 338............................................................................................................. 20 Cal. Civ. Proc. Code § 339 (2010) ................................................................................................. 20 Cal. Penal Code § 502.............................................................................................................. 20, 21 Other Authorities 4 Nimmer on Copyright §14.03 (2004) ............................................................................................ 9 -v- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 I. INTRODUCTION Since March 2007, an evolving roster of Plaintiffs has filed five complaints, each more colorful than the last. Plaintiffs contend that TomorrowNow cut too many corners in providing a lower-cost alternative to Plaintiffs' expensive software maintenance, by improperly downloading and copying software and support materials. Plaintiffs leap from that contention to billions in damages based on an alleged sinister plot by SAP. As always, the truth is less exciting than the pleadings. SAP bought TomorrowNow for $10 million to provide a choice to customers frightened by Oracle's acquisition of PeopleSoft and J.D. Edwards. TomorrowNow served only a tiny fraction of Plaintiffs' customers--customers who were already going to drop Plaintiffs' support and whom Oracle's own executives dismissed as "unprofitable laggards." TomorrowNow never made a profit, and, despite some initial optimism, no customers chose to purchase SAP software because of TomorrowNow. From the beginning of this case, SAP has acknowledged that there were mistakes in TomorrowNow's service operations and acted responsibly to address the situation. SAP changed management at TomorrowNow. It directed a revision of TomorrowNow's service procedures. And, after it could assure that TomorrowNow's customers were protected, SAP shut down TomorrowNow's operations rather than let them distract from efforts to resolve this dispute. Years of litigation have made a few things clear: although TomorrowNow did make mistakes in its operations, Plaintiffs' damage claims are vastly exaggerated, and Plaintiffs have no interest in resolving this case. Someone will have to take a major step, or this case will never end. That "someone" is SAP. SAP recognizes not only that TomorrowNow made mistakes but that Plaintiffs are entitled to compensation, for which SAP will accept ultimate financial responsibility. That compensation must be based in reality and the law, however. SAP's proposal to streamline this case for trial, outlined below, will allow the Court and the parties to focus on what matters most--a fair resolution of this case. II. DEFENDANTS' PROPOSAL TO STREAMLINE ISSUES FOR TRIAL Beyond the fact that four Plaintiffs are suing three Defendants on ten claims, the principal reason this case threatens to be so complex to try is that Plaintiffs have asserted a claim for SVI-83531v1 -1- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 billions where their true damages measure in the tens of millions, at most. Shining a clear and focused light on Plaintiffs' exaggerated damages claims may be the only way to bring this case to an end. Defendants therefore propose a significant potential compromise--one that should allow this case to reach a fair and timely resolution without unduly burdening the Court or jury: (1) Defendants would not contest TomorrowNow's liability under the asserted claims (except that they would preserve the defenses raised in the pending motions for summary judgment, defenses of preemption, statute of limitations, laches and waiver, and all defenses to the alleged fact, amount or causation of or entitlement to damages or any other relief). (2) Defendants would not contest SAP's vicarious liability for any judgment against TomorrowNow on the copyright claim and would agree to stand behind and guarantee payment of any other judgment against TomorrowNow (but would preserve all defenses above and any other defenses regarding alleged direct or indirect liability). (3) Plaintiffs should agree to dismiss other direct or indirect claims against SAP. (4) The trial should be shortened to two weeks.1 This case is about TomorrowNow's conduct. Defendants' proposal permits Plaintiffs to pursue (and collect, if awarded) the full range of legally available damages. It also permits this case to be substantially shortened (an appealing prospect in view of Plaintiffs' demand to lengthen this trial, by eliminating the need to try most liability issues. Defendants propose taking this significant step now because expert discovery has confirmed that Plaintiffs' damages claims are untethered to the facts or law. Just as Defendants elected not to contest some issues on summary judgment to focus on the core dispute, they now propose that trial focus on the issue that truly divides the parties--damages. Narrowing this case as Defendants propose, along with rulings on the pending summary judgment motions, allows this case to be tried more efficiently and to a result more closely approaching justice than by forcing the Court and a jury to spend weeks deciding issues that need not be in dispute. These proposals are not admissions and are made solely for purposes of focusing this case for trial. Nor do these proposals affect Defendants' pending motion for partial summary judgment which, if granted, would also substantially narrow the issues to be tried. SVI-83531v1 1 -2- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 III. FACTUAL BACKGROUND SAP and Plaintiffs2 are competitors in the market for enterprise resource planning ("ERP") software, each developing and licensing business software applications and offering related customer support services. Typically, Oracle licenses its software under perpetual licenses and bundled with one year of customer support, which customers may renew on an annual basis. The support agreements entitle customers to future software releases. Many customers elect not to renew support services, especially customers on stable or highly customized software packages with no plans to upgrade to future software releases. These customers find little use for the support services and get no value from the payment of support fees that are used in large part to fund future software releases that they do not want or need. The decision to leave one ERP vendor for another is one of enormous cost and business risk and is not undertaken lightly. The vast majority of customers that Plaintiffs claim to have lost to TomorrowNow or SAP would have left even if TomorrowNow had never existed. One reason that customers were driven to leave Plaintiffs arose out of Plaintiffs' acquisition of PeopleSoft, Inc. ("PeopleSoft"). On June 2, 2003, PeopleSoft announced its merger with J.D. Edwards ("JDE") in a combination that made PeopleSoft the world's second largest ERP-software company, displacing Oracle from that position. As the ink was drying on the PeopleSoft/JDE merger agreement, Oracle's executives decided the time was ripe to strike. Four days later, Oracle launched a hostile takeover bid for PeopleSoft, sparking a bitter battle that included lawsuits against Oracle by PeopleSoft and by the United States Department of Justice. PeopleSoft complained that Oracle was deliberately harming PeopleSoft's customer relationships to drive down the price of PeopleSoft's stock and make the acquisition cheaper. The DOJ sought to block the takeover on antitrust grounds. By December 2004, Oracle had defeated PeopleSoft and the United States and completed its eighteen-month battle for control of PeopleSoft. However, Oracle's tactics took a toll on the PeopleSoft customer base. During the takeover battle, Oracle had threatened to lay off thousands Plaintiffs are Oracle USA, Inc. ("OUSA"), Oracle International Corporation ("OIC"), Oracle EMEA Limited ("OEMEA"), and Siebel Systems, Inc. ("SSI") (sometimes, "Oracle"). SVI-83531v1 2 -3- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 of PeopleSoft employees, discontinue PeopleSoft's product lines, and force customers to replace their PeopleSoft information technology systems with an undefined future software package to be known as "Fusion." PeopleSoft complained that these threats were damaging its customer relationships, deterring customers from purchasing PeopleSoft products, and generally driving customers away. As a result, customers of Oracle's newly acquired PeopleSoft and JDE product lines, especially those that were at a stage in the life-cycles of their software where they needed to decide their future product direction, had good reasons to consider alternatives, including SAP. Oracle recognized this at the time, noting that its acquisition model "always assumed there would be some attrition" to SAP. See ORCL00744446. SAP had competed with PeopleSoft before the acquisition, including through its "Safe Harbor" marketing program, which offered discounts to customers that chose to replace their PeopleSoft products with SAP products. Anticipating the consummation of Oracle's takeover of PeopleSoft, SAP introduced a modified program known as "Safe Passage," designed to welcome customers interested in leaving Plaintiffs to the SAP software platform. The Safe Passage program was essentially a price discount. First and foremost, Safe Passage gave PeopleSoft customers a credit of up to 75% of the price the customer had paid for their PeopleSoft software. In addition, SAP offered as an optional component the services of its newly acquired subsidiary, TomorrowNow, to provide support services for PeopleSoft products. TomorrowNow was a small company based in Bryan, Texas that had been in business since 2002. TomorrowNow provided customer support services for users of PeopleSoft software that were weary of paying high support fees to PeopleSoft. TomorrowNow was an early entrant into the market for third party support of enterprise software, but the market has steadily grown and now has both established players and a multitude of emerging companies. Despite Plaintiffs' manifest desire to snuff out the third party support competition, its business model inevitably produces a demand for third party support. Plaintiffs' customers, including those running PeopleSoft and JDE applications, typically pay annual support fees of approximately 20% of their original software purchase price. Customers recognize, however, that a large portion of those fees is used to fund development of future software, as opposed to SVI-83531v1 -4- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 providing support for the products the customers are actually using. Thus, customers that are content with their IT systems and not interested in future software upgrades have difficulty justifying payment of the fees. These customers often seek alternatives, either through third party support providers or self-service options. These third parties are able to support the existing applications more cheaply because they do not need to charge customers for the cost of developing future software applications. Plaintiffs bristle at the notion that customers may wish to lower their support fees and forego the right to future software upgrades. A senior Oracle executive wrote: Let the bastards dream of reducing their maintenance fees. I just finished telling Toyota that we're not going to reduce their bill. Not only that, but they need to buy more software from us! Defs.' Dep. Ex. 373. That attitude contributes to customers leaving Plaintiffs' support. While the evidence will show that SAP's marketing team positioned TomorrowNow as a part of the Safe Passage offer, in reality it was an untested market concept, and no one knew whether or to what extent the TomorrowNow component of the program would be effective in persuading customers to leave Plaintiffs for SAP. Despite the high hopes of some members of SAP's marketing team for its new marketing strategy, at no time prior to the launch of Safe Passage did SAP ever quantify the extent to which TomorrowNow itself would cause sales of SAP software that SAP would not otherwise have made. These high hopes were never realized--the TomorrowNow offer had at best a modest economic impact on SAP and Plaintiffs. During its entire existence, TomorrowNow generated only 358 customers, the vast majority of which were "maintenance-only" customers, meaning that TomorrowNow provided support for Plaintiffs' products and customers did not replace their software with SAP products. The problem with that result is that TomorrowNow lost money. During its life as an SAP subsidiary, TomorrowNow suffered total losses of $90 million.3 These "maintenance-only" customers had no interest in purchasing new software, whether from Plaintiffs, SAP, or others. They were simply looking to lower their maintenance fees on 3 See Expert Report of Stephen K. Clarke, Appendix O. -5DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) SVI-83531v1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 their existing systems. In contrast to Plaintiffs' current litigation posturing, senior executives bid good riddance to such customers, which they dismissed as "unprofitable laggards": If TomorrowNow (SAP) is going to win a bunch of maintenance-only customers with no plans to upgrade for 5 years . . . then I don't think TomorrowNow will be too long for this world as SAP won't make any profitable money on these customers if they can't get them to implement SAP. Defs.' Dep. Ex. 367. Moreover, actual experience has proven that the TomorrowNow offer had virtually no impact on driving sales of SAP products and services that SAP would not otherwise have made. Of the 358 customers that purchased TomorrowNow support, only 86 also purchased SAP products or services thereafter. Importantly, however, the TomorrowNow support was not the cause of the SAP purchases.4 Upon analysis of the 86 customers, it is clear that their purchases of SAP software were driven by considerations more important than and unrelated to the fact that they may have received support services from TomorrowNow. As an example, one customer that purchased TomorrowNow support and SAP software was asked to explain why it chose SAP software. The customer testified that it developed a list of 300 relevant data points in selecting a new software package. TomorrowNow support was "not a data point," not even one of 300. This is no surprise, as business customers are generally unwilling or unable to rip out the IT systems that their business depend upon and replace them with entirely new systems unless: (1) they have a compelling business or strategy reason for doing so; and (2) they are at a point in the lifecycle of the technology where it is reasonable to make such a dramatic change. The financial cost and business risks inherent in replacing a company's business software are typically enormous. The notion that customers would do so because of an offer of discount support of their old software during a transition from the old software to the new is unfounded. Here again, During discovery, the parties identified 86 customers that purchased software or support from SAP at or after the time they began receiving support from TomorrowNow. This so-called "List of 86" explicitly did not raise any inference about whether the customer's SAP purchases were related to the support services provided by TomorrowNow. Rather, it was a purely mechanical list intended to define the subset of customers for which Plaintiffs could obtain discovery (thereby preventing burdensome and unnecessary discovery into all of the approximately 800 Safe Passage customers, the vast majority of which did not purchase TomorrowNow services). SVI-83531v1 4 -6- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Plaintiffs' senior executives recognized this fact in contemporaneous internal communications. Referring to third party support providers as "gnats," Oracle's Senior Vice President of Support Services derided the suggestion that customers would switch to SAP products because of TomorrowNow as "the silliest argument I have ever heard!" Defs.' Dep. Ex. 374. This senior executive continued: "Migrating an application involves some expense; you don't just decide it overnight and the next day you spend the millions." That's right. It takes MILLIONS. The customer has to "spend the MILLIONS." And it's fraught with business disruption and RISK! How much were you going to "save" on that support bill Mr. Customer? Id. In stark contrast to those admissions, Plaintiffs now portray TomorrowNow as the ultimate Pied Piper, single-handedly capable of forcing hordes of ERP customers, who would not otherwise have done so, to replace Plaintiffs' software with SAP. Premised on that false assumption, Plaintiffs overreach on each of their damages theories, claiming literally billions of dollars of unjustified damages. IV. PLAINTIFFS' IMPROPER DAMAGES CLAIMS The focus of this case should be the dispute over the nature and amount of Plaintiffs' alleged damages. Each side will present damages testimony through a primary damages expert, Paul Meyer for Plaintiffs and Stephen Clarke for Defendants. Defendants will also present testimony from industry expert, Brian Sommer, and testimony from customers. Plaintiffs have presented damages claims for: (1) actual damages for the copyright claim, in the form of either lost profits on support services or loss in fair market value; (2) infringer's profits for the copyright claim; and (3) investigation costs for the computer access claims. Aside from investigation costs, Plaintiffs' damage claims for its non-copyright claims are duplicative of (1) and (2). Only the first category of damages--the alleged lost support profits from customers that chose to get support from TomorrowNow--is appropriate in this case. A. Legal Standards Applicable to Damages Under each of their claims, Plaintiffs have the burden to prove that damages were caused by the allegedly wrongful acts. If Plaintiffs cannot prove that Defendants' alleged wrongful acts SVI-83531v1 -7- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 were the "but for" cause of their losses, they are not entitled to a recovery. For example, even if Plaintiffs were to prove that TomorrowNow's support model infringed Plaintiffs' copyrights in the provision of support services, if the jury finds that a customer would have left anyway, then Plaintiffs would not have made a profit and are not entitled to an award of lost profits for that particular customer. This is important in this case, as Plaintiffs are seeking the proverbial "pie-inthe-sky" damages premised on overstated "facts" and unfounded assumptions. 1. Copyright Damages The Copyright Act allows for recovery of actual damages and, to the extent not duplicative of actual damages, disgorgement of infringer's profits. See 17 U.S.C. § 504(b)-(c). Actual damages are generally calculated "by the loss in the fair market value of the copyright," which is determined by either "the profits lost due to the infringement" or "the value of the use of the copyrighted work to the infringer." Polar Bear Prods., Inc. v. Timex Corp., 384 F.3d 700, 708 (9th Cir. 2004); see also Mackie v. Rieser, 296 F.3d 909, 917 (9th Cir. 2002); Frank Music Corp. v. Metro-Goldwyn-Mayer, Inc., 772 F.2d 505, 512 (9th Cir. 1985). The Ninth Circuit has held that "in situations where the infringer could have bargained with the copyright owner to purchase the right to use the work," the "value of use" form of actual damages may be determined by using a hypothetical license. Jarvis v. K2 Inc., 486 F.3d 526, 533 (9th Cir. 2007); see also Polar Bear, 384 F.3d at 709 (stating that "a hypothetical lost license fee" may be awarded, "provided the amount is not based on undue speculation") (citation omitted). General "tort principles of causation and damages" apply when analyzing compensatory damages awards for copyright infringement. Polar Bear, 384 F.3d at 708; see also Harper & Row Publishers, Inc. v. Nation Enters., 471 U.S. 539, 567 (1985); Jarvis, 486 F.3d at 533-34; Mackie, 296 F.3d at 915; Frank Music, 772 F.2d at 514 n.8 (citing Shapiro, Bernstein & Co. v. 4636 S. Vermont Ave., Inc., 367 F.2d 236, 241 (9th Cir. 1966)). Under Section 504(b), "actual damages must be suffered `as a result of the infringement,' and recoverable profits must be `attributable to the infringement.'" Polar Bear, 384 F.3d at 708 (quoting 17 U.S.C. § 504(b)). The plain statutory language makes clear that "a causal link between the infringement and the monetary remedy sought is a predicate to recovery of both actual damages and profits." Id. SVI-83531v1 -8- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 (emphasis added). The copyright holder bears the burden of proving this necessary causal connection between the infringement and any damages sustained. See id. at 708 ("We take this opportunity to reaffirm the principle that a plaintiff in a § 504(b) action must establish this causal connection"); Jarvis, 486 F.3d at 533-34; Mackie, 296 F.3d at 914-15 (citing Data Gen. Corp. v. Grumman Sys. Support Corp., 36 F.3d 1147, 1170 (1st Cir. 1994); Frank Music, 772 F.2d at 514. Specifically, the plaintiff must show that "the infringement was the cause-in-fact of its loss by showing with reasonable probability that, but for the defendant's infringement, the plaintiff would not have suffered the loss." Data Gen., 36 F.3d at 1171. Further, the plaintiff must "prove that the infringement was a proximate cause of its loss by demonstrating that the existence and amount of the loss was a natural and probable consequence of the infringement." Id. (citing Big Seven Music Corp. v. Lennon, 554 F.2d 504, 509 (2d Cir. 1977)). Courts allow both direct and indirect evidence to establish loss, but must "reject a proffered measure of damages if it is too speculative." Mackie, 296 F.3d at 915 (quoting Frank Music, 772 F.2d at 513); see also Polar Bear, 384 F.3d at 709-11 (stating that damages may not be "based on undue speculation"); Jarvis, 486 F.3d at 534 (stating that "[e]xcessively speculative claims of damages must be rejected"). With respect to infringer's profits, a defendant's "indirect profits" are difficult to prove and are only awardable "under certain conditions" because of their "more attenuated nexus to the infringement." Mackie, 296 F.3d at 914. Here the alleged indirect profits are SAP's profits from selling its own software, as contrasted with direct profits of TomorrowNow from the sale of the allegedly infringing support services. Courts closely scrutinize claims for indirect profits and require that "a copyright holder must establish the existence of a causal link before indirect profits damages can be recovered." Polar Bear, 384 F.3d at 6 (referencing 4 Nimmer on Copyright §14.03, 14-34 (2004). When an infringer's profits "are only remotely and speculatively attributable to infringement," courts will "deny recovery" to the copyright owner." Frank Music, 772 F.2d at 8. If and only if the plaintiff carries its initial burden, the burden shifts and defendant may SVI-83531v1 -9- DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 then show that the damage complained of would have occurred even had there been no taking of the copyrighted expression. See Harper & Row, 417 U.S. at 567. Thus, if Plaintiffs carry their initial burden, Defendants may then show that customers would have ceased purchasing support services from Plaintiffs and would have made SAP software purchases, even if the infringement had not occurred. In determining causation of damages, the jury is entitled to take into account all of the diverse factors that might bear upon customers' purchasing decisions. See Data Gen., 36 F.3d at 1172 n.44. 2. Damages under Plaintiffs' Non-Copyright Claims Plaintiffs also must prove damages for each of their non-copyright claims (assuming any of the state law claims are not preempted by the Copyright Act). That proof is far more difficult than Plaintiffs suggest. Each claim requires Plaintiffs to prove causation by showing that "but for" the alleged actions by TomorrowNow, damages would not have occurred. Cal. Civ. Code 3333 (state law claims); Creative Computing v. Getloaded.com LLC, 386 F.3d 930, 936 (9th Cir. 2004) (CFAA). Plaintiffs must meet their burden on a customer-by-customer basis to demonstrate both intentional and negligent interference with prospective economic advantage. See Youst v. Longo, 43 Cal. 3d 64, 71 n.6 (2003) (standard for intentional interference); AccuImage Diagnostics Corp. v. Terarecon, Inc., 260 F. Supp. 2d 941, 957 (N.D. Cal. 2003) (standard for negligent interference). When Plaintiffs are held to their burdens of proof, the alleged damages are far below the amounts they claim. Should Plaintiffs meet their burden, damages are further limited by two important principles. First, Plaintiffs cannot recover duplicative damages (i.e., amounts taken into account in determining copyright damages). See Sparaco v. Lawler, Matusky, Skelly Engineers LLP, 313 F. Supp. 2d 247, 250 (S.D.N.Y. 2004). Additionally, under California law, "[a] plaintiff who suffers damage as a result of either a breach of contract or a tort has a duty to take reasonable steps to mitigate those damages and will not be able to recover for any losses which could have been thus avoided." Shaffer v. Debbas, 21 Cal. Rptr. 2d 110, 114 (Cal. Ct. App. 1993). Evidence will show that Plaintiffs failed to take such mitigating steps. SVI-83531v1 - 10 - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 B. Plaintiffs Are Attempting to Avoid the Court's Sanctions Order For the first two years of this case, Plaintiffs insisted on limiting damages discovery in this case to lost support sales to customers that left for TomorrowNow. When, at the eleventh hour, Plaintiffs attempted to add claims for lost software license sales and lost sales to customers that were never customers of TomorrowNow, Magistrate Judge Laporte entered the Sanctions Order precluding them from doing so.5 The Sanctions Order precludes Plaintiffs from presenting evidence of alleged lost profits relating to: (1) customers that did not become customers of TomorrowNow; (2) software licensing revenue, as opposed to support revenue; and (3) products that were not supported by TomorrowNow. See Sanctions Order at 26 (D.I. 482). Plaintiffs filed objections to the Sanctions Order and sought clarification concerning its scope. In the objections, Plaintiffs expressly acknowledged that the Sanctions Order precludes any claim for damages to goodwill.6 Plaintiffs nonetheless argued that their damages expert and other witnesses should be permitted to offer the precluded evidence for purposes other than proving lost profits damages, including in support of their expert's hypothetical license calculation and other, unspecified, alleged "impacts."7 In response, Defendants argued that Plaintiffs should not be permitted to offer the precluded evidence to bolster their other damages claims.8 Specifically, Defendants argued that the prejudice finding on which the Sanctions Order is based applies with equal force to Plaintiffs' other damage claims. Id.9 In the Adopting Order, this Court adopted the Sanctions Order in its entirety. D.I. 532. Judge Laporte held a hearing on the motion on August 19, 2009 (the "Sanctions Hearing") and granted the motion on September 17, 2009. See D.I. 482 (the "Sanctions Order"). This Court adopted the Sanctions Order on November 2, 2009. D.I. 532 (the "Adopting Order"). 6 "The damages that arguably fit Magistrate Laporte's premise are . . . damages to Oracle's goodwill . . . ." D.I. 499 at 2. 7 D.I. 499 (Oracle's Objections to Order of Discovery Magistrate Granting Defendants' Motion for Preclusion of Certain Damages Evidence Pursuant to Federal Rules of Civil Procedure 37(c) And 16(f)) at 14-15. 8 D.I. 526 (Defs.' Response to Plaintiffs' Objections to Order for Sanctions) at 21-22. 9 "If Oracle's expert is permitted to testify on the amount of the precluded lost profits damages for purposes of, for example, supporting his opinion on the value of the hypothetical license (or any other damage theory), the prejudice to Defendants is the same as if he was testifying for purposes of the lost profits claim. Defendants will have been deprived of a full and fair opportunity to rebut that evidence by Oracle's discovery misconduct."). Id. SVI-83531v1 5 - 11 - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 The Court further ruled that the precluded evidence will not be admitted for any other purpose. Id. at 1 ("the precluded evidence will NOT be admitted through the back door . . . .") (emphasis in original). Despite the Court's ruling, Plaintiffs have indicated their intent to offer the precluded evidence in support of their damage claims. This includes a newly disclosed claim of damage to goodwill, even though Judge Laporte asked Plaintiffs at the sanctions hearing whether they intended to quantify or seek damages for alleged harm to goodwill and Plaintiffs responded unequivocally that they did not intend to quantify "anything on goodwill" or to seek damages related to goodwill. D.I. 462 (8/19/09 Tr.) at 38:18-25, 41:18-24, 43:11-22.10 These issues are subject of Defendants' Motions In Limine Nos. 1 and 2, filed concurrently. C. Plaintiffs' Damage Theories Are Flawed The following sections highlight some of the many flaws in Plaintiffs' damages claims and Mr. Meyer's approaches to calculating them. 1. Plaintiffs' Cannot Meet Their Burden of Proof with Respect to Their Infringer's Profits Claim, and Their Expert's Methodology Is Defective Plaintiffs are pursuing a claim under 17 U.S.C. § 504(b) for disgorgement of $288 million of SAP "profits" allegedly caused by TomorrowNow. See Defs.' Dep. Ex. 2017. Significantly, the claim is for "indirect" profits made by SAP from selling its own software and services; there can be no claim for the "direct" profits of TomorrowNow from selling the allegedly infringing services because TomorrowNow made no profits. Mr. Meyer's approach to calculating the infringer's profits claim impermissibly lumps together hundreds of millions of dollars of SAP's sales without consideration of whether those revenues were generated as a result of the alleged copyright infringement. While Mr. Meyer purports to have performed his own causation of damages analysis and, indeed, has adopted certain of the causation conclusions reached by Defendants' expert Mr. Clarke, Mr. Meyer's causation analysis is woefully incomplete. For the vast majority of customers, Mr. Meyer has Plaintiffs' damages expert, Paul Meyer, did not provide an opinion on alleged harm to goodwill in his report. See Declaration of Jason McDonell in Support of Defendants' Motions In Limine, ¶ 7. SVI-83531v1 10 - 12 - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 applied a blanket assumption that if a customer was identified anywhere as a Safe Passage customer, all of the customers' purchases of SAP software thereafter were caused by TomorrowNow support services. That assumption is invalid. An actual example reveals the fallacy of this assumption. Included in the $288 million claim of infringer's profits are $34 million of profits resulting from SAP's software sales to a large international corporation. See Defs.' Dep. Ex. 2020. SAP's software sales to this customer, however, had nothing to do with TomorrowNow. The actual facts are that customer has been an SAP user for many years prior to SAP's acquisition of TomorrowNow. In 2007, the customer acquired a U.S. company, and according to a corporate policy converted the newly acquired subsidiary to SAP software in order keep the subsidiaries operating on a common platform with the parent. Evidently because acquired subsidiary took advantage of TomorrowNow's support during the transition to SAP software, Mr. Meyer claims that SAP's sales included in his calculation were obtained "as a result of" TomorrowNow's alleged copyright infringement and therefore should be disgorged. Meyer Report, ¶ 435. The reality, of course, is that it was parent's policy of standardization on SAP software that caused the sales of SAP software, not the TomorrowNow support. Contemporaneous documents show this fact, including TomorrowNow documents ("customer has a program in place for all of its acquired organizations to move to its standard enterprise software applications, which is SAP"), SAP documents (noting the "[w]orldwide replacement of JDE Systems into unified SAP template") and Oracle documents ("the decision had been made by the [parent/subsidiary] Integration team to standardize all applications on [parent's] SAP solutions").11 Mr. Meyer deliberately ignores this evidence and persists in his opinion that TomorrowNow was the cause of the parent's purchases of SAP software for its subsidiary. There are literally dozens of other examples of Meyer ignoring Plaintiffs' burden to prove that Defendants' alleged profits are "attributable to" the infringement,12 ignoring the available customer-specific information, and improperly relying on his blanket assumption. 11 12 See TN-OR00152649, SAP-OR00147255, ORCL00182769. 17 U.S.C. § 504(b); Polar Bear, 384 F.3d at 709; Data Gen., 36 F.3d at 1172 n.44. - 13 DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) SVI-83531v1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2. Plaintiffs' Lost Support Profits Claim Is Inflated and Fails to Address the Causation of Damages Requirement Plaintiffs seek lost profits from support revenue they claim they would have made from the TomorrowNow customers "but for" the alleged infringement. Plaintiffs' expert has calculated these lost profits as either $318 million or $91 million, depending on his timing assumptions. Defs.' Dep. Ex. 2017. But Plaintiffs' own internal records, customer testimony, and other evidence confirm that most customers that came to TomorrowNow were going to leave Oracle's maintenance service anyway--if not for TomorrowNow, then for some other service provider or for self-support.13 After applying a rigorous customer-by-customer analysis, Defendants' expert has calculated these damages at less than $40 million. Plaintiffs have the burden of proving a causal relationship between the alleged infringement and lost profits that resulted from the alleged infringement.14 Plaintiffs must prove that "but for" the alleged infringement, it would not have suffered lost profits. If and only if Plaintiffs carry their initial burden does the burden shift to Defendants to show that all or some portion of the claimed lost profits were not caused by the alleged infringement. Id. Among other things, Defendants may show that customers would have ceased purchasing support services from Plaintiffs even had the alleged misconduct not occurred. In their zeal to press this claim, Plaintiffs have manipulated evidence and thereby cast doubt on the overall credibility of the claim. One of the maintenance-only customers Plaintiffs claim they would have retained but for TomorrowNow is the public entity Cowlitz County, Washington. See Meyer Tr. at 930:1-932:20. Plaintiffs' attorneys asked Cowlitz County to sign a declaration swearing that "had Cowlitz County known" that TomorrowNow "wrongfully" downloaded, copied and maintained "Oracle proprietary software," then Cowlitz County would not have entered into a support services agreement with TomorrowNow. Defs.' Dep. Ex. 2049 Similarly, the evidence is abundant that no SAP customers chose to purchase SAP software because of TomorrowNow support services for Plaintiffs' products. The important decision to pick a business software platform was never driven by the chance of modest savings to interim maintenance and support. 14 13 Polar Bear, 384 F.3d at 709; Data Gen., 36 F.3d at 1172 n.44. - 14 DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) SVI-83531v1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 (Declaration of Kathy Sauer). Plaintiffs gave this declaration to their expert Mr. Meyer who relied on it when concluding that but for TomorrowNow Cowlitz County would have continued to renew its support agreements with Plaintiffs. Meyer Report, ¶ 357 n.668. Thereafter it came to light that Plaintiffs had suppressed a critical part of the history-- indeed the key part. In its discussions with Plaintiffs, Cowlitz County had proposed that the declaration include the following explanation of what it would have done had it not used TomorrowNow: In light of the budgetary and other concerns that led Cowlitz County to choose TomorrowNow service, as referenced above, with this information Cowlitz County believes it would have simply elected not to renew its services agreement with Oracle and relied on its own in-house technicians backstopped if necessary by time and materials services from PeopleSoft. Defs.' Dep. Ex. 2049 (Declaration of Kathy Sauer) (redlining omitted). Plaintiffs declined to accept this critical information, instead finalizing a declaration that omitted the fact that Cowlitz "would simply have elected not to renew its services agreement with Oracle," and leaving the impression that Cowlitz would have remained an Oracle support customer absent TomorrowNow. Id. Cowlitz ultimately submitted a supplemental declaration that revealed the complete story. See id. When confronted with the complete story, Mr. Meyer retreated and agreed that TomorrowNow had not caused Plaintiffs to lose support profits with respect to Cowlitz County. See Meyer Tr. at 930:1-932:20. Mr. Meyer failed to adequately consider available customer-specific information and instead relies on unwarranted assumptions (and Oracle's manipulation of the "facts"). In contrast, Defendants' damages expert Mr. Clarke made a comprehensive analysis of the causation issue and rendered an opinion on a customer-by-customer basis as to the reasons for and extent to which the TomorrowNow support offering was the cause of any damage to Plaintiffs. 3. Plaintiffs' Fair Market Value Damage Claim Is Based on a Defective Methodology and Unduly Speculative Based on Mr. Meyer's analysis, Plaintiffs seek fair market value damages in excess of $2 billion. See Defs.' Dep. Ex. 2017.15 That analysis consists primarily of a Georgia-Pacific 15 SVI-83531v1 Defendants had sought summary judgment that this license theory was not available in - 15 DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 hypothetical license approach and will be the subject of a Daubert motion by Defendants. Defendants will show that Mr. Meyer relied almost entirely on an inappropriate metric, that is, corporate acquisitions rather than comparable or "benchmark" licenses. Essentially, Mr. Meyer's "analysis" consists of nothing more than charging Defendants a pro rata share of Plaintiffs' cost to acquire PeopleSoft and Siebel. Mr. Meyer compounds this problem by cherry-picking data so as to systematically exclude any data point that would undermine his $2 billion valuation, relying on information not of the type relied on by experts in the field, and making methodological errors in his use of that information. The result is a fair market value calculation that is inherently unreliable and unduly speculative. Mr. Meyer also fails to base his fair market calculation on the alleged "actual use" of the registered works. For example, rather than considering the fact that TomorrowNow had only 358 customers, only 86 of which purchased anything from SAP, Mr. Meyer bases his pro rata share of the PeopleSoft and Siebel acquisitions on the assumption that Defendants would have acquired, outright, 3,000 PeopleSoft and 200 Siebel customers. Meyer Report, ¶¶ 122-124. Mr. Meyer's justification for ignoring actual use is his mistaken view that the law forbids him from considering reality. This is not the law, as recently confirmed by the Federal Circuit in Lucent Techs., Inc. v. Gateway, Inc., 580 F.3d 1301 (Fed. Cir. 2009) (overturning a $358 million verdict based, in part, on failure to consider actual use in the hypothetical license analysis). 4. Plaintiffs' "Saved Development Costs" Theory Is Legally Defective and Factually Absurd As addressed in Defendants' pending motion for partial summary judgment, "saved development costs" are not available in this case as a matter of law. See D.I. 640 (Defs.' Mot. for Partial Summary Judgment). Plaintiffs' demand that TomorrowNow pay the full replacement cost of software--to which Plaintiffs retained at all times the right to use, distribute, license and (continued...) this case. The Court denied that motion (D.I. 628) but in so doing expressly cautioned that such damages must be reasonable and not speculative. D.I. 628 (Order Denying Defs.' Mot. for Partial Summary Judgment). SVI-83531v1 - 16 - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 profit from--is as illogical and absurd as demanding that a user of the Bay Bridge, who neglected to pay the toll, pay the state the entire cost of building the bridge. Plaintiffs' claim for saved development costs, which far outstrips the amounts Plaintiffs seek in lost profits, illustrates the largess of Plaintiffs' overreaching. In addition, Plaintiffs' claim for saved development costs is based on expert opinion that will be the subject of a Daubert motion. V. DEFENSES TO LIABILITY Plaintiffs' dramatic pleadings aside, liability is not a foregone conclusion. While Defendants propose not to contest TomorrowNow's liability for most purposes in this case, substantial defenses to liability exist and may be a major focus of trial. These issues are summarized below.16 An important threshold issue is not so much a defense to Plaintiffs' claims as it is a reminder of what Plaintiffs would rather forget--four named entities have sued three different companies. Referring generally to "Oracle" and "SAP" is a useful timesaver for many purposes. But, as is apparent from the Court's order dismissing two plaintiff entities, Defendants' pending motion for summary judgment against another, and Plaintiffs' own numerous adjustments of the roster of named plaintiffs, "Oracle" is a shorthand term. Each individual plaintiff must prove its own claims, its standing, and its damages. So too must each actual plaintiff prove the alleged liability of and damages supposedly caused by each accused defendant on that plaintiff's claims. Plaintiffs' efforts to conflate the parties on either side is not a timesaver here, nor can it provide cover for their limited rights and inability to actually prove a case against SAP. A. Preemption A state law claim is preempted by the Copyright Act if the subject matter of the state law claim falls within the subject matter of copyright as described in 17 U.S.C. Sections 102 and 103, and the rights under the state law are equivalent to rights under Section 106 of the Copyright Act (the exclusive rights of reproduction, preparation of derivative works, distribution, and display). See Laws v. Sony Music Entm't, 448 F.3d 1134, 1137-38 (9th Cir. 2006). Plaintiffs' state law This summary references some issues addressed in the pending motions for summary judgment, but to avoid repetition does not repeat all those arguments. SVI-83531v1 16 - 17 - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 claims for breach of contract, intentional and negligent interference, unfair competition, unjust enrichment, and accounting, at least, all are based on the same essential claims--that TomorrowNow should not have copied, distributed, or created derivative works from "Oracle's" allegedly copyrighted software and support materials (few of which Plaintiffs themselves created). These state law claims seek exactly the same (or subsets of) the relief that Plaintiffs seek as relief under the Copyright Act (except punitive damages, which is probably the only reason state law claims are cluttering up this copyright case). These state law claims are preempted. B. Statute of Limitations, Laches, and Waiver Years before it filed suit on March 22, 2007, Oracle's predecessor PeopleSoft was well aware of TomorrowNow and many of its service activities at issue in this case. For example, as early as July 2002, PeopleSoft's internal lawyer wrote to TomorrowNow and alleged that its activities "violate PeopleSoft's rights," among other things, through "access to confidential PeopleSoft information in your possession," and accused TomorrowNow of unlawful interference with PeopleSoft's relationships with support customers. Defs.' Dep. Ex. 1323. These concerns continued as Oracle acquired PeopleSoft. On January 11, 2005, Richard Blotner, Vice President, North America Operations at Oracle, stated in an e-mail: "what i'm really concerned with is this . . . . . . . . is tomorrow now taking advantage of the situation by getting updates from their most recent new customers, and applying them to their older ones? i have no evidence and no one has said this, but i have a suspicious little mind. worst case, it might be worth sending them a legal letter, ensuring they know that they cannot do something like this." ORCL00172524. Oracle's concerns years before filing went straight to the top. In an eWeek article entitled "Oracle Warns SAP to Step Lightly," dated January 26, 2005, Oracle CEO Larry Ellison was quoted as saying in response to SAP's acquisition of TN, "That's our intellectual property, and they should be cautious." Defs.' Dep. Ex. 404. Yet, despite these concerns, PeopleSoft, then Oracle, actually assisted TomorrowNow in the downloading and use of software "environments" at issue in this case. For example, on April 21, 2004, Terry Wagner, Manager Subcontracts at Lockheed Martin, e-mailed Gregory Stevenson at PeopleSoft, stating, "In order for Lockheed Martin to engage TomorrowNow for continued SVI-83531v1 - 18 - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 support of V7.5 tax updates we need to have PeopleSoft's authorization to provide the CDs that they are requesting." TN-OR00800751-53. The April 21, 2004 e-mail received by Mr. Stevenson includes an e-mail from Shelley Nelson of TomorrowNow expressly stating that "TomorrowNow's standard procedure is to get a demo copy of your PeopleSoft Demo software CD's in order to install a `demo support environment' at TomorrowNow on your behalf." Id. The email also indicates that Mr. Stevenson "recommended" TomorrowNow to Lockheed Martin for "continued tax update support of version 7.5." Id. Ironically, in view of Oracle's claims in this case, Stevenson forwarded Wagner's e-mail to Seth Ravin, then co-president of TomorrowNow, asking "Why would we need to provide authorization?" Id. In fact, even after this lawsuit was filed, Oracle itself sent download help and updates to TomorrowNow. See TNOR0017847. On December 7, 2004, Nancy Lyskawa of PeopleSoft indicated that "My team is actually leading the competive/marketing strategy on the emerging third party support providers. [Redacted sentence] We are very aware of TomorrowNow and have quite a bit of information on them." Defs.' Dep. Ex. 414. In addition, Plaintiffs' privilege logs contain literally dozens of entries indicating that they anticipated litigation against TN at least as early as September 2004. See, e.g., Defs.' Dep. Ex. 420. It is no surprise, then, that Defendants are pursuing their defenses of statute of limitations, laches, and waiver. Plaintiffs (or their predecessors) knew or should have known of Defendants' allegedly objectionable conduct long before Plaintiffs filed their various complaints in this case, and knowingly failed to act.17 Plaintiffs' claims for copyright infringement, violation of the CDAFA, breach of contract, tortious interference, unfair competition, trespass to chattels, and unjust enrichment are similarly barred by the applicable statutes of limitations.18 "Laches is an equitable time limitation on a party's right to bring suit. To obtain a judgment on this affirmative defense, a defendant must prove both an unreasonable delay by the plaintiff and prejudice to itself." Kling v. Hallmark Cards Inc., 225 F.3d 1030, 1036 (9th Cir. 2000) (citation omitted). "[W]aiver is the intentional relinquishment or abandonment [by a plaintiff] of a known right." Golden West Ref. Co. v. SunTrust Bank, 538 F.3d 1233, 1242 (9th Cir. 2008) (citing In re S.B., 32 Cal. 4th 1287, 1293 n.2 (Cal. Ct. App. 2004)). Under the Copyright Act, a copyright owner must commence a legal action within three years from when the infringing action takes place or when the infringement was discovered or SVI-83531v1 18 17 - 19 - DEFENDANTS' TRIAL BRIEF Case No. 07-CV-01658 PJH (EDL) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 A related point is the damages limitation on the CFAA claim. OUSA and OIC failed to comply with the applicable statute of limitations and thus are not entitled to pursue a claim for violation of the CFAA prior to March 22, 2005. Under 18 U.S.C. § 1030(g), a claim for violations of the CFAA must be brought within two years of the date of the act complained of or the date of Plaintiffs' damage. Because, as explained on summary judgment, these Plaintiffs cannot establish that such damage ever occurred, OUSA and OIC's recovery, should they prove their CFAA claims, must be limited to violations occurring after March 22, 2005, two years prior to the filing of the original complaint on March 22, 2007. See D.I. 1. C. SAP Is Not Directly or Indirectly Liable for TomorrowNow's Conduct This case is about TomorrowNow's service activities for its customers. While to focus this case for an efficient resolution SAP has offered to accept financial responsibility for its subsidiary's liability, SAP itself did not do the downloading and copying alleged in Oracle's complaints. Thus, if it is liable, SAP is only secondarily liable. But, as explained on summary judgment, for those few claims that may in some circumstances recognize secondary liability (copyright, CFAA, CDAFA), the facts here prevent that finding against SAP. See D.I. 670. D. Defenses to Specific Causes of Action Because it is not clear whether Plaintiffs accuse SAP directly (much less how they could), Defendants briefly address substantive defenses to particular claims, notwithstanding their election to limit their attack on TomorrowNow's alleged liability. (continued...) reasonably should have been discovered. See 17 U.S.C. § 507(b); Polar Bear, 384 F.3d at 706; Goldberg v. Cameron, 482 F. Supp. 2d 1136, 1148 (N.D. Cal. 2007). A claim for violation of the CDAFA must be brought within three years of the claim's accrual. See Cal. Penal Code § 502(e)(5). A claim for breach of contract must brought within four years of accrual. See Cal. Civ. Proc. Code § 337 (2010). Claims for intentional and negligent interference with prospective economic advantage must be brought within two years of accrual. See Cal. Civ. Proc. Code § 339 (2010). A claim for unfair competition must be brought within four years of accrual. See Cal. Bus. & Prof. Code § 17208 (2010). A claim for trespass to chattels must be brought within three years of accrual. See Cal. Civ. Proc. Code § 338 (2007). "[U]njust enrichment causes of action are governed by the relevant statute of limitations applicable to the central contentions" underlying the claim. Alberghetti v. Corbis Corp., No. CV 09-5735 SVW (CWX), 2010 WL 2016853, at *11 (C.D.

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?