Search NASA⌕ Search

SEARCH · Search NASA

Results for “Ground Operational Support System”

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.

At least 1,099 records · Page 61

ISS Potable Water Quality for Expeditions 26 through 30

International Space Station (ISS) Expeditions 26-30 spanned a 16-month period beginning in November of 2010 wherein the final 3 flights of the Space Shuttle program finished ISS construction and delivered supplies to support the post-shuttle era of station operations. Expedition crews relied on several sources of potable water during this period, including water recovered from urine distillate and humidity condensate by the U.S. water processor, water regenerated from humidity condensate by the Russian water recovery system, and Russian ground-supplied potable water. Potable water samples collected during Expeditions 26-30 were returned on Shuttle flights STS-133 (ULF5), STS-134 (ULF6), and STS-135 (ULF7), as well as Soyuz flights 24-27. The chemical quality of the ISS potable water supplies continued to be verified by the Johnson Space Center s Water and Food Analytical Laboratory (WAFAL) via analyses of returned water samples. This paper presents the chemical analysis results for water samples returned from Expeditions 26-30 and discusses their compliance with ISS potable water standards. The presence or absence of dimethylsilanediol (DMSD) is specifically addressed, since DMSD was identified as the primary cause of the temporary rise and fall in total organic carbon of the U.S. product water that occurred in the summer of 2010.

Straub, John E., II↗

UTM and D-NET: NASA and JAXA's Collaborative Research on Integrating Small UAS with Disaster Response Efforts

Natural disasters, such as flooding, wildfire, hurricane, tornadoes, earthquakes and tsunamis, pose challenges in preserving human life and minimizing the damages to a region. During catastrophic events, timely response of disaster relief personnel, an efficient deployment of resources in the recovery effort, and coordinated information sharing amongst different relief agencies can make a substantial difference in responding to those impacted by the disaster. Many relief activities currently utilize both ground personnel and manned airborne assets during different phases of the disaster response. Typically, multiple organizations support relief activities and this often creates logistics coordination challenges between agencies which can result in wasted time or resources. The Japan Aerospace Exploration Agency (JAXA) has been developing an "Integrated aircraft operation system for disaster relief (D-NET)", which assists collection and sharing of disaster information through the integrated operation of aircraft such as helicopters, aircraft, and satellites, for efficient and safe rescue operations by disaster relief aircraft. Due to the advancement in unmanned aircraft systems (UAS) technologies, public safety organizations have started incorporating small UAS (sUAS) as an asset in their disasters response activities. To address the airspace integration challenges of the influx of sUAS in the United States the National Aeronautics and Space Administration (NASA), under the UAS Traffic Management (UTM) project, has been engaged in research to enable large-scale commercial applications of sUAS operating in low altitude airspace. This paper presents the integration of D-NET, which incorporate sUAS in the planning, information sharing, and operation support of disasters response activities, and UTM, which provides airspace management to enable large scale high density operations. The integration of the DNET and UTM systems enables coordination, data sharing, and airspace management to improve the timeliness of the disaster response, enable relief organization to reduce cost and overhead by using UAS assets and still maintain airspace safety during the relief activities.

UTM↗

Earth-Independent Medical Operations (EIMO) Concept of Operations

