# Presentation: 738104

- Mission Operations Center ______________Randal Davis, LASP

- Facilities and Computer Hardware
- Communications
- Software
- Procedures
- Open Items Discussion

## Mission Operations CenterFacilities and Computer Hardware

** ** CCR

- MOR-1

** ** MOR-2

** ** EOR

- Data Processing

- Servers

- Mission Operations CenterFacilities and Computer Hardware

***Facilities***
**• ****MOR-1 — Mission Operations Room 1**
**• ****MOR-2 — Mission Operations Room 2**
**• ****EOR — Engineering Operations Room**
**• ****CCR — Computer and Communications Room**

## Main mission operations room (MOR-1) ready to support ICESat
Power and cooling upgrades planned for May will not affect availability
Backup operations room (MOR-2) will be operational in March
Used to support ongoing missions (QuikSCAT and SNOE) during ICESat launch
Engineering Operations Room (EOR) operational in March
Used by Ball/GLAS personnel to support real-time activities during L&EO
Engineering Office (EO) for use by Ball & GLAS during L&EO identified and will be available for first rehearsal 
Open Item:  If ICESat and SORCE launches are closer than four months, there will be contention for EOR/EO space

- Power and cooling upgrades planned for May will not affect availability
**Backup operations room (MOR-2) will be operational in March**
- Used to support ongoing missions (QuikSCAT and SNOE) during ICESat launch
**Engineering Operations Room (EOR) operational in March**
- Used by Ball/GLAS personnel to support real-time activities during L&EO
**Engineering Office (EO) for use by Ball & GLAS during L&EO identified and will be available for first rehearsal**** **
**Open Item:  If ICESat and SORCE launches are closer than four months, there will be contention for EOR/EO space**

- Mission Operations CenterFacilities  Status

## Mission Operations CenterComputer Hardware Status 

**Workstations and servers for real-time and non-real time activities are installed and operational**
- All workstations in MOR-1, MOR-2, and EOR have been upgraded to Sun Blade 100s with LCD display screens
**Database server for housekeeping data processing is operational**
- Sun 450 with 4 CPUs and 2 GB memory
- Additional disk space will be added at time of GLAS delivery
**Instrument Support Terminal (IST) is operational at GSFC**
- Sun 250 with 2 CPUs and 1 GB memory

## Mission Operations CenterCommunications

*Data paths are*
*bi-directional,*
*unless shown*
*otherwise*

- EMSn

- Closed  IONet

- Other

- RT    = Real-Time
- NRT = Non-Real Time

- AGS

- SGS

- WGS

**Mission Ops Center**
**LASP**

**WOTIS**
**WSC**

**Firewall/Gateway**
**GSFC**

**Central SAFS**
**GSFC**

**EDOS**
**GSFC**

- RT Cmd,
- HK,Status

- RT HK

- RT Status
- NRT GP, SCI

- NRT Sched,
- Status

- NRT GP, Sched, Status

- NRT HK

**ISF**
**GSFC**

- NRT Sched

- NRT HK

**FDF**
**GSFC**

- NRT
- Ephem

- GP   = GPS+PRAP Telemetry
- HK    = Housekeeping Telemetry
- SCI   = Science Telemetry

- Open  IONet

- SKS

- PF1

- RT Trk,
- NRT Trk,
- Ephem

- MGS

## Mission Operations CenterCommunications Status

**Dual Closed IONet data lines for real-time activities are operational**
- Connections to WGS and IST tested during IGSTs
**EMSn connection for non-real time data transfers in place**
- Tested with SAFS, IST and WOTIS
**IT security up to date**
- Last security scan performed on 11/2001
- One high level and two significant medium level vulnerabilities found and resolved
- Security documentation in place
- LASP flight team and system administrators have been IT certified
**Additional three NASCOM voice lines to be installed shortly**
**New:  An 802.11b wireless Ethernet connection to our open LAN is to be available by May**
- Will provide Internet access for flight team members and engineers who have computers with wireless cards

## Mission Operations CenterKey Software Functions

**Flight Operations**

- • Receive, monitor and display real-time data
- • Send commands and uploads

**Planning and Scheduling**

**Engineering Analysis**

- • Generate orbit predicts
- • Perform GPS orbit determination
- • Prepare orbit and attitude manuevers
- • Analyze and display orbit and attitude

- • Schedule ground station contacts
- • Produce observatory operations schedules
- • Process command and table load requests
- • Generate operations procedures

- • Check health and safety
- • Analyze performance and predict trends** **

- • Collect and process housekeeping data
- • Maintain engineering database
- • Maintain project web site
- • Archive data products

**Flight Dynamics**

**Data Management**

**Quality and Status Monitoring**

- • Monitor data quality and observatory status
- • Perform data and system reliability accounting
- • Track alarms and alarm responses

- Much of the software for ICESat
- has been adapted from
- QuikSCAT operations

## Mission Operations CenterSoftware Status — 1

