Search NASA⌕ Search

SEARCH · Search NASA

Results for “task management”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

Individual differences in strategic flight management and scheduling

A group of 30 instrument-rated pilots was made to fly simulator approaches to three airports under conditions of low, medium, and high workload conditions. An analysis is presently conducted of the difference in discrete task scheduling between the group of 10 highest and 10 lowest performing pilots in the sample; this categorization was based on the mean of various flight-profile measures. The two groups were found to differ from each other only in terms of the time when specific events were conducted, and of the optimality of scheduling for certain high-priority tasks. These results are assessed in view of the relative independence of task-management skills from aircraft-control skills.

Wickens, Christopher D.↗
NASA NTRS2017

The NASA Air Traffic Management Ontology: Technical Documentation

This document is intended to serve as comprehensive documentation for the NASA Air Traffic Management (ATM) Ontology. The ATM Ontology is a conceptual model that defines key classes of entities and relationships pertaining to the US National Airspace System (NAS) and the management of air traffic through that system. A wide variety of classes are represented in the ATM Ontology, including classes corresponding to flights, aircraft, manufacturers, airports, airlines, air routes, NAS facilities, air traffic control advisories, weather phenomena, and many others. The Ontology can be useful in the context of a variety of information management tasks relevant to NAS, including information exchange, data query and search, information organization, information integration, and terminology standardization.

information management↗
DOE OSTI2025

SWARM: Reimagining scientific workflow management systems in a distributed world

Modern scientific workflows process massive amounts of data from diverse instruments and sensors, leveraging geographically distributed, heterogeneous compute and storage resources—from leadership-class systems to edge devices—connected by high-performance networks. The diversity of resources introduces challenges in harnessing their full potential, with resilience issues arising across applications, system software, networks, storage, and hardware. Today, workflow management systems (WMS) coordinate the execution of computation and data management tasks across target resources. However, WMS’s centralized nature makes them vulnerable to faults and scalability issues that may result in failures of entire computational campaigns. In conclusion, this paper introduces a novel agentic framework for workflow management, fully distributing and decentralizing the WMS functions and modeling them as swarm intelligence agents infused with advanced artificial intelligence solutions and traditional distributed computing algorithms that can make coordinated decisions in the presence of failures of the underlying cyberinfrastructure.

Swarm intelligence↗
NASA NTRS2006

X-Windows Socket Widget Class

The X-Windows Socket Widget Class ("Class" is used here in the object-oriented-programming sense of the word) was devised to simplify the task of implementing network connections for graphical-user-interface (GUI) computer programs. UNIX Transmission Control Protocol/Internet Protocol (TCP/IP) socket programming libraries require many method calls to configure, operate, and destroy sockets. Most X Windows GUI programs use widget sets or toolkits to facilitate management of complex objects. The widget standards facilitate construction of toolkits and application programs. The X-Windows Socket Widget Class encapsulates UNIX TCP/IP socket-management tasks within the framework of an X Windows widget. Using the widget framework, X Windows GUI programs can treat one or more network socket instances in the same manner as that of other graphical widgets, making it easier to program sockets. Wrapping ISP socket programming libraries inside a widget framework enables a programmer to treat a network interface as though it were a GUI.

Barry, Matthew R.↗
NASA NTRS1996

The Integrated Mode Management Interface

