# Presentation: 157133

## Section 5

***Ground System Readiness***

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

***ORR Summary***
***Ground Stations***
***Space Network***
***Science Validation Facility***
***Mission Operations Center***
***Flight Software Maintenance Facility***
***Simulations***
***Documentation***
***Remaining Work***

## Conducted on 10/3/00
Chaired by Bill Mack of Code 300 and attended by same review board as was present for the Mission Operations Review (MOR) and the Flight Operations Review (FOR)
Attended by Ron Thomas and Ann Merwarth of Red Team
Review board and attendees agreed with conclusion that EO-1 Operations is prepared for launch
Actions
1.	Check if official license to radiate with new transponder frequency was completed
2.	Create a combined EO-1/SAC-C Launch Hold criteria in time for the MRR
Question about whether SAC-C can make McMurdo a launch critical ground station
3.	Follow-up installation of ground station PTP upgrade to version 1.49

***Conducted on 10/3/00***
***Chaired by Bill Mack of Code 300 and attended by same review board as was present for the Mission Operations Review (MOR) and the Flight Operations Review (FOR)***
***Attended by Ron Thomas and Ann Merwarth of Red Team***
***Review board and attendees agreed with conclusion that EO-1 Operations is prepared for launch***
***Actions***
***1.******	******Check if official license to radiate with new transponder frequency was completed***
***2.******	******Create a combined EO-1/SAC-C Launch Hold criteria in time for the MRR***
*Question about whether SAC-C can make McMurdo a launch critical ground station*
***3.******	******Follow-up installation of ground station PTP upgrade to version 1.49***

***Results of Operational Readiness Review (ORR)***

## Operational Launch Constraints

***Operational Launch Constraints***

***EO-1***
***One of the two Northern stations (I.e., Alaska or Norway) is green for launch (includes voice and data IFs)***
***TDRSS including voice and data lines via White Sands***
***Mission Operations Control Center***
***Voice and data lines to VAFB***
***Flight Dynamics Facilities Support (Building 28 and MOC)***
***SAC-C***
***Requirement of McMurdo as prime ground station for launch being worked***

## Ground Stations

***Successfully conducted final End-to-End Interface (T5) Test between MOC and Wallops, Norway, Alaska & McMurdo on  9/14-15/00***
***Playback recorded EO-1 data from CD through system long loop***
***Tested S-Band interfaces with new (Triana) frequency***
***PTP version 1.49 tested with Compatibility Test Van (CTV)***
*In process of being installed at Wallops *
*To be installed at Svalbard, Alaska and McMurdo by 10/13/00*
***Wallops Orbital Tracking Information System (WOTIS) 8.4 operational since 05/99***
***Tracking - SCC 3.1.1 for Automated Tracking System (ATS)***
*Installed 9/18/00, tested, and is operational at Wallops*
*Installed at Svalbard and Alaska -- testing in process*

## Ground Stations (continued)

***Standard Autonomous File Server (SAFS) 1.0 operational since 05/99 – post-pass forwarding of recorded engineering data***
***Successfully conducting monthly End-to-End Science data flow Simulations (M4) which exercise X-band interfaces***
***Ampex tape recorders at Norway, Alaska and Wallops***
***Data Quality Monitors (DQM) at Alaska and Wallops ***
***RF Compatibility test successfully rerun with Triana transponder and Compatibility Test Van (CTV) on 9/16/00***
***Not tested through actual stations, rather with same equipment which resides on the CTV***
***Assured new frequency at Wallops via spectrum analyzer on 9/26/00***
***C-Band tracking ready for launch***
***Service supplied by Air Force***

## Ground Stations (continued)

***Coordination with SAC-C (co-launch with EO-1)***
***EO-1 to get Svalbard and Alaska 11 meter antennas for first 5 orbits***
***SAC-C to get Alaska 8 meter and McMurdo 10 meter antennas first few orbits***
***Plan to conduct joint Ground Interface Test and Joint Network Simulation between 10/19/00 and 10/25/00***
***Ground Network loading study conducted and reviewed by salient projects to verify that there is adequate coverage for EO-1 for L&EO and normal operations***

## Space Network

***Successfully conducted RF Compatibility test through TDRSS with (Triana) new transponder frequency and Compatibility Test Van (CTV) on 9/16/00***
***Used actual Spacecraft and Triana transponder***
***Tested and performance confirmed at the following data rates:***
*Telemetry- 2, 4, 6, 8 kbps*
*Command- 2 kbps*
***Successfully suported Launch Simulation on 9/24-26/00 through TDRSS***

