Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Lessons learned”

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 73 records · Page 4

Fabrication Lessons Learned of Transportation Packaging from the Perspective of a Design Authority - 20322

This paper presents lessons learned regarding fabricating packaging systems from the perspective of a design authority (DA). Capturing and implementing lessons learned is critical for an organization to reduce systematic project risk and thereby promote the likelihood of project success. This paper defines the design authority as the organization responsible for technical design, resolving technical design issues, quality assurance program, and maintenance of the packaging system license. A package system is defined as the packaging, its contents, and auxiliary equipment. Packages are certified by the NRC under 10 CFR 71[1] for transportation by ground. The following lessons learned subjects are presented in the paper: quality assurance, interpretation of drawing dimensional requirements, execution of manufacturing processes, hardware dimensional inspection, and leakage rate testing. All discrepancies presented in this paper have been resolved as described in the appropriate final data package. All described package systems are in compliance with their Safety Analysis Report (SAR) and certificate of conformance requirements. The intent of this paper is to identify opportunities for improving the outcome of future projects and to mitigate fabrication challenges proactively. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Lessons learned on the Skylab program

Lessons learned in the Skylab program and their application and adaptation to other space programs are summarized. Recommendations and action taken on particular problems are described. The use of Skylab recommendations to identify potential problems of future space programs is discussed.

Source record↗

G-399 and G178: Lessons learned

This paper outlines the lessons learned implementing Get Away Specials (GAS) payloads G-399 and G-178 with regard to power systems, computer/data logger, structure and working with undergraduates.

Dobeck, Michael↗

Customizing the JPL Multimission Ground Data System: Lessons Learned

This paper will describe lessons learned in adapting JPL's Multimission Ground Data System (MGDS) to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team with a handful of engineers flying the Galileo Spacecraft flight system model.

ground↗

Lessons Learned from Ares I Upper Stage Structures and Thermal Design

The Ares 1 Upper Stage was part of the vehicle intended to succeed the Space Shuttle as the United States manned spaceflight vehicle. Although the Upper Stage project was cancelled, there were many lessons learned that are applicable to future vehicle design. Lessons learned that are briefly detailed in this Technical Memorandum are for specific technical areas such as tank design, common bulkhead design, thrust oscillation, control of flight and slosh loads, purge and hazardous gas system. In addition, lessons learned from a systems engineering and vehicle integration perspective are also included, such as computer aided design and engineering, scheduling, and data management. The need for detailed systems engineering in the early stages of a project is emphasized throughout this report. The intent is that future projects will be able to apply these lessons learned to keep costs down, schedules brief, and deliver products that perform to the expectations of their customers.

Ahmed, Rafiq↗

Selected Lessons Learned in Space Shuttle Orbiter Propulsion and Power Subsystems

Over its 30 years of space flight history, plus the nearly 10 years of design, development test and evaluation, the Space Shuttle Orbiter is full of lessons learned in all of its numerous and complex subsystems. In the current paper, only selected lessons learned in the areas of the Orbiter propulsion and power subsystems will be described. The particular Orbiter subsystems include: Auxiliary Power Unit (APU), Hydraulics and Water Spray Boiler (WSB), Mechanical Flight Controls, Main Propulsion System (MPS), Fuel Cells and Power Reactant and Storage Devices (PRSD), Orbital Maneuvering System (OMS), Reaction Control System (RCS), Electrical Power Distribution (EPDC), electrical wiring and pyrotechnics. Given the complexity and extensive history of each of these subsystems, and the limited scope of this paper, it is impossible to include most of the lessons learned; instead the attempt will be to present a selected few or key lessons, in the judgment of the authors. Each subsystem is presented separate, beginning with an overview of the hardware and their function, a short description of a few historical problems and their lessons, followed by a more comprehensive table listing of the major subsystem problems and lessons. These tables serve as a quick reference for lessons learned in each subsystem. In addition, this paper will establish common lessons across subsystems as well as concentrate on those lessons which are deemed to have the highest applicability to future space flight programs.

Hernandez, Francisco J.↗

NASA Crew and Cargo Launch Vehicle Development Approach Builds on Lessons Learned from Past and Present Missions

A viewgraph presentation of NASA crew and cargo launch vehicle development building upon lessons learned from past and present missions is shown. The topics include: 1) U.S. Vision for Space Exploration; 2) NASA's Exploration Road Map; 3) The Moon-The First Step to Mars and Beyond; 4) Building on a Foundation of Proven Technologies; 5) Constellation Launch Vehicle Elements; 6) 1.5 Launch Earth Orbit/Lunar Orbit Rendezvous; 7) The Journey Continues; 8) Design Philosophy for Mission Success; 9) Lessons Learned: Implementation Tenets; and 10) Lessons Learned: Early Integration with the Operators.

