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 1,621 records · Page 90

Mars Observer Orbit Insertion Briefing

Steve Wall is the host of this video entitled, "Return to the Red Planet". Live animation of the Mars Observer orbiting Mars is presented. Steve Wall explains the spacecraft insertion maneuver and also explains the purpose for the Mars Observer launch. Live coverage of the Cape Canaveral launch of the Mars Observer is also presented. Suzanne Dodd, Chief of the Mission Planning team describes the burn start and how the spacecraft will be captured by Mars' gravity. Glenn Cunningham, Mars Observer Project Manager, gives background information on the Mars Observer and describes the organizations behind the Mars Observer Spacecraft, such as the Deep Space Network, the Mission Operation Support Office, Science Investigators, the Flight Engineering Office, Operations Office, and the Ground Data System Office. Dr. William Piotrowski, Acting Director, Solar System Exploration Division, NASA, talks about the purpose of the Mars Pathfinder which is to develop the technology and systems for landing small science packages on Mars. Mr. Roger Gibbs, Former Mars Observer Spacecraft Systems Engineer, tells us how the Mars Observer was built and describes the structural elements on the Mars Observer. The 11-month cruise period for the spacecraft is given by Joseph Beerer, Manager of the Engineering office. The thrust for the Mars Orbit Insertion is described by Ronald Klemetson, Technical Manager, Propulsion Subsystem Jet Propulsion Laboratory (JPL). George Chen, Lead Engineer Attitude and Articulation Subsystem Spacecraft Team, explains the importance of the attitude control engines on the Spacecraft. Marvin Traxler, Manager of Tracking and Data Acquisition, describes how searching for a signal from the Mars Observer works. See NONP-NASA-VT-2000081555 for a continuation of this discussion with Marvin Traxler.

Source record↗

Aerospace Systems Design in NASA's Collaborative Engineering Environment

Past designs of complex aerospace systems involved an environment consisting of collocated design teams with project managers, technical discipline experts, and other experts (e.g., manufacturing and systems operation). These experts were generally qualified only on the basis of past design experience and typically had access to a limited set of integrated analysis tools. These environments provided less than desirable design fidelity, often lead to the inability of assessing critical programmatic and technical issues (e.g., cost, risk, technical impacts), and generally derived a design that was not necessarily optimized across the entire system. The continually changing, modern aerospace industry demands systems design processes that involve the best talent available (no matter where it resides) and access to the the best design and analysis tools. A solution to these demands involves a design environment referred to as collaborative engineering. The collaborative engineering environment evolving within the National Aeronautics and Space Administration (NASA) is a capability that enables the Agency's engineering infrastructure to interact and use the best state-of-the-art tools and data across organizational boundaries. Using collaborative engineering, the collocated team is replaced with an interactive team structure where the team members are geographical distributed and the best engineering talent can be applied to the design effort regardless of physical location. In addition, a more efficient, higher quality design product is delivered by bringing together the best engineering talent with more up-to-date design and analysis tools. These tools are focused on interactive, multidisciplinary design and analysis with emphasis on the complete life cycle of the system, and they include nontraditional, integrated tools for life cycle cost estimation and risk assessment. NASA has made substantial progress during the last two years in developing a collaborative engineering environment. NASA is planning to use this collaborative engineering engineering infrastructure to provide better aerospace systems life cycle design and analysis, which includes analytical assessment of the technical and programmatic aspects of a system from "cradle to grave." This paper describes the recent NASA developments in the area of collaborative engineering, the benefits (realized and anticipated) of using the developed capability, and the long-term plans for implementing this capability across Agency.

Monell, Donald W.↗

Atmosphere of Freedom: Sixty Years at the NASA Ames Research Center

