SEARCH · Search NASA

Results for “automated transit”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 73 records · Page 4

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

Manual Crew Override of Vehicle Landings Following G-Transitions

BACKGROUND Manual control during exploration spaceflight consists of both planned automated supervisory control and unplanned crew override. This crew override capability is critical to enable overall mission success during landing contingencies. However, the introduction of manual override capabilities must be implemented to enable crews to mitigate risks introduced by human error. Adaptive changes in the sensorimotor system can manifest during g-transitions as spatial disorientation. While training and landing aids enable successful landing through disorientation, these adaptive changes may increase cognitive demand that needs to be accounted for in the manual control strategy. It is important to characterize these effects as soon as possible following the G-transition to develop appropriate countermeasures. METHODS The following study seeks to inform the risk associated with altered sensorimotor and vestibular function impacting critical mission tasks. We aim to characterize the effects of short and long-duration weightlessness on manual control following G-transitions using simulated lunar landing on a six-degree-of-freedom (6DOF) motion base, a fixed base simulation, and a supervisory control tablet task. The primary goal is to understand the impact of spaceflight on crew ability to perform manual crew override and supervisory control. This aim will be assessed by comparing pre- versus postflight simulation performance in crewmembers assigned to either short duration (< 30 day) or long duration (~6- month) missions to the International Space Station (ISS). We hypothesize there will be postflight increases in the percent time that pilots are outside of the acceptable range for recommended vehicle state parameters and the reaction time for secondary cognitive tasks. Ground-based control subjects, who are demographically matched to the crew considering age (± 5 years) and gender, will undergo the same testing schedule as the crew to examine the effects of flight phase independent of microgravity exposure. The second aim is to examine how adaptive changes in vestibular and cognitive function relate to changes in manual crew override proficiency. Crew performance for a sensorimotor perceptual test battery will evaluate motion perception tracking, roll nulling, and/or vection sensitivity using the 6DOF motion base. We hypothesize that a higher severity of vestibular alterations will be associated with increased percent time outside of guidance limits. Motion sickness severity and sleepiness will also be evaluated. To determine the impact of “just-in-time” training, the third aim seeks to compare performance during on-board lunar landing tasks conducted late in-flight to early postflight. We hypothesize that proficiency on the “just-in-time” laptop trainer late in mission will be positively correlated with early postflight proficiency on the same task. The final aim will establish assessments of performance, training protocols, and the learning progression in a ground-control cohort of first-time users. RESULTS The assessment of the learning progression associated with the piloting task on the motion base system with thirty ground subjects will be reported. Learning curves will be established across four distinct sessions and within session considering trial difficulty. The difficulty of the landing task can be modulated with the landing divert distance and cross or downrange difficulty. Results may include changes in performance across multiple trials of a multi-attribute lunar tablet supervisory control task. Preliminary investigations of eighteen subjects who completed vestibular threshold and motion perception tasks offer expected performance ranges for upcoming preflight crew evaluations. The results yielded an average roll threshold of 0.46 ± 0.30 deg/s and an average roll nulling root mean square error performance of 2.52 ± 0.52 deg/s. RELEVANCE This project will deliver an operational demonstration of crew monitoring capability following spaceflight and identify potential deficits that may require remediation. Comparison of individual vestibular and cognitive changes with crew performance will help better characterize the manual control risks associated with sensorimotor alterations. Ground testing will evaluate learning progression, refine training protocols, and serve as a control cohort for comparisons to crew performance. ACKNOWLEDGEMENTS: The authors acknowledge contributions from Draper, the Dynamic Skills Trainer (DST) Lab, and the Software, Robotics, and Simulation Division toward the development of the lunar landing simulation platforms. This project is funded by the Human Health Countermeasures Element.

Hannah M. Weiss↗

NASA NTRS2024

Operational Integration Assessment (OIA) of Midterm UAM Operations: Class C Airspace Tabletop Exercise and Integration Checkpoint

