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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

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.

Wright, Michael R.↗
NASA NTRS2009

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.

Cioletti, Louis↗
NASA NTRS1977

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.

Hecht, H.↗
NASA NTRS1978

The determination of measures of software reliability

Measurement of software reliability was carried out during the development of data base software for a multi-sensor tracking system. The failure ratio and failure rate were found to be consistent measures. Trend lines could be established from these measurements that provide 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.

Maxwell, F. D.↗
NASA NTRS1990

Concurrent engineering design and management knowledge capture

The topics are presented in viewgraph form and include the following: real-time management, personnel management, project management, conceptual design and decision making; the SITRF design problem; and the electronic-design notebook.

Source record↗
NASA NTRS1998

The NPG 7120.5A Electronic Review Process

The use of electronics to review a document is well within the technical realm of today's state-of-the-art workplace. File servers and web site interaction are common tools for many NASA employees. The electronic comment processing described here was developed for the NPG 7120.5A review to augment the existing NASA Online Directives Information System (NODIS). The NODIS system is NASA's official system for formal review, approval and storage of NASA Directives. The electronic review process worked so well that NASA and other agencies may want to consider it as one of our "best practices." It was participatory decision making at its very best, a process that attracted dozens of very good ideas to improve the document as well as the way we can be managing projects far more effectively. The revision of NPG 7120.5A has significant implications for the way all elements of the Agency accomplish program and project management. Therefore, the review of NPG 7120.5A was an Agencywide effort with high visibility, heavy participation and a short schedule. The level of involvement created interest in supplementing the formal NODIS system with a system to collect comments efficiently and to allow the Centers and Codes to review and consolidate their comments into the official system in a short period of time. In addition, the Program Management Council Working Group (PMCWG), responsible for the revision of the document and the disposition of official comments, needed an electronic system to manage the disposition of comments, obtain PMCWG consensus on each disposition, and coordinate the disposition with the appropriate Headquarters Code that had submitted the official comment. The combined NASA and contractor talents and resources provided a system that supplemented the NODIS system and its operating personnel to produce a thorough review and approval of NPG 7120.5A on April 3, 1998, 7.5 months from the start of the process. The original six-month schedule is indicated. All milestones occurred on time, except for completion of comment disposition, which required an additional 30 days. Approval of the document occurred sixteen days after completion of the "Purple Package."

McBrayer, Robert↗
NASA NTRS2004

Results of a NASA Kennedy Space Center Earned Value Management Pilot Project

The Earn Value Management Pilot provided a tremendous amount of data on the strengths and weaknesses of the new financial system, the ability to support EVM from many viewpoints, the lack of tools for small to medium projects implementing EVM, and the training and environment necessary to successfully deploy EVM to all projects. This data along with other pilots will prove invaluable. Deploying EVM should not be taken lightly - a full assessment of capabilities and supporting infrastructure should be done prior to any deployment, and some very basic questions should be asked. For instance, will sufficient training be provided? Can the project managers readily and easily obtain all the necessary data? If EVM is to thrive in all projects regardless of cost, the transition should be as seamless as possible, minimizing cost and effort, and with the end user in mind. In setting up an EVM implementation, the question, "How does the project manager benefit from this process?" must remain at the forefront. Further research in this area is needed to answer the question,"Is EVM cost effective in small projects?" The authors welcome knowledge sharing with other organizations that are striving to gain the benefits of EVM on small projects.

Delgado, Hector N.↗
NASA NTRS1997

Risk Management of NASA Projects

Various NASA Langley Research Center and other center projects were attempted for analysis to obtain historical data comparing pre-phase A study and the final outcome for each project. This attempt, however, was abandoned once it became clear that very little documentation was available. Next, extensive literature search was conducted on the role of risk and reliability concepts in project management. Probabilistic risk assessment (PRA) techniques are being used with increasing regularity both in and outside of NASA. The value and the usage of PRA techniques were reviewed for large projects. It was found that both civilian and military branches of the space industry have traditionally refrained from using PRA, which was developed and expanded by nuclear industry. Although much has changed with the end of the cold war and the Challenger disaster, it was found that ingrained anti-PRA culture is hard to stop. Examples of skepticism against the use of risk management and assessment techniques were found both in the literature and in conversations with some technical staff. Program and project managers need to be convinced that the applicability and use of risk management and risk assessment techniques is much broader than just in the traditional safety-related areas of application. The time has come to begin to uniformly apply these techniques. The whole idea of risk-based system can maximize the 'return on investment' that the public demands. Also, it would be very useful if all project documents of NASA Langley Research Center, pre-phase A through final report, are carefully stored in a central repository preferably in electronic format.

