SEARCH · Search NASA

Results for “Project 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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 235 records · Page 13

All sources NASA NTRS DOE OSTI

NASA NTRS1988

Developing integrated parametric planning models for budgeting and managing complex projects

The applicability of integrated parametric models for the budgeting and management of complex projects is investigated. Methods for building a very flexible, interactive prototype for a project planning system, and software resources available for this purpose, are discussed and evaluated. The prototype is required to be sensitive to changing objectives, changing target dates, changing costs relationships, and changing budget constraints. To achieve the integration of costs and project and task durations, parametric cost functions are defined by a process of trapezoidal segmentation, where the total cost for the project is the sum of the various project cost segments, and each project cost segment is the integral of a linearly segmented cost loading function over a specific interval. The cost can thus be expressed algebraically. The prototype was designed using Lotus-123 as the primary software tool. This prototype implements a methodology for interactive project scheduling that provides a model of a system that meets most of the goals for the first phase of the study and some of the goals for the second phase.

Etnyre, Vance A.↗

NASA NTRS1998

The Impact of NPG 7120.5A Upon Training and Development

NASA Procedures and Guidance 7120.5A for Program and Project Management Processes and Requirements should have minimal effect upon current Agency training and development programs - mainly because the new directive simply formalizes what we have been teaching and learning in the NASA Program/Project Management Initiative all along. A frequent complaint we get from the 8,000 or so graduates of our PPMI courses over the years, however, deals with resistance to what they may have learned in the classroom or training site. Brimming with new ideas, these young men and women often run up against an entrenched program or project manager who insists that things be done "the old way," too often perceived as "the NASA way" or even "the Goddard way." Management was all too often in the eyes of the manager; now we're all reading from the same book, 7120.5A, Still, there is no single method or "one size fits all" approach to project management in NASA. While each Center is responsible for developing policies, processes and procedures to comply with the new NPG, individual program and project managers will still need to tailor their requirements to the specific needs of the project, consistent with the size, complexity, risk and criticality of the project. Under NPG 7120.5A, the results of such tailoring are to be documented in agreements among managers, directors, Enterprise Associate Administrators and the Administrator.

Hoffman, Edward J.↗

NASA NTRS1990

Ulysses - An ESA/NASA cooperative programme

Cooperation between ESA and NASA is discussed, noting that the Memorandum of Understanding lays the framework for this relationship, defining the responsibilities of ESA and NASA and providing for appointment of leadership and managers for the project. Members of NASA's Jet Propulsion Laboratory and ESA's ESTEC staff have been appointed to leadership positions within the project and ultimate control of the project rests with the Joint Working Group consisting of two project managers and two project scientists, equally representing both organizations. Coordination of time scales and overall mission design is discussed, including launch cooperation, public relations, and funding of scientific investigations such as Ulysses. Practical difficulties of managing an international project are discussed such as differing documentation requirements and communication techniques, and assurance of equality on projects.

Meeks, W.↗

NASA NTRS2019

Integrated Demand Management (IDM) Project Overview

Overview of NASA Integrated Demand Management (IDM) research into synchronized use of strategic and tactical air traffic management systems describes the initial motivation for the research, summary description of key experiments conducted between 2016 and the present, collaboration with outside partners and stakeholders, and the current status of the research.

Integrated Demand Management↗

NASA NTRS2003

Static Frequency Converter System Installed and Tested

A new Static Frequency Converter (SFC) system has been installed and tested at the NASA Glenn Research Center s Central Air Equipment Building to provide consistent, reduced motor start times and improved reliability for the building s 14 large exhausters and compressors. The operational start times have been consistent around 2 min, 20 s per machine. This is at least a 3-min improvement (per machine) over the old variable-frequency motor generator sets. The SFC was designed and built by Asea Brown Boveri (ABB) and installed by Encompass Design Group (EDG) as part of a Construction of Facilities project managed by Glenn (Robert Scheidegger, project manager). The authors designed the Central Process Distributed Control Systems interface and control between the programmable logic controller, solid-state exciter, and switchgear, which was constructed by Gilcrest Electric.

Brown, Donald P.↗

NASA NTRS2001

Improving System Engineering Excellence at NASA's Marshall Space Flight Center

