# Presentation: 287395

## NMP / EARTH ORBITER-1 MISSION

***NMP / EARTH ORBITER-1 MISSION***
***Delta Mission***
***Operations Review***
***1/28/99***

## Agenda (1 of 2)

**Introduction****	**Dan Mandl	8:30
**Mission Description****	**Dan Mandl	8:30
**Ground System Status**
- Introduction	Dan Mandl	9:35
- Facilities	Dan Mandl	9:45
- RFA Status	Dan Mandl	9:50
- Ground and Space Networks	Paul Garza	9:55
- Core Ground System (CGS)	Dan Grogan	10:00
- DPS	Dan Mandl	10:05
- MOPSS	Joe Gvozdas	10:10
- FDSS	Bob Defazio	10:25
- MSO / SVF	Tom Brakke	10:40
**Break****	****	****10:45**
**Operations Overview**
- High Level Ops Concept / Operations Philosophy	Joe Howard	11:00
- Operations Status	Joe Howard	11:10
- Ops Testing	Joe Howard	11:15
- Documentation Overview	Joe Howard	11:35
- Contingency Operations	Joe Howard	11:45

- Speaker

- Time

## Agenda (2 of 2)

**Lunch****	****	****12:00**
**Mission Management****	**Joe Howard	1:00
**Automation**	Joe Howard	1:25
**Launch and Early Orbit Operations****	**Alicia Kost	1:40
**Break****	****	****2:05**
**Integrated Normal Operations****	**
- Overview	Joe Howard	2:20
- Planning and Scheduling	Joe Howard	2:15
- DCEs / Science Operations	Joe Howard	2:30
- FDSS Operations	Seth Shulman	2:45
- Spacecraft Command and Control	Alicia Kost	3:10
- New Technology Validation Operations	Alicia Kost	3:20
**Issues and Concerns**	Joe Howard	3:50
**Adjourn****	****	****4:15**

- Speaker

- Time

## Table Of Contents

**Introduction****	****5**
**Mission Description****	****7**
**Ground System Status****	****59**
- Introduction	60
- Facilities	68
- RFA Status	76
- Ground Stations and Networks	78
- Core Ground System (CGS)	81
- DPS	101
- MOPSS	108
- FDSS	116
- MSO / SVF	127
**Operations Overview****	****132**
- High Level Ops Concept / Operations Philosophy	133
- Operations Status	136
- Ops Testing	137
- Documentation Overview	150
- Contingency Operations	153
**Mission Management****	****156**
**Automation**	162
**Launch and Early Orbit Operations****	****165**
**Integrated Normal Operations****	****183**
- Overview 	184
- Planning and Scheduling	186
- DCEs / Science Operations	188
- FDSS Operations	196
- Spacecraft Command and Control	210
- New Technology Validation Operations	217
**Issues and Concerns**** ****	****239**
**Acronym List****	****241**
**Back Up Slides****	****244**

- Page Number

## Introduction

**D. Mandl**

## Purpose of Review

**To assess the ground team’s ability to develop the remaining capabilities to get to launch**
**To assess the viability of the operations plan**

**Introduction**

## Mission Description

**D. Mandl**

## Mission Overview

**Mission Overview**

**Validate revolutionary technologies contributing to the reduction of cost and increased capabilities for future land imaging missions**
**Revolutionary land imaging instruments on EO-1**
- Hyperion
- Advanced Land Imager (ALI)
- Atmospheric Corrector (AC)

**Revolutionary Spacecraft technologies on EO-1**
- X Band Phased Array Antenna (XPAA)
- Pulse Plasma Thruster (PPT)
- Light Weight Flexible Solar Array (LFSA)
**More on website:  eo1.gsfc.nasa.gov**

- Carbon-Carbon Radiator (CCR)
- Enhanced Formation Flying (EFF)

**Mission Description**

## Mission Overview

**Launching December 15, 1999 from Vandenberg Air Force Base on a Delta launch vehicle**
**Orbit: 705 km circular sun synchronous, 98.2 degree inclination**
**Flies one minute behind Landsat and collects nearly identical images for comparison purposes**

**Mission Overview**

**For each image collected**
- Approximately 13 Gbits of scene data from Hyperion, ALI and AC is collected and stored on the on-board solid state data recorder at high rates
- When in range of ground station, data is transmitted to ground and forwarded via tape to GSFC for analysis and validation by EO-1 science and technology teams

**Mission Description**

## Pictorial Overview of Science Objectives

**Pictorial Overview of Science Objectives**

**Mission Description**

## EO-1 Spacecraft Deployed Layout

**Mission Description**

## EO-1 Instruments and Technologies

**Mission Description**

## EO-1 Avionics Configuration

**RS-422**

**Mission Description**

**ADVANCED LAND IMAGER (ALI)**

**Multispectral Imaging Capability**
**Wide Field of View Reflective Optics **
**Silicon Carbide Optics **

**ATMOSPHERIC CORRECTOR (AC)**