## Other SOMO Services Network

***NISN***
***All interfaces to ground stations and White Sands successfully tested via T5 End-to-End tests***
***Lines to Vandenberg successfully used in Launch Simulations***
***Voice***
***5 required SCAMA lines installed and operational***
***3 additional SCAMA lines requested for launch, to be installed by 10/16/00***
***CSOC ORR to occur on 10/17/00***
***No issues with SOMO***

## Science Planning & Processing Overview

***Science Planning & Processing Overview***

***Instrument teams (MIT/LL, TRW, AC) will perform detailed instrument on-orbit calibration and performance verification during first 60 days on orbit.***
***Detailed list of DCEs have been compiled and simulated in mission planning exercises.***
***Major technologies are in the instruments and will be validated via paired scene comparison with Landsat 7 or special scene requests by NRA-selected Science Validation Team (SVT).***
***SVT has provided first draft list of scenes to MSO***
***Other technologies (except EFF and PPT) are passive requiring only trending data periodically to provide necessary validation data.***
***PPT will not be tested until end of mission***
***EFF has detailed plan for moving from semi-auto to autonomous mode.***
***XPAA will be utilized operationally, validated every 60 days.***
***NRA proposal selection based on creation of a SVT to ensure that instrument technologies are completely validated and can eventually meet future Landsat 8 science requirements***
***Metrics:  ***
***Instrument checkout reports by day 90***
***NRA Validation plans completed by end of mission (one year)***

## Science Planning & Processing Testing Summary

***Science Planning & Processing Testing Summary***

***Mission Planning Sims conducted numerous times.  Exercises the following:***
***Ingest and modification of LTAP, ground station scheduling, daily scene targeting, constraint resolution, command generation and daily load generation processes.***
***Sims in Jan, April, May, June, July August and Sept***
***One additional sim planned in Oct ***
***Continually refining and optimizing process to provide greatest return in images over early mission (Accelerated Minimal Mission concept)***
***Nine Monthly M4 Science Data Simulations have been conducted to date.***
***Verified all Ground Station Interfaces (WGS,AGS,SGS)***
***Verified data product output and performance of L0 processing system***
***Verified SVF and instrument team interfaces for real-time, trended, and playback data***
***M4 simulation planned monthly from now until launch***
***One normal operations simulation held which coupled together Mission planning and Processing system and ran on S/C (during T/V II)***

## MOC (ASIST / FEDS)

***MOC (ASIST / FEDS)***

***ASIST 8.1g Operational (includes FEDS); this is the launch release***
***Command, telemetry, user interface (includes MOC front end)***
***Completed installation and regression testing  9/20/00***
***Added capabilities from ASIST 8.0***
*Improved load, dump capability*
*Improved playback capability*
*Linux version of ASIST*
*Fix for DR 230  Dual CMS Usage*
***Testing***
*Detailed regression tested by ASIST developers*
*Functional regression testing plus fixes tested by FOT *
*Successfully conducted Launch sim 9/24-26/00 (58 hrs. with S/C)*
*Another launch sim scheduled for 10/00 (58 hours with S/C)*
*By launch, total aggregate hours on system will exceed 300 hours*

## MOC (Database) 

***MOC (Database) ***

***DB 2.1 Operational; this is the launch release***
***Completed installation and regression testing on 9/21/00***
*Total number of DBCR’s incorporated was 42*
*Incorporate limit changes from T/V II testing *
*Incorporated a  few polynomial coefficient changes*
*Commented out a few hazardous commands*
***Testing***
*Tested fixes with playback data to trigger specific limits*
*Conducted launch simulation 9/24-26/00 (58 hours with S/C)*
*Another launch simulation on 10/00 (58 hours with S/C)*
*By launch total aggregate hours on DB 2.1 will exceed 300 hours*

## Building procedure that modifies some limits in database via STOL procedure
Database Change Request’s (DBCRs)137, 140, 142, 143, 151, 152, 155, 156, 163
Will be tested by playback data
Decided that this would be strategy that we would use to incorporate lessons learned from Launch Sim’s and due to the fact that we do not have conditional limit capability

***Building procedure that modifies some limits in database via STOL procedure***
***Database Change Request’s (DBCRs)137, 140, 142, 143, 151, 152, 155, 156, 163***
***Will be tested by playback data***
***Decided that this would be strategy that we would use to incorporate lessons learned from Launch Sim’s and due to the fact that we do not have conditional limit capability***

***MOC (Database) ***

## MOC (MOPSS)

***MOC (MOPSS)***