In contrast to the current crew health paradigm for low-Earth orbit and Lunar missions, which depends on real-time communication with Mission Control, deep-space exploration missions will require a significant shift in medical operations. This shift is driven by the constraints of operating at a considerable distance from Earth, such as resource limitations—lack of resupply, restricted mass, power, volume, and data—as well as communication delays and the inability to evacuate back to Earth during emergencies. To move toward a more self-reliant medical model, a strategy is needed to gradually increase space-based crew autonomy and reduce risks to mission success in the challenging environment of deep space. This transformative change, known as "Earth-Independent Medical Operations" (EIMO), explores the gradual transfer of medical care and decision-making from Earth-based support to space-based systems. The goal of this transition is to enhance astronaut health and performance while minimizing mission risks. EIMO requires the development of a medical system that integrates seamlessly with mission planning, vehicle and spacesuit design, and data architecture. This integration is crucial for building a robust medical infrastructure that not only safeguards astronaut well-being but also ensures overall mission success. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has revised the EIMO model-based Concept of Operations (ConOps) which outlines an initial vision for EIMO. The ConOps, which is built on the stakeholders’ need, system goals, and objectives (NGOs), presents an array of in-mission scenarios that span a wide range of medical conditions demonstrating the system’s capabilities from basic to complex events. Developed by a multidisciplinary team of systems engineers, scientists, and clinicians within ExMC, the ConOps revision includes two new scenarios(Barotrauma and Self-Medical Management and Behavioral Health and Chronic Medical Care), and implementation of findings from EIMO technical interchange meetings that focused on data and training. The envisioned EIMO Medical System (MS) operates as a system of systems, gathering data from various sources such as reference databases, real-time wearable sensors, point-of-care diagnostics, and environmental controls. The MS also incorporates advanced training tools to support autonomous medical care, assisting the Crew Medical Officer (CMO) during medical events where Ground Support is either unavailable or communication-delayed beyond practicality. Furthermore, MS functions and capabilities were decomposed from the scenarios to establish foundational requirements for EIMO and traced to the NASA Spaceflight Human-System Standard(NASA-STD-3001, Volumes 1 and 2). These traces were performed to gain insights on the alignment of EIMO requirements with the NASA standard. This work serves as an initial recommendation to increase crew autonomy gradually and safely for Mars missions and future deep-space exploration.

medical system↗

IEEE 802.16J-Relay Fortified Aeromacs Networks; Benefits and Challenges

Aeronautical Mobile Airport Communications System (AeroMACS) is an IEEE 802.16 standard-based (WiMAX) broadband aviation transmission technology, developed to provide safety critical communications coverage for airport surface in support of fixed and mobile ground to ground applications and services. We have previously demonstrated that IEEE 802.16j-amendment-based WiMAX is most feasible for AeroMACS applications. The principal argument in favor of application of IEEE 802.16j technology is the flexible and cost effective extension of radio coverage that is afforded by relay fortified WiMAX networks, with virtually no increase in the power requirements. In this article, following introductory remarks on airport surface communications, WiMAX and AeroMACS; the IEEE 802.16j-based WiMAX technology and multihop relay systems are briefly described. The two modes of relay operation supported by IEEE 802.16j amendment; i.e., transparent (TRS) and non-transparent (NTRS) modes, are discussed in some detail. Advantages and disadvantages of using TRS and NTRS in AeroMACS networks are summarized in a table. Practical issues vis--vis the inclusion of relays in AeroMACS networks are addressed. It is argued that the selection of relay type may affect a number of network parameters. A discussion on specific benefits and challenges of inclusion of relays in AeroMACS networks is provided. The article concludes that in case it is desired or necessary to exclusively employ one type of relay mode for all applications throughout an AeroMACS network, the proper selection would be the non-transparent mode.

Networks↗

Ramp Traffic Console (RTC) Capabilities and Use in Operational Environment (Part 1)

This presentation provides an overview of ramp traffic control (RTC) and ramp manager traffic console (RMTC) features of ATD-2 Integrated Arrival, Departure, and Surface (IADS) system and will discuss operational use cases that cover surface metering, notification and optional hold of APREQ (approval request/call for release), EDCT (expected departure clearance time), and ground stops.

Airline Ramp Decision Support↗

Analysis of Launch Vehicle Liftoff Debris: Historical Perspective from Space Shuttle and Application to Artemis I

