Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Process 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 991 records · Page 55

Process for Making Carbon-Carbon Turbocharger Housing Unit for Intermittent Combustion Engines

An improved. lightweight, turbine housing unit for an intermittent combustion reciprocating internal combustion engine turbocharger is prepared from a lay-up or molding of carbon-carbon composite materials in a single-piece or two-piece process. When compared to conventional steel or cast iron, the use of carbon-carbon composite materials in a turbine housing unit reduces the overall weight of the engine and reduces the heat energy loss used in the turbo-charging process. This reduction in heat energy loss and weight reduction provides for more efficient engine operation.

Northam, G. Burton↗

A proven approach for more effective software development and maintenance

Modern space flight mission operations and associated ground data systems are increasingly dependent upon reliable, quality software. Critical functions such as command load preparation, health and status monitoring, communications link scheduling and conflict resolution, and transparent gateway protocol conversion are routinely performed by software. Given budget constraints and the ever increasing capabilities of processor technology, the next generation of control centers and data systems will be even more dependent upon software across all aspects of performance. A key challenge now is to implement improved engineering, management, and assurance processes for the development and maintenance of that software; processes that cost less, yield higher quality products, and that self-correct for continual improvement evolution. The NASA Goddard Space Flight Center has a unique experience base that can be readily tapped to help solve the software challenge. Over the past eighteen years, the Software Engineering Laboratory within the code 500 Flight Dynamics Division has evolved a software development and maintenance methodology that accommodates the unique characteristics of an organization while optimizing and continually improving the organization's software capabilities. This methodology relies upon measurement, analysis, and feedback much analogous to that of control loop systems. It is an approach with a time-tested track record proven through repeated applications across a broad range of operational software development and maintenance projects. This paper describes the software improvement methodology employed by the Software Engineering Laboratory, and how it has been exploited within the Flight Dynamics Division with GSFC Code 500. Examples of specific improvement in the software itself and its processes are presented to illustrate the effectiveness of the methodology. Finally, the initial findings are given when this methodology was applied across the mission operations and ground data systems software domains throughout Code 500.

Pajerski, Rose↗

An expert system for integrated structural analysis and design optimization for aerospace structures

The results of a research study on the development of an expert system for integrated structural analysis and design optimization is presented. An Object Representation Language (ORL) was developed first in conjunction with a rule-based system. This ORL/AI shell was then used to develop expert systems to provide assistance with a variety of structural analysis and design optimization tasks, in conjunction with procedural modules for finite element structural analysis and design optimization. The main goal of the research study was to provide expertise, judgment, and reasoning capabilities in the aerospace structural design process. This will allow engineers performing structural analysis and design, even without extensive experience in the field, to develop error-free, efficient and reliable structural designs very rapidly and cost-effectively. This would not only improve the productivity of design engineers and analysts, but also significantly reduce time to completion of structural design. An extensive literature survey in the field of structural analysis, design optimization, artificial intelligence, and database management systems and their application to the structural design process was first performed. A feasibility study was then performed, and the architecture and the conceptual design for the integrated 'intelligent' structural analysis and design optimization software was then developed. An Object Representation Language (ORL), in conjunction with a rule-based system, was then developed using C++. Such an approach would improve the expressiveness for knowledge representation (especially for structural analysis and design applications), provide ability to build very large and practical expert systems, and provide an efficient way for storing knowledge. Functional specifications for the expert systems were then developed. The ORL/AI shell was then used to develop a variety of modules of expert systems for a variety of modeling, finite element analysis, and design optimization tasks in the integrated aerospace structural design process. These expert systems were developed to work in conjunction with procedural finite element structural analysis and design optimization modules (developed in-house at SAT, Inc.). The complete software, AutoDesign, so developed, can be used for integrated 'intelligent' structural analysis and design optimization. The software was beta-tested at a variety of companies, used by a range of engineers with different levels of background and expertise. Based on the feedback obtained by such users, conclusions were developed and are provided.

Source record↗

X-Ray Computed Tomography During Preliminary Examination of Apollo Drive Tube 73001

