# Presentation: 076984

## Section 33

_***Section 33***_
***Operations / MOC***

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

## Contents

***Contents***

***Overview of Operations******	******Dan Mandl***
***Testing and Verification Status***
***MOC H/W Status***
***MOC Procedure Status***
***Launch Overview***
***Documentation***
***Configuration Management***
***SOMO Institutional Mission Operations Support***
***RFA Status from Previous Reviews***
***Readiness and Residual Risks:  Redbook Candidates***
***Special Topics***
***MOC Simulations******	******Gus Gustafson***
***Contingency Operations******	******Pete Spidaliere***
***Ampex Recorders                                                          Dan Mandl ***
***How Ops Plans to Avoid Instr Overheating                Bruce Trout***
***Operator Training                                                           Joe Howard***
***Operator Staffing Versus Functions-Overloaded?     Joe Howard***
***Planned Cooperation with Landsat                              Bob DeFazio***

## Operational Philosophy

***Operational Philosophy***

***1 year mission***
***During Normal Ops***
***3-8 passes/day (2 for science dumps)***
***During L&EO***
***14 passes/day (2 for science dumps) during first week***
***8 passes/day (2 for science dumps) from L+8 to L+60***
***80 Gb of data max (typ 2 DCE’s) 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***

**Ops Overview**

## Operations Overview

**Ops Overview**

## Operational Phases

***Operational Phases***

***Launch & Early Orbit***
***Launch and the first several orbits, spacecraft checkout, and instrument turn-ons***
***Approximately 15 days (20 days to get to 1 min behind Landsat)***
***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***

**Ops 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*

**Ops Overview**

##  Ground System Requirements Summary

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

***Process Hyperion, MS/PAN, 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 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*

**Ops Overview**

## 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
Other technology validation operations
Calibration operations
Contingency operations
Archive raw and processed data

***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***
***Other technology validation operations***
***Calibration operations***
***Contingency operations***
***Archive raw and processed data***

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

**Ops Overview**

## Verification Approach

***Verification Approach***

***Verified against***
***EO-1 Ground Functional and Performance Requirements***
***Detailed Mission Requirements (SOMO services)***
***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, and S/C subsystem engineers for final end-to-end check of team’s ability to perform required tasks***
***Post-Launch Verification of new releases of ground S/W***
***Regression testing by means of shadowing operations and comparing results with previous version***

**Testing & Verification**

## EO-1 Operations Testing Status

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

**Testing & Verification**

## Slide 11

## Requirements Verification

***Requirements Verification***

***94 % of the requirements verified***
***Unverified requirements***
***7 Instrumenter requirements not verifiable before launch because involve providing L&EO support***
***SVF shall receive DCE and calibration requests from Science Validation Team ***
***SVF shall perform Level 1 processing of AC data after receipt of code from AC Instrumenters***
***Interface with FDF algorithms to schedule activities/commands for momentum management***
*Mostly tested, waiting for delivery by 4/15/00 of enhancement to complete verification*

**Testing & Verification**

## Requirements Verification

***Requirements Verification***

***Unverified requirements (continued)***
***4 GN requirements only testable post launch, involves performance of personnel at ground stations***
***2 CGS requirements involve testing capability of SERS to page FOT member***
*Capability in process of testing*

**Testing & Verification**

## Ground Discrepancy Reports (DR) Status

***Ground Discrepancy Reports (DR) Status***
***as of 3-16-00***
*Critical DRs*

***DR 58-FDSS:  Add Solar Array modeling to computation of reaction wheel speeds***
***Fix in testing, complete by 4/15/00***
***DR 150-Networks: During simulation, lost socket connection to STGT for commanding***
***Under investigation***

**Testing & Verification**

## Ground DR Status as of 

***Ground DR Status as of ***
***3-16-00***
*Urgent DRs*