Dumbacher, Dan↗

NASA Lessons Learned from Space Lubricated Mechanisms

This document reviews the lessons learned from short-life and long life lubricated space mechanisms. A short-life lubricated mechanisms complete their life test qualification requirements after a few cycles. The mechanisms include the hinges, motors and bearings for deployment, release mechanisms, latches, release springs and support shops. Performance testing can be difficult and expensive but must be accomplished. A long-life lubricated mechanisms requires up to 5 years of life testing, or 10 to 100 years of successful flight. The long-life mechanisms include reaction wheels, momentum wheels, antenna gimbals, solar array drives, gyros and despin mechanisms. Several instances of how a mechanisms failed either in test, or in space use, and the lessons learned from these failures are reviewed. The effect of the movement away from CFC-113 cleaning solvent to ODC (Ozone-Depleting Chemical) -free is reviewed, and some of the alternatives are discussed.

Predmore, Roamer E.↗

Lessons Learned in Designing A Proposed Ultraviolet Sterilization System for Space

This paper presents a number of lessons learned while designing a proposed sterilization system for Mars Sample Return. This sterilization system is needed to inactivate any potentially hazardous Mars material on the exterior surface of the vessel containing sealed sample tubes filled with Mars rock cores, regolith and atmosphere. These returned samples would provide information on the geologic history of Mars, the evolution of its climate and the potential for ancient life. Mars Sample Return is categorized at Planetary Protection Category V Restricted Earth Return, so it is required to protect the Earth–Moon system from the biological impact of returning samples from Mars to Earth. This article reviews lessons learned in the development of a particular engineering implementation to support the protection of the Earth–Moon biosphere: the use of in situ ultraviolet LED illumination. The details of the biological efficacy of this approach or the policy-related impacts are outside of the scope of this manuscript. The lessons learned presented here include establishing design requirements for the system, the selection of a light source, optical design options, contamination control and approaches to thermal and power management.

Planetary Protection↗

Lessons Learned in Hydrogen System Operation

NASA has learned extensive lessons on the operations of hydrogen systems during the developments and operations of space hardware. A subset of these lessons that are useful for aircraft and terrestrial applications using liquid hydrogen are presented to help disseminate the information learned. Discussion includes test data, analysis, and observations on cryogenic insulation systems, stratification and temperature gradients within tank systems, fittings to reduce leakage, and integration of refrigeration systems within a cryogenic fluids system.

Liquid Hydrogen↗

Lessons Learned and Flight Results from the F15 Intelligent Flight Control System Project

A viewgraph presentation on the lessons learned and flight results from the F15 Intelligent Flight Control System (IFCS) project is shown. The topics include: 1) F-15 IFCS Project Goals; 2) Motivation; 3) IFCS Approach; 4) NASA F-15 #837 Aircraft Description; 5) Flight Envelope; 6) Limited Authority System; 7) NN Floating Limiter; 8) Flight Experiment; 9) Adaptation Goals; 10) Handling Qualities Performance Metric; 11) Project Phases; 12) Indirect Adaptive Control Architecture; 13) Indirect Adaptive Experience and Lessons Learned; 14) Gen II Direct Adaptive Control Architecture; 15) Current Status; 16) Effect of Canard Multiplier; 17) Simulated Canard Failure Stab Open Loop; 18) Canard Multiplier Effect Closed Loop Freq. Resp.; 19) Simulated Canard Failure Stab Open Loop with Adaptation; 20) Canard Multiplier Effect Closed Loop with Adaptation; 21) Gen 2 NN Wts from Simulation; 22) Direct Adaptive Experience and Lessons Learned; and 23) Conclusions

Bosworth, John↗

Development of X-33/X-34 Aerothermodynamic Data Bases: Lessons Learned and Future Enhancements

A synoptic of programmatic and technical lessons learned in the development of aerothermodynamic data bases for the X-33 and X-34 programs is presented in general terms and from the perspective of the NASA Langley Research Center Aerothermodynamics Branch. The format used is that of the aerothermodynamic chain, the links of which are personnel, facilities, models/test articles, instrumentation, test techniques, and computational fluid dynamics (CFD). Because the aerodynamic data bases upon which the X-33 and X-34 vehicles will fly are almost exclusively from wind tunnel testing, as opposed to CFD, the primary focus of the lessons learned is on ground-based testing.

Miller, C. G.↗

Modernization of Technical Requirements for Licensing of Advanced Non-Light Water Reactors: LMP Lessons Learned, Best Practices, and Frequently Asked Questions