Introduction: Starting in 2019, the Apollo Next Generation Sample Analysis (ANGSA) Program has enabled consortium studies of specially curated Apollo samples that were previously unstudied (or under studied). This began with unsealed core tube 73002 [1,2] that is the upper part of a station 3 double drive tube. More recently the pro-gram extended to the study of a variety of frozen Apollo 17 samples [3], as well as the gas extraction [4] and dis-section [5] of 73001, the lower half of the station 3 double drive tube, that was sealed under vacuum on the Moon. In this abstract we will examine the role of X-ray Computed Tomography (XCT) during the preliminary examination process for sealed core 73001, including: (1) engineering scans to aid in understanding the gas extraction process, whole-core scanning prior to opening to inform extrusion and dissection work, and (3) individual particle scanning to characterize rock fragment lithologies for follow on studies. Methodology: Sample 73001 is a 33 cm long, 4 cm diameter regolith sample collected inside a drive tube (~1 mm aluminum walls). That drive tube was sealed inside a 0.5 mm thick stainless steel (SS) Core Sample Vacuum Container (CSVC). XCT scans for engineering purposes were done on the Nikon XTH 320 system at Johnson Space Center using the 225 kV multi-metal reflection source at 215 kV, 179 A, and a 38.49 m voxel size. Individual >4 mm particles separated from the core during processing (then triply sealed in Teflon bags) were also scanned at JSC using the 180 kV source at 90 kV, 33 A, and a 2.98 – 10.65 m voxel size. Whole-core scans were done at the University of Texas High-Resolution X-ray Computed Tomography Facility (UTCT) on the 225 kV reflection source on the North Star Imaging cabinet XCT system. These scans included: (1) a series of 9 overlapping super-resolution scans each covering a ~4 cm length of the tube at 190 kV, 180 µA, and a 12.9 µm voxel size and (2) a lower resolution continuous helical scan of the entire core at 190 kV, 180 µA, and a 51.8 µm voxel size. Progress and Results: Before piercing and extracting the gas from sample 73001, an XCT scan of the bottom portion of the CSVC was used to confirm the location of the Teflon cap on the inner drive tube, to ensure it was not accidentally pierced during gas extraction. Similarly, after piercing, the bottom and top portions of the CSVC were scanned in order to capture engineering knowledge about the results of the piercing process, as well as the metal knife edge vacuum seal (SS into In-Ag alloy). Both scans will provide constraints on future work of this type, particularly for samples collected during the Artemis mission. Another finding from these "engineering" scans was that the device in the drive tube that immobilizes the regolith (the keeper) was not seated in the tube properly. This meant that (1) the drive tube could not be removed from the CSVC for the trip to UTCT, and (2) the procedure for opening and extruding the drive tube had to be modified. Had either of these things not been known prior to opening the CSVC, it could have led to an inability to XCT scan the whole core at high resolution and/or potential disruption of the core stratigraphy during extrusion. At UTCT, the entire length of the core was scanned at high resolution (12.9 microns per voxel). This scan serves multiple purposes: (1) A lower resolution (and uncorrected) version of these scans stitched together was used to help inform the processors of potential pitfalls during extrusion and dissection; and (2) the full resolution corrected data will serve as the permanent in situ record of the stratigraphy of the sample and will enable future researchers to perform a variety of analyses. So far, 92 of the 121 >4 mm particles separated during dissection pass 1 of sample 73001 have been individually scanned. These scans clearly show the lithology of each particle while keeping the particles in pristine condition. Because of the dust adhering to particle exteriors it would otherwise be impossible to determine lithologies in a non-contaminating way. Thus far the types of lithologies seen in sample 73001 (e.g., regolith breccias, impact-melt breccias, agglutinates, and basalts) are similar to those previously identified in sample 73002 [2]. By the time of the meeting, all particles from all 3 dissection passes will have been scanned and statistics on the different lithologies in 73001 compiled. References: [1] Shearer et al. (2020) 51st LPSC, abstract 1181. [2] Zeigler et al. (2020) 51st LPSC, abstract 3023. [3] Kent et al. (2022) This Volume. [4] McDonald et al. (2022) European Lunar Symposium. [5] Gross et al (2022) This volume.

Moon↗

Cylinder-temperature correlation of a single-cylinder liquid-cooled engine

An analysis based on nonboiling forced-convection heat-transfer theory is made of the cooling processes in liquid-cooled engine cylinders. Semiempirical equations that relate the average head and barrel temperatures with the primary engine and coolant parameters are derived. A correlation method based on these equations is applied to data obtained from previously reported investigations, which were conducted over large ranges of engine and coolant conditions with two liquid-cooled cylinders using water and various aqueous ethylene glycol solutions as coolants. Upon evaluation of empirical factors, an equation for the cylinder-head temperature as a function of the engine operating conditions and the flow rate, temperature, and physical properties of the coolants is obtained, which represents the data with good accuracy.

Pinkel, Benjamin↗

X-Ray Computed Tomography of Apollo Drive Tube 73001 as Part of the Apollo Next Generation Sample Analysis Program

