EDWARD J. DAVILA, District Judge.
After a ten day trial, a jury found against Plaintiffs Navcom Technology Inc. and Deere & Company (collectively, "Plaintiffs") on their claim that Defendant Oki Electric Industry Co., Ltd. ("Defendant") breached a written contract for the development and production of a component known as the "RF ASIC." Presently before the court is Plaintiffs' renewed motion for partial judgment as a matter of law under Federal Rule of Civil Procedure 50(b). Dkt. No. 330. Also before the court is Defendant's motion requesting similar relief with regard to issues left undecided by the jury, which it filed "out of an abundance of caution." Dkt. No. 332.
Federal jurisdiction arises pursuant to 28 U.S.C. § 1332. Because the basic facts of this case are well-known to the parties, the court does not recount them here. The court will, however, explain in the memorandum portion of this Order why Plaintiff's Rule 50(b) motion will be denied, and why Defendant's protective motion will be denied as moot.
Federal Rule of Civil Procedure 50 permits a district court to grant judgment as a matter of law when "the evidence, construed in the light most favorable to the nonmoving party, permits only one reasonable conclusion, and that conclusion is contrary to that of the jury."
Taking up Plaintiffs' motion, they contend the jury's finding that Section 1.0 of the Development and Purchase Agreement (the "Agreement") was not breached is contrary to the record and unsupported by legally sufficient evidence. Second, they assert there is no legally sufficient evidence to support the jury's finding that Defendant did not breach Sections 2.6 and 2.8 of the Agreement.
These arguments are unconvincing when tested against the record.
The Agreement underlying this action was admitted into evidence and discussed at length by trial witnesses. Dkt. No. 315, Exs. 46, 125. As relevant here, Section 1.0 of the Agreement, entitled "Term," provides as follows:
Section 2.6 of the Terms and Conditions, entitled "Delivery of Engineering Prototypes," states:
Section 2.8 of the Agreement's Terms and Conditions, entitled "Warranty on Engineering Prototypes," states:
The Complaint's sole claim for breach of contract is governed by California law. "The standard elements of a claim for breach of contract are `(1) the contract, (2) plaintiff's performance or excuse for nonperformance, (3) defendant's breach, and (4) damage to plaintiff therefrom.'"
At trial, the court instructed the jury consistent with the elements of a breach of contract claim and the applicable burden of proof. Final Jury Instruction No. 21 provided as follows:
Dkt. No. 314, at p. 21; Dkt. No. 319, at 1699:7-16.
Twelve questions were submitted to the jury, of which it answered three. Dkt. No. 318. The jury found that Plaintiff did not prove that Defendant breached the Agreement entered on December 14, 2005, or the Agreement entered on November 29, 2006. The jury also found that Defendant was not contractually obligated to develop a four-chip redesign of the RF ASIC.
As to Section 1.0, Plaintiffs' challenge to the verdict is primarily based on the following contention: that after Defendant provided notice terminating the Agreement on July 8, 2008, it was obligated to continue working on the RF ASICs through the end of the "then current term," but did not do so. That contention represents one possible evaluation of the evidence and seemingly could support a breach of contract finding. But the jury did not adopt that evaluation, and the record contains legally sufficient evidence supporting the jury's decision.
In proving its breach of contract claim, Plaintiffs were required to present evidence sufficient to "show it did all, or substantially all, of the significant things that the contract required it to do, or that it was excused from doing those things."
Here, Section 2.6 of the Agreement's Terms and Conditions provided that Defendant would not deliver prototypes to Plaintiff unless it was in receipt of the payments listed in Schedule C of the Agreement. As such, Plaintiff was obligated to make three separate disbursements to ensure Defendant's performance: a $300,000 payment upon signing the Agreement, a $120,000 payment "upon delivery of block specifications, pin assignment and Simulation Results," and a $150,000 payment "upon delivery of Engineering Prototypes." In is undisputed, as John Knight
Plaintiffs' arguments against this conclusion are unconvincing in the context of a Rule 50(b) motion. They first suggest their obligation to make the third payment was excused because the prototypes delivered by Defendant did not function. Plaintiffs do not, however, cite a corresponding provision of the Agreement permitting them to withhold payment under those circumstances. Notably, Section 2.5.3 of the Agreement simply states that "Buyer shall pay to Seller the NRE charges set forth in Schedule C," and that "[p]ayment shall be made in accordance with the terms specified in Schedule C." For its part, and as already described, the only condition imposed on the third payment pursuant to Schedule C is "delivery of Engineering Prototypes," which were to be provided to Plaintiffs to verify the design met their specifications. The jury could have reasonably found based on this language that Plaintiffs' obligation to make the third payment was triggered when Defendants delivered the prototypes, regardless of whether they functioned or actually met Plaintiffs' specifications. Consequently, Plaintiffs have not shown their explanation represents the "only one reasonable conclusion" based on the evidence.
Similarly, the fact that Plaintiffs were never invoiced or asked to make the third payment even though Defendant had previously provided invoices does not alter this conclusion. Course of performance evidence may only be used to explain or supplement the terms of a contract (Cal. Civ. Code § 1856(c)); not "to prove a meaning to which the language of the instrument is reasonably susceptible."
Alternatively, the verdict could be supported by a finding that Plaintiffs failed to prove damages arising from any breach of Section 1.0. "Damages are, of course, a necessary element of the breach of contract cause of action."
Plaintiffs argue, based only on allegations from the Complaint and their own interpretation of admitted exhibit PX 56, that the redesigned four-chip RF ASIC was scheduled for delivery in November, 2008, before the end of the "then current term." Thus, under Plaintiffs' theory, they were harmed when Defendants — after providing notice of termination in July, 2008 — neither delivered a four-chip prototype nor completed "important design work that would have allowed Plaintiffs to avoid or minimize their damages from not having Engineering Prototypes."
This argument misses the mark. Alleged facts are not proven facts, and Plaintiffs' reliance on their Complaint as evidence that Defendant promised a November, 2008 "tapeout" date for a four-chip prototype is entirely misplaced at this stage of the litigation. As is Plaintiffs' dependence on their self-serving description of PX 56, given Plaintiffs' witness, Steven Wilson,
Furthermore, Plaintiffs do not cite any evidence in the record permitting the jury to quantify damages arising from Defendant's purported failure to deliver "important design work." Thus, aside from not meeting the standard imposed by Rule 50(b), this unsupported and undefined hypothetical could be properly disregarded as a valid form of harm for breach of contract.
Plaintiffs' other arguments on this topic fare no better. They state that "[b]ecause it found no breach, the jury did not reach the question on the special verdict form asking whether [Plaintiffs] were harmed by [Defendant's] breach of Section 1.0." Plaintiffs theorize on that basis that "[s]ince the jury did not reach that question, it cannot be implied that the jury's breach finding was based on any finding of lack of harm." The court disagrees. "So long as the special verdict addresses all questions of fact needed to support the entry of judgment, it is harmless error if additional, unnecessary questions are also posed."
And Plaintiffs have not demonstrated an entitlement to nominal damages. They can do so only by first establishing the "only reasonable conclusion" based on the record was that Defendant breached Section 1.0.
In sum, the evidence is not contrary to the verdict with regard to Section 1.0. The jury could have found that Plaintiffs failed to sustain their burden to prove they either performed all duties required by the Agreement or were somehow excused from those duties. The jury could have also found that Plaintiffs failed to prove damages stemming from a breach of that provision. Plaintiffs' arguments are rejected on these bases.
Plaintiffs argue the only reasonable conclusion based on the evidence is that Defendant breached Section 2.6 of the Agreement. Plaintiffs believe Section 2.6 obligated Defendant to "deliver working prototypes that met the specifications." This argument is unpersuasive.
First, the court has explained why the jury could permissibly find that Plaintiffs failed to do everything required of them under the contract by not tendering the third payment due under Schedule C at the time Defendant delivered the prototype. This finding would equally support the non-breach verdict as to Section 2.6.
Second, the jury could have read the Agreement to exclude a requirement that Engineering Prototypes be "working" prototypes. At the conclusion of evidence, the jury was instructed on how they should interpret the Agreement: they were to consider the entire document, "assume the parties intended the words in their contract to have their usual and ordinary meaning" absent some special meaning, and could "consider how the parties acted after the contract was created but before any disagreement between the parties arose." Dkt. No. 314, at pp. 22, 24-25. Neither Section 2.6 nor the definition of "Engineering Prototypes" contains an explicit requirement that delivered prototypes also be "working" prototypes. To the contrary, "Engineering Prototypes" were intended for "verification that the design meets the agreed upon technical specifications, functional evaluation and for informational and testing purposes only." And Section 2.4 of the Agreement required that Engineering Prototypes be accepted by Plaintiff in some form, otherwise they were deemed rejected. Moreover, the Agreement describes two different phases, a development phase and a production phase. Thus, when the Agreement is considered as a whole according to its plain terms, a natural reading is that Defendant was required to submit prototypes during the development phase which Plaintiffs would then verify did or did not meet the specifications by accepting or rejecting them, but that delivery of a non-conforming prototype would not constitute a breach of the Agreement.
Third, the jury could have concluded that Plaintiffs failed to prove harm from a breach of Section 2.6. Plaintiffs' damages theory, as their counsel stated in closing argument, was that they "suffered damages in the form of increased costs by virtue of not having a working RF ASIC" (Dkt. No. 319, at 1597:12-14), and Plaintiffs' expert calculated damages based on a purported increase in costs to manufacture Plaintiffs' device using different components. The jury could have reasonably rejected these damages, which relate to sales of a completed product, as not proximately caused by a breach of Section 2.6 during the development phase of the Agreement.
For these reasons, Plaintiffs are not entitled to judgment as a matter of law for breach of Section 2.6.
Finally, Plaintiffs argue Defendant breached Section 2.8 of the Agreement because it "never repaired or replaced the non-working prototype chips that did not meet the specifications." In support of this argument, Plaintiffs rely on what they characterize as "undisputed evidence that the four-chip design was [Defendant's ] preferred way of repairing or replacing the admittedly non-conforming, three chip prototypes," and the fact that Defendant never tendered a four-chip prototype. The jury, however, found no breach of Section 2.8, and specifically determined that Defendant was not contractually obligated to develop the four-chip design. This is a justifiable view of the evidence.
Galyean testified that after the two versions of the three-chip prototypes were unsuccessful, Plaintiffs agreed with Defendant's assessment that "a significant redesign was going to be required," and that there came a point in time when Plaintiffs agreed to pursue a four-chip prototype. Dkt. No. 286, at 408:18-22; 412:17-23. According to Galyean, the four-chip prototype required a new specification.
Based on this evidence, the jury could have found that despite any defects in the three-chip prototypes, the parties had agreed to pursue another design in its place; for that reason, Plaintiffs did not consider any defects in the three-chip prototype to constitute a breach of Section 2.8. The jury could also permissibly find, contrary to Plaintiffs present argument, that Defendant was not obligated to complete the four-chip prototype because a specification for that design was never created.
Accordingly, there is legally sufficient evidence to support the jury's determination that Defendant did not breach Section 2.8.
Because Rule 50(b) relief will not be granted to Plaintiffs on the breach of contract claim, the court need not address arguments related to Defendant's affirmative defenses. For similar reasons, Defendant's protective Rule 50(b) motion addressing issues undecided by the jury will be denied as moot.
Plaintiffs' Renewed Motion for Partial Judgment as a Matter of Law (Dkt. No. 330) is DENIED. Defendant's Renewed Motion for Judgment as a Matter of Law (Dkt. No. 332) is DENIED AS MOOT.