***DR 16-ASIST:  Capability to change limits from database lookup window***
***Under investigation***
***DR 18 & 67-ASIST:  Slow playback***
***Fix being developed, complete 4/30/00***
***DR 163-ASIST:  SOH HDF files have error***
***Fix in process for patch to be delivered by 4/30/00***
***DR 10-DHDS:  Playback can’t be automated***
***Same fix as DR 18 and DR 67***
***DR 82-FEDS:  Translator needed for VC4***
***In process of being developed.  Date of delivery TBD***
***DR 114-FEDS:  Command interface problem with SN.  Statistics wrong***
***Under investigation ***
***DR 164-Ground:  During Time correlation test, PTP offset time by 300 msec***
***Under retest by 3/21/00***
***DR 55-MOPSS:  MOPSS needs fail-over capability***
***In process of configuring dual workstation fail-over mode.  Almost complete***
***DR 169-MOPSS:  Problem with command DB ingest***
***Problem fixed, waiting for retest***
***DR 79-Net:  Ampex recorder at Wallops broken***
***Fixed, under retest ***

**Testing & Verification**

## Ground DR Status as of 

***DR 151-Net:  ATS load configured S/C for 2K coherent.***
***Under investigation***
***DR 71-OPS:  Need to build ground station summary report***
***Action assigned to FOT***
***DR 84-Ops:  WARP directory needs to be a flat file***
***Action assigned to FOT***
***DR 107-Ops:  Monitor was unreadable***
***Action assigned to Jim Weidman, system admin.***
***DR 111-Ops: Command to SCP rejected***
***Under investigation***
***DR 115-Ops:  When command TDRSS 4k downlink, page shows error.  Possible RDL problem***
***Under investigation***
***DR 109-S/C:  During sim, TSM’s 53, 63, 71, 72 and 73 failed***
***Submit as S/C PR***
***DR 119-S/C:  During sim, unable to go backward in time***
***Under investigation by K. Blackman***
***DR 120-S/C:  During sim, no command link.  Problem in I&T***
***Assigned to I&T***
***DR 166-S/C:  Limits need to be changed for new command DB for MOPSS***
***Assigned to I&T ***

***Ground DR Status as of ***
***3-16-00***
*Urgent DRs (continued)*

**Testing & Verification**

## S/C to MOC Testing(1 of 2)

**Testing & Verification**

## S/C to MOC Testing(2 of 2)

- P - Planned

**Testing & Verification**

## Simulations

***Typical content of Launch and Day 2 simulation and contingencies are discussed in the MOC Sim special topic***

**Testing & Verification**

## EO-1 Data Link Configuration for Testing and L&EO

## EO-1 Data Link Configuration for Normal Ops

## MOC Hardware Status

***MOC Hardware Status***

***All MOC hardware in place except the following:***
***Trending system – waiting for delivery of PC***
*Using temporary PC in the meantime*
***MOC firewall***
***Have in house, but waiting for NISN approval of revised Security Plan ***
***Will be installed during 4/00***

**Hardware Status**

## MOC Procedure Status

***Regular Procedures tested***
***ACS******	******66/66***
***PSE******	******13/13***
***RCS******	******2/2***
***GPS******	******8/11***
***LFSA******	******2/2***
***MV******	******7/8***
***WARP******	******14/32***
***Combined Inst******	******17/17***
***AC******	******11/11***
***ALI******	******25/35***
***Hyperion ******	******32/43***
***COM/CDH ******	******5/9***
***RF******	******4/9***
***Timecode******	******3/3***
***Ground******	******6/6***
***ATS******	******9/9***
_***Recorder***__***	***__***3/5***_
***Total******	******233/284  = 82%***
***Contingency Procedures tested    31/51 =  60%***
***100% written***

**MOC Procedure Status**

## 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 3 km crosstrack.   ***
*The launch vehicle injection point is near the start of first ascending node.  The Local time will be ~22:04. *
*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***

**Launch Overview**

## 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 Overview**

## Launch Day Orbit Ground Trace

**Launch Overview**

## Day 1
Launch, Launch vehicle separation, SA deployment
B-dot and sun acquisition
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
Test Safehold Logic
Go to Earth Pointing
Day 3
Pitch Slew for IMU calibration
Yaw Slew for IMU calibration
Roll Slew for IMU calibration
Reengineering Thruster Burn
Day 4
Enable Enhanced Formation Flying Software in monitor mode
WARP checkout
X-band Phased Array on and dump of WARP test pattern

***Day 1***
***Launch, Launch vehicle separation, SA deployment***
***B-dot and sun acquisition***
***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***
***Test Safehold Logic***
***Go to Earth Pointing***
***Day 3***
***Pitch Slew for IMU calibration***
***Yaw Slew for IMU calibration***
***Roll Slew for IMU calibration***
***Reengineering Thruster Burn***
***Day 4***
***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***

