Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lessons learned process”

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

Demonstrating and Evaluating an Action Learning Approach to Building Project Management Competence

This paper contributes a description of an action-learning approach to building project management competence. This approach was designed, implemented, and evaluated for use with the Dynacs Engineering Development Contract at the Kennedy Space Center. The aim of the approach was to improve three levels of competence within the organization: individual project management skills, project team performance. and organizational capabilities such as the project management process and tools. The overall steps to the approach, evaluation results, and lessons learned are presented. Managers can use this paper to design a specific action-learning approach for their organization.

Kotnour, Tim↗
NASA NTRS2012

An Altair Overview: Designing a Lunar Lander for 21st Century Human Space Exploration

Altair, the lunar lander element of NASA's Constellation program, was conducted in a different design environment than many other NASA projects of similar scope. Because of this relatively unique approach, there are a number of significant success stories that should be considered during the development of any future lunar landers or human spacecraft. This paper is divided into two separate themes; the first is the approach used during the conceptual design studies, including the systematic analysis cycles and the decision making process associated with each: and the second is a summary of the resulting lessons learned that were compiled after looking back at the lifetime of the Project. Altair was terminated before entering Phase B of its design, and was often criticized for being a very heavy and very large vehicle. While there was specific rationale for all of the decisions that led up to that configuration, future design cycles were specifically planned to re-address the mass challenge. Had the project continued, the deliberate, stepwise design process would have converged on an optimized lander design that balanced mass, risk, cost and capabilities. Some of the specific items that will be addressed in this paper include project development strategy, organizational approach and team dynamics, risk-informed design process, mission architecture constraints, mission key driving requirements, model-based systems engineering process, configuration studies, contingency considerations, subsystem overviews and key trade studies. The paper will conclude with a summary of the lessons identified during the Altair project and make suggestions for application to future studies.

Brown, Kendall K.↗
DOE OSTI2024

Small Modular Reactor and Microreactor Security-by-Design Lessons Learned: Integrated PPS Designs

U.S. nuclear power facilities face increasing challenges in meeting dynamic security requirements caused by evolving and expanding threats while keeping costs reasonable to make nuclear energy competitive. The past approach has often included implementing security features after a facility has been designed and without attention to optimization, which can lead to cost overruns. Incorporating security into the design process can provide robust, cost-effective, and sufficient physical protection systems. The purpose of this report is to capture lessons learned by the Advanced Reactor Safeguards and Security (ARSS) program that may be beneficial for other advanced and small modular reactor (SMR) vendors to use when developing security systems and postures. This report will capture relevant information that can be used in the security-by-design (SeBD) process for SMR and microreactor vendors.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRSDate not supplied

The Lunar Lab Initiative

Analogous to terrestrial Antarctic basecamps at our south pole, space exploration outposts will be a combination of habitation and science-focused assets. The Artemis Exploration Roadmap endeavors to establish a sustained human presence on the lunar south pole starting in 2028. Within the planned Artemis Base Camp, most efforts to date have focused on the habitation assets or a mixture of science and habitation assets . With the recent advent of commercial lunar landing capabilities, the trade space can be further expanded to include dedicated science focused assets that ensure adequate science capability. To that end, the Forge, an innovation team initiative created at the Johnson Space Center (JSC), explored alternative ways to increase the science capabilities within the basecamp. The Forge uses structured brainstorming and facilitation to increase innovation within the assigned team, while executing its process in a rapid turnaround fashion for ideation and design study. As a pilot study for the Forge, a multi-disciplinary team investigated a lunar lab module to augment the lunar surface plans for Artemis. This formulation study evaluated the scientific and operational considerations for this dedicated crew space that would increase the capabilities of lunar surface science operations. The trade space evaluated single lunar lander delivery versus multiple lunar lander delivery for module assembly, alternative structural designs, the science instrument outfitting with mapping to scientific goals to maximize lunar science objectives, and how the lab would be operated. The lab operations options explored a stand-alone facility, as well as a facility integrated into a larger lunar surface complex, while evaluating crew usage and habitability considerations. The resulting alternatives were evaluated by the Forge team with a set of metrics to determine their originality, feasibility, and science performance, and thereby provide a recommendation to the lunar architecture planning team. Lessons learned from the lunar lab study were compiled to improve the process and tools for future Forge studies. Forward work, open issues, and challenges to further refine the design of the various science-focused asset options were also documented. By providing a robust science capability at humanity’s furthest outpost, we can plan for a sustained human lunar presence once the initial lunar surface access capability is well established.

