SEARCH · Engineering Papers

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.

SourceResearch connectionFrom yearThrough year

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

At least 1,513 records · Page 84

All sources NASA NTRS DOE OSTI

NASA NTRS2019

Aerojet Engineering Corporation: Stimulation and Creation, 1935-1942

There are multiple published accounts of the stimulation and creation of the Aerojet Engineering Corporation that are inconsistent, incomplete, or erroneous in significant details, describing principals involved, timing, and funding of the creation process. This paper corrects the record and offers a well-documented and reliable history of the creation of the Aerojet Engineering Corporation. A small group of academic researchers and technicians, joined by an attorney, working at the California Institute of Technology (Caltech), accomplished the formation and creation of the corporation. The group of six men incorporated and served as initial officers of the Aerojet Engineering Corporation—Dr. Theodore von Karman; Dr. Frank Malina; Dr. Martin Summerfield; John Parsons; Edward Forman; and a Washington, DC, attorney, Andrew Haley. A government-funded program definition study at Caltech generated a proposal to produce a means of providing superior aircraft performance capabilities using rocketry, often referred to as jet propulsion, due to engineering disrepute of “rocketry" prior to WWII. Caltech successfully conducted flight demonstrations at March Field (Riverside, California) in the summer of 1941, leading Drs. von Karman and Malina to discuss and explore the best method to provide for production of jet-assisted takeoff (JATO) rockets with established industrial leaders, as well as industrial organizational alternatives. Von Karman, Malina, Summerfield, Parsons, and Forman continued these discussions until von Karman decided, in early 1942, to solicit the legal advice of Andrew Haley on how to proceed. After meetings at von Karman's home in Pasadena, on Haley's recommendation and using his volunteered initial corporate funding, it was agreed to incorporate the group. Articles of incorporation were drawn up by Haley and on 19 March 1942 were formally filed with the Delaware Secretary of State, establishing the Aerojet Engineering Corporation. Many accounts previously published have distorted or misreported many of the details of the process followed by the group that created the company. It is intended that this paper will be regarded as a fully researched historical account of the creation of the Aerojet Engineering Corporation. Included are the historical environment, the industrial motivations, descriptions of key players, the role of government, and the ultimate confluence of these factors with the motivation of a champion and the availability of the required resources.

Doyle, Stephen E.↗

NASA NTRS2019

Extreme-Temperature Carbon- and Ceramic-Matrix Composite Nozzle Extensions for Liquid Rocket Engines

The United States (US) National Aeronautics and Space Administration (NASA) and its US industry partners are developing extreme-temperature composite nozzle extensions for a variety of cryogenic liquid rocket engine propulsion systems. Applications under consideration at the NASA Marshall Space Flight Center (MSFC) include launch vehicle (upper stage), in-space, and lunar lander descent/ascent propulsion systems. Composite material systems of interest include carbon-carbon (C-C) and carbon/silicon-carbide (C-SiC) composites, as well as modified versions of such composites (coatings, mixed matrices, oxidation inhibitors, etc.). Missions addressed include access to low Earth orbit, the lunar surface, and more distant destinations. Cryogenic upper-stage and in-space liquid rocket engines are optimized for performance through the use of high area ratio nozzles to fully expand combustion gases to low exit pressures, increasing exhaust velocities. As a result of the large size of such nozzles, and the related engine performance requirements, composite nozzle extensions are being considered to reduce mass impacts. Currently, metallic and foreign composite nozzle extensions used on the Atlas V, Delta IV, Falcon 9, and Ariane 5 launch vehicles represent the state-of-the-art. Such extensions are limited to use at or slightly above 2000°F (1093°C). Materials under development by MSFC and its industry partners have the potential to operate at temperatures up to (or above) 4250°F (2343°C). Marshall Space Flight Center efforts are aimed at (a) further developing the technology and databases needed to enable the use of composite nozzle extensions on cryogenic liquid rocket engines, (b) developing and demonstrating low-cost capabilities for testing and qualifying such nozzle extensions, and (c) advancing the US domestic supply chain for nozzle extensions. Through the Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR) Programs, low-level internal MSFC research projects, and teaming arrangements with domestic industry partners, composite material design, development, hot-fire test, and evaluation efforts are progressing. Hot- fire engine tests of subscale hardware have been conducted using oxygen/hydrogen (LOX/H2), oxygen/methane (LOX/CH4), and oxygen/kerosene (LOX/RP-1) propellants. These engine tests at MSFC have enabled the evaluation of both heritage and state-of-the-art material systems, demonstrating the initial capabilities of the extreme temperature materials and their fabrication methods. Recent, ongoing, and potential future work supporting cryogenic propulsion systems development will be presented. The composite nozzle extension technology and test capabilities being developed are intended to support both NASA and US Department of Defense requirements, as well as those of the broader Commercial Space industry.

