# Presentation: 076987

## Section 26	

_***Section 26***_***	***
***Operations / MOC***

*** ******. . . Dan Mandl***
*EO-1 Operations Manager *

## Operational Philosophy

***Operational Philosophy***

***1 year mission***
***During L&EO***
***14 passes/day (2 for science dumps) during first week***
***8 passes/day from (2 for science dumps) L+8 to L+60***
***During Normal Ops***
***3-8 passes/day (2 for science dumps)***
***80 Gb of data max from instruments per day***
***Staffing***
***24 hr  x 7 day  staffing for operations during first 60 days***
***Phase down to 8hr x 5 day after L+60 contingent on review at L+30***
***After phase down, use automation for non-manned hours***
***Weekends and evenings***

## Operational Phases

***Operational Phases***

***Launch & Early Orbit***
***Launch and the first several orbits, spacecraft checkout, and instrument turn-ons***
***Approximately 15 days***
***Begin formation flying 1 minute behind Landsat 7***
***Instrument Checkout***
*Full instrument checkout*
*Approximately 45 days*
***Nominal Ops***
***Science Validation***
***10 months***
***End of Life***
***Deorbit burn for reentry within 25 years***

## Operations Overview

##  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*
*Housekeeping data*
*Route selected virtual channels to GSFC in real time*
*Record up to 200 Mbits of data each day*
*FTP recorded data to EO-1 MOC  within two hours*
*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***

***Process Hyperion, MS/PAN and AC science data to provide at least 200 paired scene comparisons with Landsat 7***
***55 scenes for ALI, AC during 60 day checkout***
***55 Hyperion, AC scenes***
***1000 scenes total first year***
***Maintain an orbit of sufficient precision for valid scene comparisons***
***Follow Landsat 7 Ground Track***
*+/- 3 km cross track*
*1 minute behind +/- 6 seconds*
*1 minute later than Landsat in mean local time at the descending node*

**Operations**

##  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 maintain formation flying***
***Provide mission planning and command management for***
***Image operations***
***Technology operations***
***Calibration operations***
***Contingency operations***
***Archive raw and processed data***

## Verification Approach

***Verification Approach***

***System testing – done by the developers of each subsystem***
***Acceptance Testing and Mission Readiness Testing done by the FOT to verify each subsystem’s requirements and end-to-end performance of ground components***
***Simulations performed by FOT , Instrumenters, EO-1 management, and S/C subsystem engineers for final end-to-end check of team’s ability to perform required tasks***

## EO-1 Operations Testing Status

**S = Acceptance Testing  T = Mission Readiness Test  M = Simulation**

## EO-1 Ground Data System

***Requirements Verification Results***

- AGS, SGS, WOTS,  MGS Schedules

- Commands

- S-band Data

- Tracking Data

- Data Quality Statistics

**N**
**I**
**S**
**N**

- S-band Data

- Commands

- Tracking Data

- Schedules

- X-band Data

- Telemetry Attitude Data, Tracking Data

- Attitude Determination, Definitive Ephemeris
-  Data, Delta V Burn Parameters

- Planning/Schedule Aids

- Calibration Parameter File

**SN**

- T  =   12
- V  =     9
- N =      2
- D =      1
- % =    82

**WOTIS**

- T  =    5
- V  =    5
- N =     0
- D =       0
- % =  100

**GN**

-   AGS       SGS       WOTS        MGS

- T  =    31        31         31           21
- V  =      26        26          26          18
- N  =     5           5          5             3
- D  =     0           0          0              0
- % =     84         84        84            84

**DPS**

- 1

- W/B Data Quality info

- X-band Data tape

**FDSS**

- Maneuver Planning

- Orbital Prediction

- R/T Attitude Determination

- Orbital Determination

- T  =   19
- V  =   16
- N =     3
- D =     0
- % =   84

- Long Term Plan from SVF

- FD Products and Plan Aids

- Calibration Science Request

- Calibration Parameter File

- WOTIS Event Schedules

**MOPSS**

- T  = 29  V  = 25
- N =    2
- D =    2
- % =   93

