Contract analysis

I. Executive Summary The purpose of this memorandum is to analyze the rights and obligations of our client, Vantage Mobility Systems Corp. ("VMS"), under Section 9.4 (Dormancy) of the Master Embedded Software License and Services Agreement dated June 21, 2022 (the "MESLSA"), entered into between VMS and Meridian Code Technologies, Inc. ("MeridianCode"). This analysis is necessitated by VMS's suspension of active inte

II. Factual Background A. The MESLSA and Project Argonaut On June 21, 2022, VMS and MeridianCode executed the Master Embedded Software License and Services Agreement (the "MESLSA"), a comprehensive agreement governing the licensing, integration, and support of MeridianCode's proprietary embedded real-time operating system, ATLAS-RT™, Version 4.2 (which was subsequently updated to Version 4.2.3 through a maintenance r

III. Analysis of Section 9.4 — Dormancy Provisions A. Text of Section 9.4

Section 9.4 of the MESLSA, captioned "Dormancy," is the operative provision governing the parties' rights and obligations when active integration work is suspended for an extended period. The key operative language of Section 9.4 provides, in relevant part: If Licensee suspends active integration of the Licensed Software for a period exceeding one hundred twenty (120) consecutive days without providing Licensor with

Section 9.4 expressly provides that upon the effective date of Dormancy Status, "all milestone deadlines under this Agreement and any applicable Statement of Work shall be tolled for the duration of the dormancy period." This is one of the most important consequences of dormancy for VMS, and the scope of the tolling language requires careful analysis. The tolling provision plainly applies to the milestone deadlines s

Section 9.4 specifies that during Dormancy Status, MeridianCode's support obligations are "reduced to critical-security-patch-only level." This language is unambiguous: during dormancy, MeridianCode is obligated only to provide patches for critical security vulnerabilities in the ATLAS-RT software. MeridianCode has no obligation during dormancy to provide feature updates, non-security bug fixes, general technical sup

Section 9.4 provides that Dormancy Status "shall not exceed twelve (12) months from the date of Licensor's written acknowledgment thereof, after which the parties shall enter mandatory good-faith renegotiation of the terms of this Agreement, or either party may terminate this Agreement upon thirty (30) days' written notice." This provision establishes an outer limit on the duration of dormancy. The 12-month cap is me

Section 9.4 imposes certain restrictions on VMS during the dormancy period. These restrictions are designed to preserve MeridianCode's intellectual property rights and to prevent VMS from using dormancy as a mechanism to circumvent the MESLSA's licensing restrictions. Specifically, during Dormancy Status, VMS may not: (a) Sublicense the ATLAS-RT software. This restriction is consistent with the general license restri

Section 9.4 preserves VMS's right to reactivate the license at any time during the 12-month dormancy period. Reactivation is accomplished through a straightforward mechanism: VMS provides written notice of reactivation to MeridianCode, and MeridianCode is obligated to resume full support obligations within "a commercially reasonable time." The MESLSA does not define "commercially reasonable time" in this context, whi

IV. Interaction with Other Key MESLSA Provisions

Section 9.4 does not operate in isolation. Several other provisions of the MESLSA interact with the dormancy provision in ways that affect VMS's rights, obligations, and strategic options. We analyze the most significant interactions below. A. Section 4.3 — Use-It-or-Lose-It Clause

Section 4.3 of the MESLSA provides that VMS must commence integration testing on at least two vehicle platforms within 18 months of the Effective Date. The Effective Date is June 21, 2022, which yields a Section 4.3 deadline of December 21, 2023. If VMS fails to meet this deadline, MeridianCode has the right to reduce the scope of VMS's license to a single platform and to require renegotiation of the license fee to r

Section 9.1 of the MESLSA provides that either party may terminate the agreement for convenience upon 180 days' prior written notice. However, Section 9.1 also includes a fee-forfeiture provision: if VMS (as licensee) terminates the MESLSA for convenience prior to the 24-month anniversary of the Effective Date (i.e., prior to June 21, 2024), all prepaid fees are forfeited to MeridianCode. The total prepaid fees as of