NASA's Marshall Space Flight Center (MSFC) management feels that sound system engineering practices are essential for successful project management, NASA studies have concluded that recent project failures could be attributed in part to inadequate systems engineering. A recent survey of MSFC project managers and system engineers' resulted in the recognition of a need for training in Systems Engineering Practices, particularly as they relate to MSFC projects. In response to this survey, an internal pilot short-course was developed to reinforce accepted practices for system engineering at MSFC. The desire of the MSFC management is to begin with in-house training and offer additional educational opportunities to reinforce sound system engineering principles to the more than 800 professionals who are involved with system engineering and project management. A Systems Engineering Development Plan (SEDP) has been developed to address the longer-term systems engineering development needs of MSFC. This paper describes the survey conducted and the training course that was developed in response to that survey.

Takada, Pamela Wallace↗

NASA NTRS2005

Keeping Promises

Commitments are between people, not schedules. Project management as practiced today creates a "commitment-free zone," because it assumes that people will commit to centrally managed schedules without providing a mechanism to ensure their work can be done. So they give it their best, but something always seems to come up ..."I tried, but you know how it is." This form of project management does not provide a mechanism to ensure that what should be done, can in fact be done at the required moment. Too often, promises reliable promise. made in coordination meetings are conditional and unreliable. It has been my experience that at times trust can be low and hard to build in this environment. The absence of reliable promises explains why on well-run projects, people are often only completing 30-50 percent of the deliverables they d promised for the week. We all know what a promise is; we have plenty of experience making them and receiving them from others. So what s the problem? The sad fact is that the project environment-like many other work environments- is often so filled with systemic dishonesty, that we don t expect promises that are reliable. Project managers excel when they manage their projects as networks of commitments and help their people learn to elicit and make reliable promises.

Howell, Gregory A.↗

DOE OSTI2024

DE-FE0023919 Phase 5 Scientific/Technical Report

Phase 5 of the Deepwater Methane Hydrate Characterization and Scientific Assessment research project (DOE Award No. DE-FE0023919) occurred from Oct. 1, 2020 to Nov. 15, 2023. Throughout Phase 5, UT performed all aspects of project management and planning according to the award, project management plan, and statement of project objectives (Task 1). UT maintained and augmented the capability to transport, store, manipulate and analyze pressure cores (Task 13). UT’s hydrate core effective stress chamber can now run tests at effective stresses up to 20 MPa. A benchmark study was conducted and confirmed that the K0 permeameter accurately estimates geomechanical and petrophysical properties of geomaterials under uniaxial strain conditions. UT continued to analyze remaining UT-GOM2-1 pressure cores from GC955 (Task 10).

03 NATURAL GAS↗

NASA NTRS2010

Improving Life-Cycle Cost Management of Spacecraft Missions

This presentation will explore the results of a recent NASA Life-Cycle Cost study and how project managers can use the findings and recommendations to improve planning and coordination early in the formulation cycle and avoid common pitfalls resulting in cost overruns. The typical NASA space science mission will exceed both the initial estimated and the confirmed life-cycle costs by the end of the mission. In a fixed-budget environment, these overruns translate to delays in starting or launching future missions, or in the worst case can lead to cancelled missions. Some of these overruns are due to issues outside the control of the project; others are due to the unpredictable problems (unknown unknowns) that can affect any development project. However, a recent study of life-cycle cost growth by the Discovery and New Frontiers Program Office identified a number of areas that are within the scope of project management to address. The study also found that the majority of the underlying causes for cost overruns are embedded in the project approach during the formulation and early design phases, but the actual impacts typically are not experienced until late in the project life cycle. Thus, project management focus in key areas such as integrated schedule development, management structure and contractor communications processes, heritage and technology assumptions, and operations planning, can be used to validate initial cost assumptions and set in place management processes to avoid the common pitfalls resulting in cost overruns.

Clardy, Dennon↗

NASA NTRS1980

Integration of design information

