Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operator learning”

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 541 records · Page 30

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗

Space Mechanisms Lessons Learned and Accelerated Testing Studies

A number of mechanism (mechanical moving component) failures and anomalies have recently occurred on satellites. In addition, more demanding operating and life requirements have caused mechanism failures or anomalies to occur even before some satellites were launched (e.g., during the qualification testing of GOES-NEXT, CERES, and the Space Station Freedom Beta Joint Gimbal). For these reasons, it is imperative to determine which mechanisms worked in the past and which have failed so that the best selection of mechanically moving components can be made for future satellites. It is also important to know where the problem areas are so that timely decisions can be made on the initiation of research to develop future needed technology. To chronicle the life and performance characteristics of mechanisms operating in a space environment, a Space Mechanisms Lessons Learned Study was conducted. The work was conducted by the NASA Lewis Research Center and by Mechanical Technologies Inc. (MTI) under contract NAS3-27086. The expectation of the study was to capture and retrieve information relating to the life and performance of mechanisms operating in the space environment to determine what components had operated successfully and what components had produced anomalies.

Fusaro, Robert L.↗

NASA Conjunction Assessment Risk Analysis (CARA) Ground Systems, Software and Operations Infrastructure Cloud Implementation

The growing number of large-scale constellations and the improvements made in the tracking and detection of resident space objects have contributed to the increase of satellite conjunction events. As a result of the increase of objects in Earth orbit, the timeline for risk analysis computations for satellite collision avoidance is more urgent when conjunctions occur. It is imperative NASA maintains a space environment safety functionality for the agency that allows CARA remote access to the ground system while maintaining redundancy. CARA’s On-premises (On-prem) ground system would no longer be able to meet these access and redundancy requirements, hence the investigation and eventual implementation of a Cloud-based ground station infrastructure as a viable solution. This paper will provide an overview of the principal parts of the Conjunction Assessment (CA) risk analysis process used at CARA, summarize the key drivers towards the Cloud solution, and share key lessons learned that are significant for any operational entity considering a cloud solution for real-time satellite operations to ensure a sustainable space traffic environment for all.

Sustainability↗

Mars 2020 Entry, Descent, and Landing System Software Implementation

On February 18th, 2021, the Mars 2020 project's Perseverance Rover successfully touched down on the Martian surface after nearly eight years of development. The Mars 2020 Entry, Descent, and Landing (EDL) System largely leveraged heritage from the Mars Science Laboratory (MSL) EDL System while employing targeted technological advancements. The landing process is autonomously directed by a software behavior implemented in the rover's primary flight computer called the EDL Timeline that assumes control of the vehicle six days before atmospheric entry. This paper first walks through the basics of the EDL Timeline mechanics and how the behavior is designed to account for internal system variations and environmental unknowns. It then summarizes the interactions between the EDL timeline and other high-level system behaviors like spacecraft mode transitions and system fault protection, focusing on the complications that arise when passing spacecraft control between executive functions. Although the MSL-inherited EDL System is reliable and capable, targeted updates and a thorough verification and validation program were required for Mars 2020. This paper discusses changes made to close vulnerabilities discovered during both MSL and Mars 2020 development cycles, landing system capability enhancements that were enabling for Mars 2020's mission, and how these updates were integrated with the heritage system. It then describes how both analysis and testing campaigns were utilized to verify and validate all aspects of EDL and system behaviors that run during the six days before landing, as well as the operational workarounds that were needed to address problems found during the development and commissioning process. Finally, this paper imparts lessons learned from Mars 2020 EDL development, implementation, and operations, emphasizing how systems designed to conduct time-critical mission events with low margin of error can be improved in the future.

Stehura, Aaron↗

Mars 2020 Entry, Descent, and Landing Software Implementation