The National Aeronautics and Space Administration (NASA), in collaboration with the Federal Aviation Administration (FAA), is conducting research into evolving today’s air traffic management system towards a more automated and operationally flexible airspace to accommodate Urban Air Mobility (UAM) operations at scale. UAM operations, enabled by electric Vertical Takeoff and Landing (eVTOL) aircraft, may change the role of aviation in the movement of people and goods and provide practical, cost-effective air transport in metropolitan areas. FAA UAM Concept of Operations v2.0 describes three evolutionary stages of UAM operations: Initial, Midterm, and Mature State operations. Midterm operations are comprised of many complex changes to the national airspace system (NAS). The Operational Integration Assessment (OIA) was created as a capability to address the need to study the progression and identify interdependencies of those changes that may occur during the midterm UAM operations timeframe. The OIA includes a series of tabletop exercises and integration checkpoints planned to explore various use cases from end-to-end, evaluated by NASA’s Air Traffic Management eXploration (ATM-X) project in partnership with the FAA’s William J. Hughes Technical Center (WJHTC) and industry partners. The use cases were exercised in an immersive, integrated live-virtual-constructive (LVC) airspace simulation environment, called the NASA/FAA Laboratory Integrated Test Environment (NFLITE), as part of an effort to learn how UAM operations can scale beyond the as-is NAS and through the transition to higher-tempo and highly automated operations of the future. This document describes the events of the tabletop exercise held from January 24-26, 2023, at the National Airspace Research & Technology Park (NARTP) in Egg Harbor Township, New Jersey, adjacent to the WJHTC and the subsequent integration checkpoint performed on March 28, 2023,at NASA Langley Research Center (LaRC) in Hampton, Virginia.

UAM↗

NASA NTRS2012

Automation of Hubble Space Telescope Mission Operations

On June 13, 2011, after more than 21 years, 115 thousand orbits, and nearly 1 million exposures taken, the operation of the Hubble Space Telescope successfully transitioned from 24x7x365 staffing to 815 staffing. This required the automation of routine mission operations including telemetry and forward link acquisition, data dumping and solid-state recorder management, stored command loading, and health and safety monitoring of both the observatory and the HST Ground System. These changes were driven by budget reductions, and required ground system and onboard spacecraft enhancements across the entire operations spectrum, from planning and scheduling systems to payload flight software. Changes in personnel and staffing were required in order to adapt to the new roles and responsibilities required in the new automated operations era. This paper will provide a high level overview of the obstacles to automating nominal HST mission operations, both technical and cultural, and how those obstacles were overcome.

Burley, Richard↗

NASA NTRSDate not supplied

A Human-In-The-Loop Simulation for Urban Air Mobility in the Terminal Area

In this paper researchers propose a human-in-the-loop experiment to study human performance when tasked with tactical deconfliction in terminal area air taxi operations. The air taxi operations being considered herein are an advanced air transportation concept called Urban Air Mobility (UAM). The UAM concept aims to support not only air taxi operations, but also package delivery and emergency response among other use cases. The key innovation over current air transportation lies with the introduction of highly automated aircraft and air traffic management systems. Development of the UAM system will include transitional midterm phases where some operational services will be provided by a mixture of automation and human actors. Midterm operations present a unique challenge, since the scope of responsibility of automated systems is largely undefined, suggesting the need for direct human participation with little to inform how much human intervention is necessary. Here it is assumed that traffic management responsibilities require coordination between human actors and automated systems and focus on arrival flows for midterm operations. In the proposed human-in-the-loop simulation, virtual UAM traffic is strategically deconflicted by a Provider of Services for UAM at departure, then tactically managed by a human at the arrival facility. Generated traffic consists of UAM participants flying in UAM exclusive airspace structures, thus isolated from traditional traffic. The human operator is tasked with managing spacing of arrival traffic and executing speed adjustments as deemed necessary. Researchers propose the investigation of three levels of automation assistance: 1) no assistance; 2) spacing violation detection; 3) spacing violation detection and speed adjustment recommendations. Quantitative measures like throughput and delay are used to assess the human's capacity for accommodating airborne delays. Qualitative evaluations such as surveys and open-ended feedback are used to gain insight into human factors. These factors could introduce additional capacity constraints on traffic, independent of physical or technical constraints. Although findings for this study will not be reported as the study has not yet been executed, the authors conclude with potential outcomes informed by previous simulations in the literature and suggestions for the structure and procedures of midterm human-automation air traffic management.

