Search NASA⌕ Search

SEARCH · Search NASA

Results for “Level of Automation”

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 55 records · Page 3

Enabling Advanced Automation in Spacecraft Operations with the Spacecraft Emergency Response System

True autonomy is the Holy Grail of spacecraft mission operations. The goal of launching a satellite and letting it manage itself throughout its useful life is a worthy one. With true autonomy, the cost of mission operations would be reduced to a negligible amount. Under full autonomy, any problems (no matter the severity or type) that may arise with the spacecraft would be handled without any human intervention via some combination of smart sensors, on-board intelligence, and/or smart automated ground system. Until the day that complete autonomy is practical and affordable to deploy, incremental steps of deploying ever-increasing levels of automation (computerization of once manual tasks) on the ground and on the spacecraft are gradually decreasing the cost of mission operations. For example, NASA's Goddard Space Flight Center (NASA-GSFC) has been flying spacecraft with low cost operations for several years. NASA-GSFC's SMEX (Small Explorer) and MIDEX (Middle Explorer) missions have effectively deployed significant amounts of automation to enable the missions to fly predominately in 'light-out' mode. Under light-out operations the ground system is run without human intervention. Various tools perform many of the tasks previously performed by the human operators. One of the major issues in reducing human staff in favor of automation is the perceived increased in risk of losing data, or even losing a spacecraft, because of anomalous conditions that may occur when there is no one in the control center. When things go wrong, missions deploying advanced automation need to be sure that anomalous conditions are detected and that key personal are notified in a timely manner so that on-call team members can react to those conditions. To ensure the health and safety of its lights-out missions, NASA-GSFC's Advanced Automation and Autonomy branch (Code 588) developed the Spacecraft Emergency Response System (SERS). The SERS is a Web-based collaborative environment that enables secure distributed fault and resource management. The SERS incorporates the use of intelligent agents, threaded discussions, workflow, database connectivity, and links to a variety of communications devices (e.g., two-way paging, PDA's, and Internet phones) via commercial gateways. When the SERS detects a problem, it notifies on-call team members, who then can remotely take any necessary actions to resolve the anomalies.The SERS goes well beyond a simple '911' system that sends out an error code to everyone with a pager. Instead, SERS' software agents send detailed data (i.e., notifications) to the most appropriate team members based on the type and severity of the anomaly and the skills of the on-call team members. The SERS also allows the team members to respond to the notifications from their wireless devices. This unique capability ensures rapid response since the team members no longer have to go to a PC or the control center for every anomalous event. Most importantly, the SERS enables safe experimentation with various techniques for increasing levels of automation, leading to robust autonomy. For the MIDEX missions at NASA GSFC, the SERS is used to provide 'human-in-the-loop' automation. During lights-out operations, as greater control is given to the MIDEX automated systems, the SERS can be configured to page remote personnel and keep them informed regarding actions taking place in the control center. Remote off-duty operators can even be given the option of enabling or inhibiting a specific automated response in near real time via their two-way pagers. The SERS facilitates insertion of new technology to increase automation, while maintaining the safety and security of mission resources. This paper will focus on SERS' overall functionality and how SERS has been designed to handle the monitoring and emergency response for missions with varying levels of automation. The paper will also convey some of the key lessons learned from SERS' deployment across of variety of missions, highlighting this incremental approach to achieving 'robust autonomy'.

Breed, Julie↗

The Role of the Onboard Operator in Automated Rapid Rail Transit

A study of automatic train control systems used in rail rapid transit systems with various levels of automation revealed: full automation, now possible, does not preclude the onboard operator as a safety element. Elimination of the operator necessitates extremely high levels of guideway protection. Where such protection is impossible operator viglance must be maintained through assignment of non-trivial tasks. The. functions most difficult to automate are right-of-way surveillance and door operation. In new systems automation level should be based on local transportation needs derived from system studies and verified through simulation.

Susssman, E. D.↗

Use of Semi-Autonomous Tools for ISS Commanding and Monitoring

