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 1,297 records · Page 72

Lessons learned from the development and implementation of a workforce training curriculum for advanced controls for high performance HVAC systems

Over the past decade, academic research on advanced controls has slowly transitioned into new software platforms, giving rise to various companies developing and deploying these innovative products, including solutions for light commercial HVAC systems. However, the current workforce remains widely unprepared to install, maintain and operate these systems, particularly complex software-based control platforms, as most workforce training programs still focus on traditional building automation for large commercial buildings. This paper presents the development and piloting of curriculum for three key types of professionals: ● Technicians (trade-level): installing and maintaining modern high-performance HVAC systems and controls ● Programmers (undergrad-level): developing and implementing advanced controls ● Engineers and energy professionals (undergrad/grad-level): managing and evaluating system performance We share details of the material developed including training videos, open-source software, instruction manuals. We also present the results of a pilot implementation of the training materials with real students.

Casillas, Armando↗

Learning Hard Lessons from Columbia Decisions

This is a short presentation on lessons learned from the decision-making process around the Columbia Accident. It draws upon material in the CAIB report and uses two NASA public video clips.

Rogers, Ed↗

Panel Session 2: Hot Topics in US DOE Environmental Management

The well-attended Panel Session was chaired by Martin Schneider. The four panelists did not provide presentations. Rather the session was a discussion focusing on pressing issues facing US DOE Environmental Management (EM) sites and how the program is moving forward. The session began by momentarily reflecting on a success: the three Tank Waste Treatment Facilities will soon be coming online. These three facilities will treat as much waste in two years as was treated in the past 30 years. That is a significant milestone in progress. Also, safety enhancements at WIPP are a big success. The panelists noted that there will be challenges with the victories of the startup of the Waste Treatment Facilities. Treating tank waste is the last EM mission and will help with the relationships with the stakeholders, regulators and Congress. One of the biggest challenges will be moving back to full operation mode. Although the operation will increase productivity of reducing/managing the tank waste, it will decrease life cycle cost and lessen years of cleanup. The challenge will be having people understand that EM will be operating 24/7 and that maintenance will be key in keeping the operations. EM will be working together with the regulators to show tangible progress that will be effective and efficient. By working together, they can find opportunities/technologies for streamlining and accelerating cleanup. Recent changes to the regulatory framework between DOE-EM Los Alamos Field Office and New Mexico Environmental Department have helped cleanup in Los Alamos. Every year EM and the agencies review progress and come to agreements on the next work priorities. At Savannah River Site, the Federal Facility Agreement among EM, South Carolina Department of Health and Environmental Control, and Environmental Protection Agency (EPA) has developed a small core team that work are shared by together in resolving issues that come up. The discussion moved on to how progress can be made by sharing lessons learned among the contractors. An example of how these learned lessons can be shared is that key representatives from projects across the EM sites participate in various forums to review/contribute to the work planned. Other opportunities can be by temporary assignments of DOE staff to gain experience and by monthly EM Headquarters report that provide the lessons learned across the EM sites. The panelists discussed how skyline changes are the best examples of tangible progress. Decontamination and Demolition (D and D) of structures are the easiest tangible progress that can be seen. Whereas tank waste cleanup is the hardest to see. Disposal of waste onsite versus offsite is another challenge, and timely discussions are necessary to get to the best value to the government.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Lift-fan aircraft: Lessons learned-the pilot's perspective

This paper is written from an engineering test pilot's point of view. Its purpose is to present lift-fan 'lessons learned' from the perspective of first-hand experience accumulated during the period 1962 through 1988 while flight testing vertical/short take-off and landing (V/STOL) experimental aircraft and evaluating piloted engineering simulations of promising V/STOL concepts. Specifically, the scope of the discussions to follow is primarily based upon a critical review of the writer's personal accounts of 30 hours of XV-5A/B and 2 hours of X-14A flight testing as well as a limited simulator evaluation of the Grumman Design 755 lift-fan aircraft. Opinions of other test pilots who flew these aircraft and the aircraft simulator are also included and supplement the writer's comments. Furthermore, the lessons learned are presented from the perspective of the writer's flying experience: 10,000 hours in 100 fixed- and rotary-wing aircraft including 330 hours in 5 experimental V/STOL research aircraft. The paper is organized to present to the reader a clear picture of lift-fan lessons learned from three distinct points of view in order to facilitate application of the lesson principles to future designs. Lessons learned are first discussed with respect to case histories of specific flight and simulator investigations. These principles are then organized and restated with respect to four selected design criteria categories in Appendix I. Lastly, Appendix Il is a discussion of the design of a hypothetical supersonic short take-off vertical landing (STOVL) fighter/attack aircraft.

