Search NASA⌕ Search

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.

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

At least 361 records · Page 20

The role of client engagement in successful project delivery - 15599

Projects, managed using one of the standard methodologies, are the primary vehicle used by most organizations to effectively deliver their strategic objectives in a timely and high quality manner. Most projects at ANSTO with a strong nuclear technology component require the active engagement of the end user, sponsor and subject matter experts for making key decisions during the project delivery phase to ensure best value for the organization. In 2009, after a review of ANSTO's project governance and management processes, a number of changes to the governance of internal projects were made. This included the establishment of a project governance structure that includes a two-point accountability framework, where the Project Client, together with the Project Manager is held accountable for the project delivery. While the two-point project accountability framework is not a conventional approach in project management, the experience from the project managers and stakeholders at ANSTO indicates that it provides a robust, consistent and practical approach for managing projects. The challenges of the two-point accountability framework are primarily related to the clarity of roles and goals, particularly from the Client perspective. This is an area that needs further attention. Overall, this approach allows better coordination of input from the project sponsors, end users and subject matter experts for day-to-day decision making through the life-cycle of the project. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

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

Development of evaluation models of manpower needs for dismantling the dry conversion process-related equipment in uranium refining and conversion plant (URCP)

Evaluation models for determining the manpower needs for dismantling various types of equipment in uranium refining and conversion plant (URCP) have been developed. The models are widely applicable to other uranium handling facilities. Additionally, a simplified model was developed for easily and accurately calculating the manpower needs for dismantling dry conversion process-related equipment (DP equipment). It is important to evaluate beforehand project management data such as manpower needs to prepare an optimized decommissioning plan and implement effective dismantling activity. The Japan Atomic Energy Agency (JAEA) has developed the project management data evaluation system for dismantling activities (PRODIA code), which can generate project management data using evaluation models. For preparing an optimized decommissioning plan, these evaluation models should be established based on the type of nuclear facility and actual dismantling data. In URCP, the dry conversion process of reprocessed uranium and others was operated until 1999, and the equipment related to the main process was dismantled from 2008 to 2011. Actual data such as manpower for dismantling were collected during the dismantling activities, and evaluation models were developed using the collected actual data on the basis of equipment classification considering the characteristics of uranium handling facility. (authors)

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

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↗

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

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

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↗

Use of Historical EM Practices and Policies for Management of Cleanup Program and Address GAO Concerns - 20222

