Diagnostic system and method

• US 20030167111A1
• Filed: 02/26/2003
• Published: 09/04/2003
• Est. Priority Date: 02/05/2001
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Kipersztok, Oscar, Dildy, Glenn A., Chew, Susan Chan, Nelson, Scott L., Rein-Weston, Karl J.
• Granted Patent: US 6,868,319 B2
• Time in Patent Office: Days
• US Class Current: 701/29
• CPC Class Codes: G05B 23/0278 Qualitative, e.g. if-then rules; Fuzzy logic; Lookup tables; Symptomatic search; FMEA

Abstract

A diagnostic system and method are provided that include an interface for receiving input relating to observed symptoms indicative of one or more failed components, a processing element for correlating the input relating to the observed symptoms with at least one suspect component that is capable of causing the observed symptoms upon failure, and a display for presenting information relating to the suspect components. The processing element that correlates the input relating to the observed symptoms with the suspect components in accordance with a diagnostic model constructed based upon systemic information, experiential information and factual information. The processing element generally presents the suspect components in a listing prioritized based upon the relative likelihood that the respective suspect components caused the observed symptoms. Additionally, the processing element can present a prioritized listing of tests that can be conducted to refine the identification and prioritization of the suspect components.

Claims

1. A diagnostic system for identifying a component that has failed, the diagnostic system comprising:

an interface for receiving input relating to observed symptoms indicative of a failed component;

a processing element for correlating the input relating to the observed symptoms with a plurality of suspect components that are each capable of causing the observed symptoms upon failure, said processing element capable of prioritizing the plurality of suspect components based upon a relative likelihood that the respective suspect components caused the observed symptoms, said processing element also capable of identifying at least one test to be performed in order to refine the prioritization of the plurality of suspect components; and

a display for presenting a prioritized listing of the plurality of suspect components and an indication of the at least one test to be performed in order to refine the prioritization of the plurality of suspect components.

2. A diagnostic system according to claim 1 wherein said processing element is capable of identifying a plurality of tests to be performed in order to refine the prioritization of the plurality of suspect components.

3. A diagnostic system according to claim 2 wherein said processing element is further capable of prioritizing the plurality of tests based upon at least one predetermined criteria.

4. A diagnostic system according to claim 3 wherein said interface is capable of receiving input to redefine the at least one predetermined criteria according to which the plurality of tests are prioritized.

5. A diagnostic system according to claim 1 further comprising at least one database containing data related to at least one of the plurality of suspect components, the at least one test to be performed and the correlation between the observed symptoms and the plurality of suspect components.

6. A diagnostic system according to claim 1 wherein said interface is capable of receiving input relating to an outcome of a test, and wherein said processing element is further capable of reprioritizing the plurality of suspect components based upon the outcome of the test and the relative likelihood that the respective suspect components caused the observed symptoms.

7. A diagnostic system according to claim 1 wherein said processing element is further capable of determining a plurality of suspect subsystems that contain components capable of causing the observed symptoms upon failure, wherein said display is capable of listing the plurality of suspect subsystems, and wherein said interface is capable of receiving input indicative of the respective suspect subsystem to be further analyzed.

8. A diagnostic system according to claim 1 wherein said interface is capable of receiving data relating to remedial actions undertaken with respect at least one suspect component.

9. A diagnostic system according to claim 1 wherein said processing element correlates the input relating to the observed symptoms with the at least one suspect component in accordance with a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability.

10. A diagnostic system according to claim 9 wherein said processing element correlates the input relating to the observed symptoms with the at least one suspect component in accordance with the diagnostic model comprising a plurality of nodes and a plurality of arcs that interconnect the nodes in a manner defined by the systemic information and the experiential information, wherein the plurality of nodes include nodes representing the components and the observed symptoms, wherein each node has at least two states, and wherein the diagnostic model assigns a probability to each state of a node based upon at least one of the systemic information, the experiential information and the factual information.

12. A method according to claim 2 wherein identifying at least one test comprises identifying a plurality of tests to be performed in order to refine the prioritization of the plurality of suspect components.

13. A method according to claim 12 further comprising prioritizing the plurality of tests based upon at least one predetermined criteria.

14. A method according to claim 13 further comprising:

receiving input to redefine the at least one predetermined criteria; and

reprioritizing the plurality of tests based upon the redefined criteria.