Gerdes, Ronald M.↗

The Applied Meteorology Unit: Nineteen Years Successfully Transitioning Research into Operations for America's Space Program

The Applied Meteorology Unit (AMU) provides technology transition and technique development to improve operational weather support to the Space Shuttle and the entire American space program. The AMU is funded and managed by NASA and operated by a contractor that provides five meteorologists with a diverse mix of advanced degrees, operational experience, and associated skills including data processing, statistics, and the development of graphical user interfaces. The AMU's primary customers are the U.S. Air Force 45th Weather Squadron at Patrick Air Force Base, the National Weather Service Spaceflight Meteorology Group at NASA Johnson Space Center, and the National Weather Service Melbourne FL Forecast Office. The AMU has transitioned research into operations for nineteen years and worked on a wide range of topics, including new forecasting techniques for lightning probability, synoptic peak winds,.convective winds, and summer severe weather; satellite tools to predict anvil cloud trajectories and evaluate camera line of sight for Space Shuttle launch; optimized radar scan strategies; evaluated and implemented local numerical models; evaluated weather sensors; and many more. The AMU has completed 113 projects with 5 more scheduled to be completed by the end of 2010. During this rich history, the AMU and its customers have learned many lessons on how to effectively transition research into operations. Some of these lessons learned include collocating with the operational customer and periodically visiting geographically separated customers, operator submitted projects, consensus tasking process, use of operator primary advocates for each project, customer AMU liaisons with experience in both operations and research, flexibility in adapting the project plan based on lessons learned during the project, and incorporating training and other transition assistance into the project plans. Operator involvement has been critical to the AMU's remarkable success and many awards from NASA, the National Weather Association, and two citations from the Navy's Center of Excellence for Best Manufacturing Practices. This paper will present the AMU's proven methods and explain how they may be applied by other organizations to effectively transition research into operations.

Madura, John T.↗

Lessons Learned-Analytical Laboratory Construction Modifications

The purpose of this document is to disseminate lessons learned from the Sandia National Laboratories (SNL) Building 1090 modification project and other analytical laboratory related construction projects. The following sections summarize lessons learned at various phases of the project.

99 GENERAL AND MISCELLANEOUS↗

Safety and Mission Assurance Knowledge Management Retention: Managing Knowledge for Successful Mission Operations