**Flight Operations**
- OASIS-CC software is operational
- Checked out during long duration bus test and CTV end-to-end test
- Updated databases to be provided by Ball at GLAS delivery and prior to ship to launch site
**Planning and Scheduling**
- WOTIS GN scheduling connectivity verified
- 11-m scheduling through WSC slated to begin in June
- LASP is already using WSC for SNOE scheduling
- EDOS scheduling software in place and awaiting test
- Initial version of OASIS-PS software for planning and scheduling and Tablemaster software for table load generation is operational
- Ability to generate CSM loads and pointing quaternions demonstrated during long duration bus test
- New:  OASIS-PS software has been converted to Java, and ICESat will migrate to the new version
- Open Item: Scheduling interfaces with IST need to get into MEICD

## Mission Operations CenterSoftware Status — 2

**Data Management**
- FASTCopy software for data transfers from SAFS in place
- TDP software for housekeeping data processing and Sybase database for storing engineering data are operational
- Exercised during long duration bus test
- Upcoming releases at GLAS delivery and pre-ship
- New: Sybase database being upgraded to Version 12.5
- Same capabilities to be operational on the IST in April
**Engineering Analysis**
- Initial version of TCAD software for data display is operational
- Excerised during long duration bus test and CTV test
- Upgrades will be made at GLAS delivery and pre-ship
- To be operational on the IST in April
**Status and Quality Monitoring**
- TQSM software for automated operations is being upgraded for multi-mission support
- ICESat support will be available by first rehearsal

## Mission Operations CenterSoftware Status — 3

**Flight Dynamics System**
- All components (STK, MicroCosm, IDL, Matlab, CCAR code, Raytheon code) are in place and have been tested at the unit level
- Preliminary interface testing is complete
- FDS used to generate quaternions for the long duration bus test
- Currently ingesting GPS data from bus test into FDS for analysis
- Initial training complete
- Preliminary internal ICD is complete
- User’s guide to be complete by first rehearsal
- Lots of additional spacecraft testing planned

## Mission Operations CenterProcedures

**~350 automated (CSTOL) procedures needed for ICESat**
- 74 bus procedures have been signed and released
- 94 bus procedures written and under configuration control but not yet signed and released
- 104 GLAS instrument procedures needed for I&T are under development by GLAS team
- 48 have already been converted to CSTOL
- Open Item: Need to determine what I&T procedures to adapt for flight operations and how best to do it
- ~80 procedures yet to be defined
- Based upon a comparison of the number of flight procedures created for each QuikSCAT subsystem to the number defined for corresponding ICESat subsystems

## Open Item DiscussionICESat / SORCE Launch Contention

**SORCE and ICESat launches currently within 1-3 months of each other**
- Original plan was to have ICESat fully commissioned and in routine operation before SORCE pre-launch activities began in earnest
- Now SORCE is slightly ahead of ICESat, with launch slated for 10/31/2002
- Having both launches within four months of each other places some stresses on facilities and personnel as discussed below
**A separate EOR and EO may be required for each project**
- Two extra rooms have been identified to become a second EOR and EO
- But no modifications will be made until the situation is better understood
**LASP personnel may be stretched thin**
- Rehearsals and other intensive pre-launch activities may need to be coordinated to avoid conflicts
**No problems seen with hardware, software or communications**

## Open Item DiscussionNumber of Ground Station Contacts — 1

**1200z**

**1800z**

**0000z**

**0600z**

**1200z**

**AOS**

**LOS**

**R/T HK**

**PBK HK**

**COMMAND**

- PBK HK Transferred to MOC
- From C-SAFS

- GPS/PRAP Rate Buffered Data and
- SCS Summary Report
- Transferred to MOC from EDOS

**PBK SCI**

**3 hours**

- Expedited Data Set
- Transferred to ISIPS
- from EDOS

- Scenario with Four Contacts Per Day

*****

- 

- 

- 

- 

**ƒ**

**ƒ**

**ƒ**

*****

- 

**ƒ**

- {

- •  SCI data generated at 563 - 583 kbps
-     — Requires 20 minutes/day to downlink
- • SCI data downlinked on
-   three of four passes
- • Missed SCI data from  a 1200Z or 1900Z pass
-   can be recovered on  staffed pass at 0000Z
- • Missed SCI data from
-   0400Z requires an additional
-   contact between 1200Z -1800Z

## Open Item DiscussionNumber of Ground Station Contacts — 2

**1200z**

**1800z**

**0000z**

**0600z**

**1200z**

- Scenario with Five Contacts Per Day

- 

**ƒ**

- 

**ƒ**

- 

**ƒ**

- 

**ƒ**

- 

**ƒ**

*****

**R/T HK**

**PBK HK**

**COMMAND**

**PBK SCI**

*****

- 

**ƒ**

- {

- • SCI data downlinked on every pass
-     — ~ 4 minutes / pass• Missed SCI data from any pass can be  recovered on the staffed pass at 0000Z
- • Advantages:
-   — Easier for MOC and GN to recover lost SCI data
-   — 40% less SCI data/pass transmitted from a station to       EDOS and 40% less data/pass for EDOS to process
-   — Potentially quicker receipt of expedited data sets