Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “engine optimization”

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 253 records · Page 14
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Transient Optimization of an Electrified Gas Turbine Engine Using Machine Learning

Gas turbine engines are designed with sufficient margin to prevent stall under normal operating conditions throughout their life. This compromise ensures that during rapid accelerations, compressor operation remains stable, but at the cost of efficiency and thrust responsiveness. The design margin encompasses multiple sources of uncertainty and systematic deviances from the operating line, the largest of which is the transient allowance. This set-aside accounts for the temporary incoordination of the engine spools during an acceleration while still enabling it to meet the certification requirement to accelerate from low to high power within a specified time, and without experiencing overtemperature, surge, stall, or other detrimental factors. Electrification of the powertrain provides the opportunity to address this reserve and truly optimize the design. The addition of electric machines inherent in hybrid propulsion concepts offers a means to interact with the engine shafts such that the necessary margin can be reduced, which can positively impact the engine design. By adjusting the amount of power extracted from or injected to the engine spools by the electric machines during transient operation, excursions from the operating line can be minimized. Past work using a dynamic engine model has shown that optimization of the fuel flow schedule during acceleration can reduce the required margin while still meeting the time requirement, and results are further improved when combined with power injection and extraction. The current work uses machine learning through a genetic algorithm to address the problem holistically by concurrently optimizing the electric machine power command and fuel flow acceleration schedule using an updated, higher fidelity version of the original engine model.

Stall Margin↗
NASA NTRS2024

Transient Optimization of an Electrified Gas Turbine Engine Using Machine Learning

Gas turbine engines are designed with sufficient margin to prevent stall under normal operating conditions throughout their life. This compromise ensures that during rapid accelerations, compressor operation remains stable, but at the cost of efficiency and thrust responsiveness. The design margin encompasses multiple sources of uncertainty and systematic deviances from the operating line, the largest of which is the transient allowance. This set-aside accounts for the temporary incoordination of the engine spools during an acceleration while still enabling it to meet the certification requirement to accelerate from low to high power within a specified time, and without experiencing overtemperature, surge, stall, or other detrimental factors. Electrification of the powertrain provides the opportunity to address this reserve and truly optimize the design. The addition of electric machines inherent in hybrid propulsion concepts offers a means to interact with the engine shafts such that the necessary margin can be reduced, which can positively impact the engine design. By adjusting the amount of power extracted from or injected to the engine spools by the electric machines during transient operation, excursions from the operating line can be minimized. Past work using a dynamic engine model has shown that optimization of the fuel flow schedule during acceleration can reduce the required margin while still meeting the time requirement, and results are further improved when combined with power injection and extraction. The current work uses machine learning through a genetic algorithm to address the problem holistically by concurrently optimizing the electric machine power command and fuel flow acceleration schedule using an updated, higher fidelity version of the original engine model.

Stall Margin↗
NASA NTRS2026

Integrated Computational Materials Engineering (ICME) Capability Maturity Levels for Ecosystems Enabling Digital Transformation

Digital engineering (DE) and integrated computational materials engineering (ICME) are widely recognized as critical enablers of faster, more affordable, and more reliable aerospace systems. However, many organizations have struggled to realize the promised return on investment (ROI) from digital initiatives. A primary reason is the absence of a shared, decision-focused framework that distinguishes simple digitization of existing workflows from true digital transformation that fundamentally changes how engineering decisions are made. This paper introduces an ICME capability maturity framework that fills this gap. The framework defines six cumulative ICME capability maturity levels (CMLs), explicitly tied to decision authority, engineering integration, optimization, and uncertainty management across material, process, structure, and performance scales. It is designed to complement established readiness metrics such as technology readiness levels (TRLs), manufacturing readiness levels (MRLs), and integration readiness levels (IRLs), by addressing a missing dimension: the conditions required for model-informed decision authority across scales. A unifying figure and capability table illustrate the six-level ICME Capability Maturity Framework, showing how organizations progress from digitization—with limited or negative ROI—to true digital transformation, where ICME-enabled workflows deliver measurable improvements in decision quality, cycle time, risk reduction, and reuse. The framework is intended for both technical practitioners and executive leadership, providing a common language to assess current state, guide roadmaps, align software ecosystem investments, and set realistic expectations for digital transformation outcomes. A regulatory-relevant statement clarifying the relationship between ICME capability and existing certification frameworks is provided.

ICME↗
NASA NTRS1994

Fault Tree Based Diagnosis with Optimal Test Sequencing for Field Service Engineers

