System agnostic front end application for legacy systems

• US 10,372,515 B1
• Filed: 10/28/2016
• Issued: 08/06/2019
• Est. Priority Date: 10/30/2015
• Status: Active Grant

• Current Assignee: American Airlines Incorporated (American Airlines Group Incorporated)
• Original Assignee: American Airlines Incorporated (American Airlines Group Incorporated)
• Inventors: Stripe, Harry E., Wander, Kyle Edward, Adams, Tedd Dale, Kerchal, Justin Eldon
• Primary Examiner(s): McPherson, James M
• Application Number:
  US15/337,473
• Time in Patent Office: 1,012 Days
• Field of Search: 701 296
• CPC Class Codes: B64F 5/60 Testing or inspecting aircraft components or systems
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

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.

Claims

1. A method of 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 comprising:

providing a front end application that is in communication with each of the first legacy computer system and the second legacy computer system, wherein the front end application is displayed on a graphical user interface of a computer;

receiving, via a first webpage displayed on the computer and using the front end application, a plurality of inputs that comprise;

a generic command that is generic to the first operating system and the second operating system; and

an aircraft identifier;

determining, based on the aircraft identifier, whether data related to the aircraft identifier is associated with the first legacy computer system or the second legacy computer system;

if the data related to the aircraft identifier is associated with the first legacy computer system, then transforming the generic command to a first operating system command; and

if the data related to the aircraft identifier is associated with the second legacy computer system, then transforming the generic command to a second operating system command;

wherein the first operating system command is different from the second operating system command, and thus the transformation of the generic command to either the first operating system command or the second operating system command reconciles differences in data schema associated with the first and the second legacy computer systems and allows for the front end application to be a single common front end application to access data within both the first and second legacy computer systems.

2. The method of claim 1,

wherein at least one of the first legacy computer system and the second legacy computer system is a non-web based system;

and

wherein the single common front end application is a web-based application configured to access the first legacy computer system and the second legacy computer system thereby allowing a user of the single common front end application to access the first legacy computer system and the second legacy computer system using a web browser.

3. The method of claim 1, wherein, when the data related to the aircraft identifier is associated with the first legacy computer system, the method further comprises executing the first operating system command;

and wherein at least a portion of the data related to the aircraft identifier is displayed in a second webpage on the computer using the single common front end application in response to the execution of the first operating system command.

4. The method of claim 3,

wherein the generic command is to search for the data related to the aircraft identifier and the first operating system command is to search for the data related to the aircraft identifier;

and

wherein the at least a portion of the data related to the aircraft identifier includes maintenance history for the aircraft associated with the aircraft identifier.

5. The method of claim 3,

wherein the plurality of inputs further comprises a user identifier that is associated with a user of the single common front end application;

wherein the method further comprises customizing a third webpage using the single common front end application based on the user identifier received; and

wherein customizing the third webpage based on the user identifier received prevents displaying work instructions to the user when the user is an unauthorized user.

6. The method of claim 1, wherein the single common front end application validates at least one input from the plurality of inputs.

7. The method of claim 1, wherein transforming the generic command to the first operating system command comprises:

generating a JSON object that includes at least one input from the plurality of inputs;

generating, using the JSON object, a first SOAP message comprising a header that includes a first legacy computer system identifier;

identifying, at a second application, the first legacy computer system identifier in the first SOAP message;

generating, using the first SOAP message, a second SOAP message at a third application, the second SOAP message comprising a first command stack; and

generating, at a fourth application, a second command stack using the second SOAP message, wherein the second command stack is used to generate the first operating system command.

8. The method of claim 1, wherein transforming the generic command to the second operating system command comprises:

generating a JSON object that includes at least one input from the plurality of inputs;

generating, using the JSON object, a third SOAP message comprising a header that includes a second legacy computer system identifier;

identifying, at a fifth application, the second legacy computer system identifier in the third SOAP message; and

generating, at a sixth application, a fourth SOAP message using the third SOAP message, wherein the fourth SOAP message is used to generate the second operating system command.

9. The method of claim 1, wherein the first operating system is a SABRE system.

10. The method of claim 1, wherein the second operating system is a SCEPTRE system.