Operations MOC

1
Section 34 Operations / MOC
. . . Dan Mandl EO-1 Operations Manager
2
Contents

• Summary of Open Issues from Red Team Review
• Schedule of Things Left to Do
• Ground S/W Final Releases
• Testing and Verification Status
• Discrepancy Report Status
• S/C to MOC Test Time
• Simulation Time
• MOC HW Status
• MOC Procedure Status
• SCUG Training Status
• Contingency Procedure Status
• Mission Procedure Document Status
• RFA Status from Previous Reviews
• Special Topics
• Alerts/Constraints Status Paul Earle
• MOC Simulations Gus Gustafson
• Contingency Operations Dan Mandl
• Staffing/Accelerated Mission
  Joe Howard

3
Summary of Open Items fromMarch Red Team Review

• Update testing status (page 34-10)
• Update verification results (pages 34-11 to
  34-13)
• Update DR status (pages 34-14 to 43-18)
• Update S/C to MOC testing (pages 34-19 to 34-20)
• Update sims (pages 34-21)
• Update MOC HW status (page 34-22)
• Update MOC Proc status (page 34-23)
• Update document status (pages 34-28 to 34-29)
• S/C Users Guide
• Mission Procedure Document

4
Summary of Open Items fromMarch Red Team Review

• Results of Timing Correlation Problem (page 33-39
  of original presentation)
• Discovered that problem resided in PTP at Ground
  Stations
• Updating PTP drivers to version 1.49 which
  resolves problem
• Update subsystems exercised with contingencies
  (page 34-46)
• Update testing and development of contingency
  procedures (page 34-24 and page 34-48)
• Update STOL Contingency Procedures testing status
  (page 34-25 to 34-28)
• Update S/C training status (page 34-29)
• Update ground training status
• All training complete

5
Schedule of Things Left To Do
6
Schedule of Things Left To Do
7
Ground Software Final Releases

• Launch freeze August 31, 2000
• ASIST 8.0 operational
• ASIST 8.1e installed by 8/15/00, launch release
• Improved load, dump capability
• Improved playback capability
• Linux version of ASIST
• Fix for DR 230 Dual CMS Usage
• Testing
• Detailed regression tested by ASIST group
• Functional regression testing plus fixes tested
  by FOT
• Launch sims in Sept and Oct 2000 (116 hours with
  S/C)
• DB 2.0 Operational, tested in T/V II
• Upgrade to 2.1 by 8/11, launch data base
• Incorporate limit changes discovered during T/V
  II
• Incorporate A few polynomial coefficient changes
• Comment out a few hazardous commands
• Testing
• Test fixes with playback data and will trigger
  specific limits manually

Ops Overview
8
Ground Software Final Releases (continued)

• MOPSS 6.0 operational and launch capable
• MOPSS 6.1 to be delivered by 8/31/00
• Fix DR 210 - More efficient constraint checking
• Fix DR 211 Processing LTP update
• Fix DR 216 - Enhanced rescheduling capability
• Testing
• Benchmark input and output data used
• Will be used by three planners daily until
  .launch (360 hours of usage)
• Will be used for Launch Sims in September,
  October 2000
• FDSS
• STK 4.1.1 - operational, launch release, tested
  in planning sims
• PODS
• AutoCon-G 4.2- operational, is launch capable,
  tested with planning sims
• AutoCon 4.3 due 8/15/00
• Fix ingest of some Landsat parameters, will test
  with weekly planning sims

Ops Overview
9
Ground Software Final Releases (continued)

• FDSS (continued)
• MMAP 1.5 operations, is launch capable, tested
  with planning sims
• MMAP 1.6 is delivered
• Enhance auxiliary scene capability
• Tested benchmark product set
• Used in weekly planning sims (30 hours prior
  launch)
• ADS 1.4 operational, launch release, tested in
  M1 Launch Sims, used in T/V II
• ALI Alignment Util 1.2, operational, launch
  capable
• ALI Alignment Util 1.3 due 8/31/00, tested by SVF
• Enhances computation of misalignments for ALI
  detectors(add YAW), output is table load,
  interface already tested
• DPS 3.0 operational and is launch release
• Tested during T/V II in End-to-End Science data
  flow
• Benchmark data set available for future
  post-launch release regression testing if needed