Throughout Ames History, four themes prevail: a commitment to hiring the best people; cutting-edge research tools; project management that gets things done faster, better and cheaper; and outstanding research efforts that serve the scientific professions and the nation. More than any other NASA Center, Ames remains shaped by its origins in the NACA (National Advisory Committee for Aeronautics). Not that its missions remain the same. Sure, Ames still houses the world's greatest collection of wind tunnels and simulation facilities, its aerodynamicists remain among the best in the world, and pilots and engineers still come for advice on how to build better aircraft. But that is increasingly part of Ames' past. Ames people have embraced two other missions for its future. First, intelligent systems and information science will help NASA use new tools in supercomputing, networking, telepresence and robotics. Second, astrobiology will explore lore the prospects for life on Earth and beyond. Both new missions leverage Ames long-standing expertise in computation and in the life sciences, as well as its relations with the computing and biotechnology firms working in the Silicon Valley community that has sprung up around the Center. Rather than the NACA missions, it is the NACA culture that still permeates Ames. The Ames way of research management privileges the scientists and engineers working in the laboratories. They work in an atmosphere of freedom, laced with the expectation of integrity and responsibility. Ames researchers are free to define their research goals and define how they contribute to the national good. They are expected to keep their fingers on the pulse of their disciplines, to be ambitious yet frugal in organizing their efforts, and to always test their theories in the laboratory or in the field. Ames' leadership ranks, traditionally, are cultivated within this scientific community. Rather than manage and supervise these researchers, Ames leadership merely guided them, represents them to NASA headquarters and the world outside, then steps out of the way before they get run over.

Bugos, Glenn E.↗

Comprehensive Modeling of the Apache With CAMRAD II

This paper presents a report of a multi year study of the U.S. Army LONGBOW APACHE (AH-64D) aircraft. The goals of this study were to provide the Apache Project Managers Office (PMO) with a broad spectrum of calibrated comprehensive and CFD models of the AH-64D aircraft. The goal of this paper is to present an overview of the comprehensive model which has been developed. The CAMRAD II computer code was chosen to complete this task. The paper first discusses issues that must be addressed when modeling the Apache using CAMRAD. The work required the acquisition of a data base for the aircraft and the development and application of a multidisciplinary computer model. Sample results from various parts of the model are presented. Conclusions with regard to the strengths and weaknesses of simulations based on this model are discussed.

Jones, Henry E.↗

Towards a Theory for Integration of Mathematical Verification and Empirical Testing

From the viewpoint of a project manager responsible for the V&V (verification and validation) of a software system, mathematical verification techniques provide a possibly useful orthogonal dimension to otherwise standard empirical testing. However, the value they add to an empirical testing regime both in terms of coverage and in fault detection has been difficult to quantify. Furthermore, potential cost savings from replacing testing with mathematical verification techniques cannot be realized until the tradeoffs and synergies can be formulated. Integration of formal verification with empirical testing is also difficult because the idealized view of mathematical verification providing a correctness proof with total coverage is unrealistic and does not reflect the limitations imposed by computational complexity of mathematical techniques. This paper first describes a framework based on software reliability and formalized fault models for a theory of software design fault detection - and hence the utility of various tools for debugging. It then describes a utility model for integrating mathematical and empirical techniques with respect to fault detection and coverage analysis. It then considers the optimal combination of black-box testing, white-box (structural) testing, and formal methods in V&V of a software system. Using case studies from NASA software systems, it then demonstrates how this utility model can be used in practice.

Lowry, Michael↗

Sounds like Team Spirit

I recently accompanied my son Dan to one of his guitar lessons. As I sat in a separate room, I focused on the music he was playing and the beautiful, robust sound that comes from a well-played guitar. Later that night, I woke up around 3 am. I tend to have my best thoughts at this hour. The trouble is I usually roll over and fall back asleep. This time I was still awake an hour later, so I got up and jotted some notes down in my study. I was thinking about the pure, honest sound of a well-played instrument. From there my mind wandered into the realm of high-performance teams and successful projects. (I know this sounds weird, but this is the sort of thing I think about at 3 am. Maybe you have your own weird thoughts around that time.) Consider a team in relation to music. It seems to me that a crack team can achieve a beautiful, perfect unity in the same way that a band of brilliant musicians can when they're in harmony with one another. With more than a little satisfaction I have to admit, I started to think about the great work performed for you by the Knowledge Sharing team, including this magazine you are reading. Over the past two years I personally have received some of my greatest pleasures as the APPL Director from the Knowledge Sharing activities - the Masters Forums, NASA Center visits, ASK Magazine. The Knowledge Sharing team expresses such passion for their work, just like great musicians convey their passion in the music they play. In the case of Knowledge Sharing, there are many factors that have made this so enjoyable (and hopefully worthwhile for NASA). Three ingredients come to mind -- ingredients that have produced a signature sound. First, through the crazy, passionate playing of Alex Laufer, Michelle Collins, Denise Lee, and Todd Post, I always know that something startling and original is going to come out of their activities. This team has consistently done things that are unique and innovative. For me, best of all is that they are always trying to improve on what they've done before. Second, success in any endeavor stems from people who know how to interpret a composition to sound beautiful when played in a different style. For Knowledge Sharing to work, it must be adapted, reinterpreted, shaped and played with at the centers. In this regard, we've been blessed with another crazy, passionate, inspired artist named Claire Smith. Claire has turned Ames Research Center in California into APPL-west. She is so good and committed to what she does that I just refer people to her whenever they have questions about implementing project management development at the field level. Finally, any great effort requires talented people working behind the scenes, the people who formulate a business approach and know how to manage the money so that the music gets heard. I have known many brilliant and creative people with a ton of ideas that never take off due to an inability to work the business. Again, the Knowledge Sharing team has been fortunate to have competent and passionate people, specifically Tony Maturo and his procurement team at Goddard Space Flight Center, to make sure the process is in place to support the effort. This kind of support is every bit as crucial as the activity itself, and the efforts and creativity that go into successful procurement and contracting is a vital ingredient of this successful team.

