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 379 records · Page 21

Optimization of knowledge-based systems and expert system building tools

The objectives of the NASA-AMES Cooperative Agreement were to investigate, develop, and evaluate, via test cases, the system parameters and processing algorithms that constrain the overall performance of the Information Sciences Division's Artificial Intelligence Research Facility. Written reports covering various aspects of the grant were submitted to the co-investigators for the grant. Research studies concentrated on the field of artificial intelligence knowledge-based systems technology. Activities included the following areas: (1) AI training classes; (2) merging optical and digital processing; (3) science experiment remote coaching; (4) SSF data management system tests; (5) computer integrated documentation project; (6) conservation of design knowledge project; (7) project management calendar and reporting system; (8) automation and robotics technology assessment; (9) advanced computer architectures and operating systems; and (10) honors program.

Yasuda, Phyllis↗

Galileo Mission Science Briefing

The first of two tapes of the Galileo Mission Science press briefing is presented. The panel is moderated by George Diller from the Kennedy Space Center (KSC) Public Affairs Office. The participants are John Conway, the director of Payload and operations at Kennedy; Donald E. Williams, Commander of STS-43, the shuttle mission which will launch the Galileo mission; John Casani, the Deputy Assistant Director of Flight Projects at the Jet Propulsion Lab (JPL); Dick Spehalski, Galileo Project Manager at JPL; and Terrence Johnson, Galileo Project Scientist at JPL. The briefing begins with an announcement of the arrival of the Galileo Orbiter at KSC. The required steps prior to the launch are discussed. The mission trajectory and gravity assists from planetary and solar flybys are reviewed. Detailed designs of the orbiter are shown. The distance that Galileo will travel from the sun precludes the use of solar energy for heat. Therefore Radioisotope heater units are used to keep the equipment at operational temperature. A video of the arrival of the spacecraft at KSC and final tests and preparations is shown. Some of the many science goals of the mission are reviewed. Another video showing an overview of the Galileo mission is presented. During the question and answer period, the issue of the use of plutonium on the mission is broached, which engenders a review of the testing methods used to ensure the safety of the capsules containing the hazardous substance. This video has actual shots of the orbiter, as it is undergoing the final preparations and tests for the mission.

Source record↗

How Do We Work Together?

In essence, project management is about people. Virtually every successful project is defined by good relations between the people involved. In the same way, nearly every failed or troubled project is about poor relationships between the people involved. Let's consider one type of relationship: the one between the government and the contractor. It's easy to say that a contractor must earn the government's trust, but what does that mean in practice? Who needs to earn whose trust? What's the timeline for doing that? How does anyone know when he or she is trusted? What is the relationship supposed to be like before one feels like trust has really been established? So many questions it makes my head hurt. I have always found it better to begin a relationship assuming that everyone is trustworthy until, and unless, something occurs to belie trust.

Little, Terry↗

STS-121: Discovery Mission Management Team Briefing

The briefing opened with Bruce Buckingham (NASA Public Affairs) introducing John Shannon (Chairman, Mission Management Team, JSC), John Chapman (External Tank Project Manager), Mike Leinbach (Shuttle Launch Director), and 1st Lt. Kaleb Nordgren (USAF 45th Weather Squadron). John Shannon reported that the team for hydrogen loading was proceeding well and the external tank detanking was completed. During detanking the inspection team cracked foam caused by condensation and ice formation as the tank expanded and contracted. Aerothermal analysis and analysis fro ice formation will be completed before launch. John Chapman explained the mechanics of the external tank design, the foam cracking, bracket design, etc. Mike Leinbach discussed the inspection teams and their inspection final inspection for ice formation before and after external tank filling. The inspection team of eight very experienced personnel also use telescopes with cameras to find any problems before launch. Kaleb Nordgren discussed weather and said there was a 40% chance of weather prohibiting launch. The floor was the opened for questions from the press.

Source record↗

Dawn: Cooperation, not Control

On September 27, 2007, a Delta II rocket carrying the Dawn spacecraft lifted off from Kennedy Space Center. Part of NASAs Discovery program, the $370 million Dawn mission began its three-billion-mile voyage to the asteroid belt to study the asteroid Vesta and Ceres, a dwarf planet. The spacecraft is scheduled to reach Vesta in 2011. After spending nine months measuring the composition, shape, and topography of that body, it will travel a billion miles to carry out a similar analysis of Ceres in 2015. The Important Lessons: The demands of Dawn and other challenging missions have taught some important lessons for successful program and project management. These are the main ones: a) Program management, particularly of uncoupled and loosely coupled projects, should be more about enabling than controlling. You're working with motivated, high-performing teams and institutions with a track record of quality and success. Emphasize commander's intent over rudder control; let them know where you want to go and when you want to be there, then let them figure out how to get there. b) Open and honest discussion of issues is essential. People fill the void of the unknown with their worst fears. Get folks around the table and have open, honest, and frank dialogue. I've seldom seen this fail to get to the root of issues. c) You have to earn your seat at the table, proving that you are competent, trustworthy, and dedicated to the success of the mission. d) Know when to fold 'em. Your pride can get rolled up in making a milestone or launch date, but you have to make a judgment based on the realities of the situation and not wear down the team trying to meet an increasingly impossible deadline. e) The NASA governance model that gives a voice to the concerns of engineers and safety experts works-trust it and use it.

