Method, devices and program for computer-aided preventive diagnostics of an aircraft system, using critical event charts

Patent metadata

Field	Value
Publication number	US-9399526-B2
Application number	US-201313861191-A
Country	US
Kind code	B2
Filing date	Apr 11, 2013
Priority date	Apr 12, 2012
Publication date	Jul 26, 2016
Grant date	Jul 26, 2016

Abstract

Aided preventive diagnostics of an aircraft system, comprising a plurality of subsystems at least one of which comprises a subsystem configured for monitoring and notifying a detected event, using critical event charts. After receiving a message notifying the occurrence of said detected event, a minimal diagnostic set relative to said at least one detected event, comprising a plurality of elements each represented by a node of said critical event chart is created, each element of said minimal diagnostic set being determined according to at least one logical implication relation of said critical event chart with a node representing said at least one received notification message. At least some of the elements of said minimal diagnostic set are then ranked, said ranked elements forming part of said diagnostic report.

First claim

The invention claimed is:

1. A method for a computer-aided preparation of a diagnostic report for a system of an aircraft comprising a plurality of subsystems, at least one subsystem of said plurality of subsystems comprising a subsystem having a computer processor and performing monitoring and notification of at least one detected event, the method comprising:
implementing, via the computer processor, a critical event chart substantially modelling said system, said critical event chart comprising a plurality of nodes, each node of said plurality of nodes being linked by a logical implication relation to at least one other node of said plurality of nodes, said plurality of nodes comprising:
a plurality of nodes each representing a notification message capable of being received;
at least one node representing a critical event; and,
a plurality of nodes each representing an element of said system, which is liable to failure, and each such element comprising a suspect candidate item;

receiving, via the computer processor, at least one notification message of the occurrence of said at least one detected event, said detected event comprising said at least one node representing said critical event;
creating, via the computer processor, a minimal diagnostic set relative to said at least one detected event, comprising a plurality of said elements each represented by a node of said critical event chart, each element of said minimal diagnostic set being determined according to at least one logical implication relation of said critical event chart with said node representing said critical event associated with said at least one received notification message; and
ranking, via the computer processor, at least one of said elements of said minimal diagnostic set, said ranked elements forming part of said diagnostic report;
calculating, via the computer processor, a historic persistence weighting for each suspect candidate item in a current flight;
performing, via the computer processor, prioritization of at least one of minimal hitting sets of suspect candidate items based on said historic persistence weighting for establishing a diagnosis relating to the current flight, each hitting set comprising some nodes, and at least one of said hitting sets being minimal when no other hitting set is included in it, said prioritization being determined based on a cardinality of said at least one of said minimal hitting sets and a relevance score being calculated by a sum of corresponding historic persistence weightings of said each suspect candidate item in said minimal hitting set; and
displaying diagnostic results of said diagnostic report via a human-machine interface.

2. The method according to claim 1 , further comprising a step of obtaining data representative of a diagnostic history of said complex system, said ranking step being substantially based on said data representative of said diagnostic history.

3. The method according to claim 1 , wherein said step of ranking at least one of the elements of said minimal diagnostic set comprises a step of ranking at least one of minimal diagnostics.

4. The method according to claim 3 , wherein said historic persistence weighting is calculated for each element of a plurality of elements of said minimal diagnostic set, said historic persistence weighting calculation being based on the presence of each element of said plurality of elements of said minimal diagnostic set in a minimal diagnostic set of said diagnostic history, said ranking of at least one of said minimal diagnostics being substantially based on results of said historic persistence weighting calculation.

5. The method according to claim 3 , further comprising a step of prioritizing elements of said minimal diagnostic set.

6. The method according to claim 1 , wherein said step of ranking at least one of the elements of said minimal diagnostic set comprises a step of ranking problems resulting from minimal diagnostics.

7. The method according to claim 6 , wherein said historic persistence weighting is calculated for each problem of a plurality of problems resulting from said minimal diagnostics, said ranking of problems being substantially based on results of said historic persistence weighting calculation.

8. The method according to claim 1 , further comprising a step of selecting at least one notification message capable of being received represented by a node of said critical event chart and a step of identifying elements of said minimal diagnostic set capable of resulting in the generation of said at least one selected notification message, said identified elements forming part of said diagnostic report.

9. The method according to claim 8 , further comprising a step of calculating a remaining distance before an imminent effect for at least one of said identified elements, said remaining distance being calculated as a function of the number of elements that do not form part of said minimal diagnostic set and a malfunction of which is necessary to the generation of said at least one selected notification message.

10. The method according to claim 8 , further comprising a step of obtaining and assigning attributes to said identified elements.

11. The method according to claim 1 , further comprising a step of selecting at least one failure resolution procedure involving at least one element of said minimal diagnostic set.

12. The method according to claim 1 , according to which said critical event chart is substantially generated by instantiation of at least one generic subchart.

13. A computer program comprising instructions stored on a nontransient memory suitable for the implementation of each of the steps of the method according to claim 1 when said program is executed on a computer.

14. An aircraft maintenance system comprising a calculator that implements each of the steps of the method according to claim 1 .

15. An aircraft comprising the system according to claim 14 .

16. The method according to claim 1 , further comprising identifying and selecting a troubleshooting procedure being common to a resolution of diagnostic problems for resolving at least one diagnostic problem.

Assignees

• Airbus Operations Sas
• Airbus

Inventors

• Cheriere Vincent
• Roger Jeremy
• Debray Vincent
• Fabre Benjamin
• Chantal Philippe

Classifications

• G06F11/0739 Primary

  in a data processing system embedded in automotive or aircraft systems · CPC title

• B64F5/0081 Primary

  Operations & Transport · mapped topic

• G06F11/079

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title

• G05B23/0248

  Causal models, e.g. fault tree; digraphs; qualitative physics · CPC title

• B64F5/40 Primary

  Maintaining or repairing aircraft · CPC title