Section 7.2 of the MESLSA addresses ownership of derivative works created during the integration process. The provision states that derivative works are "jointly owned" by VMS and MeridianCode, with MeridianCode retaining "a perpetual, royalty-free license to use, modify, and distribute" such derivative works. This provision is unfavorable to VMS, which invested substantial engineering resources in creating the deriv

Section 12.6 of the MESLSA provides that any assignment of the agreement in connection with a change of control of VMS requires MeridianCode's prior written consent, which "shall not be unreasonably withheld, conditioned, or delayed." This provision is standard in technology licensing agreements and reflects MeridianCode's interest in controlling the identity of its licensee. The relevance of Section 12.6 during the

V. Risk Assessment A. Risks to VMS if Dormancy Position Is Challenged We have identified four principal risks to VMS's dormancy position, which we assess as follows: Risk 1: MeridianCode argues that VMS's dormancy notice was late or deficient. Assessment: Low risk. VMS's notice was dated July 14, 2023, six calendar days before the 120-day trigger date of July 20, 2023. The notice was sent to the correct counterparty

VI. Recommendations A. Immediate Actions Based on the foregoing analysis, we recommend that VMS take the following immediate actions:

1. Confirm delivery and receipt of the July 14, 2023 dormancy notice. VMS should confirm with its courier service that the notice was delivered to MeridianCode's offices at 2750 Orchard Blvd., Suite 400, Santa Clara, California 95054, and should obtain the signed return receipt. VMS should also confirm that the email transmission to Priya Ramaswamy was received and not bounced or filtered. Written confirmation of rec

2. Track MeridianCode's formal acknowledgment of Dormancy Status. We anticipate that MeridianCode will issue a formal written acknowledgment of Dormancy Status in August 2023. Upon receipt, the acknowledgment should be immediately forwarded to this firm for analysis. We will review the acknowledgment for any departures from VMS's position regarding the effective date, scope, or terms of dormancy. If MeridianCode's ac

3. Withhold payment of the Year 2 Maintenance Fee. VMS should withhold payment of the $2,400,000 Year 2 Annual Maintenance and Support Fee invoiced by MeridianCode on July 1, 2023, pending resolution of the dormancy fee-abatement question. VMS's internal accounts payable system should be flagged to prevent inadvertent payment. VMS should prepare a written communication to MeridianCode (to be reviewed by this firm bef

4. Prepare notification letter to Pinnacle National Bank, N.A. VMS must notify the administrative agent under its revolving credit facility of the MESLSA dormancy status as a material contract event exceeding $5,000,000. We recommend that this notification be directed to Howard Segal, Relationship Manager at Pinnacle National Bank, and prepared in coordination with VMS's Chief Financial Officer and outside banking co

5. Institute document preservation protocols. VMS should implement formal document preservation protocols for all Project Argonaut integration records, milestone completion documentation, internal engineering logs, and communications with MeridianCode personnel. Key MeridianCode contacts whose communications should be preserved include Gregory L. Fisk (MeridianCode Integration Lead), Diana Cho (MeridianCode Project M

1. Calendar critical deadlines. VMS should calendar the following dates and establish internal monitoring procedures to ensure that no deadline is missed: • 12-month dormancy cap deadline: anticipated August 3, 2024 (dependent on MeridianCode acknowledgment date) • Section 9.1 24-month fee-forfeiture threshold: June 21, 2024 • Section 4.3 Use-It-or-Lose-It deadline: December 21, 2023 (if not tolled by dormancy) • MES

2. Begin preparing for reactivation or structured renegotiation. Well before the 12-month dormancy cap expires, VMS should evaluate its strategic options and develop a plan for either reactivation (resuming integration work on Argonaut-A and Argonaut-C), structured renegotiation (amending the MESLSA to reflect the reduced scope of the program and to restructure fees accordingly), or managed termination (exerci