# Presentation: 819921

## Section 34

_***Section 34***_
***Validation of Mission Technologies***

*** ******. . . Nick Speciale  ***
*EO-1 Mission Technologist*

## NMP Technology Evolution

***NMP Technology Evolution***

## EO-1 Technology Validation Overview

***EO-1 Technology Validation Overview***

***Instrument teams (MIT/LL, TRW, AC) will perform detailed instrument on-orbit calibration and performance verification during first sixty days on orbit.***
***Detailed list of DCEs have been compiled and simulated in mission planning exercises.***
***Major technologies are in instrument and will be validated via paired scene comparison with Landsat 7 or special scene requests by NRA selected Science Validation Team.***
***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 proposals selection based on creation of a  Science Validation Team 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 (1 year)***

## Some Things to Keep in Mind

***Some Things to Keep in Mind***

***EO-1 is a Technology Validation Mission which is significantly different than a operational science mission***
***Only data necessary to validate instrument technologies is required for mission success  ***
***Goal is to achieve technology validation mission success objectives as quickly after launch as possible ***
***Science Validation team (35 investigators), selection based on fulfilling instrument  technology validation goals***
***Technologies and instruments on EO-1 are advanced prototypes not final science-grade instruments***
***ALI, Hyperion and AC will be refined and fully populated for future Landsat follow-on missions***
***Significant success has already been achieved by advancing these technologies to flight readiness***
***Previous hyper-spectral mission (LEWIS) was baselined to only deliver 1 hyper-spectral scene (DCE) per day ***
***EO-1 will deliver 4 times that amount of data each day ***

## Baseline Technology Validation Timeline

- L&EO / C/O

- Normal Ops

- 24

- Normal Ops

- 8

- At least 2 shifts/day 5 days per week

- ~14

- Init C/O

- Normal

- 6-8

- 24/7

- PPT Validation

- Outgas

- Normal

- Fct C/O

- GSFC Alg C/O

- GSFC Alg Auto Mode

- JPL Alg C/O

- JPL Alg Auto Mode

- Establish formation (~4 burns)

- Formation maintenance burns (weekly)

- S/C planned

- Ground planned

- Grd plan

- S/C planned

- ~8

- L+7

- L+30 day

- Perf C/O

- Full C/O

- L+60 day

- L+120 day

- L+180 day

- L+240 day

- L+270 day

## Current Mission Checkout Timeline

***Phase I:******	******S/C and Instrument turn-ons   (Days 1-9)***
***Phase Ia:******	******S/C checkout / catchup L7/test DCE’s (2-3 day quick ******	******	******turn) (Days 10-21)***
***Phase II:******	******Technology Validation (Days 21 - 60)  3-4  DCE’s/Day***
***Phase III:******	******SVT Minimal Validation (Days 61- 365) 3- 4 DCE’s/Day***

**Phase II**

- Day 21

- Day 60

- Day 365

**Phase III**

**Phase I & 1a**

## CurrentBaseline InstrumentCritical Event Timeline

***Current******Baseline Instrument******Critical Event Timeline***

***Day 4 - WARP/XPAA activation and checkout***
***Day 5 - ALI activation and DCE***
***Day 6/7 - Hyperion and LAC activation and DCE per instruments***
***Day 8 - Combined instrument DCE (under RTS control)***
***Day 10 - 21  (Catchup to L7, outgassing, Hyperion VNIR only) ***
***Collect 2-3 DCE’s per day to  evaluate S/C and instrument interaction (alignment, jitter, momentum control etc.). ***
***Outgassing in process. Quick turnaround downlinks to WGS. Perform initial solar/lunar calibrations***
***Burns to fly in formation with L7, nominally 2-3 DCEs per day to continue to  evaluate alignment and pointing performance***
***Day 21 - 69  Instrument Checkout Phase (Formation flying with L7)  ***
***Hyperion SWIR activation***
***Commence Phase II, instrument on-orbit calibration and checkout ***
***4 DCEs per day, daily cloud cover assessment, 5 day/week planning support***
***Instrument checkout reports due on day 90***
***Day 69-365   (Science Validation Team Phase)***
***Commence Phase III ***
***4 SVT DCEs  per day ***
***SVT reports due after 1 year of operations***

