Search NASA⌕ Search

SEARCH · Search NASA

Results for “Crew State Monitoring”

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 127 records · Page 7

Task Analytic Models to Guide Analysis and Design: Use of the Operator Function Model to Represent Pilot-Autoflight System Mode Problems

Task-analytic models structure essential information about operator interaction with complex systems, in this case pilot interaction with the autoflight system. Such models serve two purposes: (1) they allow researchers and practitioners to understand pilots' actions; and (2) they provide a compact, computational representation needed to design 'intelligent' aids, e.g., displays, assistants, and training systems. This paper demonstrates the use of the operator function model to trace the process of mode engagements while a pilot is controlling an aircraft via the, autoflight system. The operator function model is a normative and nondeterministic model of how a well-trained, well-motivated operator manages multiple concurrent activities for effective real-time control. For each function, the model links the pilot's actions with the required information. Using the operator function model, this paper describes several mode engagement scenarios. These scenarios were observed and documented during a field study that focused on mode engagements and mode transitions during normal line operations. Data including time, ATC clearances, altitude, system states, and active modes and sub-modes, engagement of modes, were recorded during sixty-six flights. Using these data, seven prototypical mode engagement scenarios were extracted. One scenario details the decision of the crew to disengage a fully automatic mode in favor of a semi-automatic mode, and the consequences of this action. Another describes a mode error involving updating aircraft speed following the engagement of a speed submode. Other scenarios detail mode confusion at various phases of the flight. This analysis uses the operator function model to identify three aspects of mode engagement: (1) the progress of pilot-aircraft-autoflight system interaction; (2) control/display information required to perform mode management activities; and (3) the potential cause(s) of mode confusion. The goal of this paper is twofold: (1) to demonstrate the use of the operator functio model methodology to describe pilot-system interaction while engaging modes And monitoring the system, and (2) to initiate a discussion of how task-analytic models might inform design processes. While the operator function model is only one type of task-analytic representation, the hypothesis of this paper is that some type of task analytic structure is a prerequisite for the design of effective human-automation interaction.

Degani, Asaf↗

Health Management Applications for International Space Station

Traditional mission and vehicle management involves teams of highly trained specialists monitoring vehicle status and crew activities, responding rapidly to any anomalies encountered during operations. These teams work from the Mission Control Center and have access to engineering support teams with specialized expertise in International Space Station (ISS) subsystems. Integrated System Health Management (ISHM) applications can significantly augment these capabilities by providing enhanced monitoring, prognostic and diagnostic tools for critical decision support and mission management. The Intelligent Systems Division of NASA Ames Research Center is developing many prototype applications using model-based reasoning, data mining and simulation, working with Mission Control through the ISHM Testbed and Prototypes Project. This paper will briefly describe information technology that supports current mission management practice, and will extend this to a vision for future mission control workflow incorporating new ISHM applications. It will describe ISHM applications currently under development at NASA and will define technical approaches for implementing our vision of future human exploration mission management incorporating artificial intelligence and distributed web service architectures using specific examples. Several prototypes are under development, each highlighting a different computational approach. The ISStrider application allows in-depth analysis of Caution and Warning (C&W) events by correlating real-time telemetry with the logical fault trees used to define off-nominal events. The application uses live telemetry data and the Livingstone diagnostic inference engine to display the specific parameters and fault trees that generated the C&W event, allowing a flight controller to identify the root cause of the event from thousands of possibilities by simply navigating animated fault tree models on their workstation. SimStation models the functional power flow for the ISS Electrical Power System and can predict power balance for nominal and off-nominal conditions. SimStation uses realtime telemetry data to keep detailed computational physics models synchronized with actual ISS power system state. In the event of failure, the application can then rapidly diagnose root cause, predict future resource levels and even correlate technical documents relevant to the specific failure. These advanced computational models will allow better insight and more precise control of ISS subsystems, increasing safety margins by speeding up anomaly resolution and reducing,engineering team effort and cost. This technology will make operating ISS more efficient and is directly applicable to next-generation exploration missions and Crew Exploration Vehicles.

Alena, Richard↗

STS-73 Post Flight Presentation

