Originally Posted by
corporate-wage-slave
I think BA was the first company to use Altéa, but it is now very widely used. FLY was a joint BA - Amadeus project for a bespoke version of Altéa which handles a lot of BA quirks that the first level of Altéa didn't have, and which was also customised to BA's processes and procedures. Amadeus did the coding, but under a joint spec with BA, as I understand it.
That's not entirely correct.
FLY was a wholly BA developed product utilising Amadeus APIs and web services into the Altea suite, firstly Flight Management (FM) in 2012 and latterly Customer Management (CM) in 2016.
The rationale at the time was that FLY would be a single front end used in the airport for both FM and CM, as using Altea would require two separate applications, and potentially being able to join up data with other BA systems - Amadeus RES for Reservations & Ticketing, FICO for Flight Operations, and more ambitiously linking into various sources of customer data.
As others have stated FLY itself was never the root cause but the middleware that sat between it and the backend systems. Again, the rationale for the middleware was being able to join up multiple different backend systems into a single GUI for airport agents.
Ironically, FLY was developed using a Sabre product which is the same product used for Sabre DCS's Interact GUI.