## Baseline Requirements

***Baseline Requirements***

***Schedule best 3-4 prioritized scenes daily (17 Gbits/scene or DCE).  Usually all 3 instruments will image same ground track simultaneously.***
***3-4  X-band down links daily to ground stations***
***Alaska is prime G/S during nominal Ops period***
***Wallops is prime G/S during EOC***
***Approximately 80 Gbit of data per day processed by MOC to level zero DLTs each day.***
***Approximately 1000 DCEs over mission life; 200 for commercial Hyperion users***
***Level 0 or Level 1R data processing based on SVT***

## Unique Aspects ofEO-1 Science Processing System

***Unique Aspects of******EO-1 Science Processing System***

***Overall goal is to capture and process approximately 90% of requested scenes for SVT. Therefore:***
***No extensive reprocessing of data is planned nor funded, minimal redundancy, no hot backups in place***
***Processing timeframes are long (over two weeks during nominal ops)***
***Data quality assessment is minimal, only that necessary to quickly diagnose failure mechanisms to subsystem level are in place***
***Rescheduling of  image is most likely recourse in case data is lost***
***Limited budget and operations staffing***

## Science Data Processing Products

***Science Data Processing Products***
***and General Timelines***

## Special Data Services

***Special Data Services***

***To support timely instrument checkout and image reconstruction, the following special data output products were agreed upon for all instrument teams. (Individual  ICD for each interface defines the particular data formats).***
***A subset of instrument and S/C SOH and engineering data collected by WARP during each DCE shall be processed to engineering units.  A special file (in HDF format) will be written to each DLT with this data ***
***A set of trended (sequential print) SOH parameters will be trended daily in engineering units from received stored engineering data (from ACDS ) and made accessible electronically to instrument checkout teams***
***All recorded SOH engineering data will be made accessible electronically  for processing into engineering units via a web-based interface  ***
***During initial instrument turn on and ops (first few days) the S-band contingency mode utilized to support quick turnaround delivery of L0 processed small image sets (<125 Mbytes) to instrument teams***
***To expedite instrument validation after this initial turn on the Wallops G/S will be utilized for collection of full images via X-band, and expedited delivery and turnaround will occur in the DPS***

## Science System Context

- TRW

- Science
- Validation
- Facility

- Science
- Data

- GSFC
- AC

- ACHyp, ALI L0 &L1 Products

- SVT

- AC, ALI L0,  L1 Products,
- Hyperion L0, L1 Products

- Product Request

- Orbit/
- Attitude Data

- Collection Requests

- Hyperion L0,L1
-  Products

- DCE Requests

- L0 Data

- S-band HK Data

- L7 GS

- Mission
- Planning
- Office

- Ground
- Stations

- N
- I
- S
- N

- Scheduling

- Commands

- Telemetry

- Tracking,
- Scheduling,
- Command,
- Telemetry

- FDSS Products

- Trending Data

- Mission
- Operations
- Center

- NCEP

- Cloud
- Predicts

- Image Tracking
- Data based updates

- L7 Collection
- Coordination

- Catalog Updates/Queries

- Level 1 Data
- Exchange

- Cal Coeff
- Updates

- Level 1 Data
- Exchange

- MIT/LL

## System DescriptionGround Station Science Planning and Processing Functions

***System Description****Ground Station Science Planning and Processing Functions*

