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 919 records · Page 51
All sourcesNASA NTRSDOE OSTI
NASA NTRS2025

Provider of Services for Urban Air Mobility (PSU) Prototype Simulation (X5) Final Report

Urban Air Mobility (UAM) is a new air transportation service concept to carry passengers or cargo in metropolitan areas, leveraged by innovative aircraft and air traffic automation technologies. NASA has conducted a series of simulations, called the X-series simulation, to evaluate the UAM concept of operations and support the development of airspace procedures and services for UAM operations. The simulation called “X5” was conducted in 2023 to test a Provider of Services for UAM (PSU) prototype developed by NASA for UAM flight planning, strategic conflict management support, and data exchange between UAM operators. In this simulation, two strategic conflict management capabilities, Demand-Capacity Balancing and Sequencing and Scheduling, were further investigated. This document describes the UAM system architecture modeled, the X5 simulation environment to be executed (e.g., traffic scenario and UAM airspace construct), and the strategic conflict management processes developed and evaluated in this study. Then, the simulation results are provided using several system performance metrics, such as the number of operations planned and activated, demand-capacity imbalances detected and resolved, and pre-departure delays. Based on these metrics, the test findings and lessons learned from this simulation are discussed. NASA developed a PSU prototype as part of a reference implementation of UAM system architecture and evolved strategic conflict management capabilities for UAM operations from the previous collaborative simulations with industry partners. Below is the summary of the achievements: - Aligned NASA’s UAM reference architecture with the FAA’s UAM ConOps notional architecture - Extended UAM airspace management capabilities to include 1) Demand-Capacity Balancing (DCB) to ensure operators coordinate planned usage of shared vertiports, and 2) Sequencing and Scheduling (S&S) at UAM corridor entry and exit points to help facilitate an orderly flow of traffic - Defined the PSU information exchange APIs and requirements towards informing industry standards - Developed and tested a NASA PSU prototype as reference implementation to validate the requirements and APIs - Developed a prototype service connecting NASA’s PSU and the FAA system for testing future PSU-ATM interface requirements - Tested NASA-developed assumptions for UAM operations such as airspace design, procedures, vehicle performance, and strategic conflict management methods to inform future Cooperative Operating Practices (COPs) development with industry - Evaluated system performance metrics such as number of simultaneous operations and ground delays that can help define system-level requirements. The simulation results showed that the UAM traffic demand could be managed to minimize the needs of tactical separation provision with ground delays assigned by DCB and S&S. These accomplishments and the lessons learned from the PSU Prototype X5 simulation activities will be valuable inputs for the Air Mobility Pathfinders (AMP) project, which is NASA’s new project to create and evaluate a reference architecture for safe, secure, and scalable UAM operations.

Simulation↗
DOE OSTI2026

Towards continual machine learning for particle accelerators

This talk covers our work on errant beam prognostics at the Spallation Neutron Source (SNS), focusing on the end-to-end process from data collection to the development and deployment of predictive models in specific. A short overview of AIML work done for accelerators and current trends will be presented. We will walk through key steps involved in creating robust Machine Learning (ML) models, including model training, validation, and deployment in an operational setting. In addition to presenting our technical approach, we will share valuable lessons learned, emphasizing the importance of infrastructure to support the continuous adaptation of models to evolving data and system behaviors. This talk will provide insights into the challenges and solutions involved in applying ML to real-world operational environments, with a particular focus on managing data drift and changes in accelerator setup while ensuring model resilience over time.

Accelerator Physics↗
DOE OSTI2022

In-Kind Contributions: The PIP-II Project at Fermilab

The Proton Improvement Plan II (PIP-II) Project is the first U.S. accelerator project that has significant contributions from international partners. A project management framework was created to fully integrate and make consistent across all partners the design, development, and delivery of In-Kind Contributions (IKC) into PIP-II. This framework consists of planning documentation, procedures, and communication and assessment processes to control schedule, risk, quality, and technical integration over the lifetime of the project. The purpose of this paper is to present the PIP-II IKC model put in place to properly integrate the IKC deliverables into the PIP-II Linac and share experience and lessons learned from its early implementation.

43 PARTICLE ACCELERATORS↗
DOE OSTI2023

Distributed Renewables for Arctic Energy: A Case Study

