Engineering Papers⌕ Search

Engineering topics

Overland, David

Publications and source records attributed to Overland, David.

7 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Interface Anywhere: Development of a Voice and Gesture System for Spaceflight Operations

The Interface Anywhere Project was funded through Innovation Charge Account (ICA) at NASA JSC in the Fall of 2012. The project was collaboration between human factors and engineering to explore the possibility of designing an interface to control basic habitat operations through gesture and voice control; (a) Current interfaces require the users to be physically near an input device in order to interact with the system; and (b) By using voice and gesture commands, the user is able to interact with the system anywhere they want within the work environment.

Thompson, Shelby↗
NASA NTRS2006

System Engineering and Integration of Controls for Advanced Life Support

The Advanced Integration Matrix (AIM) project at the Johnson Space Center (JSC) was chartered to study and solve systems-level integration issues for exploration missions. One of the first issues identified was an inability to conduct trade studies on control system architectures due to the absence of mature evaluation criteria. Such architectures are necessary to enable integration of regenerative life support systems. A team was formed to address issues concerning software and hardware architectures and system controls.. The team has investigated what is required to integrate controls for the types of non-linear dynamic systems encountered in advanced life support. To this end, a water processing bioreactor testbed is being developed which will enable prototyping and testing of integration strategies and technologies. Although systems such as the water bioreactors exhibit the complexities of interactions between control schemes most vividly, it is apparent that this behavior and its attendant risks will manifest itself among any set of interdependent autonomous control systems. A methodology for developing integration requirements for interdependent and autonomous systems is a goal of this team and this testbed. This paper is a high-level summary of the current status of the investigation, the issues encountered, some tentative conclusions, and the direction expected for further research.

Overland, David↗
NASA NTRS2005

A Data-Based Console Logger for Mission Operations Team Coordination

Concepts and prototypes1,2 are discussed for a data-based console logger (D-Logger) to meet new challenges for coordination among flight controllers arising from new exploration mission concepts. The challenges include communication delays, increased crew autonomy, multiple concurrent missions, reduced-size flight support teams that include multidisciplinary flight controllers during quiescent periods, and migrating some flight support activities to flight controller offices. A spiral development approach has been adopted, making simple, but useful functions available early and adding more extensive support later. Evaluations have guided the development of the D-Logger from the beginning and continue to provide valuable user influence about upcoming requirements. D-Logger is part of a suite of tools designed to support future operations personnel and crew. While these tools can be used independently, when used together, they provide yet another level of support by interacting with one another. Recommendations are offered for the development of similar projects.

Thronesbery, Carroll↗
NASA NTRS2004

Control System Architectures, Technologies and Concepts for Near Term and Future Human Exploration of Space

Technologies that facilitate the design and control of complex, hybrid, and resource-constrained systems are examined. This paper focuses on design methodologies, and system architectures, not on specific control methods that may be applied to life support subsystems. Honeywell and Boeing have estimated that 60-80Y0 of the effort in developing complex control systems is software development, and only 20-40% is control system development. It has also been shown that large software projects have failure rates of as high as 50-65%. Concepts discussed include the Unified Modeling Language (UML) and design patterns with the goal of creating a self-improving, self-documenting system design process. Successful architectures for control must not only facilitate hardware to software integration, but must also reconcile continuously changing software with much less frequently changing hardware. These architectures rely on software modules or components to facilitate change. Architecting such systems for change leverages the interfaces between these modules or components.

Boulanger, Richard↗
NASA NTRS2002

Creating a Team Archive During Fast-Paced Anomaly Response Activities in Space Missions

This paper describes a Web-based system to support the temporary Anomaly Response Team formed from distributed subteams in Space Shuttle and International Space Station missions. The system was designed for easy and flexible creation of small collections of files and links associated with work on a particular anomaly. The system supports privacy and levels of formality for the subteams. First we describe the supported groups and an anomaly response scenario. Then we describe the support system prototype, the Anomaly Response Tracking and Integration System (ARTIS). Finally, we describe our evaluation approach and the results of the evaluation.

Malin, Jane T.↗
NASA NTRS1987

Communications and tracking expert systems study

The original objectives of the study consisted of five broad areas of investigation: criteria and issues for explanation of communication and tracking system anomaly detection, isolation, and recovery; data storage simplification issues for fault detection expert systems; data selection procedures for decision tree pruning and optimization to enhance the abstraction of pertinent information for clear explanation; criteria for establishing levels of explanation suited to needs; and analysis of expert system interaction and modularization. Progress was made in all areas, but to a lesser extent in the criteria for establishing levels of explanation suited to needs. Among the types of expert systems studied were those related to anomaly or fault detection, isolation, and recovery.

Leibfried, T. F.↗