***Provides X-band down linked data to the MOC via tape (mailed to MOC twice per week during normal ops)***
***Provides raw X-band data storage for up to 30 days***
***Provides S-band data interface to the MOC***
***Electronically transfers recorded State of Health (SOH) post pass***
***Provides real-time data to the MOC***
***Provides early orbit and quicklook S-band science data to the MOC electronically post-pass***
***Real time and post pass data quality monitoring statistics***

## Provides orbit/attitude data to the Mission Planning Office to aid in planning and to the instrument/science teams
Receives a prioritized schedule of prime/alternate targets from the Mission Planning Office, updates to long term plan received weekly
Ingests NCEP cloud predicts to remove scenes from plan
Accesses the Landsat 7 target list schedule to ensure paired scenes are scheduled with L7
Provides image tracking database updates to the Mission Planning Office on DCE status:
Includes return link quality information
DCE scheduling information
DCE processing status

***Provides orbit/attitude data to the Mission Planning Office to aid in planning and to the instrument/science teams***
***Receives a prioritized schedule of prime/alternate targets from the Mission Planning Office, updates to long term plan received weekly***
***Ingests NCEP cloud predicts to remove scenes from plan***
***Accesses the Landsat 7 target list schedule to ensure paired scenes are scheduled with L7***
***Provides image tracking database updates to the Mission Planning Office on DCE status:***
***Includes return link quality information***
***DCE scheduling information***
***DCE processing status***

***System Description****MOC**Science Planning Functions*

## Ingests AMPEX DCE tapes from the EPGN or Wallops
Processes AMPEX DCE tapes to HDF Level 0 data files for ALI, AC, and Hyperion
Processes selected DCE housekeeping from WARP data to engineering units onto DLT in HDF format.
Provides tapes (DLT) of the Level 0 data products (including the DCE housekeeping files) to the instrument teams  
Overnight Fed Ex. Once per day in the L to L+2 month time
Distributed twice a week after L+2 months
Provides the capability to provide small (<125 MB) level 0 data sets electronically during initial instrument checkout (first few days) and during  contingencies.
Provides access to recorded spacecraft SOH data electronically 
Provides access to selected instrument SOH trending data electronically throughout mission

***Ingests AMPEX DCE tapes from the EPGN or Wallops***
***Processes AMPEX DCE tapes to HDF Level 0 data files for ALI, AC, and Hyperion***
***Processes selected DCE housekeeping from WARP data to engineering units onto DLT in HDF format.***
***Provides tapes (DLT) of the Level 0 data products (including the DCE housekeeping files) to the instrument teams  ***
***Overnight Fed Ex. Once per day in the L to L+2 month time***
***Distributed twice a week after L+2 months***
***Provides the capability to provide small (<125 MB) level 0 data sets electronically during initial instrument checkout (first few days) and during  contingencies.***
***Provides access to recorded spacecraft SOH data electronically ***
***Provides access to selected instrument SOH trending data electronically throughout mission***

***System Description****MOC**Science Processing Functions*

## Consists of *Mission Scientist, Mission Technologist and Operations Director (during nominal ops)
Schedule driven by instrument team requests first sixty days
SVT requests prioritized for L+60  1yr
Responsible for updating long term scene acquisition plan
Submits prioritized scene list to MOPSS, resolves with MOPSS schedule conflicts, revises Long Term Acquisition Plan

Note: 
	During EOC, mission planning office is chaired by mission manager and consists of mission director, mission technologist, instrument checkout team representatives and spacecraft checkout team representative

***Consists of *Mission Scientist, Mission Technologist and Operations Director (during nominal ops)***
***Schedule driven by instrument team requests first sixty days***
***SVT requests prioritized for L+60  1yr***
***Responsible for updating long term scene acquisition plan***
***Submits prioritized scene list to MOPSS, resolves with MOPSS schedule conflicts, revises Long Term Acquisition Plan***
***Note: ***
***	******During EOC, mission planning office is chaired by mission manager and consists of mission director, mission technologist, instrument checkout team representatives and spacecraft checkout team representative***