- T  =    46
- V  =    45
- N =      1
- D =      0
- % =    98

**M O C**

- EBNET

- R/T Electronic TLM (VC0 & VC02)   SAFS data retrieval (Post Pass)

- Daily Activity
- Plan

- Data Collect
- Event Schd

- Plans and
-  Schedules

- R/T Commands

- Command Loads

- R/T Telemetry

- P/B Telemetry

- DLT Tapes
- with L0 data

**SVF/MPO**

**Instr**

- T  = 15  V  = 02      N =   13
- D =    0
- % =   04

- T  = 20  V  = 00
- N =  20
- D =    0
- % =   93

## Requirements Verification

***Requirements Verification***

***77% of the requirements verified***
***Most of the unverified requirements are from McMurdo and X-Band data***
*McMurdo testing to be completed by 1/30/00*
*X-band long loop tests to be conducted 12/15/99 and 1/15/99 with WGS, SGS and AGS*
***Y2K Certification***
***End to end Y2k Test Plan was created for project***
***Each subsystem including the S/C was Y2K certified***
***End-to-end test was conducted with Wallops on  9/24/99***

## Ground DR Status as of 12-8-99

**Critical DR’s:**
- 58  FDSS:  Improve modelling of RW speed                 action:  fixed, pending test of MMAP 1.0
- 60  FDSS:  Slew computation problem                          action:  patch   ADS 1.2  12/1/99
- 73  FEDS:  Lack of failover capability for FEDS            action:  Reconfigure FEDS by 1/15/00

## S/C to MOC Testing

## FOT Organization

***New team structure to cover 24 hour operations 7 days a week up to Launch plus 60 days***
***Review held at Launch+30 days on whether to down-staff at Launch + 60 days***

## FOT Shift Profile

***FOT Shift Profile***

***Power up shift before launch to L+7 days***
***2 x 12 hour shifts every day***
***L+8 to L+60 3 shifts supplemented with returning TC’s from west coast***
***At L+30 & L+60 will have review to decide if we will extend 24 hour operations***
***If Ops nominal then during Normal Ops will have 2 shifts offset by 4 hours to provide coverage 12 hours per day M - F otherwise continue 3 shift 24 hour coverage***

## Documentation Philosophy

***Documentation Philosophy***

***All required documents to operate the S/C are on the EO-1 website***
***Copies of required documents will be at the console during operations***
***Mission Director and FOT Lead will be responsible for a “Controlled Document List” and will assure that all printed documents are in concurrence with the this list***

## Documents

## Documents

## Mission Procedures Document

***Mission Procedures Document***

***Mission Procedures Document (MPD) on EO-1 web site***
***MPD Vol 1 is the Ops Concepts***
***MPD Vol 2, Detailed Ops Plans***
***Launch***
*Staffing on East and West Coast*
*Launch Script*
***S/C Checkout:  L to L+15***
***Instrument Checkout:  L + 16  to L+60***
*Launch Critical Contingency Procedures*
***Normal***
*Normal operations procedures (e.g. pass operations)*
***All inclusive***
*TSM’s*
*FDC’s*
*RTS’s*
*Contingency Procedures (Flow Charts, Script and Procedure Names)*
*List of pages and procs*
*List of S/C Event messages*
*Anomaly escalation process*

## Documents are on EO-1 CM website 
 http://eo1.gsfc.nasa.gov  (select configuration management)
ISO Compliant
Procedures
Tested
Placed global procedure directory
Write privileges only by Systems Administrator
Changed via Operations Change Request
Database & Pages
All pages inherited from I&T
Build latest version and placed in configured directory
Only DB administrator can modify
Temporary changes placed in global directory by any FOT member
Changes via DB change request forms

