SEARCH · Search NASA

Results for “ENGINES - PERFORMANCE”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 343 records · Page 19

All sources NASA NTRS DOE OSTI

NASA NTRS2004

Hybrid Automotive Engine Using Ethanol-Burning Miller Cycle

A proposed hybrid (internal-combustion/ electric) automotive engine system would include as its internal-combustion subsystem, a modified Miller-cycle engine with regenerative air preheating and with autoignition like that of a Diesel engine. The fuel would be ethanol and would be burned lean to ensure complete combustion. Although the proposed engine would have a relatively low power-to-weight ratio compared to most present engines, this would not be the problem encountered if this engine were used in a non-hybrid system since hybrid systems require significantly lower power and thus smaller engines than purely internal-combustion-engine-driven vehicles. The disadvantage would be offset by the advantages of high fuel efficiency, low emission of nitrogen oxides and particulate pollutants, and the fact that ethanol is a renewable fuel. The original Miller-cycle engine, named after its inventor, was patented in the 1940s and is the basis of engines used in some modern automobiles, but is not widely known. In somewhat oversimplified terms, the main difference between a Miller-cycle engine and a common (Otto-cycle) automobile engine is that the Miller-cycle engine has a longer expansion stroke while retaining the shorter compression stroke. This is accomplished by leaving the intake valve open for part of the compression stroke, whereas in the Otto cycle engine, the intake valve is kept closed during the entire compression stroke. This greater expansion ratio makes it possible to extract more energy from the combustion process without expending more energy for compression. The net result is greater efficiency. In the proposed engine, the regenerative preheating would be effected by running the intake air through a heat exchanger connected to the engine block. The regenerative preheating would offer two advantages: It would ensure reliable autoignition during operation at low ambient temperature and would help to cool the engine, thereby reducing the remainder of the power needed for cooling and thereby further contributing to efficiency. An electrical resistance air preheater might be needed to ensure autoignition at startup and during a short warmup period. Because of the autoignition, the engine could operate without either spark plugs or glow plugs. Ethanol burns relatively cleanly and has been used as a motor fuel since the invention of internal-combustion engines. However, the energy content of ethanol per unit weight of ethanol is less than that of Diesel fuel or gasoline, and ethanol has a higher heat of vaporization. Because the Miller cycle offers an efficiency close to that of the Diesel cycle, burning ethanol in a Miller-cycle engine gives about as much usable output energy per unit volume of fuel as does burning gasoline in a conventional gasoline automotive engine. Because of the combination of preheating, running lean, and the use of ethyl alcohol, the proposed engine would generate less power per unit volume than does a conventional automotive gasoline engine. Consequently, for a given power level, the main body of the proposed engine would be bulkier. However, because little or no exhaust cleanup would be needed, the increase in bulk of the engine could be partially offset by the decrease in bulk of the exhaust system. The regenerative preheating also greatly reduces the external engine cooling requirement, and would translate to reduced engine bulk. It may even be possible to accomplish the remaining cooling of the engine by use of air only, eliminating the bulk and power consumption of a water cooling system. The combination of a Miller-cycle engine with regenerative air preheating, ethyl alcohol fuel, and hybrid operation could result in an automotive engine system that satisfies the need for a low pollution, high efficiency, and simple engine with a totally renewable fuel.

Weinstein, Leonard↗

NASA NTRS2005

Key Reliability Drivers of Liquid Propulsion Engines and A Reliability Model for Sensitivity Analysis

This paper is to address the in-flight reliability of a liquid propulsion engine system for a launch vehicle. We first establish a comprehensive list of system and sub-system reliability drivers for any liquid propulsion engine system. We then build a reliability model to parametrically analyze the impact of some reliability parameters. We present sensitivity analysis results for a selected subset of the key reliability drivers using the model. Reliability drivers identified include: number of engines for the liquid propulsion stage, single engine total reliability, engine operation duration, engine thrust size, reusability, engine de-rating or up-rating, engine-out design (including engine-out switching reliability, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction), propellant specific hazards, engine start and cutoff transient hazards, engine combustion cycles, vehicle and engine interface and interaction hazards, engine health management system, engine modification, engine ground start hold down with launch commit criteria, engine altitude start (1 in. start), Multiple altitude restart (less than 1 restart), component, subsystem and system design, manufacturing/ground operation support/pre and post flight check outs and inspection, extensiveness of the development program. We present some sensitivity analysis results for the following subset of the drivers: number of engines for the propulsion stage, single engine total reliability, engine operation duration, engine de-rating or up-rating requirements, engine-out design, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction, and engine health management system implementation (basic redlines and more advanced health management systems).

