This section describes Telemetry application processes through a series of hierarchical data flow diagrams.
Figure B-2 shows the high-level data flow of Process Satellite Telemetry.
Define Telemetry Procedures - This process allows the Vehicle Contractor and Engineer to contribute to the generation of a Telemetry IB, which serves as a repository/data store for the information indicated.
Configure System - This process enables the Operator to configure the telemetry processing system according to activities in the Timeline data store, and select display formats. When the time for the telemetry activity arrives, received telemetry data, either actual or simulated data, is input to Process Telemetry.
Process Telemetry - This process performs several functions and interfaces with other processes and data stores. Serial PCM and Simulated Serial PCM Streams are input for processing. Quality Assessed EU Measurands are provided to Attitude and Orbit for use in their processing (this interface is accomplished through the data store). Process Telemetry also includes processing for identifying anomalies and recommending corrective actions. If a predefined Recommended Corrective Action is not selected, then an SOH Activity request is written to the Timeline data store, which is read by Mission Planning. Commanding interacts directly with Process Telemetry through receipt of Quality Assessed EU Measurands and transmission of Commanded State Changes when an anticipated anomaly occurs. Raw mission/sensor data measurands are extracted for Mission Data Processing, and Time-Tagged Mainframes are archived to a Raw Data store.