GSFC 422-11-19-05
1000
EOS Aqua (PM)
Ground System
Requirements
Document
June 2000
1010
CHANGE RECORD PAGE
DOCUMENT TITLE: EOS Aqua (PM) Ground System Requirements Document (GSRD)
DOCUMENT DATE: June 2000
ISSUE
DATE
PAGES AFFECTED
DESCRIPTION
Original
June 2000
All
Approved by CCR 422-11-19-005
(ESDIS Companion
CCR# 423-42-01-052R4)
DOCUMENT TITLE: EOS Aqua (PM) Ground System Requirements Document
DOCUMENT DATE: June 2000
LIST OF AFFECTED PAGES
Page No.
Revision
Cover
Page
Original
1000-1
Page
No.
Revision
Page No.
Revision
Page No.
Revision
2070-1
Original
5100-2
Original
7300-7
Original
Original
2070-2
Original
5100-3
Original
7300-8
Original
1010-1
Original
2080-1
Original
5100-4
Original
7300-9
Original
1020-1
Original
2080-2
Original
5100-5
Original
7300-10
Original
1025-1
Original
2080-3
Original
5100-6
Original
7300-11
Original
1025-2
Original
2080-4
Original
5100-7
Original
8000-1
Original
1025-3
Original
2100-1
Original
5100-8
Original
8000-2
Original
1025-4
Original
2100-2
Original
5100-9
Original
9000-1
Original
1030-1
Original
2110-1
Original
5100-10
Original
9100-1
Original
1030-2
Original
2120-1
Original
6000-1
Original
9200-1
Original
1040-1
Original
2120-2
Original
6000-2
Original
9300-1
Original
1040-2
Original
2130-1
Original
6000-3
Original
9400-1
Original
1040-3
Original
2130-2
Original
6000-4
Original
9500-1
Original
1040-4
Original
3000-1
Original
6000-5
Original
9600-1
Original
1040-5
Original
3100-1
Original
6100-1
Original
1040-6
Original
3200-1
Original
6100-2
Original
1040-7
Original
3300-1
Original
7000-1
Original
1050-1
Original
3400-1
Original
7000-2
Original
1100-1
Original
4000-1
Original
7000-3
Original
1110-1
Original
4000-2
Original
7100-1
Original
1120-1
Original
4100-1
Original
7110-1
Original
1120-2
Original
4110-1
Original
7110-2
Original
1130-1
Original
4110-2
Original
7120-1
Original
1130-2
Original
4120-1
Original
7120-2
Original
1130-3
Original
4120-2
Original
7130-1
Original
1130-4
Original
4120-3
Original
7140-1
Original
1130-5
Original
4130-1
Original
7140-2
Original
1130-6
Original
4130-2
Original
7200-1
Original
1130-7
Original
4130-3
Original
7210-1
Original
1200-1
Original
4130-4
Original
7210-2
Original
1210-1
Original
4140-1
Original
7210-3
Original
1220-1
Original
4150-1
Original
7210-4
Original
1230-1
Original
4160-1
Original
7210-5
Original
1240-1
Original
4160-2
Original
7220-1
Original
2000-1
Original
4160-3
Original
7220-2
Original
2010-1
Original
4170-1
Original
7220-3
Original
2010-2
Original
4180-1
Original
7230-1
Original
2010-3
Original
4200-1
Original
7230-2
Original
2020-1
Original
4300-1
Original
7300-1
Original
2030-1
Original
4300-2
Original
7300-2
Original
2040-1
Original
5000-1
Original
7300-3
Original
2050-1
Original
5000-2
Original
7300-4
Original
2060-1
Original
5000-3
Original
7300-5
Original
2060-2
Original
5100-1
Original
7300-6
Original
EOS 420-CM-04 (4/92)
1025
Item
No
1
Description
Section Numbers(s); 6000
Disposition
ESDIS takes an exception to
requirements dealing with MGS.
Requirement Numbers(s): 6000.15
EDOS requires an increase of PDS file delivery latency from 4
hours to 8 hours to accommodate the use of the McMurdo
Ground Station (MGS) for contingency X-band support.
Concurrence is needed from the science team. This will only
become applicable if the requirement to use McMurdo for Xband support is accepted.
Workoff Plan: The Aqua Project will need to make decision
on the use of McMurdo. There are three main aspects to this
decision: 1) We need to obtain CSOC’s position on using
McMurdo in demonstration mode. 2) Need to obtain CSOC’s
cost impact for using McMurdo operationally (They are unable
to do this because they are awaiting cost on equipment
upgrades.) and 3) We need to assess impact of NOAA data
delivery requirements on the use of McMurdo.
Resolution Date: 06/00
2
Section Number(s): Multiple
Requirement Number(s): Multiple
ESDIS takes an exception to
requirements dealing with MGS. (See
also #1)
This document was written on the assumption that Aqua will
utilize the McMurdo GS for contingency S and X-band
support. However, the decision to use McMurdo is still
pending.
Workoff Plan: See Workoff Plan for Item #1.
Resolution Date: 06/00
3
Section Number(s): 2040, 2060, 2070, 4110, 4120
Requirement Number(s): 2040.1, table 2060.1, table 2070.1,
2070.4, 4110.2.1, 4120.9, 4120.9.1, 4120.9.2
Requirements were added for support of the SMA service with
the TDRS (H-J) spacecraft. Evaluation is needed by the ground
system elements.
ESDIS takes exception because of
potential cost impacts to various ground
system elements. EMOS cost impacts
have been resolved, but other elements
are still evaluating costs.
Workoff Plan: Submitted CCR 423-42-01-055 "Baseline the
NCCDS/MOC ICD Revision 1" revision 2 which adds SMA
capability for PM in Annex 4. CCR scheduled to be reviewed
at 4/18/00 ICWG. Cost impact small that can be covered by the
existing budget as indicated by Mission System Chair.
Resolution Date: 05/00
4
Section Number(s): 2060, 4150, 6000
Requirement Number(s): 2060.10, 4150.7, 6000.37
ESDIS takes an exception to these
requirements until a definite approach is
determined and cost impacts have been
evaluated.
Requirements were added for support of the SN "911 service"
to be used by the Aqua spacecraft. Evaluation is needed by the
ground system elements.
Work Off Plan: Presentation will be given to ESDIS Project
on details. ESDIS Project will need to approve because it will
require additional funding.
Resolution Date: 06/00
Item
No
5
Description
Section Number(s): 1210.1, 1220.1
Disposition
ESDIS takes no exception to these
requirements.
Requirement Number(s): n/a
Need to add a description for the spacecraft X-band system
comparable to what exists already for the S-band system.
Work Off Plan: Will add description in next CCR submitted.
Resolution Date: 06/00
6
Section Number(s): Multiple
Requirement Number(s): Multiple
The document is written on the assumption that the EPGS is
comprised of the AGS, SGS and MGS, and that the EPGN is
comprised of the EPGS, WGS, and WOTIS. This may need to
be revisited in a later version, as MGS, WGS and WOTIS may
be considered NASA Institutional facilities.
Workoff Plan: Will work that issue once the details are
known.
Resolution Date: 06/00
ESDIS takes an exception to
requirements dealing with MGS. (See
also #1 & #2)
7
Section Number(s): 4170, 6100, 9100, 9400
ESDIS takes no exception to these
requirements.
Requirement Number(s): 4170.2.1, Table 6100.2, 9100.6,
9100.8, 9400.1, 9400.4
Pending approval of CCR#423-01-41-216, the EOC will have
to provide attitude carryout files to both GSFC DAAC and
LaRC DAAC.
Workoff Plan: Once CCR is approved, will coordinate work
to make appropriate changes in document with Dan Marinelli.
Has not been reviewed at the ICWG as of yet.
Resolution Date: 05/00
8
Section Number(s): General
ESDIS takes no exception.
Requirement Number(s): n/a
Addition of a section for listing the documents related to the
GSRD will be beneficial to the concerned parties.
Workoff Plan: Next CCR submission will include a listing of
the related documents.
Resolution Date: 06/00
9
Section Number(s): 7220
Requirement Number(s): 7200.5
FD can asses the overlap of contacts for the listed satellites at
the EPGN sites, but does not have the capability to assess the
use of or contention for EPGN resources (such as the high-rate
data link indicated in current wording). The FD requirement
should only be a minimum timing interval between contacts.
The requirement wording has not yet been agreed by the Aqua
Project.
ESDIS takes exception to having FD
perform this function. FD can asses the
overlap of contacts for the listed
satellites at the EPGN sites, but can not
assess the use of or contention for
EPGN sites.
Workoff Plan: Coordinate meeting with Aqua Project to agree
upon acceptable wording for requirement.
Resolution Date: 06/00
Item
No
10
Description
Section Number(s): Multiple
Requirement Number(s): Multiple
Disposition
ESDIS takes no exception.
The real-time commanding and telemetry functions are taken
away from EDOS and allocated to a newly created EOSDIS
element, the EOS Real-time Processing System (ERPS). This
fact should be reflected in a future GSRD version.
Workoff Plan: Evaluate the need to update GSRD when all
the details regarding the ERPS are defined and document
elsewhere (e.g., ERPS F&PR Spec.).
Resolution Date: 06/00
11
Section Number(s): 9000
Requirement Number(s): Multiple
ESDIS takes no exception. Relate to the
appropriate scope for the document (i.e.
scope of science systems requirements
to be documented in the GSRD).
Evaluate the need to extend the scope of the GSRD to include
the requirements for the MODAPS and AMSR-E SIPS in a
future GSRD version.
Workoff Plan: Aqua Project will work with ESDIS personnel
to define the requirements for the MODAPS and AMSR-E
SIPS and make determination if they should be added to the
GSRD.
Resolution Date: 06/00
12
Section Number(s): 7210
Requirement Number(s): 7210.3.1
Resolve RFA #12 from the Aqua Mission Planning Review
(03/08/00) that addresses possibly increased delivery
frequency of definitive ephemeris data.
ESDIS takes no exception to the
requirement as currently written.
MODIS takes an exception to the
requirement. However, this issue will be
addressed in the resolution of RFA #12.
The requirement may be modified as a
result of RFA #12, and ESDIS would reevaluate at that time.
Workoff Plan: Aqua Project will work with FD and ESDIS
personnel to resolve the issue.
Resolution Date: 06/00
13
Section Number(s): 2100
Requirement Number(s): 2100.7
For performance evaluation period, current EPGN
Requirements (CSOC) specifies "99.1% over one year" as
opposed to "99% over one orbit repeat cycle" (16 days). This
discrepancy needs to be resolved.
Workoff plan: The Aqua Project will work with CSOC
personnel to resolve the discrepancy.
Code 450 takes exception because they
are unsure whether the existing Level 2
requirements for EPGS imply that the
AGS and SGS could meet the 99% data
delivery requirements. Additional
analysis is required.
Resolution Date: 06/00
14
Section Number(s): 5100
ESDIS takes no exception.
Requirement Number(s): Multiple
Need to revise all of the Service Dates provided in the GSRD.
A number of the dates, based on a December 21, 2000 launch
date, have already passed.
Workoff Plan: The Aqua Project will work with appropriate
personnel to rework the Service Dates provided in the GSRD.
Resolution Date: 06/00
Item
No
15
Description
Section Number(s): 2100
Disposition
ESDIS takes no exception to
requirement.
Requirement Number(s): 2100.5
A CSOC personnel wants to specify current wording of LEOP
support requirement in terms of support levels (number of
contacts per orbit, duration of each contact, etc.) versus EPGN
resource (SGS, AGS, DataLynx ™, & KLM-SDS).
Workoff Plan: The Aqua Project will work with CSOC
personnel to resolve issue.
Resolution Date: 06/00
16
Section Number(s): 9100 & 9400
ESDIS takes no exception to
requirement.
Requirement Number(s): 9100.8, 9400.1 & 9400.2
Predicted orbit is not needed at LaTIS (and therefore
Ingest/Archive/DPREP of such is not needed at LDAAC). At
GDAAC, both definitive and predicted orbits are to be
DPREP'd. Need to update requirements.
Workoff Plan: Will coordinate modifications needed to
sections 9100 and 9400 with Dan Marinelli in a future CCR.
Resolution Date: 06/00
17
Section Number(s): 9200
Requirement Number(s): 9200.3
ESDIS takes no exception to
requirement. Relate to the appropriate
scope for the document (i.e. scope of
science systems requirements to be
documented in the GSRD).
A new section for JPL PO DAAC needs to be added to account
for its interfaces with NASDA EOC to receive AMSR-E L1
data and with AMSR-E SIPS and NSIDC to transfer AMSR-E
L1 data. This addition will necessitate modifying 9200.3
Workoff Plan: The proposed changes will be incorporated
into the GSRD in a future CCR.
Resolution Date: 06/00
18
Section Number(s): 2040-2070
Requirement Number(s): Multiple
Current GSRD indicate that Aqua will have 10-15 20-minutes
contacts per day. There is a concern that this will not be
sufficient coverage for activation and checkout time period. A
recommendation is to have the following during the period
from L+3 hours to L+90 days:



Aqua Project takes an exception to
existing number of contacts because
they feel that it will not provide
sufficient coverage for activation and
checkout time period.
SSA not less than 50 minutes per orbit
No more than 2 contacts per orbit and at least 20
minutes per contact.
No less than 80 minutes per orbit for SA+MA
return link coverage
Workoff Plan: The Aqua Project will work with SN
representatives to evaluate the need, availability of this request
and to update the SN requirements based on agreed upon
decisions.
Resolution Date: 06/00
Note: Requirements listed should not be considered as part of the GSRD until
the associated issues are satisfactory resolved by all impacted parties.
1030
Page No.
Title
1000
Cover
1010
Change Record Page
1020
Change Control
1025
Open Items
1030
Contents and Document Outline
1040
Special Abbreviations and Nomenclature
1050
Applicable Aerospace Data System Standards and Documents
1100
Project Description
1110
EOS Aqua Project Description
1120
Experiment(s) Description
1130
Mission Operations Concept
1200
Frequency Utilization Summary
1210
Spacecraft/Payload Telemetry Systems Description
1220
Spacecraft/Payload Telecommunications System Parameters - Telemetry
1230
Spacecraft/Payload Command Systems Description
1240
Spacecraft/Payload Telecommunications System Parameters - Command
2000
Radio Frequency (RF) Telecommunications Requirements
2010
RF Telecommunications - Summary Tables
2020
RF Telecommunications - Telemetry Frame Structure
2030
RF Telecommunications - Command Structure
2040
Space Network (SN) Requirements - Summary
2050
SN - Tracking Requirements
2060
SN - Return Link Requirements
2070
SN - Forward Link Requirements
2080
SN/NCC Requirements
2100
EPGS and WGS Requirements - Summary
2110
EPGS and WGS - Metric Tracking Requirements
2120
EPGS and WGS - Downlink Requirements
2130
EPGS and WGS - Uplink Requirements
3000
Testing Requirements - Summary
3100
Interface Testing
3200
Compatibility Testing
3300
Mission Readiness Testing
3400
Simulators and Test Tools
4000
Earth Observing System (EOS) Operations Center (EOC) Requirements - Summary
4100
EOC - Mission Operations Requirements
4110
EOC - Mission Planning Requirements
4120
EOC - Mission Scheduling Requirements
4130
EOC – Command Management Requirements
4140
EOC - Flight Operations Management Requirements
4150
EOC - Spacecraft and Instrument Health and Safety Maintenance Requirements
4160
EOC - Telemetry Receipt and Processing Requirements
4170
EOC - Engineering Data Analysis Requirements
4180
EOC - History Storage Requirements
4200
EOC - Flight Software Maintenance Requirements
4300
EOC - Facility Requirements
Page No.
Title
5000
Ground System Data Transport Requirements
5100
Detailed Ground System Data Transport Requirements
6000
EDOS Requirements
6100
EDOS Product Requirements
7000
Trajectory and Attitude Support Requirements - Summary
7100
Attitude Determination and Control Requirements
7110
Attitude Determination Support
7120
Attitude Sensor Evaluation and Alignment Support
7130
Attitude Maneuver and Control Support
7140
Onboard Computer Support Processing and Verification
7200
Trajectory Requirements
7210
Trajectory Determination and Error Analysis
7220
Trajectory Design and Control
7230
Acquisition Data (Network Support)
7300
FDS Support Products
8000
FMT Requirements
9000
ECS DAACs and LaTIS Requirements
9100
GSFC DAAC Requirements
9200
NSIDC DAAC Requirements
9300
EDC DAAC Requirements
9400
LaRC DAAC Requirements
9500
LaTIS Requirements
9600
ECS DAAC System Level Requirements
1040
ACE
Attitude control electronics
ACS
Attitude Control System
ADA
Array Drive Assembly
ADC
Affiliated Data Center
AEB
Brazilian Space Agency
AFB
Air Force Base
AGS
Alaska Ground Station
AIRS
Atmospheric Infrared Sounder
AMSR-E
Advanced Microwave Scanning Radiometer - EOS
AMSU-A
Advanced Microwave Sounding Unit - A
AOS
Advanced Orbiting System
APID
Application Process Identifier
BCS
Body Coordinate System
Bps
Bits Per Second
BPSK
Binary Phase Shift Key
C&DH
Command and Data Handling
C&DHS
Command and Data Handling Subsystem
C&T
Command And Telemetry
CADU
Channel Access Data Unit
CCSDS
Consultative Committee for Space Data Systems
CDS
CCSDS Day Segmented Time Code
CERES
Clouds and Earth's Radiant Energy System
CLCW
Command Link Control Word
CLTU
Command Link Transmission Unit
CMD
Command
Co-I
Co-Investigator
COMM
Communication Subsystem
COP
Command Operations Procedure
CP-PDU
Central Processing-Protocol Data Unit
CRC
Cyclic Redundancy Check
CSA
Canadian Space Agency
CSSA
Coarse Sun Sensor Assembly
CTC
CCSDS Unsegmented Time Code
CTM
Communication Test Message
CTV
Compatibility Test Van
CUC
CCSDS Unsegmented Time Code
CVCDU
Coded Virtual Channel Data Unit
DAAC
Distributed Active Archive Center
DAR
Data Acquisition Request
DAS
Direct Access Service
dB
Decibel
DB
Direct Broadcast
dBm
dB milliwatt
dBI
dB isotropic
dBW
dB – watt
DDL
Direct Downlink
deg
Degree
DP
Direct Playback
DPM
Deputy Project Manager
DPREP
Data Pre-Processing
ECS
EOSDIS Core System
EDC
EROS Data Center
EDS
Electrical Distribution Subsystem
EDU
EDOS Data Unit
EEPROM
Electrically Erasable Programmable Read Only Memory
EGS
EOSDIS Ground System
EIRP
Equivalent Isotropically Radiated Power
EDOS
EOS Data and Operations System
ELV
Expendable Launch Vehicle
EMOS
EOS Mission Operations System
EMSn
EOS Mission Support network
ENG
Engineering
EOC
EOS Operations Center
EOL
End Of Life
EOS
Earth Observing System
EOS AM
EOS Morning Launch (AM) (renamed Terra)
EOS-CHEM
EOS Chemistry
EOS Aqua (PM)
EOS Aqua Afternoon Launch (PM)
EOSDIS
Earth Observing System Data and Information System
EPGS
EOS Polar Ground Stations
EPGN
EOS Polar Ground Network
EPS
Electrical Power Subsystem
ESE
Earth Science Enterprise
ESA
European Space Agency
ESA
Earth Sensor Assembly
ESDIS
Earth Science Data and Information System
ESMO
Earth Science Mission Operations
ESSn
EOS Science Support network
ESTMS
EOC Spacecraft Time Management Software
ETS
EOSDIS Test System
ETSF
EOC Training Simulator Facility
FD
Flight Dynamics
FDS
Flight Dynamics System
FDT
Flight Dynamics Team
FDIR
Fault Detection, Isolation, And Recovery
FLG
Flag
FMU
Formatter / Multiplexer Unit
FMT
Flight Software (FSW) Maintenance Team
FOD
Flight Operations Director
FOT
Flight Operations Team
FOV
Field Of View
GBAD
Ground-Based Attitude Determination
GCRP
Global Change Research Program
GCM
Ground Control Message
GCMR
Ground Control Message Request
GDS
Ground Data System
GEM
Graphite Epoxy Motor
GFE
Government Furnished Equipment
GHCC
Global Hydrology and Climate Center
GHz
Gigahertz
GIRD
General Interface Requirements Document
GIIS
General Instrument & Welfare Specification
GMT
Greenwich Mean Time
GN
Ground Network
GNC
Guidance, Navigation and Control
GN&C
Guidance, Navigation and Control Subsystem
GSFC
Goddard Space Flight Center
GSI
Ground System Integration
GSIF
Ground Station Interface Facility
H/K
Housekeeping
HDR
Header
H&S
Health And Safety
HMI
Human Machine Interface
HSB
Humidity Sounder for Brazil
Hz
Hertz
I/F
Interface
I&Q
In-Phase & Quadrature
I&T
Integration And Test
ICD
Interface Control Document
ICESat
Ice, Cloud and Land Elevation Satellite
ID
Identifier
IGCRP
International Global Change Research Program
IIRV
Improved Interrange Vectors
INPE
Instituto Nacionale de Perquisas Espacias
IOC
In-Orbit Checkout
IOT
Instrument Operations Team
IP
International Partner
IPGS
International Partner Ground System
IRU
inertial reference unit
ISC
Instrument Support Controller
IST
Instrument Support Toolkit
IT
Information Technology
IV&V
Independent Verification and Validation
IVVF
Independent Verification & Validation Facility
IWG
Investigator Working Group
JPL
Jet Propulsion Laboratory
kbps
Kilobits Per Second
Kbps
Kilobytes Per Second
kg
Kilogram
kHz
Kilohertz
km
Kilometer
KSA
Ku-Band Single Access
kW
Kilowatt
L/O
Lift-off
LaRC
Langley Research Center
LHC
Left-hand Circular
LHCP
Left-handed Circular Polarization
LZPF
Level Zero Processing Facility
m
Meter
MA
Multiple Access
MAM
Mirror Attenuator Mosaic
M&O
Maintenance And Operations
Mbps
Megabits Per Second
MELV
Medium Expendable Launch Vehicle
MGS
McMurdo Ground Station
MHz
Megahertz
min
Minute
MITI
Ministry of International Trade and Industry
MMFD
Multi-Mission Flight Dynamics
MOA
Memorandum Of Agreement
MODAPS
MODIS Adaptive Processing System
MODIS
Moderate Resolution Imaging Spectro-radiometer
MOU
Memorandum of Understanding
M-PDU
Multiplexed Protocol Data Unit
MRT
Mission Readiness Test
MRTT
Mission Readiness Test Team
MT
Mission Test
N/A
Not Applicable
NAD
Nadir Aperture Door
NASA
National Aeronautics and Space Administration
NASDA
National Space Development Agency (Japan)
NCC
Network Control Center
NCCDS
NCC Data System
NI
NASA Internet
NISN
NASA Integrated Services Network
NMS
Networks and Mission Services
NOAA
National Oceanic and Atmospheric Administration
NRT
Network Readiness Testing
NRT
Non-Real Time
NRZ-L
Non-Return to 0-Level
NSIDC
National Snow and Ice Data Center
NSP
NASA Support Plan
ODB
Operational Database
ODE
Orientation Drive Electronics
OPM
Operations Message
OPS
Operations
OSF
Office of Space Flight
OSI
Open Systems Interconnection
P/B
Playback
P/L
Payload
PAF
Payload Attachment Fitting
PCS
Predefined Command Scripts
PDB
Project Database
PDU
Protocol Data Unit
PC
Power Controller
PCM
Pulse Code Modulated
PDF
Programmable Data Formatter
PDS
Production Data Set
PGS
Product Generation System
PI
Principal Investigator
PM
Phase Modulation
PM
Project Manager
PMDB
Program Master Data Base
PN
Pseudo Noise
PO
Physical Oceanography
PRD
Program Requirements Document
P&S
Planning And Scheduling
PROM
Programmable Read Only Memory
PS
Propulsion Subsystem
PSK
Phase Shift Key
QA
Quality Assessment
QL
Quick-look
QPSK
Quadrature Phase Shift Key
RA
Right Ascension
RAM
Random Access Memory
RCV
Receive
RF
Radio Frequency
RFI
Radio Frequency Interference
RFSOC
Radio Frequency Simulation Operations Center
RHC
Right-hand Circular
RHCP
Right-handed Circular Polarization
R-S
Reed-Solomon
RSS
Root Sum Squared
RSS
Remote Sensing Systems
RT
Real-time
RTCS
Real Time Command Sequence
RTS
Relative Time Sequence
RWA
Reaction Wheel Assembly
SAR
Schedule Add Request
S/C
Spacecraft
S&MS
Structures and Mechanisms Subsystem
SAD
Solar Array Drive
SAS
Solar Array Simulator
SCF
Science Computing Facility
SCID
Spacecraft Identification
SCIF
Spacecraft Interface
SCITF
Spacecraft Integration and Test Facility
SCS
Stored Command Sequence
SDD
Solar Diffuser Door
SDN
Schedule Deletion Notification
SDR
Schedule Delete Request
SEC
Secondary
sfu
Solar flux unit
SGS
Svalbard Ground Station
SIPS
Science Investigator-led Processing Systems
SIT
Spacecraft Interface Test
SMA
S-Band Multiple Access
SMS
Structures and Mechanisms Subsystem
SN
Space Network
SOC
Simulations Operations Center
SPE
Sensor Processing Electronics
SQPN
Staggered Quadri-Phase PN
SQPSK
Staggered Quadrature Phase Shift Key
SRM
Solid Rocket Motor
SRM
Schedule Result Message
SRR
Schedule Result request
SSA
S-Band Single Access
SSR
Solid State Recorder
SSST
Solid State Star Tracker
STA
Star Tracker Assemblies
STPS
Software Telemetry Processor System
SUROM
Start Up Read Only Memory
SVD
Space View Door
TAM
Three-Axis Magnetometer
TBD
To Be Determined
TBR
To Be Resolved
TBS
To Be Supplied
TCS
Thermal Control Subsystem
TCXO
Temperature Controlled Crystal Oscillator
T&DA
Tracking & Data Acquisition
TDRS
Tracking And Data Relay Satellite
TDRSS
Tracking And Data Relay Satellite System
TDRSS-ZOE
Tracking And Data Relay Satellite System – Zone of Exclusion
TF
Transfer Frame
TGT
TDRSS Ground Terminal
TIE
Transponder Interface Electronics
TLM
Telemetry
TMON
Telemetry Monitor
TTM
Time Transfer Message
UPD
User Performance Data
UPDR
User Performance Data Request
UPS
Uninterruptable Power Supply
USCCS
User Spacecraft Clock Calibration System
USM
User Schedule Message
UT
Universal Time
UTC
Universal Time Coordinated
V
Voice
VAFB
Vandenberg Air Force Base
VC
Virtual Channel
VCDU
Virtual Channel Data Unit
W
Watt
WAN
Wide Area Network
WRS
World-Wide Reference System
WGS
Wallops Ground Station
WSC
White Sands Complex
WSGT
White Sands Ground Terminal
WOTIS
Wallops Orbital Tracking Information System
XMIT
Transmit
1050
Applicable Aerospace Data System Standards
Standard
System
Compliance
1.
CCSDS 101.0-B-3
Yes
Recommendation for Telemetry Channel Coding
2.
CCSDS 201.0-B-2 November 1995
Yes
Recommendations for Telecommand,
Part 1, Channel Service
3.
CCSDS 202.0-B-2 November 1992
Yes
Recommendations for Telecommand,
Part 2, Data Routing Service
4.
CCSDS 202.1-R-3
Yes
Deviations
Waivers/Remarks
Recommendations for Telecommand,
Part 2.1: Command Operations Procedures
5.
CCSDS 203.0-B-1 January 1987
Yes
Recommendations for Telecommand,
Part 3, Data Management Service
6.
CCSDS 301.0-B-1 January 1987
Yes
Recommendations for Time Code Formats
7.
CCSDS 701.00-B-2 Issue 1, October 1989
Yes
Recommendations for Advanced Orbiting
Systems, Networks and Data Links
1100
1100.1
General Description
The Earth Observing System (EOS) is the centerpiece of the
National Aeronautics and Space Administration's (NASA's) Earth
Science Enterprise (ESE) program, which is NASA's contribution to
the U.S. Global Change Research Program (GCRP). EOS will
collect data from instruments on several different spacecraft series
to support the long term study of the scope, dynamics and
implications of global change. EOS is composed of low-Earth orbit
missions from the Terra, Aqua, ICESat (Ice, Cloud and Land
Satellite), and CHEM (Chemistry) series of spacecraft, plus an
extensive data and information system. The first EOS spacecraft,
Terra, was launched December 18, 1999. The NASA ESE program
is complemented by Earth-observing missions sponsored by the
following International Partners (IPs): the European Space Agency
(ESA), the Canadian Space Agency (CSA), the National Space
Development Agency (NASDA), Ministry of International Trade and
Industry (MITI) of Japan, and the Brazilian Space Agency (AEB).
Many IPs will supply instruments for flight on EOS missions.
EOS Mission Goals and Objectives
The goal of EOS is to advance the scientific understanding of the
components of Earth system, the interactions among these
components and the ways in which the Earth system is changing
with time. Mission objectives in support of these goals are:
o
To create an integrated scientific observing system which will
provide a full set of essential, global Earth science data in a manner
that maximizes the scientific utility of the data and its analysis.
o
To develop a comprehensive data and information system (EOSDIS) to serve the
needs of scientists performing an integrated, multi-disciplinary study of the Earth
system, including the atmosphere, the oceans, the land surface and the dynamic
and energetic interactions between them.
To acquire the data necessary to create a global database of remote sensing
measurements from space over a long term to enable definitive and conclusive
studies of the Earth system.
o
1110
1110.1
The major science objectives of the EOS Aqua mission are the
study of atmospheric radiation, cloud formation, atmospheric
temperatures and humidities, precipitation, radiative balance,
terrestrial snow, sea ice, sea-surface temperatures and ocean
productivity. The Aqua spacecraft is a 3-axis stabilized vehicle
which will operate in a near-circular, sun-synchronous polar orbit at
an altitude of approximately 705 km, with ascending nodal
crossings at approximately 1:30 PM spacecraft mean local time.
The EOS Aqua payload includes the following six instruments:
o
o
o
o
o
o
Atmospheric Infrared Sounder (AIRS)
Advanced Microwave Sounding Unit - A (AMSU-A)
Advanced Microwave Scanning Radiometer - EOS (AMSR-E)
Clouds and Earth's Radiant Energy System (CERES)
Humidity Sounder for Brazil (HSB)
Moderate Resolution Imaging Spectro-radiometer (MODIS)
Nominal mission duration is 6 years (5-years design lifetime for
spacecraft and instruments) and includes near-continuous nadirpointing data collection.
The Aqua spacecraft supports the above instruments by providing
power, data services, thermal control, spacecraft pointing control,
orbit maintenance propulsion, and space-to-ground
communications.
The EOS Ground System (EGS) provides the Aqua mission with
communication, flight operations, science data processing, data
archival, and data distribution. The EGS elements supporting the
Aqua mission include the EOS Data and Information System
(EOSDIS), NASA Institutional Components (TDRSS, NCC, FD),
NOAA, and International Partner (IP) facilities (Brazil and Japan).
1120
1120.1
The instrument complement for EOS Aqua consists of six
instruments devoted to the characterization of the terrestrial and
oceanic surfaces, clouds, aerosols, and radiative balance. The
following paragraphs describe each instrument and its primary
scientific objective:
Atmospheric Infrared Sounder (AIRS)
The AIRS is a high resolution instrument which measures upwelling
infrared (IR) radiances at 2378 frequencies ranging from 3.74 and
15.4 micrometers. A limited number of visible-wavelength channels
are also present. AIRS is being developed by Lockheed Martin
Infrared Imaging Systems (LMIRIS) under a contract from the Jet
Propulsion Laboratory (JPL). AIRS in conjunction with AMSU and
HSB will provide significant improvements in the accuracy of
several climate and weather parameters, most notably atmospheric
temperatures and humidities.
Advanced Microwave Scanning Radiometer - EOS (AMSR-E)
The AMSR-E is a passive forward-looking scanning microwave
radiometer with a total of 12 channels at 6 discrete frequencies in
the range of 6.9 to 89 GHZ. AMSR-E is being developed by
Mitsubishi Electric Corporation under a contract from National
Space Development Agency of Japan (NASDA). The AMSR data
will be used to provide precipitation rate, water vapor content,
surface moisture content, sea ice coverage, and snow coverage.
Advanced Microwave Sounding Unit (AMSU)
The AMSU is a passive scanning microwave radiometer consisting
of two sensor units, A1 and A2, with a total of 15 discrete channels
operating over the frequency range of 50 to 89 GHZ. The AMSU
operates in conjunction with the AIRS and HSB instruments to
provide atmospheric temperature and water vapor data both in
cloudy and cloud-free areas. AMSU is being developed by Aerojet
under a contract from NASA GSFC.
Clouds and the Earth’s Radiant Energy System (CERES)
The CERES instrument consists of two broadband scanning
radiometers, with three detector channels, covering the bands 0.3
to 5.0 micrometers, 8.0 to 12.0 micrometers and 0.3 to 50
micrometers. One scanner will be operated in the crosstrack mode
for complete spatial coverage from limb to limb; the other with a
rotating scan plane (biaxial) to provide angular sampling. Both
instruments are capable of operating in either mode, but only one
instrument at a time can operate in the biaxial mode. CERES is
being developed by TRW under a contract from NASA LaRC.
Humidity Sounder for Brazil (HSB)
The HSB is a passive scanning microwave radiometer with a total
of 5 discrete channels operating in the range of 150 to 183 GHZ.
The HSB data are used in conjunction with the AIRS data to
provide humidity profile corrections in the presence of clouds. HSB
is being developed by Matra Marconi Space under a contract from
Instituto Nacional de Perquisas Espacias (INPE), Brazil.
Moderate Resolution Imaging Spectro-Radiometer (MODIS)
The MODIS instrument is a passive imaging spectro-radiometer.
The instrument scans a cross-track swath of 2330 km using 36
discrete spectral bands between 0.41 and 14.2 micrometers. The
MODIS will provide imagery of the Earth’s surface and cloud cover
to develop an improved understanding of global dynamics and
processes occurring on the surface and in the lower atmosphere.
MODIS is being developed by Santa Barbara Remote Sensing
under a contract from NASA GSFC.
Table 1120.1 Aqua Instrument Data Generation Rates
Acronym
Instrument Name
Average Data Rate
(kbps)
AIRS
Atmospheric Infrared Sounder
1270
AMSRE
Advanced Microwave Scanning Radiometer
87.4
AMSU
Advanced Microwave Sounding Unit
1.7
CERES
Clouds and the Earth's Radiant Energy System
(2 instruments)
19
HSB
Humidity Sounder for Brazil
4.2
MODIS
Moderate Resolution Imaging SpectroRadiometer
6847
1130 Mission Operations Concept Summary
This summary focuses on the main operations concepts of the
Aqua mission. For greater detail, documents such as the EOS
Aqua Payload Data Book should be consulted.
The EOS Aqua spacecraft will be launched on a Delta Class MELV
from the Vandenberg Air Force Base (VAFB) in California into a
near-circular, sun-synchronous, polar orbit at an altitude of 705 km
with an inclination of approximately 98.2 degrees. The Aqua
spacecraft orbital period will be approximately 100 minutes, with an
ascending node crossing time of 1:30 p.m. spacecraft mean local
time. The ground tracks of the Aqua spacecraft orbit repeats every
16 days or every 233 orbit revolutions.
The initial phase of the Aqua mission, launch through ascent and
orbit insertion, takes approximately 600 minutes (6 orbits). During
this phase, several deployments and activations critical to the
spacecraft and instruments take place. Included in these are the
activation of the S-band transmitter, deployment of the solar array
and recharging of the batteries, deployment of the X-band antenna,
deployment of the CERES instruments, and deployment of AMSRE antenna and sensor. Following the jettisoning of the launch
vehicle fairing at approximately T+5 minutes, the S-band transmitter
is activated giving the spacecraft the capability to transmit telemetry
to the EOC via a TDRS link. During this period, EOC commanding
via TDRS will only be performed if emergency conditions exist.
Beginning with revolution 2, the EPGS sites at Svalbard, Norway,
McMurdo, Antarctica and Poker Flats, Alaska will be available for
command and telemetry relay during a portion of each orbit. The
Wallops Ground Station (WGS) will also be available for telemetry
and command support during 4 to 6 orbits each 24-hour period.
Once the final orbit has been achieved, the Aqua spacecraft will
begin a 90-day On-Orbit Verification phase. During the initial 14
days of this period, the spacecraft will be in an out-gassing mode.
At the conclusion of the 14-day period, on-orbit verification of the
instruments begins and lasts for approximately 76 days, during
which time all instruments will be activated, calibrated and their
operation verified. Spacecraft Bus checkout will run concurrently
with the out-gassing and instrument checkout periods. At the
conclusion of the On-Orbit Verification phase, the Aqua spacecraft
will be declared operational and ready to support science
operations.
During pre-launch, launch and on-orbit verification phases of the
mission, the spacecraft manufacturer (TRW) will have responsibility
for FOT training and mission operations including spacecraft or
payload emergency or anomaly situations. The FOT personnel will
operate at the consoles under the direction of TRW spacecraft
system and sub-system experts. The FOT responsibility will
increase as the on-orbit verification phase nears completion, when
full responsibility for the spacecraft will transition to the ESMO
Project. System experts from TRW will remain available on an oncall basis for the remainder of the mission to assist with spacecraft
anomalies or emergencies.
Figure 1130.1 portrays the operations concept for the Aqua
mission. Subsequent paragraphs explain the overall responsibilities
of various EOSDIS and NASA Institutional elements.
1130.1 EOSDIS
EOSDIS is NASA's Earth science data system for information
management and the archival and distribution of related data.
EOSDIS will provide command and control, scheduling, data
processing, and data archiving and distribution services for the
Aqua mission as well as other EOS missions (Terra and CHEM).
Key components of the EOSDIS include the EOS Polar Ground
Network (EPGN), the EOS Data and Operations System (EDOS),
the EOS Operations Center (EOC), the Instrument Support Toolkits
(IST), the EOS Mission Support network (EMSn), the Distributed
Active Archive Centers (DAAC) and the Science Investigator-led
Processing Systems (SIPSs).
EOS Polar Ground Network (EPGN)
The EPGN is composed of the 3 EPGS ground stations (AGS, SGS
and MGS) as well as the WGS and the Wallops Orbital Tracking
Information System (WOTIS). Scheduling of the EPGS and WGS
sites will be provided through the WOTIS.
EOS Polar Ground Stations (EPGS)
The EPGS sites, the Svalbard Ground Station (SGS) and Alaska
Ground Station (AGS), will provide the primary links between the
Aqua spacecraft and the EDOS LZPF for relay of real-time S-band
command and telemetry data and X-band science and housekeeping playback data. A third EPGS site, the McMurdo Ground
Station (MGS), will provide contingency S-band and X-band
support. Scheduling of EPGS sites will be provided through the
WOTIS. Should the EPGS sites not provide adequate S-band
coverage in special or emergency situations, supplemental service
will be made available through TDRSS or WGS. In the event that
science and housekeeping data playback is not accomplished
during a particular contact, it will be scheduled for playback during
the next spacecraft contact with an EPGS site. The EPGS
(excluding MGS) will be required to provide tracking (Doppler) data
acquisition once per orbit at either AGS or SGS.
Wallops Ground Station (WGS)
The WGS will provide routine realtime S-band command and
telemetry support for the Aqua spacecraft. However, playback of
stored science data (X-band) will not be available through WGS.
Scheduling of the WGS will be provided through the WOTIS. The
WGS will be required to provide tracking (Doppler) data acquisition
twice per day.
Wallops Orbital Tracking Information System (WOTIS)
EPGS and WGS support will be scheduled through the WOTIS,
which serves as the operations center for all EPGN activities. The
WOTIS is responsible for scheduling of EPGS and WGS ground
terminal operations, and performance of link monitoring and fault
isolation.
EOS Data and Operations System (EDOS)
EDOS provides real-time forward and return link data services
between the EOC and the EPGS ground stations, between EOC
and the White Sands Complex (WSC), and between EOC and the
WGS. All commands, telemetry and science data playback will be
relayed to and from EDOS and through the various ground stations.
EDOS receives raw science data, performs level zero processing of
the data and forwards it to the appropriate DAACs. EDOS also
archives Level 0 science data for the life of the Aqua mission, plus
3 years.
EOS Operations Center (EOC)
The EOC provides services for command and control of the
spacecraft and instruments. This includes the ability to process and
display real-time and recorded telemetry, execute real-time
command procedures, build and transmit command and memory
loads, perform mission planning and schedule mission operations,
and perform offline trending and anomaly analysis. The EOC is a
multi-mission facility that currently supports the Terra mission and
will support the Aqua and Chemistry missions.
Instrument Support Toolkit (IST)
The ISTs are installed at each of the remote Instrument Operations
Team (IOT) sites and provide access to EOC functionality. This
includes the ability to schedule instrument operations, monitor realtime instrument telemetry, and perform offline instrument
performance analysis.
EOS Mission Support network (EMSn)
EMSn provides forward and return link transport services for all
Aqua (mission critical) data including spacecraft command,
telemetry, and orbit data (engineering and science data).
Functionally, the EMSn will provide communications services
among the EOS mission critical elements of the ground system.
When appropriate, EMSn will act as the ESDIS agent to procure
NASA Integrated Services Network (NISN) lines and services
required to interface EOSDIS with NASA institutional, external
launch or contractor support elements.
Distributed Active Archive Centers (DAAC)
The collection of DAACs that support Aqua provide the services
and functionality for processing science data from the Aqua
instruments, and for managing and distributing Aqua data products
and other selected data sets. The DAACs provide the ingest and
preprocessing services needed to archive the data, and generate
and distribute science data products to external users.
Science Investigator-led Processing Systems (SIPSs)
In addition to the DAACs, there are other facilities at which EOS
standard products are produced. These facilities are under the
direct control of the instrument Principal Investigators/Team
Leaders or their designees and are referred to as Science
Investigator-led Processing Systems (SIPSs). The SIPSs are
generally, but not necessarily, collocated with the PI's/TL's
Scientific Computing Facilities. Products produced at the SIPS
using investigator-provided systems and software will be sent to
appropriate DAACs for archiving and distribution.
1130.2 NASA Institutional Elements
The EOSDIS is augmented by support from several NASA
institutional facilities. These include the SN (TDRSS/NCC) and
NISN as well as operational support services from Flight Dynamics
(FD).
Space Network (SN)
The SN is the primary system for command and telemetry support
through the first three hours of the mission using SSA service.
Command and telemetry data will flow between the WSC and the
EDOS LZPF. Tracking data will be obtained using TDRSS MA or
SSA two-way coherent tracking contacts and data passed via WSC
to the MMFD and then to the FDS located in the EOC to satisfy
orbit determination support requirements. TDRS support will be
scheduled through the GSFC NCC, which serves as the operations
center for all SN activities. The NCC is responsible for scheduling
of TDRS and ground terminal operations, and performance of link
monitoring and fault isolation. A TDRSS link will be available for
special/emergency command and telemetry support using either
SMA/MA or SSA services throughout the life of the mission.
NASA Integrated Services Network (NISN)
NISN lines and services will be procured if necessary by the EMSn
Project. Together, EMSn/NISN will ensure a high level of security
for all command, telemetry, and other related information relevant
to spacecraft operations.
NASA Flight Dynamics
The Flight Dynamics Team (FDT) will provide orbit and attitude
computational services and navigation data in support of Aqua
using the Flight Dynamics System (FDS) located in the EOC and
the Multi-mission Flight Dynamics in Bldg 28. Prelaunch services
include mission design analysis, trajectory analysis, sensor
analysis, and operations planning. Operational support services
include orbit and attitude determination validation, anomaly
resolution, maneuver planning and support, sensor calibration, and
generation of planning and scheduling data products.
The FDT will perform orbit determination and frequency monitoring
functions for the Aqua spacecraft and TDRSS. Tracking data are
acquired by the TDRSS, EPGS, and WGS and shipped to the
MMFD. The overall functions performed by the FDT are as follows:
o
o
o
o
Launch vehicle support
Tracking data evaluation and spacecraft oscillator frequency calculations
TDRSS orbit determination
Generation of reference information for use in the EOC
Other FDT functions are performed using the FDS in the EOC. The
FDS is comprised of workstations that provide monitors and
generate flight dynamics products to support the services including
the following:
o
o
o
o
o
o
Maneuver planning
EOS Aqua orbit determination
Attitude estimation
Sensor Calibration
Ephemeris loads preparation for Aqua onboard orbit calculation
Generation of planning information
FD supplies hardware, software and documentation support for the
FDS throughout the mission. The FDT supports pre-launch and
early mission operations in the EOC after which operations are
handed over to EOC personnel except for operations related to
unanticipated maneuvers.
Table 1200.1 Frequency Utilization Summary
Planned
Modulation/
Frequencies
Encoding
2106.406250 MHz
NRZ-L
(± Doppler Shift)
PN on I & Q
NRZ-L
Data Rate
EOS Aqua
Other Defining
Service
Antenna
Characteristics
Description
1kbps,125, 250, 500
bps
Zenith omni
(LHC)
TDRSS SSA
Forward
125 bps
Zenith omni
(LHC)
TDRSS SMA/MA
Forward
Nadir omni
(LHC)
PN on I & Q
2106.406250 MHz
PCM/PSK/PM
2 kbps on
16 kHz ± 0.001%
NRZ-L
subcarrier
Non-coherent:
SQPSK with
I: 4.096 kbps
2287.5 MHz ±0.1 MHz
PN on I & Q
Q: 4.096 kbps
Modulation Index 0.7
Radians
EPGS/WGS
S-band Uplink
(sinusoidal subcarrier)
Zenith omni
(LHC)
Rate 1/2
TDRSS
Convolutional & R-S
Coding
SSA Return
NRZ-L
Mode 2 [DG1]
Coherent:
SQPSK with
I: 1.024 kbps
(exact frequency =240/221 of
forward link frequency)
PN on I & Q
Q: 1.024 kbps
Zenith omni
(LHC)
Rate 1/2
(Non-coherent)
Convolutional & R-S
Coding
Mode 1 [DG1]
NRZ-L
(Coherent)
Q:I power ratio
= 1:1
Non-coherent:
SQPSK with
I: 1.024kbps
2287.5 MHz ±0.1 MHz
PN on I & Q
Q: 1.024 kbps
Coherent:
NRZ-L
(exact frequency =240/221 of
forward link frequency)
Zenith omni
(LHC)
Rate 1/2
TDRSS SMA/
Convolutional & R-S
Coding
MA/SSA Return
Modes 1 & 2
Q:I power ratio
= 1:1
Carrier:
PSK/PM
Non-coherent: 2287.5 MHz ±0.1
MHz
NRZ-L
16.384 kbps PSK on
sub-carrier, 524.288
kbps
Nadir omni
(LHC)
Modulation Index 1.1
Radian
EPGS/WGS
S-band downlink
(baseband)
PM on carrier
Coherent:
0.4 Radian
240/221 x uplink frequency
(subcarrier)
Peak Carrier Phase
Rate 1/2
Modulation (radians):
Convolutional & R-S
Coding
1.1 ± 5% (rectangular)
Subcarrier:
1.024 MHz
Carrier Phase Modulation
(radians): 0.4 ± 5% (sinusoid)
8.160 GHz
Balanced SQPSK
I: 75 Mbps
Earth Coverage
NRZ-M
Q: 75 Mbps
(RHC)
Balanced SQPSK
I: 7.5 Mbps
Earth Coverage
NRZ-M
Q: 7.5 Mbps
(RHC)
R-S Coding
Playback to EPGS
R-S Coding
Direct Broadcast &
Direct Downlink
1210
1210.1
The S-Band telemetry system will be utilized to communicate realtime housekeeping, critical health and safety, diagnostic memory
dump data, and back-up recorder dumps of housekeeping data to
the ground systems. Reception of S-Band telemetry will nominally
be supported by EPGS, WGS and the TDRSS. For early orbit and
emergency situations TDRSS services will be used. The S-band
telemetry system will provide an interface for command and
telemetry functions (directly with C&DH) through the launch vehicle
umbilical for prelaunch checkout.
Major components of the S-Band telemetry systems are as follows:
a. C&DH: The Command and Data Handling subsystem will
encapsulate the data in a NASA CCSDS format and apply the
appropriate coding and signal conditioning for the communications
service mode being used. S-band data transmitted through TDRSS,
EPGS, and WGS services has rate 1/2 convolutional and ReedSolomon coding applied. X-Band playback data to the EPGS has
only Reed Solomon coding applied.
b. Transponder: The transponder will operate in the GN and TDRSS modes.
Telemetry data are accepted from the C&DH subsystem. In the GN mode, one
channel will be BPSK modulated on a 1.024 MHz subcarrier which is then
linearly added to the baseband channel and the resultant signal phase
modulated on the carrier. In the TDRSS mode, the data will QPSK modulate the
return link carrier.
c. Antennas: A nadir mounted omni antenna for EPGS and WGS communications
and a zenith antenna for TDRSS service are connected to the receive side of
both transponders at all times. The RF transmit output of a transponder is
selectively configured to a specific antenna. The antennas provide LHC
polarization with at least 70% spherical coverage.
d. RF Switching: RF switching is provided to allow connection of any transmitter to
either of the antennas.
e. Two-way and one-way Doppler tracking is performed through the transponder in
the GN modes and one-way Doppler, two-way Doppler and range tracking in the
TDRSS modes.
f. Time Reference: A master clock in the TIE maintains spacecraft and instrument
time. It receives a heartbeat signal from a stable 100 MHz frequency source
located in the communications subsystem. An internal crystal oscillator is also
available if the external frequency source fails. This allows the master clock to be
maintained within the required ± 10 msec of international atomic time.
1220
1220.1 S-Band
a. S-Band Transponder:
(1) RF power: 5.0 watts minimum
(2) GN mode: NRZ-L data phase-shiftkeyed on a 1.024 MHz subcarrier and
the NRZ-L baseband high rate data,
which is then phase-modulated on the
S-band carrier
(3) TDRSS mode: Channels: I and Q. Q/I power ratio: 1:1
(4) Frequency determining source:
Derived from the receiver if operating in
the coherent mode (DG1 Mode 1).
Derived from Temperature Controlled
Crystal Oscillator (TCXO) if Noncoherent (DG1 Mode 2)
b. Antennas:
(1) Number, type: Omni (2 - zenith and nadir)
(2) Beam, beam width: Spacecraft spinning, 70% coverage;
normal earth pointing attitude, ± 64
degrees cone about nadir (EPGS and
WGS)
± 90 degrees cone about zenith (TDRSS)
(3) Polarization: (LHC)
(4) Transmit Gain: Nadir antenna, - 3 dBi; zenith antenna , - 1.5dBi
(5) Estimated passive losses between transponder and omni
antennas:
Nadir antenna, 4.1 dB; zenith antenna, 4.8 dB
1220.2 X-Band
TBS
1230
1230.1
The S-Band command systems provide for the reception of EOS
Aqua spacecraft commands. Command reception will be supported
through the EPGS and WGS. TDRSS will also provide support
during all mission phases. Command reception capability will also
be provided via the launch vehicle umbilical for prelaunch checkout.
The major components of the S-Band telecommunication system
for command reception are as follows:
a. S-Band Omni Antennas: See page 1220.1 for description.
b. Signal Combiners: Both of the omni antennas are passively combined to allow
command reception from either antenna by both of the transponders connected
to the antennas.
c. Temperature Controlled Crystal Oscillator (TCXO): See page 1220.1 for
description.
d. S-Band Transponder: In the GN mode, the transponder receives and
demodulates the uplink command signal. In the TDRSS mode, the S-Band
transponder receives, despreads, and demodulates the command signals sent to
the spacecraft. In addition, it detects the PN code epoch on the TDRSS forward
link and provides PN epoch outputs when the PN epoch is detected to the C&DH
Subsystem for time tagging and spacecraft clock calibration processing.
e. Both transponders pass commands to the C&DH subsystem which selects and
processes commands from the transponder for which "bit" and "RF" lock and
"start sequence detection" occurs first.
1240
1240.1
Command Receiver - GN Mode:
1. The subcarrier is phase modulating on the carrier
2. Subcarrier frequency: 16 KHz
3. Center frequency (nominal) : 2106.406250 MHz ± ground station to spacecraft
Doppler Shift.
Command Receiver - TDRSS Mode
(1) Center Frequency (Nominal): 2106.40625 MHz (SSA/MA
service)
(2) Command threshold: -137.5dBm @ 125 bps; -128.5 dBm
@ 1 Kbps
(3) Acquisition Frequency Range: ± 1500 Hz of actual center
frequency with frequency rate of change £ 70 Hz/sec
(maximum).
(4) Carrier Tracking Range: ± 160 KHz about assigned
center frequency
(5) Unbalanced QPSK modulation with I to Q power ratio of
10 dB.
(6) Both I and Q channels are PN spectrum spreaded.
2000
2000.1
EOS Aqua command and telemetry communications shall be supported through
the use of the EPGS and WGS. TDRSS services shall be used for command and
telemetry communications during early orbit, when near-continuous coverage is
required and during emergency situations throughout the miroutinely required for
a minimum of one pass per day for clock correlation and tracking data collection.
The EPGS shall be required to take 1 tracking pass per orbit (either AGS or
SGS).
The requirements in this section relate to five mission phases, as follows:
1. Prelaunch testing and launch preparation
2. Launch/Ascent (from launch until approximately L+10 hours)
3. Spacecraft Activation (from L+10 hours to L+2 weeks)
4. Instrument Checkout (from approximately L+2 weeks to approximately L+90
days)
5. Normal Operations (Including special operations)
2010
2010.1
Institutional elements shall support the links listed in Table 2010.1.
Table 2010.1 RF Link Summary
S/C
Transmit/Receive
Link #
Data Rate
Purpose
1
Receive
125 bps
Command, TDRSS SMA/MA
2
Receive
1 kbps*
Command, TDRSS SSA
3
Receive
2 kbps
Command, EPGS and WGS
4A and 4B
Transmit
1.024 kbps/1.024
kbps
Telemetry, TDRSS SMA/MA
4A - R/T eng, processor dump, identical data on I&Q
4B - R/T eng, processor dump, identical data on I&Q
5A and 5B
Transmit
4.096 kbps/4.096
kbps
Telemetry, TDRSS SSA
5A - R/T eng, processor dump, identical data on I&Q
5B - R/T eng, processor dump, identical data on I&Q
6A and 6B
Transmit
1.024 kbps/1.024
kbps
Telemetry, TDRSS SSA
6A - R/T eng, processor dump, identical data on I&Q
6B - R/T eng, processor dump, identical data on I&Q
7A and 7B
Transmit
16.384 kbps and
Telemetry, EPGS and WGS
524.288 kbps
7A - R/T eng data , processor data dump
7B - Stored engineering data
8
Transmit
75/75 Mbps
Direct playback of stored science and engineering data
to EPGS (150 Mbps total on I & Q channels)
*Nominal command data rate shown, contingency rates of 125, 250 and 500bps
also available via TDRSS SSA service
2010.2
The Virtual Channel (VC) identification assigned to the various
types of data is shown in Table 2010.2. There are multiple APIDs
per VC, except for VCs 40, & 45.
Table 2010.2 Virtual Channel Identification Assignments (SBand)
Label
VC-0
Source
EOC/EDOS
VC-1
Destination
S/C
Data Rate(s)
125, 250, 500
bps,
Instruments
Channel ID
I-channel SN,
Purpose
Normal Command
Subcarrier
1 kbps, 2 kbps
EPGS and WGS
VC-16
EOC/EDOS
TIE-A
125, 250, 500
bps,
I-channel SN,
TIE Critical Command
Subcarrier
1 kbps, 2 kbps
EPGS and WGS
VC-17
EOC/EDOS
TIE-B
125, 250, 500
bps,
I-channel SN,
TIE Critical Command
Subcarrier
1 kbps, 2 kbps
EPGS and WGS
VC-2
S/C C&DH
EDOS/EOC
1.024 kbps
(realtime)
I-channel and
Selected Housekeeping
Telemetry
Q-channel, SN
VC-2
S/C C&DH
EDOS/EOC
4.096 kbps
(realtime)
I-channel and
Selected Housekeeping
Telemetry
Q-channel, SN
VC-2
S/C C&DH
EDOS/EOC
16.384 kbps
(realtime)
Subcarrier EPGS
and WGS
H/K telemetry
VC -1
S/C C&DH
EDOS/EOC
524.288 kbps
(playback)
Carrier
Stored Engineering or
Processor Data Dump
EPGS and WGS
Table 2010.2 Virtual Channel Identification Assignments (X-Band)
Label
VC-3
Source
EOS S/C
Destination
Data Rate
Channel ID
Purpose
EDOS
Ground Based Attitude
Determination (GBAD)
EDOS
CERES
C&DH
VC-10
EOS S/C
VC-15
C&DH
VC-20
EOS S/C
VC-25
C&DH
VC-30
EOS S/C
Science/eng packets
EDOS
Science/eng packets
EDOS
FMU
VC-35
EOS S/C
EOS S/C
EDOS
EOS S/C
EDOS
EOS S/C
C&DH
MODIS
AIRS
AMSR-E
Science/eng packets
EDOS
C&DH
VC-63
Direct playback
of stored data
Science/eng packets
C&DH
VC-45
150 Mbps
Science/eng packets
FMU
VC-40
AMSU-A
HSB
Science/eng packets
EDOS
Fill CADUs
VC-5
EOS S/C
C&DH
EDOS
Complete S-band GN mode
Spacecraft Bus and Instrument
Housekeeping Telemetry
packets
2020
2020.1
The EGS shall support the X-band and S-band return link
communications as defined in the following document (to be
referred to as the PM Space to Ground ICD):
422-11-19-03, EOS PM-1 Spacecraft to EOS Ground System
Interface Control Document, January 2000.
2030
2030.1
The EGS shall support the S-band forward link communications as
defined in the PM Space to Ground ICD.
2040
2040.1
The Aqua spacecraft will utilize the TDRSS SSA and SMA/MA
services for command and telemetry communications as the prime
service through launch/ascent, activation, and checkout phases.
These services will also be used during the remainder of the
mission to provide routine tracking and backup command and
telemetry support.
The Launch/Ascent phase starts with the spacecraft launch and
end at about 10 hours after the launch. Standard Services for the
Aqua mission requires nearly continuous SN support from launch
through launch plus three hours (L+3 hours). From L+3 hours
through the end of the spacecraft activation phase, ten to fifteen 20minute contacts per day are required. The activation activities are
planned to conclude within two weeks following the launch. A
checkout phase begins at the conclusion of the activation phase
and continues until approximately launch plus 90 days. The Aqua
mission requires ten to fifteen 20-minute contacts each day during
the checkout phase. TDRSS-ZOE (Guam) support is required
during launch/ascent, and activation phases and may be required
during contingency or special operations.
During the on-orbit operational phase of the mission, the Aqua
spacecraft requires routine SN support for tracking data and clock
correlation. Coherent, two way, tracking support is required four to
six times per day with a duration of approximately 10 minutes for
each contact. Clock correlation measurement can be made
coincident with tracking data collection. Aqua support requirements
can be met using SSA service or, in emergency cases, SMA/MA
service. Periodic orbital maneuvers will be required to maintain the
orbit parameters and so five to ten additional contacts will be
requested during the following two orbits.
2050
2050.1
The SN shall conduct tracking measurements of the Aqua
spacecraft as defined in Table 2050.1.
Table 2050.1 SN Tracking Measurements for the Aqua Spacecraft
Phases
Services
(Note 1)
Range
2, 3, 4, 5
Sample Rate
1 sample/
Duration of
Collection
Data Delivery
Media
Destination
entire contact
Near Real-time
Electronic
MMFD
entire contact
Near Real-time
Electronic
MMFD
entire contact
Near Real-time
Electronic
MMFD
10 secs
Two-way
Doppler
2, 3, 4, 5
1 sample/
10 secs
One-way
Return
Doppler
2, 3, 4, 5
1 sample/
10 secs
Note 1: Mission phases are 1= Prelaunch, 2=Launch/ascent, 3=Activation, 4=Checkout ,
5=Operational
2050.2
In all mission phases (except prelaunch), the SN shall support
Doppler and range measurements in two-way Doppler, range, and
one-way Doppler modes.
2050.3
The SN shall support Doppler and ranging measurements in the
coherent mode during all scheduled contacts. This will provide the
ability to support clock correlation and orbit determination.
2050.4
Five to ten scheduled contacts of approximately 10 minutes
duration each shall be supported over the two orbit period following
a maneuver.
2050.5
The SN shall support one-way return Doppler measurement service
once per day for spacecraft local oscillator frequency drift
computation. The frequency of measurement may be reduced to
one pass per week as the mission progresses and the oscillator
drift is characterized.
2050.6
The SN shall support spacecraft on-board clock time correlation
where the PN code epoch is used as a time marker and shall
provide station delay calibration data.
2060
2060.1
The SN shall support the return link services with characteristics
shown in Table 2060.1.
Table 2060.1 SN Return link Characteristics
Data
Group
Phases
Data
Types
Contact/
I- Ch
Q-Ch
(Note
2)
(Note 2)
Coding
VC-2
VC-2
Convolutional
Total
Data Rate
/Mode
Service
(Note 1)
SSA
Return
2
(through
L+3 hrs)
DG1/
Modes 1,
2
Reed-Solomon
(interleave depth of
Power
Ratio
Orbit
(Duration)
4.096/
4.096
kbps
1:1
Continuous
in view
support
1)
SSA
Return
2 (L+3 to
L+10
hrs), 3, 4
DG1/
VC-2
VC-2
Modes 1,
2
Convolutional
Reed-Solomon
4.096/
4.096
kbps
1:1
Ten to
fifteen 20minute
contacts per
day
4.096/
4.096
kbps
1:1
Four to six
10-minute
contacts per
day
1.024/
1.024
kbps
1:1
Contingency
only
1.024/
1.024
kbps
1:1
Contingency
only
1.024/
1.024
kbps
1:1
Contingency
only
(interleave depth of
1)
SSA
Return
5
DG1/
VC-2
VC-2
Modes 1,
2
Convolutional
Reed-Solomon
(interleave depth of
1)
SSA
Return
2, 3, 4, 5
DG1/
VC-2
VC-2
Modes 1,
2
Convolutional
Reed-Solomon
(interleave depth of
1)
MA
Return
2, 3, 4, 5
DG1/
VC-2
VC-2
Modes 1,
2
Convolutional
Reed-Solomon
(interleave depth of
1)
SMA
Return
(TDRSHJ only)
2, 3, 4, 5
DG1/
VC-2
Modes 1,
2
VC-2
Convolutional
Reed-Solomon
(interleave depth of
1)
Note 1: Mission phases are 1= Prelaunch, 2=Launch/Ascent , 3=Activation,
4=Checkout, 5=Operational
Note 2: Identical data on I and Q channels
2060.2
Maximum available SA return link service is required (during line of
sight) from separation to approximately L+3 hours.
2060.3
From L+3 hours through activation phase, ten to fifteen 20-minute
SSA contacts per day are required for real-time telemetry downlink.
2060.4
During the checkout phase, ten to fifteen 20-minute contacts are
required each 24-hour period for real-time telemetry downlink.
2060.5
During all mission phases (except prelaunch), contingency
telemetry support shall be provided through SSA and SMA/MA as
available.
2060.5.1
Contingency telemetry support shall be provided within 30 minutes
of a request for support.
2060.6 (Deleted)
2060.7
During the operational phase (phase 5), the SN shall support an
average of four to six 10-minute contacts per day for tracking and
clock correlation support.
2060.8
The SN shall support the transfer of Aqua high rate data from the
MGS to the WSC at 150 Mbps. MGS will provide contingency Xband support to augment the AGS and SGS sites. The SN shall
provide the mechanism for subsequently transferring this data to
the EDOS GSIF at WSC. Support will be required as needed, given
limitations imposed by TDRS and McMurdo TDRSS Relay System
(MTRS) visibility and availability.
2060.9
Given the limitations noted in 2060.8, the SN shall provide a 150
Mbps TDRS link from MGS to WSC within 12 hours of the end of
the Aqua X-band dump to MGS, with the goal being to begin the
transfer within 3 hours.
2060.10
The SN shall support the use of the "911 service" by the spacecraft,
in which the spacecraft can automatically initiate an S-band
telemetry transfer via the MA or SMA service. This would be used if
the spacecraft detected a problem that might require prompt
attention from the flight operations team.
2070
2070.1
The SN shall support the forward link service characteristics shown
in Table 2070.1.
Table 2070.1. SN Forward Link Characteristics
Service
Phases
Data Types
Total Data
Rate
(Note 1)
SSA Forward
2 (through L+3
hrs)
Contact/Orbit
(Duration)
VC-0,
1kbps
VC-1, VC-16,
(Note 2)
Continuous in view support
VC-17
SSA Forward
2 (L+3 to L+10
hrs), 3, 4
VC-0,
1kbps
VC-1, VC-16,
(Note 2)
Ten to fifteen 20-minute
contacts per day
VC-17
SSA Forward
5
VC-0,
1kbps
VC-1, VC-16,
(Note 2)
Four to six 10-minute
contacts per day
VC-17
SSA Forward
2, 3, 4, 5
VC-0,
500bps
Contingency only
250bps
Contingency only
VC-1, VC-16,
VC-17
SSA Forward
2, 3, 4, 5
VC-0,
VC-1, VC-16,
VC-17
SSA Forward
2, 3, 4, 5
VC-0,
125bps
Contingency only
VC-0,
125bps
Contingency only
VC-1, VC-16,
(Note 2)
VC-1, VC-16,
VC-17
MA Forward
2, 3, 4, 5
VC-17
SMA Forward
(TDRS H-J only)
2, 3, 4, 5
VC-0,
125bps
VC-1, VC-16,
(Note 2)
Contingency only
VC-17
SMA Forward
(TDRS H-J only)
2, 3, 4, 5
VC-0,
250bps
Contingency only
VC-1, VC-16,
VC-17
Note 1: Mission phases are 1= Prelaunch, 2=Launch/ascent, 3=Activation,
4=Checkout , 5=Operational
Note 2: Prime operating command data rates
2070.2
Maximum available SA forward link service is required (during line
of sight) from separation to approximately L+3 hours.
2070.3
From L+3 hours through Checkout phase, ten to fifteen 20 minute
SSA contacts are required per day for spacecraft commanding.
2070.4
During all mission phases (except prelaunch), contingency
commanding support shall be provided through SSA and SMA/MA
as available.
2070.4.1
Contingency commanding support shall be provided within 30 min.
of a request for support.
2070.5 (Deleted)
2080
2080.1
The NCC shall be capable of exchanging Schedule Coordination
Messages (Type 99) with the EOC.
2080.1.1
The NCC shall send a Schedule Deletion Notification (SDN)
message (Class 01) to notify the EOC of deletion of a previously
scheduled event.
2080.1.2
The NCC shall send Schedule Result Message (SRM) (Class 02) to
the EOC in response to a Schedule Add Request (SAR) or
Schedule Delete Request (SDR).
2080.1.3
The NCC shall be able to accept TDRSS SARs (Class 10) from the
EOC and schedule the requested services based on priority and
available resources.
2080.1.4
The NCC shall be able to accept SDR message (Class 11) from the
EOC to delete a scheduled event for the PM/Aqua spacecraft.
2080.1.5
The NCC shall be able to accept Schedule Result Request (SRR)
messages (Class 28) when EOC establishes a connection to the
Schedule Status service.
2080.2
The NCC shall provide the EOC with User Schedule Messages
(USMs) (Type 94).
2080.2.1
The NCC shall provide the EOC with USM (Class 01) which defines
the scheduled service and parameter values for one Normal
Support, Fixed Schedule SN Event.
2080.2.2
The NCC shall provide the EOC with USM (Class 02) which defines
the scheduled service and parameter values for one Premium
Support, Fixed Schedule SN Event that is in response to a SAR
received less than 45 minutes prior to the requested start time.
2080.2.3
The NCC shall provide the EOC with USM (Class 03) which defines
the scheduled service and parameter values for one Normal
Support, Fixed Schedule SN simulation event.
2080.3
The NCC shall have the capability to accept and process Ground
Control Message Request (GCMR) sent by the EOC (Type 98).
2080.3.1
The NCC shall have the capability to accept from the EOC requests
for a service compatible link reacquisition by utilizing a User
Reacquisition Request Message (Class 03).
2080.3.2
The NCC shall have the capability to accept from the EOC requests
for a forward link sweep on the designated forward service by
utilizing a Forward Link Sweep Request Message (Class 05).
2080.3.3
The NCC shall have the capability to accept from the EOC requests
for the SN Ground Terminal to reconfigure the SSA or KSA forward
link EIRP between normal and high power modes by utilizing a
Forward Link EIRP Reconfiguration Request Message (Class 06).
2080.3.4
The NCC shall have the capability to accept from the EOC requests
for expanding the frequency uncertainty of a scheduled return
service by utilizing an Expanded User Frequency Uncertainty
Request Message (Class 07).
2080.3.5
The NCC shall have the capability to accept from the EOC requests
for reconfiguration for six types of customer support links – forward
or return links on MA, SMA, SSA1, SSA2, KSA1, and KSA2
Services, by utilizing a User Reconfiguration Request Message
(Class 04).
2080.3.6
The NCC shall have the capability to accept from the EOC requests
for inhibiting forward link Doppler compensation on the specified
link by utilizing a Doppler Compensation Inhibit Request Message
(Class 08).
2080.4
The NCC shall provide the EOC with Ground Control Messages
(GCMs) (Type 98).
2080.4.1
The NCC shall be capable of transmitting a GCM Status Message
(Class 01) on receipt of an invalid GCMR from the EOC, on receipt
of an Operations Message (OPM) status message from the SN
Ground Terminal, or upon failure to receive an OPM status
message within 20 seconds after receipt of the SN Ground
Terminal’s acknowledgment of the service reconfiguration OPM.
2080.4.2
The NCC shall be capable of transmitting a GCM Disposition
Message (Class 02) to the EOC to indicate whether an
acknowledgement was received from the Space Network Ground
Terminal for service reconfiguration OPM.
2080.5
The NCC shall be capable of exchanging Performance Data
Messages (Type 92) with the EOC.
2080.5.1
The NCC shall have the capability to accept and process EOC
requests for User Performance Data Request (UPDR) Message
(Class 04) from the EOC to enable or disable the transmission of
User Performance Data messages.
2080.5.2
The NCC shall be capable of relaying from the SN Ground Terminal
and transmitting return channel time delay measurements by
utilizing a Return Channel Time Delay Measurement message
(Class 62).
2080.5.3
The NCC shall be capable of relaying from the SN Ground Terminal
to the EOC when an attempt to provide a scheduled return service
does not occur due to the inability of the SN to acquire the
PM/Aqua PM spacecraft by utilizing an Acquisition Failure
Notification message (Class 63).
2080.5.4
The NCC shall be capable of relaying to the EOC time transfer data
measurements taken by the SN Ground Terminal utilizing the Time
Transfer Message (Class 66).
2080.6
The NCC shall be capable of exchanging the following User
Monitor Messages (Type 91) with the EOC.
2080.6.1
The NCC shall be capable of exchanging Communication Test
Message (CTM) (Class 03) with the EOC to ascertain the existence
of an operational communications link between the EOC and the
NCC.
2080.6.2
The NCC shall be capable of transmitting User Performance Data
(UPD) Messages (Class 01) to the EOC in response to a UPDR
Message received from the EOC.
2080.7
The NCC shall provide the EOC via a Network Advisory Message
(NAM) with notification of changes in status to the Space/Ground
Network.
2080.8
The NCC shall have the capability for its operations personnel to
communicate, via voice, with the operations personnel at the EOC
facility.
2080.9
The NCC shall be capable of accepting PM/Aqua acquisition data
from the FDS via Improved Inter-range Vector Message (Message
Type 3, Class 10 or Class 15).
2080.10
The TDRSS Ground Terminal (TGT) shall provide an interface to
the Earth Observing System (EOS) Data and Operations System
(EDOS) as described in the Interface Control Document (ICD)
between the EDOS and the TGT.
2100
2100.1
The EPGS (AGS and SGS) shall provide primary S-band realtime
telemetry, tracking, command and X-band science data capture
and relay support for the life of the Aqua mission. The EPGS
(MGS) shall provide contingency S-band telemetry and command
and X-band support as needed. WGS shall provide contingency SBand support for the relay of command, tracking, and real-time
telemetry data only.
EPGS and WGS shall provide command, and telemetry support as
summarized in Table 2010.1, using frequencies as defined in Table
1200.1. Specific requirements are stated in sections 2110-2140.
Further information concerning the RF interface between EPGS
and WGS and the Aqua spacecraft can be found in the Radio
Frequency Interface Control Document Between the EOS Aqua
Spacecraft and the EOS Polar Ground Station (EPGS) and the
Wallops Orbital Tracking Station (WPS), 450-RFICD-EOS Aqua1/EPGS/WPS, March 1999.
2100.2
The WOTIS shall schedule Aqua passes for the EPGN stations at
AGS, MGS, SGS and WGS to support Aqua tracking, commanding
and data acquisition. Scheduling shall include coordination with
other spacecraft using the same stations.
2100.2.1
The WOTIS shall provide an interface with the EOC for planning
and scheduling station passes.
2100.2.2
The WOTIS shall send pass schedules to the EPGS and WGS
defining Aqua required support.
2100.3
The WOTIS shall receive station acquisition data from FD and
forward this data to the EPGS and WGS.
2100.4
The WOTIS shall accept post-pass reports from the EPGS and
WGS.
2100.5
During the Launch/Ascent Phase (Launch to approximately Launch
+ 10 hours) the EPGS (AGS, SGS, MGS) and WGS shall provide
hot back ups to the Space Network for S-band command, telemetry
and tracking.
2100.6
The EPGS (AGS, SGS, MGS) and WGS shall provide status data
to the EOC during spacecraft contacts that describes the status of
the link with the spacecraft.
2100.7
The EPGS (AGS, SGS, MGS) shall be capable of receiving and
delivering no less than 99% of all science data to its NISN/EMSn
interface during each orbit repeat cycle.
2110
2110.1
The EPGS (except MGS) shall provide tracking measurements of
the Aqua spacecraft to the MMFD as defined in Table 2110.1.
Table 2110.1 Metric Tracking Requirements
Phases
Services
(Note 1)
One-way
Doppler
2, 3, 4
Sample
Rate
1 sample/
Frequency of
Collection
Duration of
Collection
Data
Delivery
Media
Destination
Once per orbit*
5 minutes/ pass
FTP, PostPass
Electronic
MMFD
Once per orbit*
5 minutes/ pass
FTP, PostPass
Electronic
MMFD
10 secs
Two-way
Doppler
2, 3, 4
1 sample/
10 secs
Note 1: Mission phases are 2=Launch/ascent, 3=Activation, 4=Checkout
, 5=Operational
Note 2: * EPGS requirement,
2110.2
The EPGS (except MGS) shall provide tracking services using twoway Doppler in a coherent mode. The downlink carrier frequency
will be 240/221 times the uplink frequency.
2110.3
The EPGS (except MGS) shall also have the capability to provide
tracking services using one-way Doppler in a noncoherent mode.
The carrier frequency will be 2287.5 MHz +/-0.002%. The Doppler
data will be used to characterize spacecraft transmitter frequency
drift.
2110.4
The EPGS (except MGS) shall perform one tracking pass per orbit
for the Aqua spacecraft.
2120
2120.1
The EPGS (AGS, SGS and MGS) and WGS shall receive
data as with the characteristics defined in Table 2120.1 and
further defined in paragraphs 2120.2 through 2120.12.
Note: The EPGS and WGS do not support the X-band Direct
Broadcast mode (Mode 4).
Table 2120.1 Aqua Downlink Characteristics
Phases
Modulation
Type
VCID
Contact
(Duration)
Contacts per
Day
Mode
(note 1)
Data Type
1
1, 2, 3, 4,
5
S-band R/T
Telemetry
PSK on
Subcarrier
VC-2
16.384 kbps
Entire Pass
As
Scheduled
2
1, 2, 3, 4,
5
S-Band
Telemetry
Playback
PM Direct
on Carrier
VC-1
524.288 kbps
Entire Pass
As
Scheduled
3
1, 2, 3, 4,
5
X-band Science
Playback *
SQPSK
VC-3, 5,
10, 15,
20, 25,
30, 35,
40, 45
75/75Mbps
Middle of
Pass
As
Scheduled
Outside of
Pass#
Continuous
(except for
pass)
4
1, 2, 3, 4,
5
X-band Direct
Broadcast
Data Rate
SQPSK
VC-3, 5,
10, 15,
20, 25,
30, 35,
40, 45
(150 Mbps
total on I &
Q channels)
7.5/7.5Mbps
(15 Mbps
total on I &
Q channels)
Note 1: Mission phases are 1= Prelaunch, 2=Launch/ascent,
3=Activation, 4=Checkout, 5=Operational
Note 2: * X-band passes are supported by EPGS ground stations only
(they are not supported at WGS)
# "Outside of Pass" corresponds to the orbit portion over which no
spacecraft to EPGS/WGS contact is made.
2120.2
The carrier frequency for modes 1 and 2 will be 2287.5 MHz
± 0.002 when the spacecraft is operating in the non-coherent
mode and 240/221 times the uplink frequency when the
spacecraft is operating in the coherent mode.
2120.3
The subcarrier frequency for mode 1 will be 1.024 MHz ± 0.0031%.
2120.4
The peak carrier phase modulation of the carrier by the
subcarrier for mode 1 will be 0.4 radians ± 5% (sinusoid).
The peak carrier modulation of the carrier by the baseband
high rate data is 1.1 radians (± 5%).
2120.5
The 16.384 kbps and 524.288 kbps data biphase modulate
the subcarrier and carrier respectively.
2120.6
The carrier frequency for modes 3 will be 8.160 GHz ± 0.15MHz.
2120.7
EPGS and WGS shall decode the convolution code for
telemetry data in modes 1 and 2.
2120.8
The modulation in modes 3 will be NRZ-M Staggered
Quadrature Phase Shift Key (SQPSK) where the data are in
a single stream with bits alternating on the quadrature I and
Q carriers.
2120.9
The WGS shall have the capability to receive modes 1 and 2 data.
2120.10
The EPGS (AGS and SGS) shall pass X-band data to the
local EDOS GSIF.
2120.11
The EPGS (MGS) shall record X-band data for subsequent transfer through the
SN.
2120.12
The EPGS (AGS, SGS and MGS) and WGS shall provide Sband data to the EDOS LZPF as it is being received from the
spacecraft.
2130
2130.1
The EPGS (AGS, SGS and MGS) and WGS shall transmit
command data as defined in Table 2130.1 and further defined in
paragraphs 2130.2 through 2130.9.
Table 2130.1. Aqua Uplink Characteristics
Phase
Mode
1
Data Type
(Note 1)
1, 2, 3,
4, 5
Modulation
Data Type
Data
Rate
Type
Commands
Subcarrier
VC-0
(PSK/PM)
VC-1
2 kbps
Contact
Contactsper
(Duration)
Orbit/Day
Entire Pass
As Scheduled
VC-16
VC-17
Note 1: Mission phases are 1= Prelaunch, 2=Launch/ascent, 3=Activation, 4=Checkout,
5=Operational
2130.2
The nominal carrier frequency shall be 2106.40625 MHz plus
Doppler Shift.
2130.3
The subcarrier frequency shall be 16 kHz ± .001%
2130.4
The command data bit format shall be NRZ-L.
2130.5
The command data modulation of the subcarrier shall be Phase
Shift Key (PSK).
2130.6
The command data modulation of the subcarrier shall be ± p /2
radian modulation.
2130.7
The subcarrier modulation of the uplink carrier shall be Phase
Modulation (PM).
2130.8
The peak carrier phase modulation shall be 0.7±10%(radians).
2130.9
The EPGS (AGS, SGS and MGS) and WGS shall provide the
capability to receive command data from the EDOS LZPF and
forward it to the spacecraft.
3000
3000.1
To ensure that all the EOS ground facilities, the spacecraft, and the
EOSDIS Ground System (EGS) operations personnel are fully
capable of performing the Aqua mission, a series of simulations,
ground system integration tests, and spacecraft tests will be
performed. Tests will be performed with the spacecraft to ensure
compatibility and inter-operability of the EOS elements and the
spacecraft as well as spacecraft to SN interfaces.
3000.2
The EGS shall support Mission Readiness Tests (MRTs) to verify
that both bulk mission data and control message data can be
successfully transferred between EGS elements and both
Institutional elements and External elements over institutional
circuits.
3000.3
The EGS shall support the Spacecraft Interface (SCIF) Tests and
Mission Tests (MTs) with the Aqua observatory (spacecraft and
instruments).
3000.4
The EGS shall support EGS Mission Readiness Tests (MRTs) to
verify that the end-to-end tracking and data acquisition systems are
fully capable of mission support.
3000.5 (Deleted)
3000.6
The EGS shall generate a Mission Readiness Test Plan that
describes the ground system integration tests among the EOS
unique and NASA institutional elements.
3100
3100.1
The NASA Institutional elements described in section 1130.2 (SN,
NISN and FD) shall support interface tests to verify that both bulk
mission data and control message data can be successfully
transferred between EGS elements and institutional elements, and
EGS elements and external elements over institutional circuits.
Interface tests verify the proper implementation of the
communications protocol at the higher levels under both nominal
and anomalous conditions. Proper formatting of protocol data units
at the application level and any lower levels where custom formats
are employed is also verified.
3200
3200.1
The NASA Institutional elements shall support EGS I&T and Aqua
joint system tests, such as the Aqua Spacecraft Interface Tests and
Mission Readiness Tests. These tests are performed to ensure that
major tracking and data acquisition systems are fully capable of
mission support.
3200.2
The NASA Institutional elements shall support the Mission
Readiness Tests to check out the RF interfaces of the Aqua
spacecraft telecommunications systems with the tracking networks
(SN and EPGN).
3200.3
The NASA Institutional elements shall support the Mission
Readiness Tests to verify the ability of the EOC to generate
commands and process telemetry for the Aqua spacecraft.
3200.4
The EGS shall support the Mission Readiness Tests to verify that
all S and X-band data formats are compatible with the EPGN and
SN sites.
3300
3300.1
The NASA Institutional elements shall support EGS Integration
Tests (normally known as Network Readiness Testing) to verify that
the end-to-end tracking and data acquisition, and command
transmission systems are fully capable of mission support. EGS
Integration Tests will include:
1) Functional Threads
2) Performance and Stress Tests
3300.1.1
The NASA Institutional elements shall support the Functional
Thread Testing to demonstrate the ability of the integrated EGS
system to perform all functions necessary to control and process
data from the Aqua Spacecraft. Functional Thread tests verify the
correct implementation of functionality distributed between two or
more EGS elements in concert with needed institutional elements.
3300.1.2
The NASA Institutional elements shall support the Performance and
Stress Test to verify performance requirements, characterize
system response to overload and stress conditions, and provide
"End to End" operational tests, including "Day in the Life" tests that
exercise an average day’s work over a nominal timeline. The Endto-End or daily operations tests build upon previous functional
thread testing, exercising multiple threads simultaneously.
3300.2
The NASA Institutional elements shall support mission readiness
testing of the integrated network elements. This shall be
accomplished through testing, simulations, and participation in
mission end-to-end readiness testing. Tracking & Data Acquisition
(T&DA) support capabilities shall be verified in accordance with test
and simulation plans which meet the requirements defined by the
EGS Integration and Test Manager.
3300.3
Scheduling and execution of tests shall be accomplished via
established network scheduling interfaces and processes.
3400
3400.1
For compatibility testing, the Compatibility Test Van (CTV), Simulations
Operations Center (SOC), and Radio Frequency SOC (RFSOC) facilities shall be
required to provide test tools necessary for system verification and validation.
The RFSOC shall provide a direct TDRSS link for SN testing and simulator
training. CTV use is not expected to exceed 2 weeks.
The Aqua mission plan requires the use of the CTV for a minimum of two trips,
supporting three sequential events, prior to launch. The events will occur at TRW
Inc., Redondo Beach, CA.
A Space Network to Aqua spacecraft communication capability is required for
pre-launch testing at the spacecraft contractor’s facility, TRW Space Park,
Redondo Beach, CA. An S-band, roof-top antenna/amplifier system is required to
be installed at the contractor’s facility.
4000
4000.1
The Earth Observing System (EOS) Operations Center
(EOC) shall support the conduct of prelaunch through onorbit operations around the clock seven days a week through
the end of the mission.
4000.2
The EOC shall maintain the following external interfaces and
perform the following functions:
a. EDOS: Receive real-time housekeeping telemetry and ratebuffered datasets (playback housekeeping telemetry, GBAD data
and AIRS data). Send EPGS schedules and spacecraft commands.
Note: The format of schedule messages sent to EDOS are
specified in the EDOS/EGS ICD.
b. EPGN (AGS, SGS, MGS, WGS, WOTIS): Receive station status data (real-time
status and post-pass report) from EPGS and WGS. Coordinate S and X-band
communications support via WOTIS. Send commands via EDOS. Exchange
EPGS and WGS scheduling information with WOTIS.
c. SN (TDRSS, NCC): Receive ground telemetry messages (e.g., UPDs, TTMs),
SN contact schedules from NCC. Send commands via EDOS, send GCMRs and
scheduling requests to NCC.
d. FDS: Receive planning information, command data, and orbit data for mission
planning and scheduling. Send required housekeeping and GBAD telemetry
parameters.
e. Aqua SCITF at TRW (Redondo Beach, CA): Receive telemetry. Send
commands.
f. VAFB Launch Facility: Receive telemetry. Send commands.
g. FMT (IVVF): Send memory dumps. Receive flight software loads.
h. ETS: Send commands. Receive simulated telemetry packets via telemetry
EDU's. Receive CLCW EDU's.
i. ETSF: Send commands either directly or via EDOS. Receive simulated telemetry
packets via telemetry EDU's (either directly or via EDOS). Receive CLCW EDU's.
j. GSFC DAAC: Send history data, carryout files, and schedule data. Receive
history data.
k. LaRC DAAC: Send attitude carryout files and schedule data.
4000.3
The EOC shall include electronic mail to facilitate
communications among the FOT and the Aqua instrument
Operations Teams (IOTs).
4000.4
The EOC shall provide selected S-Band telemetry, as
defined in the Aqua FDS/EMOS ICD, to the Flight Dynamics
System within 2.5 hours after receipt of real time or playback
S-Band telemetry from the ground station.
4000.5
The EOC shall provide the ability to manage the SSR.
4100
4100.1
The EOC shall provide the mission operations functions of
planning, scheduling, commanding, flight operations
management, observatory health and safety maintenance,
ground software maintenance, telemetry receipt and
processing, engineering data analysis, and flight operations
history archiving.
4100.2
The EOC shall have an uptime availability for real-time
operations of 0.9998 or higher.
4100.3
The EOC shall have no single point of failure for functions
associated with observatory real-time operations.
4100.4
The EOC shall have a mean down time of one minute or less
for real-time operations.
4100.5
The EOC shall provide support for the Aqua planned mission
life of six years plus a possible two year extension of the
mission.
4100.6
The EOC shall provide the capability to support concurrently
- operations, simulations, and test exercises.
4100.7
The EOC shall install HSB IST software for Brazil and
AMSR-E IST software for Japan.
4100.8
The EOC shall install IST software and hardware for the JPL
AIRS, AMSU and HSB IOT, GSFC MODIS IOT, and LARC
CERES IOT.
4110
4110.1
The EOC shall provide mission planning, for launch through
post-separation autonomous observatory activities, including
end-of-mission tests and evaluation.
4110.2
The EOC shall plan S-Band communication services for SN and EPGN.
4110.2.1
The EOC shall plan SN services through the NCC, to include
SSA, MA and SMA services for all active TDRS spacecraft.
This thus includes planning SMA service with the TDRS H-J
spacecraft.
4110.2.2
The EOC shall plan EPGS and WGS S-Band services through WOTIS.
4110.3
The EOC shall plan X-Band communications from the
observatory to the AGS, SGS and MGS direct playback
sites.
4110.3.1
The EOC shall plan AGS, SGS and MGS X-Band services through the WOTIS.
4110.4
The EOC shall plan instrument activities in accordance with IOT requests.
4110.5
The EOC shall provide the capability to incorporate
calibration and observatory maintenance requests into the
mission plan.
4110.6
The EOC shall provide the capability to plan the recording
and playback of the onboard SSR (both S-Band and XBand) storage device.
4110.7
The EOC shall identify mission planning conflicts.
4110.8
The EOC shall provide the capability to include an IOT
request for update in the planning and scheduling cycle
within 24 hours after receipt.
4110.9
The EOC shall provide planning products to IOT's.
4110.10
The EOC shall accept operational timeline planning activities from IOTs.
4110. 11
The EOC shall accept predicted and definitive ephemeris
reports from FDS and send them to the ISTs.
4120
4120.1
The EOC shall generate a daily, 24-hour, conflict-free
schedule for the Aqua
spacecraft and its payloads.
4120.1.1
The EOC shall be capable of scheduling activities based on
events, such as spacecraft contacts and orbital events, or
via absolute start/stop times.
4120.1.2
The EOC shall use the FDS planning and scheduling aids in
observatory scheduling.
4120.1.3
The EOC shall ingest confirmed contact schedules for the
SN, EPGS and WGS and use them as inputs to the
scheduling process.
4120.1.4
The EOC shall identify mission-scheduling conflicts for operator resolution.
4120.2
The EOC shall provide the capability to schedule the S-Band
and X-Band recording, playback, and maintenance of the
onboard SSR storage device.
4120.2.1
The EOC shall schedule (via WOTIS) X-Band SSR playback
to the EPGS
using X-band down link channels.
4120.2.2
The EOC shall use the EPGS contact times to schedule the
playback of the X-Band SSR dumps.
4120.3
The EOC shall schedule X-Band down link communications
from the observatory to the EPGS.
4120.4
The EOC shall generate the daily schedule within one 8 hour
shift per day, 7 days per week.
4120.5
The EOC shall distribute the detailed activity schedule to the
Instrument Operations Teams (IOT's) via the IST and directly
to the GSFC DAAC.
4120.6
The EOC shall be capable of scheduling long-range
activities (e.g. proposed orbital maneuvers or instrument
calibrations) which extend up to 4 weeks into the future.
4120.7
The EOC shall be capable of scheduling Aqua resources,
updating the daily schedule as required, and preparing
stored command loads.
4120.8
The EOC shall be capable of scheduling Aqua
communication and data capture resources, and
commanding the observatory in real-time, within 45 minutes
of receipt of manual input, provided the necessary
communications resources are available.
4120.9
The EOC shall be capable of scheduling S-band
communication services for SN and EPGN support as
needed via the NCC and WOTIS. Planning with each of the
interfaces will be consistent with that interface’s planning
cycle.
4120.9.1
The EOC shall schedule SN services through the NCC, to
include SSA, MA and SMA services for all active TDRS
spacecraft. This thus includes scheduling SMA service with
the TDRS H-J spacecraft.
4120.9.2
The EOC shall schedule EPGS and WGS S-band services
through WOTIS.
4120.9.3
The EOC shall be capable of requesting SN, WGS and
EPGS S-Band command and telemetry service as a
contingency service.
4120.10
The EOC shall provide a color display and interface to the
mission scheduling capabilities. The displays should be
graphics-oriented where possible.
4120.10.1
The EOC shall provide the capability to generate hard copies
of any displays, as requested by the user.
4120.10.2
The EOC shall provide the capability to display the current mission timeline.
4120.10.3
The EOC shall display a user-modifiable list of events on the
mission timeline. Possible events include each scheduled
R/T contact (AOS, LOS, station or satellite identifier), events
contained within an accepted command load, orbital events
from defined FDS files, and user-specified comments.
4120.11
The EOC shall be capable of calculating the CERES scan
time-out parameter for inclusion in the command load.
4120.12
The EOC shall be capable of scheduling the CERES sun
avoidance commands for inclusion in the command load.
4130
4130.1 (Deleted)
4130.2
The EOC shall provide command and control of the
observatory commencing with the initial communications
contact after fairing separation.
4130.3
The EOC shall provide the capability to generate
observatory commands in accordance with the Aqua
Spacecraft to Ground ICD and based on the Project
Database.
4130.3.1 (Deleted)
4130.3.2 (Deleted)
4130.3.3 (Deleted)
4130.4
The EOC shall generate, constraint-check, validate, and
uplink stored command loads.
4130.4.1
The EOC shall perform activity and command level constraint checking.
4130.4.2
The EOC shall provide the capability to generate Stored
Command Sequences (SCS) and Predefined Command
Scripts (PCS).
4130.4.3
The EOC shall maintain continuity from one command load to the next.
4130.4.4
The EOC shall forward commands, via EDOS, to the SN,
EPGS and WGS for uplink to the observatory.
4130.4.5
The EOC shall provide automated and manual
retransmission capability for uplink-failed command
operations.
4130.5
The EOC shall verify receipt of all uplink commands to the observatory.
4130.5.1
The EOC shall provide checksum values (as required by the
processor) for spacecraft command and memory loads that
are built by the EOC (vs. provided by exterrnal sources).
4130.6
The EOC shall provide the capability to verify that all uplinks
to the observatory have been properly stored onboard.
4130.7
The EOC shall provide the capability for the FOT to verify
the execution of all commands sent in real-time.
4130.8
The EOC shall maintain an image of the current spacecraft
packet lists & telemetry format tables.
4130.9
The EOC shall have the capability to command memory
dumps for all reprogrammable spacecraft computers and
EEPROM's as required, and perform a memory verification
with static memory contents.
4130.10
The EOC shall request and require operator confirmation
before uplinking any commands that are specified as critical
in the Project Data Base.
4130.11
The EOC shall provide command history archive for
recording and display of operator inputs and command
operations.
4130.12
The EOC shall build and transmit commands within 3
seconds of operator request.
4130.13
The EOC shall provide real-time event message display
information within 2 seconds of occurrence.
4130.14
The EOC shall have the capability to process 1000 bytes of
real time memory dump and provide a load image
comparison report within 30 seconds of an operator initiated
request, following the receipt of the complete dump.
4130.15
The EOC shall generate spacecraft and instrument stored
command loads covering up to 24 hours of observatory
operation.
4130.16
The EOC shall provide the capability to update the
spacecraft ephemeris as required to maintain on-orbit
requirements.
4130.17
The EOC shall have the capability to display, for operator
review, all commands prior to execution.
4130.18
The EOC shall provide the capability to uplink flight software
memory loads provided by the FMT (IVVF) or the spacecraft
contractor SDVF.
4130.18.1
The EOC shall provide the capability to generate a load
report that specifies items such as the absolute address of
the load start, the number of words and the destination
controller.
4130.19
The EOC shall partition instrument microprocessor loads into
user specified partition sizes prior to uplink.
4130.20
The EOC shall meter out real-time telecommand packets to
meet command timing constraints.
4130.21
The EOC shall provide the capability to develop, validate
and constraint-check the Stored Command Sequences
(SCS's) and Pre-Defined Command Scripts (PCS's) for each
controller.
4130.21.1
The EOC shall have the capability to view the SCS's and
PCS's that are currently on-board.
4130.21.2
The EOC shall have the capability to view the Fault
Management SCS's, received from the FMT (IVVF).
4130.21.3
The EOC shall have the capability to view the allocation of
the number and size of the SCS's in each controller.
4130.22
The EOC shall provide the capability to manage SCS's in all active controllers.
4130.23
The EOC shall have the capability to generate memory loads
based on virtual tables (which allows loading selected values
to the spacecraft memory locations). Virtual tables will allow
for spacecraft data to be defined as a table of data (e.g.
spacecraft ephemeris, TMON tables, ACS parameters).
4140
4140.1
The EOC shall provide the capability to maintain the GIIS
and GIRD onboard clocks within ± 10 msec of UTC.
4140.1.1
The EOC shall be able to calculate onboard clock error and
correlation parameters.
4140.2
The EOC shall maintain a ground reference image of all
memory in each controller.
4140.2.1
The EOC shall provide the capability to dump and compare memory images.
4140.3
During each communications contact, the EOC shall receive
EPGS status data from the supporting station.
4140.4
The EOC shall provide the capability for the FOT to maintain
a Project Database (PDB) to include viewing, editing,
validating, archiving and restoring the PDB.
4140.4.1
The EOC shall provide for transfer and ingest of the Aqua
Program Master Data Base (PMDB) from the spacecraft
builder to the EOC.
4140.4.2
The EOC shall be capable of generating a PDB from the
PMDB supplied by the spacecraft builder and additional FOT
and instrument team-provided inputs.
4140.4.3
The EOC shall provide the capability to generate PDB
reports that describe the content of the PDB.
4140.5
The EOC shall provide the ability to display the current
version of the Control Center software and associated
operational database.
4150
4150.1
The EOC shall be capable of processing all observatory realtime and playback S-Band telemetry produced by Aqua.
4150.2
The EOC shall detect, display, and log observatory telemetry
out-of-limit conditions, which are defined in the project
database and are detected from the processing of real-time
S-Band telemetry.
4150.3
The EOC shall provide displays, plots, and hardcopy of
observatory housekeeping telemetry.
4150.4
The EOC shall provide special displays and print support for
observatory table and memory dump data.
4150.5
The EOC shall provide the capability to identify the current
state and operational mode of the spacecraft and
instruments.
4150.6
The EOC shall provide the capability for the FOT to monitor
command activities from any EOC work station.
4150.7
The EOC shall support the use of a "911 mode" by the
spacecraft in the back-orbit in which the spacecraft
automatically initiates an S-band housekeeping telemetry
flow via the SN. The EOC must thus be ready to receive,
process and display real-time telemetry data between
scheduled contacts. The spacecraft would use this capability
when certain anomaly conditions are automatically detected
onboard in the back-orbit.
4160
4160.1
The EOC shall provide the ability to receive spacecraft
recorder housekeeping data from EDOS and extract CCSDS
packets from the VCDU's.
4160.2
The EOC shall provide the capability to extract telemetry
parameters from CCSDS packets.
4160.2.1
The EOC shall calibrate and convert individual telemetry
parameters, which includes state conversions, conversions
to engineering units, and various raw value display options.
4160.2.2
The EOC shall perform parameter-level limit checking.
4160.2.3
The EOC shall provide the capability to receive, collect and
process observatory memory dumps.
4160.2.3.1
The EOC shall provide the capability to receive spacecraft
memory dumps from each of the flight processors.
4160.2.3.2
The EOC shall be capable of receiving and processing
multiple flight processor dumps concurrently.
4160.2.3.3
The EOC shall be capable of receiving non-contiguous data
from flight processor dumps that are initiated via a single
format table.
4160.2.3.4
The EOC shall provide the capability to receive and collect
instrument microprocessor dumps, to build a corresponding
dump image, and to make the dump image available to the
IOT.
4160.2.4
The EOC shall provide offline processing capabilities for
real-time and playback
telemetry.
4160.3
The EOC shall provide remote Instrument Operations Teams
(IOT's) with real-time display and off-line analysis capabilities
for all S-band housekeeping telemetry.
4160.4
The EOC shall capture and store real-time and playback housekeeping telemetry
4160.5
The EOC shall be capable of defining algorithms to be used
for generating derived parameters.
4160.6
The EOC shall be capable of processing and displaying
derived telemetry parameters (pseudotelemetry).
4160.7
The EOC shall be capable of processing spacecraft and
instrument context dependent telemetry, where the context
switch is located within the same packet as the telemetry
parameter.
4160.8
The EOC shall be capable of performing engineering unit
conversions on telemetered parameters using PDB-defined
polynomial equations.
4160.9
The EOC shall be capable of recognizing data dropout and
missing packets, and marking appropriate telemetry
parameters as static.
4160.10
The EOC shall receive and process GBAD data, with
processing capabilities being comparable to those provided
for housekeeping data. GBAD data will be provided only as
SSR playback data (i.e. not real-time).
4160.11
The EOC shall be capable of processing AIRS low and high
rate flexible engineering telemetry packets.
4160.11.1
The EOC shall be capable of processing AIRS supercommutated telemetry data, in which multiple samples of a
given telemetry parameter occur in a single packet.
4160.12
The EOC shall be capable of processing AIRS high rate
engineering data and providing the AIRS IOT with the ability
to perform analysis on that data via the IST. AIRS
engineering data will be provided to the EOC only as
playback data (i.e. not real-time).
4170
4170.1
The EOC shall provide the capability to perform statistical
analysis and produce reports and plots of housekeeping
data.
4170.2
The EOC shall provide the capability to generate and deliver
parameter-level carry-out files upon user request.
4170.2.1
The EOC shall generate spacecraft housekeeping carry-out
files for the MODIS and AIRS instruments and provide the
data to the GSFC DAAC. These carry-out files will contain
specific spacecraft housekeeping parameters that are
needed for science data processing.
4170.2.2
The EOC shall generate attitude carry-out files and provide
them to the GSFC DAAC and LaRC DAAC for Data
Preprocessing (DPREP). The attitude carry-out files will
contain specific information from the GBAD data stream.
4170.2.3
The EOC shall initiate the transfer of spacecraft
housekeeping and attitude carryout files to the GSFC DAAC
and LaRC DAAC within 2 hours of receipt from EDOS of all
of the spacecraft telemetry data needed for the files. This is
needed for the GSFC DAAC to meet the processing
requirements for AIRS data.
4170.3
The EOC shall provide the capability for the instrument
operations teams to submit an analysis request via their IST
and receive resulting analysis products i.e., (carryout files,
analysis reports and status reports).
4170.4
The EOC shall provide the capability to perform offline
analysis on 3 independent telemetry streams:
a. Observatory housekeeping
b. GBAD
c. AIRS high rate engineering or flexible packets
4180
The EOC will ensure that history data for the life of the
mission is archived and is available for retrieval when
needed. History data consists of a variety of data products
that are collectively a record of all data received and
generated by the EOC. The EOC will utilize the GSFC DAAC
for online long-term history data archival and retrieval.
4180.1
The EOC shall ensure that all real-time and playback
telemetry received from the observatory are stored and
available for retrieval for the life of the mission. This
telemetry includes:
a. Observatory housekeeping
b. GBAD
c. AIRS high rate engineering or flexible packets
4180.2
The EOC shall ensure that all commands and loads
transmitted to the observatory are stored and available for
the life of the mission.
4180.3
The EOC shall ensure that all event messages are stored
and available for the life of the mission.
4180.4
The EOC shall ensure that all system actions are stored and
available for the life of the mission.
4180.5
The EOC shall ensure that all of the controller fault logs and
activity and TMON logs from the operational controllers, and
back-up controllers, and their controller fault logs for a total
of 32 fault logs are stored and available for the life of the
mission.
4180.6
The EOC shall ensure that all reports and mission schedules
are stored and available for the life of the mission.
4180.7
The EOC shall provide the capability to store history data at
the GSFC DAAC and to retrieve the appropriate data from
the GSFC DAAC as needed.
4200
4200.1
The EOC shall provide the capability to receive and process
flight software loads from the FMT (IVVF) or the spacecraft
contractor SDVF and to transmit the loads to the spacecraft.
4200.2 (Deleted)
4200.2.1 (Deleted)
4200.3
The EOC shall verify the flight software loads received from
the FMT (IVVF). This includes verifying the source,
destination, and general format. It does not include verifying
the validity of load content.
4200.4
The EOC shall have the capability to accept and transfer
files to and from the FMT (IVVF), as per the EOC-IVVF ICD.
4300
4300.1
The EOC shall provide facilities to support the requirements
levied in Section 4000.
4300.2
The EOC shall provide facilities (including Government
Furnished Equipment [GFE]) by Launch minus 18 months.
4300.3
The EOC shall provide facilities for conduct of real-time (RT)
and off-line operations 24 hours per day, seven days per
week until end of mission.
4300.4
A physically separate, backup control center capability shall
be provided to support real-time health and safety operations
should the EOC become incapacitated due to a catastrophic
event.
[See Open Issues Matrix.]
4300.5
The EOC shall provide adequate space to support aroundthe-clock real-time operations with a nominal console staff.
4300.6
The EOC shall provide adequate facilities for a nominal
(GSFC-based) off-line day staff consisting of flight systems
engineering, ground system engineering, and operations
management.
4300.7
The EOC shall provide adequate facilities for mission
planning, network scheduling, command management, trend
analysis, and Flight Dynamics operations support.
4300.8
The EOC shall provide adequate space for housing and use
of the Aqua simulator (supplied by TRW, the observatory
manufacturer).
4300.9
The EOC facility shall support the required operational and
administrative voice circuits. The specific voice requirements
are specified in Section 5100.
4300.10
The EOC shall provide adequate regular (black) telephones
in all EOC operations areas.
4300.11
The EOC shall provide adequate space, regular (black)
telephones, power, and computer network interfaces for
instrument operations teams and their associated ground
support equipment for conduct of launch and instrument
activation activities.
4300.11.1
Facility support for the instrument operations teams shall be
provided from launch minus six months until launch plus 3
months.
4300.12
The EOC shall provide adequate workspace, regular (black)
telephones, and computer network interfaces for the TRW
resident team from launch minus two months until launch
plus three months.
4300.13
The EOC shall provide access to photocopy and facsimile
capabilities in close proximity to the operations control area
from launch minus 3 months to end of mission.
4300.14
The EOC shall provide additional separate space for
planning, conference, and other launch-related activities that
is in close proximity to the operations control area. Voice
communications and visual data displays for use in
monitoring operations is necessary in this space.
4300.15 (Deleted)
4300.16
The EOC facility shall provide UTC clock displays and a
countdown clock in each operational area such that all
operators may view the display.
4300.17
The EOC facility shall provide for personnel access control
for the operational areas.
4300.18
The EOC shall provide access to 'NASA Select' and
monitors necessary to view it.
4300.19
The EOC facility shall satisfy human engineering
requirements for lighting, safety, and ergonomics.
4300.20
The EOC shall provide an uninterruptable power supply for
all mission critical systems.
4300.21
The EOC shall maintain an environment that meets
established NASA/GSFC health standards and maintains a
temperature of 70 degrees Fahrenheit + / - 5 degrees
Fahrenheit.
5000
5000.1
EMSn, EOS Science Support network (ESSn), and NISN shall
provide data communications through all operations phases,
including:
o
o
o
o
o
o
EOC key interface testing
End-to-end testing
Operational readiness testing
Launch
On-orbit checkout
Routine mission operations.
5000.2
EMSn shall provide all interfaces between the EOC and the FDS to
transfer real-time and playback attitude and sensor data to the FDS
and for the FDS to provide planning aids, orbit, attitude validation,
sensor calibration data and reference files to the EOC.
5000.3
EMSn shall provide interfaces between the EOC/EDOS and EPGS
and the EOC/EDOS and WGS to transport spacecraft commands
and receive housekeeping telemetry.
5000.4
EMSn shall provide an interface between the EPGS and the MMFD
and between WGS and the MMFD for transfer of tracking data to
the MMFD.
5000.5
EMSn shall provide an interface between the EOC and the WOTIS
for transfer of station acquisition data.
5000.6
EMSn shall provide an interface between the WOTIS and EOC for
transfer of station pass reports and pass monitor data to the EOC.
5000.7
EMSn shall provide an interface between the WOTIS and the
EPGS and WGS for transfer of schedules and acquisition data to
the stations and reception of station pass reports and monitor data.
5000.8
EMSn shall provide an interface between the EOC and WOTIS to
schedule station support.
5000.9
EMSn shall provide all interfaces between the EOC and the NCC to
transfer TDRSS scheduling requests, the confirmed active
schedule, User Performance Data (UPDs), Ground Control
Messages (GCMs) and Operations Performance Messages
(OPMs).
5000.10
EMSn shall provide interfaces between the FDS and the NCC for
the transfer of Aqua orbit data to the NCC.
5000.11
The Aqua ground system shall be compliant with NASA Policy and
Guidelines Document 2810.1, and shall generate the following
security-related documentation at a minimum:
a. IT Security Plan - provides security-related information on the
managed systems and describes its associated risk and the
controls in place to counter risks. Note that this plan needs to be
updated periodically, at a minimum of every three years.
b. IT Security Contingency Plan - describes the arrangements to be taken to
continue system operations in a disaster.
c. Risk Management Plan - provides a process for conducting a risk assessment
and analysis to determine the assets at risk.
5000.12
Closed EMSn shall provide an interface between the EOC/EDOS
and the SN WSC for transport of command and telemetry data.
5000.13
Closed EMSn shall provide an interface between the EOC/EDOS
and the EPGS to transport science data recorded at the ground
stations.
5000.14
Closed EMSn shall provide an interface between the EOC/EDOS
and the spacecraft manufacturer facility at Redondo Beach,
California for transfer of spacecraft command and telemetry data
during prelaunch testing. A multi-channel data transport service is
required to support spacecraft to EOC/EDOS testing prior to
spacecraft shipment to the launch site. The data channel
requirements for the pre-shipment test phase are: 1) a single
command line operating up to 2 kbps originating at GSFC/EDOS,
2) a telemetry line operating at 524.288 kbps originating at the
TRW facility, and 3) a telemetry line operating at 16.384 kbps
originating at the TRW facility. This service is required at L-4
months.
5000.15
Closed EMSn shall provide an interface between the EOC and the
VAFB launch site for transfer of spacecraft command and telemetry
data during prelaunch testing at the launch site. The capabilities of
the data transport service to the launch site are identical to the
capabilities required to the TRW facility.
5000.16
NISN/EMSn shall provide voice communications between all
operational facilities during all phases of the mission.
5000.17
NISN/EMSn shall provide voice communications with the TRW
SCITF at Redondo Beach, CA. during the prelaunch testing phase.
5000.17.1
Two full duplex voice lines and two voice instruments (provided by
the Aqua Project) are required to be installed at the TRW SCITF to
support pre-shipment testing. This service is required at L-7
months.
5000.18
During the prelaunch testing phase, NISN/EMSn shall provide voice
communications capability at Vandenberg Air Force Base (VAFB).
Testing at the launch site is planned to commence at L-4 months.
5000.19
Voice communication is required during all phases of the mission
between AGS, SGS, WGS, MGS and Wallops Orbital Tracking
Information System (WOTIS), and the EOC/EDOS at GSFC (Bldg
32). Prelaunch testing with stations will be required.
5000.19.1
Two duplex voice lines and seven voice instruments are required to
be installed at the EOC temporary control center located at GSFC
Bldg. 32, Room S9 to support prelaunch testing. This service is
required at L-14 months.
5000.20
In support of the Spacecraft 911 Emergency Service, EMSn shall
provide a communication link to carry 1.024 kbps housekeeping
telemetry flow from the WSC to the EOC via EDOS at all times
without prior scheduling.
5000.21
EMSn shall be capable of delivering to EDOS no less than 99% of
all the science data received from each EPGS station.
5100
The Aqua spacecraft will transmit real-time housekeeping telemetry data to and
receive command data from the AGS, SGS, MGS and WGS sites and the SN
(WSC). Additionally, real-time housekeeping telemetry and command links with
the SCITF and VAFB will be needed for pre-mission test support. Tables 5100.1
and 5100.2 specify the detailed real-time data transport requirements.
Table 5100.1 Real-time S-Band Command Data Transport Requirements
Communication
Type 1
Source
Destination
Source Data Rate(s)
Service Dates
EOC
EDOS LZPF
UDP/IP
125, 250, 500 bps, 1, 2 kbps
L-12 months to EOL
EDOS LZPF
AGS
TCP/IP
2 kbps
L-12 months to EOL
EDOS LZPF
SGS
TCP/IP
2 kbps
L-12 months to EOL
EDOS LZPF
MGS
TCP/IP
2 kbps
L-12 months to EOL
EDOS LZPF
WGS
TCP/IP
2 kbps
L-12 months to EOL
EDOS LZPF
WSC (SN)
TCP/IP
125, 250, 500 bps, 1 kbps
L-12 months to EOL
EDOS LZPF
SCITF (TRW)
TCP/IP
125, 250, 500 bps, 1, 2 kbps
L-16 months to
Launch
EDOS LZPF
VAFB
TCP/IP
125, 250, 500 bps, 1, 2 kbps
L-6 months to
Launch
1Communication
type reflects the current understanding of the EGS S-band command data
transport implementation approach and is not intended to levy specific implementation
requirements.
Table 5100.2 Real-time S-Band Telemetry Data Transport Requirements
Communication
Type 1
Source Data Rate(s) 2
Service Dates
TCP/IP
16.384, 524.288 kbps
L-12 months to EOL
EDOS LZPF
TCP/IP
16.384, 524.288 kbps
L-12 months to EOL
MGS
EDOS LZPF
TCP/IP
16.384, 524.288 kbps
L-12 months to EOL
WGS
EDOS LZPF
TCP/IP
16.384, 524.288 kbps
L-12 months to EOL
WSC
(SN)
EDOS LZPF
TCP/IP
1.024, 4.096 kbps
L-12 months to EOL
SCITF
(TRW)
EDOS LZPF
TCP/IP
1.024, 4.096, 16.384,
524.288 kbps
L-16 months to Launch
VAFB
EDOS LZPF
TCP/IP
1.024, 4.096, 16.384,
524.288 kbps
L-6 months to Launch
EDOS
LZPF
EOC
UDP/IP
1.024, 4.096, 16.384,
524.288 kbps
L-12 months to EOL
Source
Destination
AGS
EDOS LZPF
SGS
1Communication
type reflects the current understanding of the EGS S-band telemetry data
transport implementation approach and is not intended to levy specific implementation
requirements.
2The
16.384 kbps housekeeping stream and 524.288 kbps stored engineering or processor dump
streams may occur in parallel.
The Aqua spacecraft will transmit high-rate science telemetry data to the AGS,
SGS and MGS sites. The EDOS GSIF located at each site (except MGS) will
store and forward the science data to the EDOS LZPF at GSFC. Table 5100.3
specifies the detailed high rate science data transport requirements.
Table 5100.3 High Rate X-Band Science Data Store-and-Forward Transport
Requirements
Communication Type 1
Delivery
Time
Source
Destination
Data
Volume 2
AGS/EDOS
GSIF
EDOS
LZPF
clock/data
7.2
Gigabytes
(1 orbit)
30
minutes
L-8
months
to EOL
SGS/EDOS
GSIF
EDOS
LZPF
clock/data
7.2
Gigabytes
(1 orbit)
30
minutes
L-8
months
to EOL
MGS
WSC/EDOS
GSIF
3.6
Gigabytes
(0.5 orbit)
10
minutes
L-8
months
to EOL
3.6
Gigabytes
(0.5 orbit)
15
minutes
L-8
months
to EOL
TDRSS
KuBand
WSC/EDOS
GSIF
EDOS
LZPF
clock/data
Service
Dates
1Communication
type reflects the current understanding of the EGS X-band science data
transport implementation approach and is not intended to levy specific implementation
requirements.
2Data
volume is based on an average science data generation rate of 8.23 Mbps and a 100
minute orbit duration. A 16% overhead was added for CCSDS and Reed-Solomon encoding.
Table 5100.4 specifies the detailed EDOS LZPF rate-buffered data transport
requirements. Delivery of these data streams will occur via file transfers. The
rate-buffered service is to be initiated within 5 minutes after receipt of all data for
each contact at the EDOS LZPF. For network sizing, the following EDOS to EOC
rate-buffered data transfers are assumed to occur in parallel:
1. Housekeeping telemetry (extracted from X or S-Band)
2. AIRS high-rate engineering data
3. GBAD data
For network sizing, the EDOS to NOAA Server and NASDA EOC rate-buffered
data transfers are assumed to occur in parallel with each other, and with the
above EOC transfers. This establishes the worst-case scenario that the network
must handle.
Table 5100.4 EDOS Rate-Buffered Data Transport Requirements
Destination
Comm.
Type
Data Type
Data Volume
Delivery
Time
Service Dates
EOC
FTP
H/K telemetry (via
X-band)
12.3 Megabytes 1
2 mins.
L-10 months to
EOL
2 mins.
L-10 months to
EOL
5 mins.
L-10 months to
EOL
2 mins.
L-10 months to
EOL
30 mins.
L-10 months to
EOL
5 mins.
L-10 months to
EOL
5 mins.
L-10 months to
EOL
Source
EDOS
LZPF
(1 orbit)
EDOS
LZPF
EOC
FTP
H/K telemetry (via
S-band)
12.3 Megabytes 1
(1 orbit)
EDOS
LZPF
EOC
FTP
AIRS high-rate
engineering data
953 Megabytes 2
(1 orbit)
EDOS
LZPF
EOC
FTP
GBAD data
3 Megabytes 3
(1 orbit)
EDOS
LZPF
NOAA 5
Server
FTP
All science data
6.2 Gigabytes 4
(1 orbit)
EDOS
LZPF
NASDA
EOC
FTP
AMSR-E science
data
66 Megabytes 6
(1 orbit)
EDOS
LZPF
NASDA
EOC
FTP
GBAD data
3 Megabytes 7
(1 orbit)
1Calculation
is based on housekeeping data at 16.384 kbps for 1 orbit (100 minutes).
2Calculation
is based on AIRS high-rate data at 1.27 Mbps for 1 orbit (100 minutes).
3Calculation
is based on GBAD data at 4 kbps for 1 orbit (100 minutes).
4Calculation
is based on all science data at 8.23 Mbps for 1 orbit (100 minutes).
5NOAA
will provide a local server at GSFC Bldg 32, Room S-9. EDOS LZPF will push files to the
NOAA server.
6Calculation
7
is based on AMSR-E science data at 87.4 kbps for 1 orbit (100 minutes).
Calculation is based on GBAD data at 4 kbps for 1 orbit (100 minutes).
Table 5100.5 specifies the tracking data and acquisition data transport
requirements. Delivery of this information will occur via file transfers. The amount
of tracking data to be transferred from a ground station to the MMFD is about 500
bytes per contact per station. Acquisition data are transmitted once per day from
FDS to WOTIS/NCC and their amount is about 2600 bytes per station. WOTIS
distributes acquisition data to the ground stations as a part of the ground station
operations schedule.
Table 5100.5 Tracking and Acquisition Data Transport Requirements
Comm.
Type
Source
Destination
Data Type
Service Dates
AGS
MMFD
FTP
UTDF Tracking Data
L-10 mos to EOL
SGS
MMFD
FTP
UTDF Tracking Data
L-10 mos to EOL
WGS
MMFD
FTP
UTDF Tracking Data
L-10 mos to EOL
WSC
mmFD
FTP
UTDF Tracking Data
L-10 mos to EOL
FDS
WOTIS
FTP
EPGN Acquisition Data
L-10 mos to EOL
FDS
NCC
FTP
SN Acquisition Data
L-10 mos to EOL
NCC
WSC
FTP
SN Acquisition Data
L-10 mos to EOL
Table 5100.6 specifies the station scheduling data transport requirements.
Delivery of this scheduling information will occur via file transfers. These file
transfers between the EOC and WOTIS or between the EOC and NCC for
scheduling coordination will occur multiple times each day. Data traffic between
EOC and WOTIS/NCC is expected to be less than 30 Kbytes per day in each
direction. The operations schedule files to be transferred from WOTIS to ground
stations include acquisition data. The transfer will occur about once a day, and
the amount of data is about 4500 bytes per delivery per station. The size of the
weekly schedule files to be transferred from EOC to EDOS is expected to be less
than 1 megabytes.
Table 5100.6 Station Scheduling Data Transport Requirements
Source
Destination
Comm. Type
Data Type
Service Dates
EOC
WOTIS
FTP
EPGN Schedule
Coordination
L-10 mos to EOL
WOTIS
AGS
FTP
AGS Ops Schedule
(including acq data)
L-10 mos to EOL
WOTIS
SGS
FTP
SGS Ops Schedule
(including acq data)
L-10 mos to EOL
WOTIS
WGS
FTP
WGS Ops Schedule
(including acq data)
L-10 mos to EOL
WOTIS
MGS
FTP
MGS Ops Schedule
(including acq data)
L-10 mos to EOL
EOC
NCC
FTP
SN Schedule
Coordination
L-10 mos to EOL
EOC
EDOS
FTP
EPGN / SN Schedule
L-8 mos to EOL
Table 5100.7 specifies the station status data transport requirements. Upon
completion of a support, an EPGS or WGS station generates a Pass Results File
(with a size of 176 bytes per pass per station) and sends the file to WOTIS.
EPGS and WGS status data is also provided from the ground stations directly to
the EOC in realtime (at a maximum data rate of about 600 bytes per second).
The EOC sends GCMRs to the NCC, and in response, the NCC provides status
messages (GCM status and GCM disposition messages) to the EOC. The EOC
sends a User Performance Data (UPD) request message to the NCC, and in
response the NCC provides clock correlation support data and acquisition failure
notification messages to the EOC. The NCC also provides the EOC with UPD
messages.
Table 5100.7 Station Status Data Transport Requirements
Comm.
Type
Source
Destination
AGS
WOTIS
FTP
Data Type
Service Dates
Pass Result File
L-8 mos to EOL
SGS
WOTIS
FTP
Pass Result File
L-8 mos to EOL
WGS
WOTIS
FTP
Pass Result File
L-8 mos to EOL
MGS
WOTIS
FTP
Pass Result File
L-8 mos to EOL
AGS
EOC
TCP/IP
AGS Real-time Station Status
Message
L-8 mos to EOL
SGS
EOC
TCP/IP
SGS Real-time Station Status
Message
L-8 mos to EOL
WGS
EOC
TCP/IP
WGS Real-time Station Status
Message
L-8 mos to EOL
MGS
EOC
TCP/IP
MGS Real-time Station Status
Message
L-8 mos to EOL
EOC
NCC
TCP/IP
GCMRs and UPD Request
L-8 mos to EOL
NCC
EOC
TCP/IP
Status Data (GCM Status Message,
GCM Disposition Message, Acq
Failure Notification Message)
L-8 mos to EOL
NCC
EOC
TCP/IP
User Performance Data (UPD)
L-10 mos to EOL
NCC
EOC
TCP/IP
Clock Correlation Support Data
L-10 mos to EOL
Table 5100.8 specifies the IST data transport requirements. ISTs are used to
conduct mission planning and scheduling, monitoring of realtime telemetry and
performing offline instrument performance analysis. Actual data traffic will be
based on instrument team usage of the IST.
The HSB IST at INPE in Brazil will only have the capability to monitor realtime
housekeeping telemetry and schedules sent from the EOC. Similarly, the SCITF
IST at TRW in California will only have the capability to monitor realtime
housekeeping telemetry.
Table 5100.8 IST Data Transport Requirements
Comm.
Type
Source
Destination
EOC
AIRS IST JPL
EOC
HSB IST JPL
Data Type
Service Dates
TCP/IP
and FTP
Schedules, Selected Planning Aids,
Realtime H/K telemetry, Analysis
Data
L-8 mos to EOL
TCP/IP
Schedules, Selected Planning Aids,
L-8 mos to EOL
EOC
AMSU-A IST
and FTP
Realtime H/K telemetry, Analysis
Data
TCP/IP
and FTP
Schedules, Selected Planning Aids,
Realtime H/K telemetry, Analysis
Data
L-8 mos to EOL
JPL
EOC
AMSR-E IST
NASDA
TCP/IP
and FTP
Schedules, Selected Planning Aids,
Realtime H/K telemetry, Analysis
Data
L-8 mos to EOL
EOC
MODIS IST
GSFC
TCP/IP
and FTP
Schedules, Selected Planning Aids,
Realtime H/K telemetry, Analysis
Data
L-8 mos to EOL
Table 5100.8 IST Data Transport Requirements (Continued)
Comm.
Type
Source
Destination
EOC
CERES IST
LaRC
EOC
HSB IST
INPE
Data Type
Service Dates
TCP/IP
and
FTP
Schedules, Selected Planning
Aids, Realtime H/K telemetry,
Instrument Memory Dumps,
Analysis Data
L-8 mos to EOL
TCP/IP
and
FTP
Realtime H/K telemetry,
Schedules (monitor only)
L-6 mos to EOL
(Brazil)
EOC
SCITF IST
TRW (Ca)
TCP/IP
and
FTP
Realtime H/K telemetry
L-10 mos to L+3 mos
AIRS IST JPL
EOC
TCP/IP
and
FTP
Scheduling requests, Instrument
Loads, Analysis Requests
L-8 mos to EOL
HSB IST JPL
EOC
TCP/IP
and
FTP
Scheduling requests, Analysis
Requests
L-8 mos to EOL
AMSU-A IST
EOC
TCP/IP
and
FTP
Scheduling requests, Analysis
Requests
L-8 mos to EOL
EOC
TCP/IP
Scheduling requests, Analysis
L-8 mos to EOL
JPL
AMSR-E IST
NASDA
and
FTP
Requests
MODIS IST GSFC
EOC
TCP/IP
and
FTP
Scheduling requests, Instrument
Loads, Analysis Requests
L-8 mos to EOL
CERES IST LaRC
EOC
TCP/IP
and
FTP
Scheduling requests, Instrument
Loads, Analysis Requests
L-8 mos to EOL
HSB IST INPE
EOC
TCP/IP
and
FTP
IST / EOC Handshaking
L-6 mos to EOL
EOC
TCP/IP
and
FTP
IST / EOC Handshaking
L-10 mos to L+3 mos
(Brazil)
SCITF IST TRW
(Ca)
Table 5100.9 Voice Requirements
Number of Voice Circuits
Service Dates
Ground System Element
From
To
Listen Only
Talk/Listen
EOC
SN/NCC
1 SCAMA
L-12 mos to EOL
EOC
FDS
2 Closed Conf. Loops
(CCL)* 1
L-12 mos to EOL
FDS
MMFD
1 Closed Conf. Loop
(CCL) 1
L-12 mos to EOL
1 SCAMA
L-12 mos to EOL
(Bldg. 28)
EOC
EPGN
(AGS, SGS, MGS,
WGS,WOTIS)
EOC
EDOS
1 Closed Conf. Loop
(CCL)*
L-12 mos to EOL
** EOC
SCITF
2 SCAMA
L-14 mos to Launch
EOC
VAFB
EOC
ISTs
2 SCAMA
9 SCAMA
L-4 mos to Launch
1 SCAMA
L-12 mos to EOL
1 SCAMA
L-12 mos to EOL
5 Closed Conf. Loop
(CCL)*
L-12 mos to EOL
(non-AMSR-E)
EOC
AMSR-E
IST
EOC
EOC
1
*
It is envisioned that the same CCLs in place for FDS support of the Terra mission can
also be used for Aqua support.
CCLs are internal to Bldg 32.
** The Aqua EOC Temporary Control Center will be located in GSFC Bldg. 32, Room S9
until approximately 90-120 days after the Terra launch.
6000
6000.1
The data received from the EOS Aqua spacecraft and
instruments are delivered to the EDOS. EDOS will provide
real-time forward and return link data handling services
between EPGS, WGS and the TDRSS/WSC and the EOC to
support command and control and health and safety
monitoring functions. EDOS also provides a rate buffered
service to NOAA and the EOC. The rate buffered service will
make raw data available for delivery within 5 minutes of
receipt of the entire data set at the EDOS facility at GSFC for
an EPGS contact period.
EDOS will also be responsible for the initial data processing
(level 0). Level 0 processing consists of packet time-order
sequencing, data transmission artifact removal, data overlap
removal and data quality checking. The level zero data are
then transferred to a designated DAAC responsible for
further processing of a particular instrument.
6000.2
EDOS shall provide an interface with the Alaska Ground
Station (AGS), Svalbard Ground Station (SGS), McMurdo
Ground Station (MGS), and the Wallops Ground Station
(WGS) to send command data to the spacecraft and to
receive telemetry data from the spacecraft.
6000.3
EDOS shall provide the capability to receive and store raw
Aqua science data from the MGS via the TDRSS Ku-Band
service. These transfers can only occur when EDOS is not
supporting a Terra Ku-Band contact.
6000.4
EDOS shall provide the capability to transmit raw Aqua
science data from WSC to the EDOS LZPF between Terra
data transfers.
6000.5
In support of pre-launch activities including spacecraft
integration, EDOS shall interface with the Spacecraft
Integration and Test Facility (SCITF) at TRW in Redondo
Beach, CA to transmit command data and receive
housekeeping telemetry.
6000.6
EDOS shall interface with the VAFB launch processing site
to support pre-launch activities.
6000.7
The EDOS shall process the X-band SSR dump data stream
containing GBAD packets and produce rate buffered data
sets for delivery to the EOC.
6000.8
The EDOS shall process the X-band SSR dump data stream
containing GBAD packets and produce rate buffered data
sets for delivery to the NOAA server.
6000.9
EDOS shall provide playback (recorded) housekeeping data
as a VCDU service to the EOC.
6000.10
EDOS shall deliver real-time, operations management
report, and post-pass data products to the appropriate
destinations, as described in Tables 6100.1 and 6100.2.
6000.11
EDOS shall create a standard 2 hour Production Data Set
(PDS) for all APIDs from the following instruments or
sensors:
a. AIRS
b. AMSU-A
c. HSB
d. AMSR-E
e. MODIS
f. GBAD
6000.12
EDOS shall create a 24 hour PDS for all APIDs from the
CERES instrument.
6000.13
EDOS shall create Expedited Data Sets (EDS) as requested
for APIDs from the following instruments:
a. AIRS
a. AMSU-A
b. CERES
c. HSB
d. MODIS
6000.14
EDOS shall create rate buffered data sets and deliver them
to the NOAA server for data from the following instruments
or sensors:
a. AIRS
b. AMSU-A
c. CERES
d. HSB
e. AMSR-E
f. MODIS
a. GBAD
6000.15
EDOS shall transmit PDS files within 8 hours of receiving all
of the relevant data at the EDOS LZPF. This provides the
ability for EDOS to incorporate data from MGS into the PDS
files, when needed, using normal processing. [Note: Use of
MGS is an open issue. Without the MGS requirement, the
EDOS PDS latency requirement is 4 hours.]
6000.16
EDOS shall be capable of processing CCSDS packets with
different secondary header structures which are APID
dependent.
6000.17
EDOS shall be capable of processing CCSDS packets with
TAI (CUC) as well as UTC (CDS) time stamps that comply
with CCSDS time code recommendations.
6000.18
EDOS shall distribute Level 0 data sets as defined in Table
6100.2.
6000.19
EDOS shall provide a backup of all Level 0 data sets
delivered by the EDOS, as specified in requirements
6000.11 and 6000.12, on non-volatile storage media.
6000.20
EDOS shall support Aqua pre-launch activities (e.g.,
operational readiness tests and simulations).
6000.21
EDOS shall support communications from both the WSC
and EPGN (AGS, SGS and WGS) stations. The sum of
EPGN and TDRSS equals 17-18 scheduled passes daily.
6000.22
EDOS shall provide the capability to receive, capture, and
process Aqua low rate real-time return link data from the
EPGN stations at a rate of 16.384 kbps.
6000.23
EDOS shall provide the capability to receive, capture, and
process Aqua low rate playback return link data from the
EPGN stations at a rate of 524.288 kbps.
6000.24
EDOS shall provide the capability to receive, capture, and
process Aqua high rate return link data from the EPGN
stations at a rate of 150 Mbps.
6000.25
EDOS shall provide Reed-Solomon (Grade of Service II)
decoding on the Aqua return link data as required.
6000.26
EDOS shall provide AOS CCSDS Path and Virtual Channel
Data Unit services on Aqua return link data.
6000.27
EDOS shall support CCSDS COP-1 by extracting the
Command Link Control Word (CLCWs) from the trailers of
the real-time return link Coded Virtual Channel Data Units
(CVCDUs) and passing them on to the EOS Operations
Center (EOC).
6000.28
EDOS shall provide enhanced CLCW EDUs to the EOC that
include the VCDU primary header and the CLCW.
6000.29
EDOS shall receive Command Data Blocks from the EOC.
6000.30
EDOS shall transfer EOS forward link data to the EPGN
stations at a rate of 2 kbps.
6000.31
EDOS shall provide to the ECS and other external
management entities summary status, quality, and
accounting information on all mission data handling and
processing.
6000.32
EDOS shall provide the capability to remotely operate EDOS
functions at the EPGS.
6000.33
EDOS shall provide Data Archive services for Aqua data as
specified in the ESDIS project Level 2 requirements, Volume
2, Requirements 2.0.4, 2.2.0.4, 2.2.3.5, and 2.2.3.6
6000.34
EDOS shall provide the capability for capture of all Aqua
return link data on separate, non-volatile physical media, and
for storage for 30 days after receipt.
6000.35
EDOS shall create and deliver all external data products
including rate buffered data, EDSs, PDSs, and archive data
in conformance with the EDOS-EGS Elements ICD.
6000.36
EDOS shall provide Operational Availability (Ao) for Aqua
mission services as specified in the ESDIS project Level 2
requirements, Volume 2, Section 2.5.
6000.37
EDOS shall support the use of a "911 mode" by the
spacecraft in which the spacecraft automatically initiates an
S-band housekeeping telemetry flow via the SN. EDOS must
thus be ready to receive, process and transfer real-time
telemetry data at any time. The spacecraft would use this
capability when certain anomaly conditions are automatically
detected onboard.
6000.38
EDOS shall de-randomize the X-band downlink data when the data
are randomized in accordance with the CCSDS Recommendations.
6000.39
EDOS shall be capable of delivering to DAACs no less than 98% all
the science data received from the EPGS via EMSn.
6100
Tables 6100.1 and 6100.2 describe the data processing product requirements for
the Aqua mission.
Table 6100.1 EDOS Realtime and Operations Management Report
Requirements
Source
Destination
Data Type
Communication Type
EOC
EDOS LZPF
Commands
UDP/IP
EDOS LZPF
EOC
Realtime Housekeeping
UDP/IP
Table 6100.2 EDOS Post-Pass Data Product Requirements
Rate
Buffered
Data
Expedited
Data Set
(EDS)
Production
Data Set
(PDS) Level 0
Product1
Product2
Product
Telemetry
Stream
Product
Source
Product Destination
X4
AIRS
EDOS LZPF
GSFC DAAC
X
EDOS LZPF
NOAA Server
X
EDOS LZPF
EOC
EDOS LZPF
GSFC DAAC
EDOS LZPF
NOAA Server
EDOS LZPF
LaTIS at LaRC
DAAC
EDOS LZPF
NOAA Server
EDOS LZPF
GSFC DAAC
EDOS LZPF
NOAA Server
EDOS LZPF
NSIDC DAAC
X
EDOS LZPF
NOAA Server
X
EDOS LZPF
NASDA EOC
EDOS LZPF
GSFC DAAC
EDOS LZPF
NOAA Server
EDOS LZPF
NSIDC DAAC
X
EDOS LZPF
NOAA Server
X
EDOS LZPF
NASDA EOC
X
EDOS LZPF
EOC
X5
EDOS LZPF
EOC
X4
AMSU-A
X
X
X
X4
CERES
X3
X
X4
HSB
X
X
AMSR-E
X
X4
MODIS
X
X
GBAD
X
Housekeeping
Data Stream
1
Rate buffered service is initiated within 5 minutes after receipt of all data for each contact at the
EDOS LZPF.
2
Expedited data shall be delivered within 3 hours of a completed spacecraft contact session.
3
CERES requires 24 hour PDS. All others are EDOS standard 2 hour PDS.
4
On an occasional basis, such as for in-orbit checkout or anomaly resolution. Routine or
continuous requests for EDS's are not anticipated.
5
The housekeeping rate buffered product provided to the EOC will be at the VCDU level.
7000
7000.1
Flight Dynamics (FD) shall be responsible for providing orbit,
attitude, and mission analysis support to the EOS PM mission.
Orbit support shall include orbit determination, generation of
definitive and predictive orbit ephemeris, and generation of onboard
orbit computation required input parameters. The navigation data
sources for the mission shall be a combination of TDRSS, WGS
and EPGS tracking passes. TDRSS will provide an average of four
ten-minute contacts per day for tracking and clock correlation
support. WGS will be required to take 2 tracking passes per day
and EPGS will be required to take one tracking pass per orbit
(either AGS or SGS). No tracking is required from MGS. This
tracking pass scenario is necessary to meet the definitive orbit
determination requirement. Attitude responsibilities shall include
ground attitude determination and control support, attitude sensor
alignment and calibration, and evaluation of the onboard attitude
control system (ACS) performance. The FD operational phase will
be supported by the FOT. The Aqua mission Flight Dynamics Team
(FDT) shall also be responsible for providing pre-mission analysis
and mission planning aids for both prelaunch testing/simulations
and the mission phases identified below. The FDT shall provide
support during pre-launch, launch acquisition, and checkout
mission phases of EOS Aqua.
The premission phase to be supported by FD is:
1. Testing/Simulations - the FDT will provide simulated data for testing
including ephemerides, planning aids, tracking data, and necessary
staffing for spacecraft simulation support
The mission phases to be supported by FD are:
1. Launch/Acquisition - begins with the transition to internal
power before launch. During this phase, the spacecraft will
null any attitude rates and perform Earth acquisition. It also
includes the delta-V maneuvers required to establish the
operational orbit.
2. Checkout - begins after the initial delta-V maneuvers are
complete. Includes initialization and checkout activities prior
to normal operations.
3. Operational - begins after initialization and checkout
activities are complete. Routine operations and activities to
perform orbit determination and maintain nominal orbit and
spacecraft health and safety will be provided using the
appropriate operations support contract reporting to the
Service Level Agreement owner. Non-routine, contingency,
and/or other special support will be provided as required
during the operational phase by FD.
FD responsibilities can be summarized as:
o
Spacecraft Processor Support.
- Generate EOS Aqua ephemeris for spacecraft onboard orbit calculation.
- Perform orbit validation
- Provide verification support
o
Calibration Support
- Calibrate alignments of the Star Tracker
Assemblies (STAs), Inertial Reference Units
(IRUs), Three Axis Magnetometers (TAMs),
and Earth Sensor Assemblies (ESAs)
- Calibrate the IRU scale factors and drift rate biases
- Calibrate Thrusters following launch
o
General mission and planning support
- Determine initial Aqua orbit
- Assess initial Aqua orbit
- Determine coarse real-time EOS Aqua attitude
- Provide mission planning aids
- Provide attitude sensor hardware
performance monitoring - periodic check, not
trending
- Determine definitive and predictive EOS Aqua
orbit ephemeris and perform maneuver
prediction and planning
- Estimate spacecraft oscillator frequency biasMulti-Mission Flight Dynamics (MMFD)
- Provide near-real-time maneuver monitoring
- Provide ground station acquisition data
- Provide TDRSS acquisition data
Flight Dynamics Definitions
attitude error: FDS shall use the best available attitude sensor
data (transformed to the body coordinate system [BCS]) to define
the zero attitude reference of the spacecraft. Zero attitude error
shall exist when the line normal to the pitch-roll plane of the BCS is
parallel to the radius vector from the spacecraft center of mass to
the center of the earth (i.e., parallel to the Z-axis), and the roll-yaw
plane of the BCS is parallel to the plane of the orbit. This alignment
is limited to the knowledge of the sensor frame relative to the BCS.
body coordinate system (BCS):
-Y: parallel to the orbit momentum vector,
+Z: parallel to nadir vector,
X: completes the orthogonal triad
solar beta angle: the angle between the Earth-to-Sun vector and
the orbital plane. The angle is measured in the plane formed by the
Earth-to-Sun vector and the angular momentum vector.
lunar beta angle: the celestial latitude of the Earth-to-Moon vector
measured from the ecliptic plane, positive to the North, negative to
the South
path number: calculated based on the longitude of the ascending
node of the orbit. There are 233 paths, path 1 corresponds to
longitude 295.4º. Since each orbit covers 16 grid lines, the path
numbers for each orbit will increment by 16 each orbit.
penumbra: the conical region opposite the direction of the Sun in
which the disk of the Sun is partially blocked from view by the disk
of the Earth or Moon
umbra: the conical region opposite the direction of the Sun in which
the disk of the Sun is completely blocked from view by the disk of
the Earth or Moon
roll axis (X): positively oriented in the direction of orbital flight,
completing an orthogonal triad with the Y-axis and Z-axis
pitch axis (Y): oriented normal to the orbit plane, with positive
sense opposite to that of the orbit's angular momentum vector
yaw axis (Z): Earth center fixed, parallel to the satellite radius
vector from the spacecraft center of mass to the center of the Earth
7100
The following sections provide the FD requirements for support of
EOS Aqua attitude determination and control. The requirements
detailed are for attitude determination and validation, sensor
calibration and alignment, and spacecraft processor support.
7110.1 Spacecraft, FOT
Detailed Requirement Product
Mission
Phase
FDS shall provide the
EOC a predicted
attitude quaternion for
upload to the
spacecraft to support
initial star acquisition
of the STA.
All
Attitude
quaternion
and
associated
epoch time
Performance
Requirement
Accuracy: 5 degree roll and
pitch, 6 degree yaw
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: As needed, to
support spacecraft transition
to fine point mode
Reference: Approximately 1
orbit of TAM, MTA, and
IRU data will be required to
meet this accuracy
constraint
1. Spacecraft, MODIS, Thermal Engineers
Detailed Requirement Product
FDS shall provide the
EOC with the predicted
Sun vector-tospacecraft BCS during
the fixed attitude
period of attitude
maneuvers.
3x3 rotation
matrix in
BCS and
table of
vector to
spacecraft
body angles
Mission
Phase
All, but
particularly in
support of large
attitude
maneuvers such
as inclination
control
Performance
Requirement
Time Span: 4 week, 78
weeks
Accuracy: +/- 1 deg. or best
available.
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: 4 week, weekly;
78 weeks every 4 weeks
Reference: Spacecraft body
coordinate system
7110.3 Spacecraft, FOT
Detailed Requirement Product
Mission
Phase
FD shall verify EOS
Aqua is meeting the
operational attitude
requirements in non
real-time using the Star
Catalog provided by
TRW.
All
Comparison
of ground
and
spacecraft
quaternions
Performance
Requirement
Accuracy: ±25 arc-sec 3sigma. Derived from
processed or raw attitude
sensor data
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Every 4 weeks
Reference: comparison of
ground and spacecraft
quaternions
7110.4 FOT
Detailed Requirement Product
FD shall verify EOS
Aqua is meeting the
operational attitude
requirements in near
real-time.
EOS realtime coarse
attitude
Mission
Phase
All
(when necessary
sensor data are
available)
Performance
Requirement
Accuracy: ± 1 degree (3sigma) each axis after
calibration or best available.
Derived from all available
attitude sensors when valid.
Response: The displayed
solutions shall be
electronically delivered to
the EOC within 8 seconds of
receipt of telemetry data.
Frequency: All realtime
passes during
launch/acquisition and
checkout, during scheduled
simulations, maneuvers,
anomalies, and upon request
of the EOC
Reference: Units shall be in
degrees.
7120.1 FOT
Detailed Requirement Product
Mission Phase
FD shall verify the
STAs alignment
stability and sensitivity
of star magnitude
measurements meet
Testing/
Simulations
Notification
Checkout
Performance
Requirement
Accuracy: Best available
Response: Delivery to EOC
shall be as defined in the
operational attitude
requirements.
Operational
FDS ICD
Frequency: Checkout –Once
Operational-As needed
7120.2 FOT
Detailed Requirement Product
Mission Phase
FDS shall evaluate the
IRUs for drift stability.
Testing/
Simulations
IRU biases
Checkout
Performance
Requirement
Accuracy: Best available
Response: Delivery to EOC
shall be as defined in the
FDS ICD
Operational
Frequency: Checkout – as
needed Operational -Every 4
weeks
7120.3 FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the STA 1 & 2
EOC STA alignment
alignment
matrices.
matrices
Testing/
Simulations
Checkout
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Operational
Frequency: Checkout – once
Operational- As needed
7120.4 FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the STA scale
EOC the STA star
factor
coordinate scale factor coefficients
coefficients.
Testing/
Simulations
Checkout
Operational
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Checkout –once
Operational–As needed
7120.5 FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the IRU
EOC the IRU
alignment
alignment matrices.
matrices
Testing/
Simulations
Checkout
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Operational
Frequency: Checkout – once
Operational –As needed
7120.6 FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the IRU scale
EOC the IRU scale
factor
factor coefficients.
coefficients
Testing/
Simulations
Checkout
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Operational
Frequency: Checkout –once
Operational –As needed
7120.7 FOT
Detailed
Requirement
Product
Mission Phase
FDS shall deliver to
the EOC the TAM
alignment matrices.
TAM
alignment
matrices
Testing/Simulations
Accuracy: Best available
Checkout
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Operational
Performance
Requirement
Frequency: Checkout– once
Operational –As required
7120.8 FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the ESA
EOC the ESA
alignment
alignment matrix.
matrix
Testing/
Simulations
Checkout
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Operational
Frequency: Checkout – once
Operational – As required
7130.1 Spacecraft, FOT
Detailed
Requirement
Product
FDS shall define the Table of
spacecraft maneuvers single-axis
required to perform
rotations
alignment calibration
of the IRUs. FDS
shall work with the
Flight Ops Team to
plan the necessary
maneuvers.
Mission Phase
Performance
Requirement
Testing/Simulations
Accuracy: Best available
Checkout
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Operational
Frequency: Checkout – once
Operational – as needed
Reference: STA data are
required to perform this
function
7130.2 FOT, MODIS
Detailed Requirement Product
Mission Phase
FDS shall deliver to the Table of
EOC predicted
rotations
spacecraft attitude
angles and rates for
FOT scheduled attitude
maneuvers.
All
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: As needed
7140.1 FOT
Detailed
Requirement
Product
Mission Phase
FDS shall provide to
the EOC the STA
star density profile.
Star ID
All
minimum,
maximum, and
average orbit
angle separation
between stars,
star magnitude,
FOV horizontal
and vertical
position and time
of entrance, and
FOV horizontal
and vertical
position and time
of exit
Performance
Requirement
Timespan: 3 weeks
Accuracy: +/-15 sec after 72
hours
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Once a week
7140.2 FOT
Detailed Requirement Product
Mission Phase
FDS shall provide to
the EOC graphical
plots of the orbit angle,
time, and Star ID for
all the stars in the FOV
of each of the STAs
during the prediction
period.
All
Orbit angle,
time, Star ID
Performance
Requirement
Timespan: 7 Days
Accuracy: +/-15 sec after 72
hours
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Once a week
7140.3 FOT, AIRS
Detailed Requirement Product
Mission Phase
FDS shall provide star
interference times to
the EOC.
All
Star ID,
Performance
Requirement
Accuracy: +/- 15 seconds
after 72 hours
STA ID,
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
FOV entrance
and exit times,
Interference
start and stop
times,
Interference
type (Sun,
Moon, Earth,
specified
Planets)
Timespan: 7 days
Frequency: Daily
7140.4 FOT
Detailed Requirement Product
Mission Phase
FDS shall provide to
EOC a table of sun and
moon interference
times of the ESA.
All
ESA number,
FOV ID, start
and stop
interference
times,
interfering
object
Performance
Requirement
Accuracy: +/-15 sec after 72
hours
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Timespan: 7 days
Frequency: Daily
7200
The following sections provide the FDS requirements for Aqua orbit
determination, predictive orbit information, orbit maneuver planning,
and TDRSS, EPGS, WGS and direct playback site contact
predictions.
1. FOT
Detailed Requirement
Product
Mission Phase
FDS shall provide a 2dimensional display of the
spacecraft ground track
projected on the earth's
surface in conjunction
Video display,
with the intent
to distribute the
display in the
EOC
All
Performance Requirement
Accuracy: Best effort
Frequency: Continuous
display
with SN, EPGS & WGS
communications coverage
areas, also projected on
the earth's surface
Continental outlines, and
day/night contour.
FDS shall provide a high
resolution, 3-dimensional
display of the Sun (and
Aqua-to-Sun vector),
Earth, Moon, Aqua
spacecraft, and all 6
TDRSs which updates
their locations in realtime. The location and
attitude of Aqua shall be
updated based on real
telemetry.
7210.2 FOT
Detailed Requirement Product
Mission Phase
FDS shall provide
predictive spacecraft
ephemeris information
at precisely each 10
minute clock time for a
48 hour period.
All
Predictive
spacecraft
ephemeris
Performance Requirement
Time Span: 48 hours
Accuracy: Onboard orbit
shall be maintained to 300
meters RSS and velocity to
0.5 meters/second 3-sigma
after ephemeris data uplink
plus 24 hours.
Response: Delivery to EOC
shall be as defined in the
FDS ICD.
Frequency: Once per day
Reference: Mean of J2000
3. AMSR-E
Detailed
Product
Mission
Pe
Requirement
FDS shall
provide
spacecraft
definitive
ephemeris
data at 1
minute
intervals.
Phase
Re
Definitive All
ephemeris
Time Span: 48 ho
Accuracy: 20 met
sigma
Response: Delive
EOC shall be as d
the FDS ICD
Frequency: Once
Reference: Mean
4. 7210.3.1 AIRS, CERES, MODIS, DAAC
Detailed Requirement Product
Mission Phase
FDS shall provide
spacecraft definitive
ephemeris data at 1
second intervals.
All
Definitive
ephemeris
Performance
Requirement
Time Span: 24 hours
Accuracy: 20 meters RSS 3
sigma
Response: Delivery to the
DAAC shall be as defined in
the FDS ICD
Frequency: Once per day
Reference: Mean of J2000
7210.4 AIRS, AMSR-E
Detailed Requirement Product
Mission Phase
FDS shall provide a
product describing the
difference between the
predicted and definitive
spacecraft ephemeris
All
at 1 minute intervals.
Difference
between the
predicted and
definitive
spacecraft
ephemeris
Performance
Requirement
Time Span: 48 hours
Accuracy: Onboard orbit
shall be maintained to 300
meters RSS and velocity to
0.5 meters/second 3-sigma.
after ephemeris data uplink
plus 24 hours.
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Once per day
Reference: Mean of J2000
7210.5 Spacecraft, FOT
Detailed Requirement Product
FDS shall provide to
the EOC an
independent estimate
of the spacecraft Sband oscillator
frequency bias.
Mission Phase
S-band
All
oscillator
frequency bias
Performance
Requirement
Accuracy: +/- 1 Hz
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Checkout – once
per day
Operational – once per week
7210.6 AIRS, MODIS, CERES
Detailed Requirement Product
Mission Phase
FDS shall deliver to the Predictive
EOC and DAAC the
ephemeris
predicted EOS
ephemeris at 1 minute
intervals.
All
Performance
Requirement
Time Span: 7 weeks
7 days
Accuracy: Onboard orbit
shall be maintained to 300
meters RSS and velocity to
0.5 meters/second 3-sigma.
after ephemeris data uplink
plus 24 hours.
Response: Delivery to the
EOC and DAAC shall be as
defined in the FDS ICD.
DAAC will receive 7-day
products only.
Frequency: 7 weeks –
weekly
7 days - daily
Reference: Mean of J2000
7210.7 FOT, AMSR-E
Detailed Requirement Product
Mission Phase
FDS shall deliver to the Post maneuver All
EOC the post
report
maneuver report
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: After each EOS
Aqua delta-V maneuver
7210.8 FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the
EOC an estimate of the
X-band oscillator
frequency.
All
X-band
oscillator
frequency
report
Performance
Requirement
Accuracy: +/-5 Hz
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Once per week
7220.1 CERES, AMSR-E, MODIS, FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the Orbit adjust
EOC a prediction of
maneuver
orbit adjustment
request
maneuvers needed.
All
Performance
Requirement
Timespan: 7 weeks
Accuracy: Ground track
repeat shall be maintained to
within ± 20 Km, the
ascending node mean time
shall be maintained at 1:30
PM ± 15 min, and radial
orbit position repeatability
for a given latitude shall be
+10/-5 Km, sunsynchronous and frozen
orbit conditions shall be
maintained
Frequency: Weekly
Reference: UTC
7220.2 FOT
Detailed Requirement Product
Mission Phase
FDS shall deliver to the Orbit adjust
EOC the required
maneuver
thruster burn times.
parameters
All
Performance
Requirement
Accuracy: Ground track
repeat shall be maintained to
within ± 20 km, the
ascending node mean time
shall be maintained at 1:30
PM ± 15 min, and radial
orbit position repeatability
for a given latitude shall be
maintained to +10/-5 Km,
sun-synchronous and frozen
orbit conditions shall be
maintained
Response: Final parameters
24 hours prior to maneuver .
During contingency
operations, delivery of
parameters is required at
least 1 hour prior to the
maneuver. Delivery to the
EOC shall be as defined in
the FDS ICD.
Frequency: As needed
Reference: UTC
7220.3 FOT
Detailed Requirement Product
Mission Phase
FDS shall provide to
Orbit adjust
All
the EOC a maneuver
maneuver
report and plots of the
report and plot
predicted ground track
and ground track drift
rate, including
predictions with the
nominal burn modeled,
with no burn modeled,
and with a predicted
increase and/or
decrease in the nominal
predicted solar flux.
Performance
Requirement
Accuracy: Ground track
repeat shall be maintained to
within ± 20 Km, the
ascending node mean time
shall be maintained at 1:30
PM ± 15 min, and radial
orbit position repeatability
for a given latitude shall be
maintained to +10/-5 Km,
sun-synchronous and frozen
orbit conditions shall be
maintained
Response: Final parameters
24 hours prior to maneuver .
During contingency
operations, delivery of
parameters is required at
least 1 hour prior to the
maneuver. Delivery to the
EOC shall be as defined in
the FDS ICD.
Frequency: As needed
Reference: UTC
7220.4 FOT
Detailed Requirement
Product
Mission
Phase
FDS shall deliver to the
EOC a database trending
file of orbital parameters
calculated from definitive
orbit data including a
Orbital
parameters
database
All
Performance
Requirement
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
daily value for semimajor axis, eccentricity,
inclination, argument of
perigee (based on
Brouwer-Lyddane (J2)
theory), daily average
ground track error, mean
local time, and orbital
period.
the FDS ICD.
Frequency: Once per day
7220.5 FOT
Detailed Requirement
Product
Mission
Phase
FD shall support the
correction of launch
vehicle injection errors
after launch. FD shall also
support the placement of
the PM spacecraft to
avoid overlap of contacts
between PM, Terra, and
Landsat-7 spacecraft with
the EPGN stations. This
is required to minimize
contention for EPGN
resources including the
high-rate data link from
the EPGN to the EDOS
LZPF at GSFC.
N/A (FD
Launch
personnel will
work with
FOT during
launch.)
Performance
Requirement
N/A
7230.1 FOT
Detailed Requirement Product
Mission Phase
FDS shall provide
EOC a table of EOS
Aqua Omni antennae
to all operational
TDRSS viewing
entrance and exit times.
All
Table of all
operational
TDRSS
contact times
via Omni
antennae
Performance
Requirement
Time span: 7 week
7 day
Accuracy: 60 seconds after 3
weeks
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: 7 week – weekly
7 day - daily
Reference: UTC
7230.2 FOT
Detailed Requirement Product
FDS shall provide
EOC a table of EOS
Aqua Omni antennae
to specified ground
sites and maximum
elevation angle during
contact.
Mission Phase
Ground
All
station contact
times via
Omni
antennae
Performance
Requirement
Time span: 7 week
7 day
instrument campaign
locations - as needed
Accuracy: 60 seconds after
3-weeks
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: 7 week – weekly
7 day – daily
instrument campaign
locations - as needed
Reference: UTC, Ground
sites include EPGS, WGS,
Direct Access locations, and
instrument campaign
locations.
7230.3 FOT
Detailed Requirement Product
Mission Phase
FDS shall provide to
the EOC predicted
EOS Aqua range data
All
Range
Predicts
Performance
Requirement
Time Span: 1 day
for use in Return Data
Delay (RDD) time
correlation.
Accuracy: Best available
Response: Delivery to the
EOC shall be as defined in
the FDS ICD
Frequency: Daily
7230.4 WOTIS, NCC
Detailed Requirement Product
Mission Phase
FDS shall provide state Spacecraft
vectors to WOTIS and state vectors
NCC (acquisition
data).
All
Performance
Requirement
Accuracy: Best available
Response: Delivery shall be
as defined in the
EOC/WOTIS ICD and the
NCCDS/MOC ICD
Frequency: As defined in the
aforementioned ICDs
7300
Several of the FDS Support Products have accuracy requirements
of 1 second after 7 days. This requirement cannot be met to 3sigma certainty until approximately 1/2002 (using Schatten +2
sigma predicted solar flux values).
The accuracy of the FDS Support Products is limited by the
accuracy of the predicted ephemeris used in the product
generation. Knowledge of atmospheric density is necessary for the
production of the predicted ephemeris, but the uncertainty in the
atmospheric density model is proportional to the uncertainty in the
solar flux. Daily solar flux variations are larger during high flux
periods than when average solar flux values are low. Periods of
high average solar flux (which peak near the planned PM launch
date) result in greater uncertainty in the atmospheric model and
consequently, reduce the potential accuracy of the predicted
ephemeris.
FD orbit error analysis has shown that the three-sigma, along-track
uncertainty near the planned Aqua launch date is approximately 31
km at 7 days at flux = 200 solar flux units (sfu), the +2 sigma flux
prediction for this date. An along-track uncertainty of 31 km
corresponds to ~4 seconds of uncertainty in the FD products. The
FD products uncertainty is ~1 second at 4 days when sfu = 200.
The along-track and timing uncertainties at two other +2 sigma flux
values (150 and 100) were also analyzed (see table below) and the
corresponding mean flux values at these times are included.
Solar Flux
Solar Flux
Along Track Error
Along Track Error
Mean Value
+2 sigma
7-day, +2 sigma
4-day, +2 sigma
Date
(sfu)
(sfu)
Km (sec)
Km (sec)
12/2000
177
201
30.4 (4)
7.5 (1)
11/2001
139
150
9.3 (1.3)
5/2003
97
100
1.4 (0.2)
The following sections provide the FDS requirements for Aqua
planning products.
7300.1 AIRS, AMSU-A, CERES, HSB, MODIS
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted Solar
azimuth and elevation
angles in instrumenterdefined coordinate
frame at 30 second
intervals.
All
Solar azimuth
and elevation
angles vs.
time
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec after 7 days
Response: Delivery shall be
as defined in the FDS ICD
Frequency: 7 week – weekly
7 day - daily
2. MODIS, CERES
Detailed
Product
Requirement
Mission
Phase
Per
Req
FDS shall
provide the
EOC
predicted
Lunar
azimuth and
elevation
angles in
instrumenterdefined
coordinate
frame at 30
second
intervals.
Lunar
All
azimuth
and
elevation
angles
vs. time
Time Span: 7 week
7 day
Accuracy: 1 sec aft
Response: Delivery
as defined in the FD
Frequency: 7 week
7 day - daily
3. Spacecraft, FOT
Detailed
Product
Requirement
FDS shall
provide the
predicted
times of Solar
eclipse (lunar
occultation)
entrance/exit
times, along
with the
percent
shadow, and
maximum
shadow time.
4.
Mission
Phase
Solar eclipse All
penumbra
and umbra
entrance/exit
times,
percent
shadow, and
maximum
shadow time
of the
spacecraft
Time Span: 7 w
7 day
Accuracy: 2 mi
days
Response: Deli
as defined in th
Frequency: 7 w
7 day - daily
Reference: UTC
MODIS
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted Solar
eclipse (lunar
occultation)
entrance/exit times of
subsatellite point.
All
Solar eclipse
entrance/exit
times of
subsatellite
point
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: Best available
Response: Delivery shall be
as defined in the FDS ICD
Frequency: 7 week - weekly
7 day - daily
Reference: UTC
7300.5 AIRS, MODIS, CERES (will use MODIS contour,
information only), AMSR-E (information only – not a
requirement), FOT
Sample SAA Contour
Latitude
Longitude
-30
276
-12
276
-1.5
306
0
328
-13.5
354
-15.4
0
-26
34
-30
34
-30
0
-30
276
AIRS Preliminary SAA Contour
(provided by JPL)
Latitude
Longitude
-35
286
-40
289
-44
295
-47
310
-46
325
-25
15
-21
20
-17
15
-5
330
-5
320
-6
310
-12
300
-25
288
-30
286
-35
286
7300.5 (Continued)
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted
entrance and exit times
of the South Atlantic
Anomaly (SAA).
All
Entrance and
exit times to
the SAA
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec. after 7 days
Response: Delivery shall be
as defined in the FDS ICD
Frequency: 7 week – weekly
7 day - daily
Reference: UTC
6. CERES, MODIS, FOT
Detailed Requirement
Product Mission
Phase
FDS shall provide the EOC
predicted Solar beta angles at
the descending node.
Solar
beta
angles
vs. time
All
Tim
7d
Ac
Re
as
Fre
7d
Re
7. Thermal Engineers
Detailed
Product
Requirement
FDS shall
provide the
Sun vectorto-spacecraft
body and
Earth center
vector-tospacecraft
body angles.
Provide asflown data
points every
20 minutes
during
identified
orbits. Log
data points
against UTC
and identify
the orbit
number.
Mission Phase
Report
Testing/Simulations
containing
a table of
the object
vectors to
spacecraft
body
angles
8. MODIS, FOT, CERES
Launch/
Acquisition
Checkout
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted local
Sun time at the
ascending and
descending node.
All
Local Sun
time
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec.
after 7 days
Response: Delivery
shall be as defined in
the FDS ICD.
Frequency: 7 week –
weekly
7 day - daily
Reference: UTC
10. MODIS, CERES, FOT
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted
spacecraft day/night
transition times (umbra
entrance/exit).
All
Spacecraft
day/night
transition
times
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec.
after 7 days
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 day - daily
Reference: UTC
10. MODIS
Detailed Requirement Product
Mission Phase
Performance
Requirement
FDS shall provide the
EOC predicted Lunar
beta angles.
Lunar beta
angles
All
Time Span: 7 week
Accuracy: 1 sec.
(0.07 degrees) after 7
days
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: Weekly
Reference: UTC
7300.11 MODIS (same field of view as AM-1, do not need
azimuth/elevation angles), CERES (same field of view as
AM-1)
Detailed Requirement Product
FDS shall provide the
EOC predicted Sun
entrance/ exit times
and azimuth and
elevation angles into
instrument-defined
fields of view.
Mission Phase
Sun
All
entrance/exit
times, azimuth
and elevation
angles
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec after
7 days
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 days - daily
Reference: UTC
7300.12 MODIS (same field of view as AM-1), CERES (same field of view as
AM-1)
Detailed Requirement Product
Mission Phase
FDS shall provide the
All
Moon
Performance
Requirement
Time Span: 7 week
EOC predicted Moon
entrance/exit
entrance/exit times into times
instrument-defined
fields of view.
7 day
Accuracy: 1 sec after
7 days
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 days - daily
Reference: UTC
7300.13 MODIS
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted times
when Planets and
MODIS-specified stars
are within 10 degrees
of the Moon while the
Moon is in specified
instrument field of
view.
All
Moon/
Planet/Star
visibility
times
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec after
7 days
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 day - daily
Reference: UTC
7300.14 MODIS, CERES
Detailed Requirement Product
Mission Phase
FDS shall provide the
Sub-satellite
EOC predicted subpoint latitude
satellite point longitude and longitude
All
Performance
Requirement
Time Span: 7 week
7 day
and latitude at 1 minute
intervals.
Accuracy: 0.005 deg
(~625 meters along
track) at 40 hrs at
equator for latitude
=0.0009 deg (~110
meters cross track) at
40 hrs at equator for
longitude
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 day - daily
Reference: UTC
7300.15 MODIS, FOT, CERES
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted
spacecraft altitude at 1
minute intervals.
All
Spacecraft
altitude
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 30 meters
after 40 hours
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 day - daily
Reference: UTC
7300.16 MODIS, CERES, FOT
Detailed Requirement Product
Mission Phase
Performance
Requirement
FDS shall provide the
EOC predicted
ascending and
descending node
crossing times,
longitude at node
crossing and orbit
number.
Node crossing
All
Times,
location and
orbit number
Time Span: 7 week
7 day
Accuracy: 1 sec.
after 7 days, 0.01
degree (~1025
meters cross track) in
longitude after 7
days, 0.04 sec. (~300
meters along track)
after 40 hours,
0.0009 degree (~110
meters cross track) in
longitude after 40
hours
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week weekly
7 day - daily
Reference: UTC
18. AIRS (needed for post-processing only)
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted user
line of sight terminator
crossing times.
All
User line of
sight
terminator
crossing times
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec.
after 7 days, 0.04 sec
over 48 hours
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 day - daily
Reference: UTC
7300.18 MODIS, FOT
Detailed Requirement Product
FDS shall provide the
EOC predicted length
of spacecraft day and
night (based on
umbra).
Mission Phase
Spacecraft day All
and night
duration
Performance Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec.
after 7 days
Response: Delivery
shall be as defined in
the FDS ICD
Frequency: 7 week –
weekly
7 day - daily
Reference: UTC
19. MODIS, CERES, FOT
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted time of
spacecraft noon.
All
Time of
spacecraft
noon
Performance
Requirement
Time Span: 7 week
Accuracy: 1 sec. after 7 days
Response: Delivery shall be
as defined in the FDS ICD
Frequency: Weekly
Reference: UTC
7300.20 MODIS, CERES, AMSR-E
Detailed Requirement Product
Mission Phase
Performance
Requirement
FDS shall provide the
EOC predicted
crossing times of
maximum and
minimum latitudes and
path number.
Max and Min
latitude times
and path
number
All
Time Span: 7 week
7 day
Accuracy: 1 sec. after 7
days, 0.04 sec. (~300
meters) after 40 hours
Response: Delivery shall be
as defined in the FDS ICD
Frequency: 7 week – weekly
7 day - daily
Reference: UTC
7300.21 MODIS, CERES
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC predicted nadir
terminator crossing
times. The direction of
the terminator crossing
(day/night or
night/day) will be
indicated.
All
Predicted
nadir
terminator
crossing times
Performance
Requirement
Time Span: 7 week
7 day
Accuracy: 1 sec. after 7
days, 0.04 sec. (~300
meters) after 40 hours
Response: Delivery shall be
as defined in the FDS ICD
Frequency: 7 week – weekly
7 day – daily
Reference: UTC
7300.22 AIRS, MODIS
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC actual nadir
terminator crossing
All
Actual nadir
terminator
crossing times
Performance
Requirement
Time Span: 48 hours
Accuracy: Capable of 0.04
times. The direction of
the terminator crossing
(day/night or
night/day) will be
indicated.
sec. over 48 hours
Response: Delivery shall be
as defined in the FDS ICD
Frequency: Daily
Reference: UTC
24. MODIS, AMSR-E
Detailed Requirement Product
Mission Phase
FDS shall provide the
EOC with viewing
entry/exit times for the
instrument field-ofview (FOV) of the
specified instrument
field campaign sites.
All
Campaign
sites FOV
entry/exit
times
Performance
Requirement
Time Span: Up to 7 weeks
Accuracy: 60 sec. after 3
weeks
Response: Delivery shall be
as defined in the FDS ICD
Frequency: As needed
Reference: UTC
8000
The Flight Software (FSW) Maintenance Team (FMT) will provide FSW
maintenance services, products, and expertise in support and use of on-board
flight software. The FMT will develop capabilities and expertise to perform flight
software support functions and will assist the FOT to ensure on-going health and
function of the observatory. The FMT will maintain and improve the quality of the
flight software and assist the flight team in correct usage. The FMT uses the
IVVF to develop the products that they provide to the EOC. The IVVF will be
provided to the FMT by the spacecraft contractor.
More specific functions of the FMT include:
· Investigate, analyze, and resolve flight software problems.
· Develop patch loading capabilities and expertise.
· Support simulations and spacecraft to ground system interoperability
testing.
· Provide training to the FOT on the 1750A on-board processor and flight
software tools.
· Establish a library of pertinent flight software documents.
· Initiate and maintain an observatory flight software maintenance history.
· Establish a configuration management information tracking system.
· Establish a software data transfer capability with the EOC.
· Enhance simulators to model changes in observatory hardware and add
capabilities that enable test of flight software.
8000.1
The FMT shall use the IVVF to provide the capability to
manage Spacecraft Flight Software Memory Loads.
8000.1.1
The FMT shall create spacecraft flight software memory
loads and provide them to the EOC in the load module
format.
8000.1.2
The FMT shall create and provide flight software code
patches to the EOC in a load module format.
8000.1.3
The FMT shall create and provide TMONs to the EOC in a
load module format.
8000.1.4
The FMT shall create and provide Format Tables/Packet
Lists to EOC in load module format.
8000.1.5
The FMT shall create and provide Hardware Data
Acquisition (HDA) tables to the EOC in a load module
format.
8000.1.6
The FMT shall create and provide the BST Transaction
Table to the EOC in a load module format.
8000.2
The FMT shall use the IVVF to provide the capability to
manage Stored Command Sequences (SCS) and
Predefined Defined Scripts (PCS). This includes:
8000.2.1
The FMT shall create and provide SCSs and PCSs to the
EOC in a load module format.
8000.3
The FMT shall use the IVVF to generate and provide the
ADA Mapping Table to the EOC.
8000.4
The FMT shall use the IST to retrieve memory dump data from the EOC.
9000
The following sections provide the mission-specific requirements for the EOSDIS
Core System (ECS) Distributed Active Archive Centers (DAAC) and the Langley
Research Center (LaRC) Tropical Rainfall Measurement Mission (TRMM)
Information System. (LaTIS). The DAAC s involved in the Aqua mission are the
GSFC DAAC, the National Snow and Ice Data Center (NSIDC) DAAC, the EROS
Data Center (EDC) DAAC and the LaRC DAAC.
9100.1
ECS at the GSFC DAAC shall perform the principal functions
of ingesting, archiving and distributing MODIS and AIRS
instrument suite (includes the AIRS, AMSU, and HSB
instruments) Level 0 data from EDOS.
9100.2
ECS at the GSFC DAAC shall generate, archive and
distribute MODIS Level 1 data products and a limited set of
Level 2 and Level 3 products and provide these products to
MODAPS for higher-level processing.
9100.3
ECS at the GSFC DAAC shall generate, archive, and
distribute AIRS instrument suite Level 1 and higher data
products.
9100.4
ECS at the GSFC DAAC shall perform the principal functions
of ingesting, archiving and distributing MODIS higher-level
ocean and atmospheric data from MODAPS (including
metadata, browse data, and associated correlative data as
appropriate).
9100.5
ECS at the GSFC DAAC shall provide data to the MODIS
SCFs and receive QA metadata updates from the MODIS
SCFs and QA Facilities.
9100.6
ECS at the GSFC DAAC shall perform ingest and archive of
the EMOS-generated carryout files (i.e., spacecraft
housekeeping carryout files for MODIS and AIRS and
attitude carryout files) and history data, and provide the
appropriate history data back to EMOS upon EMOS request.
9100.7
ECS at the GSFC DAAC shall ingest and archive definitive
orbit, and predicted orbit data from the FDS.
9100.8
ECS at the GSFC DAAC shall data preprocess (DPREP)
orbit data (i.e., definitive orbit or predicted orbit data from
FDS), and attitude carryout files from EMOS into a form
usable by the science software.
9100.9
ECS at the GSFC DAAC shall provide data to the AIRS
SCFs and receive QA metadata updates from the AIRS
SCFs.
9200.1
ECS at the NSIDC DAAC shall perform the principal
functions of ingesting, archiving and distributing AMSR-E
Level 0 science data and associated Ground Based Attitude
Determination (GBAD) data from EDOS.
9200.2
ECS at the NSIDC DAAC shall perform the principal
functions of ingesting, archiving, and distributing MODIS
higher-level snow and sea ice data from MODAPS (including
metadata, browse data, and associated correlative data as
appropriate).
9200.3
ECS at the NSIDC DAAC shall perform the principal
functions of ingesting, archiving, and distributing AMSR-E
Level 1A data (including metadata) from the JPL PO DAAC.
9200.4
ECS at the NSIDC DAAC shall perform the principal
functions of ingesting, archiving, and distributing AMSR-E
Level 2 and Level 3 data (including metadata, browse data,
and associated correlative data as appropriate) from the
AMSR-E SIPS at MSFC GHCC.
9200.5
ECS at the NSIDC DAAC shall provide data to and receive
QA metadata updates from the AMSR-E SIPS at MSFC
GHCC.
9200.6
ECS at the NSIDC DAAC shall provide data to the MODIS
SCFs and receive QA metadata updates from the MODIS
QA Facility.
9200.7
ECS at the NSIDC DAAC shall provide all L0 AMSR-E
science and GBAD data to NASDA for the first 90 days of
the mission only, and shall serve as a backup for these data
after the first 90 days.
9300.1
ECS at the EDC DAAC shall perform the principal functions
of ingesting, archiving and distributing MODIS higher-level
land data from MODAPS (including metadata, browse data,
and associated correlative data as appropriate).
9300.2
ECS at the EDC DAAC shall provide data to the MODIS
SCFs and receive QA metadata updates from the MODIS
QA Facility.
9400.1
ECS at the LaRC DAAC shall ingest and archive definitive
orbit, and predicted orbit data from the FDS.
9400.2
ECS at the LaRC DAAC shall data preprocess (DPREP)
orbit data (i.e., definitive orbit or predicted orbit data from
FDS), and attitude carryout files from EMOS into a form
usable by the science software.
9400.3
ECS at the LaRC DAAC shall provide the output of DPREP
to LaTIS.
9400.4
ECS at the LaRC DAAC shall perform ingest and archive of
the EMOS generated attitude carryout files.
9500.1
LaTIS at the LaRC DAAC shall perform the principal
functions of ingesting, archiving and distributing CERES
Level 0 data from EDOS.
9500.2
LaTIS at the LaRC DAAC shall generate, archive, and
distribute CERES Level 1 and higher data products.
9500.3
LaTIS shall ingest Data Pre-Processing (DPREP) output
from the LaRC DAAC.
9600.1
ECS shall support Aqua pre-launch testing activities such as
operational readiness testing and simulations at all DAACs.
9600.2
ECS shall support Aqua operations and testing concurrently
at all DAACs while simultaneously supporting Landsat-7,
ACRIM, and Terra operations and system upgrades.
9600.3
ECS at all DAAC sites shall support a rolling archive strategy
for Aqua data whose size is based on the following
assumptions: Level 1A data is to be deleted 6 months after
processing to Level 1B, Level 1B data is to be deleted 6
months after reprocessing, Level 2 data is to be deleted 6
months after processing to L3, L3 data is to be deleted 6
months after reprocessing.
9600.4
ECS shall support 2-way interoperability with the EOS Data
Gateway (EDG) at all DAACs and LaTIS.