The post flight presentation of the STS-73 Space Shuttle's United States Microgravity Lab. (USML) mission was presented by the flight crew, Cmdr. Kenneth Bowersox, Pilot Kent Rominger, Payload Specialists Albert Sacco and Fred Gregory, and Mission Specialists Kathryn Thornton, Catherine 'Cady' Collman, and Michael Lopez-Alegria, using color video and slides. Film footage includes the prelaunch and launch activities, the USML and Middeck experiments (Advanced Protein Crystallization Facility (APCF), the Astroculture(tm) (ASC) hardware and experiment, the Commercial Generic Bioprocessing Apparatus (CGBA), the Crystal Growth Furnace (CGF), the Drop Physics Module (DPM), the Geophysical Fluid Flow Cell (GFFC), the Glovebox (GBX), the Zeolite Crystal Growth (ZCG) experiment, the Surface Tension Driven Convection Experiment (STDCE), the Protein Crystal Growth (PCG) experiment, three Measuring Microgravity experiments (the Space Acceleration Measurement System (SAMS), the Three Dimensional Microgravity Accelerometer (3DMA), and the Orbital Acceleration Research Experiment (OARE)), and the High-Packed Digital Television (HI-PAC) demonstration system), pre-return flight systems checkout, reentry, and space shuttle landing. The USML experiments were monitored via the HI-PAC system downlink. Earth views included mostly geographical locations (Mediterranean Sea; Turkey; Lake Powell, Arizona/Utah area; San Francisco Bay; Baltimore, Maryland; Washington, DC; India; Tibet; China; Bhutan; Philadelphia; and the Himalayas).

Source record↗

Assessments of Physiology and Cognition in Hybrid-Reality Environments (APACHE)