Alaska is a vast state that stretches into the Arctic Circle. Roughly 140,000 people in the state are dependent on isolated electric grids, traditionally burning expensive fossil fuels. This has negative impacts on air quality and climate. As the climate warms, fuel supply chains and traditional ways of life are threatened. Renewable electric sources offer a clean, resilient alternative with less volatile costs, but there are a variety of technical, social, economic, and political challenges to developing renewable energy systems in remote Arctic communities. Examples include harsh operating conditions, lack of local technical and managerial capacity, complex funding mechanisms, and glacial permitting processes. In this study, we interview one group of communities that are interested in adding renewable energy to their systems to understand the needs and challenges they face, and then another group that has successfully installed renewable energy, to understand how they overcame such challenges and the lessons they learned. Notable results include the importance of local buy-in, education, and technical involvement, procuring external funding sources, inter-community collaboration, installing bespoke systems, and working with reliable equipment suppliers. The goal of this report is to orient and inspire Arctic communities that want to begin their renewable transition, by providing helpful examples and points of contact.

17 WIND ENERGY↗
DOE OSTI2025

Commercialization of Pumped Storage Hydropower Technologies

Argonne National Laboratory and the National Laboratory of the Rockies were tasked by the U.S. Department of Energy’s Water Power Technology Office (WPTO) to conduct the Commercialization of Pumped Storage Hydropower Technologies study to investigate commercialization challenges faced by developers of pumped storage hydropower (PSH) projects and technologies by going beyond literature review to gather direct industry insights, lessons learned and best practices from interviews and webinars with industry specialists to create this report for PSH stakeholders and the general public. Researchers explored key challenges faced by PSH developers and innovators seeking to commercialize new technologies to improve PSH design, siting, construction, and operations. Along with highlighting challenges, the study sought to identify the best practices in developing and deploying new PSH projects and innovations. This report is designed to present insights, lessons learned, and best practices relevant to those with an interest in highlighting, informing, or advancing these PSH commercialization efforts. Along with highlighting challenges and best practices, the study sought to identify avenues by which DOE and national laboratories can help support and streamline PSH commercialization and project development processes.

13 HYDRO ENERGY↗
DOE OSTI2023

Precursor Analysis Report: SQL Slammer Worm Infection of Davis-Besse Nuclear Power Plant 2003

The SQL Slammer Worm Infection of Davis-Besse Nuclear Power Plant 2003 Precursor Analysis Report leverages publicly available information about Davis-Besse’s 2003 cyber attack and catalogs anomalous observables for each technique employed in the attack. This analysis is based upon the methodology of the Cybersecurity for the Operational Technology Environment (CyOTE) program. On 25 January 2003, the SQL Slammer worm infected more than 90% of vulnerable hosts and crashed the internet in 10 to 15 minutes, making it one of the fastest spreading worms in history. SQL Slammer is a fileless, memory-resident worm that remotely exploits a stack-based buffer overflow vulnerability on local hosts to intensively scan and rapidly self-propagate across the internet. The worm infected approximately 300,000 unpatched hosts running Microsoft Structured Query Language (SQL) Server 2000 or Microsoft Desktop Engine (MSDE) 2000 with SQL Server Resolution Service. The SQL Slammer worm indirectly infected FirstEnergy’s Davis-Besse nuclear power plant by first infecting a consultant’s company network server and then propagating through an external misconfigured connection into Davis-Besse’s site network. The infection caused major network congestion, slow performance, data overloads, and the inability of local hosts to communicate with each other, which eventually caused a loss of availability and a loss of view when the Safety Parameter Display System (SPDS) and Plant Process Computer (PPC) crashed. At the time of the infection, the plant was already offline, the digital monitoring systems had redundant analog backups, and the plant control and safety functions were not affected, so there were no concerns of a safety breach. However, this incident resulted in many lessons learned and spawned important discussions about cybersecurity’s role in nuclear safety and electric power reliability regulation, policy, and guidance. Researchers and analysts identified 10 unique techniques utilized during the attack with a total of 640 observables using MITRE ATT&CK® for Industrial Control Systems. The CyOTE program assesses observables accompanying techniques used prior to the triggering event to identify opportunities to detect malicious activity. If observables accompanying the attack techniques are perceived and investigated prior to the triggering event, earlier comprehension of malicious activity can take place. Eight of the identified techniques used during Davis-Besse cyber attack were precursors to the triggering event. Analysis identified 596 observables associated with these precursor techniques, 428 of which were assessed to have an increased likelihood of being perceived in the 331 days preceding the triggering event. The response and comprehension time could have been reduced if the observables had been identified earlier. The information gathered in this report contributes to a library of observables tied to a repository of artifacts, data sources, and technique detection references for practitioners and developers to support the comprehension of indicators of attack. Asset owners and operators can use these products if they experience similar observables or to prepare for comparable scenarios.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗
NASA NTRS1983

