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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Communicating Risk to Program Managers

Program Managers (PM) can protect program resources and improve chances of success by anticipating, understanding and managing risks. Understanding the range of potential risks helps one to avoid or manage the risks. A PM must choose which risks to accept to reduce fire fighting, must meet the expectations of stakeholders consistently, and avoid falling into costly "black holes" that may open. A good risk management process provides the PM more confidence to seize opportunities save money, meet schedule, even improve relationships with people important to the program. Evidence of managing risk and sound internal controls can mean better support from superiors for the program by building a trust and reputation from being on top of issues. Risk managers have an obligation to provide the PM with the best information possible to allow the benefits to be realized (Small Business Consortium, 2004). The Institute for Chartered Accountants in England and Wales sees very important benefits for companies in providing better information about what they do to assess and manage key business risks. Such information will: a) provide practical forward-looking information; b) reduce the cost of capital; c) encourage better risk management; and d) improve accountability for stewardship, investor protection and the usefulness of financial reporting. We are particularly convinced that enhanced risk reporting will help listed companies obtain capital at the lowest possible cost (The Institute of Chartered Accountants in England &Wales, June 2002). Risk managers can take a significant role in quantifying the success of their department and communicating those figures to executive (program) management levels while pushing for a broader risk management role. Overall, risk managers must show that risk management work matters in the most crucial place-the bottom line- as they prove risk management can be a profit center (Sullivan, 2004).

Shivers, C. Herbert↗
NASA NTRS1972

A Management Information System Model for Program Management

The development of a model to simulate the information system of a program management type of organization is reported. The model statistically determines the following parameters: type of messages, destinations, delivery durations, type processing, processing durations, communication channels, outgoing messages, and priorites. The total management information system of the program management organization is considered, including formal and informal information flows and both facilities and equipment. The model is written in General Purpose System Simulation 2 computer programming language for use on the Univac 1108, Executive 8 computer. The model is simulated on a daily basis and collects queue and resource utilization statistics for each decision point. The statistics are then used by management to evaluate proposed resource allocations, to evaluate proposed changes to the system, and to identify potential problem areas. The model employs both empirical and theoretical distributions which are adjusted to simulate the information flow being studied.

Shipman, D. L.↗
NASA NTRS2007

Program Management Tool

The Program Management Tool (PMT) is a comprehensive, Web-enabled business intelligence software tool for assisting program and project managers within NASA enterprises in gathering, comprehending, and disseminating information on the progress of their programs and projects. The PMT provides planning and management support for implementing NASA programmatic and project management processes and requirements. It provides an online environment for program and line management to develop, communicate, and manage their programs, projects, and tasks in a comprehensive tool suite. The information managed by use of the PMT can include monthly reports as well as data on goals, deliverables, milestones, business processes, personnel, task plans, monthly reports, and budgetary allocations. The PMT provides an intuitive and enhanced Web interface to automate the tedious process of gathering and sharing monthly progress reports, task plans, financial data, and other information on project resources based on technical, schedule, budget, and management criteria and merits. The PMT is consistent with the latest Web standards and software practices, including the use of Extensible Markup Language (XML) for exchanging data and the WebDAV (Web Distributed Authoring and Versioning) protocol for collaborative management of documents. The PMT provides graphical displays of resource allocations in the form of bar and pie charts using Microsoft Excel Visual Basic for Application (VBA) libraries. The PMT has an extensible architecture that enables integration of PMT with other strategic-information software systems, including, for example, the Erasmus reporting system, now part of the NASA Integrated Enterprise Management Program (IEMP) tool suite, at NASA Marshall Space Flight Center (MSFC). The PMT data architecture provides automated and extensive software interfaces and reports to various strategic information systems to eliminate duplicative human entries and minimize data integrity issues among various NASA systems that impact schedules and planning.

Gawadiak, Yuri↗
NASA NTRS1965

Manned space flight program management.

Manned space flight program management noting system efficiency, cost factors, reliability and performance reports based on Apollo project

PROGRAM MANAGEMENT↗
NASA NTRS1971

The 1970/71 spectral data management programs

The data management programs used by the Stanford Remote Sensing Laboratory to access, modify, and reduce the data obtained from both the NASA IR airborne spectrometer, and Stanford's SG-4 field spectrometer are reported. Many details covered in previous reports are not repeated. References are provided. These programs are written in FORTRAN 4 and S/360 Assembler Language, and are currently running on a S/360 model 67 (operating under OS/MFT) at the Stanford Computation Center Campus Facility.

Marshall, A. A.↗
NASA NTRS1993

Repository-Based Software Engineering Program: Working Program Management Plan

Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents.

Source record↗
NASA NTRS1967

The program manager's problem

Saturn V program management problems induced by failure to plan for integrated logistics program and contractor logistics activities

MANAGEMENT PLANNING↗
NASA NTRS1994

Budget estimates: Fiscal year 1994. Volume 3: Research and program management

The research and program management (R&PM) appropriation provides the salaries, other personnel and related costs, and travel support for NASA's civil service workforce. This FY 1994 budget funds costs associated with 23,623 full-time equivalent (FTE) work years. Budget estimates are provided for all NASA centers by categories such as space station and new technology investments, space flight programs, space science, life and microgravity sciences, advanced concepts and technology, center management and operations support, launch services, mission to planet earth, tracking and data programs, aeronautical research and technology, and safety, reliability, and quality assurance.

