Search NASA⌕ Search

SEARCH · Search NASA

Results for “Automating”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

Perl Tools for Automating Satellite Ground Systems

The freeware scripting language Pert offers many opportunities for automating satellite ground systems for new satellites as well as older, in situ systems. This paper describes a toolkit that has evolved from of the experiences gained by using Pert to automate the ground system for the Compton Gamma Ray Observatory (CGRO) and for automating some of the elements in the Earth Observing System Data and Operations System (EDOS) ground system at Goddard Space Flight Center (GSFC). CGRO is an older ground system that was forced to automate because of fund cuts. Three 8 hour shifts were cut back to one 8 hour shift, 7 days per week. EDOS supports a new mission called Terra, launched December 1999 that requires distribution and tracking of mission-critical reports throughout the world. Both of these ground systems use Pert scripts to process data and display it on the Internet as well as scripts to coordinate many of the other systems that make these ground systems work as a coherent whole. Another task called Automated Multimodal Trend Analysis System (AMTAS) is looking at technology for isolation and recovery of spacecraft problems. This effort has led to prototypes that seek to evaluate various tools and technology that meet at least some of the AMTAS goals. The tools, experiences, and lessons learned by implementing these systems are described here.

McLean, David↗
NASA NTRS2002

The Relationship of Self-Efficacy and Complacency in Pilot-Automation Interaction

Pilot 'complacency' has been implicated as a contributing factor in numerous aviation accidents and incidents. The term has become more prominent with the increase in automation technology in modern cockpits and, therefore, research has been focused on understanding the factors that may mitigate its effect on pilot-automation interaction. The study examined self-efficacy of supervisory monitoring and the relationship between complacency on strategy of pilot use of automation for workload management under automation schedules that produce the potential for complacency. The results showed that self-efficacy can be a 'double-edged' sword in reducing potential for automation-induced complacency but limiting workload management strategies and increasing other hazardous states of awareness.

Prinzel, Lawrence J., III↗
NASA NTRS1990

Development Status: Automation Advanced Development Space Station Freedom Electric Power System

Electric power system automation for Space Station Freedom is intended to operate in a loop. Data from the power system is used for diagnosis and security analysis to generate Operations Management System (OMS) requests, which are sent to an arbiter, which sends a plan to a commander generator connected to the electric power system. This viewgraph presentation profiles automation software for diagnosis, scheduling, and constraint interfaces, and simulation to support automation development. The automation development process is diagrammed, and the process of creating Ada and ART versions of the automation software is described.

Dolce, James L.↗
NASA NTRS2004

Designing Domain-Specific HUMS Architectures: An Automated Approach

The HUMS automation system automates the design of HUMS architectures. The automated design process involves selection of solutions from a large space of designs as well as pure synthesis of designs. Hence the whole objective is to efficiently search for or synthesize designs or parts of designs in the database and to integrate them to form the entire system design. The automation system adopts two approaches in order to produce the designs: (a) Bottom-up approach and (b) Top down approach. Both the approaches are endowed with a Suite of quantitative and quantitative techniques that enable a) the selection of matching component instances, b) the determination of design parameters, c) the evaluation of candidate designs at component-level and at system-level, d) the performance of cost-benefit analyses, e) the performance of trade-off analyses, etc. In short, the automation system attempts to capitalize on the knowledge developed from years of experience in engineering, system design and operation of the HUMS systems in order to economically produce the most optimal and domain-specific designs.

Mukkamala, Ravi↗
NASA NTRS2006

Application of the H-Mode, a Design and Interaction Concept for Highly Automated Vehicles, to Aircraft