NASA is planning to return to the Moon in the mid-2020s as a stepping stone to Mars missions in the 2030s. Spacewalks, or extravehicular activities (EVAs), performed on the Moon and Mars will differ in a variety of ways from those that have been performed in decades past. NASA has identified multiple risks to human health and performance associated with a crewed mission to Mars, especially those associated with exploration EVAs which are expected to be a primary mission activity. Crew may be expected to conduct up to 24 hours of EVA per person per week, where the likelihood of injury and/or mental mistakes are increased compared to ground-based training or current microgravity EVAs and the consequences of which can be catastrophic. Current test environments for exploration EVA research and technology development are large, costly facilities that are limited in their availability or capabilities. Spacesuit testing in a reduced gravity environment such as NASA’s Neutral Buoyancy Laboratory, while a good representation of the crew’s physical workload during exploration EVAs, typically has small datasets and is difficult to integrate physiological sensors or other types of crew performance measures. Meanwhile, scientific field-based testing such as NASA’s Desert Research and Technology Studies offers an operationally relevant environment for exploration EVAs, particularly for cognitive workload, but is also limited by small datasets, lack of a pressurized spacesuit, and obtrusive measures. The limitations of current analogs for exploration EVAs identify a need for a new test environment that can approximate both the physical and cognitive demands associated with exploration EVAs to enable rapid, controlled, and repeatable evaluations of human health and performance risks of exploration missions. In response, the Human Physiology, Performance, Protection, and Operations Laboratory (H-3PO) at NASA Johnson Space Center has developed a hybrid reality exploration EVA analog named the Assessments of Physiology And Cognition in Hybrid-reality Environments (APACHE) to address these limitations using a combination of virtual, physical, and hybrid reality techniques. The APACHE facility resides at NASA Johnson Space Center and serves as a large “sandbox” for EVA research and simulation. At its center is a roughly 15x20ft space surrounded by a 14” tall sandbox partially filled with lunar regolith simulant to emulate the physical feeling of walking on a planetary surface and to allow for simulated geology operations. Nearby, a curved passive treadmill (Skillmill Connect, Technogym, Fairfield, NJ) and an omnidirectional treadmill (Infinadeck, Infinadeck, Rocklin, CA) are included to enable exploration of these large virtual environments while also imposing the physical demands, representative timelines, and cognitive burdens required to navigate and traverse these distances during exploration EVA. A 6DOF motion platform is used to simulate rover operations and supports various human performance evaluations and associated risks. Lastly, APACHE can support two extravehicular (EV) crewmembers working in tandem. A computer workstation is located nearby and also supports an intravehicular (IV) crewmember as part of a full mission simulation. The IV crewmember has direct video and audio communication with the EV crew in VR to provide operational and procedural support. The software used in APACHE was created by the JSC Engineering Directorate, in partnership with Buendea, powered by a custom Unreal Engine 5 (UE5.3, Epic Games) project. APACHE currently utilizes the HTC Vive Pro Eye in a wireless configuration for VR simulations. There are two virtual environments that subjects can explore within APACHE, a Lunar and Martian surface. The virtual Lunar surface was created from LIDAR data of the Lunar South Pole to create roughly 16 sq km of explorable terrain. The virtual Martian surface contains roughly 400 sq km of explorable terrain derived from Mars Reconnaissance Orbiter LIDAR data of the Jezero Crater. The immersion and related cognitive burdens of conducting a planetary EVA is simulated through a series of EVA-relevant tasks performed in the VR environment, using these high-fidelity visual representations. Additionally, APACHE includes biosensor driven informatics, such as real-time heart rate monitoring and/or derived values from model simulations, for active monitoring by the EV crew and added cognitive demand. A “Wizard of Oz” control panel enables test operators to activate contingency events such as simulated spacesuit malfunctions, loss of communications, and/or limited visibility. Embedded performance measures such as accuracy, completeness, and execution time have been developed for various exploration tasks to objectively quantify crew performance during an EVA and compare impacts to performance when different environmental stressors, both physical and cognitive, are added to or removed from the simulation. Additionally, validated cognitive and operational performance measures such as the Digit Symbol Substitution Task have been recreated and embedded in VR for direct and relatively unobtrusive measurement of motor perception. The APACHE environment currently supports multiple research studies at NASA. Examples include the CHAPEA project, a series of simulated year-long missions on Mars by a 4-person crew; and the CO2 Contingency Walk Back Study, an investigation of elevated CO2 exposure on crew performance during a contingency EVA scenario. APACHE also provides a test environment to support the development of the Crew State and Risk Model, which is a collection of individualized, mathematical models of crew physical and cognitive state; and the Personalized EVA Informatics and Decision Support system, an operational tool for flight controllers, and eventually a self-reliant Martian crew, to make biomedically-informed decisions in real-time to optimize the EVA planning and execution with respect to crew health and performance. Some technical challenges associated with developing the APACHE environment, as well as current limitations, include VR limitless natural walking with a hybrid spacesuit simulator, optimizing performance for wireless PC VR streaming while maintaining a high degree of visual fidelity, and the integration of various physiological (metabolic masks) and psychometric (eye tracking) sensors with the VR headset.

Human Performance↗

Overview of the NASA Terrestrial Environments Support Role: Data and Applications

This presentation focuses on the terrestrial environment component of the Natural Environments Branch’s (NEB’s) support role and highlights the instrumentation and data sources used, how the data are quality controlled and archived, and the analyses and use-cases of these datasets. A detailed overview is provided about some individual data sources that are used by the branch, which includes a network of instruments (e.g., wind towers, balloons, and profilers) and models, such as the Earth Global Reference Atmospheric Model (Earth-GRAM). Additionally, the data archival and quality control processes that maintain the high-quality climatological datasets from these sources are discussed, as are the implemented and pending updates to this process. Examples of the different applications for these datasets are presented to showcase the analytical and operational capabilities of the NEB and demonstrate the culmination of the entire process. This includes the Range Reference Atmospheres created and maintained by the NEB, sea-state analyses for crewed return, certification of observation systems for space flight, and the day-of-launch support process. The NEB at NASA Marshall Space Flight Center (MSFC) supports the NASA Engineering Directorate (ED) and Exploration Systems Development Mission Directorate (ESDMD) by providing the necessary environmental constraints to facilitate the safe design and operation of assets required for space travel. This includes, but is not limited to, the environmental considerations for assets residing at the launch sites, temporarily stationed at a launch site, traversing the [extra-]terrestrial atmosphere and open space, and arriving at their destination. As such, the Terrestrial and Planetary Environments Team within the NEB is but a part of the whole, delegated to quantify the environment that assets may encounter whilst on Earth and within its atmosphere. However, nearly all ESDMD assets are subjected to terrestrial conditions, which cover a diverse range of meteorological regimes and extremes. The team also supports day-of-launch operations for the Space Launch System (SLS), providing real-time monitoring of the winds and thermodynamics along the launch path using an amalgamation of observed, remotely sensed, and modeled output.