Huang, Zhao-Feng↗

NASA NTRS1995

Research project for increasing pool of minority engineers

The Tennessee State University (TSU) Research Project for Increasing the Pool of Minority Engineers is designed to develop engineers who have academic and research experiences in technical areas of interest to NASA. These engineers will also have some degree of familiarity with NASA Lewis Research Center as a result of interaction with Lewis engineers, field trips and internships at Lewis. The Research Project has four components, which are: (1) Minority Introduction to Engineering (MITE), a high school precollege program, (2) engineering and technology previews, (3) the NASA LeRC Scholars program which includes scholarships and summer internships, and (4) undergraduate research experiences on NASA sponsored research. MITE is a two-week summer engineering camp designed to introduce minority high school students to engineering by exposing them to: (1) engineering role models (engineering students and NASA engineer), (2) field trips to engineering firms, (3) in addition to introducing youth to the language of the engineer (i.e., science, mathematics, technical writing, computers, and the engineering laboratory). Three MITE camps are held on the campus of TSU with an average of 40 participants. MITE has grown from 25 participants at its inception in 1990 to 118 participants in 1994 with participants from 17 states, including the District of Columbia, and 51 percent of the participants were female. Over the four-year period, 77 percent of the seniors who participated in MITE have gone to college, while 53 percent of those seniors in college are majoring in science, engineering or mathematics (SEM). This first Engineering and Technology Previews held in 1993 brought 23 youths from Cleveland, Ohio to TSU for a two-day preview of engineering and college life. Two previews are scheduled for 1994-1995. The NASA LeRC Scholars program provides scholarships and summer internships for minority engineering students majoring in electrical or mechanical engineering. Presently six (6) engineering students are in the Scholars program. The average GPA for the scholars is 3.239. Each scholar must maintain a minimum GPA of 3.000/4.000. NASA LeRC Fred Higgs has been awarded a GEM Fellowship. In addition, he will be presenting a paper entitled 'Design of Helical Spring Using Probabilistic Design Methodology' at the Middle Tennessee Section ASME Student Design Presentations in Nashville on March 23rd and at the National Conference on Undergraduate Research to be held at Union College, Schenectady, New York on April 20-22, 1995. Each of the scholars is working on one of the three NASA sponsored research projects in the college.

Rogers, Decatur B.↗

NASA NTRS2006

Engine Development Design Margins Briefing Charts

New engines experience durability problems after entering service. The most prevalent and costly is the hot section, particularly the high-pressure turbine. The origin of durability problems can be traced back to: 1) the basic aero-mechanical design systems, assumptions, and design margins used by the engine designers, 2) the available materials systems, and 3) to a large extent, aggressive marketing in a highly competitive environment that pushes engine components beyond the demonstrated capability of the basic technology available for the hardware designs. Unfortunately the user must operate the engine in the service environment in order to learn the actual thrust loading and the time at max effort take-off conditions used in service are needed to determine the hot section life. Several hundred thousand hours of operational service will be required before the demonstrated reliability of a fleet of engines or the design deficiencies of the engine hot section parts can be determined. Also, it may take three to four engine shop visits for heavy maintenance on the gas path hardware to establish cost effective build standards. Spare parts drive the oerator's engine maintenance costs but spare parts also makes lots of money for the engine manufacturer during the service life of an engine. Unless competition prevails for follow-on engine buys, there is really no motivation for an OEM to spend internal money to improve parts durability and reduce earnings derived from a lucrative spare parts business. If the hot section life is below design goals or promised values, the OEM migh argue that the engine is being operated beyond its basic design intent. On the other hand, the airframer and the operator will continue to remind the OEM that his engine was selected based on a lot of promises to deliver spec thrust with little impact on engine service life if higher thrust is used intermittently. In the end, a standoff prevails and nothing gets fixed. This briefing will propose ways to hold competing engine manufacturers more accountable for engine hot section design margins during the entire Engine Development process as well as provide tools to assess the design temperature margins in the hot section parts of Service Engines.

Bentz, Chuck↗

DOE OSTI2023

Cyber-Informed Engineering Implementation Guide