UAM↗

NASA NTRS2018

Robots and Robots and More

Over the course of this year I worked on several projects across different departments, from physical robots at Swamp Works, to automated robots running functional tests on launch critical Graphical User Interfaces (GUIs). My overarching project this year was designing a new automated testing framework. It began with becoming familiar with the existing automated testing framework, which used image matching to perform programmatic GUI testing. After writing a few dozen tests with the existing framework, I was able to identify the strengths and weaknesses of the system and begin the search for another tool to replace it. I ended up selecting an open source library, which I modified to fit both National Aeronautics and Space Administration (NASA) requirements and those of the specific Computer Software Configuration Item (CSCI) I worked on. After the new framework was feature-rich enough to meet the team requirements, I helped roll out the changes, managed the transition to the new framework, and directed continuing automation work in regards to the library. The result was a comprehensive new way of efficiently testing the GUI that was robust enough to handle small changes to the GUI itself. Additionally, for approximately six weeks I worked on rebuilding, repairing, and updating the software of four "Swarmie" robots for a NASA event. By the close of the six weeks, the four robots were operational and had improved obstacle detection software that solved a faulty stop signal issue that the robots were experiencing.

Siegel, Alex↗

NASA NTRS2016

Transitioning Autonomous Systems Technology Research to a Flight Software Environment

NASA has developed methods and algorithms for autonomous spacecraft operations,including automated planning and scheduling, fault diagnostics and impact determination,procedure management and display. Making the transition from technology research tooperational flight software requires overcoming significant technical, programmatic andcultural challenges. Technology research is aimed at developing methods that performspecific functions correctly, but the resulting software may not be designed for flightprocessors with limited CPU, memory and network resources, and may not be easilyintegrated into spacecraft flight software. Our objective in the Autonomous Systems andOperations Project is to make significant strides toward the transformation from technologyto operational use. Our focus was twofold: maturing research grade autonomy software intoa flight software environment using broadly accepted languages and tools; and integratingautonomy applications with each other and with representative systems and their data andcommand interfaces. For a target flight software environment, we chose Core FlightSoftware, developed by Goddard Space Flight Center as a common operating systemindependent framework. Our hardware integration environment was provided by theIntegrated Power and Avionics Systems (iPAS) Lab at Johnson Space Center, in whichvarious subsystem development has been conducted to address engineering challenges forthe vehicles and systems required for long-duration missions into the solar system. The iPASand its network of connected facilities provides realistic subsystem hardware or simulationsof spacecraft power, life support, guidance, navigation and control, and command and datahandling subsystems. Interfaces between autonomy applications and the subsystems beingassessed and controlled were developed, assessed and refined. The hardware and softwareenvironment using CFS and the iPAS facility has proven to be a highly flexible and realisticenvironment in which to rapidly integrate applications in an iterative, low cost setting. Usingthe integration environment we have developed, we will turn our focus to performance andsizing analysis to determine the computational requirements for full-scale deployment ofautonomy technology. Scalability of reasoners and the spacecraft models upon which theyoperate, and robustness across the full range of spacecraft conditions and environments willbe explored and improved. We are making significant contributions to the future programsthat will build the spacecraft that will take humans beyond the Earth-Moon system, in whichprogram Systems Engineers will be able to accurately and confidently design in accurate,robust and mature autonomous operations systems.