Introduction: Starting in 2019, the Apollo Next Generation Sample Analysis (ANGSA) Program has enabled consortium studies of specially curated Apollo samples that were previously unstudied (or under studied). This program was intended as a participating scientist program for these Apollo samples, as well as a preparation for upcoming lunar sample return missions (e.g., Artemis). The work began with studies of unsealed core tube 73002 [1,2] that is the upper ~35 cm of an Apollo 17 double drive tube (~70 cm total depth) collected on the landslide deposit near Lara Crater at Station 3 in the Taurus Littrow Valley. More recently the program extended to the study of a variety of frozen Apollo 17 samples [3], as well as the gas extraction [4] and dissection [5] of 73001, the lower half of the station 3 double drive tube. Sample 73001 was sealed under vacuum on the Moon in a Core Sample Vacuum Container (CSVC). In this abstract we will examine the role of X-ray Computed Tomography (XCT) during the preliminary examination process for sealed core 73001, including: (1) engineering scans to aid in understanding the gas extraction process, (2) whole-core scanning prior to opening to inform extrusion and dissection work, and (3) individual particle scanning to characterize rock fragment lithologies for follow on studies. Methodology: Sample 73001 is a 33 cm long, 4 cm diameter regolith sample collected inside a lunar drive tube (~1 mm aluminum walls). That drive tube was sealed inside a 0.5 mm thick stainless steel (SS) CSVC. XCT scans for engineering purposes were done on the Nikon XTH 320 system at Johnson Space Center using the 225 kV multi-metal reflection source at 215 kV, 179 A, and a 38.49 m voxel size. Individual >4 mm particles separated from the core during processing (then triply sealed in Teflon bags) were also scanned at JSC using the 180 kV source at 90 kV, 33 A, and a 2.98 – 10.65 m voxel size. Whole-core scans were done at the University of Texas High-Resolution X-ray Computed Tomography Facility (UTCT) on the 225 kV reflection source on the North Star Imaging cabinet XCT system. These scans included: (1) a series of 9 overlapping super-resolution scans each covering a ~4 cm length of the tube at 190 kV, 180 µA, and a 12.9 µm voxel size and (2) a lower resolution continuous helical scan of the entire core at 190 kV, 180 µA, and a 51.8 µm voxel size. Progress and Results: Before piercing and extracting the gas from sample 73001, an XCT scan of the bottom portion of the CSVC was used to confirm the location of the Teflon cap on the inner drive tube and whether there was an “air” gap between the Teflon cap and the CSVC. This was to ensure the Teflon cap (which immobilized the soil inside the drive tube) was not accidentally pierced during gas extraction. Similarly, after piercing, the bottom and top portions of the CSVC were scanned in order to capture engineering knowledge about the results of the piercing process, as well as the metal knife edge vacuum seal (SS into an In-Ag alloy). Both scans will provide constraints on future work of this type, both for the design of tools used on the lunar surface during Artemis, as well as how we open future samples of this type. An unexpected finding from these engineering scans was that the device in the drive tube that immobilizes the regolith (the keeper) was not seated in the tube properly. This meant that (1) the drive tube could not be removed from the CSVC for the trip to UTCT, and (2) the procedure for opening and extruding the drive tube had to be modified. Had either of these things not been known prior to opening the CSVC, it could have led to an inability to XCT scan the whole core at high resolution and/or potential disruption of the core stratigraphy during extrusion. At UTCT, the entire length of the core was scanned at high resolution (12.9 microns per voxel). This scan serves multiple purposes: (1) A lower resolution (and uncorrected) version of these scans stitched together was used to help inform the processors of potential pitfalls during extrusion and dissection (voids, angular fragments at the edges of the sample, etc.); and (2) the full resolution corrected data will serve as the permanent in situ record of the stratigraphy of the sample and will enable future researchers to perform a variety of analyses. All 121 >4 mm particles separated during dissection pass 1 of sample 73001 have been individually scanned. These scans clearly show the lithology of each particle while keeping the particles in pristine condition (they are individually triply bagged in Teflon within our N2 purged processing cabinets). Because of the dust adhering to particle exteriors, it would otherwise be impossible to determine lithologies in a non-contaminating way. Thus far the types of lithologies seen in sample 73001 (e.g., regolith breccias, impact-melt breccias, agglutinates, and bas-alts) are similar to those previously identified in sample 73002 [2]. By the time of the meeting, all particles from all 3 dissection passes will have been scanned and statistics on the different lithologies in 73001 compiled. References: [1] Shearer et al. (2020) 51st LPSC, abstract 1181. [2] Zeigler et al. (2020) 51st LPSC, abstract 3023. [3] Kent et al. (2022) This Volume. [4] McDonald et al. (2022) European Lunar Symposium. [5] Gross et al (2022) This volume.

