Method and system for simulation-based troubleshooting and fault verification in operator-controlled complex systems

• US 20070233438A1
• Filed: 09/16/2005
• Published: 10/04/2007
• Est. Priority Date: 07/01/2004
• Status: Abandoned Application

• Current Assignee: CAE Incorporated
• Original Assignee: CAE Incorporated
• Inventors: Quimper, Remi, Sofia, Kamilia, Zariffa, Nohad, Deziel, Gilbert
• Application Number:
  US11/227,287
• Publication Number:
  US 20070233438A1
• Time in Patent Office: Days
• US Class Current: 703/6
• CPC Class Codes: G05B 23/0278 Qualitative, e.g. if-then rules; Fuzzy logic; Lookup tables; Symptomatic search; FMEA

Abstract

Troubleshooting a cause of anomalous behavior observed during operation of a complex system is enabled by a simulation system that permits an operator to operate a simulation of the complex system to initial control conditions in which the anomalous behavior was observed, and suspend the simulation to input fault symptoms observed during the anomalous behavior. The system selects fault scenarios using the input fault symptoms, injects a selected fault scenario into the simulation, and compares a behavior of the fault-inserted simulation to a behavior of a fault-free simulation operating under the initial control conditions to extract fault symptoms, in order to determine whether the anomalous behavior is reproduced by any inserted fault scenario.

Claims

1. A method of troubleshooting to determine a cause of anomalous behavior observed during operation of a complex system, comprising:

providing an operator'"'"'s station that permits an operator to operate a simulation of the complex system to initial control conditions of the complex system that existed when the anomalous behavior was observed, and to input fault symptoms associated with the anomalous behavior;

using the fault symptoms to compile candidate fault scenarios known to be associated with the operation of the complex system; and

inserting at least one of the candidate fault scenarios into the simulation operating under the initial control conditions to determine whether the fault symptoms are reproduced.

2. The method as claimed in claim 1 wherein using the fault symptoms input by the operator further comprises using the initial control conditions in conjunction with the input fault symptoms to select fault scenarios that are inserted into the simulation.

3. The method as claimed in claim 2 further comprising:

providing an operator graphical user interface associated with the operator'"'"'s station, the operator graphical user interface permitting the operator to input the fault symptoms.

4. The method as claimed in claim 3 further comprising displaying the candidate fault scenarios using the graphical user interface subsequent to the step of determining whether the fault symptoms are reproduced.

5. The method as claimed in claim 3 further comprising providing a fault resolver which receives the input fault symptoms and initial control conditions, and uses them to compile a list of fault scenarios from a database of fault scenarios.

6. The method as claimed in claim 5 further comprising:

running a fault-free simulation under the initial operating conditions of the complex system that existed when the anomalous behavior was observed;

comparing an output of the fault-free simulation with an output of a fault-inserted simulation to identify fault symptoms exhibited by the fault-inserted simulation; and

comparing the identified fault symptoms with the fault symptoms input by the operator to evaluate a probability that the fault scenario caused the observed anomalous behavior.

7. The method as claimed in claim 4 further comprising permitting the operator to select one of the displayed fault scenarios to enter a free play simulation mode in which the fault scenario is inserted into the simulation.

8. A system for simulation-based troubleshooting of a complex system to isolate a cause of anomalous behavior observed during operation of the complex system, comprising:

a simulation of the complex system with a virtual complex system (VCS) control station that permits an operator to operate the VCS to an initial control conditions that simulates an operating state of the real complex system when the anomalous behavior was observed; and

a graphical user interface associated with the VCS control station that permits the operator to enter a fault symptom input mode, and to input fault symptoms observed during the anomalous behavior; and

a fault resolver that uses the input fault symptoms to select at least one candidate fault scenario that may have caused the anomalous behavior.

9. The system as claimed in claim 8 wherein the fault resolver inserts one of the fault scenarios into the simulation, and operates the simulation to determine whether symptoms exhibited by the fault-inserted simulation match the input fault symptoms, in order to assess a probability that the fault scenario was a cause of the anomalous behavior in the real complex system.

10. The system as claimed in claim 9 wherein the fault resolver displays a list of candidate fault scenarios to the operator to permit the operator to select a fault scenario to be inserted into the simulation and permit the operator to observe the behavior of the fault-inserted simulation in a free play mode.

11. The system as claimed in claim 10 wherein the operator graphical user interface permits the operator to switch from the simulation mode to the fault symptom input mode, input fault symptoms using the graphical user interface, and send a query containing the input fault symptoms and operating conditions to the fault resolver, which uses the input fault symptoms to select a list of candidate fault scenarios from a database of known fault scenarios associated with the complex system.

12. The system as claimed in claim 11 further comprising an interface that permits the fault resolver to query the operator for additional observed fault symptoms.

13. The system as claimed in claim 9 wherein the simulation and VCS control station are further adapted to resume the suspended simulation using respective ones of the inserted fault scenarios, until sufficient information is obtained to determine whether the input fault symptoms are observed in any fault-inserted simulation.

14. The system as claimed in claim 9 further comprising:

a fault-free simulation of the complex system that is run in parallel with the fault-inserted simulation;

a symptom extractor for identifying differences between a behavior of the fault-free simulation and the fault-inserted simulation; and

a symptom comparator for comparing the extracted symptoms with the symptoms input by the operator to evaluate and rank a probability that the fault scenario is a cause of the observed anomalous behavior, and to produce a ranked list of fault scenarios.

15. The system as claimed in claim 14 wherein the system simulates system behavior with the fault-inserted scenario at the operator'"'"'s control station, while the symptoms are being extracted and compared.

16. The system as claimed in claim 14 wherein the system displays a ranked list of fault scenarios to the operator to permit the operator to select one of the fault scenarios, and to enter a free play mode in which the fault scenario is inserted.

17. A method of troubleshooting to determine a cause of an anomalous behavior observed during operation of a complex system, comprising:

providing a simulation of the complex system including an operator'"'"'s control station that permits an operator to operate the simulation to, initial control conditions that existed when the anomalous behavior was observed;

accepting inputs from the operator at the operator'"'"'s control station representing fault symptoms associated with the observed anomalous behavior; and

using the input fault symptoms to select at least one fault scenario that may have been responsible for the observed anomalous behavior.

18. The method as claimed in claim 17 further comprising:

inserting a selected fault scenario into a copy the simulation;

running the fault-inserted simulation in parallel with the fault-free simulation; and

comparing a state of the fault-inserted and the fault-free simulation to extract fault symptoms from the fault-inserted simulation.

19. The method as claimed in claim 18, further comprising:

comparing the extracted fault symptoms with the fault symptoms input by the operator; and

computing a probability that the fault scenario caused the anomalous behavior based on the comparison of the extracted fault symptoms with the input fault symptoms.

20. The method as claimed in claim 19, further comprising:

compiling a ranked fault scenario list containing an identification of the fault scenario and the computed probability; and

displaying the ranked fault scenario list to the operator.

21. The method as claimed in claim 20, further comprising:

associating at least one hyperlink with at least one fault scenario in the list prior to displaying the list to the operator, the at least one hyperlink permitting the operator to link to online documentation related to the fault scenario.