Ops Overview
10
EO-1 Operations Testing Status
S Acceptance Testing T Mission Readiness
Test M Simulation
Testing Verification
11
EO-1 Ground Data System Requirements Verification
Results
WOTIS Event Schedules
N I S N
Long Term Plan from SVF
M O C
T 29 V 26 N 0 D 3 100
SN
FD Products and Plan Aids
S-band Data
T 12 V 10 N 1 D 1
90
Daily Activity Plan
Commands
Data Collect Event Schd
Calibration Science Request
Tracking Data
Calibration Parameter File
W/B Data Quality info
Products to PIs
R/T Electronic TLM (VC0 VC02) SAFS data
retrieval (Post Pass)
X-band Data
2
GN
Commands
X-band Data tape
1
AGS SGS WOTS MGS
R/T Commands
T 31 31 31 21 V
30 30 30 20 N
1 1 1 1 D
0 0 0 0
97 97 97 95
S-band Data
Command Loads
Tracking Data
EBNET
R/T Telemetry
Data Quality Statistics
P/B Telemetry
AGS, SGS, WOTS, MGS Schedules
FDSS
Maneuver Planning
T 46 V 46 N 0 D 0
100
Orbital Prediction
Schedules
Orbital Determination
R/T Attitude Determination
INST
T 21 V 13 N 7 D 1 62
Products for Instrument's
Products for SVF
2
Testing Verification
12
Requirements Verification

• 96 of the requirements verified
• Unverified requirements
• 7 Instrumenter requirements not verifiable before
  launch because involve providing LEO support
• Requirement for SVF to perform Level 1 processing
  of AC data after receipt of code from AC
  Instrumenters closed post launch
• 2 CGS requirements to beep FOT and send data via
  beeper not launch critical, complete testing by
  launch
• 24 hour coverage for first 120 days
• SN requirement for SSA service for 2 kbps
  opened since transponder had problems
• 4 GN requirements only testable post launch,
  involves performance of personnel at ground
  stations

Testing Verification
13
Ground Discrepancy Reports (DR) Status
Testing Verification
14
Ground Discrepancy Reports (DR) Status Critical
DRs

• DR 204-Networks PTP desktop file size
  limitation
• Fixed, Wallops, Svalbard ok, retest Alaska by
  8/15/00
• DR 251-Spacecraft Unstable command link
• Transponder problem

Testing Verification
15
Ground DR Status Urgent DRs

• DR 10-DHDS Playback cant be automated
• ASIST 8.1 to be installed 8/15/00
• DR 18 67-ASIST Slow playback
• ASIST 8.1 to be installed 8/15/00
• DR 150-FEDS Commands not getting to STGT
• New equipment installed at White Sands, retest by
  8/31/00
• DR 255-FEDS Command problem
• Related to Transponder problem, retest when
  S-Band retested
• DR 210-MOPSS Constraint checker problem
• Fix due in MOPSS 6.1 by 8/31/00
• DR 211-MOPSS Processing LTP updates
• Fix due in MOPSS 6.1 by 8/31/00
• DR 216-MOPSS Rescheduling problem
• Fix due in MOPSS 6.1 by 8/31/00

Testing Verification
16
Ground DR Status Urgent DRs (continued)

• DR 209 CMS Activity dictionary problem
• Fix to be deliver post launch
• DR 230-CMS Dual CMS problem
• ASIST 8.1 8/15/00
• DR 84-Ops WARP directory needs to be a flat
  file
• Partially fixed, needs database change (DBCR), by
  8/11/00
• DR 107-Ops Monitor was unreadable
• Action assigned to Jim Weidman, system admin.
• DR 273 Ground Proc in IT set different than
  MOC
• DR 271 closed after statistics taken
• DR 166-S/C Limits need to be changed for new
  command DB for MOPSS
• MOPSS 6.2 and DBCR post launch delivery
• DR 195 S/C ACS FDC 83 tripped during sim
• Assigned to K. Blackman, pending closure

Testing Verification
17
S/C to MOC Testingas of 8/1/00(1 of 2)
Testing Verification
18
S/C to MOC Testing(2 of 2)
P - Planned
Testing Verification
19
Simulations
Testing Verification
20
MOC Hardware Status

• Trending system
• In process of configuring new PC with DTAS
• Fixed DR which didnt allow ingest of EO-1
  database
• Expect to have in MOC for testing by 8/18/00
• Firewall was installed
• De-installed during simulation when firewall went
  down
• Purchased PC for quick workaround
• In process of reinstalling firewall, to be
  complete before end of August

RFA Status
21
MOC Procedure Statusas of7-27-00
MOC Procedure Status
22
Contingency Procedure Status as of 8-1-00
23
Contingency Procedure Status as of 8-1-00
24
Contingency Procedure Status as of 8-1-00
25
Contingency Procedure Status as of 8-1-00
26
Contingency Procedure Status as of 8-1-00
27
SCUG Training Status as of 7-26-00
28
Mission Procedure Doc Statusas of 7-26-00
29
Top Level Esculation Procedure