Driven by increased safety, efficiency, and airspace capacity, automation is playing an increasing role in aircraft operations. As aircraft become increasingly able to autonomously respond to a range of situations with performance surpassing human operators, we are compelled to look for new methods that help us understand their use and guide their design using new forms of automation and interaction. We propose a novel design metaphor to aid the conceptualization, design, and operation of highly-automated aircraft. Design metaphors transfer meaning from common experiences to less familiar applications or functions. A notable example is the "Desktop metaphor" for manipulating files on a computer. This paper describes a metaphor for highly automated vehicles known as the H-metaphor and a specific embodiment of the metaphor known as the H-mode as applied to aircraft. The fundamentals of the H-metaphor are reviewed followed by an overview of an exploratory usability study investigating human-automation interaction issues for a simple H-mode implementation. The envisioned application of the H-mode concept to aircraft is then described as are two planned evaluations.

Goodrich, Kenneth H.↗
NASA NTRS2009

Human-rating Automated and Robotic Systems - (How HAL Can Work Safely with Astronauts)

Long duration human space missions, as planned in the Vision for Space Exploration, will not be possible without applying unprecedented levels of automation to support the human endeavors. The automated and robotic systems must carry the load of routine housekeeping for the new generation of explorers, as well as assist their exploration science and engineering work with new precision. Fortunately, the state of automated and robotic systems is sophisticated and sturdy enough to do this work - but the systems themselves have never been human-rated as all other NASA physical systems used in human space flight have. Our intent in this paper is to provide perspective on requirements and architecture for the interfaces and interactions between human beings and the astonishing array of automated systems; and the approach we believe necessary to create human-rated systems and implement them in the space program. We will explain our proposed standard structure for automation and robotic systems, and the process by which we will develop and implement that standard as an addition to NASA s Human Rating requirements. Our work here is based on real experience with both human system and robotic system designs; for surface operations as well as for in-flight monitoring and control; and on the necessities we have discovered for human-systems integration in NASA's Constellation program. We hope this will be an invitation to dialog and to consideration of a new issue facing new generations of explorers and their outfitters.

Baroff, Lynn↗
NASA NTRS2017

Lighting Automation - Flying an Earthlike Habit Project

Our proposal will enable the development of automated spacecraft habitats for long duration missions. Majority of spacecraft lighting systems employ lamps or zone specific switches and dimmers. Automation is not in the "picture". If we are to build long duration environments, which provide earth-like habitats, minimize crew time, and optimize spacecraft power reserves, innovation in lighting automation is a must. To transform how spacecraft lighting environments are automated, we will provide performance data on a standard lighting communication protocol. We will investigate utilization and application of an industry accepted lighting control protocol, DMX512. We will demonstrate how lighting automation can conserve power, assist with lighting countermeasures, and utilize spatial body tracking. By using DMX512 we will prove the "wheel" does not need to be reinvented in terms of smart lighting and future spacecraft can use a standard lighting protocol to produce an effective, optimized and potentially earthlike habitat.

Falker, Jay↗
NASA NTRS2019

Controls and Automation Research in Space Life Support

A highly controlled and automated life support system has long been a NASA goal. It is usually assumed that life support for future long duration missions will use physical/chemical recycling systems that substantially close the oxygen and water circulation loops. Such a tightly coupled life support system has been thought to require an overall supervisory control system to minimize crew operation and maintenance activities. The International Space Station (ISS) Environmental Control and Life Support System (ECLSS) was at first expected to have supervisory control and automation. After this was found infeasible during the design of the ISS ECLSS in the early 1990's, it was then expected that the ISS or future mission systems would be upgraded to meet the original expectations. Since then NASA has extensively researched life support system controls and automation. Automation and Artificial Intelligence (AI) have gone through several cycles of enthusiasm and neglect before their recent great achievements, and NASA life support interest has similarly varied. Since the ISS ECLSS was launched, its on-board operational problems have led NASA to deemphasize system level controls and automation in favor of improving subsystem reliability and maintainability. Recent work has investigated supervisory control for a system similar to the ISS ECLSS. This paper reviews past planning and work on the supervisory control of closed, integrated physical/chemical life support systems similar to the ISS ECLSS and its precursors dating back to the 1960's.

life support↗
NASA NTRS2008

Distribution automation applications of fiber optics

