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.
Nuclear Energy Fuel Cycle Program Knowledge Management Project.
Abstract not provided.
Nuclear Energy Fuel Cycle Program Knowledge Management Project.
Abstract not provided.
VHTR Fuel and Fuel Cycle Project Management Board Overview
Gen IV Industry Forum
VHTR Fuel and Fuel Cycle Project Management Board Status Update
17th Official Meeting of the FFC PMB Virtual event held on 14-15 Sep 2021 Canada participated as an observer
VHTR Fuel and Fuel Cycle Project Management Board Overview
33rd VHTR System Steering Committee Meeting 29 Sep 2022
TRANSFORMING THE SRS ENVIRONMENTAL BUSINESS: COMMUNICATION AND APPLIED PROJECT MANAGEMENT PRINCIPLES
A process for communicating information relating to core business functions that also encourages improving internal communications has been established at SRS. This process continues to grow and strengthen as the multiple Contractors, Regulators and DOE-SR relationships mature. A number of management communication tools have been initiated, retooled, rebooted or continued with enhancements to ensure appropriate information is communicated to all levels with environmental responsibility at SRS. The types of information that are the focus of this improved process are feedback from the customer and from informational exchange forums (i.e., Challenge Opportunity and Resolution (COR), SRS Regulatory Integration Team (SRIT), Environmental Quality Management Division (EQMD), Senior Environmental Managers Council (SEMC), etc.). These forums, SRS environmental functions centralization, and the creation of a Regulatory Integration process allows for cross-functional decision making, problem solving and information sharing that involves the field organizations, Environmental Compliance Authorities (ECA), Subject Matter Experts (SME), DOE and the Regulators. Numerous examples of effective decision-making and problem solving will be shared. Lessons Learned involving inadequate communications and the resulting impacts on the environment, customer satisfaction, and relationships will also be discussed. Additionally, the focus on improved communications also includes maintaining awareness of business activities. The tools being utilized to facilitate the continuing improvement of internal communications include weekly staff meetings for all individuals within the organization, quarterly ECA and SME meeting, quarterly Regulatory Integration & Environmental Services (RI&ES) All-Hands meetings hosted by the Director, bi-weekly EQMD and EQMD Lite meetings with the customer, bi-annual SRIT meetings, and COR meetings on an as need basis. In addition, an existing Required Reading Program is being formally utilized in RI&ES to ensure all individuals get formal notification of new/revised business documents. In all cases, the development of environmental communication topics that occur at SRS have a cost-scope-schedule basis that can be linked to delivery of environmental services.
Latest Developments in PM Systems and Methods and their Application to WM Projects - 20364
How do you improve on an industry that is well established yet often misses the mark on key metrics demonstrating effective planning and execution of project scope, schedule and budget? With the increased complexity of DOE projects relative to either poorly kept records of what wastes are stored or the lack of specific knowledge relative to the waste concentrations/quantities, this is a question continually asked and investigated by many. In fact, in 2017, the GAO's report to Congress indicated that although the DOE has made some progress on its monitoring effectiveness and demonstrating progress criteria, these goals were not met and there needs to be more improvement and monitoring. This paper will offer some insights into the latest developments in project management methodologies and the possible application of these to waste management projects. Traditional data generated via a project schedule that utilizes critical path methodology (CPM) and additional earned value management (EVM) data needs to be accurate and enable the project manager to better understand the probability of project success. Although this data has readily been available on most large-scale projects, success as measured by various stakeholder groups including the client, project team, regulators, etc. is less than optimal. Therefore, an urgent need exists to explore how traditional project data (CPM and EVM) coupled with new methodologies allows for better planning and execution by the project team. Many new approaches/methodologies can even be used to predict the success of options prior to full implementation on the actual project. Three approaches/methodologies will be discussed: - Artificial Intelligence; - Change Management; - Blend of Traditional Management (Gantt chart) and Agile Methodologies. As market forces change, so will the direction of project management. The days of 'one size fits all' are no longer valid. A combination of predictive and adaptive approaches in the management of projects is essential to enable execution of project deliverables on time, under budget, and within the contractual scope. This paper is intended to provide the reader with insight to the close relationship of project management trends and business management trends, and to provoke critical thinking about what it means to align project management strategy with an environment of non-stop innovation. (authors)
Reaching for the APEX at Ames
The multidimensional design of the APEX program is the result of an extensive research and development effort dating back nearly a decade. "In the late 1990s and early 2000, we were pretty successful at getting new research and technology projects here at the center," Johnson says, "and we had a lack of critical mass of project managers. We were taking people who were primarily researchers and putting them in the position of managing projects." Smith and Johnson held a series of workshops across the center during 2000 and 2001 to gather feedback about how to address this issue. When they briefed the center's senior management on their findings, one of the top recommendations was to establish a project manager development program at Ames. At that point, they cast a wide net for ideas and information. "We did centerwide needs assessment, we did focus groups, we did surveys," Smith says. "We came up with a proposal for what a program would look like, tying in what we knew about the Academy of Program1 Project Leadership (now the Academy for Program/Project and Engineering Leadership, or APPEL), what we've seen at other centers, what other centers have tried. We were always checking to make sure our program mapped to APPEL. We also looked at the PMI [Project Management Institute] model, INCOSE [International Council on Systems Engineering], CMMI [Capability Maturity Model Integration], you name it." "We had a lot of conversations with the Jet Propulsion Lab and Goddard," Johnson adds. "We saw those centers as models for what Ames was aspiring to be in terms of a center for managing space flight missions." Their research confirmed what they already knew-that strong practitioner involvement would be critical to their program design process. 'XPEX is for the practitioner by the practitioner," Smith says. "They have to be a part of designing it. Otherwise there's no way we could design a program that meets their needs." At the same time that they worked at the grassroots level, they also solicited feedback from the center's senior management. "We recognized that in order for anything to succeed here, we needed to have a champion at the center management level," Johnson said. "You have to have champions, and you have to listen to what the senior managers are saying. They have their own ideas." In the case of APEX, one of those ideas fundamentally reshaped the program. "When we originally started, it was a project management development program," Johnson says, "but in our meeting with our center director, he said, 'Project management is important, but we also need to strengthen our systems engineering.' So we basically added that component to the program based on what he wanted."
Special Projects: Carbon Management Program (SOSRA Project Overview)
Southeast Offshore Storage Resource Assessment (SOSRA): Special Projects - Carbon Management Program
Future ATM Concepts Evaluation Tool (FACET) Interface Control Document
This Interface Control Document (ICD) documents the airspace adaptation and air traffic inputs of NASA's Future ATM Concepts and Evaluation Tool (FACET). Its intended audience is the project manager, project team, development team, and stakeholders interested in interfacing with the system. FACET equips Air Traffic Management (ATM) researchers and service providers with a way to explore, develop and evaluate advanced air transportation concepts before they are field-tested and eventually deployed. FACET is a flexible software tool that is capable of quickly generating and analyzing thousands of aircraft trajectories. It provides researchers with a simulation environment for preliminary testing of advanced ATM concepts. Using aircraft performance profiles, airspace models, weather data, and flight schedules, the tool models trajectories for the climb, cruise, and descent phases of flight for each type of aircraft. An advanced graphical interface displays traffic patterns in two and three dimensions, under various current and projected conditions for specific airspace regions or over the entire continental United States. The system is able to simulate a full day's dynamic national airspace system (NAS) operations, model system uncertainty, measure the impact of different decision-makers in the NAS, and provide analysis of the results in graphical form, including sector, airport, fix, and airway usage statistics. NASA researchers test and analyze the system-wide impact of new traffic flow management algorithms under anticipated air traffic growth projections on the nation's air traffic system. In addition to modeling the airspace system for NASA research, FACET has also successfully transitioned into a valuable tool for operational use. Federal Aviation Administration (FAA) traffic flow managers and commercial airline dispatchers have used FACET technology for real-time operations planning. FACET integrates live air traffic data from FAA radar systems and weather data from the National Weather Service to summarize NAS performance. This information allows system operators to reroute flights around congested airspace and severe weather to maintain safety and minimize delay. FACET also supports the planning and post-operational evaluation of reroute strategies at the national level to maximize system efficiency. For the commercial airline passenger, strategic planning with FACET can result in fewer flight delays and cancellations. The performance capabilities of FACET are largely due to its architecture, which strikes a balance between flexibility and fidelity. FACET is capable of modeling the airspace operations for the continental United States, processing thousands of aircraft on a single computer. FACET was written in Java and C, enabling the portability of its software to a variety of operating systems. In addition, FACET was designed with a modular software architecture to facilitate rapid prototyping of diverse ATM concepts. Several advanced ATM concepts have already been implemented in FACET, including aircraft self-separation, prediction of aircraft demand and sector congestion, system-wide impact assessment of traffic flow management constraints, and wind-optimal routing.
Integration and Test of Shuttle Small Payloads
Recommended approaches for space shuttle small payload integration and test (I&T) are presented. The paper is intended for consideration by developers of shuttle small payloads, including I&T managers, project managers, and system engineers. Examples and lessons learned are presented based on the extensive history of NASA's Hitchhiker project. All aspects of I&T are presented, including: (1) I&T team responsibilities, coordination, and communication; (2) Flight hardware handling practices; (3) Documentation and configuration management; (4) I&T considerations for payload development; (5) I&T at the development facility; (6) Prelaunch operations, transfer, orbiter integration and interface testing; (7) Postflight operations. This paper is of special interest to those payload projects that have small budgets and few resources: that is, the truly faster, cheaper, better projects. All shuttle small payload developers are strongly encouraged to apply these guidelines during I&T planning and ground operations to take full advantage of today's limited resources and to help ensure mission success.
Integration and Test for Small Shuttle Payloads
Recommended approaches for shuttle small payload integration and test (I&T) are presented. The paper is intended for consideration by developers of small shuttle payloads, including I&T managers, project managers, and system engineers. Examples and lessons learned are presented based on the extensive history of the NASA's Hitchhiker project. All aspects of I&T are presented, including: (1) I&T team responsibilities, coordination, and communication; (2) Flight hardware handling practices; (3) Documentation and configuration management; (4) I&T considerations for payload development; (5) I&T at the development facility; (6) Prelaunch operations, transfer, orbiter integration, and interface testing; and (7) Postflight operations. This paper is of special interest to those payload projects which have small budgets and few resources: That is, the truly 'faster, cheaper, better' projects. All shuttle small payload developers are strongly encouraged to apply these guidelines during I&T planning and ground operations to take full advantage of today's limited resources and to help ensure mission success.
How Configuration Management (CM) Can Help Project Teams To Innovate and Communicate
Traditionally, CM is relegated to a support role in project management activities. CM s traditional functions of identification, change control, status accounting, and audits/verification are still necessary and play a vital role. However, this presentation proposes CM s role in a new and innovative manner that will significantly improve communication throughout the organization and, in turn, augment the project s success. CM s new role is elevated to the project management level, above the engineering or sub-project level in the Work Breakdown Structure (WBS), where it can more effectively accommodate changes, reduce corrective actions, and ensure that requirements are clear, concise, and valid, and that results conform to the requirements. By elevating CM s role in project management and orchestrating new measures, a new communication will emerge that will improve information integrity, structured baselines, interchangeability/traceability, metrics, conformance to standards, and standardize the best practices in the organization. Overall project performance (schedule, quality, and cost) can be no better than the ability to communicate requirements which, in turn, is no better than the CM process to communicate project decisions and the correct requirements.
Gleaming new facility delivers expertise now and into the future
On Tuesday, July 27, leadership from the Prototype Fabrication (PF) division welcomed a band of machinists, managers, project managers, members of Lab leadership, and NNSA to celebrate the official opening of a facility like no other at the Laboratory, and unique across the globe. The Mark Quality Manufacturing Center (MQMC) was developed throughout 2020 in support of weapons production capabilities, and is the Lab’s new home for high-precision non-nuclear components manufacturing. Work has been occurring there for several months, but with pandemic restrictions easing, it was finally time to celebrate.
Reliability measurement during software development
During the development of data base software for a multi-sensor tracking system, reliability was measured. The failure ratio and failure rate were found to be consistent measures. Trend lines were established from these measurements that provided good visualization of the progress on the job as a whole as well as on individual modules. Over one-half of the observed failures were due to factors associated with the individual run submission rather than with the code proper. Possible application of these findings for line management, project managers, functional management, and regulatory agencies is discussed. Steps for simplifying the measurement process and for use of these data in predicting operational software reliability are outlined.