Search NASA⌕ Search

SEARCH · Search NASA

Results for “program 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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

National Aeronautics and Space Administration Marshall Space Flight Center Space Transportation Directorate Risk Management Implementation Program

The US civil aerospace program has been a great contributor to the creation and implementation of techniques and methods to identify, analyze, and confront risk. NASA has accomplished mission success in many instances, but also has had many failures. Anomalies have kept the Agency from achieving success on other occasions, as well. While NASA has mastered ways to prevent risks, and to quickly and effectively react and recover from anomalies or failures, it was not until few years ago that a comprehensive Risk Management process started being implemented in some of its programs and projects. A Continuous Risk Management (CRM) cycle process was developed and has been promoted and used successfully in programs and projects across the Agency.

Duarte, Luis Alberto↗
NASA NTRS2011

Risk Acceptance Personality Paradigm: How We View What We Don't Know We Don't Know

The purpose of integrated hazard analyses, probabilistic risk assessments, failure modes and effects analyses, fault trees and many other similar tools is to give managers of a program some idea of the risks associated with their program. All risk tools establish a set of undesired events and then try to evaluate the risk to the program by assessing the severity of the undesired event and the likelihood of that event occurring. Some tools provide qualitative results, some provide quantitative results and some do both. However, in the end the program manager and his/her team must decide which risks are acceptable and which are not. Even with a wide array of analysis tools available, risk acceptance is often a controversial and difficult decision making process. And yet, today's space exploration programs are moving toward more risk based design approaches. Thus, risk identification and good risk assessment is becoming even more vital to the engineering development process. This paper explores how known and unknown information influences risk-based decisions by looking at how the various parts of our personalities are affected by what they know and what they don't know. This paper then offers some criteria for consideration when making risk-based decisions.

Massie, Michael J.↗
NASA NTRS1967

Graphic visualization of program performance aids management review

Chart technique /PERTREE/ which displays the essential status elements of a PERT system in a vertical flow array, of high graphic quality, enables visual review by management of program performance. Since the display is versatile, it can accommodate any aspect of the program which the presenter wishes to accent.

Eisenhart, G. N.↗
NASA NTRS1967

Technical facilities catalog, volume II

This Technical Facilities Catalog has been developed in response to an increasing demand for general and specific information on NASA technical facilities. The Catalog is intended to: a)provide NASA management, facilities managers, program and project managers, individual research engineers and scientists, and other agencies of the Government with knowledge of existing NASA research, development, test and evaluation facilities and b)provide the reader with a basic concept of the capabilities and functions of the wide variety of NASA technical facilities and the technological areas they support.

Wind tunnel↗
NASA NTRS2004

Managing Risk to Ensure a Successful Cassini/Huygens Saturn Orbit Insertion (SOI)

I. Design: a) S/C designed to be largely single fault tolerant; b) Operate in flight demonstrated envelope, with margin; and c) Strict compliance with requirements & flight rules. II. Test: a) Baseline, fault & stress testing using flight system testbeds (H/W & S/W); b) In-flight checkout & demos to remove first time events. III. Failure Analysis: a) Critical event driven fault tree analysis; b) Risk mitigation & development of contingencies. IV) Residual Risks: a) Accepted pre-launch waivers to Single Point Failures; b) Unavoidable risks (e.g. natural disaster). V) Mission Assurance: a) Strict process for characterization of variances (ISAs, PFRs & Waivers; b) Full time Mission Assurance Manager reports to Program Manager: 1) Independent assessment of compliance with institutional standards; 2) Oversight & risk assessment of ISAs, PFRs & Waivers etc.; and 3) Risk Management Process facilitator.

risk managment↗
NASA NTRS1998

Issues in NASA Program and Project Management. Special Edition: A Collection of Papers on NASA Procedures and Guidance 7120.5A

A key aspect of NASA's new Strategic Management System is improving the way we plan, approve, execute and evaluate our programs and projects. To this end, NASA has developed the NASA Program and Project Management processes and Requirements-NASA Procedures and Guidelines (NPG) 7120.5A, which formally documents the "Provide Aerospace Products and Capabilities" crosscutting process, and defines the processes and requirements that are responsive to the Program/Project Management-NPD 7120.4A. The Program/Project Management-NPD 7120.4A, issued November 14, 1996, provides the policy for managing programs and projects in a new way that is aligned with the new NASA environment. An Agencywide team has spent thousands of hours developing the NASA Program and Project Management Processes and Requirements-NPG 7120.5A. We have created significant flexibility, authority and discretion for the program and project managers to exercise and carry out their duties, and have delegated the responsibility and the accountability for their programs and projects.

Edward J. Hoffman↗
NASA NTRS1983

Guidelines for development of NASA (National Aeronautics and Space Administration) computer security training programs

The report presents guidance for the NASA Computer Security Program Manager and the NASA Center Computer Security Officials as they develop training requirements and implement computer security training programs. NASA audiences are categorized based on the computer security knowledge required to accomplish identified job functions. Training requirements, in terms of training subject areas, are presented for both computer security program management personnel and computer resource providers and users. Sources of computer security training are identified.

Tompkins, F. G.↗
NASA NTRS1990

Advanced program development management software system. Software description and user's manual

The objectives of this project were to apply emerging techniques and tools from the computer science discipline of paperless management to the activities of the Space Transportation and Exploration Office (PT01) in Marshall Space Flight Center (MSFC) Program Development, thereby enhancing the productivity of the workforce, the quality of the data products, and the collection, dissemination, and storage of information. The approach used to accomplish the objectives emphasized the utilization of finished form (off-the-shelf) software products to the greatest extent possible without impacting the performance of the end product, to pursue developments when necessary in the rapid prototyping environment to provide a mechanism for frequent feedback from the users, and to provide a full range of user support functions during the development process to promote testing of the software.