Motivations for interest and research in distribution automation are discussed. The communication requirements of distribution automation are examined, and shown to exceed the capabilities of power line carrier, radio and telephone systems. A fiber-optic-based communication system is described that is co-located with the distribution system and that ould satisfy the data rate and reliability requirements. A cost comparison shows that it could be constructed at a cost that is similar to that of a power line carrier system. The requirements for fiber optic sensors for distribution automation are discussed. The design of a data link suitable for opticallypowered electronic sensing is presented. Empirical results are given. A modeling technique that has been used to understand the reflections of guided light from a variety of surfaces is described. An optical positionindicator design is discussed. Systems aspects of distribution automation are discussed, in particular the lack of interface, communications and data standards. The economics of distribution automation are examined

Friend, H.↗
NASA NTRS2022

Dynamic Path Planning Automation Concept for Advanced Air Mobility

Advanced Air Mobility (AAM) aims to develop an air transportation system for novel air vehicles between local, regional, intraregional, and urban places. Safety and efficiency of increasingly complex AAM operations are expected to require extensive use of automation, ranging from controlling the revolutionary new aircraft to managing flights dynamically in the high tempo airspace and aerodrome operations. Both onboard and ground automation will play central roles in assisting AAM operators with managing the flight paths of their fleet. This document presents a concept for dynamic path planning (DPP) automation applicable to AAM and other flight operations. The role of the DPP automation system is fivefold: (1) it creates a flight path with desired qualities of being feasible, deconflicted, harmonized, flexible, and optimal; (2) it monitors the progress of flight in a dynamic operating environment; (3) it supports the user in evaluating continued acceptability of the flight path in changing conditions; (4) it revises the flight path as needed to maintain the desired flight path qualities; and (5) it coordinates the flight path with airspace users and service providers. Key users of the DPP automation system include flight planners, pilots, and airspace service providers The concept allows for the system to be installed onboard the aircraft as well as on the ground. The system responds automatically to the dynamic operating environment to ensure that a safe and operationally acceptable flight path is available throughout the flight.

Vivek Sharma↗
NASA NTRSDate not supplied

Automating Maneuvers: Considerations for Collision Avoidance

As more space operators implement large constellations of spacecraft, automating orbit maintenance maneuvers becomes a key feature of their operations concept to ensure that the workload is manageable. However the practice of performing a maneuver without sharing the plan with other nearby spacecraft causes a risk that two spacecraft will collide, not only destroying the spacecraft involved, but creating debris that will affect all other spacecraft using that orbit regime. In order to share the maneuver plan, a predicted ephemeris file containing the maneuver must be sent to a central authority to screen against predicted trajectories of all other on-orbit objects to determine where and when close approaches may occur that need to be mitigated. Currently the screening authority used by US operators is the 19th Space Defense Squadron. However the conjunction screening process in use by the 19th was developed over 30 years ago and was not designed with automation in mind, so screenings are performed once every 8 hours, meaning that spacecraft using automated maneuvering need to allow 16 hours to share their maneuver plan via the screening process. Many operators assume that automated maneuver planning must be real-time; however this time between planning and execution to allow for screening is possible if planned for during system design. In an effort to speed up the screening process, NASA has developed a prototype system for performing near-real-time screenings. This prototype system was necessitated to support the NASA Starling mission, a constellation of 4 cubesats that planned to fly at the same altitude as the SpaceX Starlink constellation, both performing automated maneuvering. Without screening of the planned maneuvers, the two constellations risked a collision. Once converted from a prototype to an operational system, this capability will greatly help smallsats, for example those that are planning to test propulsive capabilities, by allowing fast turnaround feedback to ensure safety form collision with other objects. This paper describes the existing CA process, the prototype real-time capability, and results from the experiment that tested the prototype.

Matthew Hejduk↗
NASA NTRS2000

Human versus automation in responding to failures: an expected-value analysis