The Space Shuttle focused-technology program - Lessons learned

The results of a focused technology program (FTP), its management structure, the development of the Space Shuttle, and lessons applicable to future space programs such as a space station are discussed. A committee was formed by NASA in 1969 to define the technologies necessary for a reusable spacecraft. Basic and applied research assessments were featured at the beginning of the process. Working groups were established to cover all necessary areas, e.g., Operations, Structures and Materials, Aerothermodynamics, etc., and tasks were distributed to appropriate NASA centers. Funding was drawn from existing budgets. The FTP proceeded successfully because of an understanding of the respective roles of industry and government, the willingness of industry to invest early in a new technology, and the unclassified status of information generated by the program. The in-house design and technology transfer methods that brought the project to a technology demonstration phase are explored, noting the necessity for users to take part in the development within their field.

Fitzgerald, P. E., Jr.↗
NASA NTRS1992

National launch system core vehicle

A new launch system is being defined to provide significant improvements in the national launch capability. The most challenging requirements are to reduce operational cost and increase system reliability, dependability, responsiveness while maintaining acceptable mission performance. System architecture studies have established that a family of vehicles is required to launch the required range of payloads. The vehicle design approach implements a design process that identifies the system design criteria and design concepts that enable the vehicle to meet the objectives of cost, reliability, safety and performance. The vehicle design features for the 50 to 100 K payload capability will utilize cost effective elements derived from existing vehicles, emerging technology and lessons learned to enable the system to be developed at a reasonable investment and to deliver payloads in an operationally efficient manner with high reliability.

Worlund, Armis L.↗
NASA NTRS2005

Apex Reference Manual 3.0 Beta

Apex is a toolkit for constructing software that behaves intelligently and responsively in demanding task environments. Reflecting its origin at NASA where Apex continues to be developed, current applications include: a) Providing autonomous mission management and tactical control capabilities for unmanned aerial vehicles including an autonomous surveillance helicopter and a simulation prototype of an unmanned fixed-wing aircraft to be used for wildfire mapping; b) Simulating human air traffic controllers, pilots and astronauts to help predict how people might respond to changes in equipment or procedures; and c) Predicting the precise duration and sequence of routine human behaviors based on a human-computer interaction engineering technique called CPM-GOMS. Among Apex s components are a set of implemented reasoning services, such as those for reactive planning and temporal pattern recognition; a software architecture that embeds and integrates these services and allows additional reasoning elements to be added as extensions; a formal language for specifying agent knowledge; a simulation environment to facilitate prototyping and analysis; and Sherpa, a set of tools for visualizing autonomy logic and runtime behavior. In combination, these are meant to provide a flexible and usable framework for creating, testing, and deploying intelligent agent software. Overall, our goal in developing Apex is to lower economic barriers to developing intelligent software agents. New ideas about how to extend or modify the system are evaluated in terms of their impact in reducing the time, expertise, and inventiveness required to build and maintain applications. For example, potential enhancements to the AI reasoning capabilities in the system are reviewed not only for usefulness and distinctiveness, but also for their impact on the readability and general usability of Apex s behavior representation language (PDL) and on the transparency of resulting behavior. A second central part of our approach is to iteratively refine Apex based on lessons learned from as diverse a set of applications as possible. Many applications have been developed by users outside the core development team including engineers, researchers, and students. Usability is thus a central concern for every aspect of Apex visible to a user, including PDL, Sherpa, the Apex installation process, APIs, and user documentation. Apex users vary in their areas of expertise and in their familiarity with autonomy technology. Focusing on usability, a development philosophy summarized by the project motto "Usable Autonomy," has been important part of enabling diverse users to employ Apex successfully and to provide feedback needed to guide iterative, user-centered refinement.

