Migration of the Legacy Flight-Operations Application to a New Software Solution, with the Creation of a Data Integration Layer

Troubles :

  1. The legacy application was at the center of the information system, featuring point-to-point connections with other applications in the OCC domain’s information system. As a result, all data integrations required requesting costly quotes from them for tasks that the data team could handle at a lower cost.
  2. From a business standpoint, they wanted to switch solutions, as the software had been in existence since the airline company’s inception.

Owners :

The CCO head is the project sponsor and has appointed a business-side project manager to lead the migration and the creation of the data integration layer.

Success factors :

  1. That the data from the CCO domain not be in a ‘black box’ within the legacy application.
  2. To have control over the integration of data between all internal and external partners of the airline company.
 

Constraints :

This concerns the application that manages airline operations, which serves as the nerve center of an airline company. It is a project under significant operational pressure.

Note that the application has existed since the company’s inception, requiring particular attention during the specification, development, and testing phases.

Actors :

  • Project Manager,
  • 3 functional consultants to specify software interfaces,
  • 4 FTE business analysts to specify data flows,
  • 6 FTE data engineers
  • 1 on-site tester, and a team of testers in India

Archimate diagram that explains the business motivations for the migration and the creation of the data integration layer, as well as its functionalities