***Documents are on EO-1 CM website ***
*** ***_***[http://eo1.gsfc.nasa.gov](http://eo1.gsfc.nasa.gov/)***__***  (select configuration management)***_
***ISO Compliant***
***Procedures***
***Tested***
***Placed global procedure directory***
***Write privileges only by Systems Administrator***
***Changed via Operations Change Request***
***Database & Pages***
***All pages inherited from I&T***
***Build latest version and placed in configured directory***
***Only DB administrator can modify***
***Temporary changes placed in global directory by any FOT member***
***Changes via DB change request forms***

***Configuration Management***

## Hardware Status

***Hardware Status***

***All Hardware in MOC in place except as follows:***
***Digital History Data System (DHDS)***
*Delivered 11/26/99*
*Installed by 1/15/00*
*In the meantime use current Front End Data System in dual role of FEDS and DHDS*
***MOC firewall***
*ACE control software received, routers due 12/15/99*
*Install by 12/30/99*
*Test through month of January*
*Workaround is operate without it, firewall is transparent to ops*

## Procedure Status

***Procedure Status***

***Normal Operations STOL Procedures complete except:***
***FEDS/DHDS upgrade to allow STOL control and STOL automation***
***Launch Procedures***
***Complete and being reheased in M1 simulations***
***Contingency Procedures***
***Will test Decembere 21, 1999 and January 11, 2000***
***For details, see Contingency Procedure Special Topic ***

## Launch

***Launch***

***Launch Vehicle***
***Launched from WTR on a Delta 7320***
***Co-manifested with the Argentine SAC-C spacecraft.  EO-1 separates first.  ***
***Launch Window***
***EO-1 has an instantaneous launch window with a +30 second allowance for collision avoidance.  The window occurs once per day at about 18:26 GMT. ***
***Formation flying with Landsat 7***
***To enable EO-1 to co-fly with Landsat 7, it is necessary to place EO-1 one minute (+/-6 sec) behind Landsat 7 and within 3km crosstrack.   ***
*The launch vehicle injection point is at the start of first ascending node.  The Local time will be ~22:06 GMT. *
*Depending on the performance of the Launch Vehicle, between 6 and 8 maneuvers will be required to position EO-1 behind L7.*
***Final Orbit***
***705 km , circular, sun-synchronous, inclination of 98.2 degrees***

## Space Network & Ground Network Coverage

***Space Network & Ground Network Coverage***

***Space Network***
***Use of TDRS is planned for powered flight and the first few orbits after separation and later during initial maneuvers***
***Ground Network***
***Norway***
***Alaska***
***Wallops***
***McMurdo***

## Launch Day Orbit Ground Trace

## Highlights of L&EO

***Highlights of L&EO***

***Day 1***
***Launch, separation, SA deployment***
***Turn on IRU heaters, Star Tracker, GPS, and ALI outgas heaters***
***Initialize Kalman Filter***
***Day 2***
***Begin use of Kalman Filter***
***Begin use of GPS for time***
***Go to Earth Pointing***
***Day 3***
***Pitch Slew for IMU calibration***
***Yaw Slew for IMU calibration***
***Roll Slew for IMU calibration***
***Day 4***
***Engineering Thruster Burn ***
***Enable Enhanced Formation Flying Software in monitor mode***
***WARP checkout***
***X-band Phased Array on and dump of WARP test pattern***

## Highlights of L&EO

***Highlights of L&EO***

***Day 5***
***ALI turn on and initial check out***
***Day 6***
***Inclination burn***
***Begin Hyperion turn on and initial checkout (done over 3 days)***
***Turn on and checkout Atmospheric Corrector (done over parts of 2 days)***
***Day 7***
***Continue Hyperion and AC checkout ***
***Day 8***
***Continue Hyperion Checkout***
***Perform All instrument data collection event***

## RFA Status

***RFA Status***

***23 RFA’s were assigned from the original MOR***
***All 23 responses submitted to Code 300***
***20 RFA’s were assigned from the Delta MOR***
***All 19 responses were submitted to Code 300***
***Last RFA to be submitted by 1/15/00***

## EO-1 FOR Results

***EO-1 FOR Results***

***Conducted 11/16/99 and 11/17/99***
***15 RFA’s identified***
***7 responses submitted to Code 300***

## Special Topic:

***MOC Simulations***

*** ******. . . Carl Gustafson***
*EO-1 Simulations Engineer *

## Simulation Special Topic

***Simulation Special Topic***

***Problem:  How to avoid early ops errors?***
***Approach:  Together with adequate training, conduct sufficient simulations to rehearse the team***
***M1  Launch Simulation***
***M2 Normal Operations Simulation***
***M3 Contingency Simulation, mixed in with other simulations***
***M4  End-to-End Science Simulation***
***M5 Launch Dress Reheasal***
***This set of simulations is sufficient to assure safe operations of EO-1 S/C.  With April launch, we will use additional time to buy down risk by conducting additional simulations***

## Simulation Status

***Simulation Status***

***Launch Simulation M1***
***Conducted over 3 days, approximately 12 hours/day***
***Personnel destined for West Coast were in building 7 and those destined to stay on East Coast were in the SOTA in building 14***
***Ground Station and TDRSS contacts simulated***
***Pre Liftoff activities***
*Network Ops Manager (NOM) activated voice circuits*
*S/C powered up on each day*
*Conducted GO/NO GO calls from L- 3hrs to L-15 min on day 1 *

## Simulation Status

***Simulation Status***

***Launch Simulations (M1)***
***Day 1 activities encompassed 4 orbits, S/C reaches sun acquisition and power is power positive***
***Day 2***
*Intiated Kalman filter*
*Commanded S/C to earth pointing*
*Attempted a gyro calibration maneuver*
*Conducted thruster burn*
***Day 3 ***
*Turn-ons of the WARP and each of the 3 instruments*
*Lamp cals and DCE’s were excercised*
*MOC generated instrument processes were validated*

## Simulation Status

***Simulation Status***

***Normal Operations Simulations M2***
***Conducted as a subset of three 16 hour transitional orbits during S/C Thermal/Vac Testing***
***Following ground system elements were exercised for these simulations:***
*Science Planning Office sent a week’s worth of image requests were FTP’d to the MOC for input into the MOPSS*
*CGS-CMS-MOPSS used to develop ATS and RTS command loads*
*FDSS provided partial predictions and predicted ground track data to MOPSS*
*DPS ingested both X-Band and S-Band instrument data recorded by the WARP*

## Simulation Status

***Simulation Status***

***Normal Ops Simulation M2 (continued)***
***Additional activities conducted***
*ALI cover mechanism was exercised twice*
*10 Hyperion SWIR DCE’s were planned and executed*
*MOC provided DCE planning for about 40 orbits*
*TDRSS Command and Telemetry interface was retested*

## Simulation Status

***Simulation Status***

***Simulation M3 ***
***Contingency Simulations M3 to be run in December and January interspersed with other simulations***
***End-to-End Science M4 completed once and scheduled again in January***
***Launch dress rehearsal M5 scheduled for late February 2000***
***Will rerun M1 about 3-4 more times***

## Special Topic:

***MOC Contingency Operations Plans***

*** ******. . . Pete Spidaliere***
*EO-1 Mission Systems Engineer *

## Contingency Procedures

***Contingency Procedures***

***Anomalies are dealt with through ***
_***Box or Instrument level Failure Detection and Correct software***_*** that, like the system level protection, sense and initiate safing events.***
_***On-board Telemetry and Statistics Monitors***_*** that sense an anomalous condition and either warn the Ground through an Event Message or initiate a Relative Time Sequence to safe the instruments and/or spacecraft.  These are system level protections.***
_***Ground-based contingency procedures***_*** that are used to determine an unsafe condition exists and what steps should be taken to return to a safe condition.***
***Required and highly desired contingency procedure have been identified and developed by the Systems, Subsystem, Instrument, and Flight Ops teams. ***
***All future simulations will contain anomalies.  This will allow  for training the team on how to use the procedures***

## Contingency Procedures

## Contingency Procedures (continued)

## Special Topic:

***Operator Training***

*** ******. . . Joe Howard***
*EO-1 ATSC Flight Operations *

## Training Special Topic

***Training Special Topic***

***Problem:  How do we assure that the FOT is adequately trained?***
***Approach***
***I&T and MOC use same control system; ASIST***
***Key FOT members worked in I&T to learn S/C***
***Each FOT member participates in necessary classroom training on S/C and instruments***
***All certified FOT members participated in the sufficient simulations***
***Since launch is scheduled for April 2000, we will use extra time to further buy down risk with additional simulations***

## Training Special Topic

***Training Special Topic***

***Approach (continued)***
***FOT all familiar with escalation process if problem occurs which includes:***
*Premium coverage of S/C experts for first 60 days*
*Access to S/C experts on an on-call basis after the first 60 days*

## Training Philosophy

***Training Philosophy***

***Types***
***On the Job Training***
*Development and I&T*
*Simulations (see Simulation section)*
***Classroom***
***Reading Operations Guides***
***Certification Process***
***Documented in EO-1 FOT Certification Process****** ***
*Draft 12/15/99    Final 1/15/99*
*Documents minimum demonstrated skills for given position*
*Positions*
*Mission Planner*
*Console*
*FDSS*
*DPS Operator*

## Training Philosophy

***Training Philosophy***

***Certification Process (continued)***
***Mission Director and FOT Lead will hold certification records of each person***
***Metric of adequate staffing will be that there is sufficient staffing so that each required position in each shift has at least one certified person***
***Current team getting training through system use***
***MOC involved with monitoring all key spacecraft test (CPT’s Thermal Vac) and were involved throughout I&T***
***Classroom training***
***Hyperion  ******	******11/18/99******	******Completed***
***ALI           ******	******1/5/00******	******Scheduled***
***AC            ******	******1/6/00******	******Scheduled***
***Technologies ******	******1/15/00******	******Scheduled***
***S/C Subsystems******	******1/15/00******	******Scheduled***
***ASIST (fast track)              ******	******Available as needed    ***

## Training

***Training***

***User’s Guides***
***Hyperion******	******Completed***
***ALI******	******Training mat will be integrated into S/C ******	******	******Users’ Guide***
***AC******	******Draft complete; Will be integrated into S/C ******	******User’s Guide***
***S/C******	******Draft 1/15/99***
***ASIST******	******Complete***
***FEDS/DHDS******	******Draft 1/15/99, Final version integrated into ******	******ASIST Users’ Guide by 2/15/00***
***MOPSS******	******Complete***
***FDSS******	******Not planned***
***DPS******	******Not planned***

## Automation Philosophy

***Automation Philosophy***

***Use automation only if phasing down to less than 24 x 7, this will only occur with L+30 review concurrence***
***Otherwise be prepared will continue to staff 24 x 7 for life of mission***
***Phase-in of automation philosophy***
***Phase 1 - Total manual control***
***Phase 2 -  Test automation***
*Step 1 – Fully manned 8 downlinks/day but run automation in parallel*
*Step 2 – Review automation performance by CCB*
*Step 3 – Approval to begin phasing over to usage of automation *

## Automation Philosophy

***Automation Philosophy***

***Phase 3 – Begin using automation***
***Step 1- Run some of the 8 passes with automation and the others manually***
***Step 2 – Review performance by CCB***
***Step 3 – Transition to up to 15 hours unmanned***
***L+30 review committee***
***Project Management***
***Instrumenters***
***Technologists***
***CCB consists  of:***
***FOT Lead***
***Mission Director***
***Mission Technologist***
***Mission Scientist***

## Automation Components

***Automation Components***

***(1)  Spacecraft Emergency Response System (SERS)***
***Testing has begun and will be complete in December 1999***
***Will beep FOT members when limits violated during off peak hours***
***(2)  Automated playback in order to produce trended data sets (graphical and sequential prints)***
***Need fix to DR 67, Scheduled for ASIST Release 8.0, January 2000***
***(3)  MOPSS drives passes***
***Needs scenarios populated***
***Will be done as time allows for FOT, however staffing sufficient to keep using manual method***
***(1), (2) and (3) each follow automation phase-in steps from previous page individually or together.  Each does not depend on the other***