Figure B-6 illustrates the processing flow within the Monitor Telemetry process. Subprocesses include Detect Anomalous Condition (1), Diagnose/Isolate Anomaly (2), and Resolve Anomaly (3).
Detect Anomalous Condition - This process inputs Quality Assessed EU Measurands, including measurands that are monitored to detect anomalous conditions in the SV. Based on the Anomaly Detection KB, the set of knowledge bases and/or procedures used to detect an anomalous condition in the SV, and an indicator of a command to change vehicle state, this process verifies that the SV has been configured to the intended state. Detect Anomalous Condition generates as output SV State, which is a set of indicators derived from the telemetry to describe vehicle health and status. SV State may, for example, drive operator interface screens, knowledge bases, etc. Finally, this process outputs an Anomalous Condition (including limit breaks), which is the detected SV fault.
Diagnose/Isolate Anomaly - This function inputs Anomalous Condition and SV State. Based on the Anomaly Diagnosis KB, which is a set of knowledge bases and/or procedures for diagnosing a detected anomalous condition, this process outputs a Diagnosed (and/or isolated) Condition, which is the diagnosed SV fault.
Resolve Anomaly - This function inputs Diagnosed Condition and SV State. Based on the Anomaly Resolution KB, which is a set of knowledge bases and/or procedures for resolving a diagnosed anomalous condition, this process outputs a Corrective Action Message and a Recommended Corrective Action, which may contain a resolution procedure for the anomaly. If an immediate resolution is not available for the anomaly, an SOH Activity request is written to the Timeline data store to be read by Mission Planning.