Flight Software↗

NASA NTRS2013

Combined Cycle Engine Large-Scale Inlet for Mode Transition Experiments: System Identification Rack Hardware Design

The System Identification (SysID) Rack is a real-time hardware-in-the-loop data acquisition (DAQ) and control instrument rack that was designed and built to support inlet testing in the NASA Glenn Research Center 10- by 10-Foot Supersonic Wind Tunnel. This instrument rack is used to support experiments on the Combined-Cycle Engine Large-Scale Inlet for Mode Transition Experiment (CCE‒ LIMX). The CCE‒LIMX is a testbed for an integrated dual flow-path inlet configuration with the two flow paths in an over-and-under arrangement such that the high-speed flow path is located below the lowspeed flow path. The CCE‒LIMX includes multiple actuators that are designed to redirect airflow from one flow path to the other; this action is referred to as "inlet mode transition." Multiple phases of experiments have been planned to support research that investigates inlet mode transition: inlet characterization (Phase-1) and system identification (Phase-2). The SysID Rack hardware design met the following requirements to support Phase-1 and Phase-2 experiments: safely and effectively move multiple actuators individually or synchronously; sample and save effector control and position sensor feedback signals; automate control of actuator positioning based on a mode transition schedule; sample and save pressure sensor signals; and perform DAQ and control processes operating at 2.5 KHz. This document describes the hardware components used to build the SysID Rack including their function, specifications, and system interface. Furthermore, provided in this document are a SysID Rack effectors signal list (signal flow); system identification experiment setup; illustrations indicating a typical SysID Rack experiment; and a SysID Rack performance overview for Phase-1 and Phase-2 experiments. The SysID Rack described in this document was a useful tool to meet the project objectives.

Thomas, Randy↗

NASA NTRSDate not supplied

Simplified Vehicle Control Concept for a Lift Plus Cruise eVTOL Vehicle

Electric Vertical Takeoff and Landing (eVTOL) vehicles have the potential to enable cost effective Urban Air Mobility (UAM) applications. These concepts may also pose several challenging handling and control problems, which must be addressed prior to safe and reliable urban operations. This paper investigates a simplified vehicle control concept that is designed to address some of these challenges for a conceptual Lift Plus Cruise vehicle designed by NASA’s Revolutionary Vertical Lift Technology (RVLT) project. The command and control architecture for this concept is presented along with preliminary findings. Initial results explore the vehicle performance in an approach to hover transition scenario, designed to explore the challenge of dissipating energy across all flight regimes. Operational concepts with varying aggressiveness are evaluated through changing glideslope and deceleration rates. Preliminary results show that the simplified control concept is effective over these operational conditions, with control strategies and envelope protection limits able to maintain control though aggressive operations despite saturation at steeper slopes with higher deceleration rates. Final results will show piloted simulation evaluations in the the Aerospace Cognitive Engineering Lab – Rapid Automation Test Environment (ACEL-RATE) laboratory at NASA Ames Research Center. The planned tests will build on these operations with additional test cases exploring variations in wind conditions as well as transition-to-hover automation strategies and display information.

simplified vehicle control↗

NASA NTRS2008

Increasing the Cost-efficiency of the DSN