Human exploration-class launch vehicles are inherently prone to debris due to the extreme environments generated during pre-launch operations, liftoff, and flight. The use of cryogenic propellants often requires thermal protection system (TPS) coatings, typically foam, to maintain the propellant conditions in the tank and prevent an accumulation ice on the external surface of the vehicle. Some ice growth is to be expected at umbilical interfaces, vents, flanges, or brackets where it is difficult to apply TPS. This ice may come loose at any time due to wind on the launch pad, structural vibration and acoustics after rocket ignition, or aerodynamic forces during flight. This phenomena is especially apparent on vehicles with no TPS, such as the Saturn V rockets used in the Apollo Program, see Figure 1. During propellant tanking, the thermal contraction of the underlying substrate may generate cracks in the TPS (Figure 1). Chunks of TPS can release due to the expansion of ingested gas from cryopumping or from aerodynamic forces if the crack creates an offset surface. Most foams will also have a certain amount of “popcorning” where small pieces of foam will pop off during flight because of the differential between the static surface pressure and the pressure of the gas trapped in the foam cell structure. There are a number of other coating or closeout materials that may be shed from the vehicle and become debris. During pre-launch operations and liftoff, the vehicle may also be exposed to debris originating from the launch pad or ground support equipment. This debris is separate from foreign object debris, or FOD, which is not intended to be present and is strictly controlled through operations and maintenance procedures. In this case, debris is generated from hardware and materials that are necessary for launch and are subject to the intense vibration, acoustics, and direct plume impingement of the launch environment. Examples include ice from umbilicals, tape and tie wraps that protect cables, and rust or corrosion from the launch platform. While NASA has historically been aware of debris as a potential issue that could cause a failure resulting in loss of mission, loss of vehicle, or loss of crew, the likelihood and severity of that risk was not always well understood or given sufficient weight in program and flight decisions. After the Space Shuttle Columbia accident (STS-107), the investigation found that foam TPS debris shed from the external tank was the proximate cause of the damage to the orbiter wing. Six previous observations of debris released from the foam ramp that covered the bipod connecting the forward end of the orbiter to the external tank resulted in minor changes or were determined to be accepted flight risks. Two occurrences of bipod ramp foam loss were not identified until the STS-107 investigation. Despite the damage inflicted by these debris strikes, the Shuttle Program Requirements Control Board deemed the vehicle safe to fly. During the Return to Flight effort following the Columbia disaster, NASA Engineering developed a process for the assessment of debris transport, impact, and damage tolerance to support independent assessments of risk by NASA Safety and Mission Assurance (S&MA). Under this system, each element (vehicle or ground system) defines a catalog of all expected debris based on launch history, component testing, or analysis. Debris transport analysis (DTA) is conducted using the debris catalog characteristics and potential flow transport mechanisms (e.g., vehicle aerodynamics, gravity, wind, plume-driven). The predicted debris impact locations and velocities are provided to the hardware owners, who use available test data and analysis to determine whether each component can withstand the impacts. In cases where the element hardware may be severely damaged or fail, the options are to mitigate the debris source through some change in design or operation, or to work with S&MA to try to characterize the probability of the impact and damage for program risk acceptance. Because of the differences in debris characteristics and transport, the DTA has been divided between the Liftoff and Ascent regimes. The development and application of Liftoff DTA methodology from the Shuttle Program to the current Artemis Program is the subject of this paper. Liftoff DTA covers the time from the start of pre-launch operations at the launch pad, up until the vehicle clears the launch tower and there is no longer any interaction with ground systems. Debris transport during this period is broadly classified as either gravity, wind, and plume-entrained (GWPE) or plume driven (PD). GWPE debris is generally lower speed, travelling in a forward-to-aft direction. PD transport includes flow features from the rocket ignition transient, as well as plume impingement and recirculation that occur as the vehicle lifts off the launch platform. In these cases, the debris typically moves in an aft-to-forward direction at higher speeds. The applicable transport mechanisms must be considered for each piece of debris depending on the material, and release location and time. For example, rust or metallic debris from the tower could fall (GWPE) and impact the vehicle before landing on the launch platform deck where it could be also be transported by plume impingement (PD). However, falling ice (GWPE) from an umbilical is unlikely to survive impact with the vehicle or launch platform and be available for PD transport. Modeling of debris transport is accomplished using a set of DTA tools which simulate debris trajectories subject to a reference frame acceleration (i.e., gravity) and aerodynamic drag. Where the trajectory encounters a solid surface, the debris is allowed to rebound with a specified coefficient of restitution. The drag is calculated by interpolating the fluid state at each point in the debris trajectory from high-fidelity computational fluid dynamics (CFD) simulations of the launch vehicle and pad. The CFD data may either be static (steady state or time averaged), typically for GWPE transport, or dynamic (time-accurate) for PD flow features like the ignition transient. Examples of the CFD flow field solutions for the Space Launch System (SLS) rocket and launch pad are shown in Figure 2. Typical SLS debris trajectory predictions from DTA are illustrated in Figure 3. The final version of this paper will include a more detailed examination of the Liftoff DTA process developed during the Shuttle Program, and how it has been augmented and applied to the SLS rocket under the Artemis Program. Comparisons with debris observations from the Artemis I launch will demonstrate validation of the tools and methodology.

