Operator Debrief makes use of the Diagnostician^TM expert reasoning capability to isolate any faults that occurred during the system’s operation down to the level of isolation identified by the maintenance philosophy for the system/item. 

Operator Debrief provides a generic approach for handling multiple occurrences of raw data fault codes using rules defined by the developer. This type of filtering is referred to as “Occurrence Filtering” and some examples of these rules are: 

• Combining multiple consecutive occurrences into one occurrence. 

• Declaring a raw data fault code as reliable after it occurs X times. 

Operator Debrief provides a generic approach for filtering out false alarms, intermittent and nuisance faults using rules defined by the developer. This type of filtering is referred to as “Anomaly Filtering” and some examples of these rules are: 

• Based on a rule that associates the fault code to specific operational data at the time the fault code was reported, disregard this fault code as a nuisance fault, do not display the fault code to the operator or report the fault code to maintenance as a fault. 

• Always treat this fault code as reliable and it does not need operator confirmation. 

• Based on a rule, treat this fault code as reliable and it does not need operator confirmation. 

• Based on a rule, combine these fault codes into one fault that does not need confirmation. 

• Based on a rule, combine these fault codes into one fault that requires operator confirmation. 

• Always disregard this fault code as a nuisance fault, do not display the fault code to the operator or report the fault code to maintenance as a fault.

Operator Debrief provides a generic approach for fault reporting decisions. The level of isolation achieved by the Diagnostician will be used to determine reporting. All fault codes remaining after all other rules and filtering are performed will be reported. If the Diagnostician isolates to the replaceable item, then the replace procedure will be issued. If the Diagnostician isolates to a subsystem or group of items that require further troubleshooting by a maintenance technician, then the troubleshooting procedure required will be issued. All tags to procedures will be stored inside the Diagnostician’s knowledge base. This type of filtering is referred to as “Reporting Rules.”