Hoffman, Edward↗

Willpower

I am struck by how often failure is blamed on a lack of discipline. You often hear losing coaches cite this as the reason for a big loss. I don't recall the last time I heard one say that his team lost a game because of his players' lack of skill. I think a breakdown in discipline is also one of the key reasons why program and project management teams fail to meet expectations. The first program I ever managed had a clear set of priorities. I understood the mandate, and so did everyone else on the team. We set an ambitious schedule and started to work fervently. Not too long into the program the customer wanted to know what performance he was going to get. I replied by categorizing the performance parameters into three bins: 1. Performance you will get. 2. Performance you may get. 3. Performance that there's no way you will get. Did that cause an uproar. The customer demanded everything in the second bin be moved to the first, and most everything in the third bin moved to the second. My immediate impulse was to agree, but I managed to overcome that. In my heart, I knew that we would never meet the already ambitious schedule if we had to deliver more performance. No was my answer. The program turned out to be a huge success, but the result would have been largely different had senior management or I failed to maintain discipline.

Little, Terry↗

Loss and Recovery

The author recounts his experiences of the loss of the QuickTOMS (Total Ozone Mapping Spectrometer) spacecraft, for which he was project manager. He draws from the launch failure lessons on leadership, coping with loss and maintaining morale.

Schwer, Ken↗

Is There A Perfect Organization?

A NASA project manager describes her experiences working during a leave of absence at Cisco Systems. She provides an overview of Cisco's corporate culture, particularly the level of attention which its managers paid to the opinions of subordinate employees. She also describes the problems she and other employees had with one manager which caused her to return to NASA.

Schonfeld, Julie↗

A Big Raise, A Promotion, Or...

A project manager reflects on the benefits of assigning awards to employees, versus traditional rewards involving money or competition. He includes an anecdote from his own experience to illustrate how employees appreciate official recognition.

Cameron, W. Scott↗

Test What You Fly?

It was the first time on any NASA project I know of that all the instruments on an observatory came off for rework or calibration after the full range of environmental tests, and then were reintegrated at the launch center without the benefit of an observatory environmental retest. Perhaps you've heard the expression, 'Test what you fly, fly what you test'? In theory, it's hard to argue with that. In this case, I was willing to take the risk of not testing what I flew. As the project manager for the Advanced Composition Explorer (ACE) mission, I was the one who ultimately decided what risks to take, just as it was my responsibility to get buy-in from the stakeholders.

Margolies, Don↗

ASK Talks With Judy Stokley

In the summer of 1997, Judy Stokley took over as Program Director of the Air-to-Air Joint System Project Office (JSPO) at Eglin Air Force Base in Florida. As the JSPO Program Director, she directed much of her attention to reforming the Advanced Medium Range Air to Air Missile (AMRAAM) program, which had been operational since 1991 and was presently being produced for the Air Force, Navy, Marine Corps, and many international customers. Upon careful analysis of the program, she found it rife with problems. Two of the most pressing included a bloated Average Unit Procurement Cost and an Air Force mandated draw down plan that had not been met. In this interview, following her presentation at the Fourth NASA Masters Forum of Program and Project Managers in Dallas last February, Stokley discusses some of the difficulties she experienced in carrying out the AMRAAM reforms. Stokley is presently Air Force Program Executive Officer for Weapons in Washington, D.C. She is responsible for the cost, schedule, and technical performance of a portfolio of air-to-air and air-to-ground weapons programs. These programs represent the leading edge of weapons technology, including developing the next generation of precision-guided munitions -- 'smart' bombs -- and air superiority missiles.