**Wide Band**
**Advanced**
**Recorder /**
**Processor**

**X-Band**
**Phased Array**
**Antenna**

**C&DH**
**S-Band**
**Antenna**

**G**
**R**
**O**
**U**
**N**
**D**

**Enhanced Formation Flying**

**Pulse Plasma Thruster**

**Attitude Control System**

**Carbon-Carbon Radiator**

**GPS**

**Precision**
**Pointing**

**Lightweight Flexible Solar Array**

_**EO-1 TECHNOLOGIES**_
*Multispectral Imaging Capability*
*Wide Field of View Reflective Optics*
*Silicon Carbide Optics*
*Grating Imaging Spectrometer (Hyperion)*
*Atmospheric Corrector (AC)*
*X-Band Phased Array Antenna*
*Enhanced Formation Flying (EFF)*
*Pulse Plasma Thruster (PPT)*
*Carbon-Carbon Radiator (CCR)*
*Lightweight Flexible Solar Array (LFSA) *
*Wideband Advanced Recorder / Processor (WARP)*
*Global Positioning System (GPS)*
*Precision Pointing*

**HYPERION**
**Hyperspectral Grating Imaging Spectrometer**

**EO-1 Technologies**

**Mission Description**

## ALI Flight Instrument

**Mission Description**

## Key ALI Significant Characteristics

**Multispectral and Panchromatic, 10 bands, 0.4 to 2.5 um**
**30 m resolution (10 m Pan band)**
**36 Km swath width, Push-broom**
**Lightweight Silicon Carbide Optics**
**SNR 100-200, depending on band, 5% reflectance**
**High temperature focal plane, 220K**
**Solar, lunar, and lamp calibration**
**Zero Fault tolerant**
**Simple spacecraft mechanical, electrical, and thermal interfaces**

**Mission Description**

## Hyperion Baseline DesignInstrument Subsystem Units

**HEA**

**CEA**

**HSA**

**Mission Description**

## Key Hyperion Significant Characteristics

**Hyperspectral, 220 bands, 0.4 to 2.5 um**
**30 m resolution**
**7.5 Km swath width**
**SNR ~60, depending on frequency**
**1 year life, 2 year goal**
**Aligned to be within the Panchromatic Band of the inboard ALI Sensor Chip Assembly**
**Solar, lunar, and lamp calibration**
- Radiometric cross-calibration with the ALI before launch planned
**Zero Fault tolerant**
**Simple spacecraft mechanical, electrical, and thermal interfaces**

**Mission Description**

## X-Band Phased Array Antenna (XPAA)

**Technology Need:**
- High rate, reliable RF communication subsystems
**Description:**
- The X-band phased array antenna is composed of a flat grid of many radiating elements whose transmitted signals combine spatially to produce desired antenna directivity (gain)
- Avoids problems of deployable structures and moving parts
- Lightweight, compact, supports high downlink (100’s Mbps) rates.
- Allows simultaneous instrument collection and data downlink.
**Validation:**
- The XPAA will be validated through measurement of bit error rate performance and effective ground station EIRP during science data downlinks over the lifetime of the mission.
**Benefits to Future Missions:**
- Future Earth Science missions will be extremely compact but will produce tera-bit daily data streams.  The Phase Array  antenna technology will enable:
- Lower cost, weight and higher performance science downlinks
- Lower cost and size  ground stations
- More flexible operations

**Status:**
- XPAA has been delivered to GSFC and tested with RF Exciter at Litton successfully,
- Delivered.
**Commercial Partners:**
- Boeing Phantom Works

**X-Band Phased Array Antenna (XPAA)**

**Mission Description**

## Enhanced Formation Flying (EFF)

**Status:**** **
- EFF software  delivered and successfully integrated and  tested in flight software development system.
- GPS flight unit has been successfully tested and was integrated onto S/C in Nov 1998.
**Partners:**
- JPL,GSFC, Hammers

**Technology Need:**
- Constellation Flying
**Description:**
- The enhanced formation flying (EFF) technology features flight software that is capable of autonomously planning, executing, and calibrating routine spacecraft maneuvers to maintain satellites in their respective constellations and formations.
**Validation:**
- Validation of EFF will include demonstrating on-board autonomous capability to fly over Landsat 7 ground track within a +/- 3km while maintaining a one minute separation while an image is collected.
**Benefits to Future Missions:**
- The EFF technology enables many small, inexpensive spacecraft to fly in formation and gather concurrent science data in a “virtual platform.”
- This “virtual platform” concept lowers total mission risk, increases science data collection and adds considerable flexibility to future Earth and space science missions.

**Mission Description**

## Lightweight Flexible Solar Array (LFSA)

- Increase payload mass fraction.
**Description:**
- The LFSA is a lightweight photovoltaic(PV) solar array which uses thin film CuInSe2 solar cells and shaped memory hinges for deployment. Chief advantages of this technology are:
- Greater than 100Watt/kg specific energies compared to conventional Si/GaAs array which average 20-40Watts/kg.
- Simple shockless deployment mechanism eliminates the need for more complex mechanical solar array deployment systems.  Avoids harsh shock to delicate instruments.
**Validation:****     **
- The LFSA deployment mechanism and power output will measured on-orbit to determine its ability to withstand long term exposure to radiation, thermal environment and degradation due to exposure to Atomic Oxygen.
**Benefits to Future Missions:**
- This technology provides much higher power to weight ratios (specific energy) which will enable future missions to increase science payload mass fraction.

**Status:**
- The LFSA was delivered to Swales for S/C Integration and Testing in early September.
**Partners**
- Phillips Lab, Lockheed Martin (Boulder Co)

**Lightweight Flexible Solar Array (LFSA)**

**Mission Description**

## Pulse Plasma Thruster (PPT)

- PPT flight unit (above) was delivered to Swales for S/C Integration and testing in mid-September.
-  Electrical integration successful in mid-December
**Partners**
**LeRC, Primex, GSFC**

**Technology Need:**
- Increase instrument payload mass fraction.
**Description:**
- The Pulse Plasma Thruster is a small, self contained electromagnetic propulsion system which uses solid Teflon propellant to deliver high specific impulses (900-1200sec), very low impulse bits (10-1000uN-s) at low  power making. Advantages of this approach include:
- Ideal candidate for a low mass precision attitude control device.
- Replacement of reaction control wheels and other momentum unloading devices.  Increase in science payload mass fraction.
- Avoids safety and sloshing concerns for conventional liquid propellants
**Validation:****     **
- The PPT will be substituted (in place of a reaction wheel) during the later phase of the mission.  Validation will include:
- Demonstration of the PPT to provide precision pointing accuracy, response and stability.
- Confirmation of benign plume and EMI effects
**Benefits to Future Missions:**
- The PPT offers new lower mass and cost options for fine precision attitude control for new space or earth science missions

**Pulse Plasma Thruster (PPT)**

**Mission Description**

## Carbon-Carbon Radiator

- Increase instrument payload mass fraction.
**Description:**
- Carbon-Carbon is a special composite material that uses pure carbon for both the fiber and matrix. The NMP Earth Orbiter – 1 mission will be the first use of this material in a primary structure, serving as both an advanced thermal radiator and a load bearing structure  Advantages of Carbon-Carbon include:
- High thermal conductivity including through thickness
- Good strength and weight characteristics
**Validation:**** **
- EO-1 will validate the Carbon-Carbon Radiator by replacing one of six aluminum 22” x27” panels with one constructed using the C-C composite materials. Mechanical and thermal properties of the panels will be measured and trended during environmental testing and on-orbit to validate its operation for future earth and space science missions.
**Benefits to Future Missions:**
- This technology offers significant weight reductions over conventional aluminum structures allowing increased science payload mass fractions for Earth Science Missions.  Higher thermal conductivity of C-C allows for more space efficient radiator designs.

**Carbon-Carbon Radiator**

**Status:**
- Panels successfully integrated with PSE in Oct 1998
**Partners**
- CSRP (consortium)

**Mission Description**

## Atmospheric Corrector

**Description:**
- Earth imagery is degraded by atmospheric absorption and scattering. The EO-1 mission will provide the first space based test of an AC for increasing the accuracy of surface reflectance estimates.
- The AC provides the following capabilities via a compact and simple bolt on design for future Earth Science, land imaging missions:
- High spectral, moderate spatial resolution hyperspectral imager using a wedge filter technology
- Spectral coverage of .85-1.5 um, bands are selected for optimal correction of high spatial resolution images.
- Correction of surface imagery for atmospheric variability (primarily water vapor)
**Validation:**
- Ground validation of AC data using selected areas of globe where little surface variation exists but atmospheric variability changes. Also comparison of AC data with radiosondes, and other satellites sounders.
**Benefits to Future Missions:**
- The AC Instrument will provide significant improvements in generating accurate reflectance measurements for land imaging missions.
- The algorithms developed will enable more accurate measurement and classification of land resources and better predictive models for land management in the future.

**Atmospheric Corrector**

**Status:**** **
- Atmospheric Corrector Optics and Electronics Modules have been successfully integrated and tested together.  Detector characterization testing under vacuum and temperature will commence on February 4th.

**Mission Description**

## Wideband Advanced Processor Recorder (WARP) 

**Wideband Advanced Processor Recorder (WARP) **

**Partners:**
- Litton Amecom

**Technology Enabler**
**Description:**
- High Rate (up to 840Mbps capability), high density (48Gbit storage), low weight (less than 25.0 Kg) Solid State Recorder/Processor with X-band modulation capability.
- Utilizes advanced integrated integrated circuit  packaging (3D stacked memory devices) and “chip on board” bonding techniques to obtain extremely high density memory storage per board (24Gbits/memory card)
- Includes high capacity Mongoose 5 processor which can perform on-orbit data collection, compression and processing of land image scenes.
**Validation:**
- The WARP is a critical subsystem on the EO-1 mission and is required for mission success.
**Benefits to Future Missions:**
- The WARP will validate a number of high density electronic board advanced packaging techniques and will provide the highest rate solid state recorder NASA has ever flown.
- Its basic architecture and underlying technologies will be required for future earth imaging missions which need to collect, store and process high rate land imaging data.

**Status:**** **
- First WARP first full box level test was successfully completed on Jan 7-8th.  After minor rework of WARP boards, high temperature testing will be conducted on Jan 25 - 28 to test worst case timing.

**Mission Description**

## Stennis & TRW Involvement

- TRW
- Checkout of Hyperion
- Assist in validation of Hyperion
- Level 1 processing of Hyperion data
- Details in draft GSFC/TRW ICD
- Stennis
- Commercialize Hyperion data
- Level 1 Hyperion data processing
- Details in GSFC/Stennis MOU

**Mission Description**

## EO-1 Pre-Launch Organization

*Nick Speciale*

**MISSION TECHNOLOGIST**
**Code 730**

*Dale Schulz*

**MISSION MANAGER**
**Code 426**

*Dr. Stephen Ungar*

**MISSION SCIENTIST**
**Code 923**

*Pete Spidaliere*

**MISSION SYSTEMS ENGINEER**
**Code 730**

*Dr. Matt Jurotich*

**INTERFACE ENGINEER**
**Code 730**

**ALI**
**INSTRUMENT MGR**
**Code 740**

*Tom Gostomski*

**I&T**
**MANAGER**
**Code 568  **

* *

*Ralph Welsh*

**Mission Description**

- GROUND SYSTEM
- DEVELOPMENT
- MANAGER
- Code 584
*Dan Mandl*

## EO-1 Ground Development Organization

- Ground System Engineer, MOPSS - R. Harbaugh/581

- FDSS - B. DeFazio/572,S. Godfrey/583, R. Luquette/572

- Core Ground System - D. Grogan/Raytheon/581

- Data Processing System - M. Forman/584,  L. Alexander/DEC

- Networks & SOMO Services - P. Garza/453

- FOT - J. Howard (ATSC)

**EO-1 Ground Development Organization**

**Mission Description**

## EO-1 Organization for Launch and 1st Few Days

**Decision**
**Team**

**Project Manager**
**D. Schulz**
**P. Spidaliere**
**J. Thurber**

- Spacecraft Subsystem Engineers

- Instrumenters

**Mission Description**

- Mission Director
- Code 584
-  D. Mandl
-  Shift representative

- FOT
-  J. Howard
-  B. Trout

## EO-1 Organization for Launch and 1st Few Days (Decision Flow)

**Routine or documented contingency procedures executed by MD/FOT without need for management approval**
**Problems that are not time critical solved by pulling a “tiger team” together**
- Spacecraft related - D. Schulz, P. Spidaliere, J. Thurber coordinate on separate shifts
- Ground related - D. Mandl and other shift MDs coordinate
**Problems that are time critical (non routine or non documented contingency)**
- Lead Project Manager uses on-site technical expertise to identify solution to safe the spacecraft as rapidly as possible, safing priority over solving problems

**Mission Description**

## EO-1 Organization Post Launch (Checkout)

**Project Manager**
**426**
**Dale Schultz**

- Spacecraft Subsystem Engineers

*Joe Howard*

- FOT

**Mission Description**

- Mission Director
- Code 584
- Dan Mandl

- Mission Technologist
- Code 730
- Nick Speciale

- Mission Scientist
- Code 923
- Dr. Stephen Ungarl

## EO-1 Organization Post Launch (Checkout) (Decision Flow)

**EO-1 Organization Post Launch (Checkout) (Decision Flow)**

**Routine or documented contingency procedures executed by MD/FOT without need for management approval**
**Problems that are not time critical solved by pulling a “tiger team” together**
- Spacecraft related - D. Schulz, P. Spidaliere, J. Thurber coordinate on separate shifts
- Ground related - D. Mandl and other shift MDs coordinate
- Technology - N. Speciale coordinates
- Instruments - S. Ungar coordinates
**Problems that are time critical (non routine or non documented contingency)**
- Lead Project Manager uses on-site technical expertise to identify solution to safe the spacecraft as rapidly as possible, safing priority over solving problems

## EO-1 Organization Post Launch During Normal Ops

**EO-1 Organization Post Launch During Normal Ops**

*B. Cramer*

**NMP Imp MANAGER**
**Code 426**

*Joe Howard*

- FOT

- **Note that post-launch org may go under some other org than 426

- S/C Subsystem
-  Engineers

- Flight S/W
- Maintenance

- Mission Director
- Code 584
- Dan Mandl

- Mission Technologist
- Code 730
- Nick Speciale

- Mission Scientist
- Code 923
- Dr. Stephen Ungarl

**Mission Description**

## EO-1 Organization Post Launch (Normal Operations) (Decision Flow)

**EO-1 Organization Post Launch (Normal Operations) (Decision Flow)**

**Routine or documented contingency procedures executed by MD/FOT without need for management approval**
**Problems that are not time critical solved by pulling a “tiger team” together**
- Spacecraft related - D. Schulz, P. Spidaliere, J. Thurber coordinate on separate shifts
- Ground related - D. Mandl and other shift MDs coordinate
- Technology - N. Speciale coordinates
- Instruments - S. Ungar coordinates
**Problems that are time critical (non routine or non documented contingency)**
- Lead Project Manager uses on-site technical expertise to identify solution to safe the spacecraft as rapidly as possible, safing priority over solving problems

## FOT Staffing Profile

- *Note that during L&EO, the FOT is supplemented by 3 test conductors for about 30 - 60 days

**Mission Description**

## Experienced team
Flat structure / everyone contributes equally
Leo McConville		20 years 	NRL, Sampex, FAST, TRMM
Bruce Trout		15 years	SMM, RME, FAST, SOHO, 							RadarSat, ROCsat
Tom Berry		15 years	SMM, DE, GRO
Joe Howard		13 years	COBE, ERBS, GRO, RadarSat
Seth Shulman		10 years	UARS, EUVE, XTE, TOMS EP
Alicia Kost		7 years	COBE, SWAS, ROCsat, 							operational software testing
Tom Moore		7 years	ERBS, SWAS, SOHO

**Flat structure / everyone contributes equally**
- Leo McConville		20 years 	NRL, Sampex, FAST, TRMM
- Bruce Trout		15 years	SMM, RME, FAST, SOHO, 							RadarSat, ROCsat
- Tom Berry		15 years	SMM, DE, GRO
- Joe Howard		13 years	COBE, ERBS, GRO, RadarSat
- Seth Shulman		10 years	UARS, EUVE, XTE, TOMS EP
- Alicia Kost		7 years	COBE, SWAS, ROCsat, 							operational software testing
- Tom Moore		7 years	ERBS, SWAS, SOHO

**FOT Experience**

**Mission Description**

## FOT Tasking Allocations

**Mission Description**

- *Note: Time measurement is man days

## Operations / Test Team Integration

**Operations / Test Team Integration**

**ASIST is system used in both I&T and Ops**
**FOT presently heavily involved with I&T as test conductors (6 members of the 7 member FOT working as test conductors)**
- FOT writing many of the I&T procedures
- FOT are the majority of the test conductors at this time
- FOT learning how to operate spacecraft on operations system early

## Integrated Operations Team - Flight Software Interaction

**Integrated Operations Team - Flight Software Interaction**

**FOT interact daily with flight software leads for changes needed for both Operations and I&T as needed**
- Many test procedures for Mission Readiness Tests and Mission Simulations derived from I&T tests, adjusted for things such as ground station interfaces and operations procedures
- I&T testing philosophy is to test spacecraft as it will be operated
**FOT interacting with spacecraft system engineer to ascertain which procedures should be flight Telemetry and Statistics Monitor (TSM) procedures and which should be ground procedures**
**FOT derive many operational procedures from the I&T procedures they use for testing**
**FOT also the testers for ground**

## EO-1 Test Approach

**Seamlessly integrated with I&T test plan**
**Most of the Mission Readiness Tests will capture spacecraft opportunities and hopefully be complete before the due date**
**Building a spacecraft processor board for use as simulator by FOT in testing and Operations Preparation**
- Spacecraft processor will have the real flight software
- Pre-launch used to augment tests when spacecraft is not available
- Post launch FOT will use to practice procedures on ground that will be used to fix anomalies

**Mission Description**

## Operations Working Groups (OWG)
OWG #1  Normal Operations 	11/5/98
OWG #2  Launch and Early Orbit	12/4/98
OWG #3  Roles and Responsibilities	1/7/99
OWG #4  S/C Contingency Operations 	3/99
OWG #5  Instrument and Technology Contingency Os	4/99
OWG #6  Trending Approach	5/99
All lessons learned from I&T and Ops plans recorded in Mission Procedures Document
Vol 1 - Operations Concepts
Vol 2 - Detailed Operations Plan

- OWG #1  Normal Operations 	11/5/98
- OWG #2  Launch and Early Orbit	12/4/98
- OWG #3  Roles and Responsibilities	1/7/99
- OWG #4  S/C Contingency Operations 	3/99
- OWG #5  Instrument and Technology Contingency Os	4/99
- OWG #6  Trending Approach	5/99
**All lessons learned from I&T and Ops plans recorded in Mission Procedures Document**
- Vol 1 - Operations Concepts
- Vol 2 - Detailed Operations Plan

**Operations Development Approach**

**Mission Description**

## Working on allocating procedures between TSMs and ground procedures
Ground procedures
90% reuse
Expect that less than 30 new ones need to be developed
Displays
No new displays identified
Developed in I&T (many by FOT)
Database - reused from I&T

**Ground procedures**
- 90% reuse
- Expect that less than 30 new ones need to be developed
**Displays**
- No new displays identified
- Developed in I&T (many by FOT)
**Database - reused from I&T**

**Operations Development Approach - Normal Ops Planning**

**Mission Description**

## Automation
Prepass - MOPSS
FOT populates scenarios
Use after L&EO
Estimate 1 man month effort
Pass
MOPSS drives STOL procedures w/feedback
Spacecraft Emergency Response System (SERS) notifies FOT member if there is problem
Estimate 1 man month to populate both
Post pass
DPS - manual set of activities
Trending
No additional effort identified

- Prepass - MOPSS
- FOT populates scenarios
- Use after L&EO
- Estimate 1 man month effort
- Pass
- MOPSS drives STOL procedures w/feedback
- Spacecraft Emergency Response System (SERS) notifies FOT member if there is problem
- Estimate 1 man month to populate both
- Post pass
- DPS - manual set of activities
- Trending
- No additional effort identified

**Operations Development Approach -Normal Ops Planning (Continued)**

**Mission Description**

## Identify constraints and triggers
Identify if response is via TSM, FDC or procedure activity
Identify set of activities and procedures to develop
Gather constraints and triggers
Most contingency procedures derived from I&T
Expect that there will be less than 30 unique contingency procedures - identified 10 thus far (more detail later in presentation)

**Identify if response is via TSM, FDC or procedure activity**
**Identify set of activities and procedures to develop**
**Gather constraints and triggers**
**Most contingency procedures derived from I&T**
**Expect that there will be less than 30 unique contingency procedures - identified 10 thus far (more detail later in presentation)**

**Operations Development Approach  - Contingency Ops**

**Mission Description**

## Senior experienced staff
Spacecraft and ASIST training mostly complete due to involvement of FOT in I&T
FDSS, CMS, MOPSS and DPS
FOT conducting the testing and therefore will simultaneously be trained to operate these systems
Mission Procedures Document used as a training document
ATSC highly skilled core operations team may be used to quickly replace FOT members who leave
Automation lessens need for console operators
Simulator director will be hired to help rehearse operations

**Spacecraft and ASIST training mostly complete due to involvement of FOT in I&T**
**FDSS, CMS, MOPSS and DPS**
- FOT conducting the testing and therefore will simultaneously be trained to operate these systems
**Mission Procedures Document used as a training document**
**ATSC highly skilled core operations team may be used to quickly replace FOT members who leave**
**Automation lessens need for console operators**
**Simulator director will be hired to help rehearse operations**

**Operations Development Approach - Training**

**Mission Description**

## There is budget for about 1/4 staff year of flight software maintenance
Can also use help from MAP spacecraft flight software development team since it uses the  same on-board computer

**Can also use help from MAP spacecraft flight software development team since it uses the  same on-board computer**

**Flight Software Maintenance**

**Mission Description**

## Data Policy                   	March 1999
Data Management Plan - draft 	January 15, 1999
Detailed Mission Requirements	July 1998
Mission Operations Support Plan (Design) 	June 1999
Test Plan - 2nd draft 	January 15, 1999
ICD’s
Space to Ground	Baselined
RF ICD 	In signature cycle
MOC to SVF - baseline 	1/30/99
Landsat MOU - draft 	1/15/99
GSFC to Lincoln Lab - 	Baselined (for ALI)
GSFC to TRW - draft 	1/30/99 (for Hyperion)
GSFC to Stennis MOU - draft 	1/99

**Data Management Plan - draft ****	****January 15, 1999**
**Detailed Mission Requirements****	****July 1998**
**Mission Operations Support Plan (Design) ****	****June 1999**
**Test Plan - 2nd draft ****	****January 15, 1999**
**ICD’s**
- Space to Ground	Baselined
- RF ICD 	In signature cycle
- MOC to SVF - baseline 	1/30/99
- Landsat MOU - draft 	1/15/99
- GSFC to Lincoln Lab - 	Baselined (for ALI)
- GSFC to TRW - draft 	1/30/99 (for Hyperion)
- GSFC to Stennis MOU - draft 	1/99

**Documents**

**Mission Description**

## Mission Procedures Document
Vol 1 Ops Concepts - baseline	January 6, 1999
Vol 2 Detailed Ops Plan - draft 	1/30/99
Spacecraft Users’ Guide 	6/99
Launch Site Support Plan (SWALES) 	1/4/99
PRD

- Vol 1 Ops Concepts - baseline	January 6, 1999
- Vol 2 Detailed Ops Plan - draft 	1/30/99
**Spacecraft Users’ Guide ****	****6/99**
**Launch Site Support Plan (SWALES) ****	****1/4/99**
**PRD**

**Documents (Continued)**

**Mission Description**

## SDR/MOR   11/5/97
Delta MOR 1/28/99
FOR/ORR   11/99

**Delta MOR 1/28/99**
**FOR/ORR   11/99**

**Reviews**

**Mission Description**

## Documents are on EO-1 CM website 
 http://eo1.gsfc.nasa.gov
Procedures
Database

-  http://eo1.gsfc.nasa.gov
**Procedures**
**Database**

**Configuration Management**

**Mission Description**

## All equipment is on the open side of the network at this time - MAP/IMAGE approach
Ground system / data is password protected
MOC requires a keycard for entry

**Ground system / data is password protected**
**MOC requires a keycard for entry**

**Security**

**Mission Description**

## Each subsystem is Y2k certified
End to end Y2k test plan attached in appendix

**End to end Y2k test plan attached in appendix**

**Y2K**

**Mission Description**

## EO-1 Ground Schedule as of 1-21-99 (1 of 6)

**Mission Description**

## EO-1 Ground Schedule as of 1-21-99 (2 of 6)

**Mission Description**

## EO-1 Ground Schedule as of 1-21-99 (3 of 6)

**Mission Description**

## EO-1 Ground Schedule as of 1-21-99 (4 of 6)

**Mission Description**

## EO-1 Ground Schedule as of 1-21-99 (5 of 6)

**Mission Description**

## EO-1 Ground Schedule as of 1-21-99 (6 of 6)

**Mission Description**

## Ground System Status

**D. Mandl**
**P. Garza**
**D. Grogan**
**J. Gvozdas**
**T. Brakke**

## Introduction

**D. Mandl**

##  Ground System Requirements Summary

** ****Ground System Requirements Summary**

**Ground stations to receive, process, and route science and housekeeping data to GSFC**
- X band
- Receive up to 80 Gbits of science data each day at 105 Mb/s
- Record the received X band data on hard media, mail to GSFC, and store raw data for 30 days
- S band
- Receive data at selected rates up to 2 Mb/s for WARP data and 4 Mb/s for housekeeping data
- Housekeeping data
- Route selected virtual channels to GSFC in real time
- Record up to 200 Mbits of data each day
- FTP recorded data to GSFC within one hour
- Store raw data for 30 days
- Backup science data (up to 5 Gbits per day): Process as with X band

##  Ground System Requirements Summary

** ****Ground System Requirements Summary**

**GSFC to receive and process data sent from the ground station**
- Perform Level 0+ processing on the science and housekeeping telemetry
- Fill Holes, reorder science into band order
- Up to 1000 scenes
- Archive raw and processed data
**Maintain an orbit of sufficient precision for scene comparisons**
- Follow Landsat 7 Ground Track +/- 3 km

##  Ground System Requirements Summary

** ****Ground System Requirements Summary**

**Maintain the health and safety of the spacecraft and instruments**
**Validate and calibrate on board orbit and attitude subsystems**
**Perform orbit maneuver control to enable formation flying**
**Provide mission planning and command management for**
- Image operations
- Technology operations
- Calibration operations
- Contingency operations

## Overview of EO-1 Ground System and Data Flow

**Ground System Status - Introduction**

**Overview of EO-1 Ground System and Data Flow**

- Early Orbit Testing Phase
- (Launch to Launch + 2 month)

## Overview of EO-1 Ground System and Data Flow

**Ground System Status - Introduction**

**Overview of EO-1 Ground System and Data Flow**

- Science Validation Phase
- (Launch + 2 month to Launch + 12 months)

## EO-1 Data Link Configuration for L&EO and Pre-Launch

** **

- NASA Closed IOnet

- NASA Open
-   IOnet

**Swales**

**EO-1 MOC**
- (Building 14
- Room N285)

**FEDS**
**9**

**FEDS**
**5**

- MOC LAN

**PC/**
**X-Term**
**2**

**PC/**
**X-Term**
**11**

**PC/**
**X-Term**
**17**

**MOPSS/**
**FDS**
**14**

**MOPSS/**
**FDS**
**14**

**SOTA (**Building 14 Room E259 A,B,C)

**EO-1 Launch Support Area**
- (Building 14 Room  N285)

- AMPEX Tape
- Drive

**FEDS**

- 56 Kb

- 56 Kb

**FEDS**
**TBD**

**DHDS**

**PC for**
**SERS**
**15**

**PC for**
**SERS**
**15**

**Ground System Status - Introduction**

**EO-1 Data Link Configuration for L&EO and Pre-Launch**

## EO-1 Data Link Configuration for Normal Operations

- NASA Closed IOnet

- NASA Open
-   IOnet

**EO-1 MOC**
- (Building 14
-  Room N285)

**FEDS**
**9**

**FEDS**
**5**

- MOC LAN

**PC/**
**X-Term**
**2**

**PC/**
**X-Term**
**11**

**PC/**
**X-Term**
**17**

**MOPSS/**
**FDS**
**14**

**MOPSS/**
**FDS**
**14**

**Ampex**
**Tape Unit**

**ASIST**
**at HOPC/**
**TRW**

**56 Kb line**

**56 Kb line**

**DHDS**

**FEDS**
**TBD**

**PC for**
**SERS**
**15**

**PC for**
**SERS**
**15**

**Ground System Status - Introduction**

**EO-1 Data Link Configuration for Normal Operations**

## Facilities

**D. Mandl**

## Mission Operations Center (MOC)

- Building 14 Room N285

**Facilities**

## MOC Elevation Drawing

**Facilities**

## Special Operations and Test Area (SOTA) - Used for Launch Support

**Facilities**

## SOTA Elevation Drawing (1 of 2)

**Facilities**

## SOTA Elevation Drawing (2 of 2)

**Facilities**

## MOC - ASIST, FEDS, CMS, FDSS
SOTA
Wallops Ground Station, Svalbard, Poker Flat ground stations
NISN

**Facilities**

**MOC - ASIST, FEDS, CMS, FDSS**
**SOTA**
**Wallops Ground Station, Svalbard, Poker Flat ground stations**
**NISN**

## EO-1 Science Data Flow

- SWIR Det

- VNIR Det

- DCE data

- VC7

- VC4

- VC6

- VC9

- VC3

**WARP/Satellite**

**Ground Station - Log to Ampex Tape**

**MOC/Data Processing System - Create DLT Tape**

- Data transfer via Ampex  tape

- Data transfer via DLT  tape

**EO-1 Science Data Flow**

**Facilities**

## RFA Status

**D. Mandl**

## RFA Status From MOR

**RFA Status**

## Ground and Space Networks

**P. Garza**
**R. Rodriguez**

## Ground and Space Networks

**Addition of hyperion experiment changed the required ground network support as follows****	**
- Launch + one week:  support every orbit
- Launch + 60 days:  support 6 passes/day
- Rest of mission:  support 2-3 passes/day
- Support S band 2Mb/s down link for science checkout via SAFS
- Support X band down link for quick tape recovery by shipping magnetic tape daily
- Added two 56 Kb/s data lines, one to Lincoln Lab and one to TRW

**Ground and Space Networks**

## Network Status

**Ground network 11-meter systems  **
- Operational readines testing in progress
- GN will demonstrate launch support capability by EO-1 launch
- Landsat 7 and  Quickscat currently scheduled for April 1999 launch
**Space network **
- White sands data interface service capability (WDISC) in place awaiting closed IOnet configuration for testing with MOC
- Spacecraft C band skin tracking radar support requested from Vandenberg and Kaena point during early orbit

**Ground and Space Networks**

## Combined Ground System

**D. Grogan**

## System Architecture

- Front End
- Data System
- Digital History
- Data Store
- Data
- Processing
- System

- AMPEX
- T/R

- I&T I/F
- Serial In
- 105 Mbps

- Ops I/F
- Tape In

- SCSI-2

- Serial
- Differential

- X-Band Interfaces

- I&T Bit Synch

- S-Band Interfaces

- GroundStations

- TCP/IP
- Network
- Commands
- Telemetry

- Primary
- ASIST
- W/S

- I&T I/F
- Serial
- Commands

- Associate
- ASIST
- W/S

- Filtered
- Commands
- (SFDUs)

- Associate
- ASIST
- W/S

- Associate
- ASIST
- W/S

- Associate
- ASIST
- W/S

- Telemetry

- Flight
- Dynamics
- Functions

- MOPSS

- • Real-time Commanding
- • Real-time and Off-line Displays
- • State Monitoring and Response
- • Command Management System
- • Interactive Data Language (Trending)
- • Level-1 Housekeeping Products

- Telemetry
-  Packets
-  (SFDUs)

**Combined Ground System**

## Real-Time Command and Control System - ASIST

**ASIST - Advanced System for Integration and Spacecraft Test**
**Database-driven command, monitoring and control**
**Interactive commanding**
**Script-driven test procedures**
**Real-time page displays**
**Real-time events log**
**Command status window**
**Essential Services Node (ESN) telemetry decommutation**
**Edit / load / dump / compare flight data system tables**
**Integrated trend analysis**
**Independent telemetry stream at each workstation**

**Combined Ground System**

## ASIST Status

**Currently operating with ASIST 6.1.f**
**Release 7.0 currently in development and test, is launch release**
**Release 7.1 features not critical, but needed for post launch autonomous operations**
**Patches may be necessary to fix problems, last patch / release accepted 90 days before launch**
**Release 8.1 will be final release received after L&EO**

**Combined Ground System**

**Notes:**
Items Missing from Release Notes:  Need input
Interface CMS with SCP of ASIST
Add direct interface to ASIST command database
Interface with FDF
Create a formatted memory dump report
Modify the Event Handler display   
Generalize interface to print spooler
Add an efficient display window that supports color
Add a way to specify the color of messages

## ASIST Releases (1 of 5)

**Combined Ground System**

**ASIST Releases (1 of 5)**

**ASIST Release 6.1****	****Already Released**
**ASIST Release 7.0****	****January 1999**
**Load / Dump utilities****	****Launch Critical**
**Add copy tracking to current load/dump tools**
**Add new print and compare tools**
**Test and update ASIST to work under AIX 4****	****Launch Critical**
**Support 4 digit year fields****	****Launch Critical**
**Complete Y2K testing****	****Launch Critical**
**Wallops Interface****	****Launch Critical**
**Implement Wallops command interface **
**Convert and distribute Wallops messages**
**Multi-step commanding - Enhance aggregate command mode to allow control of commands sent from the workstation****	****Launch Critical**
- Correlate VCDU time, ground time, and packet transmission time to produce a time correlation report

## ASIST Releases (2 of 5)

**Combined Ground System**

**ASIST Releases (2 of 5)**

**ASIST Release 7.0 (Continued)****	****January 1999**
- Modify the Event Handler display - Add user defined subsystems and classes
- Modify systems to use NTP time server/client software
- Define and implement syntax for array constants in STOL, SPTP, ...
- Allow the base of arrays in telemetry to be user-defined (but to default to 1)
- TDRS Interface
- Convert and distribute TDRS messages
- Allow modification of limit sets other than the initial limit set
- Improve Installation Scripts - Provide a set of scripts which will completely automate delivery of new versions of ASIST
**ASIST Release 7.1****	****June 1999**
- Improve the documentation and create a users guide and a reference manual
- Allow multi-level aggregate SFDUs to be built
- Specify the control authority in command SFDUs in RDL
- Allow access to STOL user functions from command line

## ASIST Releases (3 of 5)

**Combined Ground System**

**ASIST Releases (3 of 5)**

**ASIST Release 7.1 (Continued)****	****June 1999**
- Signal packet arrival in pseudo-telemetry
- Allow unchecked packet writes to the CVT
- Implement page distribution over the web
- Support other forms of SFDUs
- Implement NT-based GSE telemetry server
- Implement NT-based GSE command server
- Installation of SAMMI 4.0 to provide an improved human interface to the SAMMI format editor
- Implement lookup table for time fields
- Limits and polynomials for all points in an array
- Use telemetry database to drive archive utilities
- Provide a way to maintain and activate several sets of limits and limit states.
- Provide a method to enable trending on a telemetry point based on its state or the state of other telemetry or pseudo-telemetry points.
- Add the ability to archive data locally to tape without having to store the data onto disk first

## ASIST Releases (4 of 5)

**Combined Ground System**

**ASIST Releases (4 of 5)**

**ASIST Release 7.1 (Continued)****	****June 1999**
- Integrate the SAMMI V4 Format Editor with the ASIST Database - Cut and paste telemetry names to editor
- Allow undefine, enable and disable of conditional limits other than the first set from STOL. (Maybe also redefinition?)
- Database reports in Netscape - This feature places the telemetry and command database reports into Netscape format so that they may be browsed
- Command Checkpointing - This feature stores each command executed by the spacecraft in a  command CVT. This provides a simple way for the operator to determine the most recent states that the spacecraft has been commanded to.
- CCSDS segmented time support in database  This feature provides general support for CCSDS segmented time fields in the telemetry/command databases
- Add a way for the STOL server to write a data value directly to the CVT instead of through STOL
- Add command pre-verification to STOL

## ASIST Releases (5 of 5)

**ASIST Release 7.1 (Continued)****	****June 1999**
- OASIS Database Ingest
- Investigate/create a graphical procedure builder and test tool
- Support time varying database definitions - Add an option to archive the current database definitions along with the telemetry data
**ASIST Release 8.1****	**
- Reload the Command/Telemetry Database - With this option the user can recompile the command or telemetry database and then reload it, without having to stop ASIST and restart it
- Simplify Adding Database Extensions - This feature allows the developers to easily add new fields to the database field table while minimizing modifications to the telemetry or command compilers
- Project-level CM system - Provide a way for the telemetry and command databases to be controlled more easily. In particular, an interface to SCCS/RCS or some other CM tool should be allowed.
- Use the UNIX-provided account and security mechanisms with ASIST instead of the current hardwired ASIST and local account method
- Leap second processing
- Port to an Intel PC UNIX operating system

**Combined Ground System**

## Trending Software

**D. Grogan**
**L. Perkins**

## Trending and Analysis

**Trending tools and requirements for the spacecraft will be determined via cooperation with the spacecraft builder (Operations Working Group meeting in May concerned with this)**
**Trending system **
- Includes interface to IDL
- Built on the ASIST workstation structure
- Connects to data handling distribution system through telnet
- Data stored in VCDUs for minimal re-processing of data
- Plays back at 100X real-time
- Trending available for descriptive statistics: min, max, mean, standard deviation, etc.
**Existing ASIST Interface to IDL (V 7.0) **
- Can display trend graphics and collect selected data for storage on an ftp site, writing in any of the following formats: IDL file, GIF image, HDF file and CDF file
- Uses the ASIST shared memory

**Trending Software**

## Trending and Analysis Status

**Trending Software**

**Trending and Analysis Status**

**ASIST Release 6.1****	****Already Released**
- Provides trend displays and descriptive statistics
- Calculates min, max, mean, standard deviation, etc real-time or by playback over any time period
- Can be automated to ingest independent telemetry playbacks up to 100X real-time rate
**ASIST Release 7.0****	**** January 99**
- Provides an interface to IDL
- Can display trend graphics and collect selected data for storage to an ftp site in many formats:
- IDL file
- GIF image
- HDF file
- CDF file
- Users can write IDL programs for custom analysis
- Interface to SERS
- Complete Y2K testing
**ASIST Release 7.1****	****June 99**

## SERS System Architecture

**Trending Software**

**ASIST System**

**System Monitor**

**WPS**
**Scheduling**

**VMOC Data **
**Server**
**Primary**

**VMOC Data**
**Server**
**Backup**

**Skytel Paging Service**

- PC

- PC

- Spacecraft Telemetry

- Status Checks

- System Log Files
- Transferred Post Pass
- and Subset Log Files

- System Notifications

- Operational Schedules

- E Mail Notification

- Ground Monitor

- Paging Notifications

- E Mail Notification

## Front End Data Processor (FEDS) / Digital History Data Storage (DHDS)

**D. Grogan**
**L. Alexander**

## FEDS / DHDS Functional Capabilities

**FEDS / DHDS Functional Capabilities**

**Provides ground station interface**
**Provides serial interface during I&T**
**Routes real-time housekeeping telemetry to science ops**
**Real-time and playback data simultaneously available**
**Level 0 H/K and DPS product generation and delivery**
**Long-term storage of raw telemetry VCDUs**
**Automatic, COTS-based archiving to jukebox**
**Demonstrated capability to perform “lights out” telemetry capture and archiving**
**Replay of data by spacecraft (packet) and / or ground receipt time**

## FEDS / DHDS Data Capture Capabilities

**Capture of data via a serial (RS422) interface**
**Capture data via network interface (TCP/IP or FTP)**
**Convolutional decoding**
**Frame synchronization**
**Pseudo random noise decoding**
**Cyclical redundancy check (CRC)**
**Reed-solomon decoding **
**Virtual channel sorting**
**Packet reassembly**
**Output selected real-time packet (TCP/IP)**
**Output selected real-time VCDUs (TCP/IP)**

**FEDS / DHDS**

## FEDS / DPS Status

**FEDS / DHDS**

**FEDS / DPS Status**

**FEDS / DHDS Release 6.1****	****Already Released**
- Y2K Compliant
- Sample EO-1 data flows to Wallops and back
**FEDS / DHDS Release 7.0****	****January 99**
**Wallops Interface****	****Launch Critical**
**Implement Wallops telemetry interface **
**Implement Wallops command interface **
**Convert Wallops messages to telemetry packets**
**Convert and distribute Wallops messages**
- FEDS Time Stamp of received frames at frame sync
- Implement FEDS automation
- Investigate future DHDS mass storage systems
- Provide additional status about FTP transfers to FEDS
- TDRS Interface
- Implement TDRS telemetry interface
- Convert TDRS messages to telemetry packets
- Convert and distribute TDRS messages
**FEDS / DPS Release 7.1 ****	**** June 99**

## Command Management System

**D. Grogan**
**R. Whitman**

## Command Management System (CMS) Requirements / Status

**Requirements**
- Maintain Stored Command Processor ground reference image
- Accept planning products
- Accept command inputs from external sources
- Create, edit, generate, and delete SCP loads
- Transfer SCP loads to the CGS for up-link to the spacecraft
- Generate reports
**Status**
- ASIST Release 6.1				Released
- Process UDAP file from MOPSS
- Y2K compliant
- ASIST Release 7.0				January 1999
- Support for array-type command submnemonics
- Future Builds

**Command Management System**

## CMS External Interfaces

**Command Management System**

## Data Processing System (DPS)

**D. Grogan**
**L. Alexander**

## Data Processing System (DPS) Revised Requirements (1 of 3)

**Data Processing System (DPS) Revised Requirements (1 of 3)**

**DPS shall be able to ingest data down linked from the EO-1 Wideband Advanced Recorder/Processor (WARP) that has been recorded onto an Ampex tape  (rel 1)**
**DPS shall be able to process a weeks worth of recorded data (quantity TBD) at a time within 6 hours (rel 1)**
**DPS shall be able to do the following front-end processing (rel 1)**
- Decode Reed Solomon data
- Derandomize data
- Deinterleave I/Q channle
- Ingest CADU formatted data
**DPS shall be able to selectively process the files on an AMPEX tape containing files with the following file types - MS/PAN, Hyperion and LAC (rel 2)**
**DPS shall be able to process the file on the Ampex tape which contains the housekeeping data taken during the image (rel 2)**
**DPS shall process the input files and create 16 HDF formatted files; four files for PAN, four files for MS, WIS SWIR, WIS VNIR, GIS SWIR, GIS VNIR, three files for the LAC and housekeeping data. (rel 2)**
**DPS shall create an imageable PAN file as follows: (rel 1)**
- Reorder odd/even pixel offset
- Extract the scan lines and place in band sequential order
- Provide identifiable fill for those portions of a PAN line that do not have data (might to reword this)

## Data Processing System (DPS) Revised Requirements (2 of 3)

**DPS**

**Data Processing System (DPS) Revised Requirements (2 of 3)**

**DPS shall process the MS file as follows**
- Descramble the pixels
- Extract the scan lines and place in band sequential order
- Perform odd/even pixel reordering for bands 1, 1’, 2, 3, 4, 4’
- Perform correction for HgCdTe sampling for bands 5, 5’ and 7
- Provide identifiable fill for those portions of a MS line that does not have data
**DPS shall process the Hyperion SWIR file as follows: (rel 2)**
- TBD
**DPS shall process the Hyperion VNIR file as follows: (rel 2)**
- TBD
**DPS shall process the LAC file as follows:(rel 1)**
- Band order the scan lines for 250 bands
- Output of each detector shall be put into separate files that can later be assembled into a complete image
**Each Data Collection Event (DCE) which is a set of the above processed files, shall have an associated start and stop image time which is derived from the housekeeping file**
**DPS shall place the processed files on a DLT tape (rel 1)**
-  Session per tape (TBD) (rel 2)

## Files shall also be available for FTP (rel 1)
DPS shall have the following displays  (TBD)
Provide a quicklook display to indicate # of scan lines processed (rel 2)
DPS shall respond to the following error conditions:
Sequence errors
RS Errors
DPS shall perform quality control functions (rel 2)
Generate image report for each image
# of search , check , lock flywheel frames
Dropouts
Gaps
Other errors
DPS shall meet the interface requirements per the following ICD’s
EO-1 Space to Ground ICD
EO-1 MOC to SVF ICD
Goddard to MIT/Lincoln Lab ICD
Add header to each file as outlined in the above ICD
Hyperion GSFC/TRW ICD

**Files shall also be available for FTP (rel 1)**
**DPS shall have the following displays  (TBD)**
- Provide a quicklook display to indicate # of scan lines processed (rel 2)
**DPS shall respond to the following error conditions:**
- Sequence errors
- RS Errors
**DPS shall perform quality control functions (rel 2)**
- Generate image report for each image
- # of search , check , lock flywheel frames
- Dropouts
- Gaps
- Other errors
**DPS shall meet the interface requirements per the following ICD’s**
- EO-1 Space to Ground ICD
- EO-1 MOC to SVF ICD
- Goddard to MIT/Lincoln Lab ICD
- Add header to each file as outlined in the above ICD
- Hyperion GSFC/TRW ICD

**Data Processing System (DPS) Revised Requirements (3 of 3)**

## EO-1 DPS Data Flow

- SWIR Det

- VNIR Det

- DCE data

- VC7

- VC4

- VC6

- VC9

- VC3

**WARP/Satellite**

**Ground Station - Log to Ampex Tape**

**MOC/Data Processing System - Create DLT Tape**

- Data transfer via Ampex  tape

- Data transfer via DLT  tape

**EO-1 DPS Data Flow**

**DPS**

## Release 1 - February 15, 1998  
CADU processing (complete)
ALI descrambling S/W (complete)
AC processing S/W (complete)
DLT carousel interface (complete)
AMPEX tape unit interface
Need to install new driver
Integration of above modules

- CADU processing (complete)
- ALI descrambling S/W (complete)
- AC processing S/W (complete)
- DLT carousel interface (complete)
- AMPEX tape unit interface
- Need to install new driver
- Integration of above modules

**DPS Releases and Content**

**DPS**

## Release 2 - June 15, 1998 
Process Hyperion data
Process housekeeping data from an AMPEX tape
Tag images with a start and stop time derived from housekeeping data
Provide capability to FTP S-Band backup science data to DPS FEDS
Respond to  the following error conditions: sequence errors, RS errors
Provide quality reports 

- Process Hyperion data
- Process housekeeping data from an AMPEX tape
- Tag images with a start and stop time derived from housekeeping data
- Provide capability to FTP S-Band backup science data to DPS FEDS
- Respond to  the following error conditions: sequence errors, RS errors
- Provide quality reports

**DPS Releases and Content**

**DPS**

## Mission Operations Planning and Scheduling System (MOPSS)

**J. Gvozdas**
**R. Harbaugh**

## MOPSS Release Contents and Schedule

**Delivered **
- Release 1 			- delivered June 15, 1998
- Release 1.1		- delivered October 26, 1998
- Release 2			- delivered January 8, 1999 (being tested	 												by the FOT)
**Future release**
- Release 3 			- March 31, 1999
- Releases 1.1 and later are year-2000 compliant

**MOPSS **

## MOPSS Release Contents and Schedule (1 of 6)

**Release 1 - June 15, 1998 (to acceptance testing) **
- Ingest and display FDF orbital event predicts (reuse)
- Allow operator key in of TDRSS and GS event schedule (existing capability)
- Schedule activities/commands relative to orbital/GS/TDRSS events (reuse/modify)
- Allow user definition/edit of scene requests
- Schedule activities relative to image events (mod)
- Allow user to block out periods when imaging is not allowed (reuse)
- Provide capability to view and modify EO-1 timeline (reuse)
- Provide capability to build an activity plan reflecting timeline (reuse)

**MOPSS **

## MOPSS Release Contents and Schedule (2 of 6)

**Release 1 - continued **
- Provide the capability to create an updated activity plan (reuse)
- Provide the capability to schedule activities relative to events (reuse)
- Allow for the user to manually schedule activity/commands (reuse)
- Allow user to browse and modify auxiliary data for events/activities – scene requests, etc. (reuse)
- Provide feedback to the operator when constraints or conflicts occur (mod)
- Basic report generation support (reuse)

**MOPSS **

## MOPSS Release Contents and Schedule (3 of 6)

**Release 1.1 - October 26, 1998**
- Ingest FDF-generated maneuver plan and command sheet (reuse TRMM)
- Schedule orbit maneuver related sequences (slight mod TRMM)
- Ingest and display FDFSS orbital event predicts (mod)
**Release 2 - January 8, 1999 (to acceptance testing)**
- Display, allow selection, and transmit GS schedule from WSG (reuse)
- Receive and display GS schedule from WSG (reuse)
- Ingest and display SVF-provided ground image scene request (through long-term plan file) (mod)
- Ingest and display cal scene requests (through FDFSS calibration slew products)

**MOPSS **

## MOPSS Release Contents and Schedule (4 of 6)

**Release 2 - continued**
- Automatically ‘select’ images and schedule image related commands (mod)
- Ingest command database from ASIST to create MOPSS event classes
- Assign WARP file IDs for each data stream to be stored for each DCE (new)
- Perform resource utilization checks (WARP availability, instrument on time, etc.) (mod/new)
- Each WARP file should be assigned a file ID that correlates to DCE, DCE type, and data stream/type (ex – MS/PAN dark cal, MS/PAN instrument calibration, MS/PAN image, etc) (new)
- Each WARP field ID should be assigned a unique number (new)

**MOPSS **

## MOPSS Release Contents and Schedule (5 of 6)

**Release 2 - continued**
- Provide file management capabilities – over lapping data products (with continuity management), product updates, etc (mod)
- Ensure nadir imaging is not scheduled during black out periods (new)
**Release 3 - March 31, 1999**
- Calculate and display image times based on requested scene location and predicted EO-1 orbit position  (includes ingest of necessary FDFSS products) (reuse Landsat)
- Provide momentum management/attitude maneuver related constraint checking (new)

**MOPSS **

## MOPSS Release Contents and Schedule (6 of 6)

**MOPSS Release Contents and Schedule (6 of 6)**

**Release 3 - continued**
- Interface with FDFSS algorithms to schedule activities/commands for momentum management and attitude maneuvers for nadir and cal images.  Note - different interface for nadir and cal images (new)
- Generate enhanced reports: image summary report and/or pass plan (new)
- Ensure activity plan is not generated if new GS schedule from WSG has been received but not processed (new)
- Provide scenario scheduling of realtime procs (reuse MAP)
- Support recent changes to long-term plan and calibration slew file formats

## EO-1 Flight Dynamics Support SystemStatus

**R. L. DeFazio**
**S. H. Godfrey**
**R. J. Luquette**
**S. Shulman**

## EO-1 Flight Dynamics Support System Concept

**EO-1 Flight Dynamics Support System Concept**

**EO-1 Flight Dynamics ground operations support is performed entirely within the EO-1 MOC**
**This includes:  **
- Attitude Determination
- Sensor Calibration
- Momentum Management
- Instrument Calibration Planning
- Orbit Maneuver Planning and Calibration
- Orbit Determination
- Orbit and Attitude Products Generation
- Acquisition Data Generation
- Science Planning Support

## EO-1 Flight Dynamics Support System Architecture / Status

**EO-1 Flight Dynamics Support System Architecture / Status**

**Architecture     **
- The Flight Dynamics Support System (FDSS) is installed on a combination of PC (NT) and UNIX workstation platforms in the EO-1 MOC
- The FDSS software is primarily COTS or COTS (based) with limited software development support supplied under contract from Computer Sciences Corporation
**Status****	****  **
- Approximately half of the hardware used to support the FDSS in the EO-1 MOC has been installed
- The remainder is supporting software development in remote locations and will be returned to the MOC when software development is completed
- The delivery status of EO-1 FDSS software is shown on a following slide
- A testing program for the software will be performed via the EO-1 Ground System Integration & Test Activities which are beginning in January 1999

## EO-1 Flight Dynamics Support System Y2K Status

**EO-1 Flight Dynamics Support System Y2K Status**

**All platform operating systems are validated as being free of Y2K problems**
**Validation of newly developed or modified EO-1 FDSS software for possible Y2K problems will be done as part of system testing**
**All COTS used for EO-1 FDSS software applications has been declared Y2K compliant by the vendor**

## EO-1 FDSS 

**EO-1 FDSS **

## 	EO-1 FDSS Software Status	

**FDSS **

**	****EO-1 FDSS Software Status****	**

## EO-1 FDSS Software Status  (Continued)

**EO-1 FDSS Software Status  (Continued)**

## EO-1 FDSS Software Status  (Continued)

**FDSS **

**EO-1 FDSS Software Status  (Continued)**

## EO-1 FDSS Products (Receivables)

**     **

**FDSS **

**EO-1 FDSS Products (Receivables)**

## EO-1 FDSS Products (Deliverables)

**FDSS **

**EO-1 FDSS Products (Deliverables)**

## EO-1 FDSS Planned Activities

**EO-1 FDSS Planned Activities**

**Complete FDSS software development and related documentation - based on the software release schedule shown earlier**
**Support EO-1 I & T activities and Project simulations**
**Provide FDSS training to all members of the EO-1 Flight Operations Team**
**Continue EO-1 L & EO mission analyses to study options for an optimal Ascent sequence**
**Perform analyses required for timeline and launch script generation**

## Mission Science Office / Science Validation Facility

**T. Brakke**

## Mission Planning

**Coordinating Committee consists of representatives from Validation Team, Commercial Sector, and Department of Defense**
**Coordinating Committee establishes scene acquisition guidelines and adjudicates conflicts**
**MSO accepts requests from Validation Team and DOD/commercial users coordinator (SSC)**
**MSO creates Long Term Plan; FDFSS tools used where necessary; MOPSS accessed**
**MSO submits 4-week plans weekly to MOPSS**

**MSO / SVF **

## Data Processing / Distribution

**Science Validation Facility**
- Distributes **all** level-0 data to selected NRA Validation Team investigators
- Produces MS/Pan Cal Pipeline data on demand
- Provides in-house validation/analysis capability
**NASA Stennis / TRW**
- Provides **all** Hyperion processing
- Distributes Hyperion Level-0 data to all Commercial and DOD interests
- Distributes processed Hyperion data to SVF, as well as Commercial and DOD interests

**MSO / SVF **

## Science Validation Facility

**To be co-located with Landsat analysis facilities in Bldg 33**
**Essential hardware has been acquired****	**
- SGI Octane and two O2  workstations
- SGI Origin 2000 (shared  with Landsat)
- DLT7000 Tape Library
- 414 Gbytes of useable disk storage
- Two 9-Gbyte external disk drives

**Functions**
- Image Assessment
- Data Archive During Mission
- Data Distribution and Tracking for Validation Team
- Level-1 Processing
- Calibration
**Contractor Staffing**
- Two Programmer / Analysts
**Y2K Compliant**

**MSO / SVF **

## MSO / SVF 

**MSO / SVF **

## Operations Overview

**J. Howard**
**T. Berry**
**S. Shulman**
**A. Kost**
**B. Trout**

## High Level Operations Concept / Operations Philosophy

**J. Howard**

## Operations Concept Changes

**Operations Concept Changes**

**EO-1 is still a technology demonstration mission**
**Hyperion addition has caused the project to become more visible, which seems to implicate less risk, though requirements have not been stated as such**
**Number of interfaces has increased**
**Diversity of interfaces has increased**

## Operations Concept Changes (Continued)

**Technology validation has worked into the first year for some activities that were planned after science was complete**
**More activities due to third instrument**
**Some non-paired scenes now requested**
**Larger roll offset for some scenes (22 degrees)**
**Reduced power margin**

**Operations Concept / Operations Philosophy**

## MOC Operations Status

**1 FEDS**
**4 ASIST Workstations**
**4 X-terminals**
**1 HP workstation for MOPSS / FDSS**
**1 NT workstation for FDSS **
**FOT members supporting I&T using ASIST**
**FOT members trained in classroom on ASIST**
**FOT trained on FEDS **

**Operations Status**

## Operations Testing

**J. Howard**

## Operations Testing

**Testing divided into three types for ground system**
- S Type is acceptance and regression testing, done via using the system.  These tests are validated by verifying requirements have been tested and met. This is done via a weekly test team meeting.
- T Type is an interface test (also called mission readiness test).  Performed as often as possible.
- M Type are mission simulations.  These are full up, with all people involved in the real thing involved in the simulation.

**Operations Testing**

## S Tests - Verify Individual Subsystems and Software

**S Tests - Verify Individual Subsystems and Software**

**These tests are ongoing, final will be complete when the final software releases have been delivered and accepted**
**S1 CGS Acceptance Test****	****Begun**
**S2 MOPSS Acceptance Test****	****Begun**
**S3 Wallops Ground Station ****	****Begun**
**        ****Acceptance Test**
**S4 FDSS Acceptance Test****	**** Begun**
**S5 DPS  Acceptance Test****	****Begun**
**S6 Year 2000 Testing****	****Begun**

## T Tests - Verify Interfaces and Interoperability

**T Tests - Verify Interfaces and Interoperability**

**T1 Spacecraft to MOC Interface Test****	**** 12/98 **
- Data base correct for data to be decommed
- All workstations in MOC displayed data
- Plotting and sequential plots run
**T2 Spacecraft to MOC to MOPSS to CMS to ****	****2/99****	**** FDSS Interface Test ****	**
**T3 Spacecraft to MOC to MOPSS to DPS to SVF ****	****3/99****	****Interface Test**
**T4 RF Compatibility Test ****	****6/99****	**
**T5 MOC to Ground Stations Interface Test ****	****6/99****	**
**T5.1 9/99 MOC to TDRSS Interface Test**
**T6 MOC to WTR Interface Test ****	****9/99****	**

## M Tests - Mission Simulations

**M Tests - Mission Simulations**

**M1 Launch Simulations ****	****6/99****	**
**  ****(during S/C thermal vac)**
**M2 Normal Operations Simulations ****	****8/99****	**** (during 2nd thermal vacuum)**
**M3 Contingency Simulations ****	****9/99****	**
**M4 Launch Rehearsal ****	****11/99**
**Launch ****	****12/15/99**

## Test Reporting and Discrepancies

**Test Reporting and Discrepancies**

**DR database maintained on EO-1 Web site**
**Discrepancy Reports**
-  Opened by FOT
-  Assigned to subsystems - leads will generate subsystem DRs
-  Closed after successful retest
**Open item status viewable via EO1 web-site**

## Status

**Status**

**EO-1 Operations Test Plan - On EO-1 web site  **
**Web DR database operational**
**S Tests begun **
**T1 complete - 2 DRs  **
**T2 detailed plan complete**
**T3 - T7  - top level plans complete, detailed plans being worked**
**M tests in planning**

## Simulation Purpose

**Simulation Purpose**

**Demonstrate launch readiness using actual flight plans, procedures, and personnel**
**Demonstrate ability to support key scenarios:**
- L&EO, Normal, Contingency
**Develop integrated team consisting of Project, Spacecraft, Instrument, Technology, MSO, Ground Systems, and FOT**
**Develop ops support skills:**
- Anomaly detection, safing, isolation, recovery, and ops update
- Operations Coordination
- Operations Logging and Reporting
- Problem, Change, and Replanning Process
- Shift Handover
**Stress ground equipment**

## Simulations (Normal Operations)

**Simulations (Normal Operations)**

**Planned activities**
- Simulate science operations
- Combined Lunar Calibration
- Solar Calibrations for each Instrument
- Routine Data Collections
- Both X and S Band Science Playback and Processing
- Simulate Pass Ops
- S and X Band Downlink
- Playback Data Recovery and Management
- ATC / RTCS loads
- Use flight sequences and systems to extent practical

## Simulations (L&EO)

**Simulations (L&EO)**

**Planned activities**
- Simulate 1st 5 Days on-orbit operations (Not real time)
- Separation
- Attitude Acquisition
- Spacecraft Bus Check Out
- GPS turn on
- GPS Orbit Determination
- Orbit Maneuver
- Launch site Communications
- L&EO contingency
- Instrument check out
- Instrument turn on

## Simulations (Contingencies)

**Simulations (Contingencies)**

**Planned activities**
- Focus on contingency operations process, rather than how the spacecraft works per se.
- Demonstrate Contingency Ops Skills
- State of Health Assessment and Verification of Operational Activities
- Fault Detection, Isolation, Recovery, and Procedure Update process
- Anomaly Management process
- Replanning process Blind Acquisition
- Simulate key contingency scenarios
- Safehold Mode Recovery
- Blind Acquisition
- Cold Restart

## Simulations Support

**Simulations Support**

**Roles **
- Simulation Director
- FOT
- Lead Spacecraft Systems Engineer
- SubSystem Engineers - Swales / Litton (as needed)
- MSO / Instrument / Technology Reps
- Project (Mission Director, Project Management, Chief Technologist, Project Scientist)
- Ground Systems
- Launch Site Coordinator
**Resources - MOC, SOTA, Swales, spacecraft**

## Other Topics

**Other Topics**

**Do not have a high fidelity simulator**
**No closed loop attitude simulator on spacecraft**
**Simulation scripts being devloped **
**Instrumentors will not be needed on-site until launch confirmed ~ day 2**

## Documentation Overview

**J. Howard**

## Operations Procedures Preparedness

**All normal operations procedures tested with spacecraft**
**Some procedures tested through GS testing**
**All contingency procedures developed for I&T tested with Spacecraft**
**Minimal re-writing of contingency procedures tested in I&T for on-orbit operations**
**90% reuse of procedures, 30 new procedures estimated**
**No new telemetry display pages determined needed**
**Database reused from I&T**

**Documentation Overview**

## Documentation

**Mission Procedures Document**
- Comprehensive gathering of all operations to be performed on the ground and spacecraft laid out in a step by step manner
- Main training document
- Step by step procedures can be brought up from any platform and on any machine in the MOC using a web browser
**STOL procedures are part of the step by step procedures**

**Documentation Overview**

## Contingency Operations

**J. Howard**

## Contingency Operations - High Level

**Contingency Operations - High Level**

**Identify constraints and triggers**
**Identify whether response if via TSM, FDC or procedure activity**
**Identify set of activities and procedures to develop**
**Gather constraints and triggers**
**Current plans rely on spacecraft taking preliminary safing actions**
**Number of unique contingency procedures needed estimated to be 30, 10 developed so far**
**Most contingencies will be tested through I&T - we will draw upon these procedures for use on orbit**

## Contingency Operations - Low Level

**Contingency Operations - Low Level**

- Safehold recovery
- Blind Acquisition
- Warm and Cold restarts
- Battery Charging updates
- Attitude Control Calibrations
- Contingency Support
- Maneuver Abort
- Slew Abort

- RTCS Updates
- ATC Patching
- Data Replays
- TSM Updates
- Flight Software Updates
- Instrument Safing
- Earth Acquire
- Solar Array Indexing

**We will test main contingencies**

**We will identify the most likely on-orbit contingencies to scrub as well as possible in simulations**
**Safehold will be tested on orbit while engineers are supporting**
**We will develop other contingencies as identified by project and as man power permits**

## Mission Management

**J. Howard**

## On board mechanisms will safe spacecraft
SERS will notify FOT
SERS maintains web accessible data base of anomalies
Mission Director gives direction to FOT
Existing DR systems will be used 
SOARS - Spacecraft anomalies
UPR - ASIST related problems
TBD - MOPSS
TBD - FDSS
TBD - Ground Station problems

**SERS will notify FOT**
**SERS maintains web accessible data base of anomalies**
**Mission Director gives direction to FOT**
**Existing DR systems will be used **
- SOARS - Spacecraft anomalies
- UPR - ASIST related problems
- TBD - MOPSS
- TBD - FDSS
- TBD - Ground Station problems

**Mission Management**

**Anomaly Management**

## Flight Software will be tested throughout I&T
Updates will be tested through Mongoose V simulator
FSW support 1/4 person on going task
Configuration control
ASIST database will be in a controlled directory
System admin will have write privileges
Updates will be tested in a test directory
This is currently practiced for PSE software
STOL procedures will be run at system startup to do temporary changes to database for limits and calibrations until they are incorporated into database release.
Requests for changes will be on our DR system

**Updates will be tested through Mongoose V simulator**
**FSW support 1/4 person on going task**
**Configuration control**
- ASIST database will be in a controlled directory
- System admin will have write privileges
- Updates will be tested in a test directory
- This is currently practiced for PSE software
- STOL procedures will be run at system startup to do temporary changes to database for limits and calibrations until they are incorporated into database release.
- Requests for changes will be on our DR system

**Mission Management**

**Software and Database Management**

## All current members of team have been trained by developing and testing systems for launch
FOT trained on spacecraft and ASIST through I&T
ASIST training attended
FEDS training held
DPS training will be done after development
MOPSS training TBD
FDSS training will be developed
Senior experienced staff
No plans to develop training plan for new people since staffing plan calls for reduction of present staff by 40%
Automation lessens need for staff to perform routine operatins
Automation increases the need for highly trained staff during development to ensure correct operation

- FOT trained on spacecraft and ASIST through I&T
- ASIST training attended
- FEDS training held
- DPS training will be done after development
- MOPSS training TBD
- FDSS training will be developed
**Senior experienced staff**
**No plans to develop training plan for new people since staffing plan calls for reduction of present staff by 40%**
**Automation lessens need for staff to perform routine operatins**
**Automation increases the need for highly trained staff during development to ensure correct operation**

**Mission Management**

**Training**

## EO-1 FOT Tasks During Launch and Early Orbit

**Mission Management**

- Key:  AK - Alicia Kost, BD - Bob DeFazio, BT - Bruce Trout, JG - Joe Gvozdas, JH - Joe Howard, LA - Larry Alexander, LM - Leo McConville,
- RL - Rich Luquette, SS - Seth Shulman, TB - Tom Berry, TM - Tom Moore

## EO-1 FOT Tasks During Launch and Early Orbit (Continued)

**Mission Management**

- Key:  AK - Alicia Kost, BD - Bob DeFazio, BT - Bruce Trout, JG - Joe Gvozdas, JH - Joe Howard, LA - Larry Alexander, LM - Leo McConville,
- RL - Rich Luquette, SS - Seth Shulman, TB - Tom Berry, TM - Tom Moore

## Automation

**J. Howard**

## Launch and early orbit operations will be manned around the clock
Normal operations will be staffed during day shift only, except in special cases and contingencies 
SERS notifies operators via beeper for anomalies off shift
Single shift operations are phased in gradually as confidence builds
Spacecraft failure detection and correction software and spacecraft safehold provide a safe haven in the event of an on orbit anomaly
MOPSS and FDSS provide automated planning to build command loads which run the spacecraft

**Normal operations will be staffed during day shift only, except in special cases and contingencies **
- SERS notifies operators via beeper for anomalies off shift
- Single shift operations are phased in gradually as confidence builds
- Spacecraft failure detection and correction software and spacecraft safehold provide a safe haven in the event of an on orbit anomaly
**MOPSS and FDSS provide automated planning to build command loads which run the spacecraft**

**Automation**

**Automation Philosophy**

## Automation

**Pre Pass - MOPSS**
- FOT populates scenarios
- Use after L&EO
- Estimate 1 man month effort
**Pass**
- MOPSS drives STOL procedures with feedback
- Spacecraft Emergency Response System (SERS) notifies FOT member if there is a problem
- Estimate 1 man month to populate both
**Post Pass**
- DPS - manual set of activities
- Trending
- No additional effort identified

**Automation**

## Launch and Early Orbit Operations

**T. Berry**
**J. Howard**
**A. Kost**

## L&EO Operations Support

**L&EO Operations Support**

**FOT**
- 24 hour coverage for the first week
- 16 hour coverage for days 8 - 30
- Change to 8 hour coverage Monday through Friday gradually as confidence builds
**FDF**
- Personnel to perform initial on-orbit FDS system operations and checkout for first 30 days
- Swales
- Support FOT for first 30 days
**Instruments**
- Support available for weeks 2 and 3

## Launch Decision Flow

**Launch Decision Flow**

## EO-1 Data Links

**Launch and Early Orbit Operations**

**EO-1 Data Links**

## EO-1 RF Links

**EO-1 RF Links**

## Launch Profile

**Launch Status**
- Launched from WTR on a Delta 7320
- Co-manifested with the Argentine SAC-C spacecraft and will separate first from the launch vehicle
- Nominal launch date is 12/15/99
**Launch Window**
- EO-1 requires a 1 minute launch window to place it’s MLT at the descending node 1 minute behind the MLT of Landsat 7’s descending node
**FDSS Launch Hold Criteria**
- FDSS needs 1 PC (NT) and 1 HP to generate and distribute acquisition data
**Interfaces**
- Command, telemetry, and voice interfaces will be established allowing monitoring capabilities between VAFB and GSFC

**Launch and Early Orbit Operations**

## Launch Profile (Continued)

**Orbit description**
- 705 km
- Circular
- Sun-synchronous
- Frozen orbit
- Inclination of 98.2 degrees
**Spacecraft mass and area**
- Separation mass is 588 kg
- Effective cross-sectional area for drag of 4.9 meters-squared
- Separation mass includes 22.3 kg of hydrazine
**Formation flying constraints**
- To enable EO-1 to take co-fly images with Landsat 7, it is necessary to place EO-1 one minute along the track behind Landsat 7 on the same WRS path with a cross track error of within +/- km

**Launch and Early Orbit Operations**

## Launch Configuration

**Subsystems on at launch**
- Communications system
- Communications Remote Service Node (RSN)
- S band transponder (not transmitting)
- Command and Data Handling Subsystem
- Main processor (Mongoose V)
- Attitude Control System
- Processor (Mongoose V and Attitude Control Electronics RSN)
- Gyros
- Magnetometers
- Torquer bars
- Other
- Spacecraft heaters including damper heaters
- Instrument survival heaters
- Actuators for solar array release (HOPs) power service (enabled)
- HOPs will not activate without an additional fire command

**Launch and Early Orbit Operations**

## Launch Configuration (Continued)

**Timers and data rates**
- ACS
- ACS in B-Dot mode with commands overridden
- PSE timer to turn on reaction wheel assembly and electronics control unti at launch plus 65 mintues
- ACS timer to go to safemode if loose contact with Mongoose V for 66 minutes
- Torquer bar commands overridden until launch plus 66 minutes
- Initial ephemeris loaded
- Data and RF
- Telemetry stored at high rate (~65 Kb/s)
- Down link rate set to 2 Kb/s

**Launch and Early Orbit Operations**

## Launch Day Orbit Ground Trace

**Launch and Early Orbit Operations**

## Space Network and Ground Station Coverage

**Space Network**
- Use of TDRS is anticipated for the first few hours after separation and later during initial maneuvers
**Wallops Ground Stations**
- Spitzbergen, Norway
- Poker Flat, Alaska
- Wallops Island, Virginia

**Launch and Early Orbit Operations**

## Early Orbit Telemetry, Tracking, and Command CoverageLaunch Plus 1 Hour to Launch Plus 5.5 Hours

**Early Orbit Telemetry, Tracking, and Command Coverage****Launch Plus 1 Hour to Launch Plus 5.5 Hours**

## Early Orbit Coverage Launch Plus 5.5 Hours to Launch Plus 173.5 Hours

**Early Orbit Coverage Launch Plus 5.5 Hours to Launch Plus 173.5 Hours**

## Launch Profile

**Launch and Early Orbit Operations**

## Ascent Key Elements

**Liftoff****	****0.00**
**Jettison 10 ft composite fairing****	****11.00**
**S band transmitting @ 2Kb/s****	****12.00**
- AOS TDRSS (spacecraft monitoring)
**EO-1 spacecraft separation****	****58.20**
**AOS Spitzbergen****	****76.24**
**AOS Poker Flat****	****86.48**
**LOS Spitzbergen****	****87.58**
**LOS Poker Flat****	****97.52**

**Launch and Early Orbit Operations**

**Mission Elapsed Time**

## Ascent Profile

**Fairing separation at 11 minutes**
**S band transmitting 2 Kb/s at 12 minutes (TDRSS)**
**Outer solar array panel toward the sun during coast phase**
**Maneuver EO-1 to meet the formation flying constraints with respect to Landsat 7**
**Ascent should be accomplished within the first 2 to 3 weeks of mission**
**Will require 6 to 7 maneuvers and use about 2 kg of hydrazine**

**Launch and Early Orbit Operations**

## Separation Profile

**Activated by separation wires or by timer**
- Release solar arrays
- Send power to both primary and redundant heaters of both primary and redundant HOPs
- Turn on TAM and IRU (these will already be on unless there was a power interruption to the ACE LVPC during launch and ascent)
- Turn off MTB command override
- Turn of RWAs
- Enable on RWAs
- Enable ACS transition from B dot to sun-acquisition
- Set “I’m OK” safemode timer in ACE to 10 seconds

**Launch and Early Orbit Operations**

## On Orbit Operations

**Consists of**
- Initial orbits (1 - 5) of operations
- Day 1 operations
- First week operations
- Weeks 2 and 3 operations
- Further spacecraft checkout operations
- Instrument checkout
- Detailed information is provided in the backup slide section of this presentation

**Launch and Early Orbit Operations**

## Integrated Normal Operations

**J. Howard**
**S. Shulman**
**A. Kost**
**B. Trout**

## EO-1 Mission Profile

**Integrated Normal Operations**

## Normal Ops Command Requirements

**Normal Ops Command Requirements**

**Instrument Data Collection Events (DCEs)**
- Up to four per day, less when calibration DCEs being captured
**Instrument Solar Calibration **
- Weekly for Hyperion
- Monthly for ALI and AC
**Orbit Maneuvers to maintain Landsat 7 co-fly profile**
- Approximately weekly, based upon preliminary discussions with Landsat 7
**Landsat 7 orbit vector Uplink**
- Daily in ATC load
**Performance of Ground Contacts (2 -3 per day) to allow:**
- Command operations
- Real time and play back state of health data retrieval and satellite monitoring
- Science data downlink via X-Band
- Additional contacts for Maneuvers, Calibrations, and Contingencies
- ATC load Uplink
- Approximately every other day
**Performance of Technology Validation Operations**

## Planning and Scheduling

**J. Howard**

## EO-1 Operations Planning Flow

**Planning and Scheduling**

## Data Collection Events (DCEs)  / Science Operations

**J. Howard**

## Instrument DCE Summary Table

**DCE / Science Operations**

## Planned Ground Image Scenarios

**Combined Paired scene - image tied to WRS grid**
**Non Paired scene - location tied to latitude / longitude / duration**
**Landsat 7 / EO-1 stereo image **
**Will support following**
- Differing image duration
- Various permutations of instruments on
- Multi DCE per turn on

**DCE / Science Operations**

## Combined Image Profile

**DCE / Science Operations**

## Lunar Scan Raster Profile

**DCE / Science Operations**

**AC #1**

**AC #3**

**AC #2**

**ALI SCAs**

**Hyperion**

**NOTE :  Dashed lines represent Sensor Fields of View**

**    ****Black lines represent raster scan profile**

**    ****Bold lines represent actual data collect periods**

**5**

**O**

**15**

**O**

**1.25**

**O**

## Lunar Scan Data Collection Profile

**DCE / Science Operations**

**Lunar Scan Data Collection Profile**

**Limiting factors**
- Available power (solar array pointing stopped)
- Instrument duty cycle
- Data storage

## Instrument Solar Cal Highlights

**DCE / Science Operations**

**Note: Different solar calibrations needed due to different optical path of each instrument**

## Science Data Flow

**DCE / Science Operations**

## EO-1 Flight Dynamics Operations

**EO-1 Flight Dynamics Operations**

**S. Shulman**
**R. L. DeFazio**
**S. H. Godfrey**
**R. J. Luquette**

## EO-1 FDSS 

**EO-1 FDSS **

## Orbit Determination Process

**FDSS Operations**

**Orbit Determination Process**

## Maneuver Planning

**FDSS Operations**

**Maneuver Planning**

## Product Generation

**FDSS Operations**

**Product Generation**

## Attitude Operations

**FDSS Operations**

**Attitude Operations**

## EO-1 Weekly FDSS Operational Scenario

**EO-1 Weekly FDSS Operational Scenario**

## FDSS As Needed Operations

**Post Burn Product Updates (8 day Products + IIRV Acquisition Data)**
**Post Burn Thruster Calibration and Fuel Remaining Updates**
**Run MATLAB Utility to perform Instrument Calibration Slew Planning**
**Run AutoCon-G to generate EFF Tables (JR updates)**
**Run MATLAB/ADS to perform Sensor Calibration (IRU, TAM)**
**Real time Capabilities (RTADS Displays, STK/PRO Ground Track Plot)**

**FDSS Operations**

## EO-1 FDSS Products

**FDSS Operations**

**EO-1 FDSS Products**

## EO-1 FDSS Products  (Continued)

**FDSS Operations**

**EO-1 FDSS Products  (Continued)**

## EO-1 Early Orbit Adjust Profile

**FDSS Operations**

**EO-1 Early Orbit Adjust Profile**

**Worst case launch dispersions for inclination  (0.027 deg.).  Need to correct inclination dispersions as second step in executing orbit adjust profile  **
**First maneuver, an engineering test burn, would be 2 days after launch**
**Ascent took 7 additional maneuvers and completed ~16 days after launch**
**Hydrazine used:   2.86 kg**

## Landsat 7 / EO-1 EFF Operations 

**Landsat 7 / EO-1 EFF Operations **

**To meet Landsat 7 / EO-1 co-fly imaging requirements, the two spacecraft must stay within constraints**
**For ground based EFF planning, the EO-1 MOC personnel will look up to 5 weeks ahead to determine when the future EO-1 maneuvers should be performed**
**The Landsat 7 MOC is required to provide regular updates of Landsat 7’s location and future maneuver plans - these requirements are stated in an ICD**
**The EO-1 FDSS AUTOCON-G software is designed to input the Landsat 7 data, include the current state of EO-1, and evaluate when the next EO-1 EFF maneuver is required**
**When EFF planning and control is passed to the onboard AUTOCON-F software, the procedure changes somewhat - each EFF option in AUTOCON-F (The GSFC algorithm and the JPL algorithm) operate somewhat differently**

## Landsat 7 / EO-1 EFF Operations  (Continued)

**Landsat 7 / EO-1 EFF Operations  (Continued)**

**Landsat 7 state vectors are uploaded to EO-1 daily and after all Landsat 7 orbit maneuvers**
**For the GSFC EFF algorithm, AUTOCON-F takes the current EO-1 state from the onboard GPS, plus the uploaded Landsat 7 state and looks 48 hours ahead to determine if an EO-1 maneuver is required**
**With the JPL EFF algorithm, AUTOCON-F uses the current EO-1 state from the onboard GPS, plus the uploaded Landsat 7 state and a Landsat 7 maneuver delta-V and ignition time to determine when the next EO-1 maneuver should occur**
**AUTOCON-F requires uploaded tables reflecting current solar activity required by the Jacchia-Roberts drag model along with about 15 other tables which may require periodic updates**
**When AUTOCON-F is prime for EO-1 EFF maneuver operations, the ground based AUTOCON-G software can be run for comparison of results**
**Both AUTOCON-G and F provide the capability to calibrate as well as plan the EO-1 EFF maneuvers**

## Five Week Enhanced Formation Flying Profile for EO-1

**FDSS Operations**

**Five Week Enhanced Formation Flying Profile for EO-1**

## Spacecraft Command and Control

**A. Kost**

## EO-1 Command and Control

**Commanding done normally via stored command load**
**Normal stored commands consist of downloading virtual recorder (VR) data, downloading WARP data, DCE commanding, transponder operation, data rate management, and some attitude and orbit operations**
**Real time commanding will be necessary to perform flight software code loads and dumps, and table loads and dumps**
**All real time commanding will be done via STOL procedures**
**Back up S Band playback (in case of X Band failure) changed to 2 Mbps because of spacecraft limitations**
**Real Time Pass Scenario**
- Up link a command load when necessary (needs to be done every 2 to 3 days depending upon the number of DCEs scheduled)
- Down link WARP and SSR playback data via stored command
- Check spacecraft real time state of health via the SERS
- Routine activities are automated

**Spacecraft Command and Control**

## Stored Command Operations

**EO-1 utilizes Absolute Timed Sequence and Relative Timed Sequence command tables**
**On cold restart and power on the EEPROM RTS tables are loaded into the RAM slots which overwrites the RAM and erases the RAM only slots which necessitates reloading of any RAM only tables (up to 255 tables) when a cold restart occurs - to ease recovery, the CMS will store an image of the RTSs on the ground**
**New features include checksumming on commands being loaded (previously the commands were checksummed as they were executed), and the ability for another piece of flight software to patch the buffer without human intervention (see the EFF section)**

**Spacecraft Command and Control**

## Typical Week of Stored Commands

**Spacecraft Command and Control**

**Weekly Total = 1690 Commands**
**Absolute Time Command Buffer Capacity = 600 commands per buffer**
**Typical Upload Once Every Other Day**

## EO-1 Solid State Recorders (SSRs)

**EO-1’s SSR is divided into three Virtual Recorders (VRs)**
- VR1  - housekeeping data
- VR2 - events
- VR3 - GPS B packet
**Each VR has 4 datasets (DSs) in which to store data**
**Which data stored where, the amount of data stored, whether data overwritten in each DS, VC identifiers for each VR, and which data filtered can be changed via table load if needed**
**Total storage space available is 249 MBytes:**
- VR1: 222.6 MB		Enough for around 2 Days, 7.5 Hours
- VR2: 8.8 MB		115,000 event messages, several weeks 					worth of normal event messages
- VR3: 17.7 MB		Technology data only, no impact

**Spacecraft Command and Control**

## Recorder Operations

**Actions performed via stored command**
**Contingency actions performed real time**

**Spacecraft Command and Control**

## Virtual Channel Assignments

- Y - Will occur   N - Will not occur   C - Occurs on command   C* - Occurs on command (not routinely planned)

**Spacecraft Command and Control**

## New Technology Operations

**A. Kost**
**N. Speciale**

## EO-1 Technologies

**EO-1 Technologies**

**Advanced Land Imager**

**Multispectral Imaging Capability (I)**
**Wide Field Reflective Optics (I)**
**Silicon Carbide Optics (I)**

**I/F**
** ****B**
** ****0**
** ****X**

**Wide Band**
**Advanced**
**Recorder/**
**Processor**

**G**
**R**
**O**
**U**
**N**
**D**

**New Technology Operations**

**Attitude Control System**

## Technology Descriptions

**New Technology Operations**

## NMP Validation Process 

**NMP Validation Process **

**Every technology has an validation team that will process the data received from the FOT**
**FOT has met with each technology team to ensure technology validation requirements and operational needs (including monitoring and safing) are understood, and to ensure necessary development, preparations, and testing for on-orbit operations can be performed prior to launch**
**For on-orbit operations, a weekly Operations Coordination meeting will be used to determine which technology validations operations are to be scheduled - these operations are then planned by the FOT based on plans outlined in the Technology Validation plan and coordinated prior to launch, and further input provided by technology validation teams **
**Technology validation teams will provide support in the MOC during as many technology validation operations as necessary**** **

**New Technology Operations**

## Technology Validation Schedule

**New Technology Operations**

## X Band Phased Array Antenna Operations

**Validation will be performed through**
- Telemetered spacecraft in-flight measurements
- Ground station measurements
**Performance will be routinely inferred through monitoring and trending of downlink operations, and through use of science data processing metrics**
**Monitoring of each downlink performed at 3 levels:  **
- SOH telemetry used to confirm downlink
- Ground status data used to confirm received signal levels, data lock status, and record operations
- Data reception and quality monitoring performed during MOC level 0 processing of taped data
- Any problems encountered during these processes will be identified and isolated
- Signal levels at ground station
- R-S errors
- Science data quality problems

**New Technology Operations**

## XPAA Operations (Continued)

**XPAA team analysis support will be requested as necessary**
**Special operations**
- Periodic (every 2-3 months) downlinks to Wallops Island, Virginia ground station which occur while the XPAA team is at the ground station to monitor operations - Provide Ground Station status data (AGC, etc), X-band data tape, Spacecraft R-S error telemetry from Wallops downlink for X-band team analysis for these downlinks
- Special downlinks to Wallops will be requested during which the antenna remains ‘pointed’ along the nadir axis
- After MOC level 0 processing completed, X-band data tapes (before Reed-Solomon decoding) from these Wallops downlinks will be provided to the validation team
- Perform XPAA checkout – Launch + ~2 weeks
- Turn on XPAA RSN and confirm proper housekeeping status (temperature, currents, etc)

**New Technology Operations**

## Enhanced Formation Flying Requirements / Definitions

**Level 1 Requirement**
- Demonstrate the capability to fly over the same ground track as Landsat 7 within 3 Km at a nodal separation interval of nominally one minute during which time an image is collected
**What are AutoCon and EFF?**
- AutoCon is a Satellite Automation and Control Tool
- AutoCon-G is the ground version
- AutoCon-F is the flight version
- EFF is the EO-1 Flight Interface to AutoCon-F
- Supplies AutoCon with data
- Places maneuver commands in stored command processor

**New Technology Operations**

## AutoCon - On Board Process Overview

**New Technology Operations**

## EFF Operational Modes

**EFF has four ground commandable modes**
**Off**
- Nothing on, no products generated, no inputs needed
**Standby / Monitor Mode**
- Will execute, but will not generate any burn plan
**Semi-Autonomous Mode**
- Will execute and plan burns, but stored command patch is held in a buffer until a ground commit command is received
**Autonomous Mode**
- Will execute and plan burns, and patch command buffer autonomously

**New Technology Operations**

## EFF Operations

**EFF Operations**

**EFF Orbit maintenance operations phases:**
- Ground planned burns to maintain formation with monitoring of on board system
- On board planned burns to maintain formation with ground commit needed to execute burn
- On board planned burns to maintain formation
**In the early stages of the mission, the on board software will be operating and generating products - during this time, the ground will operate the ground based software mimicking the on board software**

## EFF Operations (continued)

**EFF Operations (continued)**

**Key inputs to EFF**
- L7 orbit vector from L7 MOC - daily
- L7 orbit maneuver plan from L7 MOC - weekly (only needed for JPL algorithm)
- Flight software patch to load JPL targeting algorithm - month 9
**Once the performance of the flight software is satisfactory, control will be turned over to it**
**During EFF control of the spacecraft, the EFF software will patch both ATS buffers autonomously with maneuver commands, the new requirement built into the SCP allows this**
**2 targeting algorithms are planned for on-orbit use: 1 provided by GSFC and 1 provided by JPL, the JPL algorithm is planned to be uploaded when the GSFC algorithm is verified, around 270 days into the mission**

## EFF Flight Software Development Status / Validation Objectives

**AutoCon Status**
- AutoCon-G is completed
- AutoCon-F is under acceptance testing (Vsat / Mongoose / ASIST)
**EFF Status**
- Flight software is completed
**Validation Objectives**
- Validation of AutoCon Executive
- Validation of AutoCon Interface
- Validation of Maneuver Decision
- Validation of Maneuver Design
- Validation of Maneuver Calibration

**New Technology Operations**

## EFF Validation

**New Technology Operations**

## Sample EFF Valplan Timeline

**New Technology Operations**

## EFF Planned Schedule / Activities

**Day 4: EFF turned on in monitor mode to allow check out of EFF / Autocon-F using the GSFC algorithm to begin**
**Day 4 - 30: Establish EO-1 orbit formation - not EFF related**
**Day 30 - 90: Perform ground planned formation maintenance burns using GSFC algorithm - EFF in standby / monitor mode**
**Sometime in Day 30 - 90: Switch to semi-autonomous mode when comfortable**
**By Day 90: Perform Autocon-F / EFF checkout using GSFC algorithm**
**Day 90 - 270: Perform on-board planned formation maintenance burns using GSFC algorithm - fully autonomous, semi autonomous on weekends**
**Around Day 270: Upload flight software patch for JPL algorithm**
**Day 270-300: Perform ground planned formation maintenance burns using JPL algorithm - EFF in standby / monitor mode**
**Sometime in Day 270-300: Switch to semi-autonomous mode when comfortable**
**By Day 300: Perform Autocon-F / EFF checkout using JPL algorithm**
**Day 300-365: Perform on-board planned formation maintenance burns using JPL algorithm - fully autonomous, semi autonomous on weekends**

**New Technology Operations**

## Carbon-Carbon Radiator (CCR) Operations

**Trending provided to validation team weekly**
- Thermal data of thermistors attached to panels
- Beta angle data
- Attitude history data

**New Technology Operations**

## Lightweight Flexible Solar Array Operations

**L&EO Operations**
- Performed at around Launch plus 2 weeks
- Deploy LFSA array via commanding the release of a stow pin, which in turn allows shaped memory hinges and deployment systems to deploy the LFSA
- Deployment should take ~30 seconds and will be done during orbit day while instruments operations are not occurring
**Weekly On-Orbit Operations**
- Perform LFSA I-V Curve Sweep data collect
- Use stored commands to: enable storage of LFSA data, start I-V Curve Sweep mode, change mode back to normal, and disable LFSA data storage
- I-V Curve Sweep mode should be on 10 seconds
- Performed in sunlight, with the preference that the spacecraft be in a position where the sun is at an optimal angle on the array (i.e., near 90)

**New Technology Operations**

## LFSA Operations (Continued)

**Weekly On-Orbit Operations (Continued)**
- Provide data (FDSS STK data) from which LFSA validation team can derive sun angle during data collect
- Provide LFSA validation team a time history of LFSA raw and calibrated telemetry gathered during I-V curve collects in tabular and plot forms via Excel
**Special On-Orbit Operations**
- Perform additional I-V Curve Sweep data collects (up to 3 / orbit) – as requested

**New Technology Operations**

## Pulse Plasma Thruster Operations

**L&EO Operations:**
- PPT test firing to demonstrate functionality performed during 1st week of the mission
- Test firings will be coordinated with instrument turn ons
- Consists of: powering on the PPT, sending single shot ground PPT fire commands, and powering off the PPT after firings completed
- During test firings, the ACS will remain in wheel control mode - data during these operations will be provided to the technology validation team for assessment
**While the PPT is active, PPT personnel will be co-located with the FOT in the MOC to observe turn on, coordinate required operations and commanding, and to help with any unexpected problems**
**PPT control mode limited to mission idle and science imaging (nadir pointing)**

**New Technology Operations**

## PPT Operations (Continued)

**9 or 10 months into the mission, a period of two weeks will be set aside for PPT to perform technology validation, during which the following will be performed:**
- Establish PPT performance baseline with ACS in wheel control mode
- ACS left in wheel control mode while instruments are stowed, the PPT is powered on, and the PPT is fired via ground commands
- Collect telemetry during these firings to determine torque magnitude and alignments and pass to validation team
- If necessary, flight software control parameters updated via table load (as provided by PPT validation team)
- Establish operations in PPT control with instruments stowed
- Disable X and Z magnetic torquer bars (roll and yaw remain under wheel control), and command PPT transition mode
- Make adjustments to control parameters if validation team decides it is necessary via evaluating telemetry
- Perform instrument data taking with PPT control when performance is acceptable
- Goal is to collect several images while PPT control is active

**New Technology Operations**

## PPT Operations (Continued)

**PPT Operations (Continued)**

**2 Week Validation Operations (Continued):**
- Transition back to wheel control
- Wheel control mode re-enabled, and the PPT commanded off
- Distribute  telemetry data to Tech validation team weekly
**As Needed Operations During 2 Week Validation:**
- FDCs will monitor attitude and systems performance while under PPT control - if FDC or FOT detect unacceptable performance, spacecraft will transition to wheel control, and power off PPT
- Perform FDC maintenance operations
- Involves performing table loads to broaden allowable pointing performance errors during initial PPT operations and/or issuing commands to disable FDC checks that do not apply during PPT controlled modes
- Perform table uploads to PPT control parameter as provided by PPT team

## Issues and Concerns

**J. Howard**

## Operations Issues and Concerns

**Operations Issues and Concerns**

**Issues**
- There is a discrepancy concerning who uses which VCs, notably, the WARP and the C&DH both plan to use VC3 for different types of data
- Trending requirements do not yet exist, there are issues with how much effort is needed to create a sufficient trending capability
- No closed loop ACS testing capability
- Lack of documentation - Spacecraft users’ guide running behind, no ASIST configuration set up guide, no FEDS users’ guide
- Launch site voice circuit plan running behind
- Decisions on responsibilities and approach for EO-1 instrument on orbit alignment determination is not defined
**Concerns**
- Changes / information are not always communicated between elements in the EO-1 project which has created some re-work
- Single shift operations poses inherent risk to anomaly operations

**Notes:**
Changes not always communicated examples:
1.  A command was added in the flight software, but that change was not communicated to the whole team, so Alicia spent several hours finding out that the new command existed.

## Acronym List

- AC	Atmospheric Corrector
- ACE	Attitude Control Electronics
- ACS	Attitude Control System
- ADS	Attitude Determination System
- AFSCN	Air Force Space Control Network
- AGS	Alaska Ground Station
- ALI	Advanced Land Imager
- AOS	Acquisition Of Signal
- AOS	Advanced Orbiting Systems
- APID	Application Identifier
- ASIST	Advanced Spacecraft Integration and Systems Test
- AST	Autonomous Star Tracker
- ATC	Absolute Timed Command
- AUTOCON-F	Automated Control Program-Flight
- AUTOCON-G	Automated Control Program-Ground
- AWOTS	Automated Wallops Orbital Tracking Station
- BCR	Battery Charge Regulator
- BPSK	Bi-Phase Shift Keyed
- C&DH	Command and Data Handling
- C&T	Commands and Telemetry
- CADU	Channel Access Data Unit
- C-C	Carbon-Carbon
- CCB	Configuration Control Board
- CCR	Carbon - Carbon Radiator
- CCSDS	Consultative Committee for Space Data Standards
- CDR	Critical Design Review
- CGS	Core Ground System
- CHECKEPH	Check Ephemeris
- CIS	Copper Iridium Diselinide
- CLTU	Command Link Transmission Unit
- CM	Configuration Management
- CMD	Command
- CMS	Command Management System
- COTS	Commercial Off The Shelf
- CRC	Cyclic Redundancy Check

- CSS	Course Sun Sensor
- CTE	Coefficient of Thermal Expansion
- CVT	Current Value Table
- DCE	Data Collection Events
- DCM	Dual Control Mode
- DMR	Detailed Mission Requirements
- DOD	Department Of Defense
- DPAF	Dual Payload Attachment Fitting
- DPS	Data Processing System
- DR	Discrepancy Report
- DS	Data Set
- EDC	Error Detection and Correction
- EEPROM	Electrically Erasable Programmable Read-Only Memory
- EFF	Enhanced Formation Flying
- EIRP	Effective Isotropic Radiated Power
- EO-1	Earth Orbiter 1
- EOS	Earth Observing System
- EOSDIS	Earth Observing System Data and Information System
- EPS	Electrical Power Subsystem
- EROS	Earth Resources Observation System
- ESN	Essential Services Node
- ETM+	Enhanced Thematic Mapper Plus
- FD	Flight Dynamics
- FDF	Flight Dynamics Facility
- FDSS	Flight Dynamics Support System
- FEDS	Front End Data System
- FODB	Fiber Optic Data Bus
- FOR	Flight Operations Review
- FOT	Flight Operations Team
- FOV	Field Of View
- FPA	Focal Plane Assembly
- FPD	Flight Procedures Document
- FSW	Flight SoftWare
- FTP	File Transfer Protocol
- Gbps	Giga Bits Per Second
- GIS	Grating Imaging Spectrometer

**Acronym List**

## Acronym List (Continued)

- GN	Ground Network
- GPS	Global Positioning System
- GRI	Ground Reference Image
- GS	Ground Station
- GSE	Ground Support Equipment
- GSFC	Goddard Space Flight Center
- GTAS	Generic Trending and Analysis System
- GTDS	Goddard Trajectory Determination System
- H/S	Health and Safety
- HK	Housekeeping
- HEA	Hyperion Electronics Assembly
- HOP	High Output Paraffin
- HAS	Hyperion Spectral Assembly
- HW	Hardware
- I&T	Integration and Test
- I/O	Input / Output
- IBM AIX	International Business Machines AIX
- ICD	Interface Control Document
- IDL	Interactive Data Language
- IRU	Inertial Reference Unit
- Isp	Specific Impulse
- Kbps	Kilo Bits Per Second
- L&EO	Launch and Early Orbit
- LAC	Leisa Atmospheric Corrector
- Landsat 7	Land Imaging Satellite 7
- LEISA	Linear Etalon Imaging Spectrometer Array
- LFSA	Lightweight Flexible Solar Array
- LL	Lincoln Lab
- LAN	Local Area Network
- LOS	Loss Of Signal
- LP DAAC	EOSDIS Land Processes Distributed Active Archive Center
- LV	Launch Vehicle
- LVLH	Local Vertical Local Horizontal
- LZP	Level Zero Processing
- MAP**	****Microwave Anisotropy Probe**
**MD****	****Mission Director**

- Mbps	Mega Bits Per Second
- MGS	McMurdo Ground Station
- MIPS	Million Instructions Per Second
- MIT	Massachusetts Institute of Technology
- MOC	Mission Operations Center
- MOCD	Mission Operations Concept Document
- MOP	Mission Operations Plan
- MOPSS	Mission Operations Planing and Scheduling System
- MOR	Mission Operations Review
- MOU	Memorandum Of Understanding
- MS	Multi-Spectra
- MSO	Mission Science Office
- MTB	Magnetic Torquer Bar
- N/A	Not Applicable
- NASA	National Aeronautics and Space Administration
- Nascom	NASA Communications Division
- NCC	Network Control Center
- NMP	New Millennium Program
- NORAD	NORth american Aerospace Defense command
- ODB	Operational DataBase
- Ops	Operations
- ORR	Operations Readiness Review
- OWG	Operations Working Group
- PAN	Panchromatic
- PDB	Project DataBase
- PODS	Precision Orbit Determination System
- PPT	Pulse Plasma Thruster
- PSE	Power Subsystem Electronics
- PV	Photo Voltaic
- RAM	Random Access Memory
- RCS	Reaction Control System
- RDL	Relational Database Language
- RF	Radio Frequency
- RFA	Request For Action
- ROM	Read Only Memory
- RPM	Revolutions Per Minute
- RSN	Remote Service Node

**Acronym List**

## Acronym List (Continued)

- RT	Real Time
- RTADS	Real Time Attitude Determination System
- RTCS	Relative Timed Command Sequence
- RWA	Reaction Wheel Assembly
- S/A	Solar Array
- SAC-C	Satelite de Aplicaciones Cientificas – C
- SAD	Solar Array Drive
- SADE	Solar Array Drive Electronics
- SAI	Swales Aerospace, Incorporated
- S/C	Spacecraft
- SCA	Sensor Chip Assemblies
- SCC	Spacecraft Command Center
- SCP	Spacecraft Command Processor
- SCT	Spacecraft Control Team
- SDR	System Design Review
- SERS	Spacecraft Emergency Response System
- SFDU	Standard Formatted Data Unit
- SGS	Svalbard Ground Station
- SiC	Silicon Carbide
- SLP	Solar, Lunar, Planetary
- SOTA	Special Operations and Test Area
- SN	Space Network
- SOH	State Of Health
- SSC	Stennis Science Center
- SSR	Solid State Recorder
- STK	Satellite Tool Kit
- STOL	Systems Test and Operations Language
- SVF	Science Validation Facility
- S/W	Software
- SWAS	Submillimeter Wave Astronomy Satellite
- SWG	Science Working Group
- SWIR	Short Wave Infra-Red
- TAM	Three Axis Magnetometer
- TBC	To Be Confirmed

- TBD	To Be Determined
- TBS	To Be Supplied
- TCP / IP	Transmission Control Program / Internet Protocol
- TDRSS	Tracking and Data Relay Satellite Subsystem
- THR	Thruster
- TLM	Telemetry
- TOTS	Transportable Orbital Tracking Station
- TRACKIN	Tracking Data Input Program
- TRMM	Tropical Rainfall Measuring Mission
- TSM	Telemetry and Statistics Monitor
- UPR	User Problem Report
- UPS	User Planning System
- USGS	United States Geological Survey
- V / T	Voltage / Temperature
- VAFB	Vandenberg Air Force Base
- VC	Virtual Channel
- VCDU	Virtual Channel Data Unit
- VNIR	Visible / Near Infra-Red
- VR	Virtual Recorder
- WARP	Wideband Advanced Recorder Processor
- WebTAS	Web Trending and Analysis System
- WGS	Wallops Ground System
- WIS	Wedge Imaging Spectrometer
- WOTIS	Wallops Orbital Tracking Information System
- WSC	White Sands Complex
- WSG	Wallops Scheduling Group
- WTR	Western Test Range
- XPAA	X Band Phased Array Antenna
- Y2K	Year 2000

**Acronym List**

## Back Up Slides

## Year 2 K End to End

## Spacecraft Contingency Handling

**Spacecraft Contingency Handling**

## Launch Site Operations Flow

**Launch and Early Orbit Operations**

## EO-1 Voice Usage Plan

**EO-1 Voice Usage Plan**

**Launch Voice**
- Launch Countdown
- Delta Ops
- EO-1 Payload Ops
- EO-1 Management
**Operations Voice**
- EO-1 Ops (2 lines?)
- EO-1 Ops Cord
- EO-1 Engineering
- (EO-1 Management - reused Launch line)
- EO-1 Ground Cord

**Launch and Early Orbit Operations**

**EO-1 Launch Site Communications Flow**

## Launch Profile

**Launch Profile**

**Liftoff****	****0.00**
**Solid Motor Burnout (3)****	****1.04**
**Solid Motor Separation (3)****	****1.50**
**Main Engine Cutoff****	****4.21**
**Vernier Engine Cutoff****	****4.27**
**Stage 1-2 Separation****	****4.29**
**Stage 2 Ignition****	****4.35**
**First Cutoff- Stage 2  - ****	****10.48**
-  Second Engine Cutoff 1
**Jettison 10 ft. Composite Fairing****	****12.00**
**Stage 2 Restart****	****53.51**
**Second Cutoff****	****54. 05**
- Stage 2 (Second Engine Cutoff 2)

- MET

## Launch Profile (Continued)

**Launch Profile (Continued)**

**Separate EO-1 Spacecraft****	****58.20**
**Separate Portion of Dual - ****	****61.40**
**  ****Payload Attachment Fitting****	**
**Separate SAC-C Spacecraft****	****65.00**
**AOS Spitzbergen, Norway****	****76.24**
**AOS Poker Flat, Alaska****	****86.48**
**LOS Spitzbergen****	****87.58**
**LOS Poker Flat****	****97.52**
**Second Stage Evasive Burn Ignition****	****100.0**
**Third Cutoff – Stage 2 -****	****100.5**
- Second Engine Cutoff 3
**Second Stage Depletion Burn Ignition****	****108.2**
**Stage 2 Depletion****	****109.0**

- MET

## Ascent and Separation

**Ascent and Separation**

**Ascent**
- Fairing separation at 11 minutes
- S-band transmitting at 2 kb/s at 12 minutes (TDRSS)
- Outer solar-array panel toward the sun during coast phase
- Separation at 58:20
**Separation**
- Activated by separation wires or by timer
- Release solar arrays: send power to both primary and redundant heaters of both primary and redundant HOPs
- Turn on TAM and IRU (these will already be on unless there was a power interruption to the ACE LVPC during launch and ascent)
- Turn off MTB command override
- Turn on RWAs
- Enable ACS transition from Bdot to sun-acquisition
- Set “I’m OK” safemode timer in ACE to 10 seconds

## Initial Orbits (1 - 5) Operations

**Initial Orbits (1 - 5) Operations**

**Monitor satellite through TDRSS at 2 kb/s**
**Data storage continues at the high rate, approximately 65 kb/s**
**Verify that potentiometers indicate that the solar array autonomously deployed and moved to the index position**
**At first ground contact (Spitzbergen), issue a playback command to verify that spacecraft can receive and process ground commands**
**Verify that angular momentum is decreasing (ACS is in b-dot mode)**
**Monitor transition to sun-acquisition mode, which occurs autonomously when momentum is sufficiently damped. It may take two orbits of b-dot damping, depending on tip-off velocities. Uses coarse sun sensors. **

## Initial Orbits (1 - 5) Operations (Continued)

**Initial Orbits (1 - 5) Operations (Continued)**

**Verify PSE function**
- Battery charging when solar arrays in the sun
- Transition to battery power during eclipse
**Verify that EO-1 is power-positive during an orbit**
**Monitor ACS components: RWA, TAM, MTB, IRU, and CSS**
**Turn on GPS and AST (by ground command)**
**Verify AST producing correct attitude**
**Verify SHM control signals from the ACE **
**Disable launch TSMs and enable TSMs that were disabled for launch**

## On-Orbit Day-1 Operations (1 of 3)

**On-Orbit Day-1 Operations (1 of 3)**

**Verify that EO-1 has a valid GPS fix on position and velocity**
- Takes up to one orbit to get a lock
- Takes 1-2 days for ground to verify GPS performance
**Issue command for ACS to use AST and GPS information**
**Initialize Kalman filter and begin convergence**
**C&DH functional tests**
- Commanding
- Counters
- Load / dump
- Memory scrub
- All tasks operating nominally
- RTs responding
- Bus errors?
- DRAM errors?
- LVPC current

## On-Orbit Day-1 Operations (2 of 3)

**On-Orbit Day-1 Operations (2 of 3)**

**Verify GPS time code availability and correctness**
**Verify momentum management - RWA speeds near zero**
**Verify battery health**
- Battery-state-of-charge
- Check VT curve, taper, end-of-night parameters
- C/D calculations
- Battery temperature
**Verify PSE functions**
- Solar Array switching
- FDC operating
- OM and LVPC currents nominal
**Enable use of GPS time signal and verify distribution (GPS to HK RSN, M5 C&DH)**

## On-Orbit Day-1 Operations (3 of 3)

**On-Orbit Day-1 Operations (3 of 3)**

**Verify storage filter tables**
- Normal (4 kb/s)
- High rate (65 kb/s)
**Verify real-time downlink filter tables**
- Low (2 kb/s)
- High (32 kb/s)
**Assess thermal-control system**
- Temperatures
- Heater duty cycle

## On-Orbit First Week Operations (1 of 3)

**On-Orbit First Week Operations (1 of 3)**

**Verify S-band downlink rates, 2 kb/s, 32 kb/s, and 1 Mb/s**
**Enable coherency on S-band for ground verification of GPS position**
**Checks of ACS algorithms and kalman filter**
- Monitor covariance
- Determine gyro biases
- Compare AST and TRIAD solutions, etc.
- Need several orbits of high-rate data
**Transition to Earth Pointing / Mission-Idle Mode (M5 ACS)**
**Monitor solar-array tracking and transition to digital counter**
**Switch to normal data-storage rate (4 kb/s) when not performing specific tests**
**Turn on, and verify aliveness of the WARP and X-band PAA (day 2)**

## On-Orbit First Week Operations (2 of 3)

**On-Orbit First Week Operations (2 of 3)**

**Perform MTB pulses over 10-minute period to calibrate TAM**
- Ground analysis
**Verify 2 Mb/s s-band downlink rate using WARP data**
**Enable SHM control of spacecraft for at least one orbit**
- Starting from mission-idle mode (nadir pointing), test both the transition to safe mode and the stability of the ACE controller (day 4)
**Monitor safehold performance: ACS, TSMs, and RTSs**
**Return to nadir pointing**
**Verify X-band downlink: correct commanding from ACDS, first check of performance (test data from WARP)**

## On-Orbit First Week Operations (3 of 3)

**On-Orbit First Week Operations (3 of 3)**

**Perform 90-degree attitude slews for IRU calibration - Ground analyzes data**
**Perform delta-V burn to correct errors from orbit insertion **
**Perform orbit adjusts to phase EO-1 into Landsat 7 orbit (about 6 maneuvers required)**
- Pitch maneuver required
- Thruster calibration will follow each maneuver to improve thruster scale factor
**During contact with ground**
- Perform short delta-V burn (10 seconds; could also fire thrusters one at a time) to verify thruster functions and ACS performance during thruster-control mode
- Pitch maneuver is probably not required for this test
- Ground analysis (takes 12 to 24 hours)
**Perform longer firing of all thrusters to get the thrust scale factor**
- Pitch maneuver required
- Could be done in conjunction with first orbit-adjust burn
**Verify TSM task operating correctly**

## Instrument Checkout (1 of 3)

**Instrument Checkout (1 of 3)**

**Day 3**
- Turn on and verify aliveness of the ALI, AC, LFSA, and Hyperion
**Week 1**
- ALI/WARP initial tests: ALI test pattern and WARP data acquisition and storage
**Weeks 2 and 3**
- Activate launch-release mechanism for ALI aperture cover
- Hyperion/WARP initial tests with calibration lamps; cryocooler not yet operating
- Activate launch-release mechanism for LFSA panels
- Deploy LFSA panels
- Test of ALI using internal calibration lamp

## Instrument Checkout (2 of 3)

**Instrument Checkout (2 of 3)**

**Weeks 2 and 3 (continued)**
- Test WARP/AC interface: take initial AC images, without stopping solar arrays
- Enable EFF and verify that it is operating in the background
- Turn on Hyperion cryocooler
- Take Hyperion images with internal calibration lamps and cold SWIR
- Check operation of ALI and Hyperion aperture doors (after one or two weeks, so that satellite has time to out-gas)

## Instrument Checkout (3 of 3)

**Instrument Checkout (3 of 3)**

**Further Checkout**
- ALI mechanism: test sun-calibration motors
- ALI performance tests: take images
- Hyperion performance tests: take images
- Ground assessment of instruments (ALI, LEISA/AC, and Hyperion), LFSA, and CCR performance
- Sun calibration of instruments
- ALI/ACS alignment calibration: images and ground evaluation by FDF and science team

## Further Spacecraft Checkout

**Further Spacecraft Checkout**

**Health and safety assessment of all satellite systems**
**Perform initial delta V burn to rendezvous with Landsat 7**
**Test spacecraft set-up for imaging**
- Spin-up reaction wheels
- Stop solar array, etc. (use RTSs and ATSs)
**Lunar calibration **
- ACS maneuvers
- Instrument images
**Test firing of PPT to verify function**

## Orbit Formation Operations

**Orbit Formation Operations**

**Launch up to 15 minutes behind Landsat 7**
**Perform up to seven burns to get to 1 minute behind Landsat 7’s circular orbit**
**Plan on taking 16 days using GPS Data for orbit determination**

## C&DH Operations

**C&DH Operations**

**Upload periodic Absolute Time Command (ATC) command load containing commands to support**
- Science data collection and playback from WARP
- Stored State of Health (SOH) data playback from spacecraft recorder
- Toggle SOH data rates
- Imaging operations
- Attitude and orbit maneuver operations
**Collect GPS data for orbit determination**
**Perform RTCS uploads as needed**
**Perform table operations as needed**
**Perform flight software updates as needed**

## WARP Operations

**WARP Operations**

**WARP Capabilities**
- The WARP (Wideband Advanced Recorder Processor) is the science data recorder on EO-1
- Is a solid state recorder
- Has capability to store 40 Gbits of data
- Can record data at a rate of 1 Gbit per second
- Can output data for down-link at a rate of 105 Mbps
**Data Collection**
- Data recorded into files - 1 file per science stream (VCs 4 - 9)
- Files for each science stream to be stored, with user assigned file IDs, are opened / closed for each Data Collection Event (DCE)
- Whenever a DCE occurs, housekeeping data from the spacecraft will be recorded on the WARP at the same time

## Power Operations

**Power Operations**

**Power systems management largely controlled on-board**
**Operations performed**
- Confirm correct system performance (through real-time monitoring and offline trending)
- Update operating parameters as analysis indicates
- Plan operations to ensure energy balance is maintained and that duty cycle limits are observed
- Schedule commands to halt solar arrays during imaging to reduce jitter (this causes minimal reduction in power)

## ACS / RCS Operations

**ACS / RCS Operations**

**Establish and maintain formation with Landsat 7**
**Perform attitude maneuvers to support orbit maneuvers, calibrations, and ground off point images**
**Perform momentum management to reduce jitter during imaging operations**
**Perform systems calibrations**
- Sensor and gyro calibrations
- Thruster calibration
**Perform health and status monitoring and trending**
- Expected configuration checked
- Spacecraft event messages checked for anomalies
- Configuration monitor will check stored telemetry
- Real time and recorded limit violations investigated
- Plots analyzed for anomalous conditions

## Thermal Operations

**Operational (thermostatically controlled) heaters monitored for performance verification**
**Heaters will remain enabled for the duration of the mission**
**Monitoring performed on entire spacecraft during real time and during trending of playback data**
**Subtle trends of increasing or decreasing temperatures caught with long term trending**

**Spacecraft Operations**

## RF Operations - General

**RF Operations - General**

**EO-1 has S and X band down-link capabilities**
**Concurrent S and X band support is scheduled nominally twice daily**
**S Band down-link used to establish S Band up-link**
**If the X Band antenna fails, the S Band can be used to down-link science data - backup down-link rate is 2 Mbps**

## Spacecraft Safing and Recovery

**Spacecraft Safing and Recovery**

**EO-1 is designed to identify and respond to anomalies by putting itself in a stable, known, safe configuration**
**Spacecraft provides the Telemetry and Statistics Monitor (TSM) which allows for the definition of specific conditions to monitor and can trigger the execution of an RTCS**
**EO-1 stores event messages or provides status telemetry indicating fault or anomaly occurrence -  data is retrieved and analyzed to assist in anomaly diagnosis and recovery process**

## “A Day in the Life” Of EO-1

**Integrated Normal Operations**

## “A Week In the Life” Of EO-1

**Integrated Normal Operations**