Freed, Michael A.↗
NASA NTRS2003

Cost savings through multimission code reuse for Mars image products

An overview of the library's design will be presented, along with mission adaptation experiences and lessons learned, and the kinds of additional functionality that have been added while still retaining its multimission character. The application programs using the library will also be briefly described.

cost savings ground system image processing Mars i↗
NASA NTRS2007

The X-43A Flight Research Program: Lessons Learned on the Road to Mach 10

During an aerospace engineer's undergraduate studies, he or she will attend classes in aerodynamics, thermodynamics, structures, stability and control, dynamics, design, propulsion, and computer science, along with the related courses in mathematics, physics, statistics, and chemistry required to understand the material. Upon graduation, the new engineer will have acquired a basic knowledge of how to build an aerospace vehicle. What only comes through experience, however, is the understanding of the inevitable imperfect process through which an aerospace vehicle is built. This is the adventure of turning a basic concept into functional hardware. Engineers working on a project must often deal with ambiguous situations. They are routinely asked by management to provide risk assessments of a project, yet even after careful analysis uncertainties remain. The project must be accomplished within finite limits of time and money. The question an engineer answers is whether the solution to potential problem is worth the cost and schedule delay, or if the solution might actually be worse than the problem it is meant to solve. Review protocols are established to ensure that an unknown has not been overlooked. But these cannot protect against an unknown unknown. Examples of these situations can be found in the history of the X-43A Hyper-X (Hypersonic Experiment) program. In this NASA project, a supersonic combustion ramjet (scramjet) engine was flight tested on a subscale vehicle. The X-43A Hyper-X Research Vehicle (HXRV) was launched from a B-52B mothership, then boosted to the test speed by a modified Pegasus rocket first stage, called the Hyper-X Launch Vehicle (HXLV). Once at the proper speed and altitude, the X-43A separated from the booster, stabilized itself, and then the engine test began. Although wind-tunnel scramjet engine tests had begun in the late 1950s, before the Hyper-X program there had never been an actual in-flight test of such an engine integrated with an appropriate airframe. Thus, while the scramjet had successfully operated in the artificial airflow of wind tunnels, the concept had yet to be proven in real air. These conditions meant changes in density and temperature, as well as changes in angle of attack and sideslip of a free-flying vehicle. A wind tunnel is limited in its ability to simulate these subtle factures, which have a major impact on almost any vehicle, but especially that of a scramjet's performance. The Hyper-X project was to provide a real-world benchmark of the ground test data. The full scale X-43A engine would be operated in the wind tunnel, and then flown, and the data from its operation would then be compared with projections. If these matched, the wind tunnel data would be considered a reliable design tool for future scramjet. If there were significant differences, the reasons for these would have to be identified. Until such information was available, scramjets would lack the technological maturity to be considered for future space launch or high-speed atmospheric flight vehicles.

Peebles, Curtis↗
NASA NTRS2003

Lessons Learned from Mir - A Payload Perspective

Among the principal objectives of the Phase 1 NASA/Mir program were for the United States to gain experience working with an international partner, to gain working experience in long-duration space flight, and to gain working experience in planning for and executing research on a long-duration space platform. The Phase 1 program was to provide to the US early experience prior to the construction and operation of the International Space Station (Phase 2 and 3). While it can be argued that Mir and ISS are different platforms and that programmatically Phase 1 and ISS are organized differently, it is also clear that many aspects of operating a long-duration research program are platform independent. This can be demonstrated by a review of lessons learned from Skylab, a US space station program of the mid-1970's, many of which were again "learned" on Mir and are being "learned" on ISS. Among these are optimum crew training strategies, on-orbit crew operations, ground support, medical operations and crew psychological support, and safety certification processes

Uri, John J.↗
NASA NTRS2002

Managing Risk in Safety Critical Operations - Lessons Learned from Space Operations

