Flying new technology on a faster, better, cheaper deep space mission
Explore the source record for details and available documents.
SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Explore the source record for details and available documents.
The expression faster, better, cheaper or FBC is becoming the mantra for many new projects.
NASA designs and builds systems that achieve incredibly ambitious goals, as evidenced by the Curiosity rover traversing on Mars, the highly complex International Space Station orbiting our Earth, and the compelling plans for capturing, retrieving and redirecting an asteroid into a lunar orbit to create a nearby a target to be investigated by astronauts. In order to accomplish these feats, the missions must be imbued with sufficient knowledge and capability not only to realize the goals, but also to identify and respond to off-nominal conditions. Fault Management (FM) is the discipline of establishing how a system will respond to preserve its ability to function even in the presence of faults. In 2012, NASA released a draft FM Handbook in an attempt to coalesce the field by establishing a unified terminology and a common process for designing FM mechanisms. However, FM approaches are very diverse across NASA, especially between the different mission types such as Earth orbiters, launch vehicles, deep space robotic vehicles and human spaceflight missions, and the authors were challenged to capture and represent all of these views. The authors recognized that a necessary precursor step is for each sub-community to codify its FM policies, practices and approaches in individual, focused guidebooks. Then, the sub-communities can look across NASA to better understand the different ways off-nominal conditions are addressed, and to seek commonality or at least an understanding of the multitude of FM approaches. This paper describes the development of the "Deep Space Robotic Fault Management Guidebook," which is intended to be the first of NASA's FM guidebooks. Its purpose is to be a field-guide for FM practitioners working on deep space robotic missions, as well as a planning tool for project managers. Publication of this Deep Space Robotic FM Guidebook is expected in early 2015. The guidebook will be posted on NASA's Engineering Network on the FM Community of Practice website so that it will be available to all NASA projects. Future plans for subsequent guidebooks for the other NASA sub-communities are proposed.
As part of NASA's Project Prometheus, the Nuclear Systems Program, NASA GRC performed trade studies on the various Power Management and Distribution (PMAD) options for a deep-space scientific spacecraft which would have a nominal electrical power requirement of 100 kWe. These options included AC (1000Hz and 1500Hz and DC primary distribution at various voltages. The distribution system efficiency, reliability, mass, thermal, corona, space radiation levels and technology readiness of devices and components were considered. The final proposed system consisted of two independent power distribution channels, sourced by two 3-phase, 110 kVA alternators nominally operating at half-rated power. Each alternator nominally supplies 50kWe to one half of the ion thrusters and science modules but is capable of supplying the total power re3quirements in the event of loss of one alternator. This paper is an introduction to the methodology for the trades done to arrive at the proposed PMAD architecture. Any opinions expressed are those of the author(s) and do not necessarily reflect the views of Project Prometheus.
A key science goal of the NASA “Moon to Mars” campaign is to understand how biology responds to the Lunar, Martian, and deep space environments in order to advance fundamental knowledge, reduce risk, and support safe, productive human space missions. Through the powerful emerging approaches of artificial intelligence (AI) and machine learning (ML), a paradigm shift has begun in biomedical science and engineered astronaut health systems, to enable Earth independence and autonomy of mission operations. Here we present an overview of AI/ML architecture to support deep space mission goals, developed with leaders in the field. First, we focus on the fundamental biological research that supports our understanding of physiological responses to spaceflight, and we describe current efforts to support AI/ML research including data standardization and data engineering through maximally open and FAIR (findable, accessible, interoperable, reusable) databases and the generation of AI-ready datasets for reuse and analysis. We also discuss remote data management frameworks for research data as well as environmental and health data that are generated during deep space missions. We highlight several research projects that leverage data standardization and management for fundamental biological discovery to uncover the complex effects of space travel on living systems. Next, we provide an overview of cutting-edge AI/ML approaches that can be integrated to support remote monitoring and analysis during deep space missions, including generative models and large language models to learn the underlying biomedical patterns and predict outcomes or answer questions during off world medical scenarios. We also describe current AI/ML methods to support this research and monitoring through automated cloud-based labs which enable limited human intervention and closed-loop experimentation in remote settings. These labs could support mission autonomy by analyzing environmental data streams, and would be facilitated through in situ analytics capabilities to avoid sending large raw data files through low bandwidth communications. Finally, in the context of deep space missions with limited communications or access to medical advice from Earth, we describe a solution for integrated, real-time mission biomonitoring across hierarchical levels from continuous environmental monitoring, to wearables and point-of-care devices, to molecular and physiological monitoring. We introduce a precision space health system that will ensure that the future of space health is predictive, preventative, participatory and personalized.
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
NASA's Advanced Exploration Systems Logistics Reduction Project is developing technologies that reduce mission mass and volume for exploration. Recently there has been increasing interest in determining the quantity of consumable logistics and system spares necessary to ensure a certain level of reliability. This is influenced by a technology's criticality and degree of impact to the overall mission. Technologies that directly reduce mass (e.g. longer wear crew clothing) are relatively straightforward for calculating the savings and understanding the mission impacts. Waste management technologies that process waste can reduce mass, but spares and contingency modes are more interwoven with other vehicle systems, so assessment is more complex. This paper considers mission benefits while also considering impacts from hardware failures for technologies including: crew clothing, reusable cargo bags for habitat outfitting, automated RFID cargo tracking, trash processing/storage/repurposing, and high reliability toilets.
The overall evolution of the Helios Project is summarized from its conception through to the completion of the Helios-1 mission phase 2. Beginning with the project objectives and concluding with the Helios-1 spacecraft entering its first superior conjunction (end of mission phase 2), descriptions of the project, the mission and its phases, international management and interfaces, and Deep Space Network-spacecraft engineering development in telemetry, tracking, and command systems to ensure compatibility between the U.S. Deep Space Network and the German-built spacecraft are included.
Cryogenic fluid management (CFM) technologies are very important for enabling a wider range of missions to utilize space nuclear propulsion (SNP) concepts such as nuclear thermal propulsion (NTP). Technologies for thermal and cryogenic propellant management allow for vehicles to take full advantage of the higher efficiency NTP systems for longer duration human interplanetary and deep space robotic missions. Currently, the CFM Portfolio Project at NASA’s Marshall Space Flight Center (MSFC) is developing thermal and propellant management technologies needed for SNP. When developing these technologies, it is important to understand the sensitivities of key performance parameters (KPPs) at the system and overall mission level due to the ways the technologies interact with each other, other subsystems, and influence the overall vehicle. The Advanced Concepts Office (ACO) at NASA-MSFC was tasked with building an integrated system model of a human Mars NTP mission to evaluate the impacts and sensitivities of CFM technologies on the overall vehicle and mission. This paper will cover the buildup of the model and highlight major sensitivities and breakpoints encountered, as well as future work in improving the existing models and sensitivities being evaluated.
Cryogenic fluid management (CFM) technologies are very important for enabling a wider range of missions to utilize space nuclear propulsion (SNP) concepts such as nuclear thermal propulsion (NTP). Technologies for thermal and cryogenic propellant management allow for vehicles to take full advantage of the higher efficiency NTP systems for longer duration human interplanetary and deep space robotic missions. Currently, the CFM Portfolio Project at NASA’s Marshall Space Flight Center (MSFC) is developing thermal and propellant management technologies needed for SNP. When developing these technologies, it is important to understand the sensitivities of key performance parameters (KPPs) at the system and overall mission level due to the ways the technologies interact with each other, other subsystems, and influence the overall vehicle. The Advanced Concepts Office (ACO) at NASA-MSFC was tasked with building an integrated system model of a human Mars NTP mission to evaluate the impacts and sensitivities of CFM technologies on the overall vehicle and mission. This paper will cover the buildup of the model and highlight major sensitivities and breakpoints encountered, as well as future work in improving the existing models and sensitivities being evaluated.
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
Steve Wall is the host of this video entitled, "Return to the Red Planet". Live animation of the Mars Observer orbiting Mars is presented. Steve Wall explains the spacecraft insertion maneuver and also explains the purpose for the Mars Observer launch. Live coverage of the Cape Canaveral launch of the Mars Observer is also presented. Suzanne Dodd, Chief of the Mission Planning team describes the burn start and how the spacecraft will be captured by Mars' gravity. Glenn Cunningham, Mars Observer Project Manager, gives background information on the Mars Observer and describes the organizations behind the Mars Observer Spacecraft, such as the Deep Space Network, the Mission Operation Support Office, Science Investigators, the Flight Engineering Office, Operations Office, and the Ground Data System Office. Dr. William Piotrowski, Acting Director, Solar System Exploration Division, NASA, talks about the purpose of the Mars Pathfinder which is to develop the technology and systems for landing small science packages on Mars. Mr. Roger Gibbs, Former Mars Observer Spacecraft Systems Engineer, tells us how the Mars Observer was built and describes the structural elements on the Mars Observer. The 11-month cruise period for the spacecraft is given by Joseph Beerer, Manager of the Engineering office. The thrust for the Mars Orbit Insertion is described by Ronald Klemetson, Technical Manager, Propulsion Subsystem Jet Propulsion Laboratory (JPL). George Chen, Lead Engineer Attitude and Articulation Subsystem Spacecraft Team, explains the importance of the attitude control engines on the Spacecraft. Marvin Traxler, Manager of Tracking and Data Acquisition, describes how searching for a signal from the Mars Observer works. See NONP-NASA-VT-2000081555 for a continuation of this discussion with Marvin Traxler.
In January 2017, the mission concept Psyche: Journey to a Metal World was one of two concepts selected by NASA for implementation as part of the 14th Discovery mission competition. Over the course of the past year, the Psyche team has actively worked to refine and mature the technical design, culminating in a successful completion of the Project Preliminary Design review and approval to proceed to Phase C in mid-2019. Psyche is a deep space mission utilizing solar electric propulsion (SEP), consisting of SPT-140 Hall thrusters which have been successfully employed on multiple commercial spacecraft. When launched, Psyche will carry over 1000 kg of Xenon, and will represent the farthest usage of electric propulsion usage from the Sun – a distance of over 3.3 AU. The use of solar electric propulsion in deep space has resulted in challenges unique to other missions. Spacecraft designs typically balance margins across two main elements – mass and power – that are independent of one another. Utilizing a low thrust trajectory through the application of electric propulsion introduces more elements - namely flight time, missed thrust percentage and thruster duty cycle. Moreover, these elements become connected, presenting additional relationships that must be considered. This paper will present an overview of the margin management process for Psyche, and how it has evolved from the early proposal stage to its current state. It will discuss the elements that are margined, their relationship with one another, and key uncertainties that must be addressed. It discusses challenges and mitigations obtained during the refinement of the Psyche project, culminating in a new margin strategy that enables optimization across many of the system elements, and will serve as a template for future deep space SEP missions.
The Operations Engineering Lab (OEL) at JPL has developed the multimission command system as part of JPL's Advanced Multimission Operations System. The command system provides an advanced multimission environment for secure, concurrent commanding of multiple spacecraft. The command functions include real-time command generation, command translation and radiation, status reporting, some remote control of Deep Space Network antenna functions, and command file management. The mission-independent architecture has allowed easy adaptation to new flight projects and the system currently supports all JPL planetary missions (Voyager, Galileo, Magellan, Ulysses, Mars Pathfinder, and CASSINI). This paper will discuss the design and implementation of the command software, especially trade-offs and lessons learned from practical operational use. The lessons learned have resulted in a re-engineering of the command system, especially in its user interface and new automation capabilities. The redesign has allowed streamlining of command operations with significant improvements in productivity and ease of use. In addition, the new system has provided a command capability that works equally well for real-time operations and within a spacecraft testbed. This paper will also discuss new development work including a multimission command database toolkit, a universal command translator for sequencing and real-time commands, and incorporation of telecommand capabilities for new missions.
Prior to 2010, NASA's advanced life support research and development was carried out primarily under the Exploration Life Support Project of NASA's Exploration Systems Mission Directorate. In 2011, the Exploration Life Support Project was merged with other projects covering Fire Prevention/Suppression, Radiation Protection, Advanced Environmental Monitoring and Control, and Thermal Control Systems. This consolidated project was called Life Support and Habitation Systems, which was managed under the Exploration Systems Mission Directorate. In 2012, NASA re-organized major directorates within the agency, which eliminated the Exploration Systems Mission Directorate and created the Office of the Chief Technologist (OCT). Life support research and development is currently conducted within the Office of the Chief Technologist, under the Next Generation Life Support Project, and within the Human Exploration Operation Missions Directorate under several Advanced Exploration System projects. These Advanced Exploration Systems projects include various themes of life support technology testing, including atmospheric management, water management, logistics and waste management, and habitation systems. Food crop testing is currently conducted as part of the Deep Space Habitation (DSH) project within the Advanced Exploration Systems Program. This testing is focused on growing salad crops that could supplement the crew's diet during near term missions.
The management of the Ulysses project, a probe which will fly a solar polar orbit, is described. The 5-yr mission will feature a flyby of Jupiter to deflect the spacecraft into a high-inclination orbit. Data on the solar corona, solar wind, the sun-wind interface, the heliospheric magnetic field, solar and nonsolar cosmic rays, etc., will be gathered as a function of the solar latitude. NASA will track and control the probe with the Deep Space Network. JPL provides project management for NASA while the Directorate of Scientific Programs performs ESA management functions. The DOE will provide a radioisotope thermoelectric generator while NASA and ESA each supply half the scientific payload. A NASA-ESA Joint Working Group meets about twice per year to monitor the project and discuss the technical and scientific requirements. Safety issues and measures which are being addressed due to the presence of the Pu-238 heat source for the RTG are discussed.
Deep-space manned missions will require advanced automated health assessment capabilities. Requirements such as in-space assembly, long dormant periods and limited accessibility during flight, present significant challenges that should be addressed through Integrated System Health Management (ISHM). The ISHM approach will provide safety and reliability coverage for a complete system over its entire life cycle by determining and integrating health status and performance information from the subsystem and component levels. This paper will focus on the potential advanced diagnostic elements that will provide intelligent assessment of the subsystem health and the planned implementation of these elements in the ISHM Testbed and Prototypes (ITP) Project under the NASA Exploration Systems Research and Technology program.
In January 2017, Psyche was one of two mission concepts selected by NASA for flight as part of the 14th Discovery mission competition. The project has been staffing up and maturing the spacecraft, instrument and mission system baseline designs on the path towards a 2022 launch. During much of 2018, the Project has been executing the lifecycle stage called Phase B, “Preliminary Design and Technology Completion,” one key element of which is the development and management of requirements at various levels. In the case of the Psyche project, this process has been particularly unique for several reasons. The project utilizes a Solar Electric Propulsion (SEP) Chassis from Space Systems Loral (SSL), a high volume manufacturer of commercial geostationary (GEO) telecom spacecraft based on the 1300 satellite bus. While SSL has an extensive, well-vetted set of requirements based on their very successful Earth-orbiting product line, translating that heritage to a deep space science mission required special care. In addition to the differences associated with the deep space environment and longer communication times, new interfaces had to be incorporated. While a substantial portion of the Flight System consists of the SEP Chassis, there were several new interfaces within various subsystems between SSL components and those provided by JPL and other contractors. Managing these interfaces through requirements at a relatively higher level than normally seen on internal or external builds proved challenging. Finally, the Psyche spacecraft plans to host the flight terminal of the Deep Space Optical Communications (DSOC) technology demonstration, which is itself a separate project with its own requirements that must be flowed down and managed. This paper will present an overview of the requirement development and management process for the Psyche project. It will discuss in detail the various challenges summarized above, the methods and decisions chosen to address them, and evaluate their overall effectiveness at this stage in the project.