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 649 records · Page 36
All sourcesNASA NTRSDOE OSTI
DOE OSTI2023

Lessons Learned From Techno-Economic Analysis of Solar Photovoltaics and Battery Energy Storage at a Vietnam Industrial Park

Through the Clean Energy Investment Accelerator (CEIA), engineers from the United States (U.S.) National Renewable Energy Laboratory (NREL) conducted a case study analysis evaluating the techno-economic feasibility of battery energy storage systems (BESS) at an industrial park in Vietnam. The analysis uses NREL's REopt platform, a distributed energy modeling and optimization tool, to identify the cost-optimal system sizing for BESS, in conjunction with onsite renewables such as solar photovoltaics (PV), to reduce electricity costs, increase onsite renewable energy generation utilization, and improve resilience to grid outages.

batteries↗
NASA NTRS2006

Spitzer Space Telescope Sequencing Operations Software, Strategies, and Lessons Learned

The Space Infrared Telescope Facility (SIRTF) was launched in August, 2003, and renamed to the Spitzer Space Telescope in 2004. Two years of observing the universe in the wavelength range from 3 to 180 microns has yielded enormous scientific discoveries. Since this magnificent observatory has a limited lifetime, maximizing science viewing efficiency (ie, maximizing time spent executing activities directly related to science observations) was the key operational objective. The strategy employed for maximizing science viewing efficiency was to optimize spacecraft flexibility, adaptability, and use of observation time. The selected approach involved implementation of a multi-engine sequencing architecture coupled with nondeterministic spacecraft and science execution times. This approach, though effective, added much complexity to uplink operations and sequence development. The Jet Propulsion Laboratory (JPL) manages Spitzer s operations. As part of the uplink process, Spitzer s Mission Sequence Team (MST) was tasked with processing observatory inputs from the Spitzer Science Center (SSC) into efficiently integrated, constraint-checked, and modeled review and command products which accommodated the complexity of non-deterministic spacecraft and science event executions without increasing operations costs. The MST developed processes, scripts, and participated in the adaptation of multi-mission core software to enable rapid processing of complex sequences. The MST was also tasked with developing a Downlink Keyword File (DKF) which could instruct Deep Space Network (DSN) stations on how and when to configure themselves to receive Spitzer science data. As MST and uplink operations developed, important lessons were learned that should be applied to future missions, especially those missions which employ command-intensive operations via a multi-engine sequence architecture.

missions operations↗
DOE OSTI2021

Lessons Learned—Lithium Silicide Hydration Fire

Alkali metals, such as lithium, sodium, potassium, etc., are highly reactive elements. While researchers generally handle these metals with caution, less caution is taken when these elements have been “reacted”. In this work, a recent incident is examined in which a pair of researchers ignited a lithium silicide alloy sample that was assumed to be fully hydrated to lithium hydroxide and, thereby, no longer water-reactive. However, variations in the original chemical composition of the lithium compounds examined resulted in select mixtures failing to hydrate and react completely to lithium hydroxide in the time frame allowed. This gave rise to residual unreacted, water-sensitive lithium silicide which resulted in a violent exothermic reaction with water and autoignition of the produced hydrogen gas. This Article describes this incident and improvements that can be implemented to prevent similar incidents from occurring.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗
DOE OSTI2025

Radioisotope production at the advanced test reactor: process and lessons learned

The mission of the Advanced Test Reactor (ATR) at Idaho National Laboratory (INL) focuses on creating irradiation facilities for nuclear materials and fuels research. While radioisotope production is not a core part of the ATR mission, it is important for providing a U.S. domestic source of critical radioisotopes such as cobalt-60 (Co-60). Here, this paper gives an overview for radioisotopes currently being produced in ATR as well as other potential radioisotopes that can be produced in ATR. It also provides guidance on radioisotope production that can be applied to other test reactors.

ATR↗
NASA NTRS2014

Design and Lessons Learned on the Development of a Cryogenic Pupil Select Mechanism Used in the Testing and Calibration of the Integrated Science Instrument Module (ISIM) on the James Webb Space Telescope (JWST)