Stokley, Judy↗

Motor Controllers

Kollmorgen Corporation's Mermaid II two person submersible is propeller-driven by a system of five DC brushless motors with new electronic controllers that originated in work performed in a NASA/DOE project managed by Lewis Research Center. A key feature of the system is electric commutation rather than mechanical commutation for converting AC current to DC.

Source record↗

Dressing Down

Smiles and laughter reduce stress. They also renew energy and trust in ourselves and others. A characteristic of any good project manager is his or her willingness to challenge the conventional way of doing things. Use whatever tools you have available, including a sense of humor. Do you have examples of how you learned from experience, especially examples that challenged the status quo?

Schabes, Harvey↗

The Digital Space Shuttle, 3D Graphics, and Knowledge Management

The Digital Shuttle is a knowledge management project that seeks to define symbiotic relationships between 3D graphics and formal knowledge representations (ontologies). 3D graphics provides geometric and visual content, in 2D and 3D CAD forms, and the capability to display systems knowledge. Because the data is so heterogeneous, and the interrelated data structures are complex, 3D graphics combined with ontologies provides mechanisms for navigating the data and visualizing relationships.

Gomez, Julian E.↗

Dropping in on Mars

Here I was: 26 years old, I had never worked on a flight project before, and all eyes were on me. Every time I walked by the Pathfinder project office, Tony Spear, the project manager, would throw his arm around me and announce, 'Hey everybody, the whole mission is riding on this guy right here.' Our task was to design and build airbags for Pathfinder s landing on Mars - an approach that had never been used on any mission. Airbags may seem like a simple, low-tech product, but it was eye-opening to discover just how little we knew about them. We knew that the only way to find out what we needed to learn was to build prototypes and test them. We just didn t know how ignorant we were going to be. Airbags seemed like a crazy idea to a lot of people. Nobody ever said that, mind you, but there seemed to be a widespread feeling that the airbags weren t going to work. 'We ll let you guys go off and fool around until you fall flat on your faces.' That was the unspoken message I received day after day.

Rivellini, Tommaso P.↗

See Attachment

Since e-mail generates itself on a round-the-clock, daily basis, it's not unusual for me to receive an average of fifty e-mails a day, or more than 300 a week. That s a lot of e-mail. I have spoken with many of my fellow project managers about my relationship with e-mail. In my case, reading and responding to it is a temptation almost too hard to resist. When I receive an e-mail I tend to want to stop everything I m doing, and open and answer it. Indeed, in my life you could say e-mail is a force to be reckoned with. Interestingly, my fascination with mail began a long time ago. I trace it back to my days as a young boy when I started receiving my first letters from friends and family. Walking home from school, I was often filled with curiosity, wondering if I had received any mail that day. In college, I knew the exact time the mail was delivered, and I headed for my mailbox as close to that hour as I could. After that, I served in an Army Reserve Post Office Unit, where I came to realize how important a postal unit was to the military. There were many others like myself, far from home, who relied on the written word to stay connected to the people in their lives. Over the years I have changed in many ways, and so has the mail. But the same sense of connection, and the same urge to respond to someone who has written me, remains. The 24/7 nature of e-mail has compounded the situation. It is relentless in its pursuit of my time and attention-and, as such, e-mail has become something I have had to manage in a variety of situations

Cameron, W. Scott↗

Lessons from the Dark Side

Lessons to project managers Include the following in case of failure: a) make a timeline of events and include everything that is known; b) put down known facts and check every theory against them; c) don't beat the data until it confesses, i.e., know when to stop trying to force-fit a scenario; d) do not arrive at a conclusion too rapidly. Make sure any deviation form the norm is explained--remember the wrong conclusion is prologue to the next failure; and e) know when to stop.

Madden, Jerry↗