11. A method for identifying a component that has failed, the method comprising:

receiving input relating to observed symptoms indicative of a failed component;

correlating the input relating to the observed symptoms with a plurality of suspect components that are each capable of causing the observed symptoms upon failure;

prioritizing the plurality of suspect components based upon a relative likelihood that the respective suspect components caused the observed symptoms;

identifying at least one test to be performed in order to refine the prioritization of the plurality of suspect components; and

displaying a prioritized listing of the plurality of suspect components and an indication of the at least one test to be performed in order to refine the prioritization of the plurality of suspect components.

15. A method according to claim 11 further comprising displaying data related to at least one of the plurality of suspect components, the at least one test to be performed and the correlation between the observed symptoms and the plurality of suspect components.

16. A method according to claim 11 further comprising:

receiving input relating to an outcome of a test; and

reprioritizing the plurality of suspect components based upon a relative likelihood that the respective suspect components caused the observed symptoms in light of the outcome of the test.

17. A method according to claim 11 further comprising:

determining a plurality of suspect subsystems that contain components capable of causing the observed symptoms upon failure;

listing the plurality of suspect subsystems; and

receiving input indicative of the respective suspect subsystem to be further analyzed while correlating the input relating to the observed symptoms with the plurality of suspect components.

18. A method according to claim 11 further comprising:

receiving data relating to remedial actions undertaken with respect at least one suspect component; and

creating a summary log of the observed symptoms, the at least one suspect component and the remedial actions.

19. A method according to claim 11 wherein correlating the input relating to the observed symptoms with the at least one suspect component comprises correlating the input relating to the observed symptoms with the at least one suspect component in accordance with a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability.

20. A processing element for identifying a component that has failed, the processing element comprising:

a first processing portion for correlating input relating to at least one observed symptom with a plurality of suspect components that are each capable of causing the at least one observed symptom upon failure, said first processing portion capable of prioritizing the plurality of suspect components based upon a relative likelihood that the respective suspect components caused the at least one observed symptom; and

a second processing portion for identifying a plurality of tests to be performed in order to refine the prioritization of the plurality of suspect components, said second processing portion capable of prioritizing the plurality of tests based upon at least one predetermined criteria.

21. A processing element according to claim 20 wherein said second processing portion is further capable of reprioritizing the plurality of tests based upon a redefinition of the at least one predetermined criteria.

22. A processing element according to claim 20 wherein said first processing portion is further capable of reprioritizing the plurality of suspect components based upon the outcome of a test and the relative likelihood that the respective suspect components caused the observed symptoms.

23. A processing element according to claim 20 further comprising a third processing portion for determining a plurality of suspect subsystems that contain components capable of causing the observed symptoms upon failure.

24. A processing element according to claim 20 wherein said first processing portion correlates the input relating to the observed symptoms with the plurality of suspect components in accordance with a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability.

25. A processing element according to claim 24 wherein said first processing portion correlates the input relating to the observed symptoms with the plurality of suspect components in accordance with the diagnostic model comprising a plurality of nodes and a plurality of arcs that interconnect the nodes in a manner defined by the systemic information and the experiential information, wherein the plurality of nodes include nodes representing the components and the observed symptoms, wherein each node has at least one state, and wherein the diagnostic model assigns a probability to each state of a node based upon at least one of the systemic information, the experiential information and the factual information.

26. A method for identifying a component that has failed, the method comprising:

correlating input relating to at least one observed symptom with a plurality of suspect components that are each capable of causing the at least one observed symptom upon failure;

prioritizing the plurality of suspect components based upon a relative likelihood that the respective suspect components caused the at least one observed symptom;

identifying a plurality of tests to be performed in order to refine the prioritization of the plurality of suspect components; and

prioritizing the plurality of tests based upon at least one predetermined criteria.

27. A method according to claim 26 further comprising:

altering the at least one predetermined criteria; and

reprioritizing the plurality of tests based upon the altered criteria.

28. A method according to claim 26 further comprising:

receiving input representative of an outcome of a test; and

reprioritizing the plurality of suspect components based upon the outcome of the test and the relative likelihood that the respective suspect components caused the observed symptoms.

29. A method according to claim 26 further comprising:

determining a plurality of suspect subsystems that contain components capable of causing the observed symptoms upon failure; and

receiving input identifying at least one of the suspect subsystems for further analysis,

