Taylor Investment Corp. v. Weil

169 F. Supp. 2d 1046, 44 U.C.C. Rep. Serv. 2d (West) 382, 2001 U.S. Dist. LEXIS 15232, 2001 WL 391559
CourtDistrict Court, D. Minnesota
DecidedMarch 31, 2001
DocketCIV 98-2632 JRT/FLN
StatusPublished
Cited by25 cases

This text of 169 F. Supp. 2d 1046 (Taylor Investment Corp. v. Weil) is published on Counsel Stack Legal Research, covering District Court, D. Minnesota primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Taylor Investment Corp. v. Weil, 169 F. Supp. 2d 1046, 44 U.C.C. Rep. Serv. 2d (West) 382, 2001 U.S. Dist. LEXIS 15232, 2001 WL 391559 (mnd 2001).

Opinion

MEMORANDUM OPINION AND ORDER

TUNHEIM, District Judge.

This matter is before the Court on defendant Geac Computers Inc.’s (“Geac”) motion for declaratory judgment and for dismissal of the claims of Taylor Investment Corporation (“Taylor”) for lack of subject matter jurisdiction. Also before the Court is Geac’s motion to dismiss the cross-claims of Dennis L. Weil (“Weil”) and Construction Management and Consulting, Inc. (“CMAC”) pursuant to Fed. R.Civ.P. 12(b)(3). Defendants’ Weil and CMAC also move for partial summary judgment on Taylor’s statutory and common law fraud claims. For the reasons set forth below, the Court grants Geac’s motion to dismiss for lack of subject matter jurisdiction, denies Geac’s motion to dismiss the cross-claims of Weil and CMAC, and grants the motion of Weil and CMAC for partial summary judgment. 1

BACKGROUND

Taylor is engaged in the business of developing and marketing recreational real estate. In September 1995, Taylor sent a request for proposal (“RFP”) to several vendors of software and computing services in the construction industry outlining its requirements for a new business computer system. The RFP required a Microsoft Windows-based system comprised of a variety of software applications that would *1052 provide networked integration of Taylor’s sales, land acquisitions and financial operations and would transfer data from its field sales offices to its headquarters in Minneapolis. Defendant CMAC was one of the vendors who received and responded to Taylor’s RFP.

CMAC is engaged in the business of developing and marketing computer systems for the construction industry and providing project management and integration services in connection with those systems. Weil is the president of CMAC. At all relevant times to these proceedings, CMAC was a value added reseller (“VAR”) of software produced by Geac. As a VAR, CMAC was authorized to modify and distribute Geac software to CMAC’s customers as a part of a total package including other software, computer hardware, and computing services.

After reviewing a variety of bids from computer systems developers, Taylor contracted with CMAC for its services on December 8, 1995. CMAC charged Taylor a total of $230,000 for the entire package of products and services it provided to Taylor. A core component of the software package that CMAC presented to Taylor during the bidding process was a newly developed Microsoft Windows-compatible software product from Geac called “Star-Builder.” The itemized cost of StarBuilder to Taylor was $20,000. This amount included a cost of $10,000 that CMAC paid to Geac for the product, as well as an additional $10,000 mark-up that CMAC kept for itself.

The StarBuilder product constitutes the Windows-based version of a Microsoft DOS-based product licensed by Geac called “CS2000.” In November 1995, when Weil presented CMAC’s package to Taylor, Geac had been marketing CS2000 for an extended period of time with positive customer responses indicating that it was a reliable and stable product. Star-Builder, however, was still in an incomplete stage of development. Weil nevertheless marketed StarBuilder to Taylor using CS2000 to demonstrate StarBuilder’s expected capabilities. Weil also presented Taylor with various promotional materials provided to CMAC by Geac, including a StarBuilder product brochure and an incomplete “demo version” of Star-Builder. An internal memorandum issued by Geac to its sales force indicates that Weil’s tactic of using CS2000 along with these other promotional materials to demonstrate StarBuilder was a marketing strategy approved by Geac while Star-Builder was still in development.