Valentine, Peter G.↗

NASA NTRS2019

Space Research Project Management Can Benefit from Engineering Technology Selection Methods

Many engineering methods have been developed to help management select technology for a system design or further research. The simplest way to compare technologies is to use a checklist containing all the more or less important selection criteria, so that nothing is overlooked. The criteria usually include cost, safety, reliability and maintainability, and potential problems such as noise generation and microgravity sensitivity. The next step typically is to weight and score all the criteria. The process of weighting and scoring is helpful in bringing out different priorities and reaching a shared point of view. Group technology selection methods are designed to highlight initial disagreements and produce a shared consensus. Often a frank discussion led by management rather than decision analysts can be more effective. The final selection depends on management and engineering judgment and may include programmatic and organizational factors that are beyond the engineering checklist. The objective of engineering technology selection methods is to provide engineering information to assist management in making sound decisions. Project management and technology selection are assumed to use rational engineering analytic methods, but they often do not. The reason is that human insight, intuition, and “gut feel,” rather than logic, more frequently determine our decisions. Project selection and management are strongly influenced by nonrational psychological influences, which can produce unjustified confidence and determination. Nevertheless, there is a strong need for space projects to do rational project analysis and selection. Demonstrating a rational spirit is necessary for a scientific and technical organization. Professional ethics at its best requires an open, honest, and fair process, without damaging politics. Rational analysis can help improve good projects and avoid selecting bad ones. A sanity check using rational analysis guided by a checklist can help avoid egregious and damaging errors.

Jones, Harry W.↗

NASA NTRS2019

Interference Drag Associated with Engine Locations for Multidisciplinary Design Optimization

This research aims to quantify the interference drag for various engine locations on a traditional “tube and wing,” 150-passenger commercial aircraft flying at 35,000 ft and Mach 0.8. Engine locations are varied in the chord wise, span wise, and vertical directions near the wing, both under and above the wing, as well as along the fuselage. Euler simulations are performed with representative powered modern engines. The results are intended to supplement empirical drag estimates suitable for multidisciplinary design environments. Large interference drag increases, as compared to the isolated air frame and engine geometry, are found to occur when the engine is placed directly above or below the wing. Interference effects are significantly reduced, and in some instances result in benefits compared to the isolated bodies, when the engines are placed fore or aft of the wing. Interference drag increases are partially explained by flow channels leading to choked flow and shock interactions between bodies.

Blaesser, Nathaniel J.↗

NASA NTRS2020

Strategic Perspectives on the Future of Systems Engineering at NASA