***MOPSS 6.2 operational; this is the launch release***
***Mission Operations Planning and Scheduling System (MOPSS)***
***MOPSS 6.1 delivered and installed  8/7/00***
***Found problem and needed to patch to MOPSS 6.2***
*Delivered and installed 9/4/00; tested 9/8/00*
***Testing***
*Benchmark input and output data used and compared with previous release for Delta V maneuver, ALI & AC Solar Cal and Ground Station pass*
*Conducted actual test against S/C for Hyperion Solar Cal, Combined Lunar Cal and Combined Imaging*
*MOPSS derives database from the MOC database*
*Validated MOPSS translation of MOC database 2.1 by analysis and usage*
*MOPSS database only builds mnemonic, not binary*

## MOC (MOPSS)

***MOC (MOPSS)***

***MOPSS 6.2 (continued)***
***Testing (continued)***
*Has been used since 8/7/00 for 320 hours for 6.1/6.2 and since 9/4/00 for 160 hours for 6.2 only *
*Successfully used for Launch Sim in 9/24-26/00*
*Will be used for 10/00 Launch Sim*
*Total expected hours on MOPSS 6.2 system by launch will exceed 300 hours*

## DPS 3.0 operational and is launch release
Data Processing System (DPS) built with a FEDS
Tested during T/V II in End-to-End Science data flow
End-to-End Science simulation run monthly
Total hours on DPS 3.0 will exceed 200 hours by launch
Benchmark data set available for future post-launch release regression testing if needed

***DPS 3.0 operational and is launch release***
***Data Processing System (DPS) built with a FEDS***
***Tested during T/V II in End-to-End Science data flow***
***End-to-End Science simulation run monthly***
***Total hours on DPS 3.0 will exceed 200 hours by launch***
***Benchmark data set available for future post-launch release regression testing if needed***

***MOC (DPS)***

## MOC (FDSS)

***MOC (FDSS)***

## MOC (FDSS)

***MOC (FDSS)***

## FDF Readiness 

***FDF Readiness ***

## S/C to MOC Testingas of 9/28/00(1 of 2)

***S/C to MOC Testing******as of 9/28/00****(1 of 2)*

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

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

- P - Planned

## MOC Procedure Readiness Status

## Philosophy set forth was that if S/C test time available and CCB determines that there is a decrease in mission if procedure mod implemented then CCB approved changes
11 Procedures (one command procedure) still to be tested on 10/11/00 (per DBCR)
Discovered in contingency review as needed commands
Philosophy became that all operations in MOC are via STOL procedure therefore had to transform extra commands in procedures into one command STOL procedures
Modify and test additional procedures on 10/11/00 with S/C due to lessons learned in Launch Sim and Contingency Review per 13 approved DBCRs

***Philosophy set forth was that if S/C test time available and CCB determines that there is a decrease in mission if procedure mod implemented then CCB approved changes***
***11 Procedures (one command procedure) still to be tested on 10/11/00 (per DBCR)***
***Discovered in contingency review as needed commands***
***Philosophy became that all operations in MOC are via STOL procedure therefore had to transform extra commands in procedures into one command STOL procedures***
***Modify and test additional procedures on 10/11/00 with S/C due to lessons learned in Launch Sim and Contingency Review per 13 approved DBCRs***

***MOC Procedure Readiness***

## Tools to create patches frozen
M5 – diff-s3R
Conv_s3R
RSN-ftf.jar
Facility and equipment are ready
Facility provides capability to simulate and test patches before uploads
Facility provides capability to test procedure changes prior to operational use
Items to be completed
ACE Safe Hold Mode (SHM) Open Loop Testing	10/06/00
ACS / ACE SHM Closed Loop Testing 	10/18/00
SHM Test Review Meeting 	10/20/00
FSW patch simulation of all processors conducted on 9/23/00

***Tools to create patches frozen***
***M5 – diff-s3R***
***Conv_s3R***
***RSN-ftf.jar***
***Facility and equipment are ready***
***Facility provides capability to simulate and test patches before uploads***
***Facility provides capability to test procedure changes prior to operational use***
***Items to be completed***
***ACE Safe Hold Mode (SHM) Open Loop Testing******	******10/06/00***
***ACS / ACE SHM Closed Loop Testing ******	******10/18/00***
***SHM Test Review Meeting ******	******10/20/00***
***FSW patch simulation of all processors conducted on 9/23/00***

***FSW Maintenance Facility Readiness***

## FSW Maintenance Facility Readiness

***FSW Maintenance Facility Readiness***