wherein the correlation comprises correlating input relating to at least one observed symptom with a plurality of components of the at least one suspect subsystems that has been identified.

30. A method according to claim 26 further comprising:

receiving data relating to remedial actions undertaken with respect at least one suspect component; and

creating a summary log of the observed symptoms, the at least one suspect component and the remedial actions.

31. A method according to claim 26 wherein correlating the input relating to the observed symptoms with the plurality of suspect components comprises correlating the input relating to the observed symptoms with the at least one suspect component in accordance with a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability.

32. A diagnostic system for identifying a component that has failed, the diagnostic system comprising:

an interface for receiving input relating to observed symptoms indicative of a failed component;

a processing element for correlating the input relating to the observed symptoms with at least one suspect component that is capable of causing the observed symptoms upon failure, said processing element also capable of identifying additional information relating to the at least one suspect component and including at least one item selected from the group consisting of component availability, time to repair the suspect component, cost to repair the suspect component, time to replace the suspect component and cost to replace the suspect component; and

a display for presenting the at least one suspect component and the additional information relating to the at least one suspect component.

33. A diagnostic system according to claim 32 wherein said processing element is capable of prioritizing the at least one suspect component based upon the relative likelihood that the respective suspect component caused the observed symptoms.

34. A diagnostic system according to claim 33 wherein said processing element is also capable of identifying a plurality of tests to be performed in order to refine the prioritization of the at least one suspect component.

35. A diagnostic system according to claim 34 wherein said processing element is further capable of prioritizing the plurality of tests based upon at least one predetermined criteria.

36. A diagnostic system according to claim 35 wherein said interface is capable of receiving input to redefine the at least one predetermined criteria according to which the plurality of tests are prioritized.

37. A diagnostic system according to claim 34 wherein said interface is capable of receiving input relating to an outcome of a test, and wherein said processing element is further capable of reprioritizing the at least one suspect component based upon the outcome of the test and the relative likelihood that the respective suspect components caused the observed symptoms.

38. A diagnostic system according to claim 32 further comprising at least one database containing the additional information.

39. A diagnostic system according to claim 38 wherein said at least one database comprises schematic images of the plurality of suspect components, and wherein said display is capable of presenting the schematic image of a suspect component.

40. A diagnostic system according to claim 39 wherein said display is further capable of indicating the relative likelihood that the suspect component for which a schematic image is presented has failed.

41. A diagnostic system according to claim 38 wherein said at least one database comprises a minimum equipment list, and wherein said display is capable of indicating the respective suspect components that are on the minimum equipment list.

42. A diagnostic system according to claim 38 wherein said at least one database comprises an inventory of components, and wherein said display is capable of indicating the respective suspect components that are in inventory.

43. A diagnostic system according to claim 38 wherein said at least one database comprises textual data describing each suspect component, and wherein said display is capable of presenting the textual data.

44. A diagnostic system according to claim 32 wherein said processing element correlates the input relating to the observed symptoms with the at least one suspect component in accordance with a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability.

45. A diagnostic system according to claim 44 wherein said processing element correlates the input relating to the observed symptoms with the at least one suspect component in accordance with the diagnostic model comprising a plurality of nodes and a plurality of arcs that interconnect the nodes in a manner defined by the systemic information and the experiential information, wherein the plurality of nodes include nodes representing the components and the observed symptoms, wherein each node has at least two states, and wherein the diagnostic model assigns a probability to each state of a node based upon at least one of the systemic information, the experiential information and the factual information.

46. A method for identifying a component that has failed, the method comprising:

receiving input relating to observed symptoms indicative of a failed component;

correlating the input relating to the observed symptoms with at least one suspect component that is capable of causing the observed symptoms upon failure;

identifying additional information relating to the at least one suspect component including at least one item selected from the group consisting of component availability, time to repair the suspect component, cost to repair the suspect component, time to replace the suspect component and cost to replace the suspect component; and

displaying the at least one suspect component and the additional information relating to the at least one suspect component.

47. A method according to claim 46 further comprising prioritizing the at least one suspect component based upon the relative likelihood that the respective suspect component caused the observed symptoms.

48. A method according to claim 47 further comprising identifying a plurality of tests to be performed in order to refine the prioritization of the plurality of suspect components.

49. A method according to claim 48 further comprising prioritizing the plurality of tests based upon at least one predetermined criteria.