Calibration and testing of the instruments on the Integrated Science Instrument Module (ISIM) of the James Webb Space Telescope (JWST) is being performed by the use of a cryogenic, full-field, optical simulator that was constructed for this purpose. The Pupil Select Mechanism (PSM) assembly is one of several mechanisms and optical elements that compose the Optical Telescope Element SIMulator, or OSIM. The PSM allows for several optical elements to be inserted into the optical plane of OSIM, introducing a variety of aberrations, distortions, obscurations, and other calibration states into the pupil plane. The following discussion focuses on the details of the design evolution, analysis, build, and test of this mechanism along with the challenges associated with creating a sub arc-minute positioning mechanism operating in an extreme cryogenic environment. In addition, difficult challenges in the control system design will be discussed including the incorporation of closed-loop feedback control into a system that was designed to operate in an open-loop fashion.

Testing↗
NASA NTRSDate not supplied

Lessons Learned from NASA Goddard Space Flight Center’s Product Development Lead Training Schedule and Cost Development Workshop: Continuous Improvement

This presentation provides a status of the Goddard Space Flight Center (GSFC) effort to increase foundational knowledge of Product Development Leads (PDLs) in schedule and cost management including earned value management (EVM). In 2012, GSFC’s Engineering and Technology Directorate (ETD) implemented an in-house training program to prepare PDLs for managing the technical, cost, schedule, and risk aspects of spaceflight systems to meet their subsystem commitments. Developed in-house, the PDL training program provides an integrated approach to requirements development, risk, schedule and cost management, EVM, performance tracking, and other areas. The program has been held twice yearly since its inception with 531 participating and 451 completing the curriculum. In 2017, the program won the Robert H. Goddard award for Quality and Process Improvement. Program development and evolution were presented in the 2018 NASA Schedule and Cost Symposium. The presentation was so well received that this year we focus on one workshop within the program: Schedule and Cost Development, including EVM. We examine the on-going logic modeling process and how participant and stakeholder data influence workshop content and design, and how the disciplines of schedule and cost contribute to mission success. In this presentation we refresh you on how the approach integrates lecture, small group discussion, estimating, case study exercises, and problem solving. We update you on the data collected from participants and stakeholders, and we discuss how we use these data to measure training effectiveness. Specific topics include: • How the logic model is used as the backbone for continuous program improvement, • How feedback influences implementation and curriculum updates, • How data collection and analysis inform workshop content and development, including participant discoveries of EVM data, • How including the resource analyst and planner in the product development team supports project success.

Lessons Learned↗
NASA NTRS2008

NASA Crew Exploration Vehicle, Thermal Protection System, Lessons Learned

The Orion (CEV) thermal protection system (TPS) advanced development project (ADP) was initiated in late 2006 to reduce developmental risk by significant investment in multiple heat shield architectural solutions that can meet the needs both the Low Earth orbit (LEO) and Lunar return missions. At the same time, the CEV TPS ADP was also charged with developing a preliminary design for the heat shield to meet the PDR requirement and at the time of the PDR, transfer the design to Lockheed- Martin, the prime contractor. We reported on the developmental activities of the first 18 months at the IPPW5 in Bordeaux, France, last summer. In June 08, at the time of the IPPW6, the CEV TPS ADP would have nearly completed the preparation for the Orion PDR and would be close to the original three-year mark. We plan to report on the progress at the Atlanta workshop. In the past year, Orion TPS ADP investment in TPS Technology, especially in PICA ablative Heat-shield design, development, testing and engineering (DDTE) has paid off in enabling MSL mission to switch from SLA 561 V heat shield to PICA heat shield. CEV TPS ADP considered SLA 561 V as a candidate for LEO missions and our testing identified failure modes in SLA and as a result, we dropped SLA for further evaluation. This close synergy between two projects is a highly visible example of how investment in technology areas can and does benefit multiple missions. In addition, CEV TPS ADP has been able to revive the Apollo ablative system namely AVCOAT honeycomb architecture as an alternate to the baseline PICA architecture and we plan to report the progress we have made in AVCOAT. CEV TPS ADP has invested considerable resources in developing analytical models for PICA and AVCOAT, material property measurements that is essential to the design of the heat-shield, in arcjet testing, in understanding the differences between different arc jet facilities, namely NASA Ames, NASA JSC and Air Force's AEDC, and in Non-Destructive Evaluation (NDE), and in integration of and manufacturing heat shield as a system. The capabilities of the two heat shield systems including failure modes via testing and analysis, once established, can serve the Probe Community and future mission designers to inner and outer planetary exploration very well. For example, missions to Venus, Mars and Titan can use either one of the system by selecting the mission design parameters that utilizes the full characteristics of these system to make use of system efficiency that will result in reduced heat shield mass, system robustness that will enhance mission success and cost. We plan to present significant progresses of the past three years and highlight the significant contributions CEV TPS ADP Project has made to advance the state of the art in Thermal Protection System technology that has and will continue to benefit future entry probe missions.

