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 415 records · Page 23
All sourcesNASA NTRSDOE OSTI
NASA NTRS1985

Digital processing of mesoscale analysis and space sensor data

The mesoscale analysis and space sensor (MASS) data management and analysis system on the research computer system is presented. The MASS data base management and analysis system was implemented on the research computer system which provides a wide range of capabilities for processing and displaying large volumes of conventional and satellite derived meteorological data. The research computer system consists of three primary computers (HP-1000F, Harris/6, and Perkin-Elmer 3250), each of which performs a specific function according to its unique capabilities. The overall tasks performed concerning the software, data base management and display capabilities of the research computer system in terms of providing a very effective interactive research tool for the digital processing of mesoscale analysis and space sensor data is described.

Hickey, J. S.↗
NASA NTRS2002

Shuttle Abort Flight Management (SAFM) - Application Overview

One of the most demanding tasks that must be performed by the Space Shuttle flight crew is the process of determining whether, when and where to abort the vehicle should engine or system failures occur during ascent or entry. Current Shuttle abort procedures involve paging through complicated paper checklists to decide on the type of abort and where to abort. Additional checklists then lead the crew through a series of actions to execute the desired abort. This process is even more difficult and time consuming in the absence of ground communications since the ground flight controllers have the analysis tools and information that is currently not available in the Shuttle cockpit. Crew workload specifically abort procedures will be greatly simplified with the implementation of the Space Shuttle Cockpit Avionics Upgrade (CAU) project. The intent of CAU is to maximize crew situational awareness and reduce flight workload thru enhanced controls and displays, and onboard abort assessment and determination capability. SAFM was developed to help satisfy the CAU objectives by providing the crew with dynamic information about the capability of the vehicle to perform a variety of abort options during ascent and entry. This paper- presents an overview of the SAFM application. As shown in Figure 1, SAFM processes the vehicle navigation state and other guidance information to provide the CAU displays with evaluations of abort options, as well as landing site recommendations. This is accomplished by three main SAFM components: the Sequencer Executive, the Powered Flight Function, and the Glided Flight Function, The Sequencer Executive dispatches the Powered and Glided Flight Functions to evaluate the vehicle's capability to execute the current mission (or current abort), as well as more than IS hypothetical abort options or scenarios. Scenarios are sequenced and evaluated throughout powered and glided flight. Abort scenarios evaluated include Abort to Orbit (ATO), Transatlantic Abort Landing (TAL), East Coast Abort Landing (ECAL) and Return to Launch Site (RTLS). Sequential and simultaneous engine failures are assessed and landing footprint information is provided during actual entry scenarios as well as hypothetical "loss of thrust now" scenarios during ascent.

Hu, Howard↗
NASA NTRS2010

Workload: Measurement and Management

Poster: The workload research project has as its task to survey the available literature on: (1) workload measurement techniques; and (2) the effects of workload on operator performance. The first set of findings provides practitioners with a collection of simple-to-use workload measurement techniques along with characterizations of the kinds of tasks each technique has been shown reliably address. This allows design practitioners to select and use the most appropriate techniques for the task(s) at hand. The second set of findings provides practitioners with the guidance they need to design for appropriate kinds and amounts of workload across all tasks for which the operator is responsible. This guidance helps practitioners design systems and procedures that ensure appropriate levels of engagement across all tasks, and avoid designs and procedures that result in operator boredom, complacency, loss of awareness, undue levels of stress, or skill atrophy that can result from workload that distracts operators from the tasks they perform and monitor, workload levels that are too low, too high, or too consistent or predictable. Only those articles that were peer reviewed, long standing and generally accepted in the field, and applicable to a relevant range of conditions in a select domain of interest, in analogous "extreme" environments to those in space were included. In addition, all articles were reviewed and evaluated on uni-dimensional and multi-dimensional considerations. Casner & Gore also examined the notion of thresholds and the conditions that may benefit mostly from the various methodological approaches. Other considerations included whether the tools would be suitable for guiding a requirement-related and design-related question. An initial review of over 225 articles was conducted and entered into an EndNote database. The reference list included a range of conditions in the domain of interest (subjective/objective measures), the seminal works in workload, as well as summary works

Gore, Brian Francis↗
NASA NTRS1987

Water management requirements for animal and plant maintenance on the Space Station