This Implementation Guide describes the principles of Cyber-Informed Engineering (CIE) and outlines questions that engineering teams should consider during each phase of a system’s lifecycle to effectively employ these principles. It describes what it means to engineer systems in a cyber-informed way, rather than offering a comprehensive, step-by-step process or procedure for CIE implementation. This guide complements—but does not replace—the application of cybersecurity standards or practices currently in place within an organization. Engineers and technicians that design critical energy infrastructure installations can use this Implementation Guide to integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. The guide is aimed at system or design engineers, rather than software engineers or operational cybersecurity practitioners. The engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system’s engineering design to diminish the severity of cyber attacks or digital technology failures. CIE expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences.

42 ENGINEERING↗

DOE OSTI2023

Cyber-Informed Engineering Implementation Guide: Version 1.0 [Slides]

This Implementation Guide describes the principles of Cyber-Informed Engineering (CIE) and outlines questions that engineering teams should consider during each phase of a system's lifecycle to effectively employ these principles. It describes what it means to engineer systems in a cyber-informed way, rather than offering a comprehensive, step-by-step process or procedure for CIE implementation. This guide complements - but does not replace - the application of cybersecurity standards or practices currently in place within an organization. Engineers and technicians that design critical energy infrastructure installations can use this Implementation Guide to integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. The guide is aimed at system or design engineers, rather than software engineers or operational cybersecurity practitioners. The engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system's engineering design to diminish the severity of cyber attacks or digital technology failures. CIE expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences.

24 POWER TRANSMISSION AND DISTRIBUTION↗

DOE OSTI2023

Cyber-Informed Engineering Principles: What’s in it for me?

CIE is an emerging method to integrate cybersecurity considerations into the conception, design, development, and operation of any physical system that has digital connectivity, monitoring, or control. CIE complements—but does not replace—the application of cybersecurity standards or practices currently in place within an organization. Rather, it expands cybersecurity decisions into the engineering space, not by asking engineers to become cyber experts, but by calling on engineers to apply engineering tools and make engineering decisions that improve cybersecurity outcomes. CIE examines the engineering consequences that a sophisticated cyber attacker could achieve, and drives engineering changes that may provide deterministic mitigations to limit or eliminate those consequences. Engineers and technicians that design critical energy infrastructure installations can integrate the 12 principles of CIE into each phase of the engineering lifecycle, from concept to retirement. These principles are aimed at system or design engineers, operators, and technicians, rather than software engineers or operational cybersecurity practitioners, because the engineers who design, build, operate, and maintain the physical infrastructure are best positioned to leverage a system’s engineering design to diminish the severity of cyber attacks or digital technology failures. This approach creates new opportunities for engineering teams—and not just cybersecurity teams—to secure the system using the physics and mechanics of engineering controls—not just digital monitoring and controls.

99 GENERAL AND MISCELLANEOUS↗

NASA NTRS2009

Rocketdyne - Lunar Ascent Engine

The ascent engine was the last one from the moon, and I want to focus on the idea of redundancy and teams in regard to the engine. By teams, I mean teamwork - not just within Rocketdyne. It was teamwork within Rocketdyne; it was teamwork within Grumman; it was teamwork within NASA. These were all important elements leading to the successful development of the lunar excursion module (LEM) engine. Communication, rapid response, and cooperation were all important. Another aspect that went into the development of the ascent engine was the integration of technology and of lessons learned. We pushed all the above, plus technology and lessons learned, into a program, and that led to a successful result. One of the things that I like to think about - again in retrospect - is how it is very "in" now to have integrated product and process teams. These are buzzwords for teamwork in all program phases. That s where you combine a lot of groups into a single organization to get a job done. The ascent engine program epitomized that kind of integration and focus, and because this was the mid- to late-1960s; this was new ground for Rocketdyne, Grumman, and NASA. Redundancy was really a major hallmark of the Apollo Program. Everything was redundant. Once you got the rocket going, you could even lose one of the big F-1 engines, and it would still make it to orbit. And once the first stage separated from the rest of the vehicle, the second stage could do without an engine and still make a mission. This redundancy was demonstrated when an early Apollo launch shut down a J-2 second-stage engine. Actually, they shut down two J-2 engines on that flight. Even the third stage, with its single J-2 engine, was backed up because the first two stages could toss it into a recoverable orbit. If the third stage didn't work, you were circling the earth, and you had time to recover the command module and crew. Remember how on the Apollo 13 flight, there was sufficient system redundancy even when we lost the service module. That was a magnificent effort. TRW Inc. really ought to be proud of their engine for that. (See Slide 2, Appendix I) We had planned for redundancy; we had landed on the moon. However, weight restrictions in the architecture said, "You can t have redundancy for ascent from the moon. You've got one engine. It s got to work. There is no second chance. If that ascent engine doesn't work, you re stuck there." It would not have looked good for NASA. It wouldn't have looked good for the country. There was a letter written that President Richard Nixon would read if the astronauts got stuck on the moon, expressing how sorry we were and so forth. It was a scary letter, really. The ascent engine was an engine that had to work. (See Slide 3, Appendix I).