**Launch Overview**

## Day 5
ALI turn on and initial check out
Inclination burn
Day 6
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
Day 9
Rest Day (contingency)
Day 10
Safehold test
S/C recovery from safehold
Day 11
Instrument recovery from safehold
Activity plan lays out the detailed plan for the first 11 days

***Day 5***
***ALI turn on and initial check out***
***Inclination burn***
***Day 6***
***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***
***Day 9***
***Rest Day (contingency)***
***Day 10***
***Safehold test***
***S/C recovery from safehold***
***Day 11***
***Instrument recovery from safehold***
***Activity plan lays out the detailed plan for the first 11 days***

***Highlights of L&EO***

**Launch Overview**

## L&EO Organization

**Launch Overview**

## 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 Operations Manager 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***
***Gabrielle Araiza is librarian to assure that documents in MOC library are up to date***

**Documentation**

## Key Documents for Operations

**Documentation**

## Key Documents for Operations

**Documentation**

## S/C User’s Guide Status

- Completion of S/C User’s Guide scheduled for 6/00 after all training is done and the feedback folded into the User’s Guide

**Documentation**

## Mission Procedures Document

***Mission Procedures Document***

***Mission Procedures Document (MPD) on EO-1 website***
***MPD Vol 1 is the Ops Concepts***
***MPD Vol 2, Detailed Ops Plans***
***Launch & Early Orbit (L&EO)***
*Pre-Launch Script (in process of being created)*
*Launch Script (baselined)*
*Instrument Checkout Scrip(baselined)*
*L&EO Specific Procedure*
***Normal***
*Normal operations procedures*
*Contingency procedures (flowcharts and scripts)*
***General***
*Telemetry and Statistics Monitors (baselined)*
*FDC’s (baselined)*
*Relative Time Sequences (baselined)*
*List of pages*
*List of S/C Event messages*
*Problem escalation procedures*
*CM Plan for Procs, Pages, Documents and S/W*

**Documentation**

## 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 sys admin
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 access
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***_***  (select configuration management)***
***ISO Compliant***
***Procedures***
***Tested***
***Placed global procedure directory***
***Write privileges only by sys admin***
***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 access***
***Temporary changes placed in global directory by any FOT member***
***Changes via DB change request forms***

***Configuration Management***

**Configuration Management**

## SOMO Institutional Mission Operations

***SOMO Institutional Mission Operations***

*FOT and sustaining engineering under a CSOC SODA*
*Ground station and Space Network support under CSOC*
*Requirements driven by Detailed Mission Requirements(DMR)  & Mission Operations Support Plan(MOSP)*

**SOMO Institutional Support**

## RFA Status

***RFA Status***

***23 RFAs were assigned from the original MOR and are closed***
***20 RFAs were assigned from the Delta MOR***
***19 are closed***
***1 response was submitted and still under review***
***14 RFAs were assigned from the FOR***
***10 closed***
***5 responses resubmitted and still under review***

**RFA Status**

## Critical RFA Status

**RFA Status**

## Critical PR

***Critical PR***

***Critical PR 675-20-2, 829-30-2 and 829-30-3 are being held open***
***S/C side is okay***
***Ground has some residual problem on the PTP front end at the ground stations***
*As a result recent tests stay marginally within specs for time correlation operations activities*
*PTP problems presently under investigation*

**RFA Status**

## Readiness and Residual Risks:

*** ***

***Readiness and Residual Risks:***
***Redbook Candidates***

***No significant residual risk***
***WARP repair provides additional simulation and training opportunities***
***No Redbook candidates***
***Operations is on schedule to support the launch***

## Special Topic:

***MOC Simulations***

*** ******. . . Gus Gustafson  ***
*EO-1 Simulation Manager*

## Simulation Summary

***Simulation Summary***

***Sim 1:  Normal operations during Thermal/Vac 10/10,13,16/99***
***Primary ATS loads exercising the instruments in routine operational modes***
***All three instruments exercised***
***3 separate days of operating were conducted (16 hours ea.) including X-band dumps and data processing activities***
***Exercised the MOPSS***
***Ground stations not involved***
***Sim 2:  Launch simulation days 1, 2 and 3 (no contingencies)***
***10/28/99, day 1 Prelaunch and launch activities through 5 orbits resulting in S/C having achieved sum acquisition and being power positive***
***Included Star Tracker and GPS turn on***