When field service engineers go to customer sites to service equipment, they want to diagnose and repair failures quickly and cost effectively. Symptoms exhibited by failed equipment frequently suggest several possible causes which require different approaches to diagnosis. This can lead the engineer to follow several fruitless paths in the diagnostic process before they find the actual failure. To assist in this situation, we have developed the Fault Tree Diagnosis and Optimal Test Sequence (FTDOTS) software system that performs automated diagnosis and ranks diagnostic hypotheses based on failure probability and the time or cost required to isolate and repair each failure. FTDOTS first finds a set of possible failures that explain exhibited symptoms by using a fault tree reliability model as a diagnostic knowledge to rank the hypothesized failures based on how likely they are and how long it would take or how much it would cost to isolate and repair them. This ordering suggests an optimal sequence for the field service engineer to investigate the hypothesized failures in order to minimize the time or cost required to accomplish the repair task. Previously, field service personnel would arrive at the customer site and choose which components to investigate based on past experience and service manuals. Using FTDOTS running on a portable computer, they can now enter a set of symptoms and get a list of possible failures ordered in an optimal test sequence to help them in their decisions. If facilities are available, the field engineer can connect the portable computer to the malfunctioning device for automated data gathering. FTDOTS is currently being applied to field service of medical test equipment. The techniques are flexible enough to use for many different types of devices. If a fault tree model of the equipment and information about component failure probabilities and isolation times or costs are available, a diagnostic knowledge base for that device can be developed easily.

Iverson, David L.↗
NASA NTRS1975

Clinical application of a light-pen computer system for quantitative angiography

The important features in a clinical system for quantitative angiography were examined. The human interface for data input, whether an electrostatic pen, sonic pen, or light-pen must be engineered to optimize the quality of margin definition. The computer programs which the technician uses for data entry and computation of ventriculographic measurements must be convenient to use on a routine basis in a laboratory performing multiple studies per day. The method used for magnification correction must be continuously monitored.

Alderman, E. L.↗
NASA NTRS1989

Dual-fuel versus single-fuel propulsion systems for AMLS applications

The results of using a computerized preliminary design system to integrate propulsion systems examined as a part of the Space Transportation Main Engine (STME) and Space Transportation Booster Engine (STBE) studies with reference vehicle concepts from the Advanced Manned Launch System (AMLS) study are presented. The major trade study presented is an analysis of the effect of using a single fuel for both stages of two-stage AMLS reference vehicles as opposed to using a separate fuel for the boosters. Other trade studies presented examine the effect of varying relevant engine parameters in an attempt to optimize the reference engines for use with the AMLS launch vehicles. In each propulsion trade discussed, special attention is given to the major vehicle performance and operational issues involved.

Stanley, Douglas O.↗
NASA NTRS1989

The space station tethered elevator system

The optimized conceptual engineering design of a space station tethered elevator is presented. The elevator is an unmanned mobile structure which operates on a ten kilometer tether spanning the distance between the Space Station and a tethered platform. Elevator capabilities include providing access to residual gravity levels, remote servicing, and transportation to any point along a tether. The potential uses, parameters, and evolution of the spacecraft design are discussed. Engineering development of the tethered elevator is the result of work conducted in the following areas: structural configurations; robotics, drive mechanisms; and power generation and transmission systems. The structural configuration of the elevator is presented. The structure supports, houses, and protects all systems on board the elevator. The implementation of robotics on board the elevator is discussed. Elevator robotics allow for the deployment, retrieval, and manipulation of tethered objects. Robotic manipulators also aid in hooking the elevator on a tether. Critical to the operation of the tethered elevator is the design of its drive mechanisms, which are discussed. Two drivers, located internal to the elevator, propel the vehicle along a tether. These modular components consist of endless toothed belts, shunt-wound motors, regenerative power braking, and computer controlled linear actuators. The designs of self-sufficient power generation and transmission systems are reviewed. Thorough research indicates all components of the elevator will operate under power provided by fuel cells. The fuel cell systems will power the vehicle at seven kilowatts continuously and twelve kilowatts maximally. A set of secondary fuel cells provides redundancy in the unlikely event of a primary system failure. Power storage exists in the form of Nickel-Hydrogen batteries capable of powering the elevator under maximum loads.

Anderson, Loren A.↗
NASA NTRS1990

Shielding requirements for the Space Station habitability modules

