Search NASA⌕ Search

SEARCH · Search NASA

Results for “engineering”

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 577 records · Page 32
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Phased Array Noise Source Localization Measurements Made on a Williams International FJ44 Engine

A 48-microphone planar phased array system was used to acquire noise source localization data on a full-scale Williams International FJ44 turbofan engine. Data were acquired with the array at three different locations relative to the engine, two on the side and one in front of the engine. At the two side locations the planar microphone array was parallel to the engine centerline; at the front location the array was perpendicular to the engine centerline. At each of the three locations, data were acquired at eleven different engine operating conditions ranging from engine idle to maximum (take off) speed. Data obtained with the array off to the side of the engine were spatially filtered to separate the inlet and nozzle noise. Tones occurring in the inlet and nozzle spectra were traced to the low and high speed spools within the engine. The phased array data indicate that the Inflow Control Device (ICD) used during this test was not acoustically transparent; instead, some of the noise emanating from the inlet reflected off of the inlet lip of the ICD. This reflection is a source of error for far field noise measurements made during the test. The data also indicate that a total temperature rake in the inlet of the engine is a source of fan noise.

Podboy, Gary G.↗
NASA NTRS2010

Testing for the J-2X Upper Stage Engine

NASA selected the J-2X Upper Stage Engine in 2006 to power the upper stages of the Ares I crew launch vehicle and the Ares V cargo launch vehicle. Based on the proven Saturn J-2 engine, this new engine will provide 294,000 pounds of thrust and a specific impulse of 448 seconds, making it the most efficient gas generator cycle engine in history. The engine's guiding philosophy emerged from the Exploration Systems Architecture Study (ESAS) in 2005. Goals established then called for vehicles and components based, where feasible, on proven hardware from the Space Shuttle, commercial, and other programs, to perform the mission and provide an order of magnitude greater safety. Since that time, the team has made unprecedented progress. Ahead of the other elements of the Constellation Program architecture, the team has progressed through System Requirements Review (SRR), System Design Review (SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR). As of February 2010, more than 100,000 development engine parts have been ordered and more than 18,000 delivered. Approximately 1,300 of more than 1,600 engine drawings were released for manufacturing. A major factor in the J-2X development approach to this point is testing operations of heritage J-2 engine hardware and new J-2X components to understand heritage performance, validate computer modeling of development components, mitigate risk early in development, and inform design trades. This testing has been performed both by NASA and its J-2X prime contractor, Pratt & Whitney Rocketdyne (PWR). This body of work increases the likelihood of success as the team prepares for testing the J-2X powerpack and first development engine in calendar 2011. This paper will provide highlights of J-2X testing operations, engine test facilities, development hardware, and plans.

Buzzell, James C.↗
NASA NTRS2010

From Paper to Production: An Update on NASA's Upper Stage Engine for Exploration

In 2006, NASA selected an evolved variant of the proven Saturn/Apollo J-2 upper stage engine to power the Ares I crew launch vehicle upper stage and the Ares V cargo launch vehicle Earth departure stage (EDS) for the Constellation Program. Any design changes needed by the new engine would be based where possible on proven hardware from the Space Shuttle, commercial launchers, and other programs. In addition to the thrust and efficiency requirements needed for the Constellation reference missions, it would be an order of magnitude safer than past engines. It required the J-2X government/industry team to develop the highest performance engine of its type in history and develop it for use in two vehicles for two different missions. In the attempt to achieve these goals in the past five years, the Upper Stage Engine team has made significant progress, successfully passing System Requirements Review (SRR), System Design Review (SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR). As of spring 2010, more than 100,000 experimental and development engine parts have been completed or are in various stages of manufacture. Approximately 1,300 of more than 1,600 engine drawings have been released for manufacturing. This progress has been due to a combination of factors: the heritage hardware starting point, advanced computer analysis, and early heritage and development component testing to understand performance, validate computer modeling, and inform design trades. This work will increase the odds of success as engine team prepares for powerpack and development engine hot fire testing in calendar 2011. This paper will provide an overview of the engine development program and progress to date.