## Simulation Summary

***Simulation Summary***

***Sim 2:  Day 2 10/29/99***
***Real world orbits 12 through 42, activities compressed into 7 orbits***
***Energized slewing to Earth pointing***
***One of three Gyro calibration slews***
***Delta V thruster burn***
***Sim 2:  Day 3 11/3/99***
***Real world orbit 44 through 103, activities time compressed into 12 hours***
***Included WARP and instrument turn-ons as scripted***
***S-band and X-Band downlinks exercised***
***Data processing activities conducted***
***Ground stations not involved, however used TDRSS support during Day 1***
***2 unplanned contingencies******	***

## Simulation Summary

***Simulation Summary***

***Sim 3:  Launch simulation with contingencies (Days 1 & 2) 12/13 & 14/99***
***Same scripting as Sim 2 but with contingencies***
***6 planned contingencies, 1 unplanned***
***Sim 4:  science end-to-end simulation, Day 23***
***Included ground stations (SGS, AGS and WGS)***
***No S/C interface***
***Verified command and telemetry interfaces from MOC to all three stations***
***Verified the science planning interfaces***
***Stations provided***
*Tracking data files*
*Station status messages*
*Standard Autonomous File Server (SAFS) data*
*Post pass summaries*

## Simulation Summary

***Simulation Summary***

***Sim 4:  science end-to-end simulation, Day 23***
***Exercised the Data Processing System for S-band and X-band data processing, including distribution of data products***
***Exercised data links to TRW and MIT/LL for realtime and playback data***
***Exercised the Data Quality Monitor system at WGS***
***Provided tapes to the Science Validation Facility***
***Exercised MOC trending capability***
***Sim 5:  Repeat of science end-to-end  1/4/00***
***Sim 6  Launch simulation with contingencies (Day 1 only) 1/14/00***
***4 planned contingencies***
***Sim 7:  Launch simulation with contingencies (Days 1 & 2)  1/24&28/00***
***13 planned contingencies and 2 unplanned***

## Simulation Summary

***Simulation Summary***

***Sim 8:  Repeat of science end-to-end 2/2/00***
***Sim 9:  Mini-Sim exercising safehold and safehold recovery 2/4/00***
***Sim 10:  Mini-sim exercising a thruster burn  2/16/00***
***Sim 11:  Launch sim with contingencies (Day 1 & 2)  2/17&18/00***
***15 planned contingencies***
***Sim 12: Repeat of the science end-to-end simulation 2/23/00***
***Sim 13:  Simulation of the S/C tumbling post separation  3/9/00***
***Sim 14:  Launch sim with contingencies***
***4 planned and 1 green card***

## Subsystems Exercised with Contingencies

**Planned 43    Unplanned 5   Total 48  **
**Note:  Since a given contingency may affect more than one subsystem, this explains the difference between the number of contingencies totaled in the line above and the number of total number from the right most column of the chart.**

## Special Topic:

***MOC Contingency Operations Plans***

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

## Contingency Procedures

***Contingency Procedures***

***Anomalies are dealt with through the following: ***
_***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.***
_***Box or Instrument level Failure Detection and Correction software***_*** that, like the system level protection, sense and initiate safing events.***
_***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 procedures have been identified and developed by the Systems, Subsystem, Instrument, and Flight Ops teams. ***
***Testing of approximately 60% of the procedures has occurred and the remainder will be tested before shipment.***
***All simulations, except the first, have contain anomalies.  This allows for training the team on how to use the procedures.***

## Contingency Procedures

***Contingency Procedures***

***Procedures exist in the form of STOL Procs and Decision Trees.***
***All STOL Procs will be tested before use.***
***Decision Trees will, by their nature, be verified by review.***
***Most of the STOL Procs have been developed and tested.  The Flight Software Team has been occupied with other high priority tasks, but is now free to aid in the development of C&DH STOL Contingency Procs.  ***
***Many of the Decision Trees have been developed and reviewed.  Several have been tested during Simulations, and the need for others has been determined during the Simulations.   None can be considered final at this time, but most are quite mature and have been through a round of Systems Level review. ***