As the International Space Station (ISS) has moved into a utilization phase, operations have shifted to become more ground-based with fewer mission control personnel monitoring and commanding multiple ISS systems. This shift to fewer people monitoring more systems has prompted use of semi-autonomous console tools in the ISS Mission Control Center (MCC) to help flight controllers command and monitor the ISS. These console tools perform routine operational procedures while keeping the human operator "in the loop" to monitor and intervene when off-nominal events arise. Two such tools, the Pre-positioned Load (PPL) Loader and Automatic Operators Recorder Manager (AutoORM), are used by the ISS Communications RF Onboard Networks Utilization Specialist (CRONUS) flight control position. CRONUS is responsible for simultaneously commanding and monitoring the ISS Command & Data Handling (C&DH) and Communications and Tracking (C&T) systems. PPL Loader is used to uplink small pieces of frequently changed software data tables, called PPLs, to ISS computers to support different ISS operations. In order to uplink a PPL, a data load command must be built that contains multiple user-input fields. Next, a multiple step commanding and verification procedure must be performed to enable an onboard computer for software uplink, uplink the PPL, verify the PPL has incorporated correctly, and disable the computer for software uplink. PPL Loader provides different levels of automation in both building and uplinking these commands. In its manual mode, PPL Loader automatically builds the PPL data load commands but allows the flight controller to verify and save the commands for future uplink. In its auto mode, PPL Loader automatically builds the PPL data load commands for flight controller verification, but automatically performs the PPL uplink procedure by sending commands and performing verification checks while notifying CRONUS of procedure step completion. If an off-nominal condition occurs during procedure execution, PPL Loader notifies CRONUS through popup messages, allowing CRONUS to examine the situation and choose an option of how PPL loader should proceed with the procedure. The use of PPL Loader to perform frequent, routine PPL uplinks offloads CRONUS to better monitor two ISS systems. It also reduces procedure performance time and decreases risk of command errors. AutoORM identifies ISS communication outage periods and builds commands to lock, playback, and unlock ISS Operations Recorder files. Operation Recorder files are circular buffer files of continually recorded ISS telemetry data. Sections of these files can be locked from further writing, be played back to capture telemetry data that occurred during an ISS loss of signal (LOS) period, and then be unlocked for future recording use. Downlinked Operation Recorder files are used by mission support teams for data analysis, especially if failures occur during LOS. The commands to lock, playback, and unlock Operations Recorder files are encompassed in three different operational procedures and contain multiple user-input fields. AutoORM provides different levels of automation for building and uplinking the commands to lock, playback, and unlock Operations Recorder files. In its automatic mode, AutoORM automatically detects ISS LOS periods, then generates and uplinks the commands to lock, playback, and unlock Operations Recorder files when MCC regains signal with ISS. AutoORM also features semi-autonomous and manual modes which integrate CRONUS more into the command verification and uplink process. AutoORMs ability to automatically detect ISS LOS periods and build the necessary commands to preserve, playback, and release recorded telemetry data greatly offloads CRONUS to perform more high-level cognitive tasks, such as mission planning and anomaly troubleshooting. Additionally, since Operations Recorder commands contain numerical time input fields which are tedious for a human to manually build, AutoORM's ability to automatically build commands reduces operational command errors. PPL Loader and AutoORM demonstrate principles of semi-autonomous operational tools that will benefit future space mission operations. Both tools employ different levels of automation to perform simple and routine procedures, thereby offloading human operators to perform higher-level cognitive tasks. Because both tools provide procedure execution status and highlight off-nominal indications, the flight controller is able to intervene during procedure execution if needed. Semi-autonomous tools and systems that can perform routine procedures, yet keep human operators informed of execution, will be essential in future long-duration missions where the onboard crew will be solely responsible for spacecraft monitoring and control.

Brzezinski, Amy S.↗

Line Pilots' Attitudes about and Experience with Flight Deck Automation: Results of an International Survey and Proposed Guidelines

A survey of line pilots' attitudes about flight deck automation was conducted by the Royal Air Force Institute of Aviation Medicine (RAF IAM, Farnborough, UK) under the sponsorship of the United Kingdom s Civil Aviation Authority and in cooperation with IATA (the International Air Transport Association). Survey freehand comments given by pilots operating 13 types of commercial transports across five manufacturers (Airbus, Boeing, British Aerospace, Lockheed, and McDonnell-Douglas) and 57 air carriers/organizations were analyzed by NASA. These data provide a "lessons learned" knowledge base which may be used for the definition of guidelines for flight deck automation and its associated crew interface within the High Speed Research Program. The aircraft chosen for analysis represented a progression of levels of automation sophistication and complexity, from "Basic" types (e.g., B727, DC9), through "Transition" types (e.g., A300, Concorde), to two levels of glass cockpits (e.g., Glass 1: e.g., A310; Glass 2: e.g., B747-400). This paper reports the results of analyses of comments from pilots flying commercial transport types having the highest level of automation sophistication (B757/B767, B747-400, and A320). Comments were decomposed into five categories relating to: (1) general observations with regard to flight deck automation; comments concerning the (2) design and (3) crew understanding of automation and the crew interface; (4) crew operations with automation; and (5) personal factors affecting crew/automation interaction. The goal of these analyses is to contribute to the definition of guidelines which may be used during design of future aircraft flight decks.