Systems Engineering↗

Near Real Time Tools for ISS Plasma Science and Engineering Applications

The International Space Station (ISS) program utilizes a plasma environment forecast for estimating electrical charging hazards for crews during extravehicular activity (EVA). The process uses ionospheric electron density (Ne) and temperature (Te) measurements from the ISS Floating Potential Measurement Unit (FPMU) instrument suite with the assumption that the plasma conditions will remain constant for one to fourteen days with a low probability for a space weather event which would significantly change the environment before an EVA. FPMU data is typically not available during EVA's, therefore, the most recent FPMU data available for characterizing the state of the ionosphere during EVA is typically a day or two before the start of an EVA or after the EVA has been completed. Three near real time space weather tools under development for ISS applications are described here including: (a) Ne from ground based ionosonde measurements of foF2 (b) Ne from near real time satellite radio occultation measurements of electron density profiles (c) Ne, Te from a physics based ionosphere model These applications are used to characterize the ISS space plasma environment during EVA periods when FPMU data is not available, monitor for large changes in ionosphere density that could render the ionosphere forecast and plasma hazard assessment invalid, and validate the "persistence of conditions" forecast assumption. In addition, the tools are useful for providing space environment input to science payloads on ISS and anomaly investigations during periods the FPMU is not operating.

Minow, Joseph I.↗

Information and display requirements for independent landing monitors

The ways an Independent Landing Monitor (ILM) may be used to complement the automatic landing function were studied. In particular, a systematic procedure was devised to establish the information and display requirements of an ILM during the landing phase of the flight. Functionally, the ILM system is designed to aid the crew in assessing whether the total system (e.g., avionics, aircraft, ground navigation aids, external disturbances) performance is acceptable, and, in case of anomaly, to provide adequate information to the crew to select the least unsafe of the available alternatives. Economically, this concept raises the possibility of reducing the primary autoland system redundancy and associated equipment and maintenance costs. The required level of safety for the overall system would in these cases be maintained by upgrading the backup manual system capability via the ILM. A safety budget analysis was used to establish the reliability requirements for the ILM. These requirements were used as constraints in devising the fault detection scheme. Covariance propagation methods were used with a linearized system model to establish the time required to correct manually perturbed states due to the fault. Time-to-detect and time-to-correct requirements were combined to devise appropriate altitudes and strategies for fault recovery.

Karmarker, J. S.↗

A Comparison Between Orion Automated and Space Shuttle Rendezvous Techniques

The Orion spacecraft will replace the space shuttle and will be the first human spacecraft since the Apollo program to leave low earth orbit. This vehicle will serve as the cornerstone of a complete space transportation system with a myriad of mission requirements necessitating rendezvous to multiple vehicles in earth orbit, around the moon and eventually beyond . These goals will require a complex and robust vehicle that is, significantly different from both the space shuttle and the command module of the Apollo program. Historically, orbit operations have been accomplished with heavy reliance on ground support and manual crew reconfiguration and monitoring. One major difference with Orion is that automation will be incorporated as a key element of the man-vehicle system. The automated system will consist of software devoted to transitioning between events based on a master timeline. This effectively adds a layer of high level sequencing that moves control of the vehicle from one phase to the next. This type of automated control is not entirely new to spacecraft since the shuttle uses a version of this during ascent and entry operations. During shuttle orbit operations however many of the software modes and hardware switches must be manually configured through the use of printed procedures and instructions voiced from the ground. The goal of the automation scheme on Orion is to extend high level automation to all flight phases. The move towards automation represents a large shift from current space shuttle operations, and so these new systems will be adopted gradually via various safeguards. These include features such as authority-to-proceed, manual down modes, and functional inhibits. This paper describes the contrast between the manual and ground approach of the space shuttle and the proposed automation of the Orion vehicle. I will introduce typical orbit operations that are common to all rendezvous missions and go on to describe the current Orion automation architecture and contrast it with shuttle rendezvous techniques and circumstances. The shuttle rendezvous profile is timed to take approximately 3 days from orbit insertion to docking at the International Space Station (ISS). This process can be divided into 3 phases: far-field, mid-field and proximity operations. The far-field stage is characterized as the most quiescent phase. The spacecraft is usually too far to navigate using relative sensors and uses the Inertial Measurement Units (IMU s) to numerically solve for its position. The maneuvers are infrequent, roughly twice per day, and are larger than other burns in the profile. The shuttle uses this opportunity to take extensive ground based radar updates and keep high fidelity orbit states on the ground. This state is then periodically uplinked to the shuttle computers. The targeting solutions for burn maneuvers are also computed on the ground and uplinked. During the burn the crew is responsible for setting the shuttle attitude and configuring the propulsion system for ignition. Again this entire process is manually driven by both crew and ground activity. The only automatic processes that occur are associated with the real-time execution of the burn. The Orion automated functionality will seek to relieve the workload of both the crew and ground during this phase

