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 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↗
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 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.

Jeffrey R. Cohen↗
NASA NTRS2003

Lyophilization for Water Recovery From Solid Waste

This abstract describes the development of a solid waste treatment system designed for a near term human exploration mission. The technology being developed is an energy- efficient lyophilization technique that recovers water from spacecraft solid waste. In the lyophilization process water in an aqueous waste is frozen and then sublimed, resulting in the separation of the waste into a dried solid material and liquid water. This technology is ideally suited to applications where water recovery rates approaching 100% are desirable but production of CO, is not. Water contained within solid wastes accounts for approximately 3% of the total water balance. If 100% closure of the water loop is desired the water contained within this waste would need to be recovered. To facilitate operation in microgravity thermoelectric heat pumps have be used in place of traditional fluid cycle heat pumps. A mathematical model of a thermoelectric lyophilizer has been developed and used to generate energy use and processing rate parameters. The results of laboratory investigations and discussions with ALS program management have been used to iteratively arrive at a prototype design. This design address operational limitations which were identified in the laboratory studies and handling and health concerns raised by ALS program management. The current prototype design is capable of integration into the ISS Waste Collection System.

Flynn, Michael↗
NASA NTRS1988

Space station integrated propulsion and fluid systems study. Space station program fluid management systems databook

Commonality and integration of propulsion and fluid systems associated with the Space Station elements are being evaluated. The Space Station elements consist of the core station, which includes habitation and laboratory modules, nodes, airlocks, and trusswork; and associated vehicles, platforms, experiments, and payloads. The program is being performed as two discrete tasks. Task 1 investigated the components of the Space Station architecture to determine the feasibility and practicality of commonality and integration among the various propulsion elements. This task was completed. Task 2 is examining integration and commonality among fluid systems which were identified by the Phase B Space Station contractors as being part of the initial operating capability (IOC) and growth Space Station architectures. Requirements and descriptions for reference fluid systems were compiled from Space Station documentation and other sources. The fluid systems being examined are: an experiment gas supply system, an oxygen/hydrogen supply system, an integrated water system, the integrated nitrogen system, and the integrated waste fluids system. Definitions and descriptions of alternate systems were developed, along with analyses and discussions of their benefits and detriments. This databook includes fluid systems descriptions, requirements, schematic diagrams, component lists, and discussions of the fluid systems. In addition, cost comparison are used in some cases to determine the optimum system for a specific task.

Bicknell, B.↗
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.↗
NASA NTRS2009

Designing a Better Spacecraft: Assessing Flight Operability of Human Rated Spacecraft

The design of a human rated spacecraft is a complex and costly process requiring the integrated assessment of many individual criteria. Historically, it has been difficult to include in that integrated assessment the design s full impact on the flight operations community and its costs. The unique "operability requirements" have not been well understood, nor has there been a well-defined set of criteria for assessing operability. As a result, flight operations organizations and program managers are often faced with difficult and costly operations phase implementations. In response, the Mission Operations Directorate at NASA s Lyndon B. Johnson Space Center has established a formal technique to evaluate and communicate the operational characteristics of spacecraft system designs for the Constellation Program. This process is not intended to replace or replicate other critical assessments such as risk, reliability and safety assessments. Instead, this new technique adds to the assessment toolset a means to address the concerns and potential cost drivers that are unique to the operational phase of a program and the flight operations community. This paper describes the implementation and application of this "Spacecraft Flight Operability Assessment Scale" in supporting vehicle design efforts. The six key factors of flight operability are defined, with guiding principles and goals stated for each factor. A standardized rating technique provides feedback that is useful to both the operations and program management communities. Sample assessments of legacy spacecraft, including the Space Shuttle and International Space Station systems, are provided to provide real world examples of this technique s application.

Crocker, Alan R.↗