|
Operator Debrief provides a graphic user interface (GUI) that is easy to use and follows Windows standard terminology and functionality. The GUI presents the user with anomalies that occurred during the system’s operation.
using standard Windows style (i.e. wizard next-back interface).
Operator Debrief anomalies are possible failures within the system that are presented to the operator for confirmation. The goal is to filter out spurious failure conditions, including false alarms and intermittents, and to systematically define the maintenance workload arising from system operations. All system specific data presented is supported using a generic data structure and is configured/defined per system implementation. Each anomaly presented has the following information where available and applicable to the system implementation:
- mission time
- sub-system the anomaly is attributed to
- fault code or fault name
- fault description
- relevant operating conditions at the time the failure was reported
- graphical representation of operator indications associated with the anomaly at the time the failure was reported
Operator Debrief accepts several types of operator feedback for each anomaly presented.
The operator confirms the anomaly to the best of his knowledge. Confirmation selections are configurable per system implementation. Each anomaly
is defaulted to an “unconfirmed” status until the operator selects otherwise.
The operator chooses whether the anomaly is critical to the operation of the system. If the anomaly is critical, the system is determined to be “down” and unavailable for use. If the anomaly is not critical, the system is determined to be “up” and degraded but still available for operation. Each anomaly
is defaulted to a “non-critical” status until the operator selects otherwise.
The operator can select a code indicating when the failure was discovered. A default selection is configured per system implementation. Operator Debrief can be configured to capture these codes from an external software module or maintain them inside its database.
The operator can select a code indicating the malfunction experienced when the failure occurred. Operator Debrief can be configured to capture these codes from an external software module or maintain them inside its database. Malfunction codes are optional.
The operator can select a code indicating the precautionary actions taken when the failure occurred. Operator Debrief can be configured to capture these codes from an external software module or maintain them inside its database. Precautionary actions are optional.
The operator can also add an annotation to each failure. The annotation is entered by the user and is additional information and description the user would like to add. Annotation is optional.
Operator Debrief provides a summary screen where the user can quickly review all session anomalies and provide the necessary feedback for each anomaly (confirmation, criticality, when discovered, malfunction code, precautionary procedures taken, and annotation).
Operator Debrief provides an interface for the user to enter observable failures manually. Using this screen the user creates new faults for the debrief session to be reported to the automated maintenance environment. The user can create a fault by selecting a fault type and entering a fault code or name. These faults would be observable faults that might appear on the system control panel during operation of the system. The fault types and codes/names are configurable per system implementation. He can also create general observable faults. General observables are discrepancies for particular sub-systems and parts that require further investigation by the maintenance crew. For each new fault, he can also provide the same feedback as with anomalies (confirmation, criticality, when discovered, malfunction code, precautionary procedures taken, and annotation).
|