Ruiz, Jose O,↗

Developing Advanced Support Technologies for Planetary Exploration Missions

The United States Vision for Space Exploration calls for sending robots and humans to explore the Earth s moon, the planet Mars, and beyond. The National Aeronautics and Space Administration (NASA) is developing a set of design reference missions that will provide further detail to these plans. Lunar missions are expected to provide a stepping stone, through operational research and evaluation, in developing the knowledge base necessary to send crews on long duration missions to Mars and other distant destinations. The NASA Exploration Systems Directorate (ExSD), in its program of bioastronautics research, manages the development of technologies that maintain human life, health, and performance in space. Using a systems engineering process and risk management methods, ExSD s Human Support Systems (HSS) Program selects and performs research and technology development in several critical areas and transfers the results of its efforts to NASA exploration mission/systems development programs in the form of developed technologies and new knowledge about the capabilities and constraints of systems required to support human existence beyond Low Earth Orbit. HSS efforts include the areas of advanced environmental monitoring and control, extravehicular activity, food technologies, life support systems, space human factors engineering, and systems integration of all these elements. The HSS Program provides a structured set of deliverable products to meet the needs of exploration programs. these products reduce the gaps that exist in our knowledge of and capabilities for human support for long duration, remote space missions. They also reduce the performance gap between the efficiency of current space systems and the greater efficiency that must be achieved to make human planetary exploration missions economically and logistically feasible. In conducting this research and technology development program, it is necessary for HSS technologists and program managers to develop a common currency for decision making and the allocation of funding. A high level assessment is made of both the knowledge gaps and the system performance gaps across the program s technical project portfolio. This allows decision making that assures proper emphasis areas and provides a key measure of annual technological progress, as exploration mission plans continue to mature.

Berdich, Debra P.↗

Developing Advanced Human Support Technologies for Planetary Exploration Missions

The United States Vision for Space Exploration calls for sending robots and humans to explore the Earth's moon, the planet Mars, and beyond. The National Aeronautics and Space Administration (NASA) is developing a set of design reference missions that will provide further detail to these plans. Lunar missions are expected to provide a stepping stone, through operational research and evaluation, in developing the knowledge base necessary to send crews on long duration missions to Mars and other distant destinations. The NASA Exploration Systems Directorate (ExSD), in its program of bioastronautics research, manages the development of technologies that maintain human life, health, and performance in space. Using a system engineering process and risk management methods, ExSD's Human Support Systems (HSS) Program selects and performs research and technology development in several critical areas and transfers the results of its efforts to NASA exploration mission/systems development programs in the form of developed technologies and new knowledge about the capabilities and constraints of systems required to support human existence beyond Low Earth Orbit. HSS efforts include the areas of advanced environmental monitoring and control, extravehicular activity, food technologies, life support systems, space human factors engineering, and systems integration of all these elements. The HSS Program provides a structured set of deliverable products to meet the needs of exploration programs. These products reduce the gaps that exist in our knowledge of and capabilities for human support for long duration, remote space missions. They also reduce the performance gap between the efficiency of current space systems and the greater efficiency that must be achieved to make human planetary exploration missions economically and logistically feasible. In conducting this research and technology development program, it is necessary for HSS technologists and program managers to develop a common currency for decision making and the allocation of funding. A high level assessment is made of both the knowledge gaps and the system performance gaps across the program s technical project portfolio. This allows decision making that assures proper emphasis areas and provides a key measure of annual technological progress, as exploration mission plans continue to mature.

