Results for “Level of Automation” — Page 9

NASA NTRS2013

Advanced Caution and Warning System, Final Report - 2011

The work described in this report is a continuation of the ACAWS work funded in fiscal year (FY) 2010 under the Exploration Technology Development Program (ETDP), Integrated Systems Health Management (ISHM) project. In FY 2010, we developed requirements for an ACAWS system and vetted the requirements with potential users via a concept demonstration system. In FY 2011, we developed a working prototype of aspects of that concept, with placeholders for technologies to be fully developed in future phases of the project. The objective is to develop general capability to assist operators with system health monitoring and failure diagnosis. Moreover, ACAWS was integrated with the Discrete Controls (DC) task of the Autonomous Systems and Avionics (ASA) project. The primary objective of DC is to demonstrate an electronic and interactive procedure display environment and multiple levels of automation (automatic execution by computer, execution by computer if the operator consents, and manual execution by the operator).

Spirkovska, Lilly↗

NASA NTRS2013

Creating the Deep Space Environment for Testing the James Webb Space Telescope at NASA Johnson Space Center's Chamber A

Chamber A is the largest thermal vacuum chamber at the Johnson Space Center and is one of the largest space environment chambers in the world. The chamber is 19.8 m (65 ft.) in diameter and 36.6 m (120 ft.) tall and is equipped with cryogenic liquid nitrogen panels (shrouds) and gaseous helium shrouds to create a simulated space environment. It was originally designed and built in the mid 1960 s to test the Apollo Command and Service Module and several manned tests were conducted on that spacecraft, contributing to the success of the program. The chamber has been used since that time to test spacecraft active thermal control systems, Shuttle DTO, DOD, and ESA hardware in simulated Low Earth Orbit (LEO) conditions. NASA is now moving from LEO towards exploration of locations with environments approaching those of deep space. Therefore, Chamber A has undergone major modifications to enable it to simulate these deeper space environments. Environmental requirements were driven, and modifications were funded by the James Webb Space Telescope program, and this telescope, which will orbit Solar/Earth L2, will be the first test article to benefit from the chamber s new capabilities. To accommodate JWST, the Chamber A high vacuum system has been modernized, additional LN2 shrouds have been installed, the liquid nitrogen system has been modified to minimize dependency on electrical power and increase its reliability, a new helium shroud/refrigeration system has been installed to create a colder more stable and uniform heat sink, and the controls have been updated to increase the level of automation and improve operator interfaces. Testing of these major modifications was conducted in August of 2012 and this initial test was very successful, with all major systems exceeding their performance requirements. This paper will outline the changes in overall environmental requirements, discuss the technical design data that was used in the decisions leading to the extensive modifications, and describe the new capabilities of the chamber.

Homan, Jonathan L.↗

NASA NTRS2013

Software for Generating Troposphere Corrections for InSAR Using GPS and Weather Model Data

Atmospheric errors due to the troposphere are a limiting error source for spaceborne interferometric synthetic aperture radar (InSAR) imaging. This software generates tropospheric delay maps that can be used to correct atmospheric artifacts in InSAR data. The software automatically acquires all needed GPS (Global Positioning System), weather, and Digital Elevation Map data, and generates a tropospheric correction map using a novel algorithm for combining GPS and weather information while accounting for terrain. Existing JPL software was prototypical in nature, required a MATLAB license, required additional steps to acquire and ingest needed GPS and weather data, and did not account for topography in interpolation. Previous software did not achieve a level of automation suitable for integration in a Web portal. This software overcomes these issues. GPS estimates of tropospheric delay are a source of corrections that can be used to form correction maps to be applied to InSAR data, but the spacing of GPS stations is insufficient to remove short-wavelength tropospheric artifacts. This software combines interpolated GPS delay with weather model precipitable water vapor (PWV) and a digital elevation model to account for terrain, increasing the spatial resolution of the tropospheric correction maps and thus removing short wavelength tropospheric artifacts to a greater extent. It will be integrated into a Web portal request system, allowing use in a future L-band SAR Earth radar mission data system. This will be a significant contribution to its technology readiness, building on existing investments in in situ space geodetic networks, and improving timeliness, quality, and science value of the collected data