Sarper, Hueseyin↗
NASA NTRS2009

Management of Service Projects in Support of Space Flight Research

Goal:To provide human health and performance countermeasures, knowledge, technologies, and tools to enable safe, reliable, and productive human space exploration . [HRP-47051] Specific Objectives: 1) Develop capabilities, necessary countermeasures, and technologies in support of human space exploration, focusing on mitigating the highest risks to human health and performance. 2) Define and improve human spaceflight medical, environmental, and human factors standards. 3) Develop technologies that serve to reduce medical and environmental risks, to reduce human systems resource requirements (mass, volume, power, data, etc.) and to ensure effective human-system integration across exploration systems. 4) Ensure maintenance of Agency core competencies necessary to enable risk reduction in the following areas: A. Space medicine B. Physiological and behavioral effects of long duration spaceflight on the human body C. Space environmental effects, including radiation, on human health and performance D. Space "human factors" [HRP-47051]. Service projects can form integral parts of research-based project-focused programs to provide specialized functions. Traditional/classic project management methodologies and agile approaches are not mutually exclusive paradigms. Agile strategies can be combined with traditional methods and applied in the management of service projects functioning in changing environments. Creative collaborations afford a mechanism for mitigation of constrained resource limitations.

Love, J.↗
NASA NTRS2009

Employing Earned Value Management in Government Research and Design - Lessons Learned from the Trenches

To effectively manage a project, the project manager must have a plan, understand the current conditions, and be able to take action to correct the course when challenges arise. Research and design projects face technical, schedule, and budget challenges that make it difficult to utilize project management tools developed for projects based on previously demonstrated technologies. Projects developing new technologies by their inherent nature are trying something new and thus have little to no data to support estimates for schedule and cost, let alone the technical outcome. Projects with a vision for the outcome but little confidence in the exact tasks to accomplish in order to achieve the vision incur cost and schedule penalties when conceptual solutions require unexpected iterations or even a reinvention of the plan. This presentation will share the project management methodology and tools developed through trial and error for a NASA research and design project combining industry, academia, and NASA inhouse work in which Earned Value Management principles were employed but adapted for the reality of the government financial system and the reality of challenging technology development. The priorities of the presented methodology are flexibility, accountability, and simplicity to give the manager tools to help deliver to the customer while not using up valuable time and resources on extensive planning and analysis. This presentation will share the methodology, tools, and work through failed and successful examples from the three years of process evolution.

Simon, Tom↗
NASA NTRS2003

ASK Magazine

The Academy of Program and Project Leadership (APPL) and ASK Magazine is presented. APPL is a research-based organization that serves NASA program and project managers, as well as project teams, at every level of development. In 1997, APPL was created from an earlier program to underscore the importance that NASA places on project management and project teams through a wide variety of products and services, including knowledge sharing, classroom and online courses, career development guidance, performance support, university partnerships, and advanced technology tools. ASK Magazine grew out of our Knowledge Sharing Initiative. The stories that appear in ASK are written by the 'best of the best' project managers, primarily from NASA, but also from other government agencies and industry. These stories contain genuine nuggets of knowledge and wisdom that are transferable across projects. Who better than a project manager to help another project manager address a critical issue on a project? Big projects, small projects-they're all here in ASK. APPL is one of our most exciting publications about project management.

Edward Hoffman↗
NASA NTRS2019

Managing Programs and Projects at NASA

The presentation provides an overview of the NASA organization and several highlights of major NASA Programs and Projects. The presentation then provides additional details regarding project management processes and requirements at NASA. The briefing concludes with insights and information regarding management, communication and collaboration between NASA and international partners on joint projects. All information contained in this briefing is from the public domain.

Smith, Jeffrey D.↗
NASA NTRS2008