Berdich, Debra P.↗

Onboard Sensor Data Qualification in Human-Rated Launch Vehicles

The avionics system software for human-rated launch vehicles requires an implementation approach that is robust to failures, especially the failure of sensors used to monitor vehicle conditions that might result in an abort determination. Sensor measurements provide the basis for operational decisions on human-rated launch vehicles. This data is often used to assess the health of system or subsystem components, to identify failures, and to take corrective action. An incorrect conclusion and/or response may result if the sensor itself provides faulty data, or if the data provided by the sensor has been corrupted. Operational decisions based on faulty sensor data have the potential to be catastrophic, resulting in loss of mission or loss of crew. To prevent these later situations from occurring, a Modular Architecture and Generalized Methodology for Sensor Data Qualification in Human-rated Launch Vehicles has been developed. Sensor Data Qualification (SDQ) is a set of algorithms that can be implemented in onboard flight software, and can be used to qualify data obtained from flight-critical sensors prior to the data being used by other flight software algorithms. Qualified data has been analyzed by SDQ and is determined to be a true representation of the sensed system state; that is, the sensor data is determined not to be corrupted by sensor faults or signal transmission faults. Sensor data can become corrupted by faults at any point in the signal path between the sensor and the flight computer. Qualifying the sensor data has the benefit of ensuring that erroneous data is identified and flagged before otherwise being used for operational decisions, thus increasing confidence in the response of the other flight software processes using the qualified data, and decreasing the probability of false alarms or missed detections.

Wong, Edmond↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗

Limiting Future Collision Risk to Spacecraft: An Assessment of NASA's Meteoroid and Orbital Debris Programs

Over the past 50 years, various NASA communities have contributed significantly to maturing NASA s meteoroid and orbital debris (MMOD)1 programs to their current state. As a result of these community efforts, and to NASA s credit, NASA s MMOD programs and models are now widely used and respected by the providers and users of both government and commercial satellites, nationally as well as internationally. Satellites have been redesigned to protect critical components from MMOD damage by moving critical components from exterior surfaces to deep inside a satellite s structure. Orbits are monitored and altered to minimize the risk of collision with tracked orbital debris. MMOD shielding added to the International Space Station (ISS) protects critical components and astronauts from potentially catastrophic damage that might result from smaller, untracked debris and meteoroid impacts. The space shuttle, as it orbited Earth, and whether docked to the ISS or not, was optimally oriented to protect its fragile thermal protection and thermal radiation systems from MMOD damage. In addition, astronauts inspected its thermal protection system for MMOD damage before the shuttle reentered Earth s atmosphere; Orion, NASA s capsule to carry astronauts to low Earth orbit, includes designs to mitigate the threat of MMOD damage and provide increased safety to the crew. When a handful of reasonable assumptions are used in NASA s MMOD models, scenarios are uncovered that conclude that the current orbital debris environment has already reached a "tipping point." That is, the amount of debris - in terms of the population of large debris objects, as well as overall mass of debris in orbit - currently in orbit has reached a threshold where it will continually collide with itself, further increasing the population of orbital debris. This increase will lead to corresponding increases in spacecraft failures, which will only create more feedback into the system, increasing the debris population growth rate. The increase thus far has been most rapid in low Earth orbit (LEO), with geosynchronous Earth orbits (GEOs) potentially suffering the same fate, but over a much longer time period. The exact timing and pace of this exponential growth are uncertain, but the serious implications of such a scenario require careful attention because of the strategic importance of U.S. space operations. The Office of Science and Technology Policy and the Office of Management and Budget contracted with the National Research Council for a study to perform three tasks: review NASA s MMOD programs and efforts, recommend in which of those NASA should increase or decrease its effort or change focus, and determine whether NASA should pursue work in any new MMOD areas. The official letter requesting the study and the full statement of task for the Committee for the Assessment of NASA s Orbital Debris Programs are in Appendixes A and B, respectively.

Source record↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

Application of Smart Solid State Sensor Technology in Aerospace Applications

