mops

Southwest Research Institute: 

Southwest Research Institute IBEX SWT Mission Ops Update Chelle Reno

Top-Level MOPS Requirement: 

Top-Level MOPS Requirement Responsible for implementing the functions, systems, personnel, and procedures to accomplish the operational objectives of the IBEX Mission Responsible for the collection of spacecraft data and the dissemination of that data to the ISOC for processing and evaluation of the science objectives of the mission

Ground Segment Architecture: 

Ground Segment Architecture

Organization Changes: 

Organization Changes Mission Ops Manager - Chelle Reno Science Ops Lead - Schwadron Science Software Lead - Geoff Crew

LEOps Organization: 

LEOps Organization

Nominal Ops Organization: 

Nominal Ops Organization

Institutional Responsibilities (1 of 2): 

Institutional Responsibilities (1 of 2) Orbital’s Mission Operations Center (MOC) Pre-launch operations planning (3-MOC Overview, 5-Orbit in the Life) Prepare team to ‘fly the spacecraft’ (4-Flight Operations Team & Training, 13-Testing) Create and validate command loads (7-Offline ops) Schedule contacts (7-Offline ops) Monitor spacecraft SOH (8-Real-time Ops) Trend & archive data (8-Real-time Ops) Track the spacecraft (6-Flight Dynamics) Plan orbit maintenance (6-Flight Dynamics) Detect and correct anomalies (14-Anomaly Response)

Institutional Responsibilities (2/2): 

Institutional Responsibilities (2/2) SwRI’s IBEX Science Operations Center (11-ISOC, 12-ISOC Software) Plan science operations Process data Archive data Distribute data to science team, NASA & public Monitor payload SOH SwRI’s Operations Lead Ensure mission objectives are being met Ensure operations has resources needed to complete these objectives Provide link between science and mission operations

IBEX Ground Segment Tools: 

IBEX Ground Segment Tools Orbital Mission Control Center (MCC) MAESTRO - Command and Control tool GSEOS - Science Data Viewing tool ODTK - Orbit Determination tool STK – Mission Design tool MPS - Mission Planning System Back-up MOC on Sparkle laptop IBEX Science Operations Center (ISOC) MAESTRO - Command and Control System GSEOS - Science Data Viewing System STK – Science planning tool Science Analysis Sosftware

Command & Data Flow: 

Command & Data Flow

IBEX Interfaces: 

IBEX Interfaces Change: No real-time streaming at ISOC during TDRSS contact

USN – MOC Interface: 

USN – MOC Interface

MOC – ISOC Interface: 

MOC – ISOC Interface

Mission Phases: 

Mission Phases Launch & SRM burn phase Launch on Pegasus, SRM boost to high-apogee parking orbit Orbit raising phase Ground stations acquire spacecraft and develop orbit ephemeris Spacecraft uses a series of hydrazine burns to boost up to mission orbit Commissioning phase Spacecraft bus and payload subsystems checked out Nominal operations phase Spacecraft performs nominal mission, collecting & downlinking science data Special operations Spacecraft operates through off-nominal conditions Special operations interspersed throughout Nominal Operations Phase, as needed

Phasing Diagram: 

Phasing Diagram SRM Burn Apogee Burn 1 Perigee Burn 2 Perigee Burn 1 Perigee Burn 3 Apogee Burn 2 Spacecraft Commissioning

Launch & SRM Burn Ground Operations: 

Launch & SRM Burn Ground Operations Launch & SRM Burn Phase run out of the MOC Monitor flight system telemetry from Pegasus Go/no-go for launch decision Monitor TDRS contact once it starts Gather telemetry from flight system, including SRM burn dynamics Verify system performance using received telemetry from Pegasus and TDRS Launch & SRM Burn Phase is fully automated Go/no-go is the only real-time decision Ground only observes Launch & SRM Burn Phase

Commissioning Phase Timeline: 

Commissioning Phase Timeline Near-continuous ground coverage available for all checkout activities Single ground stations line-of-sight available for ~11 hours at a time ~18 hours total ground station line-of-sight availability per day Transmitter can be on continuously for 75 minutes, then needs to cool down for ~3 hours before next contact Expected 12 passes per day with a maximum of 18 passes, for 2 weeks Commissioning Phase includes 3 activities:

Commissioning PhaseGround Operations: 

Commissioning Phase Ground Operations Schedule and perform all ground passes Run checkout procedures real-time and verify performance Analyze spacecraft data from checkout activities Troubleshoot any problems detected during checkout Perform continued orbit determination using doppler data from ground contacts Proclaim the spacecraft ready to begin Nominal Operations Phase

Commissioning PhaseSpacecraft Checkout Plan: 

Commissioning Phase Spacecraft Checkout Plan

Commissioning PhasePayload Checkout: 

Commissioning Phase Payload Checkout

Nominal Operations Phase Ground Operations: 

Nominal Operations Phase Ground Operations Ground system responsibilities during LAHO Perform high-rate data dump pass, Receive science data download and state of health telemetry Update spacecraft clock to UTC Reset 18-day master timer Upload commands for following 2 orbits (deleting previously stored commands for those orbits) Troubleshoot problems detected in real-time telemetry Use downloaded data to assess performance of re-pointing maneuver Perform low-rate tracking pass Ground responsibilities during HASO Analyze science and housekeeping telemetry Troubleshoot any problems discovered in back-orbit telemetry Perform continued orbit determination using doppler data from ground contacts Plan command load for upcoming orbits Schedule ground station passes for upcoming orbits Schedule any special operations required Perform low-rate tracking pass

Special Operations Summary: 

Special Operations Summary Special Operations are interspersed throughout the Nominal Operations Phase as needed Time and duration of Special Operations varies There are two types of Special Operations Maintenance – proactive to avoid future danger to the spacecraft or determine additional parameters for science data analysis Performing delta-V maneuvers to maintain favorable orbit by avoiding: Long eclipses (>4 hours) Strong lunar effects on orbit (perigee <3000 km or apogee >350,000 km) Suspending science operations to operate through a long eclipse Sensor gain testing and pressure measurements Contingency – reactive to an event encountered that endangers spacecraft Recovery from Contingency State or other anomalies

Special OperationsLong Eclipse Power-Down: 

Special Operations Long Eclipse Power-Down Done with special long eclipse command load and ground-commanded scripts Three ground contacts scheduled for verification that all is proceeding properly Contact 1, 12 hours prior to start of long eclipse Run script for pre-warming of spacecraft components and verify Contact 2, 30-60 minutes prior to start of long eclipse Verify that stored commands to power down the payload high voltages, shed SCB loads, enter Housekeeping State, and use long eclipse load shed algorithm were successfully performed Command these manually if they were not successfully performed Contact 3, >2.5 hours after end of long eclipse Check spacecraft state of health following long eclipse Run script to turn loads back on and return to Science State, resuming science data collection

Data from MOC to ISOC: 

Data from MOC to ISOC Real-time SOH (through VNC) Science data Housekeeping Quaternions Ephermeris Pass Logs Fill Data (not sure we can get this)