The design, analysis, development, and tests of the total meteoroid/debris protection system for the Space Station Freedom habitability modules, such as the habitation module, the laboratory module, and the node structures, are described. Design requirements are discussed along with development efforts, including a combination of hypervelocity testing and analyses. Computer hydrocode analysis of hypervelocity impact phenomena associated with Space Station habitability structures is covered and the use of optimization techniques, engineering models, and parametric analyses is assessed. Explosive rail gun development efforts and protective capability and damage tolerance of multilayer insulation due to meteoroid/debris impact are considered. It is concluded that anticipated changes in the debris environment definition and requirements will require rescoping the tests and analysis required to develop a protection system.

Avans, Sherman L.↗
NASA NTRS1990

Optimization of the propulsion cycles for advanced shuttles. II - Performance model methodology

In 1988 computer codes from NASA and DLR were combined to analyze and optimize rocket engines for advance launch vehicles. Further effort has addressed performance propulsion parameters such as chamber pressure, cycle selection (including mixed and tripropellant cycles), nozzle extension, and new technologies. Results of the study indicate that lower dry masses can be reached with the staged combustion cycle than with the gas-generator cycle, using oxygen/hydrogen at relatively high mixture ratio (7:1) and modest chamber pressure (220 bar). For low dry masses the staged combustion cycle is only excelled by the dual-expander cycle using hydrogen and propane as fuels. The emphasis here is to explain the procedure and boundary conditions used for the analysis and the variety of configurations treated, as well as to demonstrate the methods used by presenting some of the major results.

Manski, Detlef↗
NASA NTRS1993

An assessment of mission and configuration variations on multi-role fighter/attack aircraft concepts

This paper presents the results of a series of configuration studies conducted in connection with the NASA agility design study project. The purpose of these in-house studies was to develop a parametric data base of configuration concepts and resulting mission performances for a variety of notional fighter/attack missions. This data base will then be used to assess the impact of the imposition of agility requirements on these configurations. Three vehicle concepts were evaluated, and resulting vehicle sizes, weights, and mission performances were compared. Each configuration was then optimized for varying mission requirements and technology levels. It was found that small variations in mission requirements can have significant impact on the design choices. It was also found that optimization of engine cycle variables results in significant improvements in take-off gross weight and vehicle performance regardless of the concept being explored. Finally, results indicate that signature considerations such as internal vs. external weapons carriage can cause dramatic changes in vehicle size, weight, and mission performance.

Logan, Michael J.↗
NASA NTRS1989

Space Station tethered elevator system

The optimized conceptual engineering design of a space station tethered elevator is presented. The tethered elevator is an unmanned, mobile structure which operates on a ten-kilometer tether spanning the distance between Space Station Freedom and a platform. Its capabilities include providing access to residual gravity levels, remote servicing, and transportation to any point along a tether. The report discusses the potential uses, parameters, and evolution of the spacecraft design. Emphasis is placed on the elevator's structural configuration and three major subsystem designs. First, the design of elevator robotics used to aid in elevator operations and tethered experimentation is presented. Second, the design of drive mechanisms used to propel the vehicle is discussed. Third, the design of an onboard self-sufficient power generation and transmission system is addressed.

Haddock, Michael H.↗
NASA NTRS1995

An Electronic Workshop on the Performance Seeking Control and Propulsion Controlled Aircraft Results of the F-15 Highly Integrated Digital Electronic Control Flight Research Program