• Limit violation detected by operator
• Operator contacts Ops Director or Mission
  Director or calls if it is night shift
• Operator calls salient subsystem engineer with
  concurrence of Ops Director or Mission Director
• Operator and/or Ops Director consult contingency
  flow chart to see if there is any direction
  (usually, direction is to call subsystem
  engineer)
• Operator and/or Ops Director consult constraints
  database to see if any constraints violated
• No action taken by operator without phone call
• Action taken after consultation with subsystem
  engineer or Mission Director/Ops Director

30
RFA Status

• 23 RFAs were assigned from the original MOR and
  are closed
• 20 RFAs were assigned from the Delta MOR and are
  closed
• 15 RFAs were assigned from the FOR
• 11 closed
• 4 responses resubmitted and still under review

RFA Status
31
Special Topic Alerts / Constraints Status
. . . C. Paul Earle Systems Engineer
32
Operations Philosophy

• Daily Scheduled Activities (MOPSS)
• Planning is Semi-Automated by MOPSS
• Activities Performed via Fully Tested Verified
  STOL Procedures
• SOP Document for Event Messages Limit
  Violations
• Ops Alerts/Constraints Verified and Documented
• Constraints Cross-Reference to Contingency
  Procedures

33
Plan / Schedule / Status

• Initial Audit of Constraints Database - complete
• Initial Review by Subsystem Leads - complete
• Safeguards against violation where feasible -
  complete
• Individual Constraints initialed by cognizant
  engineers - in process
• Update status in database from Review to Approved
  - after initialed
• Deliver Document by 7/31/00 (ACS due 8/16/00) -
  in signoff (90 complete)

34
Alerts / Constraints Status
35
Alerts / Constraints Status
36
Alerts / Constraints Status
37
Alerts / Constraints Status
38
Special Topic Follow-Up MOC Simulations
. . . Gus Gustafson EO-1 Simulation Manager
39
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

40
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

41
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

42
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/2428/00
• 13 planned contingencies and 2 unplanned

43
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/1718/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, day 2
  only 3/16/00
• 4 planned and 1 green card
• Sim 15 Pre-Launch and Day 12 simulation with
  contingencies
• First testing of prelaunch activities beginning L
  15 hrs 6/4-6/00
• Sim 16 Day 1 only Launch sim and Pre-Launch
  Aliveness test
• 6 planned and unplanned contingencies

44
Subsystems Exercised with Contingencies
Planned 59 Unplanned 11 Total 70 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.
45
Special Topic Follow-Up Contingency Operations
. . . Dan Mandl EO-1 Operations Manager
46
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.
• 95 of the analysis of flow charts and 100 of
  testing of STOL procedures has occurred
• All simulations, except the first, have contained
  anomalies. This allows for training the team on
  how to use the procedures.

47
Contingency Procedures

• Procedures exist in the form of STOL Procs and
  Decision Trees
• All STOL Procs will be tested before use
• Decision Trees tested by review although some
  exercised in simulations for training purposes

48
Special Topic Staffing / Accelerated Mission
. . . Joe Howard EO-1 FOT Lead
49
Additional Staffing Needed Due to Accelerated
Mission

• Requirements increase DCEs per day from 4 to 6-8
  for first 120 days
• Implies 3-5 downlinks per day
• Staffed around the clock so that there is no
  impact on original staffing plan for getting
  extra passes
• Requires more data processing therefore adding 1
  DPS operator to handle extra load
• Purchasing additional hard disks to handle more
  data

50
Functional FOT Organization

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

51
FOT Experience (Core)
52
FOT Experience (Supplementing LEO)
53
FOT Experience (Supplementing LEO)
54
Additional StaffingNot Mentioned on Previous
Slides

• TBD DPS operator
• Joe Szwackowski, Mission Planner
• Jennifer Sager, Flight Dynamics, FOT

55
FOT Shift Profile

• Power up shift Before launch to L3 days
• 2 x 12 hour shifts for first 7 days and then
  transitioning to 3 shift operations
• L3 to L60 3 shifts supplemented with returning
  TCs from west coast
• At L30 L120 will have review to decide if we
  will extend 24 hour operations
• If Ops nominal then after 120 days, 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

56
FOT Shift Support Week 1
(12 hours)
Prime shift
Back shift
57
FOT Shift Support Week 2 to L120
(8 hours)
Prime shift
Swing shift
Night shift
58
FOT Shift Support Normal Ops (w/ Automation)
(8 hours)
Prime shift
Swing shift
Night shift
Note that shifts for selected FOT will be offset
by 4 hours to provide 12 hours coverage M-F
59
FOT Staffing Conclusion

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