Contract analysis

I. Executive Summary This memorandum analyzes the formal acknowledgment of Dormancy Status received from Meridian Code Technologies, Inc. ("MeridianCode") dated August 3, 2023, in response to the dormancy notice issued by Vantage Mobility Systems Corp. ("VMS") on July 14, 2023. VMS's notice invoked Section 9.4 of the Master Embedded Software License and Services Agreement dated June 21, 2022 (the "MESLSA"), which gov

II. Background and Procedural History A. The MESLSA and Project Argonaut The Master Embedded Software License and Services Agreement was executed on June 21, 2022, between VMS, as licensee, and MeridianCode, as licensor. The MESLSA represents a comprehensive embedded software licensing, maintenance, and integration services transaction with a total deal value of approximately $20,000,000 over a five-year term expirin

Section 9.4 of the MESLSA provides, in relevant part, that if the licensee suspends active integration work for more than 120 consecutive days without providing written notice to the licensor invoking Dormancy Status, the licensor may unilaterally convert the license to Dormancy Status and impose certain conditions on reactivation. This provision was negotiated to provide VMS with a right, but not an obligation, to i

III. Summary of MeridianCode's August 3, 2023 Acknowledgment This section provides a detailed summary of the substance of MeridianCode's August 3, 2023 acknowledgment letter, organized by subject matter. The analysis of each issue — including identification of departures from VMS's position, risk assessment, and recommended responses — is set forth in Section IV below. A. Acknowledgment of Dormancy Status MeridianCod

Section 9.4 of the MESLSA provides that during Dormancy Status, MeridianCode's support obligations are reduced to a "critical-security-patch-only level." VMS's July 14, 2023 dormancy notice expressly referenced this provision and stated VMS's understanding that dormancy support is strictly limited to the issuance of critical security patches applicable to the ATLAS-RT codebase then in use. MeridianCode's August 3, 20

Section 4.3 of the MESLSA requires that VMS "commence integration testing on at least two (2) Designated Platforms" within eighteen months of the MESLSA's effective date. The MESLSA was executed on June 21, 2022, which places the Section 4.3 deadline at December 21, 2023 — approximately four months and ten days from the date of this memorandum. If VMS fails to satisfy this requirement, Section 4.3 provides that the n

IV. Detailed Analysis of Departures from VMS Position This section provides a detailed analytical framework for each of the principal and secondary issues identified in MeridianCode's August 3, 2023 acknowledgment, comparing VMS's position with MeridianCode's position, assessing the relative strengths and weaknesses of each position, and providing preliminary recommendations. A. Year 2 Maintenance Fee: VMS Position v

V. Strategic Implications and Interdependencies The issues identified in MeridianCode's August 3, 2023 acknowledgment do not exist in isolation. Each interacts with and is affected by broader strategic considerations relating to VMS's financial position, its obligations to third parties, and its private equity sponsor's investment horizon. This section addresses the principal interdependencies. A. Interaction with Fe