Rudisill, Marianne↗

Understanding and avoiding potential problems in implementing automation

Technology-driven efforts to implement automation often encounter problems due to lack of acceptance or begrudging acceptance by the personnel involved. It is argued in this paper that the level of automation perceived by an individual heavily influences whether or not the automation is accepted by that individual. The factors that appear to affect perceived level of automation are discussed. Issues considered include the impact of automation on the system and the individual, correlates of acceptance, problems and risks of automation, and factors influencing alienation. Based on an understanding of these issues, a set of eight guidelines is proposed as a possible means of avoiding problems in implementing automation.

Rouse, W. B.↗

Autonomy and Automation

A significant level of debate and confusion has surrounded the meaning of the terms autonomy and automation. Automation is a multi-dimensional concept, and we propose that Remotely Piloted Aircraft Systems (RPAS) automation should be described with reference to the specific system and task that has been automated, the context in which the automation functions, and other relevant dimensions. In this paper, we present definitions of automation, pilot in the loop, pilot on the loop and pilot out of the loop. We further propose that in future, the International Civil Aviation Organization (ICAO) RPAS Panel avoids the use of the terms autonomy and autonomous when referring to automated systems on board RPA. Work Group 7 proposes to develop, in consultation with other workgroups, a taxonomy of Levels of Automation for RPAS.

rometly piloted aircraft↗

Remotely Piloted Aircraft Systems Panel (RPASP) Working Paper: Autonomy and Automation

A significant level of debate and confusion has surrounded the meaning of the terms "autonomy" and "automation". Automation is a multi-dimensional concept, and we propose that RPAS automation should be described with reference to the specific system and task that has been automated, the context in which the automation functions, and other relevant dimensions. In this paper, we present a definition of "automation". We recommend that autonomy and autonomous operations are out of the scope of the RPAS panel. WG7 proposes to develop, in consultation with other workgroups, a taxonomy of "Levels of Automation" for RPAS.

Autonomy↗

Enabling Advanced Air Mobility Operations through Appropriate Trust in Human-Autonomy Teaming: Foundational Research Approaches and Applications

Emerging Advanced Air Mobility(AAM)operations will be enabled by increasingly autonomous systems, requiring technologies to take on more responsibilities and fundamentally altering traditional human-automation interaction paradigms. The growing reliance on higher levels of automation will necessitate research to identify capabilities and principles that facilitate humans and machines working and thinking better together, i.e., human-autonomy teaming (HAT). Trust is an inherent requirement in effective teams because when members work interdependently, those agents (human, automation) must be willing to accept a level of risk to rely upon each other to reach goals and contribute to team tasks. This work provides an initial approach to enabling AAM operations through appropriate trust within HAT. The main contributions of this approach resides in connecting the construct of trust to mental models. Using the outlined mental model approach, we propose novel HAT strategies, such as Adaptive Trust Calibration, and preview planned research activities derived from this approach. Additionally, we propose several practical applications that can currently be employed by AAM development communities.

Eric T Chancey↗

A design procedure for control/display systems

This paper proposes a design procedure for control and display systems in which levels of automation vary over a significant range. The elements of the primary analysis tool (the Optimal Control Model of the Human Operator) are briefly reviewed, and the use of the model at three levels of specification (information level, display-element level, and display-format level) is discussed. Based on observation and pilot commentary, it is assumed that the pilot allocates his attention to control the aircraft to the desired level of performance, and then, with remaining capacity, to monitor displays. This facet of behavior is incorporated into the design procedure so that regardless of the level of control automation, all systems are compared at the same level of control performance. The design procedure is applied to the longitudinal control of a CH-47 helicopter. The procedure points out the need for performance-workload relations for control, which are fairly well understood, and performance-workload relations for monitoring, about which little is known.

