Compuware Corp. v. Health Care Service Corp.

203 F. Supp. 2d 952, 2002 U.S. Dist. LEXIS 9310, 2002 WL 1059807
CourtDistrict Court, N.D. Illinois
DecidedMay 28, 2002
Docket01 C 0873
StatusPublished

This text of 203 F. Supp. 2d 952 (Compuware Corp. v. Health Care Service Corp.) is published on Counsel Stack Legal Research, covering District Court, N.D. Illinois primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Compuware Corp. v. Health Care Service Corp., 203 F. Supp. 2d 952, 2002 U.S. Dist. LEXIS 9310, 2002 WL 1059807 (N.D. Ill. 2002).

Opinion

MEMORANDUM OPINION AND ORDER

BUCKLO, District Judge.

Compuware Corporation of Michigan sells software to run on mainframe computers. It entered into a permanent license agreement (governed by Michigan law) with Health Care Service Corporation of Illinois (“HCSC”) in 1984, but retained ownership in certain software licensed to HCSC. The agreement was amended in 1993 to state that the licensed software may be used only by HCSC and only at the licensed locations. The 1984 license was further amended by twenty five Software Product Schedules entered into between 1984 and 2000, identifying the particular software at issue and the locations to which it was licensed. In 1997, Compu-ware salesmen looking into whether Uni-tech Systems, Inc., might be a potential customer, discovered that Unitech was running Compuware software licensed to HCSC. In February 2000, Compuware found that HCSC had been selling Unitech the use of certain CompuServe software since 1984, and that Unitech had been developing its own line of software that Compuware believed was based on the Compuware software. Compuware sued HCSC for breach of contract (count I), CompuServe, Unitech, and “John Does” for copyright infringement (count II), as well as for misappropriation of trade secrets (count III). The defendants move for summary judgment, and I grant the motion in part and deny it in part.

Summary judgment is proper when the record “show[s] that there is no genuine issue as to any material fact and that the moving party is entitled to a judgment as a matter of law.” Fed.R.Civ.P. 56(c). In determining whether a genuine issue of material fact exists, I must construe all facts in the light most favorable to the non-moving party and draw all reasonable and justifiable inferences in its favor. Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 255, 106 S.Ct. 2505, 91 L.Ed.2d 202 (1986).

HCSC argues that all of Compuware’s claims are time-barred and should be dismissed because the original 1984 agreement requires that “no action arising out of this Agreement, regardless of form, may be brought by either party more than one year after the cause of action has accrued.” According to HCSC, Compuware knew or should have known in 1997 that Unitech was using the licensed software on the HCSC system, but it did not sue until February 2001, well after the one year limitations period in the contract. HCSC offers a statement by Compuware’s Rule 30(b)(6) corporate designee, Sean O’Shea, agreeing that “Unitech told Compuware that it was using the ... software on the [HCSC] computer in 1997,” and that there were no license agreefnents between Com-puware and HCSC. HCSC also offers notes made in the summer of 1997 from Bill Seno, Dan Schufrieder, and Guy Gross, Compuware salesman who were feeling out Unitech as a potential customer, indicating that Unitech was running the licensed software. Compuware replies that this is true, but says it thought that Compuware was merely acting as a consultant to HCSC, and that what Compuware did not know prior to February 2000 was that Unitech was working with Compu-ware software to develop its own products.

That admission takes out the contract claim and (as I shall explain below) the trade secrets claim as well. Michigan, whose law governs here, uses a plain lan *955 guage rule in interpreting contracts. Gelman Sciences, Inc. v. Fidelity and Cas. Co. of New York, 456 Mich. 305, 572 N.W.2d 617, 623 (1998) (“[W]e must enforce the terms of the contract as written, interpreting the unambiguous language in its plain and easily understood sense.”). The license provides that the licensed software “may be used only by the customer,” that is, by HCSC, which shall “maintain the confidential nature of the software.” It does not say that HCSC may allow anyone else to use it or disclose the confidential aspects of it, presumably its architecture and code, to anyone else. It does not say, e.g., “Customer may allow its consultants to use the software as long as the consultants do not use the software to develop their own products.” It says that only the customer may use it, and that the customer must keep the software confidential.

The undisputed facts show that Compu-ware knew in 1997 that Unitech was using the licensed software and therefore that HCSC was not maintaining its confidential nature. That is, Compuware knew in 1997 that HCSC was violating the terms of the agreement, but it did nothing until 2000, when it became aware that Unitech was using the licensed software for developing its own software. Compuware introduces evidence that consulting companies in the business use licensed software all the time, but in the face of exclusive licenses, that just suggests that violations of exclusivity and confidentiality clauses are commonplace. If there are to be exceptions for consultants, they must be expressly stated in the language of the contracts, or the licenses must be otherwise so formulated as to conform to the practice of using consultants. Compuware does not argue that the contract was amended by conduct of the parties or course of dealing, so any such argument is waived. I note that the agreement was amended many times, and had Compuware wished to authorize the use of its software for particular purposes by consultants, it might have specifically done so in writing, and limited external use to those purposes, when it became aware of Unitech’s use of the software in 1997. See Dawn Equipment Co. v. Micro-Trak Systems, Inc., 186 F.3d 981, 988 (7th Cir.1999) (“Had the parties wished to [include a certain contractual provision], they had ample opportunity to do so in the written agreement.”).

Compuware invokes Michigan’s “continuing breach of contract” doctrine, citing Adams v. City of Detroit, 232 Mich.App. 701, 591 N.W.2d 67, 71 (1998), which directed the trial court to treat the denied benefits in that case as like “installment contracts, each deficient payment of benefits marking the time from which a separate claim accrues,” for the purposes of the statute of limitations. However, the case is disanalogous. The present case involves not an installment contract but a one-time license agreement with subsequent amendments. Compuware argues, alternatively, that the Project Schedules “incorporate and are governed by the terms of the license agreement, but each represents a new contract for the software products identified therein.” That would exclude the Project Schedules signed before February 7, 2000, but permit those signed afterwards. However, Compuware offers no argument that the Project Schedules are indeed separate contracts as opposed to amendments, and I conclude that they are not. The contract claim is barred.

The copyright claim is a different story. As Compuware urges, this does not “arise out of’ the license agreement and so is not barred by the contractual limitations period. As the Seventh Circuit has stated, “arising out of’ and “arising under” are familiar phrases. Omron Healthcare, Inc. v. Maclaren Exports Ltd.,

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
203 F. Supp. 2d 952, 2002 U.S. Dist. LEXIS 9310, 2002 WL 1059807, Counsel Stack Legal Research, https://law.counselstack.com/opinion/compuware-corp-v-health-care-service-corp-ilnd-2002.