May, Todd↗

Using Model-Based Systems Engineering to Provide Artifacts for NASA Project Life-cycle and Technical Reviews

This paper is for the AIAA Space Conference. The ability of systems engineers to use model-based systems engineering (MBSE) to generate self-consistent, up-to-date systems engineering products for project life-cycle and technical reviews is an important aspect for the continued and accelerated acceptance of MBSE. Currently, many review products are generated using labor-intensive, error-prone approaches based on documents, spreadsheets, and chart sets; a promised benefit of MBSE is that users will experience reductions in inconsistencies and errors. This work examines features of SysML that can be used to generate systems engineering products. Model elements, relationships, tables, and diagrams are identified for a large number of the typical systems engineering artifacts. A SysML system model can contain and generate most systems engineering products to a significant extent and this paper provides a guide on how to use MBSE to generate products for project life-cycle and technical reviews. The use of MBSE can reduce the schedule impact usually experienced for review preparation, as in many cases the review products can be auto-generated directly from the system model. These approaches are useful to systems engineers, project managers, review board members, and other key project stakeholders.

MBSE↗

Using Model-Based Systems Engineering To Provide Artifacts for NASA Project Life-Cycle and Technical Reviews

The ability of systems engineers to use model-based systems engineering (MBSE) to generate self-consistent, up-to-date systems engineering products for project life-cycle and technical reviews is an important aspect for the continued and accelerated acceptance of MBSE. Currently, many review products are generated using labor-intensive, error-prone approaches based on documents, spreadsheets, and chart sets; a promised benefit of MBSE is that users will experience reductions in inconsistencies and errors. This work examines features of SysML that can be used to generate systems engineering products. Model elements, relationships, tables, and diagrams are identified for a large number of the typical systems engineering artifacts. A SysML system model can contain and generate most systems engineering products to a significant extent and this paper provides a guide on how to use MBSE to generate products for project life-cycle and technical reviews. The use of MBSE can reduce the schedule impact usually experienced for review preparation, as in many cases the review products can be auto-generated directly from the system model. These approaches are useful to systems engineers, project managers, review board members, and other key project stakeholders.

SE Product↗

The Value Proposition of Multi-Megawatt Electric Power/Propulsion for the Human Exploration of Mars

NASA and other space agencies have been offering stakeholders an architecture for the human exploration of Mars that has remained essentially unchanged since the 1960's. The mission duration and launch mass are the two first order figures of merit that drive the total cost of such an architecture. The options studied to date center on the "conjunction class" or "Long Stay" mission, in which surface infrastructure elements are sent ahead on uncrewed, slow trajectories requiring a minimum amount of propellant, and the crewed elements are sent at the synotic cycle's shortest trajectory, stay on Mars until the next close alignment, and then return to Earth. Total crewed mission durations for these architectures range from 900 to 1100 days, with variations driven primarily by trades between the amount of propellant launched and the effective specific mass of the propulsion technology assumed (e.g., chemical, nuclear thermal, solar electric, nuclear electric). Mars transit propulsion systems assumed in mission architectures studied to date have all resulted in architectural figures of merit that drive the cost to a level of "too much." However, nuclear electric propulsion (NEP) technology offers a "knob" that might be turned to enable a radically different Mars architecture, whose launch mass and mission duration may enable a value proposition more palatable to mission stakeholders. Mars architectures studied to date have assumed an NEP system providing 2.5 MWe at a specific mass of no less than 20 kg/kWe. This has often been seen as obtainable with a moderately high temperature fission reactor. An NEP system providing 15 MWe at specific mass of ~1 kg/kWe, though, could enable a short stay (30 days on surface) Mars mission, requiring only two or three SLS-class launch vehicles and a total mission duration of under one calendar year. However, turning this NEP "knob" would require a high risk development program driving innovation on the order of that delivered by the Manhattan Project, but for a fraction of the cost. Any technology option that might offer such a capability at such a development cost now stands at a low Technology Readiness Level (TRL) 3, would be based on a nuclear energy source (likely fusion), and would require an extremely high risk (and rapid) development effort. The aggressive, parallel path project management paradigm exemplified by the original Manhattan Project might have the best chance of success. An energy source developed in this manner may also have a major impact on the terrestrial power industry.

power↗

Reference Guide for Project-Control Account Managers