NASA’s Model-Based Systems Engineering (MBSE) Infusion and Modernization Initiative (MIAMI) chartered a strategy group comprising early to mid-career NASA subject matter experts with diverse experiences to look into the future of systems engineering at NASA. The purpose of the group was to provide a vision for the future state of systems engineering practices and to develop a strategic plan to enable the evolution of the art up to 20 years in the future. The group used a design thinking approach to gather ideas and obtained insight into current engineering processes and domain outlook by interviewing engineers of varying expertise and experiences who had worked on teams of different sizes for missions large and small. The group built a roadmap to highlight future needs, projected capabilities, and technology and competency gaps and developed a strategic plan to ensure the expedient introduction of these capabilities. The resulting strategic plan recommends capability development and workforce strategies and provides guidance for Agency-wide SE policy. Artifacts, details, and raw data from the strategy team’s work are contained in NASA/TM-20205002911/SUPPL, Strategic Perspectives on the Future of Systems Engineering at NASA: Supplemental Information: Appendixes A to K.

Anupa R Bajwa↗

NASA NTRS2018

The OpenSE Cookbook: A Practical, Recipe Based Collection of Patterns, Procedures, and Best Practices for Executable Systems Engineering for the Thirty Meter Telescope

The OpenSE Cookbook is an open-sourced collection of patterns, procedures, and best practices targeted for systems engineers who seek guidance on applying model-based and executable systems engineering (MBSE) using SysML. Its content has emerged from the system level modeling effort on the European Framework Program 6 (FP6) and the Thirty Meter Telescope (TMT). The TMT MBSE approach applied the Executable Systems Engineering Method (ESEM) and the open-source Engineering Environment (OpenMBEE) to specify, analyze, and verify requirements of TMT’s Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS). In these applications, implicit dependencies are made explicit in a formal model through the use of ESEM, OpenMBEE, and SysML modeling constructs. The value proposition for applying this MBSE approach was to establish precise requirements and fine-grained traceability to system designs, and to verify key requirements beginning early in development. The integration of ESEM and the OpenMBEE tooling infrastructure (providing linked-data and web-operability) is a significant added value for the MBSE approach. The APS is responsible for the overall pre-adaptive optics wavefront quality, using starlight to measure wavefront errors and align the TMT optics. In the formally integrated and executable SysML model, simulations are performed to analyze the impact of changed requirements and verify specified constraints for various operational scenarios. The APS team used several modeling patterns to capture information such as the requirements, the operational scenarios, involved subsystems and their interaction points, the estimated or required time durations, and the mass and power consumption. Adaptive optics systems are designed to sense real-time atmospheric turbulence and correct the telescope’s optical beam to remove its effect. The system model for the adaptive optics operational modes was developed to capture sequence behaviors and operational scenarios to run Monte-Carlo simulations for verifying acquisition time, observing efficiency, and operational behavior requirements. The model is particularly useful for investigating the effect of parallelization, identifying interface issues, and re-ordering sequence acquisition tasks. A former version of the Cookbook (which is now updated to MBSE challenges, goals, and lessons learned) included modeling guidelines and conventions for all system aspects, hierarchy levels, and views, which were developed during for the Active Phasing Experiment (APE), an opto-mechatronical system technology demonstrator for the Extremely Large Telescope (ELT). The Cookbook utilizes the above mentioned system models as real-world case-studies to demonstrate and document the applications of the recipes, providing also instructional examples and addressing the available tooling support. The Cookbook is accompanied by a number of SysML models and aodel libraries which facilitate model authoring and maintenance. The Cookbook covers the different aspects of Systems Engineering such as management of Requirements, Design (behavior and structure), Interfaces, Interdisciplinary Integration, Analysis, Trade Studies, and Technical Resources. This paper presents the background, motivation, architecture, and highlights some key content of the Cookbook. For example, interface management, error budget management, requirements verification, Monte Carlo driven analysis, and timing analysis of operational scenarios. The paper discusses how the capabilities of OpenMBEE contributed significantly to the adoption of executable systems engineering.

Brower, Eric↗

NASA NTRS2019

Challenges in applying model-based systems engineering: human-centered design perspective