Debris↗

Data management for Large Space Telescope

The data management system for the Large Space Telescope (LST) must be capable of meeting requirements of 160 million bits per 95 min orbit with a bit error rate of less than 0.00001 for data. The system will be supported by the Tracking and Data Relay Satellite System of the Space Tracking and Data Network. The on-board system includes a general purpose computer that controls the vehicle as a stable observation platform and the array of instruments used for data collection. The ground-based system comprises a Mission Operations Center (MOC), a Science Institute where instrument data is processed, and a communications service for the space and point-to-point data flow. The allocation of hardware and software between on-board and ground-based components to achieve design objectives of maximum flexibility at minimum cost is discussed.

Hope, G. R., Jr.↗

DSN test and training system, Mark III-77

The Mark III-77 system is configured to support DSN testing and training in preparation for the Mariner-Jupiter-Saturn 1977 and Pioneer-Venus 1978 missions, in addition to the on-going in-flight missions. DSN Test and Trailing System capabilities include functions performed in the Deep Space Stations, Ground Communications Facility, and Network Operations Control Center.

Thornman, H. C.↗

Design and operational features of the Ultraviolet Imaging Telescope flight and ground software

The NASA Office of Space Sciences and Applications is sponsoring a series of Space Shuttle missions named Astro-n which are dedicated to a variety of astronomical projects. These missions will be the first in which the Space Shuttle crew will be interactively operating an astronomical observatory which is fixed in the payload bay. The operation of an instrument in such an environment requires a considerable amount of software both on board and on the ground. The Spacelab Experiment Computer provides generalized interactive telemetry display and command processing services through the Experiment Computer Operating System. The experimenter must then design a software package for his Dedicated Experiment Processor which can provide complete control of his instrument as well as communicate with the Experiment Computer. This paper describes the design considerations and operational features of the Ultraviolet Imaging Telescope Dedicated Experiment Processor and Instrument Ground Support Equipment software.

Parise, R. A.↗

Flight Team Development in Support of LCROSS - A Class D Mission

The LCROSS (Lunar Crater Observation and Sensing Satellite) project presented a number of challenges to the preparation for mission operations. A class D mission under NASA s risk tolerance scale, LCROSS was governed by a $79 million cost cap and a 29 month schedule from "authority to proceed" to flight readiness. LCROSS was NASA Ames Research Center s flagship mission in its return to spacecraft flight operations after many years of pursuing other strategic goals. As such, ARC needed to restore and update its mission support infrastructure, and in parallel, the LCROSS project had to newly define operational practices and to select and train a flight team combining experienced operators and staff from other arenas of ARC research. This paper describes the LCROSS flight team development process, which deeply involved team members in spacecraft and ground system design, implementation and test; leveraged collaborations with strategic partners; and conducted extensive testing and rehearsals that scaled in realism and complexity in coordination with ground system and spacecraft development. As a testament to the approach, LCROSS successfully met its full mission objectives, despite many in-flight challenges, with its impact on the lunar south pole on October 9, 2009.

Tompkins, Paul D.↗

High-Payoff Space Transportation Design Approach with a Technology Integration Strategy