Kynard, Mike↗
NASA NTRS2010

The History and Promise of Combined Cycle Engines for Access to Space Applications

For the summer of 2010, I have been working in the Aerodynamics and Propulsion Branch at NASA Dryden Flight Research Center studying combined-cycle engines, a high speed propulsion concept. Combined cycle engines integrate multiple propulsion systems into a single engine capable of running in multiple modes. These different modes allow the engine to be extremely versatile and efficient in varied flight conditions. The two most common types of combined cycle engines are Rocket-Based Combined Cycle (RBCC) and Turbine Based Combined Cycle (TBCC). The RBCC essentially combines a rocket and ramjet engine, while the TBCC integrates a turbojet and ramjet1. These two engines are able to switch between different propulsion modes to achieve maximum performance. Extensive conceptual and ground test studies of RBCC engines have been undertaken; however, an RBCC engine has never, to my knowledge, been demonstrated in flight. RBCC engines are of particular interest because they could potentially power a reusable launch vehicle (RLV) into space. The TBCC has been flight tested and shown to be effective at reaching supersonic speeds, most notably in the SR-71 Blackbird2.

Clark, Casie↗
NASA NTRS2011

Optimal Tuner Selection for Kalman-Filter-Based Aircraft Engine Performance Estimation

An emerging approach in the field of aircraft engine controls and system health management is the inclusion of real-time, onboard models for the inflight estimation of engine performance variations. This technology, typically based on Kalman-filter concepts, enables the estimation of unmeasured engine performance parameters that can be directly utilized by controls, prognostics, and health-management applications. A challenge that complicates this practice is the fact that an aircraft engine s performance is affected by its level of degradation, generally described in terms of unmeasurable health parameters such as efficiencies and flow capacities related to each major engine module. Through Kalman-filter-based estimation techniques, the level of engine performance degradation can be estimated, given that there are at least as many sensors as health parameters to be estimated. However, in an aircraft engine, the number of sensors available is typically less than the number of health parameters, presenting an under-determined estimation problem. A common approach to address this shortcoming is to estimate a subset of the health parameters, referred to as model tuning parameters. The problem/objective is to optimally select the model tuning parameters to minimize Kalman-filterbased estimation error. A tuner selection technique has been developed that specifically addresses the under-determined estimation problem, where there are more unknown parameters than available sensor measurements. A systematic approach is applied to produce a model tuning parameter vector of appropriate dimension to enable estimation by a Kalman filter, while minimizing the estimation error in the parameters of interest. Tuning parameter selection is performed using a multi-variable iterative search routine that seeks to minimize the theoretical mean-squared estimation error of the Kalman filter. This approach can significantly reduce the error in onboard aircraft engine parameter estimation applications such as model-based diagnostic, controls, and life usage calculations. The advantage of the innovation is the significant reduction in estimation errors that it can provide relative to the conventional approach of selecting a subset of health parameters to serve as the model tuning parameter vector. Because this technique needs only to be performed during the system design process, it places no additional computation burden on the onboard Kalman filter implementation. The technique has been developed for aircraft engine onboard estimation applications, as this application typically presents an under-determined estimation problem. However, this generic technique could be applied to other industries using gas turbine engine technology.

Simon, Donald L.↗
NASA NTRS2011

Space Shuttle Main Engine - The Relentless Pursuit of Improvement

