[Top] | [Previous] | [Next]

F-1. Mission Planning

TT&C Applications

F-1.1 Telemetry

F-1.1.1 Input - Telemetry data values (maneuver-related parameters)

type : data transfer

to/from : from the Quality Assessed EU Measurands data store

or the Process Telemetry function

method : DB read or discrete message

sync/async : sync DB read or async message

timing : none

API standards : SQL, OQL (for implementation)

data arguments : stream_id {id, value}+

stream_id - identifier for telemetry stream

id - identifier for telemetry measurand

value - value for telemetry measurand

status reply : DB read error

F-1.2 Commanding

F-1.2.1 Output - Pass plan

type : data transfer

to/from : to Timeline data store

method : DB write

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : contact_id, pass_plan

contact_id - identifier for contact

pass_plan - data items describing pass plan

status reply : DB write error

F-1.2.2 Output - Mission requirement schedules

type : data transfer

to/from : to Timeline data store

method : DB write

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : vehicle_id, mission_requirement_schedule

vehicle_id - identifier for space vehicle

mission_requirement_schedule - data items describing

consolidated mission requirements

status reply : DB write error

F-1.2.3 Output - Orbit maneuver parameters

type : data transfer

to/from : to Timeline data store

method : DB write

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : vehicle_id, orbit_maneuver_parameters

vehicle_id - identifier for space vehicle

orbit_maneuver_parameters - data items describing

orbit maneuver parameters

status reply : DB write error

F-1.2.4 Output - Attitude maneuver parameters

type : data transfer

to/from : to Timeline data store

method : DB write

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : vehicle_id, attitude_maneuver_parameters

vehicle_id - identifier for space vehicle

attitude_maneuver_parameters - data items describing

attitude maneuver parameters

status reply : DB write error

F-1.3 Orbit

F-1.3.1 Input - SV orbit ephemeris

type : data transfer

to/from : from Orbit Ephemeris data store

method : DB read or file read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : {time, state_vector}+

time - discrete time interval

state_vector - orbitial positon and velocity at specified time

status reply : read error

F-1.3.2 Input - Orbit events

type : data transfer

to/from : from Orbit Ephemeris data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : {event_type, time, event }+

event_type - type of event (Orbital, RFI, Viewing)

time - time of event

status reply : read error

F-1.3.3 Input - Orbit maintenance activity

type : data transfer

to/from : from Timeline data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : anomaly, predicted_time

anomaly - orbit anomaly predicted

predicted_time - predicted time for the anomaly

status reply : read error

F-1.3.4 Output - Radio Frequency Interference (RFI) activity

type : status

to/from : to Deconflict Orbit process

method : discrete message

sync/async : async

timing : none

API standards : TBD

data arguments : noneWouldn't Mission Planning pass the IRON and frequency data for each SV to be deconflicted?(same question as F-1.3.1) time - discrete time interval

state_vector - orbitial positon and velocity

status reply : read error

F-1.4.2 Input - SV attitude events

type : data transfer

to/from : from Attitude Ephemeris data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : {event_type, time, event }+

event_type - type of event (Orbital, RFI, Viewing)

time - time of event

event - description of event

status reply : read error

F-1.4.3 Input - Attitude maintenance activity

type : data transfer

to/from : from Timeline data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : anomaly, predicted_time

anomaly - attitude anomaly predicted

predicted_time - predicted time for the anomaly

status reply : read error

Support Applications

F-1.5 Resource Management

F-1.5.1 Input - Network Schedule

type : service result

to/from : from Resource Management Segment

method : discrete message or DB read

sync/async : async message or sync DB read

timing : none

API standards : SQL, OQL (for implementation)

data arguments : schedule_id, schedule

schedule_id - identifier for schedule

schedule - data items describing schedule

status reply : none

F-1.5.2 Output - Network resource requests

type : service request or data transfer (depending on the

responsiveness of the scheduling function)

to/from : to Resource Management Segment

method : discrete message

sync/async : async

timing : none

API standards : SQL, OQL (for implementation)

data arguments : Time ordered list of: start time, stop time,

RGF, assoc. comm., special equipment,

IRON, purpose, TBD

status reply : request acknowledgment, request

not satisfied

Mission Specific Applications

F-1.6 Vehicle Contractor

F-1.6.1 Input - Static Mission/SOH requirements

type : data transfer

to/from : from Mission Planning Requirements data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : vehicle_id, soh_requirements, TBD

vehicle_id - identifier for space vehicle

soh_requirements - data items describing requirements

status reply : DB read error

F-1.6.2 Input - Orbit Maint. Requirements and Objectives

type : data transfer

to/from : from Mission Planning Requirements data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation)

data arguments : vehicle_id, orbit_requirements, TBD

vehicle_id - identifier for space vehicle

orbit_requirements - data items describing requirements

status reply : DB read error

F-1.6.3 Input - Attitude Maint. Requirements and Objectives

type : data transfer

to/from : from Mission Planning Requirements data store

method : DB read

sync/async : sync

timing : none

API standards : SQL, OQL (for implementation), TBD

data arguments : vehicle_id, attitude_requirements, TBD

vehicle_id - identifier for space vehicle

attitude_requirements - data items describing requirements

status reply : DB read error