Lunar outpost↗
DOE OSTI2020

SRS Strategy for Tank 3 Salt Dissolution - Performance and Lessons Learned - 20441

The Savannah River Site (SRS) Tank Farms have 51 underground waste tanks used to store and process liquid nuclear waste materials. There are 4 different tank types, ranging in capacity from 2,840,000 to 4,920,000 L (750,000 to 1,300,000 Gal). Twenty-four of the tanks are older style and do not meet full secondary containment standards. The older style tanks are the initial focus of waste removal efforts for tank closure at SRS. Eight of these twenty-four tanks have completed waste removal and are filled with grout. Prior to salt dissolution, Tank 3 was a dry salt tank that contained 5.06 m (199.3 in) of salt and sludge waste. Additional salt waste was present on cooling coils above the salt layer up to approximately 5.59 m (220 in). Three mixing eductors were installed in Tank 3 to aid in dissolving salt waste in three tank riser access ports. A transfer pump was installed, and the transfer pump suction was located 25.4 cm (10 in) from the tank bottom. Well water was added to the tank through a downcomer until the dry bulk salt was covered with liquid. During the initial fill of Tank 3, approximately 242,000 L (64,000 Gal) of rain water were added from periodic F-Tank Farm (FTF) Catch Tank additions and approximately 17,000 L (4,500 Gal) of well water were added. Following liquid additions to cover the dry bulk salt, well water was added through the three mixing eductors in batches during each stage. Additionally, during the salt dissolution campaigns, the FTF Catch Tank was utilized to add rain water through a downcomer in the center tank riser access port as needed for volume relief in the FTF Catch Tank. Following liquid additions, the water was recirculated (internal to the tank) using the transfer pump, and a sample was pulled to confirm the target specific gravity (SpG) of the dissolved salt solution was achieved. The dissolved salt solution was then transferred to the receipt tank (Tank 7), and the mixing eductors were lowered as close to the new bulk salt layer as possible, to support subsequent dissolution campaigns. While the mixing jets were able to dissolve salt successfully in Tank 3, they did not do so in a completely uniform manner. Throughout dissolution, mounds were discovered under Riser 1, Riser 2, and the Center Riser. The mixing jets dissolved the salt around the edges of the tank well but were not as effective toward the center of the tank. FTF Catch Tank additions through the center tank riser access port downcomer were required to impact the mound under the center tank riser. FTF Catch Tank additions were sporadic as they were dependent on rainfall in the area. Additionally, all mixing jets were rarely able to be lowered to the same elevation, indicating some mounding in the bulk salt layer. Indexing of the mixing jets was also utilized to impact the salt mounds. Overall, Tank 3 salt dissolution was successful as approximately 1,476,000 L (390,000 Gal) of dissolved salt solution was transferred to Tank 7 over six stages. Slightly less than 852,000 L (225,000 Gal) of water were added to Tank 3. The original material balance prediction estimated that the bulk salt level in Tank 3 would be 3.88 m (152.8 in) after six salt dissolution stages. After six stages the actual bulk salt level was 3.38 m (133 in). This paper will discuss the salt removal strategy, each salt dissolution stage, and lessons learned for future salt dissolution. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS2011

Ground Processing Affordability for Space Vehicles

