Accenture Global Services GmbH v. Guidewire Software Inc.

631 F. Supp. 2d 504, 2009 U.S. Dist. LEXIS 56030, 2009 WL 1883045
CourtDistrict Court, D. Delaware
DecidedJune 30, 2009
DocketCiv. 07-826-SLR
StatusPublished
Cited by10 cases

This text of 631 F. Supp. 2d 504 (Accenture Global Services GmbH v. Guidewire Software Inc.) is published on Counsel Stack Legal Research, covering District Court, D. Delaware primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Accenture Global Services GmbH v. Guidewire Software Inc., 631 F. Supp. 2d 504, 2009 U.S. Dist. LEXIS 56030, 2009 WL 1883045 (D. Del. 2009).

Opinion

MEMORANDUM OPINION

SUE L. ROBINSON, District Judge.

I. INTRODUCTION

Plaintiffs Accenture Global Service GmbH and Accenture LLP (collectively, “Accenture” or “plaintiffs”) brought this action against defendant Guidewire Software Inc. (“Guidewire”) on December 18, 2007, asserting patent infringement, trade secret misappropriation, and related state law claims. (D.I. 1) On February 6, 2008, defendant filed its answer and asserted counterclaims. (D.I. 10) The parties’ respective claims were subsequently pared down by the court’s October 8, 2008 order. 581 F.Supp.2d 654 (D.Del.2008) Since that time, plaintiffs have twice amended their complaint, and it is plaintiffs’ second amended complaint, filed on December 17, 2008, that is presently operative. (D.I. 92)

Defendant has three motions pending before the court: a motion to dismiss claim 4 of plaintiffs’ second amended complaint alleging tortious interference with business relations (D.I. 98); a motion to amend its answer and counterclaims to add a fifth counterclaim alleging trade secret misappropriation (D.I. 122); and a motion to unseal its proposed amended answer and counterclaim (D.I. 138). For the reasons that follow, the court grants the motion to amend, but denies the motions to dismiss and unseal.

II. BACKGROUND 2

A. Plaintiffs’ Products and Trade Secrets and Dealings with CNA

Plaintiff markets to insurance companies an insurance claims management solution called the Accenture Claim Components Solution (“ACCS”). (D.I. 92 at ¶¶9-10) ACCS combines computer software and consulting services aimed at helping insurance companies optimize their claims handling. (Id.)

Plaintiffs began developing ACCS in the 1990s. (Id. a ¶ 12) In mid-1997, St. Paul Insurance (“St. Paul”) agreed with plaintiffs to share some of the development costs for ACCS and, in October 1998, plaintiffs first implemented ACCS for St. Paul. (Id. at ¶¶ 15, 17) Shortly thereafter, plaintiffs implemented ACCS for Reliance Insurance. (Id. at ¶ 17) From these projects and earlier development efforts, plaintiffs developed trade secrets with respect to design, coding, and implementation of claims management systems. (Id. at ¶¶ 15,16)

Sometime in the late 1990s, plaintiffs implemented ACCS for CNA Insurance’s (“CNA”) personal business unit. (Id. at ¶ 20) In late 2000, CNA’s commercial business unit requested an “assessment” from plaintiffs, which called for plaintiffs to study the commercial unit’s business and develop a detailed plan for implementing ACCS. (Id. at ¶ 21) Plaintiffs performed the assessment, but not without requiring CNA to execute a non-disclosure agreement (“NDA”). (Id.) In late 2002, at CNA’s request, plaintiffs installed a working copy of ACCS software on CNA computers and submitted a bid to implement that software. (Id. at ¶ 22)

B. Defendant’s Entry into the Market and Dealings with CNA

Between 2000 and 2002, plaintiffs learned that defendant had entered the market. (Id.) In 2002, defendant added to its “Board of Advisors” Michael Conroy *507 and Wayne Hoeschen. (Id. at ¶ 23) Conroy and Hoeschen had been, respectively, St. Paul’s executive vice president and chief information officer during the period in which plaintiffs had collaborated on ACCS with St. Paul. (Id. at ¶¶ 23-24) Defendant also added to its “Board of Advisors” during this period Dennis Chookaszian, who was CNA’s chairman and chief executive officer during the period in which plaintiffs had implemented ACCS for CNA’s personal business unit and conducted the assessment for CNA’s commercial business unit. (Id. at ¶25) Conroy, Hoeschen, and Chookaszian all had access to plaintiffs’ trade secrets prior to joining defendant’s “Board of Advisors.” (Id. at ¶ 26)

In early 2003, CNA informed plaintiffs that it would develop claims management software in conjunction with another company whose bid was $10 million lower than plaintiffs; plaintiffs later learned that this company was defendant. (Id. at ¶ 27) CNA staffed the software development project with some of the same employees who had been involved with the ACCS assessment, including Richard Affenit, Jerome Reynolds, and other executives. (Id. at ¶28) These employees had access to plaintiffs’ trade secrets prior to working with defendant on developing and implementing its software. (Id.)

According to plaintiffs, defendant’s claims management product closely resembles ACCS, including those features considered trade secrets. (Id. at ¶¶ 31-32) Plaintiffs further state that defendant was aware of their prospective contract with CNA’s commercial business unit and interfered with that contract by using plaintiffs’ trade secrets, which it had acquired through improper means. (Id. at If 34)

C. Defendant’s Amended Counterclaims

On February 13, 2009, defendant filed a motion to amend its answer and counterclaims. (D.I. 122) The proposed amended complaint adds a fifth counterclaim alleging trade secret misappropriation, as well as several detailed allegations in support thereof. (See id. at ex. 2, ¶¶ 76-112) Defendant bases these detailed allegations on discovery materials — primarily emails— produced by plaintiffs. (Id. at ¶ 1) Much of the material upon which these allegations are based was designated by plaintiffs as falling within the provisions a stipulated protective order. (See D.I. 130 at ¶ 4)

III. DISCUSSION
A. Motion to Dismiss Plaintiffs’ Fourth Claim
1. Standard of review

In reviewing a motion filed under Rule 12(b)(6), the court must accept all factual allegations in a complaint as true and take them in the light most favorable to plaintiff. 3 See Christopher v. Harbury, 536 U.S. 403, 406, 122 S.Ct. 2179, 153 L.Ed.2d 413 (2002). A complaint must contain “a short and plain statement of the claim showing that the pleader is entitled to relief, in order to give the defendant fair notice of what the ... claim is and the grounds upon which it rests.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 555, 127 S.Ct. 1955, 167 L.Ed.2d 929 (2007) (interpreting Fed.R.Civ.P. 8(a)) (internal quotations omitted). A complaint does not need detailed factual allegations; however, “a plaintiffs obligation to provide the ‘grounds’ of his ‘entitle[mentj to relief re *508 quires more than labels and conclusions, and a formulaic recitation of the elements of a cause of action will not do.”

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
631 F. Supp. 2d 504, 2009 U.S. Dist. LEXIS 56030, 2009 WL 1883045, Counsel Stack Legal Research, https://law.counselstack.com/opinion/accenture-global-services-gmbh-v-guidewire-software-inc-ded-2009.