On February 18th, 2021, the Mars 2020 project's Perseverance Rover successfully touched down on the Martian surface after nearly eight years of development. The Mars 2020 Entry, Descent, and Landing (EDL) System largely leveraged heritage from the Mars Science Laboratory (MSL) EDL System while employing targeted technological advancements. The landing process is autonomously directed by a software behavior implemented in the rover's primary flight computer called the EDL Timeline that assumes control of the vehicle six days before atmospheric entry. In addition to performing the critical function of landing the rover on the Martian surface, the EDL timeline behavior must co-exist in a non-partitioned software and system environment with other high-level functions that accomplish the goals for the rest of the mission. Due to the criticality of EDL, the potential for loss of mission, and a need for complete system autonomy, the standard for how the EDL Timeline interacts with other functions in the system is highly constrained. This paper first walks through the basics of the EDL Timeline mechanics and how the behavior is designed to account for internal system variations and environmental unknowns. It then summarizes the interactions between the EDL timeline and other high-level system behaviors like spacecraft mode transitions and system fault protection, focusing on the complications that arise when passing spacecraft control between executive functions. Although the MSL-inherited EDL System is reliable and capable, targeted updates and a thorough verification and validation program were required for Mars 2020. This paper discusses changes made to close vulnerabilities discovered during both MSL and Mars 2020 development cycles, landing system capability enhancements that were enabling for Mars 2020's mission, and how these updates were integrated with the heritage system. It then describes how both analysis and testing campaigns were utilized to verify and validate all aspects of EDL and system behaviors that run during the six days before landing, as well as the operational workarounds that were needed to address problems found during the development and commissioning process. Finally, this paper imparts lessons learned from Mars 2020 EDL development, implementation, and operations, emphasizing how systems designed to conduct time-critical mission events with low margin of error can be improved in the future.

Stehura, Aaron↗

Parameter learning for performance adaptation

A parameter learning method is introduced and used to broaden the region of operability of the adaptive control system of a flexible space antenna. The learning system guides the selection of control parameters in a process leading to optimal system performance. A grid search procedure is used to estimate an initial set of parameter values. The optimization search procedure uses a variation of the Hooke and Jeeves multidimensional search algorithm. The method is applicable to any system where performance depends on a number of adjustable parameters. A mathematical model is not necessary, as the learning system can be used whenever the performance can be measured via simulation or experiment. The results of two experiments, the transient regulation and the command following experiment, are presented.

Peek, Mark D.↗

Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

Williams, David E.↗

Lessons Learned from the Node 1 Temperature and Humidity Control Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Temperature and Humidity Control (THC) subsystem and it will document some of the lessons that have been learned to date for this subsystem and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs. 1

Williams, David E.↗

Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

Williams, David E.↗

The Evolution of Exercise Hardware on ISS: Past, Present, and Future

During 16 years in low-Earth orbit, the suite of exercise hardware aboard the International Space Station (ISS) has matured significantly. Today, the countermeasure system supports an array of physical-training protocols and serves as an extensive research platform. Future hardware designs are required to have smaller operational envelopes and must also mitigate known physiologic issues observed in long-duration spaceflight. Taking lessons learned from the long history of space exercise will be important to successful development and implementation of future, compact exercise hardware. The evolution of exercise hardware as deployed on the ISS has implications for future exercise hardware and operations. Key lessons learned from the early days of ISS have helped to: 1. Enhance hardware performance (increased speed and loads). 2. Mature software interfaces. 3. Compare inflight exercise workloads to pre-, in-, and post-flight musculoskeletal and aerobic conditions. 4. Improve exercise comfort. 5. Develop complimentary hardware for research and operations. Current ISS exercise hardware includes both custom and commercial-off-the-shelf (COTS) hardware. Benefits and challenges to this approach have prepared engineering teams to take a hybrid approach when designing and implementing future exercise hardware. Significant effort has gone into consideration of hardware instrumentation and wearable devices that provide important data to monitor crew health and performance.

Buxton, R. E.↗

Reusable Autonomy