Curry, R. E.↗

Managing the Implementation of Mission Operations Automation

Reducing the cost of mission operations has necessitated a high level of automation both on spacecraft and ground systems. While automation on spacecraft is implemented during the design phase, ground system automation tends to be implemented during the prime mission operations phase. Experience has shown that this tendency for late automation development can be hindered by several factors: additional hardware and software resources may need to be procured; software must be developed and tested on a non-interference basis with primary operations with limited manpower; and established procedures may not be suited for automation requiring substantial rework. In this paper we will review the experience of successfully automating mission operations for seven on-orbit missions: the Compton Gamma Ray Observatory (CGRO), the Rossi X-Ray Timing Explorer (RXTE), the Advanced Composition Explorer (ACE), the Far Ultraviolet Spectroscopic Explorer (FUSE), Interplanetary Physics Laboratory (WIND), Polar Plasma Laboratory (POLAR), and the Imager for Magnetopause-to-Aurora Global Exploration (IMAGE). We will provide lessons learned in areas such as: spacecraft recorder management, procedure development, lights out commanding from the ground system vs. stored command loads, spacecraft contingency response time, and ground station interfaces. Implementing automation strategies during the mission concept and spacecraft integration and test phase as the most efficient method will be discussed.

Sodano, R.↗

A two-level structure for advanced space power system automation

The tasks to be carried out during the three-year project period are: (1) performing extensive simulation using existing mathematical models to build a specific knowledge base of the operating characteristics of space power systems; (2) carrying out the necessary basic research on hierarchical control structures, real-time quantitative algorithms, and decision-theoretic procedures; (3) developing a two-level automation scheme for fault detection and diagnosis, maintenance and restoration scheduling, and load management; and (4) testing and demonstration. The outlines of the proposed system structure that served as a master plan for this project, work accomplished, concluding remarks, and ideas for future work are also addressed.

Loparo, Kenneth A.↗

Applications of artificial intelligence to space station and automated software techniques: High level robot command language

The objective is to develop a system that will allow a person not necessarily skilled in the art of programming robots to quickly and naturally create the necessary data and commands to enable a robot to perform a desired task. The system will use a menu driven graphical user interface. This interface will allow the user to input data to select objects to be moved. There will be an imbedded expert system to process the knowledge about objects and the robot to determine how they are to be moved. There will be automatic path planning to avoid obstacles in the work space and to create a near optimum path. The system will contain the software to generate the required robot instructions.

Mckee, James W.↗

Hazard Perception & Avoidance (HPA): Part Task 1 - Results Outbrief

n April 2022, the Human Autonomy Teaming Lab (NASA Ames Research Center) conducted a manned, human-in-the-loop (HITL) simulation. This part task HITL began the lab’s Hazard Perception and Avoidance (HPA) technical work under NASA’s Advanced Air Mobility (AAM), Automated Flight and Contingency Management (AFCM) Sub-Project. The goals were to assess levels of automation for manned, electric vertical takeoff and landing (eVTOL) aircraft. This simulation tested manual and automated Resolution Advisory (RA) responses and return-to-course (RTC) maneuvers for the first version of the Airborne Collision Avoidance System’s (ACAS) rotary-wing (Xr) variant. This was conducted on a fixed-based simulator designed to fly eVTOL aircraft while maneuvering for intruding traffic. Variables for this study included levels of autonomy (i.e., manual and automated) as well as the types of alerts at the onset of conflicts (i.e., Corrective and RA). The data collected included response times, losses of well clear, and maneuver sizes and durations as well as subjective ratings like acceptability, and perceived workload. Additional details and future anticipations are also discussed.

air taxis↗

ACAS Xr Part Task Sim, Preliminary Experiment Design

In early 2022, the Human Autonomy Teaming Lab (NASA Ames Research Center) will conduct a manned, human-in-the-loop (HITL) simulation. This part task HITL will begin the lab’s Hazard Perception and Avoidance (HPA) technical work under NASA’s Advanced Air Mobility (AAM), Automated Flight and Contingency Management (AFCM) Sub-Project. The goals will be to assess levels of automation for manned, electric vertical takeoff and landing (eVTOL) aircraft. This simulation will test manual and automated Resolution Advisory (RA) responses and return-to-course (RTC) maneuvers for the first version of the Airborne Collision Avoidance System’s (ACAS) rotary-wing (Xr) variant. This will be conducted on a fixed-based simulator designed to fly eVTOL aircraft while maneuvering for intruding traffic. Variables for this study include levels of autonomy (i.e., manual and automated) as well as the types of alerts at the onset of conflicts (i.e., Corrective and RA). The data collected will include response times, losses of well clear, and maneuver sizes and durations as well as subjective ratings like acceptability, perceived workload, and meaningful human control. Additional details and future anticipations are also discussed.