NASA Crew Exploration Vehicle↗
NASA NTRS1997

Lessons Learned from the Clementine Mission

According to BMDO, the Clementine mission achieved many of its technology objectives during its flight to the Moon in early 1994 but, because of a software error, was unable to test the autonomous tracking of a cold target. The preliminary analyses of the returned lunar data suggest that valuable scientific measurements were made on several important topics but that COMPLEX's highest-priority objectives for lunar science were not achieved. This is not surprising given that the rationale for Clementine was technological rather than scientific. COMPLEX lists below a few of the lessons that may be learned from Clementine. Although the Clementine mission was not conceived as a NASA science mission exactly like those planned for the Discovery program, many operational aspects of the two are similar. It is therefore worthwhile to understand the strengths and faults of the Clementine approach. Some elements of the Clementine operation that led to the mission's success include the following: (1) The mission's achievements were the responsibility of a single organization and its manager, which made that organization and that individual accountable for the final outcome; (2) The sponsor adopted a hands-off approach and set a minimum number of reviews (three); (3) The sponsor accepted a reasonable amount of risk and allowed the project team to make the trade-offs necessary to minimize the mission's risks while still accomplishing all its primary objectives; and (4) The development schedule was brief and the agreed-on funding (and funding profile) was adhered to. Among the operational shortcomings of Clementine were the following: (1) An overly ambitious schedule and a slightly lean budget (meaning insufficient time for software development and testing, and leading ultimately to human exhaustion); and (2) No support for data calibration, reduction, and analysis. The principal lesson to be learned in this category is that any benefits from the constructive application of higher risk for lower cost and faster schedule will be lost if the schedule does not allow adequate time for the development of all essential systems or makes no allowance for human frailties. Another lesson to be drawn is that despite its limitations, if judged strictly as a science mission, Clementine attested that significant scientific information can be gathered during a technology-demonstration mission. In the current era of limited funds, when science missions will be infrequent, the opportunity to fly scientific instruments aboard missions whose objectives might be other than science must be seized and, indeed, encouraged. During such opportunities it would be inexcusable to do second-class science. Thus the scientific community must be actively involved in such projects from their initiation.

Source record↗
NASA NTRS1992

STGT program: Ada coding and architecture lessons learned

STGT (Second TDRSS Ground Terminal) is currently halfway through the System Integration Test phase (Level 4 Testing). To date, many software architecture and Ada language issues have been encountered and solved. This paper, which is the transcript of a presentation at the 3 Dec. meeting, attempts to define these lessons plus others learned regarding software project management and risk management issues, training, performance, reuse, and reliability. Observations are included regarding the use of particular Ada coding constructs, software architecture trade-offs during the prototyping, development and testing stages of the project, and dangers inherent in parallel or concurrent systems, software, hardware, and operations engineering.

Usavage, Paul↗
NASA NTRS1999

Designing Specification Languages for Process Control Systems: Lessons Learned and Steps to the Future

Previously, we defined a blackbox formal system modeling language called RSML (Requirements State Machine Language). The language was developed over several years while specifying the system requirements for a collision avoidance system for commercial passenger aircraft. During the language development, we received continual feedback and evaluation by FAA employees and industry representatives, which helped us to produce a specification language that is easily learned and used by application experts. Since the completion of the PSML project, we have continued our research on specification languages. This research is part of a larger effort to investigate the more general problem of providing tools to assist in developing embedded systems. Our latest experimental toolset is called SpecTRM (Specification Tools and Requirements Methodology), and the formal specification language is SpecTRM-RL (SpecTRM Requirements Language). This paper describes what we have learned from our use of RSML and how those lessons were applied to the design of SpecTRM-RL. We discuss our goals for SpecTRM-RL and the design features that support each of these goals.

Leveson, Nancy G.↗
NASA NTRS1993

Synthetic vision system flight test results and lessons learned

Honeywell Systems and Research Center developed and demonstrated an active 35 GHz Radar Imaging system as part of the FAA/USAF/Industry sponsored Synthetic Vision System Technology Demonstration (SVSTD) Program. The objectives of this presentation are to provide a general overview of flight test results, a system level perspective that encompasses the efforts of the SVSTD and Augmented VIsual Display (AVID) programs, and more importantly, provide the AVID workshop participants with Honeywell's perspective on the lessons that were learned from the SVS flight tests. One objective of the SVSTD program was to explore several known system issues concerning radar imaging technology. The program ultimately resolved some of these issues, left others open, and in fact created several new concerns. In some instances, the interested community has drawn improper conclusions from the program by globally attributing implementation specific issues to radar imaging technology in general. The motivation for this presentation is therefore to provide AVID researchers with a better understanding of the issues that truly remain open, and to identify the perceived issues that are either resolved or were specific to Honeywell's implementation.