NASA's Cryogenic Fluid Management Technology Project

The Cryogenic Fluid Management (CFM) Project's primary objective is to develop storage, transfer, and handling technologies for cryogens that will support the enabling of high performance cryogenic propulsion systems, lunar surface systems and economical ground operations. Such technologies can significantly reduce propellant launch mass and required on-orbit margins, reduce or even eliminate propellant tank fluid boil-off losses for long term missions, and simplify vehicle operations. This paper will present the status of the specific technologies that the CFM Project is developing. The two main areas of concentration are analysis models development and CFM hardware development. The project develops analysis tools and models based on thermodynamics, hydrodynamics, and existing flight/test data. These tools assist in the development of pressure/thermal control devices (such as the Thermodynamic Vent System (TVS), and Multi-layer insulation); with the ultimate goal being to develop a mature set of tools and models that can characterize the performance of the pressure/thermal control devices incorporated in the design of an entire CFM system with minimal cryogen loss. The project does hardware development and testing to verify our understanding of the physical principles involved, and to validate the performance of CFM components, subsystems and systems. This database provides information to anchor our analytical models. This paper describes some of the current activities of the NASA's Cryogenic Fluid Management Project.

Tramel, Terri L.↗
NASA NTRS1992

Data management for community research projects: A JGOFS case study

Since the mid 1980s, much of the marine science research effort in the United Kingdom has been focused into large scale collaborative projects involving public sector laboratories and university departments, termed Community Research Projects. Two of these, the Biogeochemical Ocean Flux Study (BOFS) and the North Sea Project incorporated large scale data collection to underpin multidisciplinary modeling efforts. The challenge of providing project data sets to support the science was met by a small team within the British Oceanographic Data Centre (BODC) operating as a topical data center. The role of the data center was to both work up the data from the ship's sensors and to combine these data with sample measurements into online databases. The working up of the data was achieved by a unique symbiosis between data center staff and project scientists. The project management, programming and data processing skills of the data center were combined with the oceanographic experience of the project communities to develop a system which has produced quality controlled, calibrated data sets from 49 research cruises in 3.5 years of operation. The data center resources required to achieve this were modest and far outweighed by the time liberated in the scientific community by the removal of the data processing burden. Two online project databases have been assembled containing a very high proportion of the data collected. As these are under the control of BODC their long term availability as part of the UK national data archive is assured. The success of the topical data center model for UK Community Research Project data management has been founded upon the strong working relationships forged between the data center and project scientists. These can only be established by frequent personal contact and hence the relatively small size of the UK has been a critical factor. However, projects covering a larger, even international scale could be successfully supported by a network of topical data centers managing online databases which are interconnected by object oriented distributed data management systems over wide area networks.

Lowry, Roy K.↗
NASA NTRS2002

A "Sweet 16" of Rules About Teamwork

The following "Sweet 16" rules included in this paper derive from a longer paper by APPL Director Dr. Edward Hoffman and myself entitled " 99 Rules for Managing Faster, Better, Cheaper Projects." Our sources consisted mainly of "war stories" told by master project managers in my book Simultaneous Management: Managing Projects in a Dynamic Environment (AMACOM, The American Management Association, 1996). The Simultaneous Management model was a result of 10 years of intensive research and testing conducted with the active participation of master project managers from leading private organizations such as AT&T, DuPont, Exxon, General Motors, IBM, Motorola and Procter & Gamble. In a more recent study, led by Dr. Hoffman, we learned that master project managers in leading public organizations employ most of these rules as well. Both studies, in private and public organizations, found that a dynamic environment calls for dynamic management, and that is especially clear in how successful project managers think about their teams.

Laufer, Alexander↗
NASA NTRS1993

Data management for support of the Oregon Transect Ecosystem Research (OTTER) project