The Space Shuttle Main Engine (SSME) is the only reusable large liquid rocket engine ever developed. The specific impulse delivered by the staged combustion cycle, substantially higher than previous rocket engines, minimized volume and weight for the integrated vehicle. The dual pre-burner configuration permitted precise mixture ratio and thrust control while the fully redundant controller and avionics provided a very high degree of system reliability and health diagnosis. The main engine controller design was the first rocket engine application to incorporate digital processing. The engine was required to operate at a high chamber pressure to minimize engine volume and weight. Power level throttling was required to minimize structural loads on the vehicle early in flight and acceleration levels on the crew late in ascent. Fatigue capability, strength, ease of assembly and disassembly, inspectability, and materials compatibility were all major considerations in achieving a fully reusable design. During the multi-decade program the design evolved substantially using a series of block upgrades. A number of materials and manufacturing challenges were encountered throughout SSME s history. Significant development was required for the final configuration of the high pressure turbopumps. Fracture control was implemented to assess life limits of critical materials and components. Survival in the hydrogen environment required assessment of hydrogen embrittlement. Instrumentation systems were a challenge due to the harsh thermal and dynamic environments within the engine. Extensive inspection procedures were developed to assess the engine components between flights. The Space Shuttle Main Engine achieved a remarkable flight performance record. All flights were successful with only one mission requiring an ascent abort condition, which still resulted in an acceptable orbit and mission. This was achieved in large part via extensive ground testing to fully characterize performance and to establish acceptable life limits. During the program over a million seconds of accumulated test and flight time was achieved. Post flight inspection and assessment was a key part of assuring proper performance of the flight hardware. By the end of the program the predicted reliability had improved by a factor of four. These unique challenges, evolution of the design, and the resulting reliability will be discussed in this paper.

VanHooser, Katherine P.↗
NASA NTRS2012

The Effect of Faster Engine Response on the Lateral Directional Control of a Damaged Aircraft

The integration of flight control and propulsion control has been a much discussed topic, especially for emergencies where the engines may be able to help stabilize and safely land a damaged aircraft. Previous research has shown that for the engines to be effective as flight control actuators, the response time to throttle commands must be improved. Other work has developed control modes that accept a higher risk of engine failure in exchange for improved engine response during an emergency. In this effort, a nonlinear engine model (the Commercial Modular Aero-Propulsion System Simulation 40k) has been integrated with a nonlinear airframe model (the Generic Transport Model) in order to evaluate the use of enhanced-response engines as alternative yaw rate control effectors. Tests of disturbance rejection and command tracking were used to determine the impact of the engines on the aircraft's dynamical behavior. Three engine control enhancements that improve the response time of the engine were implemented and tested in the integrated simulation. The enhancements were shown to increase the engine s effectiveness as a yaw rate control effector when used in an automatic feedback loop. The improvement is highly dependent upon flight condition; the airframe behavior is markedly improved at low altitude, low speed conditions, and relatively unchanged at high altitude, high speed.

May, Ryan D.↗
NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗
NASA NTRS2014

Interdisciplinary Interactions During R&D and Early Design of Large Engineered Systems

Designing Large-Scale Complex Engineered Systems (LaCES) such as aircraft and submarines requires the input of thousands of engineers and scientists whose work is proximate in neither time nor space. Comprehensive knowledge of the system is dispersed among specialists whose expertise is in typically one system component or discipline. This study examined the interactive work practices among such specialists seeking to improve engineering practice through a rigorous and theoretical understanding of current practice. This research explored current interdisciplinary practices and perspectives during R&D and early LaCES design and identified why these practices and perspectives prevail and persist. The research design consisted of a three-fold, integrative approach that combined an open-ended survey, semi-structured interviews, and ethnography. Significant empirical data from experienced engineers and scientists in a large engineering organization were obtained and integrated with theories from organization science and engineering. Qualitative analysis was used to obtain a holistic, contextualized understanding. The over-arching finding is that issues related to cognition, organization, and social interrelations mostly dominate interactions across disciplines. Engineering issues, such as the integration of hardware or physics-based models, are not as significant. For example, organization culture is an important underlying factor that guided researchers more toward individual sovereignty over cross-disciplinarity. The organization structure and the engineered system architecture also serve as constraints to the engineering work. Many differences in work practices were observed, including frequency and depth of interactions, definition or co-construction of requirements, clarity or creation of the system architecture, work group proximity, and cognitive challenges. Practitioners are often unaware of these differences resulting in confusion and incorrect assumptions regarding work expectations. Cognitively, the enactment and coconstruction of knowledge are the fundamental tasks of the interdisciplinary interactions. Distributed and collective cognition represent most of the efforts. Argument, ignorance, learning, and creativity are interrelated aspects of the interactions that cause discomfort but yield benefits such as problem mitigation, broader understanding, and improved system design and performance. The quality and quantity of social interrelations are central to all work across disciplines with reciprocity, respectful engagement, and heedful interrelations being significant to the effectiveness of the engineering and scientific work.