A general architectural design sequence is described to create a highly efficient, operable, and supportable design that achieves an affordable, repeatable, and sustainable transportation function. The paper covers the following aspects of this approach in more detail: (1) vehicle architectural concept considerations (including important strategies for greater reusability); (2) vehicle element propulsion system packaging considerations; (3) vehicle element functional definition; (4) external ground servicing and access considerations; and, (5) simplified guidance, navigation, flight control and avionics communications considerations. Additionally, a technology integration strategy is forwarded that includes: (a) ground and flight test prior to production commitments; (b) parallel stage propellant storage, such as concentric-nested tanks; (c) high thrust, LOX-rich, LOX-cooled first stage earth-to-orbit main engine; (d) non-toxic, day-of-launch-loaded propellants for upper stages and in-space propulsion; (e) electric propulsion and aero stage control.

McCleskey, C. M.↗

Automating Mid- and Long-Range Scheduling for NASA's Deep Space Network

NASA has recently deployed a new mid-range scheduling system for the antennas of the Deep Space Network (DSN), called Service Scheduling Software, or S(sup 3). This system is architected as a modern web application containing a central scheduling database integrated with a collaborative environment, exploiting the same technologies as social web applications but applied to a space operations context. This is highly relevant to the DSN domain since the network schedule of operations is developed in a peer-to-peer negotiation process among all users who utilize the DSN (representing 37 projects including international partners and ground-based science and calibration users). The initial implementation of S(sup 3) is complete and the system has been operational since July 2011. S(sup 3) has been used for negotiating schedules since April 2011, including the baseline schedules for three launching missions in late 2011. S(sup 3) supports a distributed scheduling model, in which changes can potentially be made by multiple users based on multiple schedule "workspaces" or versions of the schedule. This has led to several challenges in the design of the scheduling database, and of a change proposal workflow that allows users to concur with or to reject proposed schedule changes, and then counter-propose with alternative or additional suggested changes. This paper describes some key aspects of the S(sup 3) system and lessons learned from its operational deployment to date, focusing on the challenges of multi-user collaborative scheduling in a practical and mission-critical setting. We will also describe the ongoing project to extend S(sup 3) to encompass long-range planning, downtime analysis, and forecasting, as the next step in developing a single integrated DSN scheduling tool suite to cover all time ranges.

scheduling↗

Functional Fault Model Development Process to Support Design Analysis and Operational Assessment

A functional fault model (FFM) is an abstract representation of the failure space of a given system. As such, it simulates the propagation of failure effects along paths between the origin of the system failure modes and points within the system capable of observing the failure effects. As a result, FFMs may be used to diagnose the presence of failures in the modeled system. FFMs necessarily contain a significant amount of information about the design, operations, and failure modes and effects. One of the important benefits of FFMs is that they may be qualitative, rather than quantitative and, as a result, may be implemented early in the design process when there is more potential to positively impact the system design. FFMs may therefore be developed and matured throughout the monitored system's design process and may subsequently be used to provide real-time diagnostic assessments that support system operations. This paper provides an overview of a generalized NASA process that is being used to develop and apply FFMs. FFM technology has been evolving for more than 25 years. The FFM development process presented in this paper was refined during NASA's Ares I, Space Launch System, and Ground Systems Development and Operations programs (i.e., from about 2007 to the present). Process refinement took place as new modeling, analysis, and verification tools were created to enhance FFM capabilities. In this paper, standard elements of a model development process (i.e., knowledge acquisition, conceptual design, implementation & verification, and application) are described within the context of FFMs. Further, newer tools and analytical capabilities that may benefit the broader systems engineering process are identified and briefly described. The discussion is intended as a high-level guide for future FFM modelers.

Verification↗

SAM 3.0 Workshop Alliance SV Lab

Nissan is building a Seamless Autonomy Mobility (SAM) which is a cloud-based system of artificial intelligence that manages a fleet of autonomous vehicles. It pairs artificial intelligence with human intelligence in order to create a seamless solution that allows autonomous drive to be viable and marketable. They have created a Mobility Manager function which is a laborer who executed human-in-the-loop functions within SAM system. Nissan invited the HAT Lab to discuss NASA's lessons learned on remote operator support and to participate in a workshop discussion of one of their use cases. This presentation covers some of the HAT Lab's work on a human-autonomy teaming Agent and previous Reduced Crew Operations ground station development.