***System Description****Mission Planning**Office*

## System DescriptionMissionScienceOffice

***Receives scene and calibration requests from the MPO***
***Receives scheduling guidelines and priorities from the MPO***
***Submits prioritized scene list to MOPSS, resolves with MOPSS schedule conflicts, revises Long Term Acquisition Plan***
***Schedules ALI and AC performance assessments after Checkout phase***
***Provides assessments for the processed images for updating the LTAP***

***System Description****Mission**Science**Office*

## System DescriptionScience Validation Facility

***Provides Level 0 and/or Level 1 products to the SVT***
***Provides ALI MS/PAN Level 1 processing upon SVT request***
***Provides AC Level 1 processing upon SVT request after Checkout phase***
***Requests HSI Level 1 data from TRW for distribution to SVT***
***Receives calibration coefficient updates from MIT/LL***
***Provides the Level 0 data archive for the life of the mission***

***System Description****Science Validation Facility*

## Provides science validation for the EO-1 mission as per selected research topic from NRA
Provides requests for scenes to the MPO
Requests and receives AC, ALI, or Hyperion, Level 0 or Level 1 products from the SVF

***Provides science validation for the EO-1 mission as per selected research topic from NRA***
***Provides requests for scenes to the MPO***
***Requests and receives AC, ALI, or Hyperion, Level 0 or Level 1 products from the SVF***

***System Description****Science Validation Team (SVT)*

## Ingests Level 0 data provided by the MOC
Produces Hyperion Level 1 data for all data received
Provides Hyperion scene and calibration requests to the Mission Planning Office
Provides Level 1 data and associated metadata to the SVF upon request
Receives Level 1 AC or ALI products from the SVF upon request for comparisons 
Provides capability to access the following electronically from the MOC:
Recorded SOH data made available for early orbit and on contingency basis
Selected trending data made available electronically by the MOC 
Flight dynamics products
Small DCE data files (<125 MB) during initial instrument check-out

***Ingests Level 0 data provided by the MOC***
***Produces Hyperion Level 1 data for all data received***
***Provides Hyperion scene and calibration requests to the Mission Planning Office***
***Provides Level 1 data and associated metadata to the SVF upon request***
***Receives Level 1 AC or ALI products from the SVF upon request for comparisons ***
***Provides capability to access the following electronically from the MOC:***
***Recorded SOH data made available for early orbit and on contingency basis***
***Selected trending data made available electronically by the MOC ***
***Flight dynamics products***
***Small DCE data files (<125 MB) during initial instrument check-out***

***System Description****TRW*

## Functional Description:
Provides ALI validation and verification for the first 60 days
Provides backup storage capability for the MS/PAN Level 0 processed EO-1 data for mission life
Provides ALI scene and calibration requests to the Mission Planning Office during the check-out phase
Provides calibration coefficient updates to the SVF during the checkout phase only
Additional Support:
MIT/LL provides the ALI Level 1 processing software to the SVF who will operate the software throughout the mission
MIT/LL will provide the SVF with support during the check-out phase
Provides capability to access the following electronically from the MOC
S-band SOH made avail for early orbit and contingency basis
Selected trending data made avail by MOC
Flight Dynamics Products
Small DCE files (<125MB) during initial instrument check-out

***Functional Description:***
***Provides ALI validation and verification for the first 60 days***
***Provides backup storage capability for the MS/PAN Level 0 processed EO-1 data for mission life***
***Provides ALI scene and calibration requests to the Mission Planning Office during the check-out phase***
***Provides calibration coefficient updates to the SVF during the checkout phase only***
***Additional Support:***
***MIT/LL provides the ALI Level 1 processing software to the SVF who will operate the software throughout the mission***
***MIT/LL will provide the SVF with support during the check-out phase***
***Provides capability to access the following electronically from the MOC***
***S-band SOH made avail for early orbit and contingency basis***
***Selected trending data made avail by MOC***
***Flight Dynamics Products***
***Small DCE files (<125MB) during initial instrument check-out***