McGowan, Anna-Maria Rivas↗
NASA NTRS2014

Combustion Stability Characteristics of the Project Morpheus Liquid Oxygen/Liquid Methane Main Engine

The Project Morpheus liquid oxygen (LOX) / liquid methane rocket engines demonstrated acousticcoupled combustion instabilities during sea‐level ground‐based testing at the NASA Johnson Space Center (JSC) and Stennis Space Center (SSC). High‐amplitude, 1T, 1R, 1T1R (and higher order) modes appear to be triggered by injector conditions. The instability occurred during the Morpheus‐specific engine ignition/start sequence, and did demonstrate the capability to propagate into mainstage. However, the instability was never observed to initiate during mainstage, even at low power levels. The Morpheus main engine is a JSC‐designed ~5,000 lbf‐thrust, 4:1 throttling, pressure‐fed cryogenic engine using an impinging element injector design. Two different engine designs, named HD4 and HD5, and two different builds of the HD4 engine all demonstrated similar instability characteristics. Through the analysis of more than 200 hot fire tests on the Morpheus vehicle and SSC test stand, a relationship between ignition stability and injector/chamber pressure was developed. The instability has the distinct characteristic of initiating at high relative injection pressure drop (dP) at low chamber pressure (Pc); i.e., instabilities initiated at high dP/Pc at low Pc during the start sequence. The high dP/Pc during start results during the injector /chamber chill‐in, and is enhanced by hydraulic flip in the injector orifice elements. Because of the fixed mixture ratio of the existing engine design (the main valves share a common actuator), it is not currently possible to determine if LOX or methane injector dP/Pc were individual contributors (i.e., LOX and methane dP/Pc typically trend in the same direction within a given test). The instability demonstrated initiation characteristic of starting at or shortly after methane injector chillin. Colder methane (e.g., sub‐cooled) at the injector inlet prior to engine start was much more likely to result in an instability. A secondary effect of LOX sub‐cooling was also possibly observed; greater LOX sub‐ cooling improved stability. Some tests demonstrated a low‐amplitude 1L‐1T instability prior to LOX injector chill‐in. The Morpheus main engine also demonstrated chug instabilities during some engine shutdown sequences on the flight vehicle and SSC test stand. The chug instability was also infrequently observed during the startup sequence. The chug instabilities predictably initiated at low dP/Pc at low Pc. The chug instabilities were always self‐limiting; startup chug instabilities terminated during throttle‐up and shutdown chug instabilities decayed by shutdown termination.

Melcher, J. C.↗
NASA NTRS2014

Studies of Fission Fragment Rocket Engine Propelled Spacecraft