JPL has operated the Deep Space Network (DSN) on behalf of NASA since the 1960's. Over the last two decades, the DSN budget has generally declined in real-year dollars while the aging assets required more attention, and the missions became more complex. As a result, the budget has been increasingly consumed by Operations and Maintenance (O and M), significantly reducing the funding wedge available for technology investment and for enhancing the DSN capability and capacity. Responding to this budget squeeze, the DSN launched an effort to improve the cost-efficiency of the O and M. In this paper we: Analyze the components of O&M. We note for example that, for the DSN, less than 20% of the staff engage in the traditional human-in-front-a-console role, so any effort to increase the cost efficiency must go beyond reducing the number of "Real-time operators." Explain the underlying organizational and cultural structures. Any cost-efficiency activities changes either accept, or carefully modify these structures. For example, the DSN O&M is based on the concept that there are three nearly identical antenna complexes separated by approximately 1200 in latitude and that each antenna complex is operated by a different contractor (driven by international agreements). Explore planned changes in the customer interface, e.g. web-based automated scheduling, and the processes required for a transition. Changes have to be evaluated in the larger end-to-end context, e.g. do the changes provide a net cost-efficiency for the DSN and the missions, or do they merely shift cost from the DSN to the missions. Consider possible significant changes in real-time pass management, e.g. full-remoting of operations, and lights-dim operations, while maintaining (or improving) the performance metrics of the DSN. Investigate how procedural and administrative changes could increase cost-efficiency, in conjunction with changes in the customer interfaces and real-time pass management. Examples would be handling of inter-governmental agreements, improved sharing of resources with other agencies, and better use of commercial (rather than government) resources

Deep Space Network (DSN)↗

NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗

NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.↗

NASA NTRSDate not supplied

Remote Pilot Handoffs in Large UAS Multi-Vehicle Operations: Best Practices and Supportive Technologies

In response to pilot shortages and increasing air cargo demands, NASA's Pathfinding for Airspace with Autonomous Vehicles (PAAV) sub-project conducted the fourth in a series of tabletop studies investigating scalable solutions for integrating large Uncrewed Aircraft Systems (UAS) into the National Airspace System (NAS). This study solicited subject matter expertise to identify solutions to potential challenges for a further term vision, guiding participants through scenario-based discussions where the remote pilot (RP)-to-vehicle ratio has been scaled from 1:1 to m:N. Of those challenges, remote pilot handoffs were found throughout all phases of flight, both in nominal and non-nominal scenarios. The current paper details participant-suggested procedural and technological solutions for overcoming the handoff challenge, including determining the accepting RP, which aircraft to release, the location and timing of the transition, and options for supporting personnel, tools, and automation that could facilitate safe and efficient handoffs.

unmanned aircraft systems (UAS)↗

NASA NTRSDate not supplied

Remote Pilot Handoffs in Large UAS Multi-Vehicle Operations: Best Practices and Supportive Technologies

uncrewed aircraft systems↗

NASA NTRSDate not supplied

Supervisory Control with Dual Tasking in Post G-Transition Vehicle Landings