## STOL Contingency Procedures

## STOL Contingency Procedures (continued)

## STOL Contingency Procedures (continued)

## Decision Trees

***Decision Trees***

***LV Separation Anomaly ***
***SA Fails to Deploy***
***Communications Anomalies***
***No Telemetry***
***No Commanding***
***TDRS Telemetry/Commanding anomaly***
***MOC Misconfiguration***
***Ground Station Loss of Comm***
***NISN Contingency***
***Power Anomalies***
***Half Battery Voltage Differential***
***Battery Temperature***
***Battery Undervoltage***
***Battery Overvoltage***

## Decision Trees

***Decision Trees***

***ACS***
***BDOT System Momentum Not Decreasing***
*Tip-Off rates higher than worst case*
*Phasing error*
***SA Drive Not Driving to Zero Degrees (early orbit)***
***Sun Acquisition Mode Anomaly***
*Residual magnetic dipole higher than expected*
*Phasing error*
***AST Failure***
***MTR Failure***
***TAM Failure***
***IRU Failure***
***RWA Failure***
***XPAA Pointing Anomaly***

## Critical PRs and RFAsAddressed in This Section

***Critical PRs and RFAs******Addressed in This Section***

***RFA 18.15:  Status and Verification of Contingency Procedures***
***PR 675-20-4:   Red High Limit on Atmospheric Corrector Power Supply Card***

## Special Topic:

***Ampex Recorders***

*** ******. . . Dan Mandl  ***
*EO-1 Ground Systems Manager*

## Ampex Recorder Status

***Ampex Recorder Status***

***Ampex tape recorders (Special Topic)***
***Reliability of Ampex tape recorders at ground stations in question at FOR***
***Developed Ops procedure whereby during initial 30 days when tape is recorded, tape is played back through DQM before shipping to MOC to verify good data on tape***
***All Ampex tape units fixed at ground station and are operational at present time***

## Special Topic:

***How Operations Plans to Avoid Instrument Overheating***

*** ******. . . Bruce Trout  ***
*EO-1 Mission Planner/FOT*

## On-Board Protections

***On-Board Protections***

***ALI, HIS, AC all utilize thermostatically controlled heaters***
***TSMs in place / verified which monitor key temperatures and safe instruments if necessary***
***ALI 28v service OFF if FPE board, ALI radiator, or 28v service current too high***
***HSI 28v service OFF if ASPs too hot***
***AC 28v service OFF and AC turn on RTSs disabled if PSB too hot***
***Additional HSI internal FDC checks / safing performed ***
***Cal lamps OFF if lamps on too long***
***HSI safehold if ASP temps too high***
***ALI also performs internals checks / safing***
***Temperatures (FPE radiator, motors)***
***Currents (heaters, lamps, 28v input, motors, HOPAs)***
***On time (FPE, HOPA, motors)***

## Operations Plans

***Operations Plans***

***Round the clock operations staffing planned***
***Instrument reps to be co-located with FOT during instrument check-out operations***
***Capability to view real time and archive telemetry from instrument remote facilities also exists and verified***
***Up to every orbit ground station coverage planned to allow monitoring of S/C / instruments***
***MOC performs limit checking and can initiate safing commanding if necessary***
***Command procedures developed and verified which can be used to safe instruments and to perform planned instrument operations***
***A number of functional tests and sims performed to demo people, plans, and procedures***

## Operations Plans (continued)

***Operations Plans ****(continued)*

***Initial instrument ops performed during RT contacts to allow monitoring / safing (if required)***
***Ground initiated science collects***
***Ensures instruments “turned off” following science collects***
***Routine science ops performed from stored command. Processes in place and verified numerous times (TV, CPT, functional tests) to process requests and schedule required commanding. Scenarios include:***
***Images***
***Solar Cals***
***WARP Data Ops***
***ALI Internal Cals***
***Lunar Cals***

## Special Topic:

***Operator Training***

*** ******. . . Joe Howard  ***
*FOT Lead*

## FOT Training

***FOT Training***