Launch vehicles and most of their payloads spend the majority of their time on the ground. The cost of ground operations is very high. So, why so often is so little attention given to ground processing during development? The current global space industry and economic environment are driving more need for efficiencies to save time and money. Affordability and sustainability are more important now than ever. We can not continue to treat space vehicles as mere science projects. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability which are not available for ELV's (Expendable Launch Vehicles). More human-rated vehicles are being developed, with the retirement of the Space Shuttles, and for a new global space race, yet these cost more than the many unmanned vehicles of today. We can learn many lessons on affordability from RLV's. DFO (Design for Operations) considers ground operations during design, development, and manufacturing-before the first flight. This is often minimized for space vehicles, but is very important. Vehicles are designed for launch and mission operations. You will not be able to do it again if it is too slow or costly to get there. Many times, technology changes faster than space products such that what is launched includes outdated features, thus reducing competitiveness. Ground operations must be considered for the full product Lifecycle, from concept to retirement. Once manufactured, launch vehicles along with their payloads and launch systems require a long path of processing before launch. Initial assembly and testing always discover problems to address. A solid integration program is essential to minimize these impacts, as was seen in the Constellation Ares I-X test rocket. For RLV's, landing/recovery and post-flight turnaround activities are performed. Multi-use vehicles require reconfiguration. MRO (Maintenance, Repair, and Overhaul) must be well-planned--- even for the unplanned problems. Defect limits and standard repairs need to be in-place as well as easily added. Many routine inspections and maintenance can be like an aircraft overhaul. Modifications and technology upgrades should be expected. Another factor affecting ground operations efficiency is trending. It is essential for RLV's, and also useful for ELV's which fly the same or similar models again. Good data analysis of technical and processing performance will determine fixes and improvements needed for safety, design, and future processing. Collecting such data on new or low-frequency vehicles is a challenge. Lessons can be learned from the Space Shuttle, or even the Concorde aircraft. For all of the above topics, efficient business systems must be established for comprehensive program management and good throughput. Drawings, specifications, and manuals for an entire launch vehicle are often in different formats from multiple vendors, plus they have proprietary constraints. Nonetheless, the integration team must ensure that all data needed is compatible and visible to each appropriate team member. Ground processing systems for scheduling, tracking, problem resolution, etc. must be well laid-out. The balance between COTS (commercial off the shelf) and custom software is difficult. Multiple customers, vendors, launch sites, and landing sites add to the complexity of efficient IT (Information Technology) tools.

Ingalls, John↗
NASA NTRS2012

Performance of a Water Recirculation Loop Maintenance Device and Process for the Advanced Spacesuit Water Membrane Evaporator

A water loop maintenance device and process to maintain the water quality of the Advanced Spacesuit Water Membrane Evaporation (SWME) water recirculation loop has been undergoing a performance evaluation. The SWME is a heat rejection device under development at the NASA Johnson Space Center to perform thermal control for advanced spacesuits. One advantage to this technology is the potential for a significantly greater degree of tolerance to contamination when compared to the existing Sublimator technology. The driver for the water recirculation maintenance device and process is to further enhance this advantage through the leveraging of fluid loop management lessons-learned from the International Space Station (ISS). A bed design that was developed for a Hamilton Sundstrand military application, and considered for a potential ISS application with the Urine Processor Assembly, provides a low pressure drop means for water maintenance in a recirculation loop. The bed design is coupled with high capacity ion exchange resins, organic adsorbents, and a cyclic methodology developed for the Extravehicular Mobility Unit (EMU) Transport Water loop. The maintenance process further leverages a sorbent developed for ISS that introduces a biocide in a microgravity-compatible manner for the Internal Active Thermal Control System (IATCS). The leveraging of these water maintenance technologies to the SWME recirculation loop is a unique demonstration of applying the valuable lessons learned on the ISS to the next generation of manned spaceflight Environmental Control and Life Support System (ECLSS) hardware. This

Rector, Tony↗
NASA NTRS1990

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↗
NASA NTRS2018

Flight Systems Integration & Test: Lessons Learned for Future Success

This paper offers a comprehensive view of flight system integration and test (I&T) lessons learned related to mishaps and close calls, focusing on what can be done to improve the I&T process to avoid recurrence. Specific areas within the realm of I&T that are covered in this paper include: I&T team communication and training; design of flight and ground systems for I&T; planning and scheduling; configuration management and process documentation; ground support equipment and tools; cleanrooms and contamination; mechanical integration, handling, and deployments; electrical integration and electrostatic discharge; functional testing and troubleshooting; environmental testing and facilities; and launch site operations. To illustrate "real-world" lessons learned for I&T, examples from throughout the history of the U.S. space program are presented. Also presented are some best practices for I&T that can help mitigate mishaps and close calls on the ground or during flight.

