The Psyche Project is a mission to the asteroid (16) Psyche, featuring three science instruments and a gravity science investigation. (16) Psyche, located in the asteroid belt between Mars and Jupiter, will be the first potential metal world-instead of rock or ice-visited by the National Aeronautics and Space Administration (NASA). This Jet Propulsion Laboratory (JPL) managed mission will explore Psyche for 21 months after an August 2022 launch and a 3.5-year cruise. The Psyche End-to-End Information System (EEIS) is a virtual system comprised of distributed functions through the subsystems. The system is defined by how the flight, mission, and launch systems work together to enable Psyche's data flows (uplink, downlink, intra-flight system, ground processing, and timekeeping). This data passing through the EEIS includes spacecraft commands, spacecraft health telemetry, instrument science data, instrument engineering data, and timekeeping information. This paper focuses on the challenges of maintaining the integrity of the EEIS architecture throughout development of the Psyche Flight System and Mission System. It will cover how aspects of the initial architecture were eroded over the development lifecycle of the mission and how the unintended consequences of the chosen initial architecture forced late-phase design decisions to recover the intent and/or performance of the starting design. Readers will be introduced to the initial architecture of the Psyche EEIS at the end of early development (Phase B), as well as the matured architecture after a series of impacting decisions. This paper will analyze the subset of implementation decisions that resulted in deviations from the original architecture and how these deviations impact science and operations. Through decision tree examples of alternative, unchosen design choices and theoretical architectures of the Psyche EEIS, readers will be exposed to the cascading implications of early architecture decisions in the Psyche EEIS. The resulting design of the EEIS architecture will be evaluated against a set of performance criteria: aspects of operability; the quantity, quality, latency, and continuity (QQCL) of data flowing through the EEIS; and accountability of data transmitted thorough the EEIS. Readers will walk away with a good understanding of the quirks, features, weaknesses, and lessons learned of the Psyche EEIS.
Evolution and Analysis of Psyche's End-to-End Information System Architecture
2022-03-05
3907221 byte
Conference paper
Electronic Resource
English
Evolution of the Phoenix EDL System Architecture
NTIS | 2007
|Evolution of the Phoenix EDL System Architecture
NTRS | 2007
|