Aerospace applications require a range of chemical sensing technologies to monitor conditions in both space vehicles and aircraft operations. One example is the monitoring of oxygen. For example, monitoring of ambient oxygen (O2) levels is critical to ensuring the health, safety, and performance of humans living and working in space. Oxygen sensors can also be incorporated in detection systems to determine if hazardous leaks are occurring in space propulsion systems and storage facilities. In aeronautic applications, O2 detection has been investigated for fuel tank monitoring. However, as noted elsewhere, O2 is not the only species of interest in aerospace applications with a wide range of species of interest being relevant to understand an environmental or vehicle condition. These include combustion products such as CO, HF, HCN, and HCl, which are related to both the presence of a fire and monitoring of post-fire clean-up operations. This paper discusses the development of an electrochemical cell platform based on a polymer electrolyte, NAFION, and a three-electrode configuration. The approach has been to mature this basic platform for a range of applications and to test this system, combined with "Lick and Stick" electronics, for its viability to monitor an environment related to astronaut crew health and safety applications with an understanding that a broad range of applications can be addressed with a core technology.

Hunter, Gary W.↗

Phase VI Glove Durability Testing

The current state-of-the-art space suit gloves, the Phase VI gloves, have an operational life of 25 - 8 hour Extravehicular Activities (EVAs) in a clean, controlled ISS environment. Future planetary outpost missions create the need for space suit gloves which can endure up to 90 - 8 hour traditional EVAs or 576 - 45 minute suit port-based EVAs in a dirty, uncontrolled planetary environment. Prior to developing improved space suit gloves for use in planetary environments, it is necessary to understand how the current state-of-the-art performs in these environments. The Phase VI glove operational life has traditionally been certified through cycle testing consisting of ISS-based tasks in a clean environment, and glove durability while performing planetary EVA tasks in a dirty environment has not previously been characterized. Testing was performed in the spring of 2010 by the NASA Johnson Space Center Crew and Thermal Systems Division to characterize the durability of the Phase VI Glove and identify areas of the glove design which need improvement to meet the requirements of future NASA missions. Lunar simulant was used in this test to help replicate the dirty lunar environment, and generic planetary surface EVA tasks were performed during testing. A total of 50 manned, pressurized test sessions were completed in the Extravehicular Mobility Unit (EMU) using one pair of Phase VI gloves as the test article. The 50 test sessions were designed to mimic the total amount of pressurized cycling the gloves would experience over a 6 month planetary outpost mission. The gloves were inspected at periodic intervals throughout testing, to assess their condition at various stages in the test and to monitor the gloves for failures. Additionally, motion capture and force data were collected during 18 of the 50 test sessions to assess the accuracy of the cycle model predictions used in testing and to feed into the development of improved cycle model tables. This paper provides a detailed description of the test hardware and methodology, shares the results of the testing, and provides recommendations for future work.

Mitchell, Kathryn C.↗

Phase VI Glove Durability Testing

The current state-of-the-art space suit gloves, the Phase VI gloves, have an operational life of 25 -- 8 hour Extravehicular Activities (EVAs) in a dust free, manufactured microgravity EVA environment. Future planetary outpost missions create the need for space suit gloves which can endure up to 90 -- 8 hour traditional EVAs or 576 -- 45 minute suit port-based EVAs in a dirty, uncontrolled planetary environment. Prior to developing improved space suit gloves for use in planetary environments, it is necessary to understand how the current state-of-the-art performs in these environments. The Phase VI glove operational life has traditionally been certified through cycle testing consisting of International Space Station (ISS)-based EVA tasks in a clean environment, and glove durability while performing planetary EVA tasks in a dirty environment has not previously been characterized. Testing was performed in the spring of 2010 by the NASA Johnson Space Center (JSC) Crew and Thermal Systems Division (CTSD) to characterize the durability of the Phase VI Glove and identify areas of the glove design which need improvement to meet the requirements of future NASA missions. Lunar simulant was used in this test to help replicate the dirty lunar environment, and generic planetary surface EVA tasks were performed during testing. A total of 50 manned, pressurized test sessions were completed in the Extravehicular Mobility Unit (EMU) using one pair of Phase VI gloves as the test article. The 50 test sessions were designed to mimic the total amount of pressurized cycling the gloves would experience over a 6 month planetary outpost mission. The gloves were inspected periodically throughout testing, to assess their condition at various stages in the test and to monitor the gloves for failures. Additionally, motion capture and force data were collected during 18 of the 50 test sessions to assess the accuracy of the cycle model predictions used in testing and to feed into the development of improved cycle model tables. This paper provides a detailed description of the test hardware and methodology, shares the results of the testing, and provides recommendations for future work.