Moore, Angelyn W.↗

NASA NTRS2013

Controller Strategies for Automation Tool Use under Varying Levels of Trajectory Prediction Uncertainty

A human-in-the-loop simulation was conducted to examine the effects of varying levels of trajectory prediction uncertainty on air traffic controller workload and performance, as well as how strategies and the use of decision support tools change in response. This paper focuses on the strategies employed by two controllers from separate teams who worked in parallel but independently under identical conditions (airspace, arrival traffic, tools) with the goal of ensuring schedule conformance and safe separation for a dense arrival flow in en route airspace. Despite differences in strategy and methods, both controllers achieved high levels of schedule conformance and safe separation. Overall, results show that trajectory uncertainties introduced by wind and aircraft performance prediction errors do not affect the controllers' ability to manage traffic. Controller strategies were fairly robust to changes in error, though strategies were affected by the amount of delay to absorb (scheduled time of arrival minus estimated time of arrival). Using the results and observations, this paper proposes an ability to dynamically customize the display of information including delay time based on observed error to better accommodate different strategies and objectives.

Strategy↗

NASA NTRS2014

UAS Integration into the NAS: HSI Full Mission Simulation Preliminary Results

The goal of the Full Mission Sim was to examine the effects of different command and control interfaces on UAS pilots' ability to respond to ATC commands and traffic advisories. Results suggest that higher levels of automation (i.e., waypoint-to-waypoint control interfaces) lead to longer initial response times and longer edit times. The findings demonstrate the importance of providing pilots with interfaces that facilitate their ability to get back "in the loop."

ground control stations↗

NASA NTRS2014

UAS Integration into the NAS: HSI Full Mission Simulation Analysis by Input Method

The goal of the Full Mission Sim was to examine the effects of different command and control interfaces on UAS pilots' ability to respond to ATC commands and traffic advisories. Results suggest that higher levels of automation (i.e., waypoint-to-waypoint control interfaces) lead to longer initial response times and longer edit times. The findings demonstrate the importance of providing pilots with interfaces that facilitate their ability to get back 'in the loop.'

ground control stations↗

NASA NTRS2019

Automatic Execution of Collision Avoidance and Return to Course Analysis (D.6.20) Experiment Review

This presentation details the experimental design for an upcoming engineering analysis of a mock version of the Airborne Collision Avoidance System (ACAS), specifically the 'Xu' variant, which is designed for unmanned aircraft platforms. As a component of the Unmanned Aircraft System (UAS) Integration into the National Airspace System (NAS) project, this engineering analysis intends to study aspects of ACAS Xu in two parts. In the first phase of the study, the display and alerting guidance for collision avoidance (CA) resolution advisories (RA) shown to pilots at a ground control station will be manipulated, varying in level of RA transparency and presentation of safe maneuver parameters. The second phase of the engineering analysis will examine pilots' response to increasing levels of automation in the tasks of collision avoidance and return-to-course (RTC).

Sadler, Garrett↗

NASA NTRS2019

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project: ACAS Xu Engineering Analysis Results

This presentation provides an overview of the results from a two-part engineering analysis conducted as part of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. Part one of this analysis examined how to present resolution advisories (RAs) issued by Airborne Collision Avoidance System (ACAS) Xu, which can be in the vertical dimension, the horizontal dimension, or both (i.e., "blended"). The study varied the appearance of the alerting and the verbiage used in the aural alerts. Results revealed high acceptability ratings for the appearance of the RA guidance. Part two of the analysis assessed pilot acceptability of varying levels of automation in the collision avoidance (CA) task. Pilots experienced conditions in which ACAS Xu RAs were executed either manually or automatically (i.e., auto-Collision Avoidance). In some conditions the return to a previously filed course was also executed automatically (auto-Return to Course). Results indicated that improvements are needed to how the state of the automation is presented. Implications of these findings are also discussed.