Mode management is the processes of understanding the character and consequences of autoflight modes, planning and selecting the engagement, disengagement and transitions between modes, and anticipating automatic mode transitions made by the autoflight system itself. The state of the art is represented by the latest designs produced by each of the major airframe manufacturers, the Boeing 747-400, the Boeing 777, the McDonnell Douglas MD-11, and the Airbus A320/A340 family of airplanes. In these airplanes autoflight modes are selected by manipulating switches on the control panel. The state of the autoflight system is displayed on the flight mode annunciators. The integrated mode management interface (IMMI) is a graphical interface to autoflight mode management systems for aircraft equipped with flight management computer systems (FMCS). The interface consists of a vertical mode manager and a lateral mode manager. Autoflight modes are depicted by icons on a graphical display. Mode selection is accomplished by touching (or mousing) the appropriate icon. The IMMI provides flight crews with an integrated interface to autoflight systems for aircraft equipped with flight management computer systems (FMCS). The current version is modeled on the Boeing glass-cockpit airplanes (747-400, 757/767). It runs on the SGI Indigo workstation. A working prototype of this graphics-based crew interface to the autoflight mode management tasks of glass cockpit airplanes has been installed in the Advanced Concepts Flight Simulator of the CSSRF of NASA Ames Research Center. This IMMI replaces the devices in FMCS equipped airplanes currently known as mode control panel (Boeing), flight guidance control panel (McDonnell Douglas), and flight control unit (Airbus). It also augments the functions of the flight mode annunciators. All glass cockpit airplanes are sufficiently similar that the IMMI could be tailored to the mode management system of any modern cockpit. The IMMI does not replace the functions of the FMCS control and display unit. The purpose of the INMI is to provide flight crews with a shared medium in which they can assess the state of the autoflight system, take control actions on it, reason about its behavior, and communicate with each other about its behavior. The design is intended to increase mode awareness and provide a better interface to autoflight mode management. This report describes the IMMI, the methods that were used in designing and developing it, and the theory underlying the design and development processes.

Hutchins, Edwin↗
NASA NTRS1990

Spacecraft command verification: The AI solution

Recently, a knowledge-based approach was used to develop a system called the Command Constraint Checker (CCC) for TRW. CCC was created to automate the process of verifying spacecraft command sequences. To check command files by hand for timing and sequencing errors is a time-consuming and error-prone task. Conventional software solutions were rejected when it was estimated that it would require 36 man-months to build an automated tool to check constraints by conventional methods. Using rule-based representation to model the various timing and sequencing constraints of the spacecraft, CCC was developed and tested in only three months. By applying artificial intelligence techniques, CCC designers were able to demonstrate the viability of AI as a tool to transform difficult problems into easily managed tasks. The design considerations used in developing CCC are discussed and the potential impact of this system on future satellite programs is examined.

Fesq, Lorraine M.↗
NASA NTRS1990

Beyond the Baseline: Proceedings of the Space Station Evolution Symposium: Space Station Freedom Advanced Development Program - Volume 2, Part 2

This report contains the individual presentations delivered at the Space Station Evolution Symposium in League City, Texas on February 6, 7, 8, 1990. Personnel responsible for Advanced Systems Studies and Advanced Development within the Space Station Freedom program reported on the results of their work to date. Systems Studies presentations focused on identifying the baseline design provisions (hooks and scars) necessary to enable evolution of the facility to support changing space policy and anticipated user needs. Also emphasized were evolution configuration and operations concepts including on-orbit processing of space transfer vehicles. Advanced Development task managers discussed transitioning advanced technologies to the baseline program, including those near-term technologies which will enhance the safety and productivity of the crew and the reliability of station systems. Special emphasis was placed on applying advanced automation technology to ground and flight systems. This publication consists of two volumes. Volume 1 contains the results of the advanced system studies with the emphasis on reference evolution configurations, system design requirements and accommodations, and long-range technology projections. Volume 2 reports on advanced development tasks within the Transition Definition Program. Products of these tasks include: engineering fidelity demonstrations and evaluations on Station development testbeds and Shuttle-based flight experiments; detailed requirements and performance specifications which address advanced technology implementation issues; and mature applications and the tools required for the development, implementation, and support of advanced technology within the Space Station Freedom Program.

Source record↗
NASA NTRS1988

Development and demonstration of an on-board mission planner for helicopters

Mission management tasks can be distributed within a planning hierarchy, where each level of the hierarchy addresses a scope of action, and associated time scale or planning horizon, and requirements for plan generation response time. The current work is focused on the far-field planning subproblem, with a scope and planning horizon encompassing the entire mission and with a response time required to be about two minutes. The far-feld planning problem is posed as a constrained optimization problem and algorithms and structural organizations are proposed for the solution. Algorithms are implemented in a developmental environment, and performance is assessed with respect to optimality and feasibility for the intended application and in comparison with alternative algorithms. This is done for the three major components of far-field planning: goal planning, waypoint path planning, and timeline management. It appears feasible to meet performance requirements on a 10 Mips flyable processor (dedicated to far-field planning) using a heuristically-guided simulated annealing technique for the goal planner, a modified A* search for the waypoint path planner, and a speed scheduling technique developed for this project.