Human-Autonomy Teaming↗

Extended Duration: The SIRIUS 21 Crew Perspective

The SIRIUS (Scientific International Research In a Unique terrestrial Station) missions represent a collaborative effort between NASA and Russia’s Institute for Biomedical Problems (IBMP) to conduct a series of long duration isolation and confinement spaceflight analog missions. Three missions of 17-day, 4-month, and 8-month duration (SIRIUS 17, 19, and 21) have been completed at IBMP’s Ground-Based Experimental Complex / Nazemnyy eksperimental'nyy kompleks (NEK) in Moscow, Russia. The international SIRIUS 21 crew comprising representatives from the United States, United Arab Emirates and Russia recently completed the 8-month analog lunar mission. The extended duration mission included simulated lunar transit, orbital, and surface operations with corresponding deep space communication delay, during which the crew participated in nearly 70 studies, eight of which were sponsored by NASA’s Human Research Program. The studies examined the effect of isolation and confinement on the behavioral health of research subjects, and investigated medical countermeasures, team performance, crew dynamics, crew autonomy, food system risks, consequences of confinement and associated physiological stressors. SIRIUS 21 crewmembers also participated in operational tasks such as Rover and CubeSat assembly, simulated lunar sample assessment, VR activities, robotic arm training, environmental systems monitoring, exercise, greenhouse maintenance and 3D printing. Communication with Mission Control was limited to 30-minute periods every two hours. Since access to the internet and email was restricted, simulated ground support provided the Crew’s primary source of daily news and mission information. This panel discussion will include presentations from the US SIRIUS 21 crewmembers – William Brown and Ashley Kowalski – about their experience participating in the mission and science. A facilitated question and answer session will follow with attendees encouraged to ask questions and join in discussion with the SIRIUS 21 crewmembers about their experiences. William Brown came to SIRIUS 21 with experience spread across multiple industries, including the military, defense contracting, healthcare consulting, software engineering, and logistics. He has lived in the Middle East, Central Asia, and Russia. A former Boren Scholar, Brown is fluent in Russian. He holds a Master of International Business degree from the University of South Carolina’s Darla Moore School of Business. Prior to that, he earned a bachelor’s degree in Russian language, literature, and culture from the University of South Carolina. There, he also completed additional undergraduate coursework in computer science. Ashley Kowalski is a Project Leader in The Aerospace Corporation’s International Partnerships Department, where she works with, represents, and provides technical support to the the U.S. Space Force Space Systems Command International Affairs (SSC/IA) office. Through her numerous national and international assignments (Russia, China, and Germany), she has worked on topics related to international space systems, national security space systems, civil systems (including human spaceflight and civil launch projects), space policy, satellite industry analysis, and satellite manufacturing start-ups. She is proficient in Russian and German, and fluent in Polish. Kowalski received her Bachelor of Science and Master of Science degrees in mechanical and aerospace engineering from George Washington University in 2011 and 2012, respectively.

S. E. Whiting↗

Ventilation Heat Exchanger / Flow Meter for xPLSS

The flow meter / heat exchanger (FMHX) in the ventilation loop of the exploration EMU cools the ventilation gas and measures the ventilation flow rate. The heat exchanger transfers heat from the ventilation gas to the thermal control loop via a miniature shell-and-tube heat exchanger. The flow meters calculate the flow rate of gas through the ventilation loop based on the pressure drop across the heat exchanger core. Creare has delivered four design validation test (DVT) heat exchangers and five DVT flow meters to NASA JSC to support development of the exploration portable life support system (xPLSS). This paper describes the design and performance of the DVT units.The heat exchangers are designed to cool the ventilation gas to a specified temperature with low pressure losses under the most challenging operating conditions. The measured performance of the DVT heat exchangers agrees well with design models and meets all performance requirements. The flow meters use a MEMS thermal flow sensor to produce a signal that is proportional to a small bypass flow around the heat exchanger core. They are designed to achieve high measurement accuracy across the full range of xPLSS operating conditions. We calibrated the flow meters in a special-purpose flow facility that simulates operation in the xPLSS ventilation loop. Calibration testing shows that DVT flow meters produce digital output for vent loop mass flow that meets NASA’s accuracy requirements across the range of xPLSS operating conditions. This paper reviews the design of the heat exchangers and flow meters and presents data from the final flow meter calibration testing, heat exchanger performance validation, and initial ground testing in NASA’s xPLSS.