Currently, spacecraft ground systems have a well defined and somewhat standard architecture and operations concept. Based on domain analysis studies of various control centers conducted over the years it is clear that ground systems have core capabilities and functionality that are common across all ground systems. This observation alone supports the realization of reuse. Additionally, spacecraft ground systems are increasing in their ability to do things autonomously. They are being engineered using advanced expert systems technology to provide automated support for operators. A clearer understanding of the possible roles of agent technology is advancing the prospects of greater autonomy for these systems. Many of their functional and management tasks are or could be supported by applied agent technology, the dynamics of the ground system's infrastructure could be monitored by agents, there are intelligent agent-based approaches to user-interfaces, etc. The premise of this paper is that the concepts associated with software reuse, applicable in consideration of classically-engineered ground systems, can be updated to address their application in highly agent-based realizations of future ground systems. As a somewhat simplified example consider the following situation, involving human agents in a ground system context. Let Group A of controllers be working on Mission X. They are responsible for the command, control and health and safety of the Mission X spacecraft. Let us suppose that mission X successfully completes it mission and is turned off. Group A could be dispersed or perhaps move to another Mission Y. In this case there would be reuse of the human agents from Mission X to Mission Y. The Group A agents perform their well-understood functions in a somewhat but related context. There will be a learning or familiarization process that the group A agents go through to make the new context, determined by the new Mission Y, understood. This simplified scenario highlights some of the major issues that need to be addressed when considering the situation where Group A is composed of software-based agents (not their human counterparts) and they migrate from one mission support system to another. This paper will address: - definition of an agent architecture appropriate to support reuse; - identification of non-mission-specific agent capabilities required; - appropriate knowledge representation schemes for mission-specific knowledge; - agent interface with mission-specific knowledge (a type of Learning); development of a fully-operational group of cooperative software agents for ground system support; architecture and operation of a repository of reusable agents that could be the source of intelligent components for realizing an autonomous (or nearly autonomous) agent-based ground system, and an agent-based approach to repository management and operation (an intelligent interface for human use of the repository in a ground-system development activity).

Truszkowski, Walt↗

Conceptual designs study for a Personnel Launch System (PLS)

A series of conceptual designs for a manned, Earth to Low Earth Orbit transportation system was developed. Non-winged, low L/D vehicle shapes are discussed. System and subsystem trades emphasized safety, operability, and affordability using near-term technology. The resultant conceptual design includes lessons learned from commercial aviation that result in a safe, routine, operationally efficient system. The primary mission for this Personnel Launch System (PLS) would be crew rotation to the SSF; other missions, including satellite servicing, orbital sortie, and space rescue were also explored.

Wetzel, E. D.↗

MODIS On-Orbit Performance and Lessons Learned

MODIS is a key instrument for the NASA's Earth Observing System (EOS) and has successfully operated for more than 11 and 9 years, respectively, on-board the Terra and Aqua spacecraft. MODIS collects data in 36 spectral bands, covering wavelengths from visible (VIS) to long-wave infrared (LWIR). To date, both Terra and Aqua MODIS have produced an unprecedented amount of data products and significantly contributed to the earth remote sensing studies and applications. MODIS was developed with stringent calibration requirements and was, consequently, designed and built with a set of on-board calibrators (OBC), which include a solar diffuser (SD), a solar diffuser stability monitor (SDSM), a blackbody (BB), and a spectroradiometric calibration assembly (SRCA). This presentation briefly reviews MODIS instrument operation and various calibration and characterization activities, It demonstrates both the instrument and the OBC on-orbit performance and discusses lessons learned, particularly focusing on on-orbit changes in sensor responses, optics degradation, and major challenging issues. As expected, Terra and Aqua MODIS on-orbit performance and lessons learned will continue to benefit the operation and calibration of future sensors, such as NPP/JPSS VIIRS and GOES-R ABI.

Xiong, Xiaoxiong↗

Early Artemis Surface Navigation: Challenges, Approaches, and Opportunities

The early Artemis missions represent the return of humanity to the surface of the Moon and provide opportunities for meeting early science and exploration goals. Position, Navigation, and Timing (PNT) capabilities are a fundamental element and inform operational design, flight rules, and the ability to meet these. This paper provides an overview of the needs, potential implementations, challenges, and concepts of operations in the initial human surface missions, Artemis III and IV. These early excursions are a crucial learning opportunity to gain more experience in the actual operational environment for Artemis V and beyond where exploration objectives and complexity increases. As part of the study, the team defined a threshold performance navigation requirement (including position and orientation) to meet crew safe return and assessed a breadth of navigation approaches that could be deployed to augment the crew’s baseline navigation capability. Data was collected in terms of size, mass, power, operational constraints, environment constraints, interface, and performance to define the technical metrics. Given these, the trade team conducted polling among the various Artemis Campaign elements to capture preference, integration challenges, and operational impacts. These were used to develop weightings and inform a ranked order of solutions across each of the early missions. The results of the study recommended augmenting the initial orientation capability with additional navigation sensors to provide coarse position and heading information to the crew to enable a safe contingency walk-back when out of video range. The team identified opportunities for embedding this hardware in future scenarios to provide an integrated solution. With the deployment of the LunaNet’s Lunar Augmented Navigation System, the crew will be able to maintain accurate real-time navigation knowledge with minimal physical impacts. Discussion of future testing and continued analysis is included in this paper. These forward plans and long-term architecture systems will enable a powerful navigation approach for orbiting and surface users, enabling a high level of scientific return and crew safety.