Systems engineering is, by its nature, human-centered. It is about tradeoffs and negotiations by systems engineers among different disciplines and systems to ensure the resulting system of systems can achieve the mission objectives successfully. Applying MBSE means enabling system engineers to use MBSE processes, methods, and tools to perform such work. This requires not only tools and infrastructure that support MBSE but also cultural change in how system engineers approach their work. Although the cultural change is listed as one of the challenges for MBSE infusion to address, its details and how to address them are not often discussed in the literature and the community. We used Human-Centered Design framework to articulate a core set of related challenges and the implications to tool and infrastructure developments. We will discuss the details of the HCD framework applied and discuss the core challenges using an electrical system engineering to harness engineering workflow as a case study.

Jimenez, Alejandro↗

NASA NTRS2021

Evaluations of Damaged High-Pressure Compressor Blades in Two Turbine Engines of NASA DC–8

A series of flights were performed by the NASA DC-8 for the FIREX-AQ missions to observe the effects of wildfires and agricultural fires on air quality and climate in selected locations of the United States. Borescope evaluations after these flights indicated accelerated damage had occurred over this flight series to the blades in the high pressure compressor section of all four CFM56-2C1 turbine engines. This erosion and impact damage appeared to vary in severity, and appeared most severe for engines 3 and 4 located on the right wing of the DC-8.Engine 3 had the most flight hours and cycles since last overhaul of 7,152 h and 2,502 cycles. Engine 4 had the lowest flight hours and cycles since last overhaul of 1,354 h and 369 cycles. For these reasons, three noticeably damaged blades were selected from the high pressure compressor for each of these two engines, and then evaluated at NASA GRC using optical and scanning electron microscopy. Engine 3 compressor blades had both erosion and impact damage that were observed and characterized. The erosion damage was associated with embedded particles 13 μm to 42 μm in sectioned width, composed of varied compositions ranging from SiO2 to SiO2 also containing Ca, Mg, and Al (CMAS). The impact damage was associated with the impacts of larger objects at least 650 μm to 850 μm in width, but only small fragments 5 μm to 15 μm in sectioned width were embedded in the impact surface, also composed of SiO2 to SiO2 containing Ca, Mg, and Al (CMAS). On the other hand, engine 4 blades had only impact damage that was observed and characterized. This impact damage was associated with impacts of objects at least 1,480 μm to 2,080μm in width. Small fragments 5 μm to 15 μm in sectioned width were embedded in the impact surface. For one impact, the fragments were again composed of SiO2 to SiO2 containing Ca, Mg, and Al (CMAS). For two other impacts, the fragments were often composed of Fe, and less frequently Cu.

turbine↗

NASA NTRSDate not supplied

A Model-Based Systems Engineering Journey to Developing a Concept of Operations

Starting in 2017, NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) element began a systems engineering transition from traditional, document-centric development to model-centric development when defining its foundation medical systems. These foundation medical systems define a Concept of Operations (ConOps) and identify the generic requirements for a medical system based on assumptions about a generic crew and mission environments and guidance from NASA standards (e.g., Medical “Levels of Care”). By making the transition, ExMC intends to improve communication among stakeholders about foundation medical system requirements and content. In addition, this transition will enable ExMC to lower both development and crew treatment risks for future, mission-specific medical systems. ExMC followed a Model Based Systems Engineering (MBSE) paradigm when developing the foundation medical systems. A model-based approach provides several advantages over a traditional, document-centric approach. First, when Systems Engineers (SE) develop diagrams in a model using a standard modeling language, they produce information dense pictures that facilitate understanding much more efficiently with less room for misinterpretation than text. Second, due to the evolving nature of projects, documentation becomes out of date the minute it is published. This can result in people making decisions based on information that is no longer current, especially if they are referencing a locally-stored copy of a document. A model, on the other hand, is always up to date with the latest approved changes and information. It serves as a single point of truth. Third, a model-centric approach centralizes all important information in one place. Rather than having to flip through separate ConOps documents, design specifications, requirements specifications, and the like to coordinate information, a model captures the content in one, integrated spot. This integration makes tracing information from end-to-end easier with greater reliability. The ExMC Systems Engineering Lifecycle follows a well-defined process. ExMC Systems Engineers perform all major steps of the process, regardless of the development methodology. One of the first steps in the process is developing the ConOps that describes the operation of the system from the point of view of the users. It includes a list of the users and their needs, the goals of the medical system, key assumptions about the system, and definitions of the medical system’s operational environments. For this development effort, ExMC chose to replace the traditional text-based ConOps document with a model. While the decision to change the development workflow was not difficult, implementing the structural and organizational workflows were. It required showing ExMC’s users, most of whom are not Systems Engineers, how the information they require would be presented in the model and to gain their acceptance of this approach. This paper documents key lessons learned during the ConOps transformation by focusing on how the model represents information, the agile workflow used by SEs when developing the model and how it integrates into a project plan, how leadership influenced key users to accept the transformation, and how the users interact with the model information.