As Department of Energy (DOE) Environmental Management (EM) program policies and management practices are revised over time, it might be useful to periodically reflect on the DOE EM program's past to identify practices that have worked and those that might be appropriate for possible reuse in the future. An added impetus to examine alternative approaches is the recent Government Accountability Office (GAO) report entitled 'Nuclear Waste Cleanup - DOE Could Improve Program and Project Management by Better Classifying Work and Following Leading Practices.' The February 2019 GAO report states that EM categorizes most of its work in a way that does not adequately involve independent experts and DOE senior leadership. It also noted that EM has not followed leading practices for program and project management that could help keep the cleanup efforts on schedule and control costs. The GAO report recommended that EM, working with DOE Office of Project Management (PM): - Establish requirements and then assess EM's ongoing operations activities to determine if some activities should be reclassified as capital asset projects based on these newly established requirements. - Review and revise EM's 2017 cleanup policy to include program management leading practices related to scope, cost, schedule performance, and independent reviews. - Update the cleanup policy to require that earned value management (EVM) systems be maintained and used in a way that follows EVM best practices. - Develop a policy to ensure that work is categorized as level of effort (LOE) only in appropriate, specified circumstances, such as when work is not measurable or when measurement is impractical. - Integrate EVM data into EM's performance metrics for operations activities. To assist with improving program performance and implementing audit recommendations, this paper reviewed past successful cleanups such as Weldon Springs, Rocky Flats, Fernald, Ashtabula, Battelle Columbus (abs, and other historical resources and people with experience during the early years of EM program. As such, there are several past practices which may well be suited for reuse today. Some of these practices include: - In 1990's, as the DOE EM cleanup program, known as Environmental Restoration came into effect, the known cleanup scope at each geographic location or site was organized into four levels ranging from overall site-wide cleanup effort to the individual 'release sites', providing high granularity to the program. - The cleanup program was organized by geography (Northwest, Southwest, Eastern Area Programs, etc.). These 'sub-program' managers provided a degree of Headquarters oversight and management allowing upper management (EM-1, 2, and 3) to focus on major decisions and issues. - Budget levels at selected cleanup sites were funded above 'minimum-safety' levels to accelerate actual cleanup work. - Past practice utilized EVM techniques and uniform EM oversight over all discrete project-like activities, providing for a coordinated cleanup effort. - EM managed LOE activities using benchmarking and best in class management practice techniques to help manage costs. - EM managed and reviewed entire site cleanup baselines, not only individual projects, focusing on a successful overall outcome. - Sites had a 'Road map' or 'Management Action Plan' that provided the overall strategy or plan for that site's cleanup - this helped with understanding and coordination of efforts. - EM had a robust lessons-learned program and database to capture and transmit worthy ideas. - EM had well-structured cleanup baseline change control policies to control cost and schedule changes, at the contractor and higher Headquarters levels. Finally, some of the GAO observations may be valid, however it is not clear as to their extent. For example, for some operation types of work, the use of the Level of Effort (LOE) earned value method to track progress may be appropriate. Also, to ensure independence of thought, and to obtain useful insight on past practices, it may be suitable to have former EM employees to assist with understanding past practices or to verify that activities have been properly identified. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

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

White Paper on the Use of Team Calendars with the JIRA Issue Tracking System and Confluence Collaboration Tools for the xLPR Project

ORNL was tasked by xLPR project management to propose a team calendar for use within the xLPR consortium. Among various options that were considered, the approach judged by ORNL to best fit the needs of the xLPR project is presented in this document. The Atlassian Team Calendars plug-in used with the Confluence collaboration tool was recommended for several reasons, including the advantage that it provides for a tight integration between Confluence (found at https://xlpr.ornl.gov/wiki ) and xLPR s JIRA issue tracking system (found at https://xlpr.ornl.gov/jira ). This document is divided into two parts. The first part (Sections 1-6) consists of the white paper, which highlights some of the ways that Team Calendars can improve com mun ication between xLPR project managers, group leads, and team members when JIRA is applied for both issue tracking and change-management activities. Specific points emphasized herein are as follows: The Team Calendar application greatly enhances the added value that the JIRA and Confluence tools bring to the xLPR Project. The Team Calendar can improve com mun ication between xLPR project managers, group leads, and team members when JIRA is applied for both issue tracking and change-management activities. The Team Calendar works across different email tools such as Outlook 2011, Outlook 2010, Outlook 2007, Google Calendars and Mac s iCalendar to name a few. xLPR users can now access the wiki Confluence (with embedded Team Calendars) directly from JIRA without having to re-validate their login. The second part consists of an Annex (Section 7), which describes how users can subscribe to Team Calendars from different calendar applications. Specific instructions are given in the Annex that describe how to Import xLPR Team Calendar to Outlook Version Office 2010 Import xLPR Team Calendar to Outlook Version Office 2007 Subscribe to Team Calendar from Google Calendar The reader is directed to Section 4 for instructions on adding events to the Team Calendar or accessing ORNL staff for assistance with such additions. To seek help with your questions and problems regarding the content of this document, please contact Hilda Klasky at klaskyhb@ornl.gov

97 MATHEMATICS AND COMPUTING↗

Material and energy recovery in integrated waste management systems: Project overview and main results

Highlights: > The source separation level (SSL) of waste management system does not qualify adequately the system. > Separately collecting organic waste gives less advantages than packaging materials. > Recycling packaging materials (metals, glass, plastics, paper) is always attractive. > Composting and anaerobic digestion of organic waste gives questionable outcomes. > The critical threshold of optimal recycling seems to be a SSL of 50%. - Abstract: This paper describes the context, the basic assumptions and the main findings of a joint research project aimed at identifying the optimal breakdown between material recovery and energy recovery from municipal solid waste (MSW) in the framework of integrated waste management systems (IWMS). The project was carried out from 2007 to 2009 by five research groups at Politecnico di Milano, the Universities of Bologna and Trento, and the Bocconi University (Milan), with funding from the Italian Ministry of Education, University and Research (MIUR). Since the optimization of IWMSs by analytical methods is practically impossible, the search for the most attractive strategy was carried out by comparing a number of relevant recovery paths from the point of view of mass and energy flows, technological features, environmental impact and economics. The main focus has been on mature processes applicable to MSW in Italy and Europe. Results show that, contrary to a rather widespread opinion, increasing the source separation level (SSL) has a very marginal effects on energy efficiency. What does generate very significant variations in energy efficiency is scale, i.e. the size of the waste-to-energy (WTE) plant. The mere value of SSL is inadequate to qualify the recovery system. The energy and environmental outcome of recovery depends not only on 'how much' source separation is carried out, but rather on 'how' a given SSL is reached.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

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

Tipping the Balance

As an activist for the project community at NASA's Ames Research Center, I see my role as finding out what resource project managers need to help them run successful projects. I need to go out and advocate for those resources, if necessary, and I need to be supportive, not just for the projects, but also for the project managers and their teams. It's not something I can do sitting at my desk waiting for the phone to ring. To me, that's what an activist does. It's public service. In this case my public is the project-practitioner community.

Smith, Claire↗

TANK OPERATIONS CONTRACT CONSTRUCTION MANAGEMENT METHODOLOGY UTILIZING THE AGENCY METHOD OF CONSTRUCTION MANAGEMENT TO SAFELY AND EFFECTIVELY COMPLETE NUCLEAR CONSTRUCTION WORK

Washington River Protection Solutions, LLC (WRPS) has faced significant project management challenges in managing Davis-Bacon construction work that meets contractually required small business goals. The unique challenge is to provide contracting opportunities to multiple small business construction subcontractors while performing high hazard work in a safe and productive manner. Previous to the Washington River Protection Solutions, LLC contract, Construction work at the Hanford Tank Farms was contracted to large companies, while current Department of Energy (DOE) Contracts typically emphasize small business awards. As an integral part of Nuclear Project Management at Hanford Tank Farms, construction involves removal of old equipment and structures and installation of new infrastructure to support waste retrieval and waste feed delivery to the Waste Treatment Plant. Utilizing the optimum construction approach ensures that the contractors responsible for this work are successful in meeting safety, quality, cost and schedule objectives while working in a very hazardous environment. This paper describes the successful transition from a traditional project delivery method that utilized a large business general contractor and subcontractors to a new project construction management model that is more oriented to small businesses. Construction has selected the Agency Construction Management Method. This method was implemented in the first quarter of Fiscal Year (FY) 2009, where Construction Management is performed by substantially home office resources from the URS Northwest Office in Richland, Washington. The Agency Method has allowed WRPS to provide proven Construction Managers and Field Leads to mentor and direct small business contractors, thus providing expertise and assurance of a successful project. Construction execution contracts are subcontracted directly by WRPS to small or disadvantaged contractors that are mentored and supported by DRS personnel. Each small contractor is mentored and supported utilizing the principles of the Construction Industry Institute (CII) Partnering process. Some of the key mentoring and partnering areas that are explored in this paper are, internal and external safety professional support, subcontractor safety teams and the interface with project and site safety teams, quality assurance program support to facilitate compliance with NQA-1, construction, team roles and responsibilities, work definition for successful fixed price contracts, scheduling and interface with project schedules and cost projection/accruals. The practical application of the CII Partnering principles, with the Construction Management expertise of URS, has led to a highly successful construction model that also meets small business contracting goals.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Long Term Environment and Economic Impacts of Coal Liquefaction in China

The project currently is composed of six specific tasks – three research tasks, two outreach and training tasks, and one project management and communications task. Task 1 addresses project management and communication. Research activities focused on Task 2 (Describe and Quantify the Economic Impacts and Implications of the Development and Deployment of Coal-to-Liquid Facilities in China), Task 3 (Development of Alternative Coal Gasification Database), and Task 4 (Geologic Carbon Management Options). There also were significant activities related to Task 5 (US-China Communication, Collaboration, and Training on Clean Coal Technologies) as well as planning activity performed in support of Task 6 (Training Programs).

01 COAL, LIGNITE, AND PEAT↗

MACCS (MELCOR Accident Consequence Code System) User Guide

The MELCOR Accident Consequence Code System (MACCS) is used by Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This User Guide is intended to assist analysts in understanding the MACCS/WinMACCS model and to provide information regarding the code. This user guide version describes MACCS Version 3.10.0. Features that have been added to MACCS in subsequent versions are described in separate documentation. This User Guide provides a brief description of the model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2. PAPERWORK REDUCTION ACT STATEMENT The NUREG does not contain information collection requirements and, therefore, is not subject to the requirements of the Paperwork Reduction Act of 1995 (44 USC 3501, et seq.). PUBLIC PROTECTION NOTIFICATION The NRC may not conduct or sponsor, and a person is not required to respond to, a request for information or an information collection requirement unless the requesting document displays a currently valid OMB control number. ACKNOWLEDGEMENTS Contributions to this User Guide were received from NRC and Sandia National Laboratories (SNL) project managers, technical experts, and code authors dedicated to the production of a valuable resource for the MACCS user community. Instructions and guidance included herein were developed over many years and include advancements in the code that provide users the ability to develop complex consequence modeling scenarios. WinMACCS and many of the early MACCS developments were due to vision of an earlier Project Manager, Jocelyn Mitchell. Jonathan Barr and AJ Nosek also contributed to the development of this report. The current NRC Project Manager, Salman Haq, provided the leadership to ensure this document was completed. Several other NRC and Sandia staff provided insights supporting development of the MACCS code and of this document.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Customer Responsiveness

If you know anyone who's been involved in building a spacecraft, I'm sure you've heard the mantra, 'Test what you fly, and fly what you test.' Listen to a project manager from my institution (The Johns Hopkins Applied Physics Laboratory, a.k.a. APL) talking in his or her sleep, and this is likely what you're going to hear. At APL, we do a lot of testing. We probably do more testing in the initial stages of a project than we could explain to review boards. Perhaps we are conservative in this respect, but our project managers and engineers believe in getting a good night's sleep before a launch, and testing is a good way of ensuring that. So you can imagine my reaction when the NASA project manager, Don Margolies, suggested that on the Advanced Composition Explorer (ACE) mission we pull all the instruments off the spacecraft after we had just completed the full range of environmental testing. This would allow the scientists to do a better job of calibrating their instruments.

Chiu, Mary↗

Institutionalizing Lessons Learned

The NASA Integrated Action Team (NIAT) was formed by the NASA Administrator in March 2000. The purpose of this team was to identify the actions that NASA must take to address systemic findings reported in 4 different anomaly investigations. Team membership represented senior managers from all the field centers and NASA Headquarters. NIAT report addressed 165 findings and developed 17 action plans that are described in five themes: people and teams, technology, risk, formulation rigor, and communications. The NIAT actions present a systems solution for strengthening formulation and implementation of programs and improving the environment for their support. NIAT results included: enhancing success by avoiding failures that could have been prevented through good planning and sound practice; ensuring that prudent risks do not compromise safety; and ensuring that mission risks are objectively assessed, appropriately mitigated and consciously accepted by the program team and customers. Definitions of Faster, Better, Cheaper and Success Criteria were also developed and included as part of the NIAT report. As a result of the NIAT report, program and project management process changes were incorporated into NASA's quality system documentation, including NPG 7120.513, "NASA Program and Project Management Processes and Requirements. This paper describes the NIAT results and the resulting updates to NPG 7120.5 that keep this program and project management description a living process.

McBrayer, Robert O.↗