Integration & Test↗
DOE OSTI2020

Lessons Learned in the Development of Industry Guidance - 20279

The availability of industry guidance on different aspects of waste management forms a valuable reference for waste practitioners. The guidance typically details the principles, processes and practices that should be consulted during each stage of the relevant activities. It also includes relevant regulatory and international requirements, appropriate case studies and examples of best practices to illustrate technical concepts and make the information available to the reader in an accessible manner. Over recent years Wood have developed (or are developing) a number of industry guidance documents on a range of topics including Solid Waste Characterization, Routine Water Quality Monitoring on Nuclear Sites: Pipeline Characterization: Determining Background Radioactivity for Land Quality Assessment: Interim Storage and Aqueous Waste Management. This talk provides an overview of lessons learned along the way including: - the importance of stakeholder engagement through the process: - how to identify 'good practice'; - the importance of iterative development; and - the selection of illustrative and informative case studies. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS1990

Interpreting the handling qualities of aircraft with stability and control augmentation

The general process of designing an aircraft for good flying qualities is first discussed. Lessons learned are pointed out, with piloted evaluation emerging as a crucial element. Two sources of rating variability in performing these evaluations are then discussed. First, the finite endpoints of the Cooper-Harper scale do not bias parametric statistical analyses unduly. Second, the wording of the scale does introduce some scatter. Phase lags generated by augmentation systems, as represented by equivalent time delays, often cause poor flying qualities. An analysis is introduced which allows a designer to relate any level of time delay to a probability of loss of aircraft control. This view of time delays should, it is hoped, allow better visibility of the time delays in the design process.

Hodgkinson, J.↗
NASA NTRS2008

Computational Fluid Dynamics Analysis Success Stories of X-Plane Design to Flight Test

Examples of the design and flight test of three true X-planes are described, particularly X-plane design techniques that relied heavily on computational fluid dynamics(CFD) analysis. Three examples are presented: the X-36 Tailless Fighter Agility Research Aircraft, the X-45A Unmanned Combat Air Vehicle, and the X-48B Blended Wing Body Demonstrator Aircraft. An overview is presented of the uses of CFD analysis, comparison and contrast with wind tunnel testing, and information derived from CFD analysis that directly related to successful flight test. Lessons learned on the proper and improper application of CFD analysis are presented. Highlights of the flight-test results of the three example X-planes are presented. This report discusses developing an aircraft shape from early concept and three-dimensional modeling through CFD analysis, wind tunnel testing, further refined CFD analysis, and, finally, flight. An overview of the areas in which CFD analysis does and does not perform well during this process is presented. How wind tunnel testing complements, calibrates, and verifies CFD analysis is discussed. Lessons learned revealing circumstances under which CFD analysis results can be misleading are given. Strengths and weaknesses of the various flow solvers, including panel methods, Euler, and Navier-Stokes techniques, are discussed.

Cosentino, Gary B.↗
NASA NTRS1987

Launch Processing System operations with a future look to Operations Analyst (OPERA)

The Launch Processing System architecture and the ground support operations required to provide Shuttle System engineers with the capability to safely process and launch an Orbiter are described. The described ground operations are the culmination of eleven years of experience and redesign. Some of the 'lessons learned' are examined, and problem areas which ground support operations have identified over the years as the Shuttle and Launch Processing Systems continue to grow in complexity are discussed. The Operational Analyst for Distributed Systems (OPERA), a proposed set of expert systems for the Launch Processing System Operational assistance, is discussed along with its extensions to prospective future configurations and components for the Launch Processing System.

Heard, Astrid E.↗
NASA NTRSDate not supplied

Porting OVERFLOW CFD Code to GPUs: To Hackathons and Beyond!