Radke, Jeffrey↗
DOE OSTI2025

Emergency vacuum repairs in an aging accelerator: Case studies and lessons learned

Jefferson Lab operates the CEBAF electron accelerator at energies to 12 GeV for the Department of Energy Nuclear Physics program. The CEBAF injector beamline was designed and built in the early 1990s. Although we’ve upgraded and replaced many of the vacuum systems, we still have unique original components installed which operate daily. Over the past 3 years, we have had several vacuum leaks in ageing components leading to emergency repairs on a tight timeline. I’ll discuss the nature of these vacuum component failures, the difficulties in repair due to their ages, the lessons we’ve learned, and how we hope to minimize similar failures going forward.

Stutzman, Marcy [Thomas Jefferson National Acceler↗
NASA NTRS2006

Lessons Learned from Daily Uplink Operations during the Deep Impact Mission

The Deep Impact mission to comet Tempel-1 produced some of the more spectacular science results ever collected by a spacecraft. On July 4, 2005 the Deep Impact Flyby vehicle observed the Deep Impact Impactor vehicle's collision with the comet. 24 hours earlier the Flyby vehicle released the Impactor vehicle into the path of comet Tempel-1. The process to command the spacecraft was a challenge to the entire flight operations team. This paper presents an overview of the process used prepare command products for uplink and the lessons that were learned from this process.

mission operations↗
NASA NTRS2007

Lessons Learned from the Node 1 Sample Delivery Subsystem Design

This paper will provide an overview of the International Space Station (ISS) Environmental Control and Life Support (ECLS) design of the Node 1 Sample Delivery Subsystem (SDS) and it will document some of the lessons that have been learned to date for this part of the subsystem.

Williams, David E.↗
NASA NTRS1999

Unpressurized Logistics Carriers for the International Space Station: Lessons Learned

The International Space Station has been in development since 1984, and has recently begun on orbit assembly. Most of the hardware for the Space Station has been manufactured and the rest is well along in design. The major sets of hardware that are still to be developed for Space Station are the pallets and interfacing hardware for resupply of unpressurized spares and scientific payloads. Over the last ten years, there have been numerous starts, stops, difficulties and challenges encountered in this effort. The Space Station program is now entering the beginning of orbital operations. The Program is only now addressing plans to design and build the carriers that will be needed to carry the unpressurized cargo for the Space Station lifetime. Unpressurized carrier development has been stalled due to a broad range of problems that occurred over the years. These problems were not in any single area, but encompassed budgetary, programmatic, and technical difficulties. Some lessons of hindsight can be applied to developing carriers for the Space Station. Space Station teams are now attempting to incorporate the knowledge gained into the current development efforts for external carriers. In some cases, the impacts of these lessons are unrecoverable for Space Station, but can and should be applied to future programs. This paper examines the progress and problems to date with unpressurized carrier development identifies the lessons to be learned, and charts the course for finally accomplishing the delivery of these critical hardware sets.

Robbins, William W., Jr.↗
DOE OSTI2025

Lessons Learned from Three Agrivoltaic Installations in New Jersey

Agrivoltaics is a new technology that has the potential to positively impact commercial farming by combining agricultural practices with the generation of solar energy. While some yield reduction is to be expected, resulting from less sunlight reaching the plant canopy and ground occupied by support structures, the generated electricity provides a low-risk supplemental income to farmers. In order to combine farming with electricity generation, agrivoltaic systems use a lower ground coverage ratio compared to normal solar farms and the PV panels are often mounted higher above the ground in order to facilitate the movement of agricultural equipment and to reduce the contrast between shaded and non-shaded areas. With funding provided from the state of New Jersey and the New Jersey Agricultural Experiment Station (NJAES), we designed and installed three unique agrivoltaic research systems at Rutgers/NJAES farms. These projects were recently completed and are generating electricity that is exported to the grid. This paper discusses the lessons we have learned along the way, including all the steps necessary to see an agrivoltaic project through to completion.

Both, A. J. (ORCID:0000000150845296)↗