Long-duration Space Station experiments that use animals and plants as test specimens will require increased automation and advanced technologies for water management in order to free scientist-astronauts from routine but time-consuming housekeeping tasks. The three areas that have been identified as requiring water management and that are discusseed are: (1) drinking water and humidity condensate of the animals, (2) nutrient solution and transpired water of the plants, and (3) habitat cleaning methods. Automation potential, technology assessment, crew time savings, and resupply penalties are also discussed.

Johnson, C. C.↗
NASA NTRS1985

An overview of the Space Station Technology/Advanced Development Program

The Advanced Technology Plan of the Fiscal Year (FY) 1986 is designed to focus on the most promising technology options applicable to the Space Station (SS), selected from the list of tasks identified by the FY 1984 Technology Program as the most critical technologies to be developed for the initial SS Initial Operating Capability. Most of the current activities are in the stages of manufacture and life tests of specific SS subsystems. Special attention is given to major technologies, which include power systems (PSs) (with emphasis on a Solar Dynamic PS concept); the thermal control system (with the focus on the 'thermal bus' concept); the environmental control and life support system; and the data management system; all are illustrated schematically. Other tasks, including dynamics, communications, extravehicular activities, mechanics, propulsion, and fluid, as well as the tasks of cost, maintainability, automation and robotics, and productivity are discussed.

Carlisle, R. F.↗
NASA NTRS1999

Continuous Risk Management: An Overview

Software risk management is important because it helps avoid disasters, rework, and overkill, but more importantly because it stimulates win-win situations. The objectives of software risk management are to identify, address, and eliminate software risk items before they become threats to success or major sources of rework. In general, good project managers are also good managers of risk. It makes good business sense for all software development projects to incorporate risk management as part of project management. The Software Assurance Technology Center (SATC) at NASA GSFC has been tasked with the responsibility for developing and teaching a systems level course for risk management that provides information on how to implement risk management. The course was developed in conjunction with the Software Engineering Institute at Carnegie Mellon University, then tailored to the NASA systems community. This is an introductory tutorial to continuous risk management based on this course. The rational for continuous risk management and how it is incorporated into project management are discussed. The risk management structure of six functions is discussed in sufficient depth for managers to understand what is involved in risk management and how it is implemented. These functions include: (1) Identify the risks in a specific format; (2) Analyze the risk probability, impact/severity, and timeframe; (3) Plan the approach; (4) Track the risk through data compilation and analysis; (5) Control and monitor the risk; (6) Communicate and document the process and decisions.

Rosenberg, Linda↗
DOE OSTI2026

Evaluation of Howard A. Hanson Dam Juvenile Fish Passage and Survival Study Live Fish Injury Assessment, Sensor Fish, and BioPA Modeling Tasks

The live fish injury assessment, Sensor Fish, and BioPA modeling study tasks were conducted by researchers from Pacific Northwest National Laboratory (PNNL). The four tasks were part of the larger Evaluation of Howard A. Hanson Dam (HAHD) Juvenile Fish Passage and Survival study, which had six total tasks. To achieve study objectives for each of the four tasks, field work occurred at Green Peter Dam (GPR) to evaluate the highest elevation steep slope bypass pipe, at HAHD to evaluate baseline conditions of the horseshoe tunnel, and at PNNL’s Aquatic Research Laboratory (ARL) to evaluate simulated dam passage conditions (i.e., shear forces and collision). Each of these evaluations utilized live fish injury assessment, Sensor Fish, and BioPA modeling. Live fish injury assessment and survival (tagged with and without balloon or passive integrated transponder [PIT] tags) was correlated with Sensor Fish to determine thresholds. The CFD analyses were then performed, and the computed values were compared to the corresponding measured values of Sensor Fish data. The results of the overall injury and survival of fish was also used in the validation of the CFD modeling method. Collectively, the results will aid in future modeling of fish passage at HAHD. Results from these tasks can be used by biologists, engineers, resource managers, and regional decision-makers to inform baseline conditions under current operations and the engineering design of the new FPF at HAHD. This draft report contains initial data and results from the four tasks. Table 8 1, Table 8 2, and Table 8 3, and Figure 8 1, Figure 8 2, and Figure 8 3 depict the CFD modeling findings for the GPR steep slope bypass, HAHD horseshoe tunnel, and laboratory testing. Table 8 4, Table 8 5, and Table 8 6 depict the Sensor Fish findings for the GPR steep slope bypass and HAHD horseshoe tunnel testing. The Mv values observed in the HAHD were significantly lower compared to the laboratory experiments conducted at PNNL. Currently, investigations are underway to understand the reasons for this disparity and to establish an appropriate threshold value for Mv. Survival predictions presented in the tables below should be considered preliminary and should not be used until further analyses and adjustments are completed. The next steps for modeling will include the flow regime, (i.e., density of flow regimes due to water and air mixing ) to continue to improve on the threshold value for Mv.