Flight research for the F-15 HIDEC (Highly Integrated Digital Electronic Control) program was completed at NASA Dryden Flight Research Center in the fall of 1993. The flight research conducted during the last two years of the HIDEC program included two principal experiments: (1) performance seeking control (PSC), an adaptive, real-time, on-board optimization of engine, inlet, and horizontal tail position on the F-15; and (2) propulsion controlled aircraft (PCA), an augmented flight control system developed for landings as well as up-and-away flight that used only engine thrust (flight controls locked) for flight control. In September 1994, the background details and results of the PSC and PCA experiments were presented in an electronic workshop, accessible through the Dryden World Wide Web (http://www.dfrc.nasa.gov/dryden.html) and as a compact disk.

Powers, Sheryll Goecke↗
NASA NTRS1997

Propulsion Flight Research at NASA Dryden From 1967 to 1997

From 1967 to 1997, pioneering propulsion flight research activities have been conceived and conducted at the NASA Dryden Flight Research Center. Many of these programs have been flown jointly with the United States Department of Defense, industry, or the Federal Aviation Administration. Propulsion research has been conducted on the XB-70, F-111 A, F-111E, YF-12, JetStar, B-720, MD-11, F-15, F- 104, Highly Maneuverable Aircraft Technology, F-14, F/A-18, SR-71, and the hypersonic X-15 airplanes. Research studies have included inlet dynamics and control, in-flight thrust computation, integrated propulsion controls, inlet and boattail drag, wind tunnel-to-flight comparisons, digital engine controls, advanced engine control optimization algorithms, acoustics, antimisting kerosene, in-flight lift and drag, throttle response criteria, and thrust-vectoring vanes. A computer-controlled thrust system has been developed to land the F-15 and MD-11 airplanes without using any of the normal flight controls. An F-15 airplane has flown tests of axisymmetric thrust-vectoring nozzles. A linear aerospike rocket experiment has been developed and tested on the SR-71 airplane. This paper discusses some of the more unique flight programs, the results, lessons learned, and their impact on current technology.

Burcham, Frank W., Jr.↗
NASA NTRS1999

Parallelization of Rocket Engine Simulator Software (P.R.E.S.S.)

Parallelization of Rocket Engine System Software (PRESS) project is part of a collaborative effort with Southern University at Baton Rouge (SUBR), University of West Florida (UWF), and Jackson State University (JSU). The project has started on October 19, 1995, and after a three-year period corresponding to project phases and fiscal-year funding by NASA Lewis Research Center (now Glenn Research Center), has ended on October 18, 1998. The one-year no-cost extension period was granted on June 7, 1998, until October 19, 1999. The aim of this one year no-cost extension period was to carry out further research to complete the work and lay the groundwork for subsequent research in the area of aerospace engine design optimization software tools. The previous progress for the research has been reported in great detail in respective interim and final research progress reports, seven of them, in all. While the purpose of this report is to be a final summary and an valuative view of the entire work since the first year funding, the following is a quick recap of the most important sections of the interim report dated April 30, 1999.

Cezzar, Ruknet↗
NASA NTRS2006

SpaceWire Protocol ID: What Does It Mean To You?

Spacewire is becoming a popular solution for satellite high-speed data buses because it is a simple standard that provides great flexibility for a wide range of system requirements. It is simple in packet format and protocol, allowing users to easily tailor their implementation for their specific application. Some of the attractive aspects of Spacewire that make it easy to implement also make it hard for future reuse. Protocol reuse is difficult because Spacewire does not have a defined mechanism to communicate with the higher layers of the protocol stack. This has forced users of Spacewire to define unique packet formats and define how these packets are to be processed. Each mission writes their own Interface Control Document (ICD) and tailors Spacewire for their specific requirements making reuse difficult. Part of the reason for this habit may be because engineers typically optimize designs for their own requirements in the absence of a standard. This is an inefficient use of project resources and costs more to develop missions. A new packet format for Spacewire has been defined as a solution for this problem. This new packet format is a compliment to the Spacewire standard that will support protocol development upon Spacewire. The new packet definition does not replace the current packet structure, i.e., does not make the standard obsolete, but merely extends the standard for those who want to develop protocols over Spacewire. The Spacewire packet is defined with the first part being the Destination Address, which may be one or more bytes. This is followed by the packet cargo, which is user defined. The cargo is truncated with an End-Of-Packet (EOP) marker. This packet structure offers low packet overhead and allows the user to define how the contents are to be formatted. It also provides for many different addressing schemes, which provide flexibility in the system. This packet flexibility is typically an attractive part of the Spacewire. The new extended packet format adds one new field to the packet that greatly enhances the capability of Spacewire. This new field called the Protocol Identifier (ID) is used to identify the packet contents and the associated processing for the packet. This feature along with the restriction in the packet format that uses the Protocol ID, allows a deterministic method of decoding packets that was not before possible. The first part of the packet is still the Destination Address, which still conforms to the original standard but with one restriction. The restriction is that the first byte seen at the destination by the user needs to be a logical address, independent of the addressing scheme used. The second field is defined as the Protocol ID, which is usually one byte in length. The packet cargo (user defined) follows the Protocol ID. After the packet cargo is the EOP, which defines the end of packet. The value of the Protocol ID is assigned by the Spacewire working group and the protocol description published for others to use. The development of Protocols for Spacewire is currently the area of greatest activity by the Spacewire working group. The first protocol definition by the working group has been completed and is now in the process of formal standardization. There are many other protocols in development for missions that have not yet received formal Protocol ID assignment, but even if the protocols are not formally assigned a value, this effort will provide synergism for future developments.

Rakow, Glenn↗