The NASA Office of Chief Technologist has funded from FY11 through FY14 successive studies of the physics, design, and spacecraft integration of a Fission Fragment Rocket Engine (FFRE) that directly converts the momentum of fission fragments continuously into spacecraft momentum at a theoretical specific impulse above one million seconds. While others have promised future propulsion advances if only you have the patience, the FFRE requires no waiting, no advances in physics and no advances in manufacturing processes. Such an engine unequivocally can create a new era of space exploration that can change spacecraft operation. The NIAC (NASA Institute for Advanced Concepts) Program Phase 1 study of FY11 first investigated how the revolutionary FFRE technology could be integrated into an advanced spacecraft. The FFRE combines existent technologies of low density fissioning dust trapped electrostatically and high field strength superconducting magnets for beam management. By organizing the nuclear core material to permit sufficient mean free path for escape of the fission fragments and by collimating the beam, this study showed the FFRE could convert nuclear power to thrust directly and efficiently at a delivered specific impulse of 527,000 seconds. The FY13 study showed that, without increasing the reactor power, adding a neutral gas to the fission fragment beam significantly increased the FFRE thrust through in a manner analogous to a jet engine afterburner. This frictional interaction of gas and beam resulted in an engine that continuously produced 1000 pound force of thrust at a delivered impulse of 32,000 seconds, thereby reducing the currently studied DRM 5 round trip mission to Mars from 3 years to 260 days. By decreasing the gas addition, this same engine can be tailored for much lower thrust at much higher impulse to match missions to more distant destinations. These studies created host spacecraft concepts configured for manned round trip journeys. While the vehicles are very large, they are primarily made up of a habitat payload on one end, the engine on the opposite end and a connecting spine containing radiator acreage needed to reject the heat of this powerful, but inefficient engine. These studies concluded that the engine and spacecraft are within today's technology, could be built, tested, launched on several SLS launchers, integrated, checked out, maintained at an in-space LEO base, and operated for decades just as Caribbean cruise ships operate today. The nuclear issues were found to be far less daunting that [than for] current nuclear engines. The FFRE produces very small amounts of radioactive efflux compared to their impulse, easily contained in an evacuated "bore-hole" test site. The engine poses no launch risk since it is simply a structure containing no fissionable material. The nuclear fuel is carried to orbit in containers highly crash-proofed for launch accidents from which it, in a liquid medium, is injected into the FFRE. The radioactive exhaust, with a velocity above 300 kilometers per second rapidly leaves the solar system.

Werka, Robert O.↗
NASA NTRS2016

Preliminary Results From a Heavily Instrumented Engine Ice Crystal Icing Test in a Ground Based Altitude Test Facility

Preliminary results from the heavily instrumented ALF502R-5 engine test conducted in the NASA Glenn Research Center Propulsion Systems Laboratory are discussed. The effects of ice crystal icing on a full scale engine is examined and documented. This same model engine, serial number LF01, was used during the inaugural icing test in the Propulsion Systems Laboratory facility. The uncommanded reduction of thrust (rollback) events experienced by this engine in flight were simulated in the facility. Limited instrumentation was used to detect icing on the LF01 engine. Metal temperatures on the exit guide vanes and outer shroud and the load measurement were the only indicators of ice formation. The current study features a similar engine, serial number LF11, which is instrumented to characterize the cloud entering the engine, detect/characterize ice accretion, and visualize the ice accretion in the region of interest. Data were acquired at key LF01 test points and additional points that explored: icing threshold regions, low altitude, high altitude, spinner heat effects, and the influence of varying the facility and engine parameters. For each condition of interest, data were obtained from some selected variations of ice particle median volumetric diameter, total water content, fan speed, and ambient temperature. For several cases the NASA in-house engine icing risk assessment code was used to find conditions that would lead to a rollback event. This study further helped NASA develop necessary icing diagnostic instrumentation, expand the capabilities of the Propulsion Systems Laboratory, and generate a dataset that will be used to develop and validate in-house icing prediction and risk mitigation computational tools. The ice accretion on the outer shroud region was acquired by internal video cameras. The heavily instrumented engine showed good repeatability of icing responses when compared to the key LF01 test points and during day-to-day operation. Other noticeable observations are presented.

Enigine Icing↗
NASA NTRS2016

Preliminary Results From a Heavily Instrumented Engine Ice Crystal Icing Test in a Ground Based Altitude Test Facility

