New Millennium EO1 Advanced Land Imager 23 January 1998

1
Ground System
Dan Mandl January 22, 1999
2
(No Transcript)
3
Ground System
Dan Mandl January 22, 1999
4
(No Transcript)
5
(No Transcript)
6
Documents

• Data Policy March 1999
• Data Mangement Plan draft January 1999
• Detailed Mission Requirements - July 1998
• Mission Operations Support Plan (Design) - June
  1999
• Test Plan - 2nd draft January 15, 1999
• ICDs
• Space to Ground - baselined
• MOC to SVF - baseline 1/30/99
• Landsat MOU - draft 1/15/99
• Mission Procedures Document
• Vol 1 Ops Concepts - January 6, 1999 (baseline on
  1/30/99)
• Vol 2 Detailed Ops Plan - draft 1/30/99
• S/C Users Guide 6/99

7
Reviews

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

8
CGS Releases and Content

• Release 1 - December 15, 1997
• ASIST 5.0 - base capability
• Release 2 - June 15, 1998
• ASIST 6.1 - enhanced base capability
• Release 3 - Slipped from Dec 15, 1998 to February
  15, 1999
• ASIST 6.2 - Working CMS capability for EO-1
• Release 3.1 - March 1, 1999
• ASIST 6.2a - TCP/IP interface to ground station
  capability
• Release 4 - June 15, 1999
• ASIST TBD - SAMMI Samplets capbility for Web
  displays and cleanup

9
DPS Releases and Content

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

10
DPS Releases and Content

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

11
MOPSS Releases and Content

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

12
MOPSS Releases and Content

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

13
MOPSS Releases and Content

• Release 1.1 - October 26, 1998 (complete)
• Ingest FDF-generated maneuver plan and command
  sheet (reuse TRMM)
• Schedule orbit maneuver related sequences (slight
  mod TRMM)
• Ingest and display FDF orbital event predicts
  (mod)

14
MOPSS Releases and Content

• Release 2 - January 8, 1999 (to acceptance
  testing)
• Display, allow selection, and transmit GS
  schedule from WSG (reuse)
• Receive and display GS schedule from WSG (reuse)
• Ingest and display SVF-provided ground image
  scene request (through long-term plan file) (mod)
• Ingest and display cal scene requests (through
  FDF calibration slew products)
• Automatically select images and schedule image
  related commands (mod)
• Ingest command database from ASIST to create
  MOPSS event classes.

15
MOPSS Releases and Content

• Release 2 - continued
• Assign WARP file IDs for each data stream to be
  stored for each DCE (new)
• Perform resource utilization checks (WARP
  availability, instrument on time, etc.) (mod/new)
• Each WARP file should be assigned a file ID that
  correlates to DCE, DCE type, and data stream/type
  (ex MS/PAN dark cal, MS/PAN instrument
  calibration, MS/PAN image, etc) (new)
• Each WARP field ID should be assigned a unique
  number (new)

16
MOPSS Releases and Content

• Release 3 - March 31, 1999
• Calculate and display image times based on
  requested scene location and predicted EO-1 orbit
  position (includes ingest of necessary FDF
  products) (reuse Landsat)
• Interface with FDF algorithms to schedule
  activities/commands for momentum management and
  attitude maneuvers for nadir and cal images.
  Note - different interface for nadir and cal
  images (new)
• Provide momentum management/attitude maneuver
  related constraint checking (new)
• Generate enhanced reports image summary report
  and/or pass plan (new)

MOPSS
17
MOPSS Releases and Content

• Release 3 - March 31, 1999
• Ensure activity plan is not generated if new GS
  schedule from WSG has been received but not
  processed. (new)
• Provide scenario scheduling of realtime procs
  (reuse MAP)
• Support recent changes to long-term plan and
  calibration slew file formats.

MOPSS
18
FDSS Release Contents and Schedule

• Release 1 - May 15, 1998 complete
• STK (COTS) Generate baseline orbit product set
  for testing with MOPSS rel 1
• Autocon-G (COTS) Model profile for performing EFF
  maneuvers
• MatLab/ADS (COTS based) perform base attitude
  determination functions
