BRUEL AND KJAER, Plaintiff-Appellant,
v.
The VILLAGE OF BENSENVILLE, Defendant (Suburban O'Hare Commission, Defendant-Appellee).
Appellate Court of Illinois, Second District.
*446 Marios N. Karayannis, Brady & Jensen, Elgin, R. Brent Hatcher Jr., Smith, Gilliam, Williams & Miles, P.A., Gainsville, GA, for appellant.
Patrick K. Bond, Mary E. Dickson, Scott A. Hadala, Bond, Dickson & Associates, P.C., Wheaton, for appellee.
OPINION
Justice BIRKETT delivered the judgment of the court, with opinion.
¶ 1 Plaintiff, Bruel & Kjaer, a supplier of noise-monitoring and radar equipment and *447 systems, appeals the judgment of the circuit court of Du Page County dismissing its complaint against defendant, the Suburban O'Hare Commission, pursuant to section 2-619 of the Code of Civil Procedure (Code) (735 ILCS 5/2-619 (West 2010)), on the ground that plaintiff's complaint was filed outside the four-year statute of limitations that applies to the sale of goods pursuant to a contract under the Uniform Commercial Code (UCC) (810 ILCS 5/2-725 (West 2010)). Plaintiff contends that the contract between the parties predominantly called for the provision of services instead of the sale of goods and was subject to the 10-year limitations period pursuant to section 13-206 of the Code (735 ILCS 5/13-206 (West 2010)). Alternatively, plaintiff contends that the unopposed affidavit of its employee, Imram Mohamed, an engineer who worked on the project, established that material factual issues existed and that they were sufficient to survive defendant's motion to dismiss. We affirm.
¶ 2 In February 1999, plaintiff entered into an agreement with defendant and the Village of Bensenville.[1] Plaintiff agreed to provide certain equipment and services to defendant in exchange for a single payment of $227,000. The agreement labeled plaintiff as the seller and defendant as the buyer in the transaction. As is pertinent here, plaintiff supplies noise-monitoring and radar equipment and systems. Under paragraph 2 of the agreement, plaintiff was to sell to defendant "the upgrade to the noise-monitoring and radar systems, and annual servicing agreements with respect thereto." The exact items, services, and specifications were identified in Exhibit A to the agreement.
¶ 3 Plaintiff also agreed to "deliver, assemble, install, test and make fully operational such Equipment and System F.O.B. at the MCI Tower, Bensenville, Illinois, or other site designated" by defendant. Plaintiff further warranted, under paragraph 5 of the agreement, that "all Equipment and services furnished and/or delivered hereunder will be delivered, installed and operated in a workmanship like manner and that the design of the System is fit for the purposes therein purchased."
¶ 4 The agreement further provided that a "material inducement" for defendant to pay the purchase price was the specifications regarding the performance of the equipment and systems. The agreement devoted about 3½ pages to providing the requirements for the performance of the equipment and systems. Under the agreement, plaintiff's equipment and systems were required to produce reliable and complete flight track data, to identify flight arrivals and departures, to identify aircraft flight information, to input data into the Federal Aviation Administration (FAA) Integrated Noise Model, to allow defendant to browse and analyze different geographic information, to correlate flight information to noise events, to provide consistent collection and reporting of the noise-monitoring data, and to ensure that the software was accessible by defendant.
¶ 5 The agreement specified the terms for defendant's acceptance of the equipment and systems, along with the timeline to make the single payment of $227,000. The agreement provided in paragraph 4:
"The Equipment and System shall be delivered and installed F.O.B. at the site identified in Section 2, with all freight and cartage to be paid by Seller [plaintiff]. [Defendant] shall provide the real *448 property for the site location which Seller has advised and represented is suitable and appropriate for the System to function effectively and [defendant] shall provide all of the necessary utilities for the site. Upon final payment, Seller shall deliver to [defendant] a Bill of Sale for the Equipment and System and which shall vest in [defendant] good and marketable title to such Equipment and System free and clear of any and all liens and encumbrances."
¶ 6 The agreement also set forth a service component. In paragraph 2, an annual servicing agreement was referenced. Paragraph 3(j) provided that plaintiff would "provide all software adjustments necessary to insure" that the software for the systems would be accessible to all the member communities of defendant. Exhibit A to the agreement enumerated the work to be provided by plaintiff in upgrading the existing passive radar to Long-Range PAS SUR, upgrading the software as necessary, and setting forth terms of additional free services to be offered to defendant as a "most favored customer" by plaintiff and its subcontractor, Megadata.
¶ 7 In its complaint, plaintiff alleged that the software upgrades specified under the agreement included significant efforts devoted to developing new software programs and customizing existing software programs for defendant. Plaintiff alleged that the software it developed was designed to allow defendant to obtain the required information and was not an off-the-shelf product that defendant could have obtained. Additionally, plaintiff alleged that it provided site visits and engineering support during the installation and configuration of the equipment and systems. For example, as part of the services provided, plaintiff obtained FAA data and compared it to the flight tracks obtained from the systems. Plaintiff also assisted in setting up a case study to display the noise contours based on the systems' flight tracks. Plaintiff further provided defendant with technical assistance over the telephone between 1999 and 2007.
¶ 8 Plaintiff alleged that it provided the equipment and systems, which were accepted and used by defendant. In January 2002, plaintiff submitted a formal approval document and invoice for the $227,000 price specified in the agreement. Plaintiff alleged that defendant did not pay this first invoice, so it again invoiced defendant for the purchase price.
¶ 9 In June 2004, following repeated invoicing, defendant paid plaintiff $50,000 toward the purchase price set forth in the agreement. Thereafter, despite further invoices plaintiff sent to defendant, defendant did not pay any more money toward the purchase price. Plaintiff alleged further that defendant never sent a notice of rejection of any of the equipment or services and that defendant continued to use the equipment and systems, resulting in defendant's success in obtaining nuisance relief.
¶ 10 On November 12, 2010, plaintiff filed its complaint for breach of the agreement. Defendant filed a motion to dismiss under section 2-619 of the Code, arguing that plaintiff's complaint was untimely under the four-year statute of limitations in section 2-725 of the UCC. Plaintiff countered that the UCC statute of limitations was not applicable, because the contract was predominantly for the provision of services and not the sale of goods. Plaintiff argued that, instead, the 10-year statute of limitations governing written contracts set forth in section 13-206 of the Code applied to its action.
¶ 11 In support of its response, plaintiff included an affidavit by Imram Mohamed, a support engineer on the project. Mohamed outlined the time that was spent *449 developing new software and upgrading existing software for the equipment and systems. Mohamed averred that, as a result of these efforts, the software "in no way constituted a pre-developed, stock product." Mohamed compiled a chart, which was attached to the affidavit, that purported to show the number of days spent developing the software and whether that development was for newly developed software or for customizing an existing application. The chart further indicated that the customization and development work was "typically done for each noise monitoring system" plaintiff installs. According to Mohamed's chart, plaintiff spent 52 days creating newly developed software, 37 days customizing software from an existing application for this project, and 72 days of combined work, consisting of "New/Customized application[s]," for a total of 161 days working on software for the project. Mohamed averred that, "[w]ithout the services to develop the software, and without the services to install and support the upgrade," defendant would not have been able to obtain the information it was seeking. Further, Mohamed somewhat redundantly averred that, "[w]ithout the software development services performed by [plaintiff], the actual hardware and other equipment delivered to [defendant] for the system upgrade would have been useless."
¶ 12 On April 28, 2011, the parties argued the motion to the trial court, focusing on whether the software could be considered a good. Plaintiff conceded that software may, in some circumstances, be a good, but argued that there was a sufficient factual controversy, underscored by Mohamed's affidavit, to preclude a judgment pursuant to section 2-619 of the Code.
¶ 13 On May 1, 2011, the trial court delivered a written order. The court held:
"The law in Illinois is clear and agreed upon by the parties. If a contract is predominantly for goods, then there is a four year limitation period. If a contract is predominantly for a service, then there is a ten year limitation period. This is known as the `predominant purpose' test.
Initially, there must be a determination of whether the case should be decided on a motion to dismiss. Illinois courts frequently decide the `predominant purpose' test on a motion to dismiss. [Citation.] The `predominant purpose' test can be applied to this case at this stage of the proceeding.
[Plaintiff] is a supplier of radar systems. It sold the upgrade and annual service agreement to [defendant]. The Plaintiff had to do extensive development of 22 software applications that took 161 days to complete. [Citation.] The sale of software, whether off the shelf or customized, is the sale of a good not a service. [Citation.] The contract also called for the delivery and installation of the `Equipment and Systems'. Since [plaintiff] was to provide `marketable title to such Equipment and systems free and clear of any and all liens', then the `Equipment and Systems' must be a good and not a service.
The contract calls for the delivery, assembly, installation and testing of the equipment. The contract provided that the monitors will be [calibrated] once annually. Each additional calibration shall be $2,500. [Plaintiff] agreed to provide a three year service agreement by [Megadata] free of charge.
The terms of the contract are not disputed. The hours spent developing the software are not contested. The predominate [sic ] nature of the transaction as a whole is the sale of goods, `Equipment and Systems'. The delivery, *450 installation and services provided under the contract are incidental to the sale of the `Equipment and Systems'.
This case was filed more than 4 years after the accrual of the cause of action and is barred by the statute of limitations."
Plaintiff timely appeals.
¶ 14 Plaintiff challenges the trial court's dismissal of its complaint pursuant to section 2-619 of the Code. We review de novo the trial court's grant of a section 2-619 motion to dismiss. Pugsley v. Tueth,
¶ 15 On appeal, plaintiff argues that the predominant purpose of the agreement was the provision of services to defendant, so the 10-year limitations period of section 13 -206 of the Code should apply rather than the 4-year period of section 2-725 of the UCC. Plaintiff also argues that, in the alternative, Mohamed's affidavit evidences the existence of disputed issues of material fact regarding the predominant purpose of the agreement, which should have precluded the dismissal of its complaint. We consider plaintiff's contentions in turn.
¶ 16 This appeal concerns whether section 2-725 of the UCC or section 13-206 of the Code should apply to the subject matter of the agreement between the parties. Article 2 of the UCC applies only to transactions in "goods" (Nitrin, Inc. v. Bethlehem Steel Corp.,
¶ 17 In determining whether a contract is predominantly for goods, a court will review the contractual language relating *451 to the design, installation, or delivery of an identifiable and tangible object. E.g., Bob Neiner Farms, Inc. v. Hendrix,
¶ 18 In this case, the agreement referred to the parties as "buyer" (defendant) and "seller" (plaintiff). The object of the contract was the upgrade of tangible equipment, being components of noise-monitoring systems and radar systems. In addition, the contract provided that, "[u]pon final payment [plaintiff] shall deliver to [defendant] a Bill of Sale for the Equipment and System free and clear of any and all liens and encumbrances." We note that the UCC defines a "sale" as "the passing of title from the seller to the buyer for a price." 810 ILCS 5/2-106 (West 2010). Thus, the contract appeared by its language to contemplate a sale of goods via the passing of title from plaintiff to defendant for the equipment and systems that were the object of the agreement.
¶ 19 In addition, the agreement provided that plaintiff was to deliver and install the goods: plaintiff agreed to "deliver, assemble, install, test and make fully operational such Equipment and System, F.O.B." Further, "[t]he Equipment and System shall be delivered and installed F.O.B. * * * with all freight and cargo to be paid by Seller." "F.O.B." is an abbreviation for "free on board," a term used in transactions in tangible goods, and is defined in the UCC. See 810 ILCS 5/2-319 (West 2010). Plaintiff also promised to provide various services "in consideration" of defendant's purchase of the equipment and systems. Thus, the terminology employed by the agreement called for the sale of goods rather than the provision of services.
¶ 20 This is also seen by noting that defendant was to make a single payment of $227,000 after plaintiff had delivered and installed the equipment, rather than multiple payments based on time and type of service. Further, there was no breakdown in the price between the cost of the equipment and the cost of the labor needed to make it operational. For all these reasons, then, we hold that the agreement provided for the sale of goods, with any specified services being only incidental to the sale of goods.
¶ 21 This can also be seen when approached from a different angle. Plaintiff supplies certain tangible widgets to buyers along with sufficient services to make the widgets operable. In the absence of the widgets themselves, the services to make them operable would be meaningless and without value. In this case, the widgets were the equipment used in the noise-monitoring and radar systems. The services were the installation of the equipment and the creation and modification of software sufficient to enable the equipment to function properly. The point of the agreement was to furnish the equipment *452 necessary to perform the desired noise monitoring and radar detection needed to accomplish the buyer's goals of abating excessive noise from the airport. Accordingly, we hold that the trial court did not err in determining that this was a contract predominantly for goods and not services, so that the limitations period in section 2-725 of the UCC was applicable to bar plaintiff's action.
¶ 22 We next consider plaintiff's specific arguments. Plaintiff first criticizes the trial court's reading of Dealer Management Systems, Inc. v. Design Automotive Group, Inc.,
¶ 23 In Dealer Management, the court had to decide whether a contract for the provision of an accounting management system was predominantly for goods or services. Dealer Management,
¶ 24 After setting out the possibilities, the court then applied the predominant purpose test of Brandt to decide the issue. Dealer Management,
¶ 25 The Dealer Management court held that the contract at issue in that case was predominantly for goods only after analyzing the facts of the contract in light of the *453 Brandt predominant purpose test and the acknowledgment that software occupies a continuum between goods and services depending on the interplay between the contract and the attendant facts. Thus, Dealer Management teaches that the sale of software may be a good or a service depending where upon the continuum the facts of the case fall.
¶ 26 Here, the facts and contractual language demonstrate that the transaction here was one for goods. The parties were denominated "buyer" and "seller"; title to tangible goods was passed upon completion of the contractual terms; plaintiff agreed to deliver, assemble, install, test, and make fully operational the equipment that was the subject of the contract; and defendant was to make a single payment for the equipment provided by plaintiff rather than multiple payments based on plaintiff's time and type of services provided. In addition, any services were provided "in consideration" of defendant's purchase of the equipment and systems. Considering the totality of the facts and contractual language, it is clear that this transaction falls on the goods side of the continuum, not the services side. Even if the trial court's rationale based on its reading of Dealer Management was incorrect, it is of no moment to our review, because the trial court still entered the correct judgment. Hope,
¶ 27 Plaintiff argues that services predominated in the agreement at issue, citing a number of cases concerning mixed contracts in support of that position. These cases, however, are distinguishable or else they simply illustrate the application of the predominant purpose test. For example, plaintiff relies on Brandt, apparently because the item at issue, a medical sling to treat incontinence, was acknowledged to be a good under the UCC, while the entire transaction was deemed to be one for services, namely, the surgical implantation of the sling. Brandt,
¶ 28 At best, Brandt is illustrative of plaintiff's point that a mixed contract may have the provision of services as its predominant purpose. It offers little guidance beyond that broad point, however. Brandt involves the interplay not of goods and software, but of medical goods and medical services. Plaintiff does not analogize the provision of medical goods and services to the transaction involved in this case; further, there was no written contract to be considered in Brandt; here, by contrast, there was a written contract the terms of which support the idea that plaintiff was providing to defendant goods sufficient to accomplish defendant's purposes. Nothing in Brandt compels a different result than the one we have already reached.
¶ 29 Next, plaintiff cites to Heuerman,
¶ 30 In addition, the Heuerman court's analysis focuses on the terms of the contract. The case involved a contract for the procurement, hauling, and delivery of gravel to a road improvement project. Heuerman,
¶ 31 In this case, the trial court analyzed the terms of the contract in determining that it was for the provision of goods. The trial court, then, actually followed the guidance in Heuerman, namely, to carefully consider the terms of the contract. As to plaintiff's point about Heuerman, that it stands for the proposition that the predominant purpose test presents a factual question, we disagree that it does for this case. Heuerman stated only that the predominant purpose test generally presents a question of fact (Heuerman,
¶ 32 Plaintiff next cites five cases that, it asserts, are sufficiently factually similar as to provide guidance in determining that the predominant purpose of the agreement was the provision of services by plaintiff to defendant. We briefly consider each case in turn.
¶ 33 Plaintiff first cites Lukwinski v. Stone Container Corp.,
¶ 34 We hold that Lukwinski is distinguishable. In that case, there was no mixed contract between the plaintiff and the defendant. Rather, the contract was between the plaintiff's employer and the defendant, and it was a contract for services, namely, hauling goods to be delivered. The contract that the plaintiff attempted to benefit from was between the defendant and the defendant's customer, so the plaintiff was actually outside of the contract that was under the scope of Article 2 of the UCC. Here, by contrast, the contract was between plaintiff and defendant and was a mixed contract. Lukwinski is inapposite and provides no guidance in the circumstances of this case.
¶ 35 Plaintiff next cites Zielinski,
¶ 36 We conclude that Zielinski is also distinguishable. The party in Zielinski who most closely resembles plaintiff in this case is the mason. The Zielinski court, however, did not provide any express analysis of the contract. Instead, it noted that "masonry subcontracts" of the kind at issue there were "not primarily contracts for the sale of goods." Zielinski,
¶ 37 In Boddie,
¶ 38 Boddie is also distinguishable. While the contract at issue called for the defendant to supply and install a conveyor system, it also contained many further requirements regarding the construction of the building in which the conveyor was to be placed. Thus, the Boddie court contemplated the contractual terms before determining whether goods or services predominated. The contract at issue in *456 Boddie appears to have been much more extensive than the one in this case, and the provision of the conveyor system appears to have been a small part of the defendant's overall obligations. Here, by contrast, the contract focused exclusively on the noise-monitoring and radar equipment and systems to be used in monitoring flights at the O'Hare airport. The scope of the contract in this case was narrower, and it was much less clear in the division between goods and services. Further, Boddie appeared to follow the analysis in Zielinski because it generalized a class of contracts, namely, construction contracts. Thus, while the result in Boddie is the same that plaintiff is looking for in this case, the rationale actually supports the trial court's decision. It considered the terms of the contract in determining whether goods or services predominated and it used a generalization from a similar case to underpin its result, much as the trial court in this case analyzed the agreement and relied on Dealer Management. In any event, we do not believe that Boddie is particularly helpful given that it involved a contract in which the provision of goods was clearly a small part, while the contract here was of a smaller scope than the construction of a building and focused on the noise-monitoring and radar equipment and systems.
¶ 39 In Nitrin,
¶ 40 Nitrin used the same procedure to effect the analysis of its contract as the trial court and we used in this case, namely, a review the contract to discern its purpose. In the agreement at issue in this case, the parties denominated themselves as buyer and seller. Items in the contract were sold from the seller to the buyer, not built in place or designed as in Nitrin. Further, the agreement called for the transfer of title from the seller-plaintiff to the buyer-defendant in this case; in Nitrin, the defendant never had title to anything, and title to all equipment, including the disputed converter, remained in the plaintiff. These factual differences in the contractual language serve to distinguish Nitrin from this case. The overall analytical scheme followed by the court in Nitrin is the one we have endeavored to explain and follow; that is the main point of relevance of Nitrin. Due to the differences in the contractual language, there is little factual similarity between Nitrin and this case. Accordingly, we conclude that Nitrin is inapposite.
*457 ¶ 41 Plaintiff last points to Continental Illinois National Bank & Trust Co. v. National Casket Co.,
¶ 42 Plaintiff cited the foregoing cases for the purpose of illustrating how courts analyze mixed contracts under the UCC. Our review of the cases shows that they are either factually distinct or otherwise inapposite, except for their general approach to analyzing the issue. Both we and the trial court below followed this general analytical framework. Accordingly, to the extent that plaintiff relies on Lukwinski, Zielinski, Boddie, Nitrin, and Continental Illinois, that reliance is unavailing. The cases do not change our analysis above.
¶ 43 Next, plaintiff turns to specific disagreements with the trial court's judgment and defendant's arguments below (which, presumably, the trial court accepted in reaching its judgment). Plaintiff complains that defendant, in its arguments below, devoted "substantial time" to the agreement while "ignoring the `predominate nature of the transaction as a whole.'" In particular, plaintiff objects to defendant's argument that the contractual language "`implie[d]'" a sale of goods because, according to plaintiff's synopsis of the argument, the agreement referred to plaintiff as the seller and defendant as the buyer. Plaintiff contends that "`the labels used by the parties to describe the transaction are not controlling'" (quoting Dealer Management,
¶ 44 Plaintiff correctly cites Dealer Management for the proposition that the parties' labels will not control the court's interpretation of a transaction. Plaintiff, however, overstates the point, attempting to imply that the parties' labels are actually worthless in determining the predominant purpose of a transaction. There is no support for that position. Instead, the parties' labels are data to use in determining the predominant purpose of the transaction, just as the relative breakdown of costs between the goods and services in a mixed contract is useful information, but not dispositive on its own. Dealer Management,
¶ 45 Plaintiff contends next that the "Agreement itself contains myriad terms devoted to prescribing [plaintiff's] Services." While this may be a true statement (albeit vague), it begs the question as to whether goods or services predominate in the transaction at issue here. "Myriad" simply means many, and the employment of that term does nothing to help quantify the terms that prescribe the *458 goods to be supplied under the agreement or the relative importance of the goods versus the services in the transaction. Further, our review of the agreement and the transaction indicates that goods predominate notwithstanding the "myriad terms" used in the agreement to prescribe the services to be provided. In addition, we believe that plaintiff is conflating systems specifications, meaning what functions the agreement's "Equipment and System" will perform, with the services plaintiff is to perform under the agreement. Accordingly, we reject plaintiff's "myriad terms" contention.
¶ 46 Plaintiff criticizes the trial court for failing to consider the "transaction as a whole." Brandt,
¶ 47 Last, plaintiff highlights the fact that some of the software was original and some was customized for the equipment and systems of the agreement. While true, that fact does not transform the transaction from one for goods into one for services. As we have noted, the services were incidental to the sale of the equipment and systems. We note, however, that simply because the services were incidental does not mean that they were not necessary. Plaintiff is conflating the idea of necessary with the thrust of the transaction. Indeed, without the goods (the noise-monitoring and radar equipment), the software would have been wholly without function or purpose (and likely could not have been developed). Likewise, without the software, the equipment would not function as desired. The necessity of both goods and services is manifest, but the necessity does not determine the predominant nature of the transaction. A review of the circumstances and the agreement demonstrates that the goods predominate in this transaction, notwithstanding the necessity of the services to make the goods function as required. We reject plaintiff's final contention on this point.
¶ 48 We have carefully reviewed the transaction between the parties to determine whether the goods aspect or the services aspect of the transaction was predominant. The authority we have reviewed emphasized the importance of reviewing the terms of the agreement in determining the predominant nature of the transaction in the procedural posture of this case. Our review indicated that the transaction was predominantly for the sale of goods, namely, noise-monitoring and radar equipment and systems, with the services, namely, software development and customization, incidental to that purpose. Plaintiff's arguments to the contrary are unavailing. Accordingly, we hold that the trial court correctly determined that the UCC's statute of limitations in section 2-725 (810 ILCS 5/2-725 (West 2010)) applied to the transaction, and that plaintiff's action was time-barred *459 as a result. Thus the trial court properly granted defendant's motion to dismiss.
¶ 49 Next, and in the alternative, plaintiff argues that Mohamed's affidavit, which defendant did not oppose by filing a counteraffidavit, demonstrated the existence of a material factual dispute that should have precluded the grant of defendant's motion to dismiss. Plaintiff's argument is fairly simple: The law says that an unopposed affidavit may demonstrate the existence of an issue of material fact (plaintiff says "create" an issue of material fact), and this occurs when reasonable minds viewing the uncontradicted affidavit might differ about the inferences to be drawn from the undisputed evidence. Pothier v. Chicago Transit Authority,
¶ 50 While plaintiff's logic is largely correct, it is deficient in at least one key aspect, which is seen by the terms it uses. The crux of plaintiff's argument is that the unopposed affidavit creates an issue of material fact. This is simply incorrect. See American States Insurance Co. v. National Cycle, Inc.,
¶ 51 We first recap: The issue facing the court is whether the statute of limitations in section 2-725 of the UCC (810 ILCS 5/2-725 (West 2010)) bars plaintiff's complaint as untimely. In order to resolve the issue, the court must apply the predominant purpose test. Brandt,
¶ 52 Plaintiff contends that Mohamed's affidavit gives details of the engineering services he and two others provided pursuant to the agreement. Defendant counters that the affidavit only restates the requirements and parameters called for in the *460 agreement. We agree with defendant. For example, paragraph 5 of Mohamed's affidavit restates the goal of the agreement. Paragraph 6 recapitulates the performance requirements set forth in Exhibit A to the agreement. Paragraph 7 sets forth the parameters regarding flight data, arrivals and departures, and voltage reports from the noise-monitoring equipment. Paragraphs 9 through 12 discuss the development of the software to perform the functions identified in paragraphs 5 through 7.
¶ 53 In particular, Mohamed noted that the development of new software and customization of existing software took a total of 161 days (presumably meaning person-days of labor among the three engineers on the project). Mohamed provided a threefold categorization of the software tasks: new software, customized software, and combined new and customized software, but did not elaborate on what tasks each category represented. We believe that the "new software" category means creating software that did not previously exist; "customized software" means changing an existing piece of software to conform to the requirements of the agreement; and "new and customized software" means some sort of combination of the two, either changing existing software to provide new output, or the concurrent development of new software and the changing of existing software. Mohamed's chart shows that 52 days were spent on new software, 37 days were spent on customizing software, and 72 days were spent on combined new and customized software. Only 52 days of the 161 were spent on developing new software; the remaining time was spent customizing existing software in some fashion. (We note that customization of existing software may be akin to creating specially manufactured goods under the UCC. Dealer Management,
¶ 54 Mohamed's affidavit, then, focuses on various forms of software development. It also assumes, without establishing, that such software development is a service and not a good. In Dealer Management, the court noted that software could be either a good or a service, depending on the circumstances of the transaction. Dealer Management,
¶ 55 Plaintiff particularly emphasizes paragraphs 14 through 16 of Mohamed's *461 affidavit, in which he opined that, without the development and customization of the software, the equipment would be worthless. Plaintiff argues that, because the hardware manifestly would be worthless without the software developed to run it, the agreement must have been one predominantly for services, focusing on that software development. We see at least two major problems with this line of reasoning. First, the statements are conclusory, not factual. Because these statements are not factual, they cannot demonstrate the existence of a factual dispute. Second, and at least as important, the converse is equally true: without the hardware, the software would be irrelevant. Indeed, without the hardware, it is likely that the software could not have been developed and customized at all. The averments in paragraphs 14 through 16, then, cannot realistically serve as the lynchpin of plaintiff's arguments about the affidavit.
¶ 56 Based on our careful review of Mohamed's affidavit, we conclude that it does not establish that a disputed issue of material fact exists that should have been resolved by the jury. The affidavit recapitulates the terms of the agreement identifying the performance standards expected of the equipment and systems. The focus on software development shows that it is more in the nature of goods than services. Additionally, the affidavit includes nonfactual information that contributes nothing to the search for a factual dispute. Based on these reasons, we hold that the Mohamed affidavit does not demonstrate that there exists in this case a disputed issue of material fact.
¶ 57 We now turn to plaintiff's specific arguments. Plaintiff first argues that an uncontradicted affidavit may create a factual issue. We have above debunked plaintiff's reasoning. It is not the function of an affidavit to create an issue; rather, the affidavit helps the court to visualize an existing issue. American States Insurance,
¶ 58 Plaintiff next suggests that Pothier supports the idea that an uncontradicted affidavit may establish factual questions. In that case, the plaintiff's affidavit set out facts supporting her defense of estoppel against the defendant's motion to dismiss based on the plaintiff's failure to file a notice of accident with the defendant. Pothier,
¶ 59 Plaintiff further cites to Janowiak v. Tiesi,
*462 ¶ 60 Next, plaintiff returns to the idea that the predominant purpose test generally presents a question of fact to be resolved by a jury. We have addressed this issue above, noting that it is well settled that the predominant purpose test may be resolved as a matter of law in the appropriate circumstances, and determining that those circumstances are present in this case. Brandt,
¶ 61 Next, plaintiff attempts to distinguish Dealer Management and show that the trial court's reliance on it was misplaced. We discussed this above, noting that, even if the trial court misread and overplayed Dealer Management's holding, its judgment was still correct. We need not consider further plaintiff's contentions regarding Dealer Management.
¶ 62 Plaintiff also criticizes the trial court's focus on the three years of free services that Megadata was to perform. Plaintiff contends that this was a key consideration leading to the trial court's judgment. Once again, even if this were so, and even if it constituted erroneous reasoning on the trial court's part, the trial court arrived at the correct result, so we need not consider it further. Hope,
¶ 63 Accordingly, for the foregoing reasons, we affirm the judgment of the circuit court of Du Page County.
¶ 64 Affirmed.
Justices McLAREN and HUTCHINSON concurred in the judgment and opinion.
NOTES
Notes
[1] Plaintiff conceded that the Village of Bensenville was acting solely as defendant's agent and does not dispute the propriety of the trial court's order dismissing it from this action. The Village of Bensenville is not a party to this appeal.