Detect and Avoid↗

NASA NTRS2009

TPSAS-NF1676L-9785-DND

Evaluate feasibility of inferring aspects of pilot state using active (force-feedback) side-stick, including a) contact with stick (haptic monitoring), b) Desire to change automation support level, c) pilot workload, and d) stress. Conduct human-in-the loop experiment to generate database for off-line investigation of potential signals and identification methods

Ken Goodrich↗

NASA NTRS2020

DEVELOP Poster: Louisville Urban Development

Greenness and land surface temperature (LST) have been extensively correlated to urban public health. Chronic diseases such as diabetes, asthma, and cardiovascular illnesses have been linked to regions of high LST and areas lacking urban green spaces. One of our partners, the University of Louisville Envirome Institute, champions the importance of urban green spaces. Their research has pioneered efforts in increasing the area and accessibility of urban parks and greenspaces as a way to improve public health and combat environmental inequality. Louisville, Kentucky, is currently working to plant and manage urban trees. Our team used NASA Landsat 8 Operational Land Imager (OLI) and Thermal Infrared Sensor (TIRS) imagery to calculate the Normalized Difference Vegetation Index (NDVI) in Louisville at the census tract level and automated the process for use in other cities. The New York University School of Medicine’s City Health Dashboard displays public health metrics across 500 US cities and will use our methods to complete the NDVI analysis for all of these locations plus an additional 293 cities they are adding to their dashboard in the near future. Our NDVI and LST calculations will allow cites across the US to make informed decisions about reducing environmental inequality by focusing on areas with low NDVI and high LST.

Urban Development↗

NASA NTRSDate not supplied

HAT m:N Cognitive Task Analysis (CTA)

This Cognitive Task Analysis (CTA) study was designed to understand the capability of the m:N Tactical Operator (TO) interfaces developed by the Human-Autonomy Teaming Laboratory at NASA Ames to support operators responsible for simplified pilot operations of 100 independently operated small UAS (sUAS) in a constrained geographic area. The m:N sUAS TO interface includes a central Tactical Situation Display (TSD) digital map with moving icons reflecting the sUAS location and planned flight route. The interface also has two side panels. The left panel includes a tabular list of UAS assets and mission tasking, a list of recently viewed assets, and a list of events and alerts. The right panel includes a tabular list of UAS assets and their associated telemetry, text-based chat communication window, and a tabbed checklist window. This CTA was adapted from the incident-based applied cognitive task analysis (Militello & Hutton, 1998) and included demographics questions, scenario-based simulations, a task diagram and knowledge audit methods. In addition to examining the support provided by this m:N sUAS TO interface, this CTA study, conducted with aviation subject matter experts in analogous roles to the future tactical operator, was designed to illuminate and project likely cognitive requirements of the tactical operator. Interviewees participated in two scenario-based simulations using the m:N sUAS TO interfaces. In the first simulation, the interviewees supervised 12 sUAS operating in downtown San Diego, California transiting to and from a central sUAS Hive, restaurant locations, and customer drop off locations. Interviewees were asked to react to a UAS Volume Reservation (UVR) event with a two-phase impact on food delivery operations. In the second scenario, the interviewees supervised 100 sUAS operating in the same airspace and with the same mission. Interviewees used the interfaces to recognize and react to two sUAS air vehicle problems. After each scenario, we asked the interviewees a semi-structured list of questions to elicit their reflections about using the interfaces. Interviewees were confident in their ability to respond to two off-nominal situations in each simulation. Interviewees felt that, given high levels of automation on the sUAS, they would be able to manage the events without requiring additional support or handing off the sUAS to a colleague or supervisor in both the n=12 or n=100 sUAS settings. In the n=12 sUAS condition, interviewees used the center map to understand the asset location and progress along with mission tasking. An additional display window, Asset Telemetry, helped interviewees understand battery state and sUAS altitude. When the number of sUAS increased, interviewees altered their behavior. Rather than maintaining awareness of individual assets, interviewees appeared to become more reactive, managing exceptions. Interviewees reported that they spent less time looking at the nominal aircraft, and focused their attention primarily on the off-nominal aircraft. In addition, in the second simulation with n=100 sUAS, interviewees reported that they relied more on the side panels (Mission Timeline and Asset Telemetry) to gather information.