BACKGROUND Landing during exploration spaceflight may consist of both planned automated supervisory control and unplanned crew override. Supervisory control, particularly when performed under cognitive load with additional monitoring tasks, is essential for ensuring overall mission success during landing contingencies. Evaluating performance in a relevant Human Landing System (HLS) supervisory landing task after long-duration microgravity exposure can help identify potential risks from human error and sensorimotor alterations. Adaptive changes in the sensorimotor system can manifest during g-transitions as spatial disorientation. Although training and landing aids facilitate successful landings despite disorientation, these adaptive changes may heighten cognitive demand, which must be considered in the landing strategy. It is important to characterize these effects as soon as possible following the G-transition while the sensorimotor system remains in a state of adaptive flux to inform appropriate countermeasures. METHODS A Multi-attribute Lunar Table Battery (MALTB) task was developed for an iOS tablet device to provide flexible crew testing and training capabilities in-flight and on the ground. Elements of the tablet task were derived from the Multi-Attribute Task Battery (MATB, Cegarra et al. 2020). The task requires crew members to study a map of a planned landing site and memorizing the terrain and surface landmarks to inform potential divert maneuvers during landing. The user will oversee a series of approaches through touchdown simulations on the tablet with an external camera view of the Lunar surface. The primary responsibility of the crew member will be to execute a divert if the guidance recommended site is erroneous (e.g., the guidance projected landing target is not within 10m of the planned landing site center), or the projected landing site is no longer suitable due to surface obstacles. Considering vehicle maneuverability and fuel reserves, the divert capabilities will diminish as the task progresses. In cases where a divert is initiated, a new landing target will need to be designated by the user and will be evaluated for the proximity to the original pre-planned site. A secondary operational monitoring task will challenge the user's cognitive reserve by requiring the user to maintain several gauges within acceptable limits and respond to a visual indicator while completing the landing approach. Outcome measures include distance from the planned landing site to the user-initiate divert landing location, ground slope at the new landing site, time to divert, the ability to accomplish the secondary monitoring tasks, and perceived workload. The tablet task is being evaluated in a ground-based study to determine the learning effect of first-time users. The tablet task will be utilized in a flight study to test performance multiple times postflight. Future potential testing in-flight have been identified for capsules with iOS tablet devices. Multi-attribute Lunar Table Battery Task MALTB comprises video footage of thirty distinct landing conditions. The landing scenarios feature various landing sites (n = 3), hazardous object sizes (n = 6), sun azimuth degrees (n = 4), camera modes (i.e., fixed or gimbaled), and navigation bias (i.e., true or false). Each seventy second trial uses a sixty-degree constant glideslope trajectory. The application architecture and layout include user identification setup and data storing, a guided walkthrough of the task and interface components, practice mode for task familiarization, and a modified Bedford workload scale administered following task completion. The time-based dependent measures are saved locally to the iOS Files application and post-processing scripts have been developed to evaluate the remaining measures of performance. RELEVANCE This project will deliver an operational demonstration of crew monitoring capability following spaceflight and identify potential deficits that may require remediation. Comparison of individual vestibular and cognitive changes with crew performance will help better characterize the landing risks associated with sensorimotor alterations. ACKNOWLEDGEMENTS: This project is funded by NASA’s Human Research Program Human Health Countermeasures Element. REFERENCES Cegarra J, Valery B, Avril E, Calmettes C, Navarro J (2020) OpenMATB: A Multi-Attribute Task Battery promoting task customization, software extensibility and experiment replicability. Behav Res Methods 52:1980-1990 doi: 10.3758/s13428-020-01364-w

Matthew McDonnell↗

NASA NTRS2011

Allocation of Functions in a Far-Term Air Traffic Control Environment

A human-in-the-loop exploration of a ground-based automated separation assurance concept was conducted that involved the allocation of certain functions between humans and automation. This exploration included operations that were sustained for prolonged periods of time with high levels of traffic in the presence of convective weather and scheduling constraints. An investigation into the acceptability of the defined roles and performance of tasks was conducted where it was found that the participants rated the concept and allocation of functions with a high level of acceptability. However, issues were encountered with the automation related to the detection of and response to tactical conflicts. Lower ratings were given on account of these concerns, and it was found that a key contributor to the underlying problems was transitioning aircraft and the uncertainty of their trajectories. Stemming from those results, participants responded that they would rather have direct control over aircraft transitions as well as more control over the tactical conflict resolution automation. In contrast, participants responded that they would rather have the automation place aircraft back on trajectory, and perform weather avoidance and scheduling tasks.

Homola, Jeffrey↗

NASA NTRS1995

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↗

NASA NTRS1996

State modeling and pass automation in spacecraft control

The integrated monitoring and control commercial off-the-shelf system (IMACCS), which demonstrates the feasibility of automating spacecraft monitoring and control activities through the use of state modeling, is described together with its use. The use of the system for the control and ground support of the solar, anomalous and magnetic particle explorer (SAMPEX) spacecraft is considered. A key component of IMACCS is the Altair mission control system which implements finite state modeling as an element of its expert system capability. Using the finite state modeling and state transition capabilities of the Altair mission control system, IMACCS features automated monitoring, routine pass support, anomaly resolution and emergency 'lights on again' response. Automatic orbit determination and the production of typical flight dynamics products exists. These functionalities are described.

Klein, J.↗

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↗