Preliminary results from the heavily instrumented ALF502R-5 engine test conducted in the NASA Glenn Research Center Propulsion Systems Laboratory are discussed. The effects of ice crystal icing on a full scale engine is examined and documented. This same model engine, serial number LF01, was used during the inaugural icing test in the Propulsion Systems Laboratory facility. The uncommanded reduction of thrust (rollback) events experienced by this engine in flight were simulated in the facility. Limited instrumentation was used to detect icing on the LF01 engine. Metal temperatures on the exit guide vanes and outer shroud and the load measurement were the only indicators of ice formation. The current study features a similar engine, serial number LF11, which is instrumented to characterize the cloud entering the engine, detect/ characterize ice accretion, and visualize the ice accretion in the region of interest. Data were acquired at key LF01 test points and additional points that explored: icing threshold regions, low altitude, high altitude, spinner heat effects, and the influence of varying the facility and engine parameters. For each condition of interest, data were obtained from some selected variations of ice particle median volumetric diameter, total water content, fan speed, and ambient temperature. For several cases the NASA in-house engine icing risk assessment code was used to find conditions that would lead to a rollback event. This study further helped NASA develop necessary icing diagnostic instrumentation, expand the capabilities of the Propulsion Systems Laboratory, and generate a dataset that will be used to develop and validate in-house icing prediction and risk mitigation computational tools. The ice accretion on the outer shroud region was acquired by internal video cameras. The heavily instrumented engine showed good repeatability of icing responses when compared to the key LF01 test points and during day-to-day operation. Other noticeable observations are presented.

turbomachinery↗
NASA NTRS2016

Advanced Control Considerations for Turbofan Engine Design

This paper covers the application of a model-based engine control (MBEC) methodology featuring a self tuning on-board model for an aircraft turbofan engine simulation. The nonlinear engine model is capable of modeling realistic engine performance, allowing for a verification of the advanced control methodology over a wide range of operating points and life cycle conditions. The on-board model is a piece-wise linear model derived from the nonlinear engine model and updated using an optimal tuner Kalman Filter estimation routine, which enables the on-board model to self-tune to account for engine performance variations. MBEC is used here to show how advanced control architectures can improve efficiency during the design phase of a turbofan engine by reducing conservative operability margins. The operability margins that can be reduced, such as stall margin, can expand the engine design space and offer potential for efficiency improvements. Application of MBEC architecture to a nonlinear engine simulation is shown to reduce the thrust specific fuel consumption by approximately 1% over the baseline design, while maintaining safe operation of the engine across the flight envelope.

control↗
NASA NTRS2019

Using Machine Learning to Predict Core Sizes of High-Efficiency Turbofan Engines

With the rise in big data and analytics, machine learning is transforming many industries. It is being increasingly employed to solve a wide range of complex problems, producing autonomous systems that support human decision-making. For the aircraft engine industry, machine learning of historical and existing engine data could provide insights that help drive for better engine design. This work explored the application of machine learning to engine preliminary design. Engine core-size prediction was chosen for the first study because of its relative simplicity in terms of number of input variables required (only three). Specifically, machine-learning predictive tools were developed for turbofan engine core-size prediction, using publicly available data of two hundred manufactured engines and engines that were studied previously in NASA aeronautics projects. The prediction results of these models show that, by bringing together big data, robust machine-learning algorithms and automation, a machine learning-based predictive model can be an effective tool for turbofan engine core-size prediction. The promising results of this first study paves the way for further exploration of the use of machine learning for aircraft engine preliminary design.

Tong, Michael T.↗
NASA NTRS2019

Using Machine Learning to Predict Core Sizes of High-Efficiency Turbofan Engines

With the rise in big data and analytics, machine learning is transforming many industries. It is being increasingly employed to solve a wide range of complex problems, producing autonomous systems that support human decision-making. For the aircraft engine industry, machine learning of historical and existing engine data could provide insights that help drive for better engine design. This work explored the application of machine learning to engine preliminary design. Engine core-size prediction was chosen for the first study because of its relative simplicity in terms of number of input variables required (only three). Specifically, machine-learning predictive tools were developed for turbofan engine core-size prediction, using publicly available data of two hundred manufactured engines and engines that were studied previously in NASA aeronautics projects. The prediction results of these models show that, by bringing together big data, robust machine-learning algorithms and data science, a machine learning-based predictive model can be an effective tool for turbofan engine core-size prediction. The promising results of this first study paves the way for further exploration of the use of machine learning for aircraft engine preliminary design.

