180 likes | 195 Views
University of California, Berkeley Space Sciences Laboratory. ICON End-To-End Operations Philosophy. Will Marchant, Manfred Bester, Carl Dobson, Scott England, Stewart Harris, Mark Lewis, Will Rachelson, Bryce Roberts, Irene Rosen, and Ellen Taylor Space Sciences Laboratory
E N D
University of California, Berkeley Space Sciences Laboratory ICON End-To-End Operations Philosophy Will Marchant, Manfred Bester, Carl Dobson, Scott England, Stewart Harris, Mark Lewis, Will Rachelson, Bryce Roberts, Irene Rosen, and Ellen Taylor Space Sciences Laboratory University of California, Berkeley
Operations History at UCB/SSL EUVE FAST RHESSI NuSTAR UCB/SSL operated 10 NASA Explorer spacecraft over a period of more than 20 years (7 are currently operational). CHIPS ICON ICON, the 11th spacecraft, is scheduled for launch in 2017. Mission Operations Center BGS 11-m THEMIS / ARTEMIS
Operations Facilities at UCB/SSL Multi-mission Operations Center Berkeley Ground Station 11-m S-band antenna and equipment racks
ICON Mission Implementation MIGHTI EUV IVM FUV S/C
Measure altitude profiles of airglow near the Earth limb at visible and UV wavelengths via remote sensing, and measure in-situ ion densities and flows near the local magnetic field line to determine the connection between terrestrial weather and space weather. ICON Mission Science Objectives 300 km 200 km 100 km
ICON Participating Institutions and Team Roles Project Management Systems Engineering S&MA UV Instruments Payload Electronics Mission/Science Ops MIGHTI Neutral Wind Interferometer (2) Naval Research Laboratory Ion Velocity Meter (2) UT-Dallas UC Berkeley Payload Structure LEOStar-2 Spacecraft Observatory I&T ATK-Magna FUV Calibration Orbital Sciences Corporation Centre Spatial de Liège • Instrument Support • Cameras/electronics • Payload I&T GSFC – Explorers Office KSC – LV Services Space Dynamics Lab NASA
Mission Operations System Architecture Overview • Most internal MOC systems and interfaces required for ICON are operational already within the multi-mission support environment. • All ICON network interfaces are already used with other missions. • New operational flight dynamics tools are added for ICON target processing, and for GPS based orbit determination and attitude maneuver QA. • Science operations planning and pipeline processing software tools are adapted from existing software. • IT Security Plan, physical and network controls are in place already and are regularly audited by the GSFC IONet Security Office.
Using Common Flight-like Interfaces Instrument Simulator Spacecraft Simulator Mission Development Phases TLM & CMD Network Routing ITOS Observatory CMD & CTRL Instrument Spacecraft Simulator TLM Source Packet Archive MySQL DB Instrument Spacecraft Disk Storage Orbiting Observatory Ground Station Standardized interfaces at theCCSDS transfer frame layer allow usage of operational software from the earliest stages.
Ground Systems & Operations Test-like-you-fly philosophy, follows NuSTAR model used at UCB Box level to integrated systems level for all operations functions Early interface and data format verification via simulators End-to-end network data flows and pass simulations Science data flows from instrument to bus to ground and SOC pipeline Strive for Realistic Testing • I&T Support • Portable MOC and BGS ground systems used as EGSE throughout I&T • UCB flight controllers participate as console operators in all I&T phases
Taking advantage of fully integrated ground system to support spacecraft bus and instrument development Participating in all phases from early flight software and hardware development to full-up observatory testing Applying lessons learned: get involved early Taking the MOC to the ICON Spacecraft MOC Supports Development, Integration & Testing
EM development feeds simulator delivery Software emulator: ICP-CE, software based emulator for IVM Payload emulator: also hosting FSW, with simulated instrument data Hardware simulators: EM1, EM2, EM3 (hosting FSW) Instrument Simulators and EM Development
Converting legacy databases, scripts and telemetry pages to ITOS ITOS supported NuSTAR & ICON flight software development at Orbital ITOS will also be used for instrument development and testing Key strategy is to use standard CCSDS frames early in the development phase with small simulators serving as temporary stand-ins for not yet existing flight systems and software ITOS Configuration and Testing • Configuration management via Git • Data flows between FlatSat and MOC operational
Results & Lessons Learned • Use integrated MOC software (ITOS, FrameRouter, BTAPS) during earliest stages of I&T • Provide simple instrument simulators and interface modules to allow CCSDS transfer frame level interfacing to ITOS very early on • Steep ramp-up to get close to flight-like environment • Don’t be afraid of developing software in-house, but know where the limitations are of what makes sense • Integrate configuration management for all hardware and software solutions • Try to have FlatSat available with interfaces to the MOC
Summary • Successfully applied lessons learned from previous missions • Naturally, project and spacecraft contractor were skeptical about UCB proposal to deliver turn-key command and control system with hardware and software for I&T, but concerns were dispersed relatively quickly • Operations team involvement beginning with ITOS configuration 2.5 years before launch provides excellent training in preparation for on-orbit operations • Sizeable effort early on for operations team, but transition to on-orbit operations are very easy and low risk
The U.C. Berkeley Space Sciences Laboratory (SSL) Multi-mission Operations Center (MOC) provides support for Caltech's NuSTAR mission and will operate the ICON mission (scheduled for launch in 2017.) The MOC uses the Integrated Test and Operations System (ITOS) developed by NASA's GSFC and commercialized by The Hammers Company. The MOC supplied ITOS workstations and support for the NuSTAR instrument and spacecraft development efforts. This led to very smooth observatory integration, launch operations, and on orbit operations. ICON is following in those footsteps with some enhancements from lessons learned on the NuSTAR program. This talk will provide a brief overview of the suite of operations tools and discuss the advantages, and disadvantages, of using them for early flight software development and for integration and test activities. Abstract