Moon↗

Experimental evaluation of the ignition process of carbon monoxide and oxygen in a rocket engine

Carbon monoxide and oxygen ignition boundaries were determined in a spark torch igniter as a function of propellant inlet temperatures. The oxygen temperature was varied from ambient to -258 F, and the carbon monoxide temperature was varied from ambient to -241 F. With the oxygen and carbon monoxide at -253 F and -219 F, respectively, they successfully ignited between mixture ratios of 2.42 and 3.10. Analysis of the results indicated that the lower ignition boundary was more sensitive to oxygen temperature than to carbon monoxide temperature. Another series of tests was performed in a small simulated rocket engine with oxygen at -197 F and carbon monoxide at -193 F. An oxygen/hydrogen flame was used to initiate combustion of the oxygen and carbon monoxide. Tests performed at the optimum operating mixture ratio of 0.55 obtained steady-state combustion in every test.

Linne, Diane L.↗

Simulating Operations at a Spaceport

SPACESIM is a computer program for detailed simulation of operations at a spaceport. SPACESIM is being developed to greatly improve existing spaceports and to aid in designing, building, and operating future spaceports, given that there is a worldwide trend in spaceport operations from very expensive, research- oriented launches to more frequent commercial launches. From an operational perspective, future spaceports are expected to resemble current airports and seaports, for which it is necessary to resolve issues of safety, security, efficient movement of machinery and people, cost effectiveness, timeliness, and maximizing effectiveness in utilization of resources. Simulations can be performed, for example, to (1) simultaneously analyze launches of reusable and expendable rockets and identify bottlenecks arising from competition for limited resources or (2) perform what-if scenario analyses to identify optimal scenarios prior to making large capital investments. SPACESIM includes an object-oriented discrete-event-simulation engine. (Discrete- event simulation has been used to assess processes at modern seaports.) The simulation engine is built upon the Java programming language for maximum portability. Extensible Markup Language (XML) is used for storage of data to enable industry-standard interchange of data with other software. A graphical user interface facilitates creation of scenarios and analysis of data.

Nevins, Michael R.↗

Discovering Digital Engineering Needs Through Human-Centered Approaches

Digital engineering has the power to transform organizations in profound ways, but digitizing legacy workflows and infusing new technologies into existing practices may not yield the intended results or address the underlying problems or bottlenecks. This paper describes the human-centered approaches used to understand stakeholder challenges and identify digital engineering needs during the design-build-test portion of the systems development lifecycle. Through a series of interactive stakeholder workshops and need-finding activities, key stakeholder needs were identified to help guide the integration of digital engineering technologies. The overarching need was for downstream system development steps to be considered further upstream in the project lifecycle in a manner that allows for proactive and interactive co-constructive idea exploration, problem resolution, and requirements considerations in a collective engagement with engineers and technicians from multiple disciplines to increase efficiency and reduce risks while offering opportunities to improve the final engineered system. Supporting this need was a wide-ranging desire from stakeholders for digital and non-digital support structures for efficient rapid iteration during system development. This work yielded several improvements for system development processes and for digital engineering infusion.

Human-centered Design↗

Discovering Digital Engineering Needs Through Human-Centered Approaches

Digital engineering has the power to transform organizations in profound ways, but digitizing legacy workflows and infusing new technologies into existing practices may not yield the intended results or address the underlying problems or bottlenecks. This paper describes the human-centered approaches used to understand stakeholder challenges and identify digital engineering needs during the design-build-test portion of the systems development lifecycle. Through a series of interactive stakeholder workshops and need-finding activities, key stakeholder needs were identified to help guide the integration of digital engineering technologies. The overarching need was for downstream system development steps to be considered further upstream in the project lifecycle in a manner that allows for proactive and interactive co-constructive idea exploration, problem resolution, and requirements considerations in a collective engagement with engineers and technicians from multiple disciplines to increase efficiency and reduce risks while offering opportunities to improve the final engineered system. Supporting this need was a wide-ranging desire from stakeholders for digital and non-digital support structures for efficient rapid iteration during system development. This work yielded several improvements for system development processes and for digital engineering infusion.

Design Science↗

The Ames-Lockheed orbiter processing scheduling system