human-autonomy teaming↗

NASA NTRSDate not supplied

m:N ConOps/R&R Remote Simulation

This presentation details the experimental design of an investigation of small unmanned aircraft system (sUAS) operations involving multiple vehicle management by a remote operator. The study is part of an ongoing effort to explore multiple vehicle control by multiple operators, i.e., the control of N vehicles by m operators (m:N operations). For this effort, NASA and collaborators have developed prototypes of a concept of operations (ConOps), roles and responsibilities (R&R) for operators and supervisors, and a ground control station (GCS), including software displays and interfaces. Participants in this study acted as the pilot-in-command of twelve aircraft flying pre-approved routes in a simulation of a food delivery operation utilizing sUAS in the San Diego, CA area. Each participant experienced four experimental trials. Twice within the course of each trial, participants were responsible for responding to a sudden, unanticipated, and high-priority contingency: an airspace restriction for sUAS operations known as a UAS Volume Reservation (UVR). Upon issuance of a UVR, pilots were expected to reroute affected vehicles around the airspace. The level of automation (LoA) and workload of the flight rerouting task were varied. The LoA was manipulated by providing reroute suggestions ("auto" condition) for aircraft or by requiring pilots to manually reroute ("manual" condition) affected vehicles. Workload was varied as a function of the number of vehicles affected by the UVR contingencies: 2 vehicles ("low workload" condition) versus 4 vehicles ("high workload" condition). Additionally, some vehicles required pilots to adjust for terrain conflicts while avoiding the UVR region. Due to the COVID-19 pandemic, in-person data collection for this study was not possible. Researchers adapted to this circumstance through the development of remote data collection protocol. Participants were able to view adapted GCS displays using the Microsoft Teams teleconferencing platform and responded to events by using a verbal protocol developed for the experiment. Using this protocol, participants provided instructions for actions to a researcher, referred to as the surrogate, to carry out on their behalf. This presentation describes the experiment design, including special details for remote data collection via a subject-surrogate configuration, and concludes with planned data analysis and results to be presented at a later date.

multi-UAS↗

NASA NTRS2022

National Campaign (NC)-1 Strategic Conflict Management Simulation (X4) Community Based Rules