Management of data collected during projects that involve large numbers of scientists is an often overlooked aspect of the experimental plan. Ecosystem science projects like the Oregon Transect Ecosystem Research (OTTER) Project that involve many investigators from many institutions and that run for multiple years, collect and archive large amounts of data. These data range in size from a few kilobytes of information for such measurements as canopy chemistry and meteorological variables, to hundreds of megabytes of information for such items as views from multi-band spectrometers flown on aircraft and scenes from imaging radiometers aboard satellites. Organizing and storing data from the OTTER Project, certifying those data, correcting errors in data sets, validating the data, and distributing those data to other OTTER investigators is a major undertaking. Using the National Aeronautics and Space Administration's (NASA) Pilot Land Data System (PLDS), a Support mechanism was established for the OTTER Project which accomplished all of the above. At the onset of the interaction between PLDS and OTTER, it was not certain that PLDS could accomplish these tasks in a manner that would aid researchers in the OTTER Project. This paper documents the data types that were collected under the auspices of the OTTER Project and the procedures implemented to store, catalog, validate, and certify those data. The issues of the compliance of investigators with data-management requirements, data use and certification, and the ease of retrieving data are discussed. We advance the hypothesis that formal data management is necessary in ecological investigations involving multiple investigators using many data gathering instruments and experimental procedures. The issues and experience gained in this exercise give an indication of the needs for data management systems that must be addressed in the coming decades when other large data-gathering endeavors are undertaken by the ecological science community.

Skiles, J. W.↗
NASA NTRS2010

Cryogenic Fluid Management Technology for Moon and Mars Missions

In support of the U.S. Space Exploration Policy, focused cryogenic fluid management technology efforts are underway within the National Aeronautics and Space Administration. Under the auspices of the Exploration Technology Development Program, cryogenic fluid management technology efforts are being conducted by the Cryogenic Fluid Management Project. Cryogenic Fluid Management Project objectives are to develop storage, transfer, and handling technologies for cryogens to support high performance demands of lunar, and ultimately, Mars missions in the application areas of propulsion, surface systems, and Earth-based ground operations. The targeted use of cryogens and cryogenic technologies for these application areas is anticipated to significantly reduce propellant launch mass and required on-orbit margins, to reduce and even eliminate storage tank boil-off losses for long term missions, to economize ground pad storage and transfer operations, and to expand operational and architectural operations at destination. This paper organizes Cryogenic Fluid Management Project technology efforts according to Exploration Architecture target areas, and discusses the scope of trade studies, analytical modeling, and test efforts presently underway, as well as future plans, to address those target areas. The target areas are: liquid methane/liquid oxygen for propelling the Altair Lander Ascent Stage, liquid hydrogen/liquid oxygen for propelling the Altair Lander Descent Stage and Ares V Earth Departure Stage, liquefaction, zero boil-off, and propellant scavenging for Lunar Surface Systems, cold helium and zero boil-off technologies for Earth-Based Ground Operations, and architecture definition studies for long term storage and on-orbit transfer and pressurization of LH2, cryogenic Mars landing and ascent vehicles, and cryogenic production via in situ resource utilization on Mars.

Doherty, Michael P.↗
NASA NTRS2018

An “EPIIC” Vision to Evolve Project Integration, Innovation, and Collaboration with Broad Impact for How NASA Executes Complex Projects

Evolving Project Integration, Innovation, and Collaboration (EPIIC) is a vision defined to transform the way projects manage information to support real-time decisions, capture best practices and lessons learned, perform assessments, and manage risk across a portfolio of projects. The foundational project management needs for data and information will be revolutionized through innovations on how we manage and access that data, implement configuration control, and certify compliance. The embedded intelligence of new interactive data interfaces integrate technical and programmatic data such that near real time analytics can be accomplished to more efficiently and accurately complete systems engineering and project management tasks. The system-wide data analytics that are integrated into customized data interfaces allows the growing team of engineers and managers required to develop and implement major NASA missions the ability to access authoritative source(s) of system information while greatly reducing the labor required to complete system assessments. This would allow, for example, much of what is accomplished in a scheduled design review to take place as needed, between any team members, at any time. An intelligent data interface that rigorously integrates systems engineering and project management information in near real time can provide substantially greater insight for systems engineers, project managers, and the large diverse teams required to complete a complex project. System engineers, programmatic personnel (those who focus on cost, schedule, and risk), the technical engineering disciplines, and project management can realize immediate benefit from the shared vision described herein. Implementation of the vision also enables significant improvements in the performance of the engineered system being developed.

Moreland, Robert J.↗