ICES-401-SPEC-002

Version 2.0

Revision Date: 9-1-99

\`

DRAFT

**Mission Operations Requirements DOCUMENT (MORD)**

**FOR THE**

**ICE, CLOUD & LAND ELEVATION SATELLITE (ICESat)**

Goddard Space Flight Center

Greenbelt, Maryland 20771

Prepared by:

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Edward Chang ICESat System Operations Manager

Reviewed by:

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Michael Tasevoli,

Mission Systems Engineer

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

William Anselm

Observatory Manager

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

David Hancock

Science Computing Facility Manager

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Alan Johns

ESDIS Mission Systems Manager

Approved by:

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Joe Dezio,

ICESat Project Manager

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Dolly Perkins,

ESDIS Project Manager

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Bob Schutz,

Science Team Leader

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Jay Zwally

Project Scientist

1\. Introduction [1](#introduction)

1.1 Purpose [1](#purpose)

1.2 Document Control [1](#document-control)

1.3 Scope [1](#scope)

1.4 Document Approach [1](#document-approach)

1.5 Applicable Documents [2](#applicable-documents)

2\. Mission Level Requirements [3](#mission-level-requirements)

2.1 Mission Phases [3](#mission-phases)

2.2 Mission Data Flow [4](#mission-data-flow)

2.3 Mission Operations Documentation
[6](#mission-operations-documentation)

2.4 Major Reviews [9](#major-reviews)

2.5 Mission Operations Development Support
[10](#mission-operations-development-support)

2.6 Acceptance and Transition Roles and Responsibilities
[10](#acceptance-and-transition-roles-and-responsibilities)

3\. EOS Polar Ground Stations [11](#eos-polar-ground-stations)

3.1 Interface Standards [11](#interface-standards)

3.2 Baseline Ground Station Contact Scenario
[11](#baseline-ground-station-contact-scenario)

3.3 Emergency Commanding [12](#emergency-commanding)

3.4 Wallops Flight Facility Ground Network Scheduling System
[12](#wallops-flight-facility-ground-network-scheduling-system)

3.5 Doppler Ranging [13](#doppler-ranging)

3.6 S-band Command & Telemetry Command Processing
[13](#s-band-command-telemetry-command-processing)

3.7 Compatibility Test Van Support [14](#compatibility-test-van-support)

3.8 Communications Links Testing [14](#communications-links-testing)

4\. Ground Communications [15](#ground-communications)

4.1 Mission Operations System Communications
[15](#mission-operations-system-communications)

4.2 Launch Pad Communications with the MOC
[15](#__RefHeading___Toc460824700)

4.3 Science Distribution Communications
[15](#science-distribution-communications)

4.4 Communications Testing [15](#communications-testing)

5\. Mission Operations Center [16](#mission-operations-center)

5.1 Mission Communications Support Profile
[16](#mission-communications-support-profile)

5.2 Major Interfaces [16](#major-interfaces)

5.3 Flight Systems [17](#flight-systems)

5.4 Facility [17](#__RefHeading___Toc460824707)

5.5 Operational Coverage [17](#operational-coverage)

5.6 Database Compatibility [18](#database-compatibility)

5.7 Planning and Scheduling [18](#planning-and-scheduling)

5.8 Real-time Observatory Telemetry Monitoring
[18](#real-time-observatory-telemetry-monitoring)

5.9 Trending Analysis [18](#trending-analysis)

5.10 Observatory Commanding [18](#observatory-commanding)

5.11 Remote Monitoring Terminal [18](#remote-monitoring-terminal)

5.12 Sustaining Engineering [19](#sustaining-engineering)

5.13 Anomaly Resolution [19](#anomaly-resolution)

5.14 MOC Data Archive [19](#moc-data-archive)

5.15 Laser Flight Safety Operations
[19](#laser-flight-safety-operations)

5.16 Flight Operations Team [19](#flight-operations-team)

5.17 Reliability [20](#reliability)

5.18 Security [20](#security)

5.19 Observatory Integration and Testing Support
[21](#observatory-integration-and-testing-support)

5.20 Documentation [21](#documentation)

5.21 Reviews and Status Reporting [21](#reviews-and-status-reporting)

6\. Flight Dynamics System [23](#flight-dynamics-system)

6.1 CSOCProvided Flight Dynamics Services (MMFD)
[23](#__RefHeading___Toc460824726)

6.2 Mission Characteristics [23](#__RefHeading___Toc460824727)

6.3 BASD Provided FDS [24](#__RefHeading___Toc460824728)

6.3.1 The following data shall be ingested for use by the FDS.
[24](#__RefHeading___Toc460824729)

6.3.2 The data processing performance for the following data shall be:
[24](#__RefHeading___Toc460824730)

6.3.3 The following data product shall be generated with the following
frequency: [24](#__RefHeading___Toc460824731)

6.4 Software, Hardware, Personnel, and Facilities
[25](#software-hardware-personnel-and-facilities)

6.5 Mission Phases Support [25](#mission-phases-support)

6.5.1 Maneuver Constraints [25](#maneuver-constraints)

6.5.2 Pre-Launch Phase [25](#pre-launch-phase)

6.5.3 Check-out Period Phase [25](#check-out-period-phase)

6.5.4 Calibration and Validation Phase
[26](#calibration-and-validation-phase)

6.5.5 Maneuver Planning [26](#maneuver-planning)

6.5.6 Ground-Track Monitoring and Prediction:
[26](#ground-track-monitoring-and-prediction)

6.5.7 Mission Planning Support [26](#mission-planning-support)

6.6 Orbit & Attitude Determination [27](#orbit-attitude-determination)

6.6.1 Operational Orbit Determination
[27](#operational-orbit-determination)

6.6.2 Operational Attitude Support [27](#operational-attitude-support)

6.7 Sensor Support [27](#sensor-support)

6.7.1 Sensor Uploadable Parameters Support
[27](#sensor-uploadable-parameters-support)

6.7.2 Sensor Calibration Support [28](#sensor-calibration-support)

6.8 Products Exchange [28](#products-exchange)

6.8.1 FDS Products to the Mission Operations Center
[28](#fds-products-to-the-mission-operations-center)

6.8.2 MOC Products to the Flight Dynamics System
[28](#moc-products-to-the-flight-dynamics-system)

6.8.3 Flight Dynamics Products to the Science Team
[28](#flight-dynamics-products-to-the-science-team)

6.8.4 Data and Products Archive [29](#data-and-products-archive)

7\. Instrument Support Facility [30](#instrument-support-facility)

7.1 Instrument Flight Systems [30](#instrument-flight-systems)

7.2 Facility [30](#facility)

7.3 Operational Coverage [30](#operational-coverage-1)

7.4 Planning and Scheduling [30](#planning-and-scheduling-1)

7.5 Instrument Operations, Maintenance and Calibration
[30](#__RefHeading___Toc460824757)

7.5.1 ISF shall provide periodic uploads for the following GLAS
subsystems: [30](#__RefHeading___Toc460824758)

7.5.2 The ISF shall participate in the following calibration activities
with support from BASD and science operations:
[30](#__RefHeading___Toc460824759)

7.6 Trending Analysis [31](#trending-analysis-1)

7.7 Sustaining Engineering [31](#sustaining-engineering-1)

7.8 Anomaly Resolution [31](#anomaly-resolution-1)

7.9 Instrument Operations Team [31](#instrument-operations-team)

EDOS [33](#__RefHeading___Toc460824764)

8.1 General Level Zero Data Processing Functions
[33](#general-level-zero-data-processing-functions)

8.2 EDOS ICESat Mission Performance Reqirements
[34](#edos-icesat-mission-performance-reqirements)

8.3 Data Products Latency Requirements
[35](#data-products-latency-requirements)

9\. ISIP [36](#__RefHeading___Toc460824768)

10\. Science Data Archival & Distribution
[37](#science-data-archival-distribution)

11\. ESDIS Integration and Test. [38](#__RefHeading___Toc460824770)

ESDIS Project shall be responsible for integrating EBNet, EDOS, EDOS and
NSIDC DAAC in support of the ICESat mission.
[38](#__RefHeading___Toc460824771)

BASD Sustaining Engineering Requirements
[40](#__RefHeading___Toc460824772)

12.1 Engineering Data Archive [40](#engineering-data-archive)

12.2 Integration & Testing Activities
[40](#integration-testing-activities)

12.3 Sustaining Engineering Support
[40](#sustaining-engineering-support)

12.3.1 Anomaly Resolution [40](#anomaly-resolution-2)

12.3.2 Trending & Analysis [40](#trending-analysis-2)

12.3.3 Software Maintenance [41](#software-maintenance)

12.3.4 Maintain Flight Software Test Bed
[41](#maintain-flight-software-test-bed)

13\. GLAS Instrument Developer Requirements
[42](#glas-instrument-developer-requirements)

13.1 Instrument Operations Training
[42](#instrument-operations-training)

13.2 Documentation [42](#documentation-1)

13.3 Integration & Testing Activities
[42](#integration-testing-activities-1)

13.4 On-Orbit Check-out & Transition Activities
[42](#on-orbit-check-out-transition-activities)

13.5 Calibration and Validation Support
[42](#calibration-and-validation-support)

13.6 Engineering Data Archive [43](#engineering-data-archive-1)

13.7 Instrument Sustaining Engineering
[43](#instrument-sustaining-engineering)

13.7.1 Anomaly Resolution Support [43](#anomaly-resolution-support)

13.7.2 Trending & Analysis [43](#trending-analysis-3)

13.7.3 Software Maintenance [43](#software-maintenance-1)

14\. Science Team Requirements [44](#science-team-requirements)

15\. Appendix [45](#__RefHeading___Toc460824792)

# Introduction

This is the Mission Operations Requirements Document (MORD) for the

Ice, Cloud, & Land Elevation Satellite (ICESat). This section discusses
the purpose, scope, and applicable documents of this document.

## Purpose

This MORD is derived from the ICESat Mission Systems Requirements
Document, February, 1998. It completes the Ground System Requirements of
the Requirements Document Hierarchy, Figure 1, page 1, in terms of
mission operations and ground system requirements.

## Document Control

This MORD is maintained under the Configuration Management System of the
ICESat Project Office.

The latest version of this document shall be available under the Project
Implementation/Virtual CM/Documents section of the ICESat Homepage at
URL: http://icesat.gsfc.nasa.gov/

Contacts for changes & comments:

Edward Chang, ICESat System Operations Manager

PHONE: 301-286-6964 EMAIL: edward.chang@gsfc.nasa.gov

Mike Tasevoli, ICESat System Engineer

PHONE: 301-286-2321

EMAIL: Michael.Tasevoli.1@gsfc.nasa.gov

## Scope

This MORD details the project-level ICESat mission operations and ground
system requirements and is the governing document for the ICESat mission
operational development. This is the controlling document for mission
operations and ground system requirements, as well as the operational
interactions and agreements required between the major mission elements.

The information in this document encompasses the mission level
end-to-end operational requirements and implementation plans and
agreements considered necessary to achieve the ICESat mission
operationally. Lower level requirements shall be derived from these
requirements by each respective mission element.

## Document Approach

To minimize documentation, this MORD includes requirements for GSFC
institutional support traditionally covered in separate documents.
Hence, this document replaces the Detailed Mission Requirements (DMR)
document. In response to this document, the ICESat project shall expect
detailed ground system requirements to be derived, documented, and
flowed down to the respective subsystems by the organization to which
the requirements have been allocated. The detailed listing of ICESat
Operations documents is found in Section 2.3.

## 

##  

## 

  ------- -------------------------------- --------------- ---------------
                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           

                                                           
  ------- -------------------------------- --------------- ---------------

## Applicable Documents

The following are applicable documents to the MORD:

1.  ICESat Mission Systems Requirements Document, 2/98.

2.  Ground System Interface Control Document; Data, 12/10/98.

3.  Ground System Interface Control Document; Radio Frequency, 4/99,

4.  Operations Handbook for the ICESat Observatory.

5.  EOSDIS Architecture Description Document (latest version on WWW).

6.  GLAS Instrument Description Document

7.  GLAS I-SIPS Software Architectural Design Document, October, 1998
    (Version 2.0)

8.  GLAS Science Computing Facility (SCF) Plan, February, 1998 (Version
    0.4)

# Mission Level Requirements

## Mission Phases

The following flow chart describes the major ICESat Mission Phases that
shall be supported.

![](media/image1.wmf)

A description of each mission phase follows:

Development Phase -- the development and fabrication phases of each key
mission element (GLAS, BUS, IGS, and SCF/SIPS)

Integration & Test Phase -- the I&T of each of the major mission
elements as stand-alone elements, followed by a series of integration
and test between the various mission elements. This phase culminates in
a series of ICESat System End-to-End Check-out tests, including
end-to-end data flow tests, simulations, and dress rehearsals.

Launch Phase -- these are all activities from packaging and shipment of
the Observatory through launch and orbit insertion of the Observatory.

Spacecraft Bus Check-out Phase -- this is the time period from launch
through acceptance of the observatory from BASD by the Government. This
phase includes the activation and check-out of the spacecraft's
subsystems. This phase is expected to last \~ L + 30 days.

Instrument Check-out phase -- this phase coincides with the Bus
Check-Out Phase and includes activation and check-out of the GLAS
instrument's subsystems. This phase begins \~ L + 5 days, immediately
after key Spacecraft Bus subsystems have been activate and expect to
complete \~ L+ TBD days.

Transition to Operations Phase -- this phase also coincides with the
Spacecraft and Instrument Check-out Phases and culminates with
transitioning flight operations control from BASD to the flight
operations team \~ L + 30 days.

Calibration & Validation Phase -- this phase covers the time period from
\~ L + 30 days to \~ L+ 150 days and includes the calibration and
validation of the GLAS instrument's subsystems and measurements.

Nominal Science Phase -- this is the operations phase of the ICESat
mission beginning \~ L + 150 days. Normal operations includes activities
such as orbit determination and maneuver planning/execution and GLAS
data acquisition. Contingency operations includes operational responses
to any anomalies that may occur. Platform Disposal Phase -- this phases
begins when the Observatory's expendable resources have been depleted
(L + 5 years). Note that the ICESat space segment has been designed for
3 years of operations with a goal of 5 years. Analysis indicates that
the Observatory is expected to naturally reenter the earth's atmosphere
within 25 years after EOL (\~ L + 30 years).

## Mission Data Flow

The following architecture diagram defines the top-level data flow to be
supported by each of the ground system elements.

![](media/image20.wmf)

## Mission Operations Documentation

Mission operations documentation is defined as those documents that are
required to define, build, test, operate, and maintain the ICESat ground
systems. Table 2.3.1 lists key documents and other media-based
deliverables that are critical to the ICESat mission operations
development. Some names and contents of documents are expected to change
based on each element's unique documentation system currently in place
and these will be negotiated and documented as an update to this
document. However, the intent, as is evident by the title of each
document, shall be retained.

Table 2.3.1

+----+----------------------------+------+---------+-----------------+
| *  | **Mission Operations**     | **   | *       | **C             |
| *I | **Document Title**         | Sour | *Actual | omments/Trace** |
| GS |                            | ce** | DOC     |                 |
| D  |                            |      | \#**    |                 |
| oc |                            |      |         |                 |
| \# |                            |      | **C     |                 |
| ** |                            |      | onsider |                 |
|    |                            |      | TBD for |                 |
|    |                            |      | all     |                 |
|    |                            |      | un-n    |                 |
|    |                            |      | umbered |                 |
|    |                            |      | docu    |                 |
|    |                            |      | ments** |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | IGS Master Schedule        | All  |         | IGS Requirement |
| 01 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | IGS Test Plan              | Pro  |         | Overall Test    |
| 02 |                            | ject |         | Plan for all    |
|    |                            |      |         | IGS elements    |
+----+----------------------------+------+---------+-----------------+
| 2. | Mission System             | Pro  |         |                 |
| 03 | Requirements Document for  | ject |         |                 |
|    | ICESat Mission             |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | Mission Operations         | Pro  | ICE     |                 |
| 04 | Requirements Document      | ject | S-401-S |                 |
|    | (MORD) for ICESat,         |      | PEC-002 |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | Observatory Launch Site    | Ball |         | RSA CDRL 11     |
| 05 | Operations and Test Plan   |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | Spacecraft Observatory     | Ball |         | RSA CDRL 6      |
| 06 | Integration and Test Plan  |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | GLAS Instrument Laser      | 924  | GLA     |                 |
| 07 | Safety Analysis 11/1/98    |      | S-924-A |                 |
|    |                            |      | NYS-001 |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | Environmental Assessment   | Pro  |         |                 |
| 08 |                            | ject |         |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | ICESat Mission Operations  | Pro  |         |                 |
| 09 | Concept Document           | ject |         |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | Project Support Level      | Pro  |         |                 |
| 10 | Agreement (PSLA)           | ject |         |                 |
+----+----------------------------+------+---------+-----------------+
| 2. | MOC/FOT/FDS Procurement    | Pro  |         | MOC             |
| 11 | Package to SOMO/CSOC       | ject |         | requirements to |
|    |                            |      |         | SOMO            |
+----+----------------------------+------+---------+-----------------+
| 3. | Ground System Interface    | Ball |         | RSA CDRL 5B,    |
| 01 | Control Document; Data     |      |         | See ICD \# 1 in |
|    |                            |      |         | IGS             |
|    |                            |      |         | Architecture    |
+----+----------------------------+------+---------+-----------------+
| 3. | RF ICD between the ICESat  | Ball |         | RSA CDRL 5A,    |
| 02 | Spacecraft and the EPGS    |      |         | See ICD \# 1 in |
|    |                            |      |         | IGS             |
|    |                            |      |         | Architecture    |
+----+----------------------------+------+---------+-----------------+
| 3. | Network Operations Support | 450  |         | Similar         |
| 03 | Plan for the ICESat        |      |         | approach used   |
|    | Mission                    |      |         | for QuikSCAT    |
|    |                            |      |         | doc             |
+----+----------------------------+------+---------+-----------------+
| 3. | IGS CTV Support Plan       | 450  |         | Similar         |
| 04 |                            |      |         | approach used   |
|    |                            |      |         | for QuikSCAT    |
+----+----------------------------+------+---------+-----------------+
| 3. | EPGS IGS Design Spec & Ops | 450  |         |                 |
| 05 | Plan                       |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 3. | EPGS/WFF Test Plan         | 450  |         |                 |
| 06 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 4. | IGS Security Plan          | 423  |         |                 |
| 01 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 4. | IGS Ebnet/NISN ICDs        | 423  |         |                 |
| 02 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 4. | Ebnet/NISN Test Plan       | 423  |         |                 |
| 03 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 5. | ICESat T&C Handbook        | Ball |         | RSA CDRL 5A     |
| 01 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 5. | Spacecrat Operations       | Ball |         | RSA CDRL 8      |
| 02 | Description Manual for the |      |         |                 |
|    | ICESat Observatory         |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 5. | Mission Requirements       | Ball |         | RSA CDRL 18     |
| 03 | Document                   |      |         | (Mission        |
|    |                            |      |         | requirements    |
|    |                            |      |         | document for    |
|    |                            |      |         | the spacecraft  |
|    |                            |      |         | & ground system |
+----+----------------------------+------+---------+-----------------+
| 5. | Spacecraft Operations      | Ball |         | RSA CDRL 10     |
| 04 | Handbook for the ICESat    |      |         |                 |
|    | Observatory                |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 5. | MOC External Interfaces    | LASP |         | Similar         |
| 05 | ICD                        |      |         | approach used   |
|    |                            |      |         | for QuikScat    |
|    |                            |      |         | MOC ICD. See    |
|    |                            |      |         | ICD \# 9 in IGS |
|    |                            |      |         | Architecture    |
+----+----------------------------+------+---------+-----------------+
| 5. | Detailed MOC Requirements  | LASP |         | Include MOC     |
| 06 | & Design Document          |      |         | Design,         |
|    |                            |      |         | Staffing        |
|    |                            |      |         | &Training       |
|    |                            |      |         | Plans, Facility |
|    |                            |      |         | Plans           |
+----+----------------------------+------+---------+-----------------+
| 5. | MOC Operations Concept     | LASP |         |                 |
| 07 | Document (MOCD)            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 5. | MOC Flight Operations      | LASP |         | Detailed        |
| 08 | Procedures                 |      |         | Operations      |
|    |                            |      |         | Procedures and  |
|    |                            |      |         | Contingencies   |
+----+----------------------------+------+---------+-----------------+
| 5. | MOC Operational Agreements | LASP |         |                 |
| 09 | with FDS, IOT, ST, and     |      |         |                 |
|    | other mission elements     |      |         |                 |
|    | (EPGS, WFF, etc.).         |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 5. | MOC Test Plan              | LASP |         |                 |
| 10 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 5. | Spacecraft Database        | Ball |         |                 |
| 11 | (Electronic)               |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 6. | FDS Detailed Requirements  | B    |         | FDS design,     |
| 01 | and Design Specification.  | all/ |         | staffing,       |
|    |                            | LASP |         | facilities,     |
|    |                            |      |         | etc.            |
+----+----------------------------+------+---------+-----------------+
| 6. | FDS Operations Procedures  | B    |         |                 |
| 02 | Handbook.                  | all/ |         |                 |
|    |                            | LASP |         |                 |
+----+----------------------------+------+---------+-----------------+
| 6. | FDS Test Plan (FDSTP).     | B    |         |                 |
| 03 |                            | all/ |         |                 |
|    |                            | LASP |         |                 |
+----+----------------------------+------+---------+-----------------+
| 6. | FDS Operational Agreements | B    |         |                 |
| 04 | with FOT, IOT, ST, and     | all/ |         |                 |
|    | other mission elements     | LASP |         |                 |
|    | (EPGS, WFF, etc.).         |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 6. | Flight Dynamics External   | B    |         | Serves as       |
| 05 | Interfaces ICD             | all/ |         | response to     |
|    |                            | LASP |         | MORD. See ICD   |
|    |                            |      |         | \# 7 in IGS     |
|    |                            |      |         | Architecture    |
+----+----------------------------+------+---------+-----------------+
| 7. | GLAS Instrument Support    | ISF  |         | See ICD \# 8 in |
| 10 | Facility (GISF) External   |      |         | IGS             |
|    | Interfaces ICD             |      |         | Architecture    |
+----+----------------------------+------+---------+-----------------+
| 7. | GLAS Operations Agreements | ISF  |         |                 |
| 20 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 7. | GLAS Database (Electronic  | GSEF |         | GLAS Database   |
| 30 |                            |      |         | for MOC         |
+----+----------------------------+------+---------+-----------------+
| 8. | ICD Between EDOS and EGS   | EDOS |         | See ICD #2.     |
| 01 | Elements (Appendix to      |      |         | This is EDOS    |
|    | address ICESat Specifics)  |      |         | CDRL B301.      |
|    |                            |      |         | Replaces 5.10   |
|    |                            |      |         | and 9.01        |
+----+----------------------------+------+---------+-----------------+
| 8. | EDOS Detailed Design       | EDOS |         |                 |
| 02 | Specification              |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 8. | EDOS Test Plan             | EDOS |         |                 |
| 03 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
|    |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 9. | GLAS ISIPS ICD (Appendix   | SCF  |         | See ICD \# 5 in |
| 02 | to existing generic ISIPS  |      |         | IGS             |
|    | ICD)                       |      |         | Architecture    |
+----+----------------------------+------+---------+-----------------+
| 9. | GLAS ISIPS Softward        | SCF  |         |                 |
| 03 | Architecture Design        |      |         |                 |
|    | Document                   |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 9. | ICD between ISIPS/IST and  | SCF  |         | See ICD \# 6 in |
| 04 | CSR                        |      |         | IGS             |
|    |                            |      |         | Architecture.   |
|    |                            |      |         | Internal ICD to |
|    |                            |      |         | ISIPS/SCF.      |
+----+----------------------------+------+---------+-----------------+
| 9. | GLAS Level 0 Instrument    | SCF  |         |                 |
| 05 | Data Product Specification |      |         |                 |
|    | Ver 2.2                    |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 9. | GLAS Level 0 Instrument    | SCF  |         |                 |
| 06 | Data Products              |      |         |                 |
|    | Specification Level 1 Ver  |      |         |                 |
|    | 1.2                        |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 9. | GLAS Standard Data         | SCF  |         |                 |
| 07 | Products Specification     |      |         |                 |
|    | Level 2 Ver 1.2            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | DAAC Design Document       | DAAC |         |                 |
| 0. |                            |      |         |                 |
| 01 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | DAAC Test Plan             | DAAC |         |                 |
| 0. |                            |      |         |                 |
| 02 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | User Guide for GLAS Data   | N    |         |                 |
| 0. | (Describes how users       | SIDC |         |                 |
| 03 | access GLAS data from      |      |         |                 |
|    | NSIDS                      |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | Spacecraft Engineering     | Ball |         |                 |
| 1. | Data Archive               |      |         |                 |
| 01 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | Spacecraft Sustaining      | Ball |         |                 |
| 1. | Engineering Support Plan   |      |         |                 |
| 02 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | Spacecraft Flight Software | Ball |         |                 |
| 1. | Maintenance Support Plan   |      |         |                 |
| 03 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | Spacecraft Simulator       | Ball |         |                 |
| 1. | User\'s Manual             |      |         |                 |
| 03 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | Spacecraft Activation,     | Ball |         |                 |
| 1. | Check-Out, and Transition  |      |         |                 |
| 04 | Plan                       |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | Spacecraft FMECA Analysis  | Ball |         |                 |
| 1. |                            |      |         |                 |
| 05 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS Engineering Data      | 924  |         |                 |
| 2. | Archive                    |      |         |                 |
| 01 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS Sustaining            | 924  |         |                 |
| 2. | Engineering Support Plan   |      |         |                 |
| 02 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS Flight Software       | 924  |         |                 |
| 2. | Maintenance Support Plan   |      |         |                 |
| 03 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS Operations Manual     | 924  |         |                 |
| 2. |                            |      |         |                 |
| 04 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS Flight Software       | 924  |         |                 |
| 2. | Manual                     |      |         |                 |
| 05 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS Training Plan &       | 924  |         |                 |
| 2. | Materials                  |      |         |                 |
| 06 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS FMECA Analysis        | 924  |         |                 |
| 2. |                            |      |         |                 |
| 07 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+
| 1  | GLAS Calibration &         | ST   |         |                 |
| 3. | Validation Plan            |      |         |                 |
| 01 |                            |      |         |                 |
+----+----------------------------+------+---------+-----------------+

## Major Reviews

The following are key operations and ground system reviews that shall be
supported.

  ---------------------- ------------------------------ ---------------------- --------------------------
  [Review                [Description & Relationship to [Lead                  [Month/Year]{.underline}
  Name]{.underline}      Mission Operations and Ground  Element]{.underline}   
                         Systems]{.underline}                                  

  IGS Critical Design    Overall Design Review of all   BASD                   December, 1999
  Review                 Ground System elements (MOC,                          
                         FOT, IOC, IOT, FDS, etc.).                            

  Mission Operations     Demonstration of mission       BASD                   December, 1999
  Review (MOR)           operations readiness to                               
                         support mission, including I&T                        
                         support. Joint review with                            
                         BASD, GLAS, ESDIS, CSOC, and                          
                         Science.                                              

  Flight Operations      Demonstrate that all flight    BASD                   April-2001
  Review                 and ground systems and                                
                         personnel reflect the deployed                        
                         state of the system. Joint                            
                         review with BASD, GLAS, ESDIS,                        
                         CSOC, and Science.                                    

  Operations Readiness   Focuses on networks support    CSOC                   May-2001
  Review (ORR)           readiness for ICESat. Also                            
                         supported by MOC, ESDIS, etc.                         

  Launch Readiness       (also called FRR) Demonstrates BASD                   June-2001
  Review (LRR)           readiness to launch the                               
                         spacecraft by all mission                             
                         elements. Joint review with                           
                         BASD, GLAS, ESDIS, and                                
                         Science.                                              

  Mission Activation     Review by all mission elements ICESat Project         August-2001
  Review                 of successful activation,                             
                         transition, and calibration                           
                         events.                                               

  Acceptance Review                                                            

  GLAS Commissioning                                                           
  Review                                                                       

  CAL-VAL Mid-Term                                                             
  Review                                                                       

  Cycle 1 Review                                                               
  ---------------------- ------------------------------ ---------------------- --------------------------

## Mission Operations Development Support

Each mission element shall support the definition, implementation,
testing, and transition to operations of the ICESat This includes
participation in working groups and planning sessions, preparing
materials, and participating in activities such as working sessions,
reviews, testing, status reporting, simulations, and dress rehearsals.

## Acceptance and Transition Roles and Responsibilities

1.  From the time of launch to final observatory acceptance by the
    Government, BASD Flight Director shall bear full responsibility, in
    concert with a team of experts from NASA, Ball, and the Instrument
    Developer, for the health and safety of the ICESat Observatory.

2.  After acceptance by the Government, BASD, through the MOC/FOT
    organization shall have full responsibility for the safe operations
    of the ICESat Observatory and the health and safety of the GLAS
    instrument for the life of the mission.

# EOS Polar Ground Stations

The EPGS Project consists of three ground stations: Alaska Ground
Station (AGS), Svalbard Ground Station (SGS), and Wallops Ground Station
(WGS). These ground stations shall provide space-ground
telecommunications services for the ICESat spacecraft for the life of
the mission. These services consist of S-band command, S-band telemetry,
and X-band telemetry. WGS shall be used as a back-up S-band command and
telemetry support, including contacts to confirm certain periodic
maneuvers that occur over the equator on the ascending pass towards
Wallops. The contact schedule is described in the next section.

## Interface Standards

1.  Up-link and down-link data formats are CCSDS compatible and data
    interface standards adhere to Ground System Interface Control
    Document; Data.

2.  Radio frequency interface specifications are specified to be
    compatible with the EOS Polar Ground Stations, as stated in the
    Ground System Interface Control Document: Radio Frequency.

3.  The EPGS technical experts or their designees shall participate in
    the development and maintenance of these ICDs.

## Baseline Ground Station Contact Scenario

The EPGS shall support the following ground station contact scenario.

+---------------+------------+------------+------------+------------+
| [Contact      | X-band     | S-Band     | R/T S-band | S-band Up  |
| Ch            | Down       | Down       | Down @ 16  |            |
| aracteristics |            |            | Kbps       | @ 2 Kbps   |
| ]{.underline} | @ 40 Mbps  | @ 264 Kbps |            |            |
+---------------+------------+------------+------------+------------+
| Base-line     | 10 degrees | 5 degrees  | 5 degrees  | 5 degrees  |
| ground        |            |            |            |            |
| station       |            |            |            |            |
| antenna       |            |            |            |            |
| elevation     |            |            |            |            |
| angle for AOS |            |            |            |            |
+---------------+------------+------------+------------+------------+
| Minimum Link  | 3dB        | \> = 3dB   | 3dB        | \> = 3dB   |
| Margin        |            |            |            |            |
| guaranteed by |            |            |            |            |
| ICESat        |            |            |            |            |
| project at 10 |            |            |            |            |
| degrees.      |            |            |            |            |
+---------------+------------+------------+------------+------------+
| Minimum       | Up to one  | Up to one  | Up to one  | Up to one  |
| Scheduled     | contact    | contact    | contact    | contact    |
| Contacts from | every      | every      | every      | every      |
| Launch        | orbit      | orbit.     | available  | available  |
| Through       |            |            | pass.      | pass.      |
| Calibration   |            |            |            |            |
|               |            |            |            |            |
| L + 150 days  |            |            |            |            |
+---------------+------------+------------+------------+------------+
| Minimum       | At least   | At least   | At least   | At least   |
| Scheduled     | one        | one        | one        | one        |
| Contacts for  | contact    | contact    | contact    | contact    |
| pos           | every 6    | every 6    | every 6    | every 6    |
| t-calibration | hours      | hours      | hours      | hours      |
| normal        |            |            |            |            |
| operations    |            |            |            |            |
| from L+150    |            |            |            |            |
| days to EOL   |            |            |            |            |
+---------------+------------+------------+------------+------------+
| Contact       | Which ever | Which ever | Which ever | Which ever |
| Duration      | comes      | comes      | comes      | comes      |
|               | first:     | first:     | first:     | first:     |
|               |            |            |            |            |
|               | 1.  time   | 1.  time   | 1.  time   | 1.  time   |
|               |     to     |     to     |     to     |     to     |
|               |     dump   |     dump   |     dump   |     dump   |
|               |     SSR or |     DSU or |     DSU or |     DSU or |
|               |            |            |            |            |
|               | 2.  time   | 2.  time   | 2.  time   | 2.  time   |
|               |     when   |     when   |     when   |     when   |
|               |            |            |            |            |
|               |    contact |    contact |    contact |    contact |
|               |     t      |     t      |     t      |     t      |
|               | erminates. | erminates. | erminates. | erminates. |
+---------------+------------+------------+------------+------------+

After launch, the ground stations shall characterize the X-band
communications links and determine a baseline contact scenario. This
contact scenario will define the minimum ground antenna elevation angle
for acquisition of signal (AOS). The baseline elevation angle for AOS is
currently 10 degrees.

## Emergency Commanding

Emergency commanding shall be made available within two hours after the
declaration of a flight system emergency by the flight operations team.

## Wallops Flight Facility Ground Network Scheduling System

The Wallops Orbital Tracking Information System (WOTIS), located at the
Wallops Flight Facility (WFF) is the central facility that the ICESat
Mission Operations Center (MOC) interfaces with for scheduling ground
station resources and obtaining post-pass reports. WOTIS will ingest the
ICESat project schedule requests, employ de-confliction algorithms, and
distribute the final schedules to ground stations and the ICESat MOC.
WOTIS will provide scheduling support 24 hours per day, 7 days a week.
Table 3-1 lists the typical transactions and transaction timing between
the ICESat MOC and WOTIS.

**Table 3-1. Typical WOTIS File Interchange Timeline**

+-----+--------------------+------------------------+-----------------+
| **  | **File & Content** | **Action**             | **Time Period** |
| Ste |                    |                        |                 |
| p** |                    |                        |                 |
+-----+--------------------+------------------------+-----------------+
| 1   | Strawman Schedule  | WOTIS generates        | T\*-3 weeks     |
|     |                    | initial schedule,      |                 |
|     | Contains initial   | using WOTIS generated  |                 |
|     | supports at all GS | Inviews, according to  |                 |
|     | using resources    | WOTIS/ICESat agreed    |                 |
|     | per the ICD        | scheduling rules.      |                 |
+-----+--------------------+------------------------+-----------------+
| 2   | Update to Strawman | MOC returns schedule   | T-2 weeks       |
|     | Schedule           | to WOTIS with those    |                 |
|     |                    | supports needed, and   |                 |
|     | Contains only      | may adjust times and   |                 |
|     | those supports     | activity codes; a new  |                 |
|     | needed by ICESat   | support may be         |                 |
|     |                    | requested, if needed.  |                 |
|     |                    | If Strawman is         |                 |
|     |                    | correct, no update     |                 |
|     |                    | needs to be returned.  |                 |
+-----+--------------------+------------------------+-----------------+
| 3   | Operations         | WOTIS sends final      | T-1 week,       |
|     | Schedule Contains  | Operations schedule to | usually Tuesday |
|     | supports as they   | MOC, if desired.       | before Ops week |
|     | will be processed  |                        |                 |
|     | at each GS         |                        |                 |
+-----+--------------------+------------------------+-----------------+
| 4   | Ephemeris          | MOC sends IIRV or      | At least 3 days |
|     |                    | corrected NORAD 2-Line | before pass to  |
|     |                    | Elements, if needed;   | accommodate     |
|     |                    | otherwise WOTIS        | weekend and     |
|     |                    | automatically gets     | holiday         |
|     |                    | orbital elements from  | operation. New  |
|     |                    | the Internet.          | data shall      |
|     |                    |                        | overwrite old   |
|     |                    |                        | data.           |
+-----+--------------------+------------------------+-----------------+
| 5   | GS Operations      | WOTIS generates weekly | Time span is    |
|     | Schedule (AOTS     | and/or daily           | for Operations  |
|     | Master)            | Operations Schedule    | week, generated |
|     |                    | (containing ephemeris) | on              |
|     |                    | and forwards to GS via | Thursday/Friday |
|     |                    | FTP.                   | & updated daily |
|     |                    |                        | as needed       |
+-----+--------------------+------------------------+-----------------+
| 6   | Post-Pass Summary  | WOTIS provides a       | After each pass |
|     | File Contains the  | summary of support     |                 |
|     | summary statistics | results to MOC shortly |                 |
|     | from the support   | after the completion   |                 |
|     |                    | of the support.        |                 |
+-----+--------------------+------------------------+-----------------+

.T\* denotes target operation week

## 

## .

## Doppler Ranging

Allground stations (AGS and, SGS, and WGS) shall provide two-way Doppler
data for launch and early orbit check-out of the ICESat spacecraft, and
for contingency operations in the event of on-board Global Positioning
System (GPS) receiver failure.

## S-band Command & Telemetry Command Processing

1.  All ground stations (AGS, SGS, and WGS) shall provide received
    Real-Time S-band telemetry data to the Mission Operations Center
    (MOC).

2.  All ground stations shall transmit commands received from the MOC to
    the ICESat spacecraft.

3.  All ground stations shall forward received S-band Playback telemetry
    data and all Real-Time S-band telemetry data to EDOS.

4.  AGS and SGS shall forward all received X-band data to the EDOS
    Ground Station Interface Facility (GSIF)

5.  

6.  GPS data packets shall be available via EDOS/EBNet at the FDS no
    later than 6 hours after the X-band ground station contact is
    completed.

7.  S-band real-time data, including GPS on-board solutions data, shall
    be available at the FDS within 1 minute of ground station contact.

8.  S-band playback data shall be available at the FDS via EDOS within
    30 minutes after S-band ground station contact is completed

9.  All ground stations shall uplink data to the ICESat observatory as
    the data are received from the MOC (via EBNet).

## Compatibility Test Van Support 

CSOC shall provide:

1.  Compatibility Test Van (CTV) at BASD's I&T facility for Radio
    Frequency testing of the ICESat spacecraft at the designated X-band
    and S-band frequencies.

2.  CTV Test Plans and Procedures, including facility and communications
    requirements

3.  CTV Test Report

4.  CTV testing at WGS .

## Communications Links Testing

Provisions shall be made such that the ground stations shall accept
X-band and S-band test data as recorded from the spacecraft on CD-ROM
media or direct transmission through commercial rate data links.

# Ground Communications

The ESDIS Project shall provide all ground communications infrastructure
to support the mission requirements.

## Mission Operations System Communications

ESDIS shall provide all ground communications networks and links
required to support the ICESat mission operations, including both voice
and data communications..

## 

## 

## Launch Pad Communications with the MOC

ESDIS shall provide voice loops between the launch pad and the Mission
Operations Center.

.

## Science Distribution Communications

1.  ESDIS shall provide all network support services required to
    interconnect the data archive centers, the Science Computing
    Facilities and ISIPS

2.  ESDIS shall provide all external network connectivity to distribute
    science data products to the end user.

## Communications Testing

ESDIS shall test and verify all communications links prior to
interfacing with any ICESat mission element, in order to mitigate risks
due to unforeseen interface problems.

# Mission Operations Center

## Mission Communications Support Profile

The following chart shows the expected number of contacts to be
supported by the MOC/FOT for the major mission phases shown.

+---------------+------------+------------+------------+------------+
| [Contact      | X-band     | S-Band     | S-band Up  | R/T S-band |
| Ch            | Down @ 40  | Down @ 264 | @ 2 Kbps   | @ 16 Kbps  |
| aracteristics | Mbps       | Kbps       |            |            |
| ]{.underline} |            |            |            |            |
+---------------+------------+------------+------------+------------+
| Minimum       | Up to one  | Up to one  | Up to one  | Up to one  |
| Scheduled     | contact    | contact    | contact    | contact    |
| Contacts from | every      | every      | every      | every      |
| Launch        | orbit      | orbit.     | available  | available  |
| Through       |            |            | pass.      | pass.      |
| Calibration   |            |            |            |            |
|               |            |            |            |            |
| L + 150 days  |            |            |            |            |
+---------------+------------+------------+------------+------------+
| Minimum       | At least   | At least   | At least   | At least   |
| Scheduled     | one        | one        | one        | one        |
| Contacts for  | contact    | contact    | contact    | contact    |
| pos           | every 6    | every 6    | every 6    | every 6    |
| t-calibration | hours      | hours      | hours      | hours      |
| normal        |            |            |            |            |
| operations L+ |            |            |            |            |
| 150 days to   |            |            |            |            |
| EOL           |            |            |            |            |
+---------------+------------+------------+------------+------------+

## Major Interfaces

The MOC major interfaces are listed below and shown schematically in the
ICESat Ground System Data Flow and Architecture Diagram in Section 2.2.
.

1.  EOS Polar Ground Station (EPGS) in Alaska and Norway -- EPGS's are
    the primary ground stations for S-band command and telemetry and
    X-band data communications with the ICESat Observatory. The MOC
    shall interface with EPGS for real-time (R/T) housekeeping data and
    for command uploads.

2.  Wallops Ground Station (WGS) in Virginia -- WGS provides back-up
    S-band command and telemetry interfaces. The MOC shall interface
    with WGS for backup command and control interfaces.

3.  Wallops Orbital Tracking Information System (WOTIS) in Virginia --
    the WOTIS provides planning and scheduling of ground station
    resources. The MOC shall interface with WOTIS to coordinate
    scheduling of the ground system.

4.  Earth Observing System (EOS) Data and Operations System (EDOS) at
    GSFC -- EDOS provides the processing of Playback (PB) S-band
    housekeeping data and recorded X-band science data. The MOC shall
    interface with EDOS for receipt of the processed S-band data and for
    the exchange of scheduling information.

5.  Multi-mission Flight Dynamics (MMFD at GSFC -- MMFD will primarily
    provide support during launch and early orbit and shall provide
    processing of the launch vehicle's separation vector and provide
    acquisition data to the EPGS. The MOC shall interface with the GFDS
    and receive theseMMFD products for command generation to adjust the
    Observatory's orbit and attitude. MMFD may also be called upon to
    support emergency situations.

6.  NASA Integrated Support Network (NISN) shall provide all
    communications networks and network operations personnel to provide
    connectivity to all ground system elements. The MOC shall utilize
    these networks for all communications requirements external to the
    MOC.

7.  Instrument Support Facility (ISF) at GSFC -- The ISF conducts long
    term instrument trending and analysis and contains the Instrument
    Operations Team (IOT). The MOC shall interface with the ISF and
    provide planning products and receive command requests and GLAS
    flight software generated by the IOT.

8.  ICESat Integration & Test (I&T) Facility at BASD -- The MOC shall
    interface with the Ball I&T facility during all phases of the I&T
    process. The I&T facility will also contain the Spacecraft Bus
    Simulator (SBS) to be used by the MOC when the spacecraft is not
    available for testing.

9.  Spacecraft Sustaining Engineering Facility (SSEF) at BASD -- The
    SSEF will contain the ICESat Flight Software Test Bed (FSTB). The
    MOC shall interface with the FSTB after launch to support testing of
    any software modifications and to receive software uploads generated
    by the FSTB. The SSEF includes personnel with which the MOC shall
    interface for spacecraft anomaly resolution and spacecraft trending
    analysis.

## Flight Systems

BASD shall provide all MOC hardware and software systems.

1.  

[]{#__RefHeading___Toc460824707 .anchor}Facility

1.  BASD shall provide all facilities necessary to house the systems and
    personnel that comprise the MOC, including floor space, Heating,
    Ventilation, and Cooling (HVAC), lighting, and physical security.

2.  Office space with a desk and internet connection for up to four
    project personnel (such as instrument engineers, project staff,
    etc.) shall be provided

## Operational Coverage

1.  The MOC shall operate on a basis consistent with the mission's
    science requirements, schedule, and ground station contact
    scenarios. Autonomous ("lights out" or "brown out") operations are
    encouraged

2.  The MOC hardware and software systems shall operate on a 24 hour per
    day basis, 365 days per year.

3.  ICESat operations shall be conducted in coordination with the ICESat
    science objectives and plans as generated by the IOT and the science
    team (ST).

4.  MOC and FOT shall have a response time of no more than (TBD) minutes
    in response to a spacecraft/instrument emergency.

5.  MOC and FOT shall be responsible for the health and safety of GLAS
    instrument.

## Database Compatibility

The MOC software shall be compatible with the Operations and Science
Instrument Support (OASIS) database format. All ground systems to be
implemented shall be compatible with the OASIS database and be driven by
Integration & Test (I&T) database electronic files provided by BASD.

## Planning and Scheduling

The MOC shall perform the following:

1.  coordinate the planning and scheduling of all ground system
    resources and contacts.

2.  shall perform all the planning and scheduling of all flight related
    activities with inputs from the IOT and ST.

3.  shall integrate the instrument command requests from the ISF.

4.  shall produce the spacecraft's operation schedule and operations
    timelines.

## Real-time Observatory Telemetry Monitoring

1.  The MOC shall monitor all real-time flight critical telemetry
    parameters during all ground station contacts.

## Trending Analysis

The MOC shall perform the following:

1.  shall conduct long term trending and analysis of the ICESat
    Observatory's playback telemetry parameters collected over the life
    of the mission. This includes critical spacecraft bus and instrument
    telemetry.

2.  shall provide predicted trends for critical Observatory parameters.

3.  shall deliver monthly trending curves.

4.  shall be provided to BASD for analysis and long term performance
    assessment.

## Observatory Commanding

The MOC shall perform the following:

1.  shall perform the real-time commanding of the ICESat Observatory to
    meet all mission objectives.

2.  shall provide for the generation of stored command strings to be
    up-linked to the ICESat Observatory.

3.  provide the uploading of parameters (such as tables, software,
    etc.).

4.  receive GLAS command requests, parameters, flight software, tables
    from the GLAS ISF for subsequent upload.

## Remote Monitoring Terminal

1.  A monitor-only remote MOC terminal shall be provided to the ISF/IOT
    to support the monitoring of the ICESat Observatory by the IOT
    during all phases of the mission.

2.  Four monitor-only MOC terminals located at the MOC for use during
    launch and early orbit check-out operations by instrument and
    spacecraft bus engineering personnel shall be provided. These
    terminals shall be retained for the life of the mission.

## Sustaining Engineering

BASD shall maintain the MOC and perform sustaining engineering of all
MOC hardware and software systems. This shall include the loading and
testing of any software upgrades, hardware upgrades, and facility
improvements required to sustain operations for the life of the ICESat
Observatory.

## Anomaly Resolution

1.  The MOC shall provide support for anomaly resolution of all
    Observatory anomalies. This includes coordinating such efforts with
    subsystem experts from BASD and the GLAS instrument developer.

2.  Anomaly resolution shall include interfacing with the GLAS developer
    and BASD for the maintenance, correction, and uploading of flight
    software and other uploadable parameters.

3.  Monthly Anomaly reports shall be provided to the GSFC Reliability
    and Safety Office.

## MOC Data Archive

The MOC shall:

1.  permanently archive all S-band real-time and playback telemetry for
    the life of the mission.

2.  archive all received (maneuver planning products and orbit
    determination solutions) and generated (command files, trending
    data, schedules etc.) products for the life of the mission.

3.  make available to authorized users via File Transfer Protocol (or
    similar Internet connection) all products such as command files,
    maneuver planning files, trending data, schedules, etc. .

4.  

5.  deliver to (TBD) DAAC all ICESat related data held at the MOC at the
    end of the ICESat mission.

## Laser Flight Safety Operations

There are no laser flight safety operational requirements for ICESat.

## Flight Operations Team

1.  BASD shall provide a flight team organization chart. A description
    of the roles and responsibilities of the Flight Director and each
    FOT member shall be provided.

### 

1.  
2.  

### 

2.  BASD shall provide a system whereby members of the FOT shall be
    available on an on-call basis to provide anomaly resolution support
    in the event that a spacecraft emergency or anomaly situation
    occurs.

3.  BASD shall provide pre-launch training and post-launch continued
    training of the FOT personnel, including continued certification in
    flight operations of the ICESat Observatory.

4.  BASD shall support at least 3 Flight Operations Rehearsals for the
    purpose of training and developing flight operations proficiency.
    Each Rehearsal shall nominally be scheduled for a 5 day period at 24
    hours each day. The Rehearsals to be supported are outlined as
    follows:

  ------------------ ------------------------------------- ---------------
  Rehearsal \#       Purpose                               Rehearsal Need
                                                           Dates

  Rehearsal \# 1     Basic Operations Training             L -- 3 months

  Rehearsal \# 2     Anomaly resolution and                L -- 2 months
                     trouble-shooting.                     

  Rehearsal \# 3     Full Flight Dress Rehearsal           L -- 2 months
  ------------------ ------------------------------------- ---------------

## Reliability

1.  The MOC shall be designed for an availability that meets the
    operational coverage requirements set forth in this MORD. BASD shall
    provide an availability calculation, along with supporting
    rationale, for the MOC/FOT system.for Government approval.

2.  No single point hardware or software failure shall be implemented in
    the Real-Time telemetry and command processing system.

3.  MOC system maintenance shall be scheduled during non-contact times
    and shall be conducted on only a non-operational functional string
    to ensure that a functioning string is always available to support
    telemetry monitoring and commanding.

## Security

1.  Physical security shall be provided and demonstrated such that the
    MOC facility and systems shall be secured from unauthorized access.
    Unrestricted access to MOC facilities and computer systems shall not
    be allowed.

2.  The MOC's computer systems and supporting network interfaces shall
    be protected from unauthorized access.

3.  Flight Database access and updates shall be controlled**.**

4.  Security measures shall be taken to prevent database corruption and
    permanent database loss.A backup copy of all changed software,
    databases, and documentation shall be retained in a separate
    physical location other than the MOC.

## Observatory Integration and Testing Support

1.  The MOC/FOT shall interface with BASD during all phases of the
    Observatory I&T process. This includes participating in all ground
    system simulations and rehearsals, including end-to-end science data
    flow tests, and interfacing with the Spacecraft Simulator and the
    Flight Software Test Bed (FSTB). The FSTB is the flight software
    development environment used by BASD for the development, testing,
    and maintenance of flight software.

2.  The MOC/FOT shall interface with the Spacecraft Ground Support
    Equipment (GSE) to support integration & test activities including
    end-to-end science data flow tests.

## Documentation

BASD shall deliver the following documents to NASA/GSFC. If existing
documentation structures used on other missions currently exist, these
may be used with Government approval in lieu of these documents .

[Mission Operations Center Documentation:]{.underline}

1.  Integrated MOC/FOT/FDS Development Schedule.

2.  MOC External Interfaces Control Document (MEICD) that includes
    interfaces between all external MOC interfaces.

3.  Detailed MOC Requirements & Design Document (DMR&DD), that includes
    derived requirements, detailed design, staffing & training plans and
    facility plans.

4.  MOC Test Plan.

5.  MOC Flight Operations Procedures (MFOP).

6.  Operational Agreements with IOT, ST, and other major ground system
    elements (EPGS, WFF, EDOS, etc.).

[Flight Dynamics Documentation:]{.underline}

The FDS contractor provide the following documentation:

1.  FDS External Interface Control Document (FEICD) (may be combined
    with the MOC External Interfaces ICD).

2.  FDS Detailed Requirements and Specification.

3.  FDS Test Plan (FDSTP).

4.  FDS Operations Procedures Handbook.

5.  Operational Agreements with the FOT, IOT, ST, and other mission
    elements (EPGS, WFF, etc.).

## Reviews and Status Reporting

BASD shall provide the following reviews and status reporting (note,
some reviews are likely to be combined with existing reviews base-lined
in the ICESat contract) on the MOC/FOT activities:

1.  Status Reports to the ICESat Operations Manager (Monthly)

2.  Requirements/Design Review (\~ L - 18 months)

3.  Flight Operations Review (\~L - 4 months)

4.  Launch Readiness Review (\~L - 1 months)

5.  BASD shall provide a FDS Design Review (FDSDR) for approval of the
    design by the Goddard Space Flight Center's Flight Guidance and
    Navigation personnel, Science Team personnel, and University of
    Colorado personnel.

# Flight Dynamics System

The Flight Dynamics System (FDS) shall be that part of the MOC which
provides overall Guidance & Navigation (G&N) for the ICESat mission.
With the exception of the NASA-provided services described below, BASD
shall provide all the FDS functions described in Section 4.

## CSOCProvided Flight Dynamics Services (MMFD)

CSOC shall:

1.  interface with the BASD-provided FDS.

2.  provide the traditional MMFD flight dynamics support during launch
    and early orbit such as:

```{=html}
<!-- -->
```
1.  Work with NASA ground stations to analyze and verify tracking system
    accuracy.

2.  Serve as the interface to the launch contractor for acquiring and
    processing launch trajectory predicts and initial post-separation
    spacecraft orbit predicts.

3.  Acquire LTAS data from launch site and process to generate initial
    orbit predict.

4.  Acquire NORAD tracking data and process to generate orbit predicts.

5.  Acquire UTDF angles tracking data from NASA ground stations after
    passes and process into orbit predicts.

6.  Generate initial orbit predict after spacecraft separation and
    distribute as IIRV to the MOC, WOTIS and to ground stations.

7.  Generate updated orbit predicts every four hours for the first 24
    hours after launch and distribute as IIRVs to the MOC, WOTIS and
    ground stations.

8.  Generate updated orbit predicts every 24 hours, starting one day
    after launch and continuing through seven days after launch and
    distribute as IIRVs to the MOC and WOTIS.

9.  Orbit Determination based on Ground Station Doppler-ranging and X-Y
    angles data from the ground tracking stations (if GPS data is not
    available).

[]{#__RefHeading___Toc460824727 .anchor}Mission Characteristics

The following are the top-level ICESat norminal science mission
characteristics applicable to the FDS.

1.  Inclination = 94 degrees.

2.  Right Ascension of the Ascending Node - n/a

3.  Semi-major Axis = 6970.0 Km

4.  Eccentricity = 0.0013

5.  Augument of Perigee = 90 degrees

6.  Orbit Operational Lifetime = 975 (minimum) /1705 (maximum) days

7.  Altitude = 600 km.

8.  Orbit = non-sun synchronous frozen orbit.

9.  orbits repeat after 183 days .

10. +/- 800 meter ground track control at all latitudes.

During Calibrationa and Validation Phase, the orbital parameters are:

1.  Inclination = 94 degrees

2.  Right Ascension of the Ascending Node - n/a

3.  Semi-major Axis = 6971.5 Km

4.  Eccentricity = 0.0013

5.  Argument of Perigee =90 degrees

6.  Orbit Operational Lifetime \~90 days

7.  Orbit repeats after 8 days

## BASD Provided FDS

:

### The following data shall be ingested for use by the FDS.

a)  X-band data packets that contain GPS raw data shall be available via
    EDOS at the FDS no later than 6 hours after the X-band ground
    station contact is completed.

b)  S-band real-time data, including GPS on-board solutions data, shall
    be available via the EPGS and WFF at the FDS within 1 minute of
    ground station contact.

c)  S-band playback data shall be available at the FDS via EDOS within
    30 minutes of ground station contact.

### The data processing performance for the following data shall be:

TBD

### The following data product shall be generated with the following frequency:

TBD

## Software, Hardware, Personnel, and Facilities

1.  BASD shall provide all FDS software development and maintenance and
    all hardware systems and training required to operate the software
    for the life of the mission.

2.  BASD shall provide all FDS personnel and facilities required to
    operate the flight dynamics systems for the life of the mission.

## Mission Phases Support

### Maneuver Constraints

1.  No maintenance maneuvers shall occur over Antarctica or at points
    above 60 degrees latitude that are coincident with a post-maneuver
    pass over Greenland except in special or emergency circumstances.

2.  All initial orbit maneuvers shall be performed during ground station
    contacts.

3.  Ground track maintenance shall be performed using only one maneuver
    when possible.

4.  Frozen orbit maintenance shall be done in conjunction with the
    ground track maintenance maneuver.

5.  Maneuvers shall be constrained to occur no more frequently than once
    daily to support the Precision Orbit Determination (POD).

6.  Maneuver times shall be coordinated with the science team.

### Pre-Launch Phase

The Pre-launch period shall cover all time up to separation from the
launch vehicle. The following FDS functions and services shall be
provided:

1.  Mission Analysis and Design Delta Velocity (Delta V) Budget
    calculation and analysis.

2.  Injection Orbit Selection analysis.

3.  Reentry analysis (lifetime).

4.  Ground Station coverage analysis.

5.  Launch window analysis.

6.  Operations Planning, including participation in launch rehearsals
    and simulations.

### Check-out Period Phase

The Check-out period is the time from launch vehicle separation to the
time the spacecraft bus has been accepted by the Government
(approximately 30 days). The following FDS functions and services shall
be provided:

1.  Ingest and process launch vehicle separation vector from MMFD.

2.  Planning and calibration of all orbit raising maneuvers.

3.  Planning and calibration of all routine ground track maintenance
    maneuvers.

4.  Planning and calibration of inclination maneuvers.

5.  Thruster calibration for the orbit attainment maneuvers.

6.  Thruster calibrations for the orbit maintenance maneuvers.

7.  Orbit determination and prediction based on GPS data from the flight
    receiver.

8.  On-board attitude validation support.

9.  Anomaly resolution support.

10. Sensor calibration support.

11. Provide Orbit Predictions in Improved Inter-Range Vector (IIRV)
    format to the ground station network.

12. Convert Maneuver Plan into commands and table uploads for uplink to
    spacecraft.

### Calibration and Validation Phase

The Calibration and Validation period covers all time from acceptance of
the spacecraft by the Government to the time that the GLAS instrument
has been calibrated and verified and data products have been validated.
Subsequently, the science mission operations begins.. The following FDS
functions and services shall be provided:

1.  Planning and calibration of the inclination and ground-track
    maintenance maneuvers.

2.  Support onboard orbit and attitude determination validation.

3.  Anomaly resolution support.

4.  Sensor calibration support.

5.  Generation of planning and scheduling data products used by the MOC.

6.  Provide Orbit Predictions in IIRV format to the ground station
    network.

7.  Convert Maneuver Plan into commands and table uploads for uplink to
    spacecraft.

### Maneuver Planning

BASD shall provide maneuver planning and maneuver calibration for all
phases of mission operations. The FDS system shall be capable of
designing three types of maneuvers:

(1) [Drag Make-up Maneuvers]{.underline} - along track maneuvers to
    adjust the orbit semi-major axis shall be designed to change the
    ground-track drift rate relative to the exact repeat orbit.

(2) [Inclination Maneuvers]{.underline} - across track maneuvers to
    adjust the orbit inclination shall be designed to change the
    ground-track offset at high latitudes relative to the exact repeat
    orbit.

(3) [Orbit Change Maneuvers]{.underline} - two along track maneuvers to
    adjust the orbit semi-major axis shall be designed to switch between
    the calibration and mission orbits.

(4) [Attitude Maneuvers]{.underline} - in support of instrument
    operations

NOTE: The effect of these maneuvers on the mean orbit elements and
ground-track offset shall be predicted and communicated to the MOC.

### Ground-Track Monitoring and Prediction:

1.  The Ground-Track shall be monitored daily and compared to that of
    the calibration or mission orbit, whichever is appropriate. Such
    monitoring shall be valid for all latitudes.

2.  The Ground-Track evolution shall be predicted to aid in maneuver
    planning. Such predictions shall make use of solar activity
    predictions to anticipate atmospheric drag, and the effect of
    luni-solar gravity on the orbit inclination.

3.  The Ground-Track output shall consist of both a graphical display of
    predicted ground-track offset, and tables of predicted mean orbit
    element and ground-track offset evolution.

### Mission Planning Support

1.  Determine coarse real-time ICESat attitude.

2.  Provide mission planning aids.

3.  Provide attitude sensor hardware performance monitoring.

4.  Determine predictive ICESat orbit ephemeris and perform maneuver
    prediction and planning.

5.  Provide near-real-time maneuver monitoring (temperature, pressure,
    etc.).

6.  Provide acquisition data products.

7.  Assess the post-maneuver spacecraft state.

## Orbit & Attitude Determination

### Operational Orbit Determination

BASD shall perform Operational Orbit Determination (OOD) using GPS data
from the flight receiver in combination with GPS data from a worldwide
network of ground tracking sites. Accuracy and timeliness shall be as
follows:

Orbit Monitoring and Maneuver Planning OOD:

1.  Along track position: Within 5 meters (1 sigma).

2.  Across track position: Within 5 meters (1 sigma).

3.  Radial position: Within 1.0 meters (1 sigma).

4.  OOD Latency: Within 2 hours after X-band data received at FDS.

5.  Comparison with POD: Flight Dynamics shall compare the OOD with the
    POD generated by the ST on a periodic basis in support of the
    onboard GPS validation.

Propagation Accuracy of the OOD solution after 1 day:

1.  Along track position: Within 1.0 kilometer (1 sigma).

2.  Across track position: Within 10 meters (1 sigma).

3.  Radial position: Within 10 meters (1 sigma).

4.  ODD Latency: Within 2 hours after X-band data received at FDS.

Propagation accuracy of the OOD solution for Antenna Pointing ODD after
24 hours of propagation and 24 hours after a maneuver:

1.  Along track position: Within 4 kilometers (1 sigma).

2.  Across track position: Within 4 kilometers (1 sigma).

3.  Radial position: Within 4 kilometers (1 sigma).

4.  ODD Latency: Within 2 hours after X-band data received at FDS.

### Operational Attitude Support

BASD shall provide the following Operational Attitude (OA) support:

1.  The FDS shall calculate and monitor off-nadir pointing by running
    the off-nadir pointing algorithm provided by the University of
    Colorado.

2.  The FDS shall generate the off-nadir quaternions and provide them to
    the MOC for uploading to the spacecraft.

## Sensor Support

BASD shall provide for the operation, maintenance, and calibration of
various sensors used on the spacecraft.

### Sensor Uploadable Parameters Support

The BASDshall provide periodic updates for the following sensors and
subsystems. FDS shall support these updates.

1.  Star Catalog for spacecraft bus star tracker:

```{=html}
<!-- -->
```
a)  Updates with respect to proper stellar motion (estimated annual
    upload of approximately 50 stars).

b)  Updates of a star Precession Quaternion (estimated weekly upload).

```{=html}
<!-- -->
```
2.  GPS Initial Conditions Vector - Initialization of the GPS receiver
    whenever a Spacecraft Control Computer (SCC) reset takes place.

3.  Magnetic Field Tables -- Table upload approximately annually.

.

### Sensor Calibration Support

The BASD shall participate in the following calibration activities with
support from the BASD () and science operations:

1.  Calibrate alignments of the Solid State Star Tracker (SSST), and
    Inertial Reference Units (IRU).

2.  Calibrate the star-tracker's field-of-view (FOV) calibration
    coefficients.

3.  Calibrate the IRU scale factors and drift rate biases (3-axis
    calibration at varying rates).

## Products Exchange

### FDS Products to the Mission Operations Center

BASD shall generate the following products for use by the MOC on a
routine basis for all phases of the mission:

1.  Operational Orbit Determination and Propagated State Vectors.

2.  Maneuver Design (magnitude, attitude, and time).

3.  Ground Track Offset Plot and Table (actual versus predicted time).

4.  Plots and Tables to monitor the frozen orbit, including Inclination,
    Eccentricity, and Argument of Perigee parameters.

5.  Initial Condition Vector for the SCC and/or GPS, as needed.

6.  Generation of base time load to correlate the spacecraft clock
    (clock correlation code).

7.  Orbit & Attitude verification support.

### MOC Products to the Flight Dynamics System

The MOC shall make available the following products to the FDS:

1.  Propulsion system data, including tank pressure and temperature.

2.  The MOC shall make available to the FDS by electronic file transfer
    all raw S-band real-time and playback data received and all products
    generated by the MOC.

3.  Solar Array Encoder Conversions.

BASD shall provide the equations for the spacecraft mass model and the
propulsion model.

### Flight Dynamics Products to the Science Team

The FDS shall make available the following products to the science team.

1.  Inertia & Mass Properties.

2.  Maneuver magnitudes and timelines.

3.  OOD solutions.

4.  CT-602 Star Tracker data.

### Data and Products Archive

The FDS shall maintain a data archive with the following
characteristics:

1.  The FDS shall permanently archive all data received and products
    generated by FDS for the life of the mission.

2.  All data archives shall be readily accessible (via File Transfer
    Protocol, etc.) by authorized users external to the FDS for the life
    of the mission.

# Instrument Support Facility

## Instrument Flight Systems

All ISF hardware and software systems that are necessary to meet the
instrument operations requirements shall be provided by the Instrument
Operations Team (IOT).

## Facility

1.  All facilities necessary to house the ISF systems and personnel
    shall be provided. This includes floor space, lighting, and physical
    security.

2.  Office space with a desk and internet connection for up to two
    project personnel (such as an instrument engineer, project staff,
    etc.) shall be provided.

## Operational Coverage

1.  The ISF/IOT shall be operated on a nominal 5 day, 8 hour per day
    schedule. Autonomous (lights out or brown) operations are encouraged
    as a means of reducing mission costs during non-normal working
    hours. The IOT shall be on-call during the off staff periods. In an
    emergency, IOT shall staff the ISF within 3 hours of alert.

2.  All hardware and software systems necessary to support nominal
    off-hour operations shall operate on a 24 hour per day basis, 365
    days per year.

## Planning and Scheduling

1.  The ISF/IOT shall generate science plans, goals and objectives, and
    schedules for instrument operations that are in accord with the
    science plans and objectives.

2.  The ISF/IOT shall generate any unique planning and scheduling, such
    as for off-pointing for specific geographic areas.

3.  The ISF/IOT shall generate all instrument command requests and
    transmit them to the MOC/FOT for transmission to the Observatory.

## Instrument Operations, Maintenance and Calibration

### ISF shall provide periodic uploads for the following GLAS subsystems:

1.  Star Catalog for GLAS star tracker:

2.  Updates with respect to proper stellar motion (estimated annual
    upload of approximately 50 stars).

3.  Updates of a star Precession Quaternion (estimated weekly upload).

4.  GLAS Computer flight software updates

5.  GLAS software uploadable parameters and tables-- Table uploads for
    DEM and surface type, range control parameters.

### The ISF shall participate in the following calibration activities with support from BASD and science operations:

1.  Calibrate alignments of the GLAS subsystems

2.  Calibrate the GLAS star-tracker's field-of-view (FOV) calibration
    coefficients.

> Note: Some of these will require planning for spacecraft operation at
> specific pointing angles to collect data at requested ground targets.

## Trending Analysis

1.  The ISF shall provide for the long term trending and analysis of the
    GLAS Instrument's telemetry collected over the life of the mission.
    This includes critical related spacecraft bus telemetry.

2.  Trending requirements shall be provided by the GLAS Instrument
    Developer.

3.  Monthly trending curves and data reports shall be provided to the
    GLAS Instrument Developer for analysis and long term performance
    assessment.

## Sustaining Engineering

The ISF/IOT shall provide for the maintenance of all ISF hardware and
software systems. This includes the loading and testing of any software
upgrades, hardware upgrades, and facility improvements required to
sustain instrument operations for the life of the ICESat Observatory.

## Anomaly Resolution

1.  The ISF shall provide support for anomaly resolution of all
    Instrument anomalies and related spacecraft bus anomalies.

2.  The ISF shall interface with the GLAS Sustaining Engineering
    Facility (GSEF) and shall include interfacing with subsystem experts
    from the GLAS Instrument Developer.

3.  The GSEF shall include the GLAS Developer's GLAS Software
    Maintenance Facility (GSMF) for the maintenance, correction, and
    uploading of instrument software and other uploadable parameters.
    The ISF shall accept GLAS software uploads from the GSMF/GSEF for
    transmission to the MOC/FOT for transmission to the Observatory.

4.  Monthly Anomaly reports shall be provided to the GSFC Reliability
    and Safety Office.

## Instrument Operations Team

###  {#section-9 .unnumbered}

1.  Instrument Operations Team (IOT) shall be established by the Project
    Scientist/Science Team Leader to perform the GLAS operations.

2.  A system shall be provided by the IOT whereby members of the IOT
    shall be available on an on call basis to provide anomaly resolution
    support in the event that a spacecraft or instrument emergency or
    anomaly situation occurs.

3.  Pre-launch training and post-launch continued training of the IOT
    personnel shall be provided by the GLAS developer, including
    continued certification in flight operations of the GLAS instrument
    and overall ICESat Observatory shall be provided.

# EDOS

EDOS shall perform L0 data processing on the X-band down-link data and
the S-band down-link recorder playback housekeeping data.

## General Level Zero Data Processing Functions

  -------- --------------------------------------------------------------
  1.1      EDOS shall provide a safe backup of all ICESat GLAS Level 0
           data sets produced by EDOS.

  1.2      EDOS shall support ICESat pre-launch activities (e.g.,
           operational readiness tests and simulations).

  1.3      EDOS shall maintain/assure the integrity of all ICESat data
           received, stored, and transmitted.

  1.4      EDOS shall support ICESat operations 24 hours per day, 7 days
           per week on a continuous basis.

  1.5      EDOS shall support the CCSDS AOS Grade of Service 2 and 3.

  1.6      EDOS shall provide the capability for capture of all ICESat
           X-band high rate return link data on separate, non-volatile,
           physical media, and for storage for 30 days after receipt.

  1.7      EDOS shall provide Reed-Solomon (Grade of Service II) decoding
           on the ICESat high rate return link data as required.

  1.8      EDOS shall provide AOS CCSDS Path and Virtual Channel Data
           Unit services on ICESat return link data.

  1.9      EDOS shall provide processing support to produce Level 0 data
           sets (production data sets) \[PDSs\] and expedited data sets
           \[EDSs\] for the GLAS instrument packets.

  1.10     EDOS shall provide Customer Operations Data Accounting (CODA)
           reports to the ICESat Flight Operations Segment located in
           Boulder, CO every 5 seconds.

  1.11     EDOS shall provide SCS (spacecraft contact session) summary
           reports to the ICESat Flight Operations Segment located in
           Boulder, CO after each spacecraft contact.

  1.12     EDOS shall deliver a data file containing Star Tracker, IRU,
           LRS, and GPS packets to Flight Dynamics Facility (FDF) within
           6 hours of receipt of downlink at the ground station

  1.13     EDOS shall distribute physical media containing archived GLAS
           PDSs to the ISIPS located at the Wallops Flight Facility upon
           request(D3 tapes).

  1.14     EDOS shall provide processing support for ICESat low rate data
           that are played back from the spacecraft recorder.

  1.15     EDOS shall provide Reed-Solomon (Grade of Service III)
           decoding on the ICESat low rate return link data as required.

  1.16     EDOS shall provide rate buffered delivery service for ICESat
           low rate return link data.

  1.17     EDOS shall receive schedules for downlink support from the
           ICESat Control Center located in Boulder, CO

  1.18     EDOS shall receive, create, and deliver all external data
           products including schedules, rate buffered data, EDSs, PDSs,
           CODA reports, and SCS summary reports, in conformance with the
           EDOS-EGS Elements ICD.

  1.19     EDOS shall deliver PDSs and EDSs to the ISIPS system located
           at the Wallops Flight Facility.

  1.20     EDOS shall archive all GLAS Production Data Sets (PDSs) on
           physical media (D3 tapes) at the Data Archive Facility (DAF)
           located at White Sands, New Mexico.
  -------- --------------------------------------------------------------

## EDOS ICESat Mission Performance Reqirements

  -------- --------------------------------------------------------------
  2.1      EDOS shall provide frame synchronization for ICESat high rate
           return link data at rates up to 40 Mbps from one physical
           channel.

  2.2      EDOS shall provide processing support to produce GLAS PDSs
           from single spacecraft contact sessions at the average
           incoming data rate of 500 kbps per orbit.

  2.3      EDOS shall provide processing support to produce GLAS EDSs
           from single spacecraft contact sessions for selected data at
           the average data volume of 2% of production data set volume.

  2.4      EDOS shall deliver GLAS PDSs to the GSFC DAAC, within 24 hours
           of receipt of all appropriate input data at GSFC.

  2.5      EDOS shall deliver GLAS EDSs to the GSFC DAAC, within 3 hours
           of receipt of all appropriate input data at GSFC.

  2.6      EDOS shall provide frame synchronization for ICESat low rate
           return link playback data at rates up to 262.144 kbps from one
           physical channel.

  2.7      The LZPF shall initiate the transfer of rate buffered data to
           a destination within 5 minutes after receipt of all of the
           data for the rate buffering session.

  2.8      The LZPF shall have an MTTR of 2 hours or less for all
           functionality required to support non-real-time mission data
           handling.

  2.9      The LZPF shall have an operational availability of 0.998 or
           greater to support non-real-time mission data handling.
  -------- --------------------------------------------------------------

## Data Products Latency Requirements

The following table summarizes the latency requirements for S-band and
X-band data.

![](media/image1.wmf)

1.  During the calibration & validation phases (\~L+120 days), select
    science products shall be delivered by EGS to the ISF within 1 hour
    of receipt at the ground station.

2.  The EDOS shall extract and deliver to the FDS the GPS data packets
    within 6 hours of X-band contact at EPGS.

# ISIP

ISIP shall:

1.  Receive Production Data Set (PDS) and Expedited Data Set (EDS) from
    EDOS.

2.  Produce Level 1 and Level 2 Standard Data Products.

3.  Deliver Level 1 and Level 2 Standard Data Products to the NSIDC and
    GLAS SCF.

4.  Provide L0 data to ISF as required.

# Science Data Archival & Distribution

NSIDC DAAC shall:

1.  Accept Level 0 production data sets from EDOS.

2.  Accept Level 1 and Level 2 Standard Data Products from the ISIPS
    Facility.

3.  Provide a permanent archive of Level 0, Level 1 and Level 2 data
    products.

4.  Maintain a Database of all data products in the Archive.

5.  Update the Archive and the Database when reprocessed products are
    received and accepted.

6.  Accept requests from the user community for specific data products.

7.  Distribute data products to the user community as requested.

8.  

# ESDIS Integration and Test.

## ESDIS Project shall be responsible for integrating EBNet, EDOS, EDOS and NSIDC DAAC in support of the ICESat mission. {#esdis-project-shall-be-responsible-for-integrating-ebnet-edos-edos-and-nsidc-daac-in-support-of-the-icesat-mission. .unnumbered}

#  {#section-10 .unnumbered}

# BASD Sustaining Engineering Requirements

## Engineering Data Archive

BASD shall maintain a permanent archive of all spacecraft engineering
data, including schematics, specifications, operations manuals and
drawings that are necessary to trouble-shoot and maintain the spacecraft
during on-orbit operations. This data archive is to be maintained at
BASD under configuration management for the life of the mission.

## Integration & Testing Activities

BASD shall schedule support for the following major ground system tests.

  ----------------- ----------------- -----------------------------------
  GSCT \#           S/C Activity --   Approximate Month/Year
                    ICEsat            

  #1: Basic Tlm,    S/C Bus           4/00
  command           performance Test  

  #2: RF Tlm, CMD   Transmitter, SSR\ 6/00
                    *with CTV*        

  #3: Instrument    Post electrical   12/00
  Ops               Integration       
                    CPT/APT           

  #4: Full ETE Dry  Post Thermal Vac  1/01
  Run                                 

  #5: Full ETE      Post Thermal Vac  2/01 and 4/01

  #6: Launch Site   Align SFF         6/01
  ETE                                 

  #7: Pad ETE       Payload Aliveness 7/00
                    and ESDIS         
  ----------------- ----------------- -----------------------------------

## Sustaining Engineering Support

### Anomaly Resolution

BASD shall provide anomaly resolution support to resolve any Observatory
anomalies that may occur from launch through mission end-of-life (EOL).
This includes supporting the development of any Observatory operating
contingencies resulting from unplanned changes in the mission operations
baseline (e.g., changes in orbit, power, subsystem degradation, etc.)
and to support the resolution of anomalies such as software errors, out
of tolerance parameters, etc., and providing expert consultation to the
FOT.

### Trending & Analysis

BASD shall provide capabilities to trend and analyze key Observatory
parameters. This includes any trending or analysis of the Observatory's
operating and health & safety conditions, especially when needed in
support of anomaly resolution. This also includes trending and analysis
to support planned Observatory flight configuration changes, including
raising from calibration to mission orbit, transition to first full
eclipse season, and executing required yaw transitions.

### Software Maintenance

BASD shall provide FSW maintenance. This shall include the maintenance
of development and test beds and providing expertise to modify, test,
and deliver any uploadable spacecraft FSW or parameters that may be
required during mission life BASD shall deliver the modified FSW /
tables / parameters to the MOC for upload to the spacecraft.

NOTE: Although FSW source code shall be delivered to the Government, the
Government will not modify any FSW code.

### Maintain Flight Software Test Bed

The provisions for the Flight Software Test Bed (FSTB) shall be as
follows:

1.  The FSTB shall remain resident at BASD to EOL.

2.  The FSTB shall be dedicated to the ICESat mission to EOL

3.  The FSTB shall be accessible for off-line FOT training and FSW
    validation purposes with the MOC on a scheduled basis to EOL.

4.  BASD shall maintain the FSTB to EOL.

5.  BASD shall remain technically cognizant and technically competent in
    the operation of the ICESat FSW and the FSTB to EOL.

# GLAS Instrument Developer Requirements

Code 924, the GLAS Instrument Developer, shall provide the following
functions and services to support the ICESat operations.

## Instrument Operations Training

Code 924 shall provide training for the Instrument Operations Team (IOT)
and Flight Operations Team (FOT) personnel in instrument operations and
maintenance. This shall include the development of written training
materials, providing formal classroom training, and on-the-job training
(OJT) during instrument and observatory Integration & Test (I&T) to a
level deemed sufficient by the organizations to be trained to transfer
operational knowledge of the GLAS Instrument to these operations
personnel.

[Classroom Training]{.underline}

Code 920 shall provide formal classroom training to the IOT and the FOT.
This shall include a video taped session, training materials, and
documentation.

[On the Job Training (OJT)]{.underline}

At the GLAS I&T facility at GSFC, the IOT and FOT shall have access to
the GLAS instrument in an observation capacity during key phases of the
GLAS I&T process. These observation sessions shall serve to familiarize
the IOT/FOT with the flight hardware.

## Documentation

GLAS developer shall provide operations documentation that includes:

1.  GLAS Operations Manual

2.  GLAS Flight Software Manual

## Integration & Testing Activities

GLAS developer shall participate in end-end science data flow tests with
the ground system prior to launch. This includes supporting any
simulations and dress rehearsals for the analysis of instrument science
and engineering data, and to support the development of the ISF for
instrument operations and to support the development of the MOC/FOT for
nominal observatory level operations.

## On-Orbit Check-out & Transition Activities

1.  Code 924 shall support the on-orbit check-out and transition phases.

2.  Code 924 shall provide personnel to be resident at the MOC to
    support the FOT/IOT during on-orbit check-out of the ICESat bus and
    the GLAS instrument.

3.  Code 924 personnel shall monitor telemetry and approve all commands
    sent to the Observatory during this phase.

## Calibration and Validation Support

Code 924 shall support the Calibration and Validation (C&V) Phase. C&V
support includes analysis and evaluation of on-orbit GLAS performance.

## Engineering Data Archive

1.  Code 924 shall maintain a GLAS Engineering Data Archive to include
    all schematics, specifications, operations manuals, drawings, and
    test results that are necessary to trouble-shoot and maintain the
    instrument during on-orbit operations.

2.  This archive shall to be maintained under configuration management
    for the life of the mission.

## Instrument Sustaining Engineering

Code 924 shall provide the following sustaining engineering functions
for the life of the ICESat mission.

### Anomaly Resolution Support

Code 924 shall provide Anomaly Resolution Support to resolve any GLAS
Instrument anomalies that may occur from launch through mission
end-of-life (EOL). This includes supporting the development of any
instrument operating contingencies resulting from unplanned changes in
the mission operations baseline (e.g., changes in orbit, power,
subsystem degradation, etc.) and to support the resolution of anomalies
such as software errors, out of tolerance parameters, etc., and
providing expert consultation to the IOT/FOT.

### Trending & Analysis

Code 924 shall provide Trending & Analysis of key GLAS parameters. This
includes any trending or analysis of GLAS operating and health & safety
conditions, especially when needed in support of anomaly resolution.
This also includes trending and analysis to support planned GLAS flight
configuration changes (such as laser switching or altimetry detector
switching) and any calibration and validation support required to
support these activities.

### Software Maintenance

Code 924 shall provide GLAS Flight Software (GFSW) Maintenance. This
includes maintaining GFSW development and test beds and providing
expertise to modify, test, and deliver any uploadable FSW or parameters
that may be required during mission life.

# Science Team Requirements

-   The Science Team (ST) shall provide the reference ground track to be
    flown during the 8-day repeat orbit and the 183-day repeat orbit

-   The launch window shall be coordinated with the ST

-   The prelaunch observatory center of mass location, location of a
    reference point on theGPS antennas and their orientation with
    respect to defined spacecraft or instrument axes, the location of
    the SLR reflector and the location of the instrument reference point
    shall be provided to the ST

-   GPS antenna phase center variation as a function of azimuth and
    elevation

-   Specular and diffuse reflectivity characteristics of the observatory

    Postlaunch Information

-   The ST shall review and provide changes to the reference ground
    track

-   The ST shall review and recommend changes to the orbit
    characteristics that may result from anomalous orbit insertion

-   The start and completion of the calibration/validation (C/V) phase
    and the 8-day repeat orbit shall be determined by the ST. Under
    nominal conditions, the start of the cal/val phase will occur within
    several (TBD) days of GLAS power-on and shall extend for up to
    120-days after this event.

-   The ST, in collaboration with other mission elements, such as the
    Instrument Team, shall organize a calibration/validation readiness
    review prior to start of the C/V phase.

-   The ST, in collaboration with other mission elements, such as the
    Instrument Team, shall organize a mid-term C/V review to assess
    status and performance in support of the science objectives

-   The ST, in collaboration with other mission elements, such as the
    Instrument Team, shall organize a main mission readiness review

-   The ST, in collaboration with other mission elements, shall
    periodically organize status and performance reviews in support of
    the science objectives

-   Orbit maintenance and other thrust maneuvers shall be coordinated
    with the ST.

-   Yaw and special attitude maneuvers shall be coordinated with the ST.

-   Off-nadir pointing plans shall be provided by the ST and other
    recommendations shall be coordinated with the ST

-   Data from the spacecraft star tracker shall be provided to the ST

-   The ST shall be the interface to the International Laser Ranging
    Service

-   Data from the operating GPS receiver shall be available with a
    latency of about 6 hours

-   Data from the instrument star camera shall be available with a
    latency of less than 6 hours

-   Solar panel articulation history shall be provided to the ST with a
    latency of less than one day

-   The time history of the changes in observatory mass properties shall
    be provided to the ST

-   Thermal data from the observatory, including the instrument

[]{#__RefHeading___Toc460824792 .anchor}Appendix

**Acronyms**

AD Attitude Determination

AGS Alaska Ground Station

AOS Acquisition of Signal

BAP Baseline Activity Plan

BASD Ball Aerospace Systems Division

C&V Calibration & Validation

CCSDS Consultive Committee for Space Data Systems

CMD Command

CTV Compatibility Test Van

DAAC Distributed Active Archive Center

Delta V Delta Velocity (budget)

DMR Detailed Mission Requirements

DSU Data Storage Unit

Ebnet EOSDIS Backbone Network

EDOS EOS Data and Operations System

EOC EOS Operations Center

EOL End-of-Life

EOS Earth Observing System

EOSDIS EOS Data Information System

EPGS EOS Polar Ground Station

ESDIS Earth Sciences Data Information Systems

ETE End-to-End

FDR FDS Design Review

FDS Flight Dynamics System

FDSTP FDS Test Plan

FEICD FDS External Interface Control Document

FMECA Failure Modes and Effect Analysis

FOT Flight Operations Team

FOV Field of View

FRR Flight Readiness Review

FSTB Flight Software Test Bed

FSW Flight Software

FTP File Transfer Protocol

G&N Guidance & Navigation

GFSW GLAS Flight Software

GLAS Geoscience Laser Altimeter System

GPS Global Positioning System

GSCT Ground System Compatibility Test

GSEF GLAS Sustaining Engineering Facility

GSFC Goddard Space Flight Center

GSMF GLAS Software Maintenance Facility

HVAC Heating, Ventilation, and Cooling

I&T Integration & Test

ICD Interface Control Document

ICESat Ice, Cloud, and Land Elevation Satellite

IGS ICESat Ground System

IOT Instrument Operations Team

IRU Inertial Reference Unit

ISF Instrument Support Facility

ISF Instrument Support Facility

ISIPS ICESat Science Investigator Processing System

Kbps Kilo Bits Per Second

km Kilometers

LASP Laboratory for Astronomy and Solar Physics

LRR Launch Readiness Review

LZDP Level Zero Data Processing

Mbps Mega Bits Per Second

MDR Mission Design Review

MOC Missions Operations Center

MODIS

MOR Mission Operations Review

MORD Mission Operations Requirements Document

MOSR Mission Operations Status Review

NASA National Aeronautics & Space Administration

NISN NASA Integrated Support Network

NSIDC National Snow & Ice Data Center

OA Operational Attitude

OASIS Operations and Science Instrument Support

OD Orbit Determination

OJT On-the-Job Training

OOD Operational Orbit Determination

ORR Operations Readiness Review

PB Playback (data)

PDS Production Data Sets (EDOS)

POD Precision Orbit Determination

R/T Real Time (data)

RF Radio Frequency

S/C Spacecraft

SCC Spacecraft Control Computer

SCF Science Computing Facility

SLR Satellite Laser Ranging

SOMO Space Operations Management Office

SSEF Spacecraft Sustaining Engineering Facility

SSR Solid State Recorder

SSST Solid State Star Tracker

ST Science Team

TBD To be Determined

Tlm Telemetry

TT&C Tracking, Telemetry & Control

UT University of Texas

WFF Wallops Flight Facility

WGS Wallops Ground Station

WOTIS Wallops Orbital Tracking Information System

##  

##