13 HYDRO ENERGY↗
NASA NTRS1992

Coordinating complex problem-solving among distributed intelligent agents

A process-oriented control model is described for distributed problem solving. The model coordinates the transfer and manipulation of information across independent networked applications, both intelligent and conventional. The model was implemented using SOCIAL, a set of object-oriented tools for distributing computing. Complex sequences of distributed tasks are specified in terms of high level scripts. Scripts are executed by SOCIAL objects called Manager Agents, which realize an intelligent coordination model that routes individual tasks to suitable server applications across the network. These tools are illustrated in a prototype distributed system for decision support of ground operations for NASA's Space Shuttle fleet.

Adler, Richard M.↗
NASA NTRS1994

General purpose architecture for intelligent computer-aided training

An intelligent computer-aided training system having a general modular architecture is provided for use in a wide variety of training tasks and environments. It is comprised of a user interface which permits the trainee to access the same information available in the task environment and serves as a means for the trainee to assert actions to the system; a domain expert which is sufficiently intelligent to use the same information available to the trainee and carry out the task assigned to the trainee; a training session manager for examining the assertions made by the domain expert and by the trainee for evaluating such trainee assertions and providing guidance to the trainee which are appropriate to his acquired skill level; a trainee model which contains a history of the trainee interactions with the system together with summary evaluative data; an intelligent training scenario generator for designing increasingly complex training exercises based on the current skill level contained in the trainee model and on any weaknesses or deficiencies that the trainee has exhibited in previous interactions; and a blackboard that provides a common fact base for communication between the other components of the system. Preferably, the domain expert contains a list of 'mal-rules' which typifies errors that are usually made by novice trainees. Also preferably, the training session manager comprises an intelligent error detection means and an intelligent error handling means. The present invention utilizes a rule-based language having a control structure whereby a specific message passing protocol is utilized with respect to tasks which are procedural or step-by-step in structure. The rules can be activated by the trainee in any order to reach the solution by any valid or correct path.

Loftin, R. Bowen↗
DOE OSTI2024

Active causal learning for decoding chemical complexities with targeted interventions

Abstract Predicting and enhancing inherent properties based on molecular structures is paramount to design tasks in medicine, materials science, and environmental management. Most of the current machine learning and deep learning approaches have become standard for predictions, but they face challenges when applied across different datasets due to reliance on correlations between molecular representation and target properties. These approaches typically depend on large datasets to capture the diversity within the chemical space, facilitating a more accurate approximation, interpolation, or extrapolation of the chemical behavior of molecules. In our research, we introduce an active learning approach that discerns underlying cause-effect relationships through strategic sampling with the use of a graph loss function. This method identifies the smallest subset of the dataset capable of encoding the most information representative of a much larger chemical space. The identified causal relations are then leveraged to conduct systematic interventions, optimizing the design task within a chemical space that the models have not encountered previously. While our implementation focused on the QM9 quantum-chemical dataset for a specific design task—finding molecules with a large dipole moment—our active causal learning approach, driven by intelligent sampling and interventions, holds potential for broader applications in molecular, materials design and discovery.

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

NASA Schedule Management Handbook

The purpose of schedule management is to provide the framework for time-phasing, resource planning, coordination, and communicating the necessary tasks within a work effort. The intent is to improve schedule management by providing recommended concepts, processes, and techniques used within the Agency and private industry. The intended function of this handbook is two-fold: first, to provide guidance for meeting the scheduling requirements contained in NPR 7120.5, NASA Space Flight Program and Project Management Requirements, NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Requirements, NPR 7120.8, NASA Research and Technology Program and Project Management Requirements, and NPD 1000.5, Policy for NASA Acquisition. The second function is to describe the schedule management approach and the recommended best practices for carrying out this project control function. With regards to the above project management requirements documents, it should be noted that those space flight projects previously established and approved under the guidance of prior versions of NPR 7120.5 will continue to comply with those requirements until project completion has been achieved. This handbook will be updated as needed, to enhance efficient and effective schedule management across the Agency. It is acknowledged that most, if not all, external organizations participating in NASA programs/projects will have their own internal schedule management documents. Issues that arise from conflicting schedule guidance will be resolved on a case by case basis as contracts and partnering relationships are established. It is also acknowledged and understood that all projects are not the same and may require different levels of schedule visibility, scrutiny and control. Project type, value, and complexity are factors that typically dictate which schedule management practices should be employed.