Jeffrey Robert Cohen↗

NASA NTRS2022

Design Thinking, Lean Startup, and High-Technology Marketing for Human-Centered Systems Engineering

The use of design thinking, lean startup, and high-technology marketing in systems engineering are presented as a case study. All were used and evaluated for their potential to improve systems engineering processes and design, address the challenges of culture change, increase the adoption rate of new technology, and engage with potential users and sponsors more effectively. Multiple examples of training and use on a model-based systems engineering initiative at a large government agency showcase how these approaches were tailored and used successfully for significant benefits such as enhanced collaboration and better problem definition and design solutions. Challenges remain for use by quiet thinkers and with virtual teams. These new ways of thinking are well aligned with creating and using new technologies and are suitable for situations involving innovation, uncertainty, and change within organizations. This case study intends to familiarize systems engineers with the application of these human-centered approaches, to interest systems engineers in incorporating these approaches into their work processes ,and to inspire the systems engineering research community to investigate further.

Karen J. Weiland↗

NASA NTRSDate not supplied

Methods for Developing Successful Systems Engineers

Systems Engineering (SE) is a complex and challenging field that incorporates the knowledge of systems engineering processes, the ability to synthesize a wide-range of engineering disciplines, and the ability to lead a team of people to successfully accomplish the goals of a project. It requires hard technical skills and soft-skill leadership savvy. As a result, three main development needs are identified: 1) Knowledge of SE processes, the benefits of these processes to a project and their tailored application 2) Knowledge of a wide-range of engineering disciplines, how they interrelate in a system, and the development of sound technical judgement 3) Team leadership to direct and motivate a team of subsystem and discipline experts This paper describes the establishment of a comprehensive training and development program for Systems Engineers at NASA Ames Research Center that addresses in part each of these three areas from the perspective of the implementing manager. A variety of methods have been utilized including the establishment of a SE Community of Practice, a unique and innovative web tool, on-line videos, classroom training in NASA’s 17 Common Technical Processes, guidance on the tailored application of these processes, monthly technical talks, mentoring in both technical judgment and team leadership, and NASA’s Leadership Development Programs. While much of professional SE development must come through project experience, the approaches listed above can accelerate development. The diversity of skills required of Systems Engineering demands a multi-faceted approach to successfully train and develop this critical skill.

development↗

NASA NTRSDate not supplied

Methods for Developing Successful Systems Engineers