The Mission Control Center (MCC) at Johnson Space Center (JSC) has a rich legacy of supporting Human Space Flight operations throughout the Apollo, Shuttle and International Space Station eras. Through the evolution of ground operations and the Mission Control Center facility, NASA has gained a wealth of experience of what it takes to manage the risk in Safety Critical Operations, especially when human life is at risk. The focus of the presentation will be on the processes (training, operational rigor, team dynamics) that enable the JSC/MCC team to be so successful. The presentation will also share the evolution of the Mission Control Center architecture and how the evolution was introduced while managing the risk to the programs supported by the team. The details of the MCC architecture (e.g., the specific software, hardware or tools used in the facility) will not be shared at the conference since it would not give any additional insight as to how risk is managed in Space Operations.

Gonzalez, Steven A.↗
NASA NTRSDate not supplied

From Apollo to Artemis: Opening and Processing Lunar Core 73002 for the ANGSA Program

The Apollo mission returned 382 kg of lunar material comprising rock, soil and core samples. Some of these samples were intentionally set aside after their return from the Moon for future study, including samples sealed on the lunar surface, frozen samples and samples stored under Helium. The Apollo Next Generation Sample Analysis (ANGSA) program was established to study thesesamples, in part to help bridge the gap between Apollo and the next generation of lunar science and exploration.Apollo 17 double drive tube core sample 73001/73002 was collected about 50 meters east of Lara Crater from a landslide deposit originating from South Massif. After separating the two halves, the lower drive tube 73001 was immediately sealed in a special vacuum container. Both drive tubes were then placed in an Apollo Lunar Sample Return Container (ALSRC) and returned to Earth under vacuum. Total sample weight and length of 73001/73002 is 1263.0 g and up to 60 cm, with the upper drive 73002 containing 429.7 g and 23 cm of material ( which was then compressed to 18.5 cm during extrusion in the lab). We will present the meticulous methods involved in preparing for, opening and processing lunar core 73002, the upper half of the double drive tube. This includes searching and locating procedures and tools, practicing assembly and extrusion in a mock-up, and finally opening and dissecting the core sample 73002. Challenges (both expected and unexpected) encountered along the way and lessons learned during this project will help pave the way towards improving future lunar sample return missions and advancing insight into the Moon’s history

C. H. Krysher↗
DOE OSTI2021

Lessons learned from studying Histoplasma capsulatum extracellular vesicles

Histoplasma capsulatum is a major endemic mycosis. Our laboratories have demonstrated that H. capsulatum produces extracellular vesicles (EV) that are loaded with diverse compounds that influence virulence. We have further shown that H. capsulatum dynamically regulates the loading and release of fungal EV in response to stimuli and growth conditions. This chapter details the current knowledge of EV biology in H. capsulatum and the impact of this information on our understanding of this important process that is closely linked to pathogenesis.

Zamith-Miranda, Daniel↗
NASA NTRS1983

TDRS-A - The pioneering payload

The first launch of a Tracking Data Relay Satellite (TDRS-A) on board the Shuttle Orbiter 'Challenger' of the Space Transportation System (STS) provided many pioneering events as a payload/user. The TDRS-A was launched as a payload of the STS as well as a payload of the Inertial Upper Stage (IUS) on April 4, 1983. This paper traces the payload processing flow of the TDRS-A from its arrival at the Kennedy Space Center (KSC), through its launch on Challenger and its trans-orbit flight on the IUS to geosynchronous orbit. The TDRS-A, as a customer/user of these launch systems, is examined and reviewed and lessons learned are noted.

Browning, R. K.↗
NASA NTRS1991

Space Station Freedom - Design review process

The Space Station Freedom (SSF) design review process is described. The SSF program background is summarized, and the program review management plan and organization are described. The technical approach of the Integrated System Preliminary Design Review (ISPDR) is examined along with the Review Item Discrepancy Tracking System. ISPDR results are summarized and compared with its objectives. Lessons learned for the future support of the management life cycle are addressed.

Koontz, Robert↗
NASA NTRS2007

Looking at Hubble Through the Eyes of JWST

The phase retrieval algorithm developed for the James Webb Space Telescope (JWST) is used to process archival image data that was originally used to characterize the Hubble primary mirror edge defect. The Hubble mirror conic constant is inferred from these results and comparisons are made with earlier conic values reported by teams comprising the HARP (Hubble Aberration Recovery Project) study. A number of important lessons learned from the Hubble phase retrieval problem are described and a discussion is given on how these have been incorporated into the JWST Observatory design.

Dean, Bruce H.↗