The overall concepts of the integrated programs for aerospace-vehicle design (IPAD) from the user's viewpoint are discussed. Also a top-level view of what the user requires from such a system is provided, and the interactions between the system and user are described. The four major components discussed are design process; data storage, management and manipulation; user interface; and project management. Although an outgrowth of aerospace production experience, the basic concepts discussed, and especially their emphasis on integration, are considered applicable to all problem solving. Thus, these concepts may offer a broad base for exploitation by industry in general. This is the first in a set of three papers, the other two being Future Integrated Design Process, by D. D. Mayer, and Requirements for Company-Wide Management of Engineering Information, by J. W. Southall. In addition to tying the three together, how project management can be handled in a computing environment and also the user interface needs are discussed in detail.

Anderton, G. L.↗

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 NTRS2011

Habitat Demonstration Unit Project: Leadership and Management Strategies for a Rapid Prototyping Project

This paper gives an overview of the National Aeronautics and Space Administration (NASA) led multi-center Habitat Demonstration Unit (HDU) project leadership and management strategies being used by the NASA HDU team for a rapid prototyping project. The HDU project team constructed and tested an analog prototype lunar surface habitat/laboratory called the Pressurized Excursion Module (PEM) during 2010. The prototype unit subsystems were integrated in a short amount of time, utilizing a tiger team rapid prototyping approach that brought together over 20 habitation-related technologies and innovations from a variety of NASA centers. This paper describes the leadership and management strategies as well as lessons learned pertaining to leading and managing a multi-center diverse team in a rapid prototype environment. The PEM configuration went from a paper design to an operational surface habitat demonstration unit in less than 12 months. The HDU project is part of the strategic plan from the Exploration Systems Mission Directorate (ESMD) Directorate Integration Office (DIO) and the Exploration Mission Systems Office (EMSO) to test destination elements in analog environments. The 2011 HDU-Deep Space Habitat (DSH) configuration will build upon the PEM work, and emphasize validity of crew operations (remote working and living), EVA operations, mission operations, logistics operations, and science operations that might be required in a deep space context for Near Earth Object (NEO) exploration mission architectures. The 2011 HDU-DSH will be field-tested during the 2011 Desert Research and Technologies Studies (DRaTS) field tests. The HDU project is a "technology-pull" project that integrates technologies and innovations from multiple NASA centers. This project will repurpose the HDU 2010 demo unit that was field tested in the 2010 DRaTS, adding habitation functionality to the prototype unit. This paper will describe the strategy of establishing a multi-center project management team that put in place the key multi-center leadership skills and disciplines to enable a successful tiger team approach. Advocacy was established with key stakeholders and NASA Headquarters (HQ) by defining a strategic vision, mission, goals and objectives for the project and team. As a technology-pull testbed capability the HDU project was able to collaborate and leverage the Exploration Technology Development Program (ETDP) and individual NASA center investments which capitalized on their respective center core competencies and skills. This approach enable the leveraging of over $7.5m of value to create an operational habitat demonstration unit 2010 PEM configuration.

Kennedy, Kriss J.↗

NASA NTRS1993

Software Formal Inspections Guidebook

The Software Formal Inspections Guidebook is designed to support the inspection process of software developed by and for NASA. This document provides information on how to implement a recommended and proven method for conducting formal inspections of NASA software. This Guidebook is a companion document to NASA Standard 2202-93, Software Formal Inspections Standard, approved April 1993, which provides the rules, procedures, and specific requirements for conducting software formal inspections. Application of the Formal Inspections Standard is optional to NASA program or project management. In cases where program or project management decide to use the formal inspections method, this Guidebook provides additional information on how to establish and implement the process. The goal of the formal inspections process as documented in the above-mentioned Standard and this Guidebook is to provide a framework and model for an inspection process that will enable the detection and elimination of defects as early as possible in the software life cycle. An ancillary aspect of the formal inspection process incorporates the collection and analysis of inspection data to effect continual improvement in the inspection process and the quality of the software subjected to the process.

Source record↗

NASA NTRS2004

An Approach to Tailoring Major Technical Reviews Based on Project Characteristics and Stakeholder Interests

