Contract analysis

I. Executive Summary This memorandum analyzes whether Vantage Mobility Systems Corp. ("VMS" or "Vantage") is obligated to pay the $2,400,000 Year 2 Annual Maintenance & Support Fee invoiced by Meridian Code Technologies, Inc. ("MeridianCode") on July 1, 2023, given that the MESLSA was placed in Dormancy Status effective August 3, 2023, following VMS's dormancy notice dated July 14, 2023. The analysis examines the int

II. Background and Relevant Facts A. The MESLSA and Its Fee Structure VMS and MeridianCode entered into the Master Embedded Software License and Services Agreement (the "MESLSA") effective June 21, 2022. The MESLSA was the product of approximately seven months of negotiation, with MeridianCode preparing the initial draft and VMS negotiating revisions through successive redlines. The agreement governs the license, int

Section 9.4 of the MESLSA establishes a dormancy mechanism that is triggered when the licensee suspends active integration for more than 120 consecutive calendar days without providing written notice to the licensor. Specifically, Section 9.4 provides, in relevant part: "If Licensee suspends active integration activities under this Agreement for a period exceeding one hundred twenty (120) consecutive calendar days, L

III. Legal Analysis A. Contractual Interpretation of Section 9.4 (Dormancy Provisions)

1. Text of Section 9.4 — Support Reduction to Critical-Security-Patch-Only. The plain language of Section 9.4 is unambiguous on one critical point: during Dormancy Status, MeridianCode's support obligations under Section 5 "shall be reduced to the provision of critical-security-patch-only support." This language is mandatory ("shall be reduced"), unconditional, and comprehensive in its reference to the entirety of Me

2. The Silence of Section 9.4 on Fee Adjustment. The most significant feature of Section 9.4 for purposes of this dispute is what it does not say. The MESLSA drafters addressed dormancy's effect on milestone deadlines (tolling under subsection (b)) and on MeridianCode's support obligations (reduction to critical-security-patch-only under subsection (a)), but Section 9.4 does not contain any express provision addressi

3. Interplay Between Section 9.4 and Maintenance Fee Provisions. The analysis above is reinforced by the fundamental principle that the maintenance fee provisions of Section 5 contemplate payment in exchange for a defined suite of services. The $2,400,000 annual fee is not a standalone obligation divorced from MeridianCode's performance; it is the contractual price for a specific package of support services. When the

1. Pre-Dormancy Period (July 15, 2023 – August 3, 2023). The Year 2 maintenance fee covers the period from the Year 2 payment date through the Year 3 payment date. Assuming a Year 2 service period running from approximately July 15, 2023 (the anniversary of the Year 1 payment date) through July 14, 2024, VMS received full maintenance and support services — i.e., MeridianCode was obligated to provide the complete Sect

2. Dormancy Period (August 3, 2023 – End of Year 2 Period or Reactivation). During the dormancy period, MeridianCode's support obligations are reduced to critical-security-patch-only. The value of patch-only support, relative to the comprehensive maintenance and support package, is the principal variable in the proration calculation. Based on a review of industry benchmarks for embedded software maintenance tiers — i

3. Alternative: Full Abatement During Dormancy. VMS could assert an even more aggressive position: that the maintenance fee should be fully abated during the dormancy period, on the theory that critical-security-patch support is a baseline obligation inherent in the license grant itself — not a separately compensable maintenance service. Under this theory, the obligation to provide critical security patches is implic

1. Annual Fee as Non-Refundable and Non-Proratable. MeridianCode is likely to argue that the MESLSA characterizes the annual maintenance and support fee as a non-refundable obligation payable regardless of usage or service level. Section 5.2(d) of the MESLSA includes the following language: "All fees paid under this Section 5 are non-refundable except as expressly provided herein." MeridianCode may contend that this

2. Invoice Date Precedes Dormancy. MeridianCode has already advanced this argument through Mr. Briscoe's August 14, 2023 letter: the July 1, 2023 invoice predates the dormancy notice (July 14, 2023) and acknowledgment (August 3, 2023), and therefore the obligation to pay the full Year 2 fee crystallized before Dormancy Status took effect. Rebuttal: The timing of the invoice is irrelevant to the underlying contractual

3. Dormancy as Licensee Election. MeridianCode may argue that Dormancy Status is a licensee-elected status and that VMS should bear the financial consequences of its own decision to suspend integration and invoke dormancy. Under this theory, VMS's dormancy election is analogous to a voluntary reduction in usage, and the maintenance fee — like a fixed subscription — remains payable regardless of actual usage. Rebuttal

IV. Strategic Considerations A. Relationship with Overall Fee Exposure The $2,400,000 disputed Year 2 maintenance fee cannot be evaluated in isolation. It is part of a broader financial picture that encompasses VMS's total commitment under the MESLSA: $12,320,000 in fees already paid and approximately $7,680,000 in total remaining contractual commitments. The resolution of the maintenance fee dispute will set a prece

V. Recommendations Based on the foregoing analysis, we recommend the following course of action:

1. Dispute the Invoice. VMS should formally dispute the $2,400,000 Year 2 Maintenance & Support Fee invoiced by MeridianCode on July 1, 2023. The dispute should be communicated in writing from Mr. Cross to Ms. Ramaswamy, with a copy to Mr. Briscoe at Redstone Whitaker LLP, setting forth VMS's position that Dormancy Status reduces MeridianCode's support obligations to critical-security-patch-only under Section 9.4, an

2. Propose Prorated Payment. VMS should offer to pay a prorated amount reflecting the reduced service level during dormancy. Based on the proration analysis set forth in Section III.D above, the appropriate prorated payment falls in the range of approximately $350,000 to $580,000, depending on the valuation assigned to critical-security-patch-only support. We recommend proposing an initial payment of $350,000 (the lo

3. Credit Against Future Obligations. VMS should propose that any Year 2 maintenance fee ultimately determined to be owed be credited against future integration services fees (Milestones 4 and 5, with $1,280,000 remaining) or against an adjusted runtime royalty cap under the MESLSA. This approach is consistent with the broader fee restructuring strategy and avoids additional cash outlay by VMS during the dormancy per

4. Coordinate with Broader Negotiation. The maintenance fee dispute should be integrated into the term sheet for dormancy extension and fee restructuring currently being negotiated with Redstone Whitaker LLP and MeridianCode. A global resolution addressing the maintenance fee, derivative works ownership (DW-001, DW-002, and DW-003), scope reduction from five vehicle platforms to two, and reactivation terms would be s

5. Avoid Full Payment Pending Resolution. VMS should not pay the full $2,400,000 at this time. Payment of the full invoiced amount would: (a) increase VMS's forfeiture exposure under Section 9.1 from $12,320,000 to $14,720,000; (b) potentially waive or undermine VMS's arguments regarding dormancy-period fee adjustment by creating an inference that VMS accepted the obligation to pay full maintenance fees during dorman

6. Preserve Arbitration Option. If MeridianCode insists on full payment and refuses to engage in good-faith negotiation of the maintenance fee dispute, VMS should be prepared to raise the dispute in binding arbitration before a three-arbitrator panel of the Midwest Arbitration Institute in Detroit, Michigan, pursuant to Section 13.2 of the MESLSA. VMS should seek to consolidate the maintenance fee dispute with other