Harmon, Tim↗

NASA NTRSDate not supplied

Pilot Controls for a Hybrid Turbine-Electric 17 Engine Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft where the aft turbine provides electric power in a hybrid design to wing mounted electric engines. A pilot-in-the-loop study was conducted at Langley Research Center in Hampton, Virginia to explore the design of a flight deck for the hybrid electric aircraft with 16 wing fans and an aft mounted turbine engine. Current flight deck designs provide control inceptors for each propulsion engine and display of all engine parameters for all primary aircraft engines. Automation trends and increasing automation in flight controls and throttle controls indicate less controls instead of more. The design team researched state-of-the-art and recommended study of three, two, and one throttle levers. Engine displays were researched and two were recommended for initial evaluation. 16 airline pilots evaluated the three throttle configurations and two engine display options. Engine failures for known probable indications were evaluated against all throttle and display configurations. This included one, four symmetric, eight non-symmetric, and sixteen momentary electric engine failures with the loss of the aft turbine. The turbine engine was evaluated for complete and partial failure during critical phases of takeoff as well as enroute. This paper details the pilot study including pilot comments supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Recommendations for future study are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗

NASA NTRSDate not supplied

Pilot Controls for a Hybrid Turbine-Electric 17-Engine Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft where the aft turbine provides electric power in a hybrid design to wing mounted electric engines. A pilot-in-the-loop study was conducted at Langley Research Center in Hampton, Virginia to explore the design of a flight deck for the hybrid electric aircraft with 16 wing fans and an aft mounted turbine engine. Current flight deck designs provide control inceptors for each propulsion engine and display of all engine parameters for all primary aircraft engines. Automation trends and increasing automation in flight controls and throttle controls indicate less controls instead of more. The design team researched state-of-the-art and recommended study of three, two, and one throttle levers. Engine displays were researched and two were recommended for initial evaluation. 16 airline pilots evaluated the three throttle configurations and two engine display options. Engine failures for known probable indications were evaluated against all throttle and display configurations. This included one, four symmetric, eight non-symmetric, and sixteen momentary electric engine failures with the loss of the aft turbine. The turbine engine was evaluated for complete and partial failure during critical phases of takeoff as well as enroute. This presentation details the pilot study including pilot comments supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Recommendations for future study are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗

DOE OSTI2023

Engineering Computational Practices (Rev. 1)

This manual will attempt to motivate the use of an automated build system for the purposes of computational science and engineering. As part of this motivation, the surrounding computational practices of version control, documen tation, compute environment management, and regression testing will also be addressed as applied to the practice of computational engineering. Specifically, this manual intends to motivate the adoption of these traditional software engineering practices for use in research and production engineering simulation projects. This manual is not the first such effort in the greater scientific computing community. In fact, the authors relied heavily on the lesson plans of the Software Carpentry, established to teach computing skills to researchers in 1998. As the intention for this manual is to lay out fundamental practices of engineering computing, it will not attempt to fully teach the underlying concepts and will instead reference the well designed lesson plans of the Software Carpentry. Where possible, this manual will explain to general computing practices and concepts and limit discussion of specific software implementations to examples or vehicles for practice in concrete application. The specific software taught by the Software Carpentry curriculum is an excellent starting point to learn the core concepts of computational engi neering. However, the authors have found that applications to engineering simulation and analysis require translation of these software development concepts into the language and workflows of computational engineers. Adopting these computational tools may require engineers to re-imagine their workflows in some combination of traditional engineer ing and software concepts. It has also been necessary to extend existing software build systems for engineering practices beyond the simple wrap ping of engineering software execution. Where necessary, examples of specific software and their method of extension to engineering simulations will be given, with reference to the User Manual for recommended practical use. Where this manual relies on specific implementation examples, it should be understood that the practicing engineer may find that different software is more amenable to their specific work. It is always the overall collection of computational practices is more important than any specific software implementation. The ability to recognize which concepts are implemented by a software package will make a practicing engineer agile to changing project needs, computing resources, numeric solvers, programming languages, and even available funding.

