Search NASA⌕ Search

SEARCH · Search NASA

Results for “technical 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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Understanding and Improving High-Performance I/O Subsystems

This research program has been conducted in the framework of the NASA Earth and Space Science (ESS) evaluations led by Dr. Thomas Sterling. In addition to the many important research findings for NASA and the prestigious publications, the program has helped orienting the doctoral research program of two students towards parallel input/output in high-performance computing. Further, the experimental results in the case of the MasPar were very useful and helpful to MasPar with which the P.I. has had many interactions with the technical management. The contributions of this program are drawn from three experimental studies conducted on different high-performance computing testbeds/platforms, and therefore presented in 3 different segments as follows: 1. Evaluating the parallel input/output subsystem of a NASA high-performance computing testbeds, namely the MasPar MP- 1 and MP-2; 2. Characterizing the physical input/output request patterns for NASA ESS applications, which used the Beowulf platform; and 3. Dynamic scheduling techniques for hiding I/O latency in parallel applications such as sparse matrix computations. This study also has been conducted on the Intel Paragon and has also provided an experimental evaluation for the Parallel File System (PFS) and parallel input/output on the Paragon. This report is organized as follows. The summary of findings discusses the results of each of the aforementioned 3 studies. Three appendices, each containing a key scholarly research paper that details the work in one of the studies are included.

El-Ghazawi, Tarek A.↗
NASA NTRS2003

Report from the School of Experience: Lessons-Learned on NASA's EOS/ICESat Mission

Abstract-NASA s Earth Observing System EOS) Ice, Cloud, and Land Elevation Satellite (ICESat) mission was one of the first missions under Goddard Space Flight Center s (then-) new Rapid Spacecraft Development Office. This paper explores the lessons-learned under the ICESat successful implementation and launch, focusing on four areas: Procurement., Management, Technical, and Launch and Early Operations. Each of these areas is explored in a practical perspective of communication, the viewpoint of the players, and the interactions among the organizations. Conclusions and lessons-learned are summarized in the final section.

Anselm, William↗
NASA NTRS1999

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 operations). 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 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 geographically 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 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 the Agency.

Monell, Donald W.↗
NASA NTRS2004

Mothers of Invention: Hubble Engineers Push Robotic 'Evolution' to Save Telescope, Enable New Exploration

Robotic technology being developed out of necessity to keep the Hubble Space Telescope operating could also lead to new levels of man-machine team-work in deep-space exploration down the road-if it survives the near-term scramble for funding. Engineers here who have devoted their NASA careers to the concept of humans servicing the telescope in orbit are planning modifications to International Space Station (ISS) robots that would leave the humans on the ground. The work. forced by post-Columbia flight rules that killed a planned shuttle-servicing mission to Hubble, marks another step in the evolution of robot-partners for human space explorers. "Hubble has always been a pathfider for this agency," says Mike Weiss. Hubble deputy program manager technical. "When the space station was flown and assembled, Hubble was the pathfinder. not just for modularity, but for operations, for assembly techniques. Exploration is the next step. Things we're going to do on Hubble are going to be applied to exploration. It's not just putting a robot in space. It's operating a robot in space. It's adapting that robot to what needs to be done the next time you're up there."

Morring, Frank, Jr.↗
NASA NTRS2007

The Challenges of Integrating NASA's Human, Budget, and Data Capital within the Constellation Program's Exploration Launch Projects Office

The U.S. Vision for Space Exploration directs NASA to retire the Space Shuttle in 2010 and replace it with safe, reliable, and cost-effective space transportation systems for crew and cargo travel to the Moon, Mars, and beyond. Such emerging space transportation initiatives face massive organizational challenges, including building and nurturing an experienced, dedicated team with the right skills for the required tasks; allocating and tracking the fiscal capital invested in achieving technical progress against an integrated master schedule; and turning generated data into useful knowledge that equips the team to design and develop superior products for customers and stakeholders. It has been more than 30 years since the Space Shuttle was designed; therefore, the current aerospace workforce has limited experience with developing new designs for human-rated spaceflight hardware. To accomplish these activities, NASA is using a wide range of state-of-the-art information technology tools that connect its diverse, decentralized teams and provide timely, accurate information for decision makers. In addition, business professionals are assisting technical managers with planning, tracking, and forecasting resource use against an integrated master schedule that horizontally and vertically interlinks hardware elements and milestone events. Furthermore, NASA is employing a wide variety of strategies to ensure that it has the motivated and qualified staff it needs for the tasks ahead. This paper discusses how NASA's Exploration Launch Projects Office, which is responsible for delivering these new launch vehicles, integrates its resources to create an engineering business environment that promotes mission success, which is defined by replacing the Space Shuttle by 2014 and returning to the Moon by 2020.

Kidd, Luanne↗
NASA NTRS2009

Human Systems Integration (HSI) Case Studies from the NASA Constellation Program