Projected demand for transportation services in the urban environment has led to the development of several Concepts of Operation for Urban Air Mobility, or UAM. UAM is a concept for the transportation of people and goods in the metropolitan environment using small, efficient aircraft over short distances as part of an expanding multimodal transportation network. UAM will leverage emerging technologies including electric Vertical Takeoff and Landing (eVTOL) aircraft, increasing levels of automation and a new operational paradigm in dense airspace where a set of agreed-upon rules govern the procedures and interactions defining a cooperative environment in which operators are entrusted with a range of functions typically conducted by Air Traffic Control (ATC). These rules, proposed in the FAA NextGen Office’s UAM Concept of Operations [1], were originally termed Community Based Rules or Community Business Rules (CBRs), and will in the future termed Cooperative Operating Practices (COPs); this document uses the original term, CBR. CBRs are a set of rules, developed by the UAM community and (where necessary) approved by the FAA that govern the interactions between UAM entities and limit the need for ATC services including, but not limited to, separation control by ATC, addressing a fundamental challenge to scaling UAM operations. UAM community development of CBRs is anticipated to accelerate the adoption of new practices while retaining the regulatory authority of the FAA within required domains (e.g., NAS safety, security and equal access). However, there currently exists no agreed industry forum or defined procedures for CBR development. Investigation of best practices for the development of UAM CBRs was identified by NASA and the FAA NextGen Office as a research need. In collaboration with seven industry partners, NASA participated in a series of simulations that investigated elements of the envisioned UAM operations, with a primary focus on Strategic Conflict Management (SCM). The development and conduct of cooperative UAM simulations with seven industry partners provided a unique opportunity to investigate CBR development practices. Development of CBRs for the UAM SCM simulations was conducted in parallel with simulation capability development and was closely related to requirements definition for the simulations. As such, the CBR development effort presented herein had two objectives: explore CBR development practices in collaboration with the industry partners and develop an initial set of UAM CBRs to support simulation requirements definition and development. Consensus was achieved among NASA and the industry partners on 24 CBRs that were developed to support the cooperative simulation operations across five topic areas: General (related to test requirements), Operational Intent, Conformance Monitoring, Demand Capacity Balancing, and Airspace Constraint Management. Additional topic areas and CBRs were discussed but were deemed outside the scope of the simulation; these are included in the appendices. A collaborative, iterative process was employed for developing the CBRs engaging both NASA and Industry; because CBR development is envisioned to be community-driven, opportunities were sought that provided industry partners leadership roles in developing CBRs. The following key observations and recommendations may aid the UAM industry in future CBR development efforts: - The lack of a defined process proved challenging initially. Stakeholder engagement in the early stages of CBR development was intermittent and may have been due to the lack of a clear definition of roles and responsibilities of those involved in the effort. - Industry leadership of CBR topic areas proved successful. Discussions in these topic areas were engaging, with alternate viewpoints freely discussed and detailed CBRs resulting. This points to the importance of identifying the best-suited leadership in technical areas for CBR development. - Discussions within a CBR topic area were typically dominated by only a few participants. Whereas all industry partners contributed to CBR development, within each topic area, technical leadership was evident even when not formally established. This observation may indicate that smaller, focused groups may be more effective in initial CBR development than an open forum or large standards development effort (although both maybe required prior to FAA review and approval for some CBRs). - Identifying suitable forums for initial UAM CBR development and identifying the most effective industry participants and leadership will be crucial for successful CBR development. Although the operational need for UAM CBRs may not be immediate, establishing the forums and leadership to define the processes for CBR development is a prudent early step to UAM realization.

Community Based Rules↗

NASA NTRSDate not supplied

Control Architecture for a Concept Aircraft with a Series/Parallel Partial Hybrid Powertrain and Distributed Electric Propulsion

Traditional aircraft propulsion control approaches are insufficient for electrified aircraft powertrains due to their increased complexity compared to current systems. New control approaches are required to manage the increased interdependency and complexity of these electrified powertrains. Additionally, electrification enables aircraft to have multiple distributed thrust producing fans that the flight control system can leverage for enhanced maneuverability, further increasing the control complexity. This paper describes the control architecture for a concept vehicle with these characteristics, the SUbsonic Single Aft eNgine (SUSAN) Electrofan. SUSAN is a series/parallel partial hybrid electric single-aisle transport aircraft that leverages its electrified powertrain to provide fuel burn and emissions benefits when compared to the state-of-the-art. Achieving these benefits requires an appropriately designed control architecture that coordinates the various powertrain and flight control subsystems. As such, the SUSAN aircraft is designed with a high level of automation, allowing it to properly manage coupled subsystems and react rapidly to failures and anomalies. This paper presents a summary of the SUSAN powertrain design and discusses several of the novel control approaches used to manage the complex electrified powertrain.

Control↗

NASA NTRSDate not supplied

Control Architecture for a Concept Aircraft with a Series/Parallel Partial Hybrid Powertrain and Distributed Electric Propulsion