42 ENGINEERING↗

DOE OSTI2020

Gasoline Engine and Fuels Offering Reduced Fuel Consumption and Emissions: Vehicle Modeling Final Report

The Gasoline Engine and Fuels Offering Reduced Fuel Consumption and Emissions (GEFORCE) project was proposed in response to the U.S. Department of Energy’s Funding Opportunity Announcement 0991 by a team made up of the members of the Coordinating Research Council (CRC) and the research staff at Oak Ridge National Laboratory (ORNL.) The project focused on investigating the potential benefits that might be attained through synergistic use of specific engine technology together with fuels formulated to represent potential directions that high-octane fuels of the future might progress. A stated objective in the DOE FOA was to demonstrate a 25% reduction in petroleum consumption through optimization of the engine technologies together with a suitable fuel. An advanced engine was constructed and used with a matrix of research fuels to investigate potential avenues for efficiency improvement. The engine incorporated technologies expected to become mainstream for boosted engines in the next 10 to 20 years. These included increased compression ratio, a two-stage turbocharger, and cooled external exhaust gas recirculation (EGR). The fuel matrix was designed to investigate impacts from research octane number (RON), volumetric ethanol content, and the final boiling point of the fuel. The engine calibration was optimized for each fuel individually and data collected to enable vehicle system modelling that projected energy consumption, fuel economy, tailpipe CO₂ emissions, and impact on petroleum consumption for an industry-average mid-size sedan. The engine calibration and data collection were carried out at IAV in Michigan and is the subject of a separate report. IAV provided the engine data to Oak Ridge National Laboratory to support the vehicle modelling portion of the project. The vehicle modelling results show the following trends: Ethanol content does have a consistently strong influence on the fuel economy results for all cycles and all fuels. Among the fuels of a nominal RON level, increasing ethanol content consistently lowers fuel economy, with the 30% ethanol fuels always providing the lowest fuel economy for a given RON level. However, in some cases the energy consumption improvement allows the 30% ethanol fuels to match the fuel economy of the ethanol-free fuel P. These observations underscore the importance of both engine efficiency and fuel volumetric energy content on vehicle fuel economy.; There was no consistent trend in the projected energy consumption results for differences in fuel T90 for all fuels and cycles. Fuel economy projections did show a consistent trend, with the higher T90 fuel providing slightly greater fuel economy when compared to the low T90 fuel of the same ethanol content. The observed trends were consistent with differences in the heating value of the fuels.; The 102-RON fuels provided reduced energy consumption and greater fuel economy for the advanced engine on all drive cycles. The engine compression ratio of 11.5 was higher than would typically be used in a turbocharged engine when 92-RON fuel use is expected. Hence, the engine experiences more efficiency degradation from knock avoidance when using the 92-RON fuels. This degradation causes the fuel economy results for the 92-RON fuels to be lower than those for the 102-RON fuels.; Fuels E and F (92-RON, 30% ethanol) are projected to achieve 10% or greater reduction in petroleum consumption, with fuels K (102-RON, 30% ethanol) and O (97 RON, 30% ethanol) achieving greater than a 20% reduction. Fuel L (102-RON, 30% ethanol) achieves greater than 25% reduction, meeting the petroleum reduction target of the project. All of the fuels that achieve 10% or greater reduction in petroleum consumption are 30% ethanol blends.; Increasing final boiling point increased fuel economy at fixed ethanol content when the 102-RON fuels were used. This trend is a result of differences in the volumetric energy content of the fuels and the projected energy consumption values for the fuels. In the case of the 102-RON fuels, increasing final boiling point also resulted in an increase in the energy content of the fuel. There was not a consistent trend between the energy content and final boiling point for the 92-RON fuels at fixed ethanol content.

33 ADVANCED PROPULSION SYSTEMS↗

DOE OSTI2021

Retaining Systems Engineering Model Meaning Through Transformation: Demo 2