Mitchell, Kathryn↗

Desert Research and Technology Studies (D-RATS) 2022 Quicklook Report

This report summarizes the Desert Research and Technology Studies (D-RATS) 2022 analog tests. BACKGROUND - Artemis Challenges – NASA’s concept of operations (ConOps) for the Artemis mission architecture brings new challenges for human exploration of the lunar surface, including: (1) Low-angle, natural lighting at lunar poles; and (2) Exploration sites that challenge communication with Earth. - International Partner Involvement – NASA is working with the Japan Aerospace Exploration Agency (JAXA) to scope mission & functional requirements for an Artemis Pressurized Rover (PR), which JAXA may provide. - Charter – HQ Exploration Systems Development Mission Directorate (ESDMD) Moon to Mars Architecture Development Office (M2MADO) Strategy and Architectures (SA) chartered the Human-in-the-Loop (HITL) test team to investigate Artemis architectural questions related to pressurized rover ConOps. - Rationale – to inform the NASA/JAXA pressurized rover study-agreement. PLAN - Objectives – Analog tests conducted in October 2022 by the D-RATS team addressed three high-level objectives: 1. Investigate pressurized rover (PR) ConOps and capabilities for Artemis exploration 2. Integrate with JAXA engineers & astronauts and incorporate JAXA PR design elements into testing. 3. Re-establish analog field-testing skills & capabilities with rovers to investigate Artemis architecture ConOps. - Secondary Objectives – Work with other groups to leverage D-RATS field test for additional objectives. 4. Work with the Public Affairs Office (PAO) to perform D-RATS public outreach activities. 5. Coordinate with the Human Physiology Performance Protection & Operations (H-3PO) team to facilitate in-field evaluation of human health and performance (HHP) objectives. 6. Share D-RATS field-site and assets with Lunar LTE Studies (Lunar LiTES) team, to aid their study of the use of 4G/LTE communication protocols and devices for astronauts and robotic nodes on the lunar surface. - Team – Fully integrated test team comprised of members from 5 NASA centers, JAXA, and the United States Geological Survey (USGS) - Location – Black Point Lava Flow, ~40 miles north of Flagstaff, AZ HIGH-LEVEL OBJECTIVES ACCOMPLISHED - Investigated Pressurized Rover ConOps & Capabilities for Artemis Exploration (Objective 1) - Completed testing with 4 crew pairs, each spending 3 days and 2 nights in the rover conducting Artemis PR dayin-the-life activities (2 JAXA astronauts, 2 JAXA engineers, 1 NASA astronaut, 3 NASA engineers). - Collected detailed objective & subjective data supporting 10 strategic questions related to Artemis PR operations. - Field geologists present in field observed rover operations & EVAs. - Science team in Houston MCC communicated directly with crew. - Demonstrated crew-led and MCC-led PR teleoperation use cases during EVAs. - Integrated with JAXA Engineers & Astronauts and Incorporated JAXA PR Design Elements into Testing (Objective 2) - NASA & JAXA engineers, flight controllers, scientists, roboticists, and astronauts directly participated in and/or observed testing both in field and in MCC-Houston. - Incorporated JAXA PR design elements into both integrated and standalone testing at JSC and in the field. - Re-established Analog Field-Testing Skills & Capabilities with Rovers to Investigate Artemis Architecture ConOps (Objective 3) - Multiple teams successfully worked to establish and manage field-test base camp, monitor and maintain the rover, and plan and execute 2 weeks of consecutive field-testing with little to no breaks between crews. TEST OUTCOMES - Results will inform Artemis architecture ConOps & capabilities related to pressurized rover operations (see sections 2 for more details) - Summary and team detailed reports will be posted on the D-RATS 2022 wiki

Analog↗