air taxis↗

Fault tolerant computer control for a Maglev transportation system

Magnetically levitated (Maglev) vehicles operating on dedicated guideways at speeds of 500 km/hr are an emerging transportation alternative to short-haul air and high-speed rail. They have the potential to offer a service significantly more dependable than air and with less operating cost than both air and high-speed rail. Maglev transportation derives these benefits by using magnetic forces to suspend a vehicle 8 to 200 mm above the guideway. Magnetic forces are also used for propulsion and guidance. The combination of high speed, short headways, stringent ride quality requirements, and a distributed offboard propulsion system necessitates high levels of automation for the Maglev control and operation. Very high levels of safety and availability will be required for the Maglev control system. This paper describes the mission scenario, functional requirements, and dependability and performance requirements of the Maglev command, control, and communications system. A distributed hierarchical architecture consisting of vehicle on-board computers, wayside zone computers, a central computer facility, and communication links between these entities was synthesized to meet the functional and dependability requirements on the maglev. Two variations of the basic architecture are described: the Smart Vehicle Architecture (SVA) and the Zone Control Architecture (ZCA). Preliminary dependability modeling results are also presented.

Lala, Jaynarayan H.↗

Automation and robotics human performance

The scope of this report is limited to the following: (1) assessing the feasibility of the assumptions for crew productivity during the intra-vehicular activities and extra-vehicular activities; (2) estimating the appropriate level of automation and robotics to accomplish balanced man-machine, cost-effective operations in space; (3) identifying areas where conceptually different approaches to the use of people and machines can leverage the benefits of the scenarios; and (4) recommending modifications to scenarios or developing new scenarios that will improve the expected benefits. The FY89 special assessments are grouped into the five categories shown in the report. The high level system analyses for Automation & Robotics (A&R) and Human Performance (HP) were performed under the Case Studies Technology Assessment category, whereas the detailed analyses for the critical systems and high leverage development areas were performed under the appropriate operations categories (In-Space Vehicle Operations or Planetary Surface Operations). The analysis activities planned for the Science Operations technology areas were deferred to FY90 studies. The remaining activities such as analytic tool development, graphics/video demonstrations and intelligent communicating systems software architecture were performed under the Simulation & Validations category.

Mah, Robert W.↗

Measuring the Effectiveness of Human Autonomy Teaming

Human-Automation Teaming (HAT), is now recognized as a promising solution to the problems of humans managing increasingly complex work systems. A human-automation team can be defined as the interdependent coupling between one or more human operators and one or more autonomous systems requiring collaboration and coordination to accomplish system and task goals (e.g., Langan-Fox et al., 2009). In this conception, automated agents are considered team members that can operate at various levels of automation, be focused on one or more human-information-processing stages, and the interactions with human operators may be adaptable, adjustable or mixed initiative. We investigated some metrics for assessing HAT effectiveness in a demonstration of a HAT tool used by ground station operators in a Reduced Crew Operations project that was conducted at NASA Ames Human Automation Teaming Laboratory. In this paper, we focus on operator metrics of HAT effectiveness, specifically workload and operator behaviors.

measurements↗

The self-consistent calculation of pseudo-molecule energy levels, construction of energy level correlation diagrams and an automated computation system for SCF-X(Alpha)-SW calculations

The self consistent calculation of the electronic energy levels of noble gas pseudomolecules formed when a metal surface is bombarded by noble gas ions is discussed along with the construction of energy level correlation diagrams as a function of interatomic spacing. The self consistent field x alpha scattered wave (SCF-Xalpha-SW) method is utilized. Preliminary results on the Ne-Mg system are given. An interactive x alpha programming system, implemented on the LeRC IBM 370 computer, is described in detail. This automated system makes use of special PROCDEFS (procedure definitions) to minimize the data to be entered manually at a remote terminal. Listings of the special PROCDEFS and of typical input data are given.

Schlosser, H.↗