This report captures lessons learned, best practices, and frequently asked questions with responses gleaned from the experiences of early adopters of the LMP RIPB process. Interviews were conducted in late 2019 with five non-LWR design organizations to gather their feedback on the application of the LMP RIPB process under real production conditions. The overall feedback from the reactor developers is that the LMP RIPB process can be successfully implemented with material benefits to the designer. As with any new processes, numerous challenges and questions were relayed by the designers. These challenges have been translated into lessons learned and best practices. Those two sections address both technical and organizational aspects of implementing the LMP RIPB process. Questions that were asked by multiple designers were turned into “frequently asked questions” and responses were provided by the LMP team.

42 ENGINEERING↗

Lessons Learned from Applying Design Thinking in a NASA Rapid Design Study in Aeronautics

In late 2015, NASA's Aeronautics Research Mission Directorate (ARMD) funded an experiment in rapid design and rapid teaming to explore new approaches to solving challenging design problems in aeronautics in an effort to cultivate and foster innovation. This report summarizes several lessons learned from the rapid design portion of the study. This effort entailed learning and applying design thinking, a human-centered design approach, to complete the conceptual design for an open-ended design challenge within six months. The design challenge focused on creating a capability to advance experimental testing of autonomous aeronautics systems, an area of great interest to NASA, the US government as a whole, and an entire ecosystem of users and developers around the globe. A team of nine civil servant researchers from three of NASA's aeronautics field centers with backgrounds in several disciplines was assembled and rapidly trained in design thinking under the guidance of the innovation and design firm IDEO. The design thinking process, while used extensively outside the aerospace industry, is less common and even counter to many practices within the aerospace industry. In this report, several contrasts between common aerospace research and development practices and design thinking are discussed, drawing upon the lessons learned from the NASA rapid design study. The lessons discussed included working towards a design solution without a set of detailed design requirements, which may not be practical or even feasible for management to ascertain for complex, challenging problems. This approach allowed for the possibility of redesigning the original problem statement to better meet the needs of the users. Another lesson learned was to approach problems holistically from the perspective of the needs of individuals that may be affected by advances in topic area instead of purely from a technological feasibility viewpoint. The interdisciplinary nature of the design team also provided valuable experience by allowing team members from different technological backgrounds to work side-by-side instead of dividing into smaller teams, as is frequently done in traditional multidisciplinary design. The team also learned how to work with qualitative data obtained primarily through the 70-plus interviews that were conducted over the course of this project, which was a sharp contrast to using quantitative data with regards to identifying, capturing, analyzing, storing, and recalling the data. When identifying potential interviewees who may have useful contributions to the design subject area, the team found great value in talking to non-traditional users and potential beneficiaries of autonomous aeronautics systems whose impact on the aeronautics autonomy ecosystem is growing swiftly. Finally, the team benefitted from using "sacrificial prototyping," which is a method of rapidly prototyping draft concepts and ideas with the intent of enabling potential users to provide significant feedback early in the design process. This contrasts the more common approach of using expensive prototypes that focus on demonstrating technical feasibility. The unique design approach and lessons learned by the team throughout this process culminated in a final design concept that was quite different than what the team originally assumed would be the design concept initially. A summary of the more usercentered final design concept is also provided.

McGowan, Anna-Maria↗

Planning and scheduling lessons learned study, executive summary

The study was performed to document the lessons on planning and scheduling activities for a number of missions and institutional facilities in such a way that they can be applied to future missions; to provide recommendations to both projects and Code 500 that will improve the end-to-end planning and scheduling process; and to identify what, if any, mission characteristics might be related to certain lessons learned. The results are a series of recommendations of both a managerial and technical nature related to the underlying lessons learned.

Robinson, Toni↗

Cumulus Lessons Learned: Building, Testing, and Sharing a Cloud Archive

Cumulus is a scalable, extensible cloud-based archive system which is capable of ingesting, archiving, and distributing data from both existing on-prem sources and new cloud-native missions. As we have built and evolved the system with contributions from seven NASA EOSDIS organizations, we have learned several lessons about how to build a robust, broadly-applicable, microservices-based cloud system for geospatial data which we will share in this talk.

Quinn, Patrick↗

The role of failure/problems in engineering: A commentary of failures experienced - lessons learned

The written version of a series of seminars given to several aerospace companies and three NASA centers are presented. The results are lessons learned through a study of the problems experienced in 35 years of engineering. The basic conclusion is that the primary cause of problems has not been mission technologies, as important as technology is, but the neglect of basic principles. Undergirding this is the lack of a systems focus from determining requirements through design, verification, and operations phases. Many of the concepts discussed are fundamental to total quality management (TQM) and can be used to augment this product enhanced philosophy. Fourteen principles are addressed with problems experienced and are used as examples. Included is a discussion of the implication of constraints, poorly defined requirements, and schedules. Design guidelines, lessons learned, and future tasks are listed. Two additional sections are included that deal with personal lessons learned and thoughts on future thrusts (TQM).

Ryan, R. S.↗