***Major finding of FOR was that classroom training needed strengthening. This has been done***
***Training developed as result of FOR***
***Plan follows CSOC ISO-9001 approved training plan***
***Flight Dynamics Support***
***Command Controller***
***Mission Planner***
***Data Processor***
***Training consists of:***
***S/C subsystem classroom and video training***
***Classroom ground system training***
***Various specialty classes such as STK training and familiarization with the Flight Dynamics Support System***
***OJT through simulations and I&T***
***ATSC sponsored Center for Operations, Research & Engineering (CORE)***

## FOT Training

***FOT Training***

***Training documented through Training Event Reports, Job Requirement Checklist, Skills Catalog, and Certification***
***Certification follows the CSOC approved certification process***
***FOT member must complete their Skills Catalog and receive favorable evaluations before FOT Lead and Mission Operations Manager will sign Certification Certificate***

## S/C Training Status as of 3-8-00

## Ground Training Status as of 3-8-00

## Special Topic:

***Operator Staffing Versus Function-Overloaded***

*** ******. . . Joe Howard***
***  ****FOT Lead*

## Functional 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 Experience (Core)

## FOT Experience (Supplementing L&EO)

## FOT Experience (Supplementing L&EO)

## FOT Shift Profile

***FOT Shift Profile***

***Power up shift: Before launch to L+3 days***
***2 x 12 hour shifts for first 7 days and then transitioning to 3 shift operations***
***L+3 to L+60 3 shifts supplemented with returning TCs 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***

## FOT Shift Support – Week 1

***FOT Shift Support – Week 1***

**(12 hours)**

**Back shift**

**Prime shift**

## FOT Shift Support – Week 2 to L+60

***FOT Shift Support – Week 2 to L+60***

**(8 hours)**

**Night shift**

**Prime shift**

**Swing shift**

## FOT Shift Support – Normal Ops (w/ Automation)

***FOT Shift Support – Normal Ops (w/ Automation)***

**(8 hours)**

**Night shift**

**Prime shift**

**Swing shift**

- Note that shifts for selected FOT will be offset by 4 hours to provide 12 hours coverage M-F

## FOT Staffing Conclusion

***FOT Staffing Conclusion***

***Based on the present operations plan, we are adequately staffed***

## Special Topic:

***Planned Cooperation with Landsat 7***

*** ******. . . Bob DeFazio  ***
*EO-1 Flight Dynamics*

## Landsat-7 / EO-1 Interface

***Landsat-7 / EO-1 Interface***

***The Landsat-7  /  EO-1 Interface is documented in an ICD that was prepared, reviewed and signed off by both projects***
***ICD content includes flight dynamics issues, cloud cover products, Landsat-7 daily target list and Landsat-7 cloud cover assessment scores***

## Landsat-7 / EO-1 Flight Dynamics Planning

***Landsat-7 / EO-1 Flight Dynamics Planning***

***To retain the Landsat-7  /  EO-1 formation flying configuration, Landsat-7 must inform EO-1 about current Landsat-7 orbit position and future orbit maneuver plans ***
***Landsat-7 will provide a daily orbit state vector and a weekly product set that details their orbit maneuver plans over the next 6 weeks***
***EO-1 will use the Landsat-7 inputs to plan EO-1 maneuvers that maintain the Landsat-7  /  EO-1 formation flying configuration***

## Landsat-7 / EO-1 Co-Imaging

***Landsat-7 / EO-1 Co-Imaging***

***To plan and validate the co-fly images taken by Landsat-7 and EO-1 the following items will be provided to EO-1:***
***From the National Center for Environmental Predictions (NCEP) predicts of cloud coverage will be available to EO-1 daily from the NOAA NCEP website***
***A Landsat-7 daily target list will be available to EO-1 Monday-Friday from a Landsat-7 website***
***Landsat-7 post-imaging cloud cover assessment scores will be available to EO-1 from the Earth Resources Observation System (EROS) Data Center******	******	******	******	******	***

## Landsat-7 / EO-1 Interface Validation

***Landsat-7 / EO-1 Interface Validation***

***Since October 1999***
***Run FreeFlyer on Fridays to provide model of next 6 weeks of maneuvers for Landsat***
***Product output from FreeFlyer is input into Autocon-G which then generates a 35 day ephemeris for EO-1***
***Products from Autocon-G are sent through FORMATS and MOPSS to generate simulated image planning***
***Planned simulated EO-1 scenes are compared with Landsat image plan as a check***
***This exercise is done on a weekly basis***