The National Aeronautics and Space Administration (NASA) Constellation Program is responsible for planning and implementing those programs necessary to send human explorers back to the moon, onward to Mars and other destinations in the solar system, and to support missions to the International Space Station. The Constellation Program has the technical management responsibility for all Constellation Projects, including both human rated and non-human rated vehicles such as the Crew Exploration Vehicle, EVA Systems, the Lunar Lander, Lunar Surface Systems, and the Ares I and Ares V rockets. With NASA s new Vision for Space Exploration to send humans beyond Earth orbit, it is critical to consider the human as a system that demands early and continuous user involvement, inclusion in trade offs and analyses, and an iterative "prototype/test/ redesign" process. Personnel at the NASA Johnson Space Center are involved in the Constellation Program at both the Program and Project levels as human system integrators. They ensure that the human is considered as a system, equal to hardware and software vehicle systems. Systems to deliver and support extended human habitation on the moon are extremely complex and unique, presenting new opportunities to employ Human Systems Integration, or HSI practices in the Constellation Program. The purpose of the paper is to show examples of where human systems integration work is successfully employed in the Constellation Program and related Projects, such as in the areas of habitation and early requirements and design concepts.

Baggerman, Susan↗
NASA NTRS2010

Alvin (Al) Sieff: Thoughts About and Lessons from a Great Engineer

Alvin (Al) Seiff was known as a world-class atmospheric scientist during the last three decades of his life. Equally deserving, however, were his prior achievements as an innovative engineer, an exceptional technical manager, and a mentor of young engineers at NASA Ames Research Center. This paper outlines Al's role in developing Ames ballistic range facilities, probably the most advanced in the world at that time, and his seminal 1963 report that contained the concepts used to reconstruct the atmospheres of Mars, Venus, Jupiter and Titan. Also discussed is my affiliation with Al after he hired me in 1962, including our joint work on Mars missions and investigating the feasibility that a Jupiter probe could survive entry, work that eventually led to the development of the Galileo probe. Finally, suggestions are offered for speeding the analysis and design of thermal protection systems based on lessons learned from successful probes and landers.

Tauber, Michael↗
NASA NTRS2011

NASA System Engineering Design Process

This slide presentation reviews NASA's use of systems engineering for the complete life cycle of a project. Systems engineering is a methodical, disciplined approach for the design, realization, technical management, operations, and retirement of a system. Each phase of a NASA project is terminated with a Key decision point (KDP), which is supported by major reviews.

Roman, Jose↗
NASA NTRS2011

Bootstrapping Process Improvement Metrics: CMMI Level 4 Process Improvement Metrics in a Level 3 World

The measurement techniques for organizations which have achieved the Software Engineering Institutes CMMI Maturity Levels 4 and 5 are well documented. On the other hand, how to effectively measure when an organization is Maturity Level 3 is less well understood, especially when there is no consistency in tool use and there is extensive tailoring of the organizational software processes. Most organizations fail in their attempts to generate, collect, and analyze standard process improvement metrics under these conditions. But at JPL, NASA's prime center for deep space robotic exploration, we have a long history of proving there is always a solution: It just may not be what you expected. In this paper we describe the wide variety of qualitative and quantitative techniques we have been implementing over the last few years, including the various approaches used to communicate the results to both software technical managers and senior managers.

Hihn, Jairus↗
NASA NTRS2015

EOS Aura Mission Status

This PowerPoint presentation will discuss EOS Aura mission and spacecraft subsystem summary, recent and planned activities, inclination adjust maneuvers, propellant usage lifetime estimate. Eric Moyer, ESMO Deputy Project Manager-Technical (code 428) has reviewed and approved the slides on April 30, 2015.

propellant usage↗
NASA NTRS2016

International Earth Science Constellation Mission Operations Working Group September 27-29, 2016 Aqua Spring 2017 IAM Series

This Aqua Spring 2017 IAM Series powerpoint presentation will be presented at the MOWG meeting in Albuquerque, NM. Topics to be discussed are: recap Aqua 2016 IAM campaign maneuver results and post 2016 IAM MLT evolution; current DMU strategy; 2017 IAM campaign dates and planning; Aqua latest lifetime MLT team predictions. Susan Good is a contractor who supports David Tracewell in code 595 therefore this is being routed through 595. Eric Moyer, ESMO Deputy Project Manager-Technical has reviewed and approved this presentation.

Constellation↗
NASA NTRS2016

Challenges with Electrical, Electronics, and Electromechanical Parts for James Webb Space Telescope

