Legacy Suite Retirement and FMM Stabilization

Challenge

The team charter was to retire a legacy application suite module by module to cut maintenance cost, while the same legacy flight movement system had to stay reliable until the new platform went live.

Approach

• ▸Ran use-case and impacted-business-unit analysis across 20+ maintenance and operations modules (aircraft records, work orders, reliability, audits, vendor lists, and more) and identified low-usage applications and unused charter components for decommissioning.
• ▸Stabilized FMM: fixes for comment rendering, flight-loading errors, status reverting on tail removal, blank-screen and OOOI-edit defects; airport-code priority (IATA, then FAA, then ICAO) to stop missing records in maintenance actuals; a 31-day query limit after broad queries crashed the system; a hotfix that ended recurring crashes from the anomaly finder.
• ▸Decoupled legacy reports and the vouchers app from the flight-leg dependency, positioning Navitaire as the system of record; carried a nine-month PHP/Composer platform upgrade through SRE and DevOps to closure.
• ▸Owned the stations and airports reference apps: audit fields, vendor and de-ice decoupling, removal of the airports dependency as a CAE prerequisite, and an airport-code transition cut over in August 2026 with database inserts, service restarts, crew-system entries, and vendor static-data coordination.

Outcome

• 20+ modules assessed with retirement paths and business owners identified.
• FMM crashes and repeated alerts stopped; the legacy system carried stable to the migration.
• Airport-code transition completed across the ecosystem in one coordinated cutover.