The purpose of this guide is intended to be a quick reference for a Project-Control Account Manager (P-CAM) or technical manager empowered with a project’s cost, schedule, and technical responsibilities of a control account(s) when Earned Value Management (EVM) is required. The overall objective is to support the P-CAM in performing their responsibilities as they relate to EVM. In addition, the reference guide describes at a summary level how the scope, schedule, and budget of a project integrate for optimal planning and control of prime contracts and in-house projects. Because NASA implements a diverse and unique portfolio of projects, those projects have traditionally created project-specific systems to manage planning and performance analysis. However, establishment and implementation of a project management system that is common across all centers and mission directorates will facilitate the adoption of best business practices. In addition, the application of timely and predictive analysis, as well as, providing all stakeholders with greater insight into project performance will enhance opportunities for project success. For more detailed information, refer to the NASA EVM System Description; Integrated Baseline Review (IBR) Handbook; EVM Implementation Handbook; Schedule Management Handbook; Work Breakdown Structure (WBS) Handbook; and other agency/industry documentation. In addition, you may contact your local center’s EVM Focal Points. All this information and more can be found at and/or the NASA Engineering Network located at https://nen.nasa.gov/web/pm.

Christopher Lewis Sadler↗

NASA PERT time II

Program Evaulation and Review Technique (PERT) is disciplined management technique involving computer processing. NASA PERT Time 11 gives project manager insight into current and future project development and forewarns of potential problems. Program utilizes modular technique. Module is "fragnet"; once aspects of project are described in terms of fragnets, control network is automatically generated. Program is written in FORTRAN IV and OS Assembler for batch execution and has been implemented on IBM 370.

Bainbridge, R. C.↗

NASA Systems Engineering Handbook

This handbook brings the fundamental concepts and techniques of systems engineering to NASA personnel in a way that recognizes the nature of NASA systems and environment. It is intended to accompany formal NASA training courses on systems engineering and project management when appropriate, and is designed to be a top-level overview. The concepts were drawn from NASA field center handbooks, NMI's/NHB's, the work of the NASA-wide Systems Engineering Working Group and the Systems Engineering Process Improvement Task team, several non-NASA textbooks and guides, and material from independent systems engineering courses taught to NASA personnel. Five core chapters cover systems engineering fundamentals, the NASA Project Cycle, management issues in systems engineering, systems analysis and modeling, and specialty engineering integration. It is not intended as a directive. Superseded by: NASA/SP-2007-6105 Rev 1 (20080008301).

Shishko, Robert↗

ASK Magazine

Welcome to the Academy of Program and Project Leadership (APPL) and ASK Magazine. APPL helps NASA managers and project teams accomplish today's missions and meet tomorrow's challenges by providing performance enhancement services and tools, supporting career development programs, sponsoring knowledge sharing events and publications, and creating opportunities for project management collaboration with universities, professional associations, industry partners and other government agencies. ASK Magazine grew out of APPL's 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 ali here in ASK. Stories in this issue include: Earthly Considerations on Mars, Getting Politically Active, Stumping for the Project, Grins & Giggles: The Launch Pad to High Performance, Transfer Wisdom Workshops: Coming to a NASA Center Near You, Project Management: The Television Show, Lessons Learned Again and Again and Again, Implementation Reviews, ASK Talks with Dr. Michael Hecht, and What Is This Fourth Dimension?.

Laufer, Alexander↗

The management of research institutions: A look at government laboratories

Technology development; project management; employment patterns; research productivity; legal status of support services; functions of senior executives; the role of the sponsoring agency; research diversification; obstacles to technical innovation; organizational structures; and personnel management are addressed.

Mark, H.↗

Science operations management

The operation teams engaged in the IR Astronomical Satellite (IRAS) project included scientists from the IRAS International Science Team. The detailed involvement of these scientists in the design, testing, validation, and operations phases of the IRAS mission contributed to the success of this project. The Project Management Group spent a substantial amount of time discussing science-related issues, because science team coleaders were members from the outset. A single scientific point-of-contact for the Management Group enhanced the depth and continuity of agreement reached in decision-making.

Squibb, G. F.↗

Earned Value Management (EVM) System Description

The purpose of this Earned Value Management (EVM) System Description is to provide guidance in NASA’s Earned Value Management Capability for the effective application, implementation, and utilization of EVM on NASA programs, projects, major contracts and subcontracts. EVM is a project management process that effectively integrates a project’s scope of work with schedule and cost elements for optimum project planning and control. The goal is to achieve timely and accurate quantification of progress that will facilitate management by exception and enable early visibility into the nature and the magnitude of technical problems as well as the intended course and success of corrective actions. This system description contains detailed information on implementation of EVM processes, procedures, roles and responsibilities.

Schumann, Deborah C.↗

Earned Value Management (EVM) System Description

The purpose of this Earned Value Management (EVM) System Description is to provide guidance in NASA’s Earned Value Management Capability for the effective application, implementation, and utilization of EVM on NASA programs, projects, major contracts and subcontracts. EVM is a project management process that effectively integrates a project’s scope of work with schedule and cost elements for optimum project planning and control. The goal is to achieve timely and accurate quantification of progress that will facilitate management by exception and enable early visibility into the nature and the magnitude of technical problems as well as the intended course and success of corrective actions. This system description contains detailed information on implementation of EVM processes, procedures, roles and responsibilities.

Christopher Lewis Sadler↗