Source record↗
NASA NTRS2019

Program Management for Concurrent University Satellite Programs, Including Propellant Feed System Design Elements

Propulsion options for CubeSats are limited but are necessary for the CubeSat industry to continue future growth. Challenges to CubeSat propulsion include volume/mass constraints, availability of sufficiently small and certified hardware, secondary payload status, safe storage of high energy, and power requirements. A multi-mode (chemical and electric) thruster was developed by at the Missouri University of Science and Technology (Missouri S&T) to enable CubeSat propulsion missions. Two satellite buses, a 3U and 6U, are being developed by the M-SAT satellite research team at Missouri S&T to demonstrate the multi-mode thruster's capabilities. Two key challenges related to these missions are the development of the feed system to support the thruster and management of the two programs' personnel, resources, timelines, and budgets. The feed system was designed to support the unique needs of the thruster including material compatibility with the custom ionic liquid, variable flow rate, high pressurization, and high voltage within the constraints and budget of a student-designed propulsion system. The feed system was also designed to minimize risk as a secondary payload. This resulted in the development of a unique method to pressurize propellant stored in the feed system tubing. Within the expected operating pressure range, the method was experimentally shown to provide sufficient pressure and propellant volume to the thruster to meet mission success criteria. The 3U and 6U CubeSat buses were designed concurrently with complimentary payloads, hardware, objectives, and team structures. Resources such as personnel, lab space, and time had to be carefully balanced between the two teams. With proper management, the two programs have been able to support one another, providing valuable insight and collaboration between the two teams. Lessons learned include experience with design, testing, and assembly of hardware, team training/mentoring and motivation, improved documentation practices, and risk management.

Withrow, Shannah Nichole↗
NASA NTRS2017

The 2015-2016 SEPMAP Program at NASA JSC: Science, Engineering, and Program Management Training

The Systems Engineering Project Management Advancement Program (SEPMAP) at NASA Johnson Space Center (JSC) is an employee development program designed to provide graduate level training in project management and systems engineering. The program includes an applied learning project with engineering and integrated science goals requirements. The teams were presented with a task: Collect a representative sample set from a field site using a hexacopter platform, as if performing a scientific reconnaissance to assess whether the site is of sufficient scientific interest to justify exploration by astronauts. Four teams worked through the eighteen-month course to design customized sampling payloads integrated with the hexacopter, and then operate the aircraft to meet sampling requirements of number (≥ 5) and mass (≥ 5g each). The "Mars Yard" at JSC was utilized for this purpose. This project activity closely parallels NASA plans for the future exploration of Mars, where remote sites will be reconnoitered ahead of crewed exploration.

Graham, L.↗
NASA NTRS1987

Acquisition-Management Program

NASA Acquisition Management Subsystem (AMS) program integrated NASA-wide standard automated-procurement-system program developed in 1985. Designed to provide each NASA installation with procurement data-base concept with on-line terminals for managing, tracking, reporting, and controlling contractual actions and associated procurement data. Subsystem provides control, status, and reporting for various procurement areas. Purpose of standardization is to decrease costs of procurement and operation of automatic data processing; increases procurement productivity; furnishes accurate, on-line management information and improves customer support. Written in the ADABAS NATURAL.

Avery, Don E.↗
NASA NTRS1985

A case study in R and D productivity: Helping the program manager cope with job stress and improve communication effectiveness

Certain structural changes in the Naval Material Command which resulted from a comparison of its operations to those of selected large-scale private sector companies are described. Central to the change was a reduction in the number of formal reports from systems commands to headquarters, and the provision of Program Management Assistance Teams (at the request of the program manager) to help resolve project problems. It is believed that these changes improved communication and information-processing, reduced program manager stress, and resulted in improved productivity.

Bodensteiner, W. D.↗
NASA NTRS1990

The NASA Risk Management Program

This paper describes the NASA Risk Management Program established by the Headquarters Office of Safety and Mission Quality (MSQ). Current agency policy is outlined, risk management assistance to the field is described, and examples are given of independent risk assessments conducted by SMQ. The motivation for and the structure of the program is placed in the historical context of pre- and post-Challenger environments.

Buchbinder, Benjamin↗
NASA NTRS2006

The NASA Program Management Tool: A New Vision in Business Intelligence

This paper describes a novel approach to business intelligence and program management for large technology enterprises like the U.S. National Aeronautics and Space Administration (NASA). Two key distinctions of the approach are that 1) standard business documents are the user interface, and 2) a "schema-less" XML database enables flexible integration of technology information for use by both humans and machines in a highly dynamic environment. The implementation utilizes patent-pending NASA software called the NASA Program Management Tool (PMT) and its underlying "schema-less" XML database called Netmark. Initial benefits of PMT include elimination of discrepancies between business documents that use the same information and "paperwork reduction" for program and project management in the form of reducing the effort required to understand standard reporting requirements and to comply with those reporting requirements. We project that the underlying approach to business intelligence will enable significant benefits in the timeliness, integrity and depth of business information available to decision makers on all organizational levels.

Maluf, David A.↗
DOE OSTI2025

Federal Energy Management Program

Fact sheet describes the Federal Energy Management Program and its mission, and outlines top priorities to achieve key federal agency statutory requirements for facility energy and water management.

Source record↗