Core Size↗
NASA NTRSDate not supplied

A New Concurrent Engineering Tool for the New Mission Design Center at NASA Ames Research Center

The NASA Ames Mission Design Center (MDC) has undergone a significant transformation process in recent years, culminating in becoming a true Concurrent Engineering Center. The underlying goal of this transformation is to better serve the Ames PI community in a cost-effective and rapidly-responsive way, providing quality products pivotal to the decision-making proposal strategy of our center. The four pillars of the change focus on four areas: personnel, physical places, tools, and training. Personnel: the MDC switched from using a dedicated pool of engineers—mostly entry-level career—for a matrixed approach with more experienced Subject Matter Experts, usually involved in spaceflight projects. These SMEs get detailed to the MDC for the duration of the study on a part-time or full-time basis. Physical places: The physical aspect pertains mostly to the layout of the new Engineering building and the dedicated concurrent engineering layout to foster collaboration. The current plan includes a dedicated space for concurrent engineering sessions as well as dedicated project rooms for concept studies. Tool: the MDC team is developing a new in-house concurrent engineering tool to facilitate concurrent engineering sessions. The team leveraged the many lessons learned and insight gained from using the current concurrent engineering tool, in use since 2007. SMEs have been involved throughout its design and development, ensuring accuracy and providing validity to the implementation approach. This new tool is database-driven and allows a team to work concurrently on the same model of a mission concept. “Workspaces” are provided for each of the traditional spacecraft mission design disciplines, including cost accounting and systems engineering. There are multiple tiers of fidelity available within each workspace, which can be completed parametrically or independently from the other disciplines as needed or synchronously with the other disciplines. A “commit” step synchronizes a workspace with the mission database and identifies any potential conflicts, along with the user who entered the conflicting data. A Mission Summary workspace enables a Study Lead to run an effective CE session, displaying key graphics, workspace status information, and technical and monetary budget information. This new CE tool will be undergoing Beta Testing with its primary user base and a limited Parts database in the summer of 2020. The team plans to release the first fully operational version in December 2020. Training: working in early concept development and maturation for a space mission requires a unique mindset and being comfortable with uncertainties in an environment where requirements are not yet fully developed, and where changes and trade-offs happen at a high tempo. The MDC started a weekly training program to ensure a common knowledge base on how do develop and mature early concept studies, as well as how to operate in a concurrent engineering environment. In conclusion, the MDC transformation will provide the overall PI community focused on cost-effective small satellite scientific missions with a powerful tool to address and mature early concepts more effectively and efficiently.

David Mauro↗
NASA NTRS2020

Assisted Authoring of Model-Based Systems Engineering Documents

In systems engineering practices system design and analysis have historically been performed using a document-centric approach where stakeholders produce a number of documents that represent their views on a system under development. Given the ad-hoc, disparate, and informal nature of natural language documents, these views become quickly inconsistent. Rigor in engineering work is also lost in the transition from model based engineering design and analysis to engineering documents. Once the documents are delivered, the engineering portion of the work is disconnected. In the Open Model Based Engineering Environment (OpenMBEE), Cross-References (aka transclusions) synthesize data for engineering when the information is not simply hyperlinked, but referenced in place in a document, upgrading a document-based process with model-based engineering technology. Those Cross-References are nowadays partially created manually, putting a burden on the engineer who is authoring the document.This paper presents an approach which can assist the engineer by providing machine-generated suggestions for Cross-References using language processing, graph analysis, and clustering technologies on model data managed by the OpenMBEE infrastructure.

Gomes, Ivan↗