50. A method according to claim 49 further comprising receiving input to redefine the at least one predetermined criteria according to which the plurality of tests are prioritized.

51. A method according to claim 48 further comprising:

receiving input relating to an outcome of a test; and

reprioritizing the at least one suspect component based upon the outcome of the test and the relative likelihood that the respective suspect components caused the observed symptoms.

52. A method according to claim 46 wherein identifying additional information comprises identifying schematic images of the plurality of suspect components, and wherein displaying the at least one suspect component and the additional information comprises presenting the schematic image of a suspect component.

53. A method according to claim 52 presenting the schematic image of a suspect component comprises indicating the relative likelihood that the suspect, component has failed.

54. A method according to claim 46 wherein identifying additional information comprises identifying a minimum equipment list, and wherein displaying the at least one suspect component and the additional information comprises indicating the respective suspect components that are on the minimum equipment list.

55. A method according to claim 46 wherein identifying additional information comprises identifying an inventory of components, and wherein displaying the at least one suspect component and the additional information comprises indicating the respective suspect components that are in inventory.

56. A method according to claim 46 wherein identifying additional information comprises identifying textual data describing each suspect component, and wherein displaying the at least one suspect component and the additional information comprises presenting the textual data.

57. A method according to claim 46 wherein the correlation comprises correlating the input relating to the observed symptoms with the at least one suspect component in accordance with a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability.

58. A diagnostic system for identifying a component that has failed, the diagnostic system comprising:

an interface for receiving input relating to observed symptoms indicative of a failed component;

a processing element for correlating the input relating to the observed symptoms with at least one suspect components that is capable of causing the observed symptoms upon failure, said processing element correlating the input relating to the observed symptoms with the at least one suspect component in accordance with a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability; and

a display for presenting the at least one suspect component.

59. A diagnostic system according to claim 58 wherein said processing element correlates the input relating to the observed symptoms with the at least one suspect component in accordance with the diagnostic model comprising a plurality of nodes and a plurality of arcs that interconnect the nodes in a manner defined by the systemic information and the experiential information, wherein the plurality of nodes include nodes representing the components and the observed symptoms, wherein each node has at least two states, and wherein the diagnostic model assigns a probability to each state of a node based upon at least one of the systemic information, the experiential information and the factual information.

60. A diagnostic system according to claim 58 wherein said processing element is capable of prioritizing the at least one suspect component based upon the relative likelihood that the respective suspect component caused the observed symptoms.

61. A diagnostic system according to claim 60 wherein said processing element is also capable of identifying a plurality of tests to be performed in order to refine the prioritization of the at least one suspect component.

62. A diagnostic system according to claim 61 wherein said processing element is further capable of prioritizing the plurality of tests based upon at least one predetermined criteria.

63. A diagnostic system according to claim 62 wherein said interface is capable of receiving input to redefine the at least one predetermined criteria according to which the plurality of tests are prioritized.

64. A diagnostic system according to claim 61 wherein said interface is capable of receiving input relating to an outcome of a test, and wherein said processing element is further capable of reprioritizing the at least one suspect component based upon the outcome of the test and the relative likelihood that the respective suspect components caused the observed symptoms.

65. A diagnostic system according to claim 61 further comprising at least one database containing data related to the at least one suspect component, the plurality of tests to be performed and the correlation between the observed symptoms and the at least one suspect component.

66. A diagnostic system according to claim 58 wherein said processing element is further capable of determining a plurality of suspect subsystems that contain components capable of causing the observed symptoms upon failure, wherein said display is capable of listing the plurality of suspect subsystems, and wherein said interface is capable of receiving input indicative of the respective suspect subsystem to be further analyzed.

67. A diagnostic system according to claim 58 wherein said interface is capable of receiving data relating to remedial actions undertaken with respect at least one suspect component.

68. A method for constructing a diagnostic model for correlating at least one observed symptom with at least one suspect component that is capable of causing the at least one observed symptom upon failure, the method comprising:

obtaining systemic information relating to the components and input-output relationships of the components;

obtaining experiential information relating to direct relationships between component failures and the observed symptoms;

obtaining factual information relating to component reliability; and

constructing the diagnostic model comprising a plurality of nodes and a plurality of arcs that interconnect the nodes in a manner defined by the systemic information and the experiential information, wherein the plurality of nodes include nodes representing the components and the observed symptoms, wherein each node has at least two states, and wherein constructing the diagnostic model comprises assigning a probability to each state of a node based upon at least one of the systemic information, the experiential information and the factual information.

