Related Information

See the ISOC Level III Specification for the requirements driving the design of CHS software systems.

The incoming and outgoing data flows managed by CHS systems are depicted in a series of drill-down diagrams. See Top-Level ISOC Data Flows.

The roles of CHS team members and the procedures they follow in managing flight operations are discussed in the presentation CHS Operations (MS PowerPoint), given at the 2006 ISOC Technical Review (Confluence link). A presentation on the software systems built to support these activities, CHS Design and Implementation (MS PowerPoint), was given at the same Review.

Flight Operations: A Functional Overview

The bulk of the ISOC requirements relate to flight operations. Using operations procedures that serve as the script for MOC activities, pre-defined telecommand lists stored on the ground for transmission, and pre-defined telecommand lists stored on the spacecraft, the ISOC must manage all activities involved in powering the LAT, troubleshooting, changing observation modes, collecting physics or diagnostic data collection, and upgrading the system. The operations procedures and command lists must be designed to achieve the planned goals as well as respond to contingencies. The "flight operations" rubric is also extended to the exchange of data products with the MOC and the GSSC and preparation of science data retrieved from the instrument for automated processing.

Flight operations-related requirements are satisfied by systems built primarily by the Commanding, Health, and Safety team. The CHS team has analyzed the ISOC requirements, identified the data flows stated or implied by these requirements, and is building and testing systems to manage these flows. These systems allow the ISOC to:

The Flight Software team:


Please send all comments and suggestions to: LAT ISOC Web Admin.