spacesuit↗

Ventilation Heat Exchanger / Flow Meter for xPLSS

The flow meter / heat exchanger (FMHX) in the ventilation loop of the exploration EMU cools the ventilation gas and measures the ventilation flow rate. The heat exchanger transfers heat from the ventilation gas to the thermal control loop via a miniature shell-and-tube heat exchanger. The flow meters calculate the flow rate of gas through the ventilation loop based on the pressure drop across the heat exchanger core. Creare has delivered four design validation test (DVT) heat exchangers and five DVT flow meters to NASA JSC to support development of the exploration portable life support system (xPLSS). This paper describes the design and performance of the DVT units.The heat exchangers are designed to cool the ventilation gas to a specified temperature with low pressure losses under the most challenging operating conditions. The measured performance of the DVT heat exchangers agrees well with design models and meets all performance requirements. The flow meters use a MEMS thermal flow sensor to produce a signal that is proportional to a small bypass flow around the heat exchanger core. They are designed to achieve high measurement accuracy across the full range of xPLSS operating conditions. We calibrated the flow meters in a special-purpose flow facility that simulates operation in the xPLSS ventilation loop. Calibration testing shows that DVT flow meters produce digital output for vent loop mass flow that meets NASA’s accuracy requirements across the range of xPLSS operating conditions. This paper reviews the design of the heat exchangers and flow meters and presents data from the final flow meter calibration testing, heat exchanger performance validation, and initial ground testing in NASA’s xPLSS.

spacesuit↗

Risk Trade-Space Analysis for Safe Human Expeditions to Mars

We assessed the integrated safety, health, and performance risk to crews on long-duration missions, specifically to Mars. Using a systems approach rather than one focused on individual countermeasures, we examined the trade space around several such risks to identify high-potential risk mitigation strategies and characterize aspects of Mars mission architectures that could lower aggregated risk. Current Mars Design Reference missions would require durations well over two years and would increase crew exposure to radiation and microgravity well beyond ISS levels, likely resulting in significantly reduced performance beyond our current capability to mitigate that could jeopardize mission success. A “fast Mars transit” round-trip mission concept was studied using an innovative flight dynamics approach to quantify the minimum total mission energy required for a Mars transit with total mission duration less than 400 days. This approach holds promise for sending humans to Mars and returning them safely with acceptable, potentially mitigatable, exposure to microgravity and radiation using current or near-term technologies. The fast transit concept would also result in fewer time-driven vehicle failures and enable sustainable deployment of humans and infrastructure to Mars on a regular cadence, allowing steady exploration and colonization of Mars. Finally, we conclude that reliance on the Low Earth Orbit (LEO) mission operations paradigm – i.e., one of near-complete real-time dependence on experts at Mission Control to manage the combined state of the mission, vehicle, and crew – is high risk given the communication delays and limited resupply of any Mars mission, and this risk is not eliminated by the shorter missions durations of fast transit scenarios. Based on historical trends, it is highly likely that the crew will face a high-consequence problem of uncertain origin during Mars transit when ground support will be greatly reduced. While it may be possible to reduce anomaly rates through improved reliability analysis and testing, and to reduce anomaly impacts through added robustness, such mitigations address only known failure modes and known uncertainties. Therefore, a radical shift in the Human-Systems Integration Architecture (HSIA) that defines the operational paradigm, systems design, and human-systems interactions is required to improve the risk posture to an acceptable level regardless of mission duration.

Mars↗