A simple analytical criterion is provided for deciding whether a human or automation is best for a failure detection task. The method is based on expected-value decision theory in much the same way as is signal detection. It requires specification of the probabilities of misses (false negatives) and false alarms (false positives) for both human and automation being considered, as well as factors independent of the choice--namely, costs and benefits of incorrect and correct decisions as well as the prior probability of failure. The method can also serve as a basis for comparing different modes of automation. Some limiting cases of application are discussed, as are some decision criteria other than expected value. Actual or potential applications include the design and evaluation of any system in which either humans or automation are being considered.

NASA Discipline Space Human Factors↗
NASA NTRS2003

Effects of a psychophysiological system for adaptive automation on performance, workload, and the event-related potential P300 component

The present study examined the effects of an electroencephalographic- (EEG-) based system for adaptive automation on tracking performance and workload. In addition, event-related potentials (ERPs) to a secondary task were derived to determine whether they would provide an additional degree of workload specificity. Participants were run in an adaptive automation condition, in which the system switched between manual and automatic task modes based on the value of each individual's own EEG engagement index; a yoked control condition; or another control group, in which task mode switches followed a random pattern. Adaptive automation improved performance and resulted in lower levels of workload. Further, the P300 component of the ERP paralleled the sensitivity to task demands of the performance and subjective measures across conditions. These results indicate that it is possible to improve performance with a psychophysiological adaptive automation system and that ERPs may provide an alternative means for distinguishing among levels of cognitive task demand in such systems. Actual or potential applications of this research include improved methods for assessing operator workload and performance.

Task Performance and Analysis↗
NASA NTRS2006

Cassini-Huygens maneuver automation for navigation

Many times during the Cassini-Huygens mission to Saturn, propulsive maneuvers must be spaced so closely together that there isn't enough time or workforce to execute the maneuver-related software manually, one subsystem at a time. Automation is required. Automating the maneuver design process has involved close cooperation between teams. We present the contribution from the Navigation system. In scope, this includes trajectory propagation and search, generation of ephemerides, general tasks such as email notification and file transfer, and presentation materials. The software has been used to help understand maneuver optimization results, Huygens probe delivery statistics, and Saturn ring-plane crossing geometry. The Maneuver Automation Software (MAS), developed for the Cassini-Huygens program enables frequent maneuvers by handling mundane tasks such as creation of deliverable files, file delivery, generation and transmission of email announcements, generation of presentation material and other supporting documentation. By hand, these tasks took up hours, if not days, of work for each maneuver. Automated, these tasks may be completed in under an hour. During the cruise trajectory the spacing of maneuvers was such that development of a maneuver design could span about a month, involving several other processes in addition to that described, above. Often, about the last five days of this process covered the generation of a final design using an updated orbit-determination estimate. To support the tour trajectory, the orbit determination data cut-off of five days before the maneuver needed to be reduced to approximately one day and the whole maneuver development process needed to be reduced to less than a week..

propulsion maneuvers↗
NASA NTRS2012

Automation and Process Improvement Enables a Small Team to Operate a Low Thrust Mission in Orbit Around the Asteroid Vesta

NASA's Dawn mission to the asteroid Vesta and dwarf planet Ceres launched September 27, 2007 and arrived at Vesta in July of 2011. This mission uses ion propulsion to achieve the necessary delta-V to reach and maneuver at Vesta and Ceres. This paper will show how the evolution of ground system automation and process improvement allowed a relatively small engineering team to transition from cruise operations to asteroid operations while maintaining robust processes. The cruise to Vesta phase lasted almost 4 years and consisted of activities that were built with software tools, but each tool was open loop and required engineers to review the output to ensure consistency. Additionally, this same time period was characterized by the evolution from manually retrieved and reviewed data products to automatically generated data products and data value checking. Furthermore, the team originally took about three to four weeks to design and build about four weeks of spacecraft activities, with spacecraft contacts only once a week. Operations around the asteroid Vesta increased the tempo dramatically by transitioning from one contact a week to three or four contacts a week, to fourteen contacts a week (every 12 hours). This was accompanied by a similar increase in activity complexity as well as very fast turn around activity design and build cycles. The design process became more automated and the tools became closed loop, allowing the team to build more activities without sacrificing rigor. Additionally, these activities were dependent on the results of flight system performance, so more automation was added to analyze the flight data and provide results in a timely fashion to feed the design cycle. All of this automation and process improvement enabled up the engineers to focus on other aspects of spacecraft operations, including spacecraft health monitoring and anomaly resolution.