Deutsch, Owen L.↗
NASA NTRS2010

Simulation Training Versus Real Time Console Training for New Flight Controllers

For new flight controllers, the two main learning tools are simulations and real time console performance training. These benefit the new flight controllers in different ways and could possibly be improved. Simulations: a) Allow for mistakes without serious consequences. b) Lets new flight controllers learn the working style of other new flight controllers. c) Lets new flight controllers eventually begin to feel like they have mastered the sim world, so therefore they must be competent in the real time world too. Real time: a) Shows new flight controllers some of the unique problems that develop and have to be accounted for when dealing with certain payloads or systems. b) Lets new flight controllers experience handovers - gathering information from the previous shift on what the room needs to be aware of and what still needs to be done. c) Gives new flight controllers confidence that they can succeed in the position they are training for when they can solve real anomalies. How Sims could be improved and more like real-time ops for the ISS Operations Controller position: a) Operations Change Requests to review. b) Fewer anomalies (but still more than real time for practice). c) Payload Planning Manager Handover sheet for the E-1 and E-3 reviews. d) Flight note in system with at least one comment to verify for the E-1 and E-3 reviews How the real time console performance training could be improved for the ISS Operations Controller position: a) Schedule the new flight controller to be on console for four days but with a different certified person each day. This will force them to be the source of knowledge about every OCR in progress, everything that has happened in those few days, and every activity on the timeline. Constellation program flight controllers will have to learn entirely from simulations, thereby losing some of the elements that they will need to have experience with for real time ops. It may help them to practice real time console performance training in the International Space Station or Space Shuttle to gather some general anomaly resolution and day-to-day task management skills.

Heaton, Amanda↗
NASA NTRS2002

Reusable Autonomy

Currently, spacecraft ground systems have a well defined and somewhat standard architecture and operations concept. Based on domain analysis studies of various control centers conducted over the years it is clear that ground systems have core capabilities and functionality that are common across all ground systems. This observation alone supports the realization of reuse. Additionally, spacecraft ground systems are increasing in their ability to do things autonomously. They are being engineered using advanced expert systems technology to provide automated support for operators. A clearer understanding of the possible roles of agent technology is advancing the prospects of greater autonomy for these systems. Many of their functional and management tasks are or could be supported by applied agent technology, the dynamics of the ground system's infrastructure could be monitored by agents, there are intelligent agent-based approaches to user-interfaces, etc. The premise of this paper is that the concepts associated with software reuse, applicable in consideration of classically-engineered ground systems, can be updated to address their application in highly agent-based realizations of future ground systems. As a somewhat simplified example consider the following situation, involving human agents in a ground system context. Let Group A of controllers be working on Mission X. They are responsible for the command, control and health and safety of the Mission X spacecraft. Let us suppose that mission X successfully completes it mission and is turned off. Group A could be dispersed or perhaps move to another Mission Y. In this case there would be reuse of the human agents from Mission X to Mission Y. The Group A agents perform their well-understood functions in a somewhat but related context. There will be a learning or familiarization process that the group A agents go through to make the new context, determined by the new Mission Y, understood. This simplified scenario highlights some of the major issues that need to be addressed when considering the situation where Group A is composed of software-based agents (not their human counterparts) and they migrate from one mission support system to another. This paper will address: - definition of an agent architecture appropriate to support reuse; - identification of non-mission-specific agent capabilities required; - appropriate knowledge representation schemes for mission-specific knowledge; - agent interface with mission-specific knowledge (a type of Learning); development of a fully-operational group of cooperative software agents for ground system support; architecture and operation of a repository of reusable agents that could be the source of intelligent components for realizing an autonomous (or nearly autonomous) agent-based ground system, and an agent-based approach to repository management and operation (an intelligent interface for human use of the repository in a ground-system development activity).