Evan Anzalone↗

Early Artemis Surface Navigation: Challenges, Approaches, and Opportunities

The early Artemis missions represent the return of humanity to the surface of the Moon and provide opportunities for meeting early science and exploration goals. Position, Navigation, and Timing (PNT) capabilities are a fundamental element and inform operational design, flight rules, and the ability to meet these. This paper provides an overview of the needs, potential implementations, challenges, and concepts of operations in the initial human surface missions, Artemis III and IV. These early excursions are a crucial learning opportunity to gain more experience in the actual operational environment for Artemis V and beyond where exploration objectives and complexity increases. As part of the study, the team defined a threshold performance navigation requirement (including position and orientation) to meet crew safe return and assessed a breadth of navigation approaches that could be deployed to augment the crew’s baseline navigation capability. Data was collected in terms of size, mass, power, operational constraints, environment constraints, interface, and performance to define the technical metrics. Given these, the trade team conducted polling among the various Artemis Campaign elements to capture preference, integration challenges, and operational impacts. These were used to develop weightings and inform a ranked order of solutions across each of the early missions. The results of the study recommended augmenting the initial orientation capability with additional navigation sensors to provide coarse position and heading information to the crew to enable a safe contingency walk-back when out of video range. The team identified opportunities for embedding this hardware in future scenarios to provide an integrated solution. With the deployment of the LunaNet’s Lunar Augmented Navigation System, the crew will be able to maintain accurate real-time navigation knowledge with minimal physical impacts. Discussion of future testing and continued analysis is included in this paper. These forward plans and long-term architecture systems will enable a powerful navigation approach for orbiting and surface users, enabling a high level of scientific return and crew safety.

Evan Anzalone↗

Crew Factors in Flight Operations X: Alertness Management in Flight Operations

In response to a 1980 congressional request, NASA Ames Research Center initiated a Fatigue/Jet Lag Program to examine fatigue, sleep loss, and circadian disruption in aviation. Research has examined fatigue in a variety of flight environments using a range of measures (from self-report to performance to physiological). In 1991, the program evolved into the Fatigue Countermeasures Program, emphasizing the development and evaluation of strategies to maintain alertness and performance in operational settings. Over the years, the Federal Aviation Administration (FAA) has become a collaborative partner in support of fatigue research and other Program activities. From the inception of the Program, a principal goal was to return the information learned from research and other Program activities to the operational community. The objectives of this Education and Training Module are to explain what has been learned about the physiological mechanisms that underlie fatigue, demonstrate the application of this information in flight operations, and offer some specific fatigue counter-measure recommendations. It is intended for all segments of the aeronautics industry, including pilots, flight attendants, managers, schedulers, safety and policy personnel, maintenance crews, and others involved in an operational environment that challenges human physiological capabilities because of fatigue, sleep loss, and circadian disruption.

Rosekind, Mark R.↗

Crew Factors in Flight Operations X: Alertness Management in Flight Operations

In response to a 1980 congressional request, NASA Ames Research Center initiated a Fatigue/Jet Lag Program to examine fatigue, sleep loss, and circadian disruption in aviation. Research has examined fatigue in a variety of flight environments using a range of measures (from self-report to performance to physiological). In 1991, the program evolved into the Fatigue Countermeasures Program, emphasizing the development and evaluation of strategies to maintain alertness and performance in operational settings. Over the years, the Federal Aviation Administration (FAA) has become a collaborative partner in support of fatigue research and other Program activities. From the inception of the Program, a principal goal was to return the information learned from research and other Program activities to the operational community. The objectives of this Education and Training Module are to explain what has been learned about the physiological mechanisms that underlie fatigue, demonstrate the application of this information in flight operations, and offer some specific fatigue countermeasure recommendations. It is intended for all segments of the aeronautics industry, including pilots, flight attendants, managers, schedulers, safety and policy personnel, maintenance crews, and others involved in an operational environment that challenges human physiological capabilities because of fatigue, sleep loss, and circadian disruption.

Rosekind, Mark R.↗