## 872 hours of simulation hours expected by launch
Types
Eight launch simulations
Four normal operations simulations
Nine End-to-End Science processing simulations
Three exclusively contingency simulations, although almost all of the launch simulations had contingencies
one All ground anomalies sim
One FSW patch simulation
One Tumbling simulations
Six Science Planning simulations

***872 hours of simulation hours expected by launch***
***Types***
***Eight launch simulations***
***Four normal operations simulations***
***Nine End-to-End Science processing simulations***
***Three exclusively contingency simulations, although almost all of the launch simulations had contingencies***
*one All ground anomalies sim*
***One FSW patch simulation***
***One Tumbling simulations***
***Six Science Planning simulations***

***Simulations***

## Simulations

## Subsystems Exercised with ContingenciesDuring Launch Simulations as of 9-28-00

- Note:  All simulations specified above were launch simulations.  Sim1 was done with no contingencies and
- therefore not listed. Sim 10 still to be conducted.  Table illustrates number of contingencies exercised against
- a subsystem.

## Key documents to fly EO-1 are the Mission Procedure Document (MPD) and the S/C User’s Guide (SCUG)
Both are on the EO-1 web site 
MPD includes
Launch script
Contingency Procedure document which includes escalation procedure
Link to the Constraints database
Pertinent S/C information and procedures
Both documents will reside in hardcopy on console during operations and have been used during launch simulations

***Key documents to fly EO-1 are the Mission Procedure Document (MPD) and the S/C User’s Guide (SCUG)***
***Both are on the EO-1 web site ***
***MPD includes***
***Launch script***
***Contingency Procedure document which includes escalation procedure***
***Link to the Constraints database***
***Pertinent S/C information and procedures***
***Both documents will reside in hardcopy on console during operations and have been used during launch simulations***

***Documentation Readiness***

## Work Remaining

***Work Remaining***

***Install PTP SW 1.49 at all stations and test***
***ACE Safehold Mode (SHM)  Open Loop Testing -- 10/6/00***
***ACS/ACE SHM Closed Loop testing -- 10/18/00***
***Test 11 (1 command ea) STOL procedures derived from contingency procedure review by 10/11/00***
***Test procedure that adjusts limits per 11 approved DBCRs***
***Test procedures per 12 approved DBCR’s against S/C by 10/11/00***
***Conduct Launch Simulation on 10/12/00***
***Conduct joint Ground Station test and simulation with SAC-C by end of Oct 2000***
***Install 3 additional SCAMA lines for launch***
***Conduct part 2 of SADA training by end of Oct 2000***
***Install extra disks on DPS***
***Conduct M4 simulations to test 8 DCE/day scenario***
***Update Contingency Book to version 6 based on lessons learned from launch simulations***
***Create cross reference index for contingency book post launch***
***Finalize DTAS configuration***

## EO-1 CSOC Requirements

***EO-1 CSOC Requirements***

*** ******Ground Network***
*** ******Alaska, Svalbard and Wallops stations provide S-band and X-band telemetry, command and tracking services.***
***McMurdo station provide S-band telemetry and command services.***
***Space Network***
*** ******TDRSS provide S-band and telemetry, command and tracking services.***

## EO-1 CSOC Requirements(continued)

***EO-1 CSOC Requirements****(continued)*

***Flight Dynamics Facility (FDF)***
***Provide acquisition data and orbit determination during Launch and early orbit (approximately L+8 hours).***
***NASA Integrated System Network (NISN)***
***Provide voice and data lines connectivity to EO-1 mission ground systems.***

## EO-1 CSOC Status

*** ******CSOC Resources Status***
***All GN and SN requirements verified through End-to-End Interface (T5), Compatibility testing and Launch Simulations with the spacecraft and MOC.***
***FDF and NISN requirements demonstrated throughout testing and simulations.***
***3 additional voice circuits requested for launch, to be installed by 10/16/00.***
***CSOC Readiness***
*** ******CSOC is ready to support EO-1 mission pending last GN and SN Network Simulation scheduled 10/24/00 and 10/25/00 and successful installation and checkout  of additional voice circuits.***

***EO-1 CSOC Status***

## EO-1 CSOC Work Remaining

***EO-1 CSOC Work Remaining***

*** ******GN and SN Network Simulation***
***Conduct simultaneous testing of EO-1 and SAC-C spacecraft with Alaska and Svalbard stations 10/19 and 10/20.***
***Conduct simultaneous Launch and Early Orbit simulation of EO-1 and SAC-C spacecraft with GN and SN facilities on 10/24 and 10/25.***