Knowledge Management is a proactive pursuit for the future success of any large organization faced with the imminent possibility that their senior managers/engineers with gained experiences and lessons learned plan to retire in the near term. Safety and Mission Assurance (S&MA) is proactively pursuing unique mechanism to ensure knowledge learned is retained and lessons learned captured and documented. Knowledge Capture Event/Activities/Management helps to provide a gateway between future retirees and our next generation of managers/engineers. S&MA hosted two Knowledge Capture Events during 2005 featuring three of its retiring fellows (Axel Larsen, Dave Whittle and Gary Johnson). The first Knowledge Capture Event February 24, 2005 focused on two Safety and Mission Assurance Safety Panels (Space Shuttle System Safety Review Panel (SSRP); Payload Safety Review Panel (PSRP) and the latter event December 15, 2005 featured lessons learned during Apollo, Skylab, and Space Shuttle which could be applicable in the newly created Crew Exploration Vehicle (CEV)/Constellation development program. Gemini, Apollo, Skylab and the Space Shuttle promised and delivered exciting human advances in space and benefits of space in people s everyday lives on earth. Johnson Space Center's Safety & Mission Assurance team work over the last 20 years has been mostly focused on operations we are now beginning the Exploration development program. S&MA will promote an atmosphere of knowledge sharing in its formal and informal cultures and work processes, and reward the open dissemination and sharing of information; we are asking "Why embrace relearning the "lessons learned" in the past?" On the Exploration program the focus will be on Design, Development, Test, & Evaluation (DDT&E); therefore, it is critical to understand the lessons from these past programs during the DDT&E phase.

Johnson, Teresa A.↗

Semantic Search with Sentence-BERT for Design Information Retrieval

Managing and referencing design knowledge is a critical activity in the design process. However, reliably retrieving useful knowledge can be a frustrating experience for users of knowledge management systems due to inherent limitations of standard keyword-based searches. In this research, we consider the task of retrieving relevant lessons learned from the NASA Lessons Learned Information System (LLIS). To this end, we apply a state-of-the-art natural language processing (NLP) technique for information retrieval: semantic search with sentence-BERT, which is a modification of a Bidirectional Encoder Representations from Transformers (BERT) model that uses siamese and triplet network architectures to obtain semantically meaningful sentence embeddings. While the pretrained sBERT model shows excellent out-of-the-box performance, we further fine-tune the model on data from the LLIS so that it learns on design engineering-relevant vocabulary. We quantify the improvement in query results using both standard sBERT and fine-tuned sBERT over the LLIS’s built-in keyword search. Additionally, we demonstrate a use case for the query system by searching for lessons learned relevant to specific requirements from a NASA project as part of a broader knowledge management and retrieval system. Results indicate that applying state-of-the-art natural language processing techniques, especially when fine-tuned using engineering data, to design information retrieval tasks shows significant promise in modernizing design knowledge management systems.

Hannah S. Walsh↗

Savannah River Site H-Canyon Advancing Technologies for Remote Inspections - 20345

In 2017, the DOE Environmental Management Office of Technology Development (DOE-EM TD) sponsored the H-Canyon Advanced Technology Demonstration (ATD) to demonstrate to DOE facilities the value of using new commercial-off-the-shelf (COTS) and near-ready technologies to solve difficult problems and enhance worker safety. The DOE Savannah River Site (SRS) H-Canyon Air Exhaust Tunnel (HCAEX) inspection task was identified as representative of the hazardous, human denied environments which could benefit from advanced technologies. The HCAEX underground concrete tunnel is visually inspected biannually using a camera mounted on a remotely operated vehicle (ROV) designed and built by SRNL. While tunnel images have provided valuable visual information, it is desirable to have a higher order of understanding of the environment to support a more thorough structural integrity (SI) analysis and for long term planning purposes. As part of the ATD, the Concrete Integrated Product Team (CIPT) was formed to identify and evaluate available sensors and methods mature enough to remotely obtain tunnel concrete characterization data of high value and with a high probability of success. The team included SMEs and H-Canyon stakeholders in the field of concrete, nondestructive examination (NDE), structural integrity, sensors and remote systems from SRNL, SRNS, LANL, DOE-SR and the Army Corps of Engineering. The CIPT completed an in-depth identification of customer concrete inspection needs and potential technology solutions. Sensors and methods were evaluated on performance, data usefulness, cost and the feasibility of a successful deployment given the unique tunnel access challenges and environment. Two technologies were identified as promising by the CIPT for near term demonstration and evaluation: Lidar (Light Detection and Ranging) 3-dimensional (3D) mapping and remote robotic deployment of NDE instrumentation. Laser spectroscopy to characterize tunnel surface chemical changes was also of interest, but presently cost prohibitive. This paper will include a discussion of the two efforts underway to evaluate and implement the CIPT recommendations. First, the status of the November 2019 deployment of Lidar at a single location into the tunnel is presented. This initial deployment provided the team a learning curve and lessons learned on the challenges of tunnel deployment to include remote operation and data collection, stabilization of the sensor in high air flow (∼30 mph), ability to achieve a tolerance accuracy of 0.25-inches, and the probability to identify change in tunnel dimensions over time. Secondly, a discussion on the development of the Robotic Arm Concrete Inspection Test Bed capable of deploying NDE instruments to examine custom concrete forms will be presented. Concrete forms simulating the rough concrete surfaces, strength, composition and potential structural defects that can be found at our DOE EM facilities have been designed and built for the test bed. Two state-of-the art concrete NDE instruments have been identified as having potential to work on rough concrete walls, they are being tested and characterized as to their ability to provide desired structural integrity data to include wall thickness and defect identification on the developed test beams. Lastly, lessons learned, and the path forward will be presented. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Lessons We Learned Designing and Building the Chandra Telescope

2014 marks the crystal (15th) anniversary of the launch of the Chandra X‐ray Observatory. This paper offers some of the major lessons learned by some of the key members of the Chandra Telescope team. We offer some of the lessons gleaned from our experiences developing, designing, building and testing the telescope and its subsystems, with 15 years of hindsight. Among the topics to be discussed are the early developmental tests, known as VETA‐I and VETA‐II, requirements derivation, the impact of late requirements and reflection on the conservatism in the design process.

Arenberg, Jonathan↗

Sludge Removal: Success and Partnership with T Plant - 20510

U.S. DOE contractor CH2M Hill Plateau Remediation Company (CHPRC) has safely and efficiently managed the removal of highly radioactive sludge from the 105-K West Reactor fuel storage basin (105- KW Basin) near the Columbia River. In mid-September 2019, sludge retrieval was completed after 21 storage containers were safely loaded with highly radioactive sludge and transported approximately 13 miles from the 105-KW Basin to T Plant, located in the 200 West Area on the Central Plateau of the Hanford Site. Sludge removal represents the last major source term reduction necessary before the K West Reactor and fuel storage basin can transition to closure activities in preparation for final deactivation and demolition. The technical complexity of the sludge retrieval process, coupled with the challenging physical and radiological characteristics of the waste, necessitated a methodical and deliberate approach using unique design and operational solutions to safely conduct the work. This challenge was further complicated by the need to plan and conduct the work in two separate facilities, each subject to the controls and requirements of its own nuclear facility safety basis. The project overcame these challenges through creating an integrated team that actively engaged, communicated and coordinated each phase of the project to ensure successful completion. This paper will cover how these key elements of the Sludge Removal Project led to its success: - Integrating project planning and management; - Lessons learned from design and construction; - Preparing for a successful campaign (lessons learned from testing and start-up); - Lessons learned from operating in two separate facilities, transporting sludge containers on the Hanford Site and ensuring compliance with a range of regulatory and safety basis requirements. The establishment of an integrated group spanning two facilities and multiple organizations created a team capable of overcoming the challenges necessary to successfully plan and execute the sludge retrieval mission. Sharing lessons learned from this successful project can enhance the ability of teams across the DOE complex to successfully plan and execute complex projects. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Lessons from 30 Years of Flight Software

This presentation takes a brief historical look at flight software over the past 30 years, extracts lessons learned and shows how many of the lessons learned are embodied in the Flight Software product line called the core Flight System (cFS). It also captures the lessons learned from developing and applying the cFS.

Flight Software↗

Surviving the Lead Reliability Engineer Role in High Unit Value Projects

A project with a very high unit value within a company is defined as a project where a) the project constitutes one of a kind (or two-of-a-kind) national asset type of project, b) very large cost, and c) a mission failure would be a very public event that will hurt the company's image. The Lead Reliability engineer in a high visibility project is by default involved in all phases of the project, from conceptual design to manufacture and testing. This paper explores a series of lessons learned, over a period of ten years of practical industrial experience by a Lead Reliability Engineer. We expand on the concepts outlined by these lessons learned via examples. The lessons learned are applicable to all industries.

