Relational database for maintenance information for complex systems

• US 20040039499A1
• Filed: 08/26/2002
• Published: 02/26/2004
• Est. Priority Date: 08/26/2002
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Stinson, Michael W., Felke, Timothy J., Kolbet, David M., Stone, John F., van der Zweep, Jeff J.
• Granted Patent: US 6,829,527 B2
• Time in Patent Office: Days
• US Class Current: 701/29
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A relational database is for relating maintenance information that differs for each of a plurality of complex systems, such as a plurality of differing aircraft, using a common database structure so as to facilitate maintenance procedures for the plurality of complex systems. The database structure comprises: a plurality of primary entities for providing a fault model description of each of the plurality of complex systems, the fault model description including, for each of the plurality of complex systems, failure modes, symptoms and data required to effect a repair; and a categorical entity corresponding to a complex system, such as an aircraft, that enables selection of the fault model description corresponding to the complex system or aircraft. The relational database is particularly suited for use in or by an aircraft maintenance and diagnostic system that assists with fault correction for a fault condition within an aircraft based on a fault model for the aircraft.

Claims

1. A relational database for relating maintenance information that differs for each of a plurality of complex systems using a common database structure so as to facilitate maintenance procedures for the plurality of complex systems, the relational database comprising:

a plurality of primary entities for providing a fault model description of each of the plurality of complex systems, said fault model description including, for each of the plurality of complex systems, failure modes, symptoms and data required to effect a repair; and

a categorical entity corresponding to a complex system that enables selection of the fault model description corresponding to the complex system.

2. The relational database of claim 1 wherein said categorical entity further includes a complex system type and a set of tags that cross reference relevant information within said plurality of primary entities that correspond to said complex system type.

3. The relational database of claim 2 wherein the common database structure provides a new fault model description for a new complex system by entering only new information corresponding to said new complex system in said plurality of primary entities and said categorical entity.

4. The relational database of claim 2 wherein said plurality of primary entities further include an observation entity that includes one of a user reported and automatically reported indication of a problem indexed to an observation code.

5. The relational database of claim 4 wherein said plurality of primary entities further include a fault code entity including a fault code for each distinct set of observation codes that indicate a problem with a system of said complex system.

6. The relational database of claim 5 wherein said plurality of primary entities further include a subsystem entity that includes a subsystem corresponding to one or more fault codes and one of a corresponding list of repairs, list of isolation procedures, and list of deferral procedures.

7. The relational database of claim 6 wherein said subsystem entity is further arranged to consolidate a plurality of fault codes and when each fault code results in the same maintenance procedure indicating said maintenance procedure without resolving a specific fault code.

8. The relational database of claim 6 wherein said plurality of primary entities further include a isolation entity including isolation procedures each having one or more outcomes.

9. The relational database of claim 8 wherein said plurality of primary entities further include an outcome entity having outcomes with each of said outcomes associated with one isolation procedure and one or more repairs wherein an interactive process of performing isolation procedures with resultant outcomes will resolve said one or more repairs to a specific repair.

10. The relational database of claim 1 wherein said categorical entity further includes a thesaurus entity that facilitates a user'"'"'s interface to the relational database by providing a relationship between words used interchangeably in complex system maintenance.

11. The relational database of claim 1 wherein the plurality of complex systems is a plurality of different aircraft.

12. A relational database for relating maintenance information that differs for each of a plurality of complex systems using a common database structure so as to facilitate maintenance procedures for the plurality of complex systems, the relational database comprising:

a categorical entity corresponding to a complex system that enables selection of a fault model description corresponding to said complex system; and

a plurality of primary entities for providing said fault model description corresponding to said complex system selected according to said categorical entity from a plurality of fault model descriptions of the plurality of complex systems, said plurality of fault model descriptions including, for each of the plurality of complex systems, failure modes, symptoms and data required to effect a repair;

wherein said plurality of primary entities facilitate classification of a fault condition and then fault isolation and repair procedures to correct the fault condition.

13. The relational database of claim 12 wherein said plurality of primary entities further includes one of a procedure entity and a document reference entity that correlate with known maintenance procedures.

14. The relational database of claim 12 wherein said categorical entity further includes a thesaurus entity that facilitates conversion of unstructured user inputs into structured inputs.

15. The relational database of claim 12 wherein said categorical entity further includes a change package entity that identifies a set of changes for said complex system.

16. The relational database of claim 15 wherein said change package entity further controls when said set of changes becomes active for said complex system.

17. An aircraft maintenance and diagnostic system for assistance with fault correction for a fault condition within an aircraft based on a fault model for the aircraft, the system comprising in combination:

a user interface;

a computer, coupled to the user interface, having a processor and memory for storing software instructions and a relational database;

said processor executing said software instructions to process information to facilitate the identification and correction of the fault condition within the aircraft according to a fault model defined by said relational database;

said relational database for relating maintenance information that differs for each of a plurality of aircraft using a common database structure so as to facilitate maintenance procedures for the plurality of aircraft, the relational database comprising;

a plurality of primary entities for providing a fault model description of each of the plurality of aircraft, said fault model description including, for each of the plurality of aircraft, failure modes, symptoms and data required to effect a repair; and

a categorical entity corresponding to the aircraft that enables selection of the fault model description corresponding to the aircraft.

18. The aircraft maintenance and diagnostic system of claim 17 wherein said categorical entity further includes an aircraft type and a set of tags that cross reference relevant information within said plurality of primary entities that correspond to said aircraft type.

19. The aircraft maintenance and diagnostic system of claim 18 wherein said plurality of primary entities further include an observation entity that includes one of a user reported and automatically reported indication of a problem indexed to an observation code.

20. The aircraft maintenance and diagnostic system of claim 19 wherein said plurality of primary entities further include a fault code entity including a fault code for each distinct set of observation codes that indicate a problem with a system of said aircraft.

21. The aircraft maintenance and diagnostic system of claim 20 wherein said plurality of primary entities further include a subsystem entity that includes a subsystem corresponding to one or more fault codes and one of a corresponding list of repairs, list of isolation procedures, and list of deferral procedures.

22. The aircraft maintenance and diagnostic system of claim 21 wherein said subsystem entity is further arranged to consolidate a plurality of fault codes and when each fault code results in the same maintenance procedure indicating said maintenance procedure without resolving a specific fault code.

23. The aircraft maintenance and diagnostic system of claim 22 wherein said plurality of primary entities further includes an isolation entity including isolation procedures each having one or more outcomes.

24. The aircraft maintenance and diagnostic system of claim 23 wherein said plurality of primary entities further include an outcome entity having outcomes with each of said outcomes associated with one isolation procedure and one or more repairs wherein an interactive process of performing isolation procedures with resultant outcomes will resolve said one or more repairs to a specific repair.

25. The aircraft maintenance and diagnostic system of claim 17 wherein said categorical entity further includes a thesaurus entity that facilitates a user'"'"'s interface to the relational database by providing a relationship between words used interchangeably in aircraft maintenance.