Source record↗
NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗
NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗
NASA NTRS2014

User Interaction with the CNPC Link

As part of NASAs UAS in the NAS project, human factor guidelines are being developed for the ground control station of unmanned aircraft systems. A critical task for the pilot of a UAS is the management and control of the terrestrial radio links used to provide control of the vehicle and relay communications with air traffic control. An analysis of the task of the UAS pilot has been conducted to identify areas where guidelines are required. This analysis has identified a set of information requirements that must be supported by the radio equipment used to provide Control and Non-payload Communication (CNPC). Key requirements include the need for an alert when the link is lost, information on the current quality and latency of the link, and information to enable the future quality of the link to be anticipated as the aircraft changes location. These identified requirements can assist in the development of minimum operational performance standards for CNPC equipment.

unmanned aerial systems↗
NASA NTRS1985

Concepts and Tools for the Software Life Cycle

The tools, techniques, and aids needed to engineer, manage, and administer a large software-intensive task are themselves parts of a large softwaare base, and are incurred only at great expense. The needs of the software life cycle in terms of such supporting tools and methodologies are highlighted. The concept of a distributed network for engineering, management, and administrative functions is outlined, and the key characteristics of localized subnets in high-communications-traffic areas of software activity are discussed. A formal, deliberate, structured, systems-engineering approach for the construction of a uniform, coordinated tool set is proposed as a means to reduce development and maintenance costs, foster adaptability, enhance reliability, and promote standardization.

Tausworthe, R. C.↗
NASA NTRS1985

Concepts and tools for the software life cycle

The tools, techniques, and aids needed to engineer, manage, and administer a large software-intensive task are themselves parts of a large software base, and are incurred only at great expense. The needs of the software life cycle in terms of such supporting tools and methodologies are highlighted. The concept of a distributed network for engineering, management, and administrative functions is outlined, and the key characteristics of localized subnets in high-communications-traffic areas of software actively are discussed. A formal, deliberate, structured, systems-engineering approach for the construction of a uniform, coordinated tool set is proposed as a means to reduce development and maintenance costs, foster adaptability, enhance reliability, and promote standardization.

Tausworthe, R. C.↗
NASA NTRS1999

Continuous Risk Management at NASA

NPG 7120.5A, "NASA Program and Project Management Processes and Requirements" enacted in April, 1998, requires that "The program or project manager shall apply risk management principles..." The Software Assurance Technology Center (SATC) at NASA GSFC has been tasked with the responsibility for developing and teaching a systems level course for risk management that provides information on how to comply with this edict. The course was developed in conjunction with the Software Engineering Institute at Carnegie Mellon University, then tailored to the NASA systems community. This presentation will briefly discuss the six functions for risk management: (1) Identify the risks in a specific format; (2) Analyze the risk probability, impact/severity, and timeframe; (3) Plan the approach; (4) Track the risk through data compilation and analysis; (5) Control and monitor the risk; (6) Communicate and document the process and decisions. This risk management structure of functions has been taught to projects at all NASA Centers and is being successfully implemented on many projects. This presentation will give project managers the information they need to understand if risk management is to be effectively implemented on their projects at a cost they can afford.

Hammer, Theodore F.↗
NASA NTRS1999

Continuous Risk Management: A NASA Program Initiative

NPG 7120.5A, "NASA Program and Project Management Processes and Requirements" enacted in April, 1998, requires that "The program or project manager shall apply risk management principles..." The Software Assurance Technology Center (SATC) at NASA GSFC has been tasked with the responsibility for developing and teaching a systems level course for risk management that provides information on how to comply with this edict. The course was developed in conjunction with the Software Engineering Institute at Carnegie Mellon University, then tailored to the NASA systems community. This presentation will briefly discuss the six functions for risk management: (1) Identify the risks in a specific format; (2) Analyze the risk probability, impact/severity, and timeframe; (3) Plan the approach; (4) Track the risk through data compilation and analysis; (5) Control and monitor the risk; (6) Communicate and document the process and decisions.

Hammer, Theodore F.↗