There are numerous technical reviews that occur throughout the systems engineering process life cycle. Many are well known by project managers and stakeholders such as developers and end users, an example of much is the critical design review (CDR). This major milestone for a large, complex new project may last two or more days, include an extensive agenda of topics, and entail hundreds of hours of developer time to prepare presentation materials and associated documents. Additionally, the weeks of schedule spent on review preparation is at least partly at the expense of other work. This paper suggests an approach for tailoring technical reviews, based on the project characteristics and the project manager s identification of the key stakeholders and understanding of their most important issues and considerations. With this insight the project manager can communicate to, manage expectations oc and establish formal agreement with the stakeholders as to which reviews, and at what depth, are most appropriate to achieve project success. The authors, coming from diverse organizations and backgrounds, have drawn on their personal experiences and summarized the best practices of their own organizations to create a common framework to provide guidance on the adaptation of design reviews to other system engineers.

Richstein, Alan B.↗

NASA NTRS1985

Software management tools: Lessons learned from use

Experience in inserting software project planning tools into more than 100 projects producing mission critical software are discussed. The problems the software project manager faces are listed along with methods and tools available to handle them. Experience is reported with the Project Manager's Workstation (PMW) and the SoftCost-R cost estimating package. Finally, the results of a survey, which looked at what could be done in the future to overcome the problems experienced and build a set of truly useful tools, are presented.

Reifer, D. J.↗

NASA NTRS2003

Oh, Develop

In a mature view of the subject, career development is not simply four years of college or a week at training, culminating in a diploma or a certificate to hang on an office wall. That's why we wanted to take a broad look at career development in this issue of ASK. Take for example, Dr. Gerald Mulenburg s contribution, Fly on the Wall. When Mulenburg and other members of a knowledge-sharing group at Ames were invited to observe an upcoming project review, Mulenburg thought it would be interesting to learn how another project does its reviews. Note that Mulenburg is no fresh out who's never attended a NASA project review. Not only has he been through a fair share of them as the reviewed, he has also been on the other side of the table as a reviewer. This experienced project manager recognizes that at any stage of a career there is room to grow and develop one's repertoire. Too often people associate career development with textbooks and role classroom training, far removed from project life. But classroom training need not be like this, as you'll find in our Special Feature, The Enterprise Project by Wendy Dolci, which sprung out of an APPL Advanced Project Management class in July 2003 at Ames Research Center. In addition to Dolci, some of her classmates contribute to the story. Mike Sander of the Jet Propulsion Laboratory, project manager for the Mars Science Laboratory mission, who provided the assignment on which the story is based, also has a cameo in the story. We think Dolci's story is an inspiring example of what classroom training can be if it's approached imaginatively and made to serve a practical purpose. Another story from Ames, by Frank Larsen, takes a different twist on career development. At the annual Experimental Aircraft Association Fly-in in Oshkosh, Wisconsin, Larsen represented Ames at a NASA booth. While there, Larsen met a colleague from Glenn Research Center. Months later on a project with a quick turnaround, he remembered his colleague from Glenn who had equipment that might help Larsen save time and money on his project. Although they had never worked together and they had to unravel a lot of red tape before they could collaborate, they managed a way to get the job done. There are other stories in this issue that deal directly with this theme of career development. Then there are others in which it is less explicit. But if you take the view that career development happens all the time, and is as necessary to your survival as breathing, then you can read almost any story in ASK with your career development in mind. In that case, all the best, and so then-start developing.

Post, Todd↗

NASA NTRS2010

Project Interface Requirements Process Including Shuttle Lessons Learned

Most failures occur at interfaces between organizations and hardware. Processing interface requirements at the start of a project life cycle will reduce the likelihood of costly interface changes/failures later. This can be done by adding Interface Control Documents (ICDs) to the Project top level drawing tree, providing technical direction to the Projects for interface requirements, and by funding the interface requirements function directly from the Project Manager's office. The interface requirements function within the Project Systems Engineering and Integration (SE&I) Office would work in-line with the project element design engineers early in the life cycle to enhance communications and negotiate technical issues between the elements. This function would work as the technical arm of the Project Manager to help ensure that the Project cost, schedule, and risk objectives can be met during the Life Cycle. Some ICD Lessons Learned during the Space Shuttle Program (SSP) Life Cycle will include the use of hardware interface photos in the ICD, progressive life cycle design certification by analysis, test, & operations experience, assigning interface design engineers to Element Interface (EI) and Project technical panels, and linking interface design drawings with project build drawings

Bauch, Garland T.↗

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