Operations Manfred Bester Operations & Ground Systems Space Sciences Laboratory

1. Operations • Manfred Bester • Operations & Ground Systems • Space Sciences Laboratory • University of California, Berkeley

2. Operations Agenda • Agenda Concept of Operations Ground System Design Software Tools Verification & Validation Pre-launch Testing Normal Science Operations Issues

3. Concept of Operations • Concept of Operations • Mission orbit • Spin stabilized spacecraft • Baseline orbit 650 km circular at 72° inclination • Communications and pass coverage • Communications via S-band (TLM) and UHF (CMD) • Typically 4 passes/day with 30 min access time • Tracking via TLEs downloaded from USSTRATCOM • Data recovery • Store-and-forward scheme, downlink at 1 Mbps • Recoverable science data volume 760 Mbits/day • Ground segment • MOC and ground station located at UCB/SSL • Use heritage command & control system (ITOS)

4. CINEMA Ground Track

5. MOC Systems & Interfaces • CINEMA ground system is modeled after the NuSTAR ground system • Berkeley Ground Station is primary for CINEMA • CINEMA may also use the Integrated Test and Operations System (ITOS) for spacecraft command and control • Most internal MOC systems and interfaces required for CINEMA are functional already • Flight dynamics product generation and pass scheduling are part of multi-mission operations system

6. MOC Major Software Tools

7. ITOS Configuration & Testing • ITOS Configuration • Configure “databases” for telemetry and command • Key strategy is to use standard CCSDS frames early in the development phase to get as close to the flight configuration as early as possible in the program • ITOS Data Flows and Interface Testing • Exchange of telemetry and command data tested during CubeSat integration • Setup also allows mission simulations where flight controllers talk to the spacecraft during CubeSat integration as if it was on orbit already

8. Verification & Validation • Verification & Validation Approach • Purpose is to verify and validate all requirements • Follow test-like-you-fly philosophy • Exercise all ground systems functions and interfaces • Train and certify operations team members • Mission Readiness Testing • Organized similar to flight hardware development and testing • Component level • Box level • Subsystem level • System level • Full CubeSat level • Clearly defined pass/fail criteria • Used to track progress and document discrepancies • Retest all cases where discrepancies are observed

9. Pre-launch Operations • Pre-launch Operations • End-to-end tests with all network elements • Data flows with Berkeley Ground Station • Flight dynamics with download of TLEs (USSTRATCOM) • Voice loop checkout • Procedure testing and validation • Launch & early orbit operations • Normal operations • Contingency operations • Launch and mission simulations with green card exercises • Practice of anomaly detection and recovery • Dress rehearsals • Multiple cycles of launch readiness test runs

10. Normal Science Operations • Mission Planning • Pass schedule planning • ACS versus science operations timeline • Command sequence load generation • Spacecraft Command and Control • Spacecraft health and safety monitoring and trending • Recovery of science and engineering data • Command sequence load uplink twice per week • Ephemeris uploads • Clock correlation • Instrument configuration and calibration • Response to anomalies

11. Issues • Ground Data System • Try to use as much heritage as possible, but not much progress made • Flight Ground Interface Control Document • Need to define frame formats and communications protocols • RF Spectrum Licensing • Frequency bands selected, but NTIA paperwork not yet submitted