During his marketing presentations, Weil informed Taylor’s employees that the development of StarBuilder was unfinished. Taylor therefore was aware that the CS2000 product demonstrated by Weil was not the same product as StarBuilder. Taylor was also aware, when it signed the contract with CMAC in December 1995, that the development of StarBuilder was incomplete. Nevertheless, Weil represented to Taylor that StarBuilder was “virtually” complete and that it would be available to customers by January 1996. Weil also stated that StarBuilder was expected to be as reliable and stable as CS2000. Weil avers that he made these statements solely on Geac’s representations to him. Neither Weil nor Taylor has produced specific evidence, however, of what Geac’s representations to Weil precisely were. At no time during the negotiation process did Geac communicate directly with Taylor about the stability or development status of Star-Builder.

According to Weil, CMAC obtained a copy of StarBuilder from Geac through “ordinary channels” and began installing it at Taylor’s offices in early 1996. Prior to installing the software CMAC provided Taylor with a license agreement for Star- *1053 Builder, as Geac required it to do under Geac’s contracts with CMAC. This document purported to be an agreement between Geac, CMAC and the end user, in this case Taylor, for use of the software. The agreement stated that Geac warranted the software “to conform to its published specifications when shipped ... for ninety (90) days from the date of delivery.” The agreement further provided that “[Geac] does not warrant that the licensed program will be uninterrupted or error free.” The agreement explicitly limited all other warranties by stating that, “[t]he foregoing warranties are in lieu of all other warranties, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.” The agreement also included a clause purporting to limit Geac’s liability. It provided that Geac’s liability in contract or in tort “shall not exceed the actual payments made,” and that “[i]n no event will [Geac] be liable for ... lost profits, loss of business, business interruption, or other consequential damages.” Finally, the licensing agreement provided that it would not “become a valid and binding obligation of [Geac] unless and until a copy of [it was] received and executed by an officer of [Geac].” Although representatives of both Taylor and CMAC signed the agreement, no officer of Geac ever executed it.

Shortly after CMAC installed StarBuilder at Taylor, Taylor began discovering serious defects in the software that made it entirely unusable. The record reflects that numerous other Geac customers, including other customers of CMAC, were having similar problems with StarBuilder. On March 5,1996, Geac issued a memorandum to its sales force describing various flaws in the software that customers had discovered. The memorandum further stated that Geac would not ship StarBuilder to any new clients until the known products were rectified, reasoning, “While there are customers and prospects who say they want StarBuilder immediately (never mind the bugs) our experience is that they eventually do care very much.... Better that they find fault with shipping delays than our software.” In September 1996, Taylor contacted Geac directly for the first time for help with the product. Geac directed Taylor to continue dealing with CMAC as its provider for software support.

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

Related

Barton v. Delfgauw
W.D. Washington, 2024
Core and Main, LP v. McCabe
D. Minnesota, 2023
Nelson v. American Family Mutual Insurance Co.
262 F. Supp. 3d 835 (D. Minnesota, 2017)
Paisley Park Enterprises, Inc. v. Boxill
253 F. Supp. 3d 1037 (D. Minnesota, 2017)
Luckey v. Alside, Inc.
245 F. Supp. 3d 1080 (D. Minnesota, 2017)
Podpeskar v. Makita U.S.A. Inc.
247 F. Supp. 3d 1001 (D. Minnesota, 2017)
Block v. Toyota Motor Corp.
5 F. Supp. 3d 1047 (D. Minnesota, 2014)
Qwest Communications Co. v. Free Conferencing Corp.
990 F. Supp. 2d 953 (D. Minnesota, 2014)
BAE Sys. Info. v. SpaceKey Components
2013 DNH 064 (D. New Hampshire, 2013)
Khoday v. Symantec Corp.
858 F. Supp. 2d 1004 (D. Minnesota, 2012)
Teng Moua v. Jani-King of Minnesota, Inc.
810 F. Supp. 2d 882 (D. Minnesota, 2011)
Cannon Technologies, Inc. v. Sensus Metering Systems, Inc.
734 F. Supp. 2d 753 (D. Minnesota, 2010)

Cite This Page — Counsel Stack

Bluebook (online)
169 F. Supp. 2d 1046, 44 U.C.C. Rep. Serv. 2d (West) 382, 2001 U.S. Dist. LEXIS 15232, 2001 WL 391559, Counsel Stack Legal Research, https://law.counselstack.com/opinion/taylor-investment-corp-v-weil-mnd-2001.