A general purpose scheduling system and its application to Space Shuttle Orbiter Processing at the Kennedy Space Center (KSC) are described. Orbiter processing entails all the inspection, testing, repair, and maintenance necessary to prepare the Shuttle for launch and takes place within the Orbiter Processing Facility (OPF) at KSC, the Vehicle Assembly Building (VAB), and on the launch pad. The problems are extremely combinatoric in that there are thousands of tasks, resources, and other temporal considerations that must be coordinated. Researchers are building a scheduling tool that they hope will be an integral part of automating the planning and scheduling process at KSC. The scheduling engine is domain independent and is also being applied to Space Shuttle cargo processing problems as well as wind tunnel scheduling problems.

Zweben, Monte↗

Characterization of Hybrid Rocket Internal Heat Flux and HTPB Fuel Pyrolysis

None given. From statement of problem:The broad nature of this work has been to extend our understanding of the nature of the conventional or classical hybrid rocket combustion process (fuel decomposition, heat and mass transfer, and chemical reaction), and the critical engineering parameters that define this process.

rocket↗

Automation and Process Improvement Enables a Small Team to Operate a Low Thrust Mission in Orbit Around the Asteroid Vesta

NASA's Dawn mission to the asteroid Vesta and dwarf planet Ceres launched September 27, 2007 and arrived at Vesta in July of 2011. This mission uses ion propulsion to achieve the necessary delta-V to reach and maneuver at Vesta and Ceres. This paper will show how the evolution of ground system automation and process improvement allowed a relatively small engineering team to transition from cruise operations to asteroid operations while maintaining robust processes. The cruise to Vesta phase lasted almost 4 years and consisted of activities that were built with software tools, but each tool was open loop and required engineers to review the output to ensure consistency. Additionally, this same time period was characterized by the evolution from manually retrieved and reviewed data products to automatically generated data products and data value checking. Furthermore, the team originally took about three to four weeks to design and build about four weeks of spacecraft activities, with spacecraft contacts only once a week. Operations around the asteroid Vesta increased the tempo dramatically by transitioning from one contact a week to three or four contacts a week, to fourteen contacts a week (every 12 hours). This was accompanied by a similar increase in activity complexity as well as very fast turn around activity design and build cycles. The design process became more automated and the tools became closed loop, allowing the team to build more activities without sacrificing rigor. Additionally, these activities were dependent on the results of flight system performance, so more automation was added to analyze the flight data and provide results in a timely fashion to feed the design cycle. All of this automation and process improvement enabled up the engineers to focus on other aspects of spacecraft operations, including spacecraft health monitoring and anomaly resolution.

ground system automation↗

The NASA quiet engine program.

The NASA quiet engine program will incorporate all available noise-reduction technology into a propulsion system suitable for subsonic civil transport aircraft. Full-scale experimental hardware is being built and tested primarily for noise performance. The program is in process, and component and engine tests to date indicate that it is possible to achieve or exceed noise reduction objectives of 15-20 PNdB below the levels of 707/DC-8 long-range transport aircraft.

Kramer, J. J.↗

Test plan pressure fed thrust chamber technology

Aerojet is developing the technology for the design of a reliable, low cost, efficient, and lightweight LOX/RP-1 pressure fed engine. This technology program is a direct result of Aerojet's liquid rocket booster (LRB) study and previous NASA studies that identified liquid engines using high bulk density hydrocarbon fuels as very attractive for a space transportation system (STS). Previous large thrust LOX/RP-1 engine development programs were characterized by costly development problems due to combustion instability damage. The combustion stability solution was typically obtained through trial and error methods of minimizing instability damage by degrading engine performance. The approach to this program was to utilize existing and newly developed combustion analysis models and design methodology to create a thrust chamber design with features having the potential of producing reliable and efficient operation. This process resulted in an engine design with a unique high thrust-per-element OFO triplet injector utilizing a low cost modular approach. Cost efficient ablative materials are baselined for the injector face and chamber. Technology demonstration will be accomplished through a hot fire test program using appropriately sized subscale hardware. This subscale testing will provide a data base to supplement the current industry data bank and to anchor and validate the applied analysis models and design methodology. Once anchored and validated, these analysis models and design methodology can be applied with greatly increased confidence to design and characterize a large scale pressure fed LOX/RP-1 thrust chamber. The objective of this test program is to generate a data base that can be used to anchor and validate existing analysis models and design methodologies and to provide early concept demonstration of a low cost, efficient LOX/RP-1 thrust chamber. Test conditions and hardware instrumentation were defined to provide data sufficient to characterize combustion stability, performance, and thermal operation over a wide thrust chamber throttling range.

Dunn, Glenn↗