Truszkowski, Walt↗
DOE OSTI2024

Building a Simplistic Automatic Extruder: Instrument Development Opportunities for the Laboratory

This work presents an automatic extruder as a research experience for undergraduate students. The system offers a user-friendly approach to preparing vesicles, such as liposomes or polymersomes, with a defined size and polydispersity properties crucial for research in biology and macromolecules. It comprises two syringe pumps connected by a membrane filter. The setup is controlled by software. Compared to manual extrusion, this automated system provides advantages, such as precisely controlled variables. The project describes a tool to enhance undergraduate learning in science and engineering laboratories. Building an automatic extruder serves as a simplified model of a complex industrial process. It offers a clear advantage: automating a well-understood manual extrusion process. To make this project accessible, it is broken down into three manageable tasks: software development, hardware assembly, and testing procedures. This breakdown describes the software created, the hardware components used, and the testing procedures conducted for this project. All project data, including software code, testing data, and procedures, are freely available online. This allows undergraduate students to not only begin their own projects but also contribute to this educational instrument’s ongoing development.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗
NASA NTRS1975

Earth resources experiments and results

One of the major objectives of the Skylab Program was to investigate the feasibility of addressing the techniques of resource management through the use of remote sensors from a space platform. To accomplish these investigations, a package of broad-spectrum remote sensors was devised to investigate the extent to which surface features could be interpreted for potential use in understanding and managing the earth's resources. This paper will describe the total system capability needed to accomplish the resource management task; and, for a few specific examples, indicate how the results of EREP will contribute to the on-going development of the total resources system.

Zarcaro, J. G.↗
NASA NTRS1976

Data management in pattern recognition and image processing systems

Data management considerations are important to any system which handles large volumes of data or where the manipulation of data is technically sophisticated. A particular problem is the introduction of image-formatted files into the mainstream of data processing application. This report describes a comprehensive system for the manipulation of image, tabular, and graphical data sets which involve conversions between the various data types. A key characteristic is the use of image processing technology to accomplish data management tasks. Because of this, the term 'image-based information system' has been adopted.

Zobrist, A. L.↗
NASA NTRS1979

Wildlife monitoring program plan

A plan for integrating the various requirements for wildlife monitoring with modern aerospace technology is presented. This plan is responsive to user needs, recognizes legal requirements, and is based on an evolutionary growth from domestic animals and larger animals to smaller, more scarce and remote species. The basis for animal study selection was made from the 1973 Santa Cruz Summer Study on Wildlife Monitoring. As techniques are developed the monitoring and management tasks will be interfaced with and eventually operated by the user agencies. Field efforts, aircraft and satellites, will be supplemented by laboratory investigations. Sixty percent of the effort will be in hardware research and development (satellite technology, microminiaturization) and the rest for gathering and interpreting data.

Sebesta, P.↗
NASA NTRS1980

User's guide to SFTRAN

Structured programming language has been given new features and some limitations are removed. Language runs more efficiently, and concepts of top down development and modularity are extended to task management.

Fessler, T. E.↗
NASA NTRS1980

The work breakdown structure in software project management

A work breakdown structure (WBS) is defined as an enumeration of all work activities in hierarchic refinement of detail which organizes work to be done into short manageable tasks with quantifiable inputs, outputs, schedules, and assigned responsibilities. Some of the characteristics and benefits of the WBS are reviewed, and ways in which these can be developed and applied in software implementation projects are discussed. Although the material is oriented principally toward new-software production tasks, many of the concepts are applicable to continuing maintenance and operations tasks.

Tausworthe, R. C.↗
NASA NTRS1981

On the use of corresponding orbitals in the calculation of nonorthogonal transition moments

Full valence and first-order CI wave functions are invariant with respect to unitary transformations among the valence orbitals. We exploit this degree of freedom and show that by transforming the valence orbitals into a corresponding orbital basis, nonorthogonal transition moment calculations become an easily managed task. Sample full valence calculations on several states of O2(+) and OF are also presented.

Lengsfield, B. H., III↗