Source record↗
NASA NTRS1992

Global Temperature and Salinity Pilot Project

Data exchange and data management programs have been evolving over many years. Within the international community there are two main programs to support the exchange, management and processing of real time and delayed mode data. The Intergovernmental Oceanographic Commission (IOC) operate the International Oceanographic Data and Information Exchange (IODE) program which coordinates the exchange of delayed mode data between national oceanographic data centers, World Data Centers and the user community. The Integrated Global Ocean Services System is a joint IOC/World Meteorological Organization (WMO) program for the exchange and management of real-time data. These two programs are complemented by mechanisms that have been established within scientific programs to exchange and manage project data sets. In particular TOGA and WOCE have identified a data management requirement and established the appropriate infrastructure to achieve this. Where GTSPP fits into this existing framework is discussed.

Searle, Ben↗
NASA NTRS1980

LeRC reduced gravity fluid management technology program

The program reviewed in the present paper has provided information of the reduced-gravity behavior of fluids, thermal control of cryogenic tankage, and fluid management system design. The studies are currently shifting from the utilization of in-house experimental facilities to the development of Spacelab experiments. The cryogenic fluid management experiment, currently undergoing detailed design, is expected to provide an orbital evaluation of a subcritical liquid hydrogen storage and supply system, as part of the Shuttle/Spacelab program. Efforts are continuing to develop computer techniques for simulating reduced-gravity fluid dynamic processes.

Aydelott, J. C.↗
NASA NTRSDate not supplied

Human Systems Integration (HSI) Framework and Training - Shifting the View of HSI for Better Implementation

The Implementation of Human Systems Integration (HSI) presents challenges within the acquisition community for two reasons. The first is that misconceptions of HSI still exist, with many Program Managers (PMs) and leadership uncertain of the value or where to begin. The second is due to an unbalanced approach to HSI in its own framework. These implementation challenges lead to barriers in the early prevention of mishaps. Understanding HSI practices and how they should be implemented in the Acquisition Product Life Cycle (PLC) has been a challenge across the government, leaving the value of HSI unknown and misunderstood with Program Managers. In the case for many acquisition programs, HSI is not implemented in early design, losing the perspective on human capabilities and limitations, creating impacts on human-centered design. Expectations in human performance are not clearly set and operations are baselined with no margin for changes in technology and processes that will affect system performance. The HSI framework addresses total system performance holistically using collaboration as the primary tool. The goal is to create a system with efficiencies while minimizing risk to the operators, maintainers, and support personnel, as well as any collateral personnel and systems. To accomplish this, HSI should be implemented as part of preemptive measures to minimize potential human error and mishaps during the operation phase. Investigative and assessment tools exist that consider events, issues, and other outside influences of a system that may not fall under the current construct of the HSI domains, leaving gaps in early HSI implementation and affecting the prevention of human errors and mishaps. This presentation will outline what NASA HSI is doing to support Early HSI implementation and Operational Performance shifts that affect human performance.

Anthony T Thomas↗
NASA NTRS1991

The NASA cryogenic fluid management technology program plan

During the past three decades, NASA has been designing and using large quantities of cryogenic fluids for propulsion system propellants, coolants for experiments, and for environmental control systems. As a consequence, an erroneous conclusion has been drawn that the technology exists for using large quantities of cryogens in space for long periods of time. The attempt here is to dispel that myth and to present the technology needs that require development in order to support the NASA programs of the future. A NASA program, developed through the impetus of the Marshall Space Flight Center and the Lewis Research Center and supported by all NASA centers is outlined. The current state of the art is discussed along with specific needs for near future missions. Then, using the Space Exploration Initiative mission set, cost/benefit projections are made for the development of advanced cryogenic fluid management techniques. Earth based and space based test programs are discussed relative to the technology requirements for liquid storage, supply, and transfer for fluid transfer and advanced instrumentation.

Faddoul, James R.↗
NASA NTRS1982

Results of the automated power systems management /APSM/ program and future technology implementation

The APSM program was initiated in 1975. The purpose of this program was to develop and demonstrate the technology and benefits of autonomous operation of planetary spacecraft power systems to meet the projected requirements of future missions. Development of the APSM program was based on implementing a selected set of autonomous functions in a state-of-the-art breadboard power system. A distributed microcomputer system was developed to implement the functions. Several critical programmatic elements were identified as necessary to implement autonomous functions. These elements, including proper skill combination, well defined autonomous functions, and management of the software design and development task, were found to be more significant than hardware management. The incorporation of APSM technology in future space programs is also discussed.

Bridgeforth, A. O.↗
NASA NTRS1987

Documenting the Development of Software

Some routine supervisory functions performed automatically. Program Management Facility (PMF) computer program integrated software-development and control system. Applicable to large software systems involving as many as several hundred programmers and one million lines of codes, it ensures timely and orderly planning, development, implementation, and documentation of software. Designed as support tool. Has many features providing efficient processing and utilization of space for development programmer. Incorporates security system to prevent improper maintenance. Provides full set of cross-referenced reports and supervisory functions for detailed management information. Written in assembler. IBM program TSO required.

Source record↗
NASA NTRSDate not supplied

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, requirement engineers, clinicians (doctors, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling toolsor have never used these tools. Many of these individuals (clinicians, scientists, even program managers)may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeff Cohen↗
NASA NTRSDate not supplied

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.1Trade names and trademarks are used in this report for identification only. Their usage does not constitute an official endorsement, either expressed or implied, by the National Aeronautics and Space Administration.

Jeffrey R. Cohen↗