OVERFLOW is an overset, structured computational fluid dynamics (CFD) code written in Fortran which is widely used in the government, industry, and academia. Over the last several years the OVERFLOW developers have been working to port miniapps based on computationally expensive parts of OVERFLOW to run on GPUs, primarily using OpenACC. This effort started at our first hackathon in 2019 and since then the OVERFLOW team has attended two additional hackathons (virtually). These hackathon environments have provided a great place to collaborate with others and learn from experts. These learning experiences enabled porting two miniapps to run effectively on NVIDIA GPUs using OpenACC. The first miniapp focused on motifs found in the solver itself and the final ported version runs three times fast ona single V100 compared to a 40 core, dual-socket Intel Skylake node. The speed up in this solverminiapp required multiple design changes including increasing the amount of parallelism available and the amount of work performed in each kernel. The second miniapp focused on overset MPI communication, also saw significant speedups over the CPU implementation using a CUDA-aware MPI implementation through OpenACC. This presentation will discuss our experience at the hackathons, our process of porting the miniapps to run on the GPUs, and several lessons learned throughout.

OpenACC↗
NASA NTRS1988

An environment for the integration and test of the Space Station distributed avionics systems

An approach to supplying an environment for the integration and test of the Space Station distributed avionics systems is described. Background is included on the development of this concept including the lessons learned from Space Shuttle experience. The environment's relationship to the process flow of the Space-Station verification, from systems development to on-orbit verification, is presented. The uses of the environment's hardware implementation, called Data Management System (DMS) kits, are covered. It is explained how these DMS kits provide a development version of the space-station operational environment and how this environment allows system developers to verify their systems performance, fault detection, and recovery capability. Conclusions on how the use of the DMS kits, in support of this concept, will ensure adequate on-orbit test capability are included.

Barry, Thomas↗
NASA NTRS2001

Selection of the Ground Segment for the Next Generation Space Telescope (NGST) Flight Demonstrator (Nexus)

Nexus was a technology demonstrator project that was designed to bridge from the Hubble Space Telescope (HST) to its successor, the Next Generation Space Telescope (NGST). This paper focuses on the process used in designing the ground segment for Nexus and the lessons learned in its development. Ground station cost drivers were: (1) Contact time, (2) Cost of transporting data between the ground stations and control center, and (3) Cost savings via ground automation. We found that reducing the communication requirement in just the first 100 days could have reduced the total ground station cost by 40%. Contact time cost dwarfed the cost trade between automation development and off-shift operations personnel. Real-time Telemetry and Control (T&C) system analysis was divided into: (1) Potential reuse of the Nexus real-time (T&C) system for NGST, (2) Feasibility of using a 'Finite State-Based Modeling' product, and (3) Selecting a Commercial Off the Shelf (COTS) versus Government Off The Shelf (GOTS) products. We found that each of the products evaluated in detail (ASIST, EPOCH 2000, and ITOS) could adequately support basic mission requirements. Lessons learned were: (1) Include operations at the beginning of the mission, and (2) Develop an operations concept as soon as possible.

Gal-Edd, Jonathan↗
NASA NTRS2002

The Role of Formal Experiment Design in Hypersonic Flight System Technology Development

Hypersonic airbreathing engine (scramjet) powered vehicles are being considered to replace conventional rocket-powered launch systems. Effective utilization of scramjet engines requires careful integration with the air vehicle. This integration synergistically combines aerodynamic forces with propulsive cycle functions of the engine. Due to the highly integrated nature of the hypersonic vehicle design problem, the large flight envelope, and the large number of design variables, the use of a statistical design approach in design is effective. Modern Design-of-Experiments (MDOE) has been used throughout the Hyper-X program, for both systems analysis and experimental testing. Application of MDOE fall into four categories: (1) experimental testing; (2) studies of unit phenomena; (3) refining engine design; and (4) full vehicle system optimization. The MDOE process also provides analytical models, which are also used to document lessons learned, supplement low-level design tools, and accelerate future studies. This paper will discuss the design considerations for scramjet-powered vehicles, specifics of MDOE utilized for Hyper-X, and present highlights from the use of these MDOE methods within the Hyper-X Program.

McClinton, Charles R.↗