Systems Engineering (SE) is a complex and challenging field that incorporates the knowledge of systems engineering processes, the ability to synthesize a wide-range of engineering disciplines, and the ability to lead a team of people to successfully accomplish the goals of a project. It requires hard technical skills and soft-skill leadership savvy. As a result, three main development needs are identified: 1. Knowledge of SE processes, the benefits of these processes to a project and their tailored application 2. Knowledge of a wide-range of engineering disciplines, how they interrelate in a system, and the development of sound technical judgement 3. Team leadership to direct and motivate a team of subsystem and discipline experts This paper describes the establishment of a comprehensive training and development program for Systems Engineers at NASA Ames Research Center that addresses in part each of these three areas from the perspective of the implementing manager. A variety of methods have been utilized including the establishment of a SE Community of Practice, a unique and innovative web tool, on-line videos, classroom training in NASA’s 17 Common Technical Processes, guidance on the tailored application of these processes, monthly technical talks, mentoring in both technical judgment and team leadership, and NASA’s Leadership Development Programs. While much of professional SE development must come through project experience, the approaches listed above can accelerate development. The diversity of skills required of Systems Engineering demands a multi-faceted approach to successfully train and develop this critical skill.

development↗

NASA NTRSDate not supplied

System Safety Analysis of Complex NASA Systems with Model-Based Engineering (REV B)

The emergence of model-based engineering is transforming design and analysis methodologies. A recognized benefit of model-based engineering is the existence of a “single source of truth” about the system that becomes the authoritative source of data and information for designers, analysts, and developers. This promotes consistency and efficiency as the design emerges and can be used to further optimize the design. Integrating System Safety Engineers to the “single source of truth” will ensure that the outputs of their assessments and analyses are relevant to the design as it evolves. Use of an integrated system model enables near immediate evaluation of a design change as well as development of operational processes for risk assessment and communication. Such models can enable efficient and timely analysis of system hazards (e.g., hazard fault tree analysis and procedure simulations) and produce complete, accurate, and more consistent products (e.g., hazard reports and safety requirement evaluations). Therefore, an agency-sponsored team at Goddard Space Flight Center (GSFC) recently completed a System Safety Study of modeling and testing capabilities as part of a Model-Based Safety and Mission Assurance Initiative (MBSMAI). Using an existing model developed for reliability analyses, GSFC modeling and system safety experts performed system safety analysis/modeling and produced safety products. The team evaluated model-based feasibility to support System Safety Engineering, developed safety analysis modeling processes, and identified tool capability advancement/development needs. These study results indicate model-based engineering is valid and useable for System Safety Engineering for NASA if adequate modeling processes and environment are established.

NASA↗

NASA NTRS2023

Requirements Engineering Scorecard and the Next-Generation Space Suit

The objective for a NASA contractor, the performing organization in this case study, is to provide engineering services to develop and deliver the next generation space suit to NASA, the customer in this case study. A case study with qualitative and quantitative analyses regarding a new process and approach to requirements engineering is described, with the intent that if utilized, these tools may have contributed to improvements across the project in terms of meeting cost, scope, budget and quality while appropriately accounting for risk management. The procedure entails a research method in which the current state of the project, current state of the art, and the identified systems engineering challenges are evaluated. Iterative models are tempered through development by continual improvements by engineering evaluation of engineers on the project. The current results have produced a prototype of a requirements engineering scorecard with implementations of FMEA and quantitative analysis to (i) identify root cause of underdeveloped requirements and (ii) project management impacts with regards to project risk. Forward work includes customer, performing organization, acceptance against applicable INCOSE community accepted practices.

INCOSE↗

NASA NTRSDate not supplied

Expanding the Capability of A Legacy Combustion Flametube to Test High Temperature Engine Materials in Relevant Environments

