[Top] | [Previous] | [Next]

A-4. Mission Planning Data Flow Diagrams

A-4.1 Mission Planning - Top Level

Figure A-2 shows the top level DFD for the Mission Planning process. This function performs orbit and attitude maneuver planning and schedules needed contact time for these functions, normal SOH processing, and any mission-related processing. The data stores produced by this function are Orbit Maneuver Parameters, containing a specification of any planned orbit maneuvers, Attitude Maneuver Parameters, containing a specification of any planned attitude maneuvers, and Timeline, containing a schedule of room activities, a schedule of contacts (including pass plans), and a list of planning activities that must occur.

Generate Timeline - This process consolidates all mission requirements into a timeline, or schedule. This schedule, stored in the Timeline data store, contains a list of planning activities, a deconflicted set of satellite contacts, and detailed pass plans for each contact. This process must "negotiate" with the network scheduling function of the RMS and perform internal RFI conflict resolution using the Orbit process. Requirements and resource requests are accepted from the Orbit Maneuver Parameters, Attitude Maneuver Parameters, Timeline, and Mission Planning Requirements data stores.

Figure A-2. Overall data flow diagram for Mission Planning.

Plan Orbital Maneuvers - Based on requirements found in the Timeline data store that initiated the maneuver planning activity, this process plans the indicated orbital maneuver. In addition, constraints and objectives from the Mission Planning Requirements data store must be considered in this process. The orbit ephemeris is needed for this process, along with certain vehicle-specific information, such as thruster locations, and telemetry items, such as tank pressures. This process might request an attitude maneuver planning activity by making an entry in the Timeline data store. Detailed maneuver parameters, including indicators of the commands needed to produce the thrusts are placed in the Orbit Maneuver Parameter data store.

Plan Attitude Maneuvers - Based on requirements found in the Timeline data store that initiated the maneuver planning activity, this process plans the indicated attitude maneuver. In addition, constraints and objectives from the Mission Planning Requirements data store must be considered in this process. The attitude and orbital ephemerides are needed for this process, along with certain vehicle-specific information, such as thruster locations; and telemetry items, such as tank pressures. Detailed maneuver parameters, including indicators of the commands needed to produce the thrusts are placed in the Attitude Maneuver Parameters data store.