lessons learned↗

Utah FORGE: Phase 2C Topical Report

This is the topical report that wraps up the work and results achieved during Utah FORGE Phase 2C. The zip file includes several folders containing (1) an overview; (2) the results; (3) the lessons learned; and (4) the conclusions. It also contains a folder containing appendices including (1) the updated permitting inventory; (2) the updated site characterization data inventory; (3) the updated conceptual geological model; and (4) the stakeholders engagement and outreach status.

15 GEOTHERMAL ENERGY↗

Ontology Development and Evolution in the Accident Investigation Domain

InvestiigationOrganizer (IO) is a collaborative semantic web system designed to support the conduct of mishap investigations. IO provides a common repository for a wide range of mishap related information, allowing investigators to integrate evidence, causal models, and investigation results. IO has been used to support investigations ranging from a small property damage case to the loss of the Space Shuttle Columbia. Through IO'S use in these investigations, we have learned significant lessons? about the application of ontologies and semantic systems to solving real-world problems. This paper will describe the development of the ontology within IO, from the initial development, its growth in response to user requests during use in investigations, and the recent work that was done to control the results of that growth. This paper will also describe the lessons learned from this experience and how they may apply to the implementaton of future ontologies and semantic systems.

Carvalho, Robert↗

Cost Analysis in a Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single mission-type support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multi-mission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature service-oriented, multi-mission control centers to streamline or refine their cost analysis process.

Felton, Larry↗

Cost Analysis In A Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single missiontype support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multimission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature serviceoriented, multi-mission control centers to streamline or refine their cost analysis process.

Newhouse, M.↗