New materials and component designs are needed to advance gas turbine engine technology and provide the performance and efficiency needs for future applications. In order to advance these materials, testing in combustion environments is a critical step prior to engine testing. In this work, we detail the design and the fabrication of a materials test sector in a flametube combustor facility. The facility simulates a combustion environment similar to that experienced by components in gas turbine engines. The flow regime is characterized by a combination of high-temperature, high-velocity, high-heat flux, and high-velocity that components experience in gas turbine engines. Exposure of components in this facility allows for the study of combined environmental effects and the impact on both coating and substrate durability. The test facility may operate across a wide range of pressures from 275-400 psig (1,896-2,758 kPa) and an air flow rate of 5 lb/s (2.27 kg/s). While combustion gas temperature is expected in excess of 3,000°F (1,649°C), 900°F (482°C) cooling air may be supplied to the backside of components or test articles. The flametube combustor was previously used to evaluate fuel injectors and combustion products, and the new test configuration will also allow for materials exposure to complex, engine-like conditions. The interior of the Test Section was additively manufactured from GRCop-84 and cryogenically fit and brazed to a stainless steel 304 housing. The use of a copper liner minimizes welds and with active cooling, is expected to provide better durability over traditional hardware using stainless steel or Inconel with a ceramic liner. The Test Section has two opposing removable windows approximately 230 mm x 80 mm that can accommodate articles up to 85 mm tall. This modular design allows for custom platforms to hold coupons, panels, or airfoil shapes to be tested with minimal re-engineering or fabrication. The bolted joint and sealing remains consistent, so any new testing only needs to work within the existing design footprint. This paper will provide an overview of the facility capabilities, design considerations, as well as thermal and structural analysis of the hardware. Future testing of ceramic matrix composite (CMC) airfoils and advanced environmental barrier coatings (EBCs) will also be discussed.

Combustion↗

NASA NTRSDate not supplied

Assessing Engine Hot Fire Data for Human Spaceflight Applications

Development and certification of liquid engine systems for human spaceflight missions requires exhaustive analysis to meet the NASA’s requirements for engine health, reliability, and performance. The techniques used to assess requirement conformance and test-to-test engine health pose many unique challenges including the unusually large scale of data, complex component and system analysis, and rigorous engineering judgement standards. To address these challenges, NASA Marshall Space Flight Center’s Engine Systems branch has developed and maintained a robust software suite and operational processes that satisfy programmatic requirements levied on engines and the 7 Elements of Flight Rationale. Analysis at a systems level includes subsystem assessment of components such as turbomachinery and combustion devices as well as structural and fluid dynamics and transient and steady-state assessment at a systems level. Some of the most important tools to accomplish this analysis are automated script databases, creation of historical and statistical comparisons, and parameters calculated at the full data rate. These tools greatly simplify the crucial processes of anomaly investigation, limit monitoring, health assessment, and timely communication of key conclusions drawn from hot fire testing and flight data analysis.

Data Assessment↗

NASA NTRSDate not supplied

Assessing Engine Hot Fire Data for Human Spaceflight Applications

Data Assessment↗

DOE OSTI2020

Measurement of engine-oil fuel dilution using laser induced florescence spectroscopy

An optical diagnostic, based on laser-induced fluorescence (LIF), has been developed for on-engine measurements of real-time fuel dilution of engine oil, or fuel in oil (FiO). Fuel dilution of oil is believed to be one of the underlying mechanisms that promotes low speed pre-ignition (LSPI) during high-load engine operations. While standard (e.g., ASTM D3524-90) methods are not capable of transient measurements, the LIF technique resolves transient dilution on the minutes time scale, making it possible to study the relation between FiO and LSPI. The measurement is based on adding a dye (ca. 500 ppm) to the fuel and monitoring for its presence in the oil via LIF. The instrument contains a 532-nm laser diode, and a spectrometer to resolve the LIF spectra. A fiber-optic assembly links the instrument to the engine measurement location; the probe is in a Y-configuration with the six fibers around one on a common probe end that connects to the engine; the Y-assembly legs are connected to the instrument; the two legs are the six fibers for transporting the laser light, and the single fiber for the fluorescence. We have expanded on our previous work (Parks et al, SAE paper 2007-01-4108, 2007), by demonstrating the diagnostic technique with to measure transient oil dilution on a 2.0-liter GM ECOTEC LNF single cylinder SI engine. The proposed LIF diagnostic will be critical in studying oil-dilution correlation with LSPI events.

Neupane, Sneha↗