Digital Ally, Inc. v. Z3 Technology, LLC

754 F.3d 802, 2014 WL 1979373, 2009 U.S. App. LEXIS 29852
CourtCourt of Appeals for the Tenth Circuit
DecidedMay 16, 2014
Docket12-3258, 12-3268
StatusPublished
Cited by8 cases

This text of 754 F.3d 802 (Digital Ally, Inc. v. Z3 Technology, LLC) is published on Counsel Stack Legal Research, covering Court of Appeals for the Tenth Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Digital Ally, Inc. v. Z3 Technology, LLC, 754 F.3d 802, 2014 WL 1979373, 2009 U.S. App. LEXIS 29852 (10th Cir. 2014).

Opinion

McKAY, Circuit Judge.

This diversity case arises out of two contracts between the parties to this litigation. Both parties have filed appeals, in which Appellant—Cross-Appellee Digital Ally mainly challenges the validity and enforceability of one of the contracts, while Appellee—Cross-Appellant Z 3 Technology challenges certain elements of the damages award.

I. Background

The contracts at issue in this case related to Z 3 ’s design and manüfacturing of circuit board modules for use in Digital’s products. The first contract, signed in November 2008, called for Z 3 to design, manufacture, and deliver to Digital 1,000 modules incorporating Texas Instruments’ DM355 computer chip. The second contract, signed on January 2, 2009, involved a larger quantity of modules that would use Texas Instruments’ next-generation DM365 chip. Both contracts were signed by Robert Haler, who was then Digital’s Executive Vice President of Engineering and Production. The contracts were described as “Production License Agreement[s],” and they expressly provided that the modules would be licensed, not sold, to Digital. (Appellant’s App. at 39, 52.) The contracts both stated they would “be governed by and interpreted in accordance with the laws of the State of Nebraska, without reference to conflict of laws principles.” (Id. at 43, 58.)

The 2008 contract called for Digital to make a total payment of $155,000 in exchange for Z 3 ’s design and delivery of the 1,000 DM355-based modules. Digital paid the first $140,000 required by the contract, but it refused to make the final $15,000 payment. Digital claimed that the DM355 modules provided by Z 3 had hardware and/or software design flaws that resulted in “pink noise” and other problems. 1 The jury ultimately found that both parties had breached the contract, Digital by failing to pay the final $15,000, and Z 3 by failing to satisfy the contract’s hardware warranties. The jury awarded $15,000 to Z 3 for Digital’s breach of its payment obligations, while it awarded $30,000 to Digital for Z 3 ’s failure to satisfy the contract’s hardware warranties. On appeal, the only issue we must consider regarding the 2008 contract is Z 3 ’s argument that it was entitled to prejudgment interest on the $15,000 award.

The 2009 contract, which is the main subject of this appeal, was a somewhat more complex contract than the 2008 contract. Unlike the 2008 contract, this con *808 tract did not simply call for a specific total payment in exchange for a specific number of modules. Rather, the contract included various types of payments Digital would be required to make at different points of the process. First, after setting out a twenty-eight-week design schedule, the contract listed a payment schedule for $300,000 in fees that were payable during the design period. Next, ¶ 14 of the contract—entitled “Guaranteed Minimum Purchase Quantity or Minimum Royalty”—required Digital to fulfill several purchase and/or royalty obligations at various times during the contract period. (Id. at 62 (bolding omitted).) Specifically, the first subsection of ¶ 14 obligated Digital to make a minimum purchase of fifty pre-production samples at a cost of $200 per unit. Subsection (b)(ii) of ¶ 14 then provided for an “initial production order (guaranteed) of 3,000 units @ $100/unit.” (Id. at 63 (capitalization omitted).) Finally, subsection (b) of ¶ 14 included the following terms:

iii) Minimum 12,000 units or equivalent Royalty PER YEAR for 3 years.
(1) LICENSEE [Digital] will provide LICENSOR [Z 3 ] 1st opportunity to manufacture modules given LI-CENSOR’S per module pricing, quality, and delivery are competitive with alternative manufacturers, including consideration of royalty cost for non-Z3 manufactured modules.
(2) Module price ESTIMATED TARGET is $100/module assuming similar [printed circuit board] .layer, component, and architecture to [the modules manufactured pursuant to the 2008 contract]. FINAL PER/MODULE PRICE WILL BE AGREED AFTER COMPLETION OF FINAL HARDWARE DESIGN AND SUBMISSION OF FINAL BOM [ (BILL OF MATERIALS) ] TO LICENSEE. Specialized components may affect this pricing. Pricing is reviewed between LI-CENSOR and LICENSEE every 90 days. LICENSOR will provide LICENSEE 100% complete BOM for LICENSEE’S use in cost analysis. BOM must include all manufacturer names and manufacturer part numbers.
(3) Production Payment Terms: Net 30 days[.]
(4) Production Lead Time: estimated 10 weeks[.]
iv) If LICENSOR cannot provide on-time delivery, a price and quality acceptable to LICENSEE, or is not willing to produce [the DM365-based module], then LICENSEE has the right to use alternative manufacturing. LICENSEE is liable for royalty of $7.50 per unit on modules actually SOLD BY LICENSEE on all modules not manufactured by Z3. []If LICEN[S]EE does not order 36,000 units at 12,000 units per year, LICENSEE is [to] pay a minimum royalty to LICENSOR equivalent to 12,000*$7.500 = $90,000 royalty per calendar year or the pro-rated balance if at least some units have been purchased within the fiscal year in question.

(Id. at 63.)

Initially, both parties began performing their various obligations under the contract. Digital paid the first two payments required under the payment schedule, $75,000 in January 2009 and $50,000 in February 2009, and both sides spent time working on the module’s design. However, in April 2009, Digital sent Z 3 a letter purporting to terminate the contract. It is undisputed that this letter did not comply with the contractual termination require *809 ments, which included a notice-and-cure period. However, in accordance with Digital’s letter, Z 3 stopped its design work on the DM365-based module. Accordingly, no DM365 modules were ever completed byZ 3 .

After repudiating the 2009 contract, Digital filed a lawsuit in the Kansas district court seeking a declaration that the 2009 contract was validly rescinded or void because Executive Vice President Haler, the Digital officer who signed this contract, lacked the authority to do so as a result of a change in Digital’s internal signature policies in December 2008. Digital also raised a claim based on the 2008 contract, alleging that Z 3 breached this contract by delivering faulty modules that did not satisfy the contractual warranties. Z

Related

Cite This Page — Counsel Stack

Bluebook (online)
754 F.3d 802, 2014 WL 1979373, 2009 U.S. App. LEXIS 29852, Counsel Stack Legal Research, https://law.counselstack.com/opinion/digital-ally-inc-v-z3-technology-llc-ca10-2014.