Digital engineering strategies typically assume that digital engineering models interoperate seamlessly across the multiple different engineering modeling software applications involved, such as model- based systems engineering (MBSE), mechanical computer-aided design (MCAD), electrical computer-aided design (ECAD), and other engineering modeling applications. The presumption is that the data schema in these modeling software applications are structured in the familiar flat- tabular schema like any other software application. Engineering domain-specific applications (e.g., systems, mechanical, electrical, simulation) are typically designed to solve domain-specific problems, necessarily excluding explicit representations of non-domain information to help the engineer focus on the domain problems (system definition, design, simulation). Such exclusions become problematic in inter-domain information exchange. The obvious assumptions of one domain might not be so obvious to experts in another domain. Ambiguity in domain-specific language can erode the ability to enable different domain modeling applications to interoperate, unless the underlying language is understood and used as the basis for translation from one application to another. The engineering modeling software application industry has struggled for decades to enable these applications to interoperate. Industry standards have been developed, but they have not unified the industry. Why is this? The authors assert that the industry has relied on traditional database integration methods. The basic issue prohibiting successful application integration then is that traditional database-driven integration does not consider the distinct languages of each domain. An engineering models meaning is expressed through the underlying language of that engineering domain. In essence, traditional integration methods do not retain the semantic context (meaning) of the model. The basis of this research stems from the widely held assumption that systems engineering models are (or can be) structured according to the underlying semantic ontology of the model. This assumption can be imagined from two thoughts. 1) Digital systems engineering models are often represented using graph theory (the graph of a complex systems model can contain millions of nodes and edges). When examining the nodes one at a time and following the outbound edges of each node one by one, one can end up with rudimentary statements about the model (i.e., node A relates to node B), as in a semantic graph. 2) Likewise, from the study of natural languages, a sentence can be structured into unambiguous triples of subject-predicate-object within formal and highly expressive semantic ontologies. The rudimentary statements about a systems model discerned with graph theory closely mimic the triples used in the ontologies that try to structure natural languages. In other words, a systems models semantic graph can be (or is) structured into an ontology. Additionally, it is well established in industry that through natural language processing (NLP), which provides the means to create language structures, that computers can interpret ontological graphs. Therefore, the authors hypothesized that if the integrity of the underlying semantic structure of a systems model is retained, the contextual meaning of the model is retained. By structuring system models into the triples of the underlying ontology during the transformation from one MBSE application to another, the authors have provided a proof of the concept that the meaning of a system model can be retained during transformation. The authors assert that this is the missing ingredient in effective systems model-to-model interoperability. ACKNOWLEDGEMENTS The authors would like to thank the FY19 Model Interoperability team members who provided a solid foundation for the FY20 team to leverage: John McCloud, for the work he did to guide us toward the right use of technology that will appropriately discover and manipulate ontologies. Carlos Tafoya, for the work he did to develop an application programming interface (API)/Adapter that would export ontology-based data from GENESYS. Peter Chandler, for the work he did to architect our overall integration solution, with an eye toward the future that would influence a large-scale federated production-level systems engineering digital model ecosystem.

42 ENGINEERING↗

NASA NTRSDate not supplied

Ground Test Technology Demonstration for Nuclear Thermal Propulsion Engines

Nuclear Thermal Propulsion (NTP) engines have been deemed a key technology to enable human missions to Mars due to their high efficiency, also known as specific impulse (Isp). Ground testing the NTP engine is critical in maturing the technology and increasing the design’s Technology Readiness Level (TRL), thus mitigating risk from NTP engine performance/operations. NTP engine development began with open-air ground testing through the Rover/NERVA program back in the 1960s when regulatory requirements were not as stringent as they are today. Due to the formation of regulatory bodies, increase in oversight and environmental requirements, the exhaust gas released from NTP engines must be captured or processed to gain approval in the case that the exhaust gas contains fission products from the nuclear fuel elements within the reactor. Ground test campaigns following Rover/NERVA focused on the certification of a full scale NTP engine, which led to exhaust processing systems such as the Rocket Exhaust Capture System (RECS) and Real Time (RT) exhaust processing. These systems were deemed favorable for regulatory compliance but have a high initial investment cost. Reassurance on the feasibility of ground testing and the NTP engine technology likely need to be achieved before NASA invests in these systems. Recently the objectives for NTP engine ground testing have shifted from certification testing of a full scale engine to demonstration testing of a subscale engine. The shift to demonstration testing allows for a shorter testing duration and a lower operational thrust (for demo testing purposes only) to demonstrate the NTP engine (5k-12.5k lbf). Due to these factors, the infrastructure, consumables, total footprint, and exhaust system complexity are able to be drastically reduced, thus reducing cost significantly. The High-pressure Exhaust Capture System (HECS) concept was designed for a NTP engine ground test demonstration. The HECS concept greatly reduces cost compared to previous concepts and suggests favorable regulatory acceptance due to its ability to capture all of the exhaust gas from the NTP engine.