Traditional aircraft propulsion control approaches are insufficient for electrified aircraft powertrains due to their increased complexity compared to current systems. New control approaches are required to manage the increased interdependency and complexity of these electrified powertrains. Additionally, electrification enables aircraft to have multiple distributed thrust producing fans that the flight control system can leverage for enhanced maneuverability, further increasing the control complexity. This paper describes the control architecture for a concept vehicle with these characteristics, the SUbsonic Single Aft eNgine (SUSAN) Electrofan. SUSAN is a series/parallel partial hybrid electric single-aisle transport aircraft that leverages its electrified powertrain to provide fuel burn and emissions benefits when compared to the state-of-the-art. Achieving these benefits requires an appropriately designed control architecture that coordinates the various powertrain and flight control subsystems. As such, the SUSAN aircraft is designed with a high level of automation, allowing it to properly manage coupled subsystems and react rapidly to failures and anomalies. This paper presents a summary of the SUSAN powertrain design and discusses several of the novel control approaches used to manage the complex electrified powertrain.

Control↗

NASA NTRS2023

Control Architecture for a Concept Aircraft with a Series/Parallel Partial Hybrid Powertrain and Distributed Electric Propulsion

Traditional aircraft propulsion control approaches are insufficient for electrified aircraft powertrains due to their increased complexity compared to current systems. New control approaches are required to manage the increased interdependency and complexity of these electrified powertrains. Additionally, electrification enables aircraft to have multiple distributed thrust producing fans that the flight control system can leverage for enhanced maneuverability, further increasing the control complexity. This paper describes the control architecture for a concept vehicle with these characteristics, the SUbsonic Single Aft eNgine (SUSAN) Electrofan. SUSAN is a series/parallel partial hybrid electric single-aisle transport aircraft that leverages its electrified powertrain to provide fuel burn and emissions benefits when compared to the state-of-the-art. Achieving these benefits requires an appropriately designed control architecture that coordinates the various powertrain and flight control subsystems. As such, the SUSAN aircraft is designed with a high level of automation, allowing it to properly manage coupled subsystems and react rapidly to failures and anomalies. This paper presents a summary of the SUSAN powertrain design and discusses several of the novel control approaches used to manage the complex electrified powertrain.

Control↗

NASA NTRSDate not supplied

National Campaign Partner Demonstration Team Annual Review April 2023

- NASA developed the Advanced Air Mobility Project (AAM) and the National Campaign (NC) series to identify and address challenges ahead for advanced air mobility concepts. - NC seeks to challenge industry as follows; - Execute progressively more difficult ecosystem-wide system-level safety and integration scenarios - Demonstrate practical and scalable system concepts - Build a knowledge base for development of requirements and standards - There are currently three focus areas within the NASA AAM NC Portfolio - Vehicle Development and Operations: test and inform capabilities that are critical enablers for AAM such as electric aircraft propulsion and increasing levels of automation - Airspace Design and Operations: develop and validate an operational concept to integrate and manage AAM traffic safely and efficiently - Community Integration: understand and address critical barriers to community integration, such as public acceptance (noise, security, privacy, etc.), supporting infrastructure, and local regulation

Eric N Becker↗

NASA NTRSDate not supplied

Trustworthy Autonomy for Gateway Vehicle System Manager

The Vehicle System Manager (VSM) is the highest-level software control system in the Gateway hierarchical Autonomous System Management Architecture. The VSM provides four function categories: Mission Management and Timeline Execution, Resource Management, Fault Management, Vehicle Control and Operation. VSM provides various levels of automation ranging from fully autonomous operations with no flight crew and minimal ground monitoring to advisory automation when Gateway is crewed and has full ground monitoring. Trustworthiness is achieved via verified specification, comprehensive development verification, and real-time verification using assume-guarantee contracts. Development verification includes semantic verification of the data model via peer review and testing and assume-guarantee contracts implemented using the PlusCal/TLA+ environment. VSM also uses runtime assume-guarantee contracts, implemented in R2U2 via a runtime monitor that feeds the necessary telemetry data to R2U2 and which receives and responds to the R2U2 verdict stream. The full lifecycle verification approach and use of assume-guarantee contracts provides increased trustworthiness to VSM. Preliminary results provide encouragement that VSM can be both autonomous and trustworthy.

Assume-guarantee contracts↗