***System Description****MIT /**Lincoln Lab*

## Functional Description:
Ingests LZP data provided by the MOC on DLT during first 60 days.
Submits AC scene and calibration requests to the MPO, and provides image tracking database updates following processing of AC Level 0 data.
Receives Level 1 Hyperion or ALI products from the SVF for comparisons
Produces AC Level 1 data and associated metadata during EOC upon request of the SVF (the SVF will assume this functionality after EOC for the duration of the mission)
Additional Support:
The GSFC AC will provide the SVF with the Level 1 processing software after performance assessment of the ACCS
Provides capability to access the following electronically from the MOC:
S-band SOH made avail for early orbit and contingency basis
Selected trending data made avail by MOC
Flight Dynamics Products
Small DCE files (<125 MB) during initial instrument check-out

***Functional Description:***
***Ingests LZP data provided by the MOC on DLT during first 60 days.***
***Submits AC scene and calibration requests to the MPO, and provides image tracking database updates following processing of AC Level 0 data.***
***Receives Level 1 Hyperion or ALI products from the SVF for comparisons***
***Produces AC Level 1 data and associated metadata during EOC upon request of the SVF (the SVF will assume this functionality after EOC for the duration of the mission)***
***Additional Support:***
***The GSFC AC will provide the SVF with the Level 1 processing software after performance assessment of the ACCS***
***Provides capability to access the following electronically from the MOC:***
***S-band SOH made avail for early orbit and contingency basis***
***Selected trending data made avail by MOC***
***Flight Dynamics Products***
***Small DCE files (<125 MB) during initial instrument check-out***

***System Description****GSFC AC*

## Mission Planning and Processing Working Meetings - Late Feb 99’ and April 7-8 1999
Agreed to approaches for all major interfaces
Ironed out major requirements and data product interfaces
Agreed to operations concept and planning/processing timelines
Mission Planning and Processing Review (July 21-22 1999)
Finalized all data product formats and interfaces
Detailed agreement on operations timelines, data product delivery and mission planning interfaces
Began plans for tests (M4’s, Thermal vacuum) of operations
Mission Planning and Processing Status Briefing (Oct 7, 1999)
Refinement of data product interfaces
Readiness of elements to support tests (M4’s)
Since October 
Testing monthly (M4’s Science ETE tests)
Weekly telecons, adhoc meetings and discussions
Monthly face to face discussion scheduled

***Mission Planning and Processing Working Meetings - Late Feb 99’ and April 7-8 1999***
***Agreed to approaches for all major interfaces***
***Ironed out major requirements and data product interfaces***
***Agreed to operations concept and planning/processing timelines***
***Mission Planning and Processing Review (July 21-22 1999)***
***Finalized all data product formats and interfaces***
***Detailed agreement on operations timelines, data product delivery and mission planning interfaces***
***Began plans for tests (M4’s, Thermal vacuum) of operations***
***Mission Planning and Processing Status Briefing (Oct 7, 1999)***
***Refinement of data product interfaces***
***Readiness of elements to support tests (M4’s)***
***Since October ***
***Testing monthly (M4’s Science ETE tests)***
***Weekly telecons, adhoc meetings and discussions***
***Monthly face to face discussion scheduled***

***Mission Planning and Processing******Reviews******and ******Meetings***

## Problem Reporting System

***Problem Reporting System***

***Utilizing web-based Discrepancy Reporting System in MOC to prioritize and ensure corrective action***
***No critical Discrepancy Reports in system***
***Minor problem with ALI pixel reordering (1 pixel off)***

## Testing Summary

***Testing Summary***

***Mission Planning Sim for first 60 days conducted late January through early March***
***Valuable lessons learned, refining scene request information and operational procedures***
***Planning rerun of this simulation  from April 17- May 20 with more integrated SVT and Instrument scene list***
***Four 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 instrument team interfaces for real-time, trended, and playback data***
***M4 simulation planned monthly from now until launch***
***Monthly instrument/science team meetings scheduled***
***Weekly telecons to discuss processing and scheduling issues   ***

## Testing Summary

***Testing Summary***

***Instrument and WARP activation script finalized***
***Early version run in early November. Will once more before launch***
***Normal operations simulations run in TV in Oct. Will run with full ETE science planning and processing simulation before S/C shipment***
***Still need to send final data products for analysis to representative SVT team members***
***Will be ready to do so after test on 3/22***

## Special Topic:

***Accelerated Validation Timeline***

*** ******. . . Nick Speciale***
*EO-1 Mission Technologist*

## Considering Accelerated EO-1 Mission Success Timeline

***Considering Accelerated EO-1 Mission Success Timeline***

***Previous mission operations scenario had distinct phases with different scene collections from instrument teams and SVT.***
***These scene databases will be integrated and prioritized over next month. ***
***Propose to double number of scenes scheduled and downlinked each day (from 4 - 8 DCE’s with a surge capability of 10 per day)***
***A detailed mission planning simulation of the integrated plan will occur from April 17- May 21  to flush out constraints and ***
*Similar exercise has been run on original first 60 day schedule with valuable lessons learned*
***Goals is to achieve a well oiled planning and replanning team, capable of daily prioritization of scene collections to achieve both successful and minimal mission success within 120 days.***
***Achieve Successful Mission criteria within 120 days after launch vs previous 1 year timeframe***
***Be able to seamlessly retreat to minimal mission (ALI validation) success criteria (in 120 day timeframe) if problems occurs with other instruments.***
***Increases probability of success of mission, well within resources of S/C.***
***Other technology validations in parallel or on a non-interference basis (as they always have been).***
***Preserves original validation and technology infusion timeline.***

## Capabilities Already in Place SupportingAccelerated Mission Validation 

***Capabilities Already in Place Supporting******Accelerated Mission Validation ***

***Wallops Ground Station will support 24hr turnaround of data during first 60 days (will extend to 120days)***
***DQM’s in place to verify quality of scene data during and after pass data have will be in place at all G/S.***
***Higher rate L0 front end processing equipment already in place to support higher data processing demand.***
***All current (4 DCE’s per day) data formatting and processing requirements have been met by instrument, SVF and DPS teams.***
***ETE mission planning and data processing simulations held monthly from Nov - April have been very successful in uncovering performance bottlenecks***
***Demonstrated capability to plan and process 4DCE’s per day, should be extendable to 8DCE’s per day (see enhancement slides)***
***Lessons learned have been flowed back into operational procedures (especially DPS).***
***No Spacecraft resource or performance issues to preclude scheduling of additional DCE’s per day.***

## Proposed Enhancements to CurrentEO-1 Ground System

***Proposed Enhancements to Current******EO-1 Ground System***

***Double Level zero processing capability (from 4-8 scenes per day)***
***Minor hardware upgrades, additional staffing first 120days, 2shifts, 7days a week vs. baseline single shift seven days/week***
***Double SVF processing capability (from 4-8 scenes day)***
***Requires additional staffing, 2 shifts needed 7 days/week first 120 days.***
***Double TRW processing capability (from 4-8 scenes day)***
***Additional processing hardware, additional staffing first 120 days***
***Minor enhancement to MIT/LL systems (extend presence to 120 days vs 60) ***
***Plan nominally 8 scenes and 4 - 5 X-band downlinks per day, 10 scene surge capability.***
***Current EPGN ground stations loading supports this request already, need to expand Wallops from 60-120 days to support faster turnaround of high priority scenes.***
***On-orbit testing of additional backup stations (Australia, Mac Murdo) will enhance probability of getting data down.***
***S/C performance envelop supports this scenario well.***