Nuclear Thermal Propulsion↗

NASA NTRSDate not supplied

Nuclear Thermal Propulsion Engine Technology Demonstration Testing

Nuclear Thermal Propulsion↗

NASA NTRS1967

Design of Liquid Propellant Rocket Engines Second Edition

This book intends to build a bridge for the student and the young engineer: to link the rocket propulsion fundamentals and elements (which are well covered in the literature) with the actual rocket engine design and development work as it is carried out in industry (which is very little, if at all covered in literature). The book attempts to further the understanding of the realistic application of liquid rocket propulsion theories, and to help avoid or at least reduce time and money consuming errors and disappointments. In so doing, it also attempts to digest and consolidate numerous closely related subjects, hitherto often treated as separate, bringing them up to date at the same time. The book was written "on the job" for use by those active in all phases of engine systems design, development, and application, in industry as well as government agencies. Since it addresses itself to human beings set out to create new machines, rather than describing machines about to dominate man, the language chosen may not always be "functional" in the strict sense of the word. The book presents sufficient detail to familiarize and educate thoroughly those responsible for various aspects of liquid propellant rocketry, including engine systems design, engine development, and flight vehicle application. It should enable the rocket engineer to conduct, independently, complete or partial engine systems preliminary detail designs and to understand and judge the activities in, and the problems, limitations, and "facts of life~ of the various subsystems making up a complete engine system. It also attempts to educate those ultimately interested in specialized subsystems and component design (thrust chamber, turbopump, control valves, etc.) about their own as well as neighboring subsystems and about the complete engine system. This should enable the student to prepare realistic analytical calculations and design layouts with a long headstart toward the final specialized designs for subsystem production release. Special emphasis has been placed on engine flight application to stimulate engine systems and subsystem designers to think in these terms from the outset. The book is intended as a textbook, with specific consideration of the teacher without industry experience. We hope it will stimulate those desiring to specialize in the area of a rocket engine subsystem by supplying adequate information to enable them to benefit fully from the specialized literature. Thus, it provides a realistic expert introduction for those joining the liquid propellant rocket engine field.

Dieter K Huzel↗

NASA NTRS1972

Analysis of the effect of engine characteristics on the external aerodynamics of STOL wing propulsion systems

The effects of engine presssure ratio, engine size, and engine location on the pressure distribution, lift coefficient, and flow field of a STOL wing propulsion system are presented. The flow variables of the engines are included in the two-dimensional potential flow analysis by considering the effects of mass flow coefficient at the engine inlet and thrust coefficient at the engine exit. A functional relation between these coefficients and engine pressure ratio is given. The results of this study indicate that the effect of engine pressure ratio on the external aerodynamics is a function of engine location. For engines located on the bottom of the wing, the highest pressure ratio engine resulted in the highest lift coefficient. For engines located on the top of the wing, the lowest pressure ratio engine resulted in the highest lift coefficient.

Albers, J. A.↗

NASA NTRS2002

Virtual Collaborative Environments for System of Systems Engineering and Applications for ISAT

This paper describes an system of systems or metasystems approach and models developed to help prepare engineering organizations for distributed engineering environments. These changes in engineering enterprises include competition in increasingly global environments; new partnering opportunities caused by advances in information and communication technologies, and virtual collaboration issues associated with dispersed teams. To help address challenges and needs in this environment, a framework is proposed that can be customized and adapted for NASA to assist in improved engineering activities conducted in distributed, enhanced engineering environments. The approach is designed to prepare engineers for such distributed collaborative environments by learning and applying e-engineering methods and tools to a real-world engineering development scenario. The approach consists of two phases: an e-engineering basics phase and e-engineering application phase. The e-engineering basics phase addresses skills required for e-engineering. The e-engineering application phase applies these skills in a distributed collaborative environment to system development projects.

Dryer, David A.↗