ground system automation↗
NASA NTRS2014

NextGen Technologies on the FAA's Standard Terminal Automation Replacement System

This paper describes the integration, evaluation, and results from a high-fidelity human-in-the-loop (HITL) simulation of key NASA Air Traffic Management Technology Demonstration - 1 (ATD- 1) technologies implemented in an enhanced version of the FAA's Standard Terminal Automation Replacement System (STARS) platform. These ATD-1 technologies include: (1) a NASA enhanced version of the FAA's Time-Based Flow Management, (2) a NASA ground-based automation technology known as controller-managed spacing (CMS), and (3) a NASA advanced avionics airborne technology known as flight-deck interval management (FIM). These ATD-1 technologies have been extensively tested in large-scale HITL simulations using general-purpose workstations to study air transportation technologies. These general purpose workstations perform multiple functions and are collectively referred to as the Multi-Aircraft Control System (MACS). Researchers at NASA Ames Research Center and Raytheon collaborated to augment the STARS platform by including CMS and FIM advisory tools to validate the feasibility of integrating these automation enhancements into the current FAA automation infrastructure. NASA Ames acquired three STARS terminal controller workstations, and then integrated the ATD-1 technologies. HITL simulations were conducted to evaluate the ATD-1 technologies when using the STARS platform. These results were compared with the results obtained when the ATD-1 technologies were tested in the MACS environment. Results collected from the numerical data show acceptably minor differences, and, together with the subjective controller questionnaires showing a trend towards preferring STARS, validate the ATD-1/STARS integration.

air traffic management↗
NASA NTRS2014

Human-Automation Cooperation for Separation Assurance in Future NextGen Environments

A 2012 Human-In-The-Loop air traffic control simulation investigated a gradual paradigm-shift in the allocation of functions between operators and automation. Air traffic controllers staffed five adjacent high-altitude en route sectors, and during the course of a two-week experiment, worked traffic under different function-allocation approaches aligned with four increasingly mature NextGen operational environments. These NextGen time-frames ranged from near current-day operations to nearly fully-automated control, in which the ground systems automation was responsible for detecting conflicts, issuing strategic and tactical resolutions, and alerting the controller to exceptional circumstances. Results indicate that overall performance was best in the most automated NextGen environment. Safe operations were achieved in this environment for twice todays peak airspace capacity, while being rated by the controllers as highly acceptable. However, results show that sector operations were not always safe; separation violations did in fact occur. This paper will describe in detail the simulation conducted, as well discuss important results and their implications.

air traffic control↗
NASA NTRS2018

Crew Resource Management for Automated Teammates (CRM-A)

Crew Resource Management (CRM) is the application of human factors knowledge and skills to ensure that teams make effective use of all resources. This includes ensuring that pilots bring in opinions of other teammates and utilize their unique capabilities. CRM was originally developed 40 years ago in response to a number of airline accidents in which the crew was found to be at fault. The goal was to improve teamwork among airline cockpit crews. The notion of "team" was later expanded to include cabin crew and ground resources. CRM has also been adopted by other industries, most notably medicine. Automation research now finds itself faced with similar issues to those faced by aviation 40 years ago: how to create a more robust system by making full use of both the automation and its human operators. With advances in machine intelligence, processing speed and cheap and plentiful memory, automation has advanced to the point that it can and should be treated as a teammate to fully take advantage of its capabilities and contributions to the system. This area of research is known as Human-Autonomy Teaming (HAT). Research on HAT has identified reusable patterns that can be applied in a wide range of applications. These patterns include features such as bi-directional communication and working agreements. This paper will explore the synergies between CRM and HAT. We believe that HAT research has much to learn from CRM and that there are benefits to expanding CRM to cover automation.

Crew Resource Management↗