• WRS Sun Angle Utility (C) Compute Sun Angles
  with Respect to Rows on the World Reference
• Release 2 - October 15, 1998 complete
• Autocon-G (COTS)
• Generate EO-1 Orbit Ephemerides containing EFF
  maneuvers
• Generate first group of Autocon-G orbit products
  for MOPSS

19
FDSS Release Contents and Schedule

• Release 2 - October 15, 1998 complete
• MatLab/ADS (COTS based) Capability to use a
  socket connection to ASIST
• MatLab/RTADS (COTS based) Perform base realtime
  attitude determination function
• Release 3 - January 2, 1999 complete
• FreeFlyer (COTS) Capability to plan EO-1 ascent
  maneuver
• Autocon-G (COTS) Capability to generate
  additional orbit products for MOPSS plus
  acquisition data products
• Release 4 - March 15, 1999
• STK (COTS) Capability to generate additional
  orbit products in EO-1 MOC version of STK

20
FDSS Release Contents and Schedule

• Release 4 - March 15, 1999 (cont)
• MatLab/ADS (COTS based) Refined attitude
  determination capabilities
• MatLab/RTADS (COTS based) Refined real time
  attitude determination capabilities
• MatLab/Momentum Management Utility (COTS based)
  Compute required wheel speed changes to reduce
  jitter during EO-1 imaging
• MatLab(CALMAN/Attifude Slew Utility) (COTS Based)
  Planning tool for EO-1 instrument calibration or
  computing any required S/C slews
• INTRACK Tool for performing S-band tracking data
  pre-processing

21
FDSS Release Contents and Schedule

• Release 4 - March 15, 1999 (cont)
• Precision Orbit Determination (PODS) (COTS) Tool
  to perform EO-1 Orbit Determination/Orbit
  Smoothing using either GPS data or ground based
  S-Bans tracking
• Fuel Remaining Utility (COTS based) Tool to
  estimate the amount of hydrazine remaining in the
  propellant tank
• Release 5 - May 15, 1999
• Science Planning Aids Algorithm (COTS based)
  Algorithm to enable MOPSS and Mission Science
  Office to schedule EO-1 imaging activities

22
Tests and Sims

• Acceptance testing for all subsystems internal to
  developer groups
• T1 S/C to MOC complete 12/22/98 telemetry ok,
  command testing deferred to T2
• T2 S/C-MOC-CMS-MOPSS-FDSS 2/99
• T3 S/C-MOC-MOPSS-DPS-SVF 4/99
• T4 RF Compatibility 6/99 and 8/99
• T5 MOC to Ground Stations 6/99
• T5.1 MOC to TDRSS 9/99
• T6 MOC to WTR 9/99
• T7 Fully integrated End to End 10/99

23
Tests and Sims (cont)

• Launch Sim 6/99 during Thermal Vac
• Normal Ops Sim 8/99 during 2nd Thermal Vac
• Contingency Ops Sim 9/99
• Dress Reheasal 11/99
• Note that these sims may be run on a few
  occasions as needed

24
Launch Planning

• Operations Working Group 2 12/4/98
• Launch timeline
• Draft 12/98
• Baseline 6/99
• Launch site preparations (SWALES)
• PRD

25
Normal Ops Planning

• Working on allocating procedures between TSMs
  and ground procedures
• Ground procedures
• 90 reuse
• Guess that less than 30 new ones need to be
  developed
• Displays
• No new displays identified
• Database - reused from IT

26
Normal Ops Planning (cont)

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

27
Contingency Ops

• Identify constraints and triggers
• Identify if response is via TSM, FDC or procedure
  activity
• Identify set of activities and procedures to
  develop
• Gather constraints and triggers
• Most contingency procedures derives from IT
• Guess that there will be less than 30 unique
  contingency procedures - identified 10 thus far

28
Training

• Senior experienced staff
• S/C and ASIST training mostly complete due to
  involvement of FOT in IY
• FDSS, CMS, MOPSS and DPS
• FOT conducting the testing and therefore will
  simultaneously be trained to operate these
  systems
• No plans to develop training plan for new people
  since staffing plan calls for reduction of
  present staff by 40 anyway
• Automation lessens need for highly trained staff