69. A method of troubleshooting a system experiencing a fault, the method comprising:

providing input relating to observed symptoms indicative of a failed component;

executing a diagnostic model constructed based upon systemic information relating to the components and input-output relationships of the components, experiential information relating to direct relationships between component failures and the observed symptoms, and factual information relating to component reliability, wherein execution of the diagnostic model correlates the input relating to the observed symptoms with at least one suspect component;

identifying the suspect component that caused the fault based at least in part upon the correlation of the input relating to the observed symptoms with the at least one suspect component; and

determining remedial action to be taken with respect to the identified component.

70. A method according to claim 69 wherein determining the remedial action comprises determining whether the identified component is to be fixed prior to further operation of the system or whether fixing the identified component is capable of being deferred.

71. A method according to claim 70 wherein determining the remedial action further comprises:

linking to a database comprising a minimum equipment list;

determining if the identified component is included in the minimum equipment list; and

if the identified component is not included in the minimum equipment list, fixing the identified component prior to further operation of the system.

72. A method according to claim 69 wherein determining the remedial action comprises:

linking to a database comprising an inventory of components; and

determining if the identified component is in inventory.

73. A method according to claim 69 wherein determining the remedial action comprises:

linking to a database comprising schematic images of the at least one suspect component; and

reviewing a schematic image of the at least one suspect component.

74. A method according to claim 69 wherein determining the remedial action comprises:

linking to a database comprising textual data describing the at least one suspect component; and

reviewing the textual data describing the at least one suspect component.

75. A method according to claim 69 wherein execution of the diagnostic model correlates the input relating to the observed symptoms with a plurality of suspect components, prioritizes the plurality of suspect components based upon a relative likelihood that the respective suspect components caused the observed symptoms, and identifies at least one test to be performed in order to refine the prioritization of the plurality of suspect components.

76. A method according to claim 75 further comprising:

performing at least one of the identified tests; and

re-executing the diagnostic model based upon the outcome of the at least one test in order to reprioritize the plurality of suspect components.

77. A method according to claim 69 further comprising providing data relating to remedial actions undertaken with respect to the identified component in order to create a summary log of the observed symptoms, the at least one suspect component and the remedial actions.

78. A method of troubleshooting a system experiencing a fault, the method comprising:

providing input relating to observed symptoms indicative of a failed component;

executing a diagnostic model to correlate the input relating to the observed symptoms with a plurality of suspect components that are each capable of causing the observed symptoms upon failure, wherein execution of the diagnostic model also prioritizes the plurality of suspect components based upon a relative likelihood that the respective suspect components caused the observed symptoms, and wherein execution of the diagnostic model further identifies at least one test to be performed in order to refine the prioritization of the plurality of suspect components;

identifying the suspect component that caused the fault based at least in part upon the correlation of the input relating to the observed symptoms with the at least one suspect component; and

determining remedial action to be taken with respect to the identified component.

79. A method according to claim 78 wherein determining the remedial action comprises determining whether the identified component is to be fixed prior to farther operation of the system or whether fixing the identified component is capable of being deferred.

80. A method according to claim 79 wherein determining the remedial action further comprises:

linking to a database comprising a minimum equipment list;

determining if the identified component is included in the minimum equipment list; and

if the identified component is not included in the minimum equipment list, fixing the identified component prior to further operation of the system.

81. A method according to claim 78 wherein determining the remedial action comprises:

linking to a database comprising an inventory of components; and

determining if the identified component is in inventory.

82. A method according to claim 78 wherein determining the remedial action comprises:

linking to a database comprising schematic images of the at least one suspect component; and

reviewing a schematic image of the at least one suspect component.

83. A method according to claim 78 wherein determining the remedial action comprises:

linking to a database comprising textual data describing the at least one suspect component; and

reviewing the textual data describing the at least one suspect component.

84. A method according to claim 78 further comprising:

performing at least one of the identified tests; and

re-executing the diagnostic model based upon the outcome of the at least one test in order to reprioritize the plurality of suspect components.

85. A method according to claim 78 further comprising providing data relating to remedial actions undertaken with respect to the identified component in order to create a summary log of the observed symptoms, the at least one suspect component and the remedial actions.