Unified Front-End Interface for Legacy Airline Maintenance Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
When two airlines merge, mechanics face challenges in accessing and managing data from different legacy computer systems, leading to increased risks of non-compliance due to differences in commands, data inputs, and formatting, as well as the need to access and validate qualifications across disparate systems.
Innovation Solution
A System Agnostic Front End (SAFE) application is developed to provide a common front-end interface that communicates with both legacy systems, transforming generic commands into system-specific commands and ensuring regulatory compliance by accessing and managing data from both systems through a unified interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mechanics access multiple legacy computer systems directly, then they can retrieve data from both airlines, but the complexity of operation increases and compliance risk increases
Solution Approach 1:
The patent implements a common front-end application that serves as an intermediary layer between mechanics and the two different legacy computer systems. This application automatically routes requests to the appropriate backend system based on the airline associated with the aircraft, eliminating the need for mechanics to manually access multiple systems with different interfaces and commands.
Solution Approach 2:
The front-end application provides a universal interface that can access and manage data from both legacy computer systems through a single unified system. This multi-functional application handles diverse operations (accessing aircraft data, mechanic qualifications, maintenance records) across different airlines through one consistent interface.
2Adaptability or versatility
If mechanics are trained on multiple legacy systems, then they can service aircraft from both fleets, but the training time and cost increase
Solution Approach 1:
The common front-end application acts as a mediator that abstracts away the complexities of the underlying legacy systems. Mechanics only need to learn this single unified interface, and the application automatically handles system-specific commands and data formats, eliminating the need for extensive training on multiple different systems.
Solution Approach 2:
The universal front-end application consolidates multiple system-specific interfaces into one unified system that can service aircraft from different fleets. This single application performs the functions of multiple legacy systems, reducing training requirements while maintaining the ability to service diverse aircraft.
3Adaptability or versatility
If different legacy systems are used for different airlines, then each system can maintain its own data format, but the risk of non-compliance increases when accessing cross-system data
Solution Approach 1:
The front-end application serves as a controlled intermediary that manages data access between the two legacy systems. It implements authentication and authorization mechanisms to verify mechanic qualifications against the appropriate backend system, ensuring compliance while allowing access to cross-system data. The application also validates data formats and transformations before presenting information to users.
Data Source
AI summary
A system and method for accessing data in one of a first legacy computer system that has a first operating system and a second legacy computer system that has a second operating system that is different from the first operating system. The method includes providing a front end application that is in communication with the first and second legacy computer systems, with the application being displayed on a user interface of a computer. Aircraft and maintenance data of a first legacy airline is associated with the first legacy computer system and aircraft and maintenance data of a second legacy airline is associated with the second legacy computer system.