James Webb Space Telescope (JWST) is the space-based observatory that will extend the knowledge gained by the Hubble Space Telescope (HST). Hubble focuses on optical and ultraviolet wavelengths while JWST focuses on the infrared portion of the electromagnetic spectrum, to see the earliest stars and galaxies that formed in the Universe and to look deep into nearby dust clouds to study the formation of stars and planets. JWST, which commenced creation in 1996, is scheduled to launch in 2018. It includes a suite of four instruments, the spacecraft bus, optical telescope element, Integrated Science Instrument Module (ISIM, the platform to hold the instruments), and a sunshield. The mass of JWST is approximately 6200 kg, including observatory, on-orbit consumables and launch vehicle adaptor. Many challenges were overcome while providing the electrical and electronic components for the Goddard Space Flight Center hardware builds. Other difficulties encountered included developing components to work at cryogenic temperatures, failures of electronic components during development and flight builds, Integration and Test electronic parts problems, and managing technical issues with international partners. This paper will present the context of JWST from a EEE (electrical, electronic, and electromechanical) perspective with examples of challenges and lessons learned throughout the design, development, and fabrication of JWST in cooperation with our associated partners including the Canadian Space Agency (CSA), the European Space Agency (ESA), Lockheed Martin and their respective associated partners. Technical challenges and lessons learned will be discussed.

EEE Parts↗
NASA NTRS2018

Mission Status for Earth Science Constellation MOWG Meeting @ Sioux Falls SD EOS Aura

This presentation provides mission operations status for the Earth Observing System (EOS) Aura satellite for the past six-months (December 2017 through May 2018). It only contains information that is of interest to the International Earth Science Constellation (ESC) Mission Operations Working Group (MOWG) member missions. It will be presented at the bi-annual MOWG Meeting at the USGS EROS Data Center in Sioux Falls, South Dakota on Wednesday, June 12, 2018. These meetings have been occurring twice a year since the MOWG was formed in 2003. The presentation has been reviewed and approved by Eric Moyer, ESMO Deputy Project Manager Technical.

Aura satellite↗
NASA NTRS2018

How Do You Go From a Concept Idea to a NASA Selected Mission? Formulating the Psyche Discovery Mission with JPL's Concurrent Engineering Teams

JPL’s Office of Formulation provides continuity of support and access to domain subject matter experts, as Principal Investigators mature their mission concepts from “cocktail napkin” ideas to Preliminary Design Reviews [1]. Using NASA’s Psyche mission as a case study, we describe JPL’s concurrent engineering A-Team and Team X support to the Psyche competed concept study team in the areas of 1) Initial Feasibility, 2) Trade Space Exploration, 3) Spacecraft Point Design and Cost Estimate, 4) Science, Technical, Management, and Cost Review, and 5) Strategy and Communication Development. NASA’s Psyche Discovery-class mission started as a grassroots idea from Principal Investigator L.T. ElkinsTanton. Is there a compelling Discovery mission to visit the interior of a body for the first time, by sending a mission to an iron metal asteroid? In less than five years the Psyche concept was selected as a mission under NASA’s Discovery Program. While Psyche had a dedicated concept development team [2], they utilized JPL’s concurrent engineering teams, methods, analysis tools, and subject matter experts throughout their mission concept formulation lifecycle

Ziemer, John↗
NASA NTRS2018

How Do You Go From a Concept Idea to a NASA Selected Mission? Formulating the Psyche Discovery Mission with JPL's Concurrent Engineering Teams

JPL’s Office of Formulation provides continuity of support and access to domain subject matter experts, as Principal Investigators mature their mission concepts from “cocktail napkin” ideas to Preliminary Design Reviews [1]. Using NASA’s Psyche mission as a case study, we will describe JPL’s concurrent engineering ATeam and Team X support to the Psyche competed concept study team in the areas of 1) Science Feasibility, 2) Trade Space Exploration, 3) Spacecraft Point Design and Cost Estimate, 4) Science, Technical, Management, and Cost Review, and 5) Strategy and Communication Development. NASA’s Psyche Discovery class mission started as a grassroots idea in our A-Team facility, and in less than five years was selected as a mission under NASA’s Discovery Program. While Psyche had a dedicated concept development team [2], they utilized JPL’s concurrent engineering teams, methods, analysis tools, and experts throughout their mission concept lifecycle.

Ziemer, John↗
NASA NTRSDate not supplied

My Life as a NASA Test Subject

In addition to Joe McMann’s duties as project engineer and technical manager, he was a test subject for spacesuits, life support systems, and other systems under his purview for over 18 years. During this Spacesuit Knowledge Capture event, he shared his experiences as a test subject during the Gemini, Apollo, and Space Shuttle Programs, which include both comical and serious lessons learned.

Joe McMann↗
NASA NTRSDate not supplied

Systems Engineering Tutorial with Case Studies

Due to the ever-growing number of complex technical problems facing our world, a Systems Engineering approach is needed to assist in successful design, build and implementation of solutions. The interdisciplinary technical structure of current systems, technical processes representing System Design, Technical Management and Product Realization are instrumental in the development and integration of new technologies into mainstream applications. This tutorial will demonstrate the application of Systems Engineering tools to these types of problems. Learning objectives include, understanding how to develop and engineer a conceptual system; understand the importance of teams, communication, requirements definition, interface control, and focus on deliverables; useful tools and techniques for each aspect of the System Engineering process including Model Based Systems Engineering which will be touched upon lightly. Some hands-on problems will be pursued especially in requirements development which is always key to a successful project. Case studies will be presented to assist in the learning process.

Systems Engineering↗