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 937 records · Page 52
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

How Engineers Really Think About Risk: A Study of JPL Engineers

The objectives of this work are: To improve risk assessment practices as used during the mission design process by JPL's concurrent engineering teams. (1) Developing effective ways to identify and assess mission risks (2) Providing a process for more effective dialog between stakeholders about the existence and severity of mission risks (3) Enabling the analysis of interactions of risks across concurrent engineering roles.

risk identification↗
NASA NTRS1999

Advanced Technology Inlet Design, NRA 8-21 Cycle II: DRACO Flowpath Hypersonic Inlet Design

The report outlines work performed in support of the flowpath development for the DRACO engine program. The design process initiated to develop a hypersonic axisymmetric inlet for a Mach 6 rocket-based combined cycle (RBCC) engine is discussed. Various design parametrics were investigated, including design shock-on-lip Mach number, cone angle, throat Mach number, throat angle. length of distributed compression, and subsonic diffuser contours. Conceptual mechanical designs consistent with installation into the D-21 vehicle were developed. Additionally, program planning for an intensive inlet development program to support a Critical Design Review in three years was performed. This development program included both analytical and experimental elements and support for a flight-capable inlet mechanical design.

Sanders, Bobby W.↗
NASA NTRS2010

An Integrated Architecture for On-Board Aircraft Engine Performance Trend Monitoring and Gas Path Fault Diagnostics

Aircraft engine performance trend monitoring and gas path fault diagnostics are closely related technologies that assist operators in managing the health of their gas turbine engine assets. Trend monitoring is the process of monitoring the gradual performance change that an aircraft engine will naturally incur over time due to turbomachinery deterioration, while gas path diagnostics is the process of detecting and isolating the occurrence of any faults impacting engine flow-path performance. Today, performance trend monitoring and gas path fault diagnostic functions are performed by a combination of on-board and off-board strategies. On-board engine control computers contain logic that monitors for anomalous engine operation in real-time. Off-board ground stations are used to conduct fleet-wide engine trend monitoring and fault diagnostics based on data collected from each engine each flight. Continuing advances in avionics are enabling the migration of portions of the ground-based functionality on-board, giving rise to more sophisticated on-board engine health management capabilities. This paper reviews the conventional engine performance trend monitoring and gas path fault diagnostic architecture commonly applied today, and presents a proposed enhanced on-board architecture for future applications. The enhanced architecture gains real-time access to an expanded quantity of engine parameters, and provides advanced on-board model-based estimation capabilities. The benefits of the enhanced architecture include the real-time continuous monitoring of engine health, the early diagnosis of fault conditions, and the estimation of unmeasured engine performance parameters. A future vision to advance the enhanced architecture is also presented and discussed

Simon, Donald L.↗
NASA NTRS1980

IPAD project overview

To respond to national needs for improved productivity in engineering design and manufacturing, a NASA supported joint industry/government project is underway denoted Integrated Programs for Aerospace-Vehicle Design (IPAD). The objective is to improve engineering productivity through better use of computer technology. It focuses on development of technology and associated software for integrated company-wide management of engineering information. The project has been underway since 1976 under the guidance of an Industry Technical Advisory Board (ITAB) composed of representatives of major engineering and computer companies and in close collaboration with the Air Force Integrated Computer-Aided Manufacturing (ICAM) program. Results to date on the IPAD project include an in-depth documentation of a representative design process for a large engineering project, the definition and design of computer-aided design software needed to support that process, and the release of prototype software to integrate selected design functions. Ongoing work concentrates on development of prototype software to manage engineering information, and initial software is nearing release.

Fulton, R. E.↗
NASA NTRSDate not supplied

Generative Design and Digital Manufacturing: Using AI and Robots to Build Lightweight Instruments

Digital Engineering technologies are transforming long-stagnant development processes by applying the tremendous advancements in Information Technology (IT) to classical engineering tasks such as design, analysis, and fabrication of space-flight instrument structures. Generative Design leverages developments in Artificial Intelligence (AI) and Cloud computing to enable a paradigm shift in the design process, allowing the engineer to focus on defining the requirements and objectives of the design while AI generates optimized designs which comply with the input requirements. Digital Manufacturing allows these complex lightweight designs to be efficiently manufactured by directly fabricating from the resulting 3D models. The development of these two Digital Engineering technologies realizes significant mass savings while simultaneously reducing structure development time from months to days. This paper describes the development of the Evolved Structures process applying these technologies to spaceflight optical instrument structures including an example demonstrating greater than 10x reduction in development time/cost and greater than 3x improvement in structural performance.

Ryan McClelland↗
NASA NTRS2002

ISO 9000 and/or Systems Engineering Capability Maturity Model?

For businesses and organizations to remain competitive today they must have processes and systems in place that will allow them to first identify customer needs and then develop products/processes that will meet or exceed the customers needs and expectations. Customer needs, once identified, are normally stated as requirements. Designers can then develop products/processes that will meet these requirements. Several functions, such as quality management and systems engineering management are used to assist product development teams in the development process. Both functions exist in all organizations and both have a similar objective, which is to ensure that developed processes will meet customer requirements. Are efforts in these organizations being duplicated? Are both functions needed by organizations? What are the similarities and differences between the functions listed above? ISO 9000 is an international standard of goods and services. It sets broad requirements for the assurance of quality and for management's involvement. It requires organizations to document the processes and to follow these documented processes. ISO 9000 gives customers assurance that the suppliers have control of the process for product development. Systems engineering can broadly be defined as a discipline that seeks to ensure that all requirements for a system are satisfied throughout the life of the system by preserving their interrelationship. The key activities of systems engineering include requirements analysis, functional analysis/allocation, design synthesis and verification, and system analysis and control. The systems engineering process, when followed properly, will lead to higher quality products, lower cost products, and shorter development cycles. The System Engineering Capability Maturity Model (SE-CMM) will allow companies to measure their system engineering capability and continuously improve those capabilities. ISO 9000 and SE-CMM seem to have a similar objective, which is to document the organization's processes and certify to potential customers the capability of a supplier to control the processes that determine the quality of the product or services being produced. The remaining sections of this report examine the differences and similarities between ISO 9000 and SE-CMM and make recommendations for implementation.

Sampson E. Gholston↗
NASA NTRS2005

State Analysis: A Control Architecture View of Systems Engineering

A viewgraph presentation on the state analysis process is shown. The topics include: 1) Issues with growing complexity; 2) Limits of common practice; 3) Exploiting a control point of view; 4) A glimpse at the State Analysis process; 5) Synergy with model-based systems engineering; and 6) Bridging the systems to software gap.

state analysis↗
NASA NTRS2007

Shuttle Entry Imaging Using Infrared Thermography

During the Columbia Accident Investigation, imaging teams supporting debris shedding analysis were hampered by poor entry image quality and the general lack of information on optical signatures associated with a nominal Shuttle entry. After the accident, recommendations were made to NASA management to develop and maintain a state-of-the-art imagery database for Shuttle engineering performance assessments and to improve entry imaging capability to support anomaly and contingency analysis during a mission. As a result, the Space Shuttle Program sponsored an observation campaign to qualitatively characterize a nominal Shuttle entry over the widest possible Mach number range. The initial objectives focused on an assessment of capability to identify/resolve debris liberated from the Shuttle during entry, characterization of potential anomalous events associated with RCS jet firings and unusual phenomenon associated with the plasma trail. The aeroheating technical community viewed the Space Shuttle Program sponsored activity as an opportunity to influence the observation objectives and incrementally demonstrate key elements of a quantitative spatially resolved temperature measurement capability over a series of flights. One long-term desire of the Shuttle engineering community is to calibrate boundary layer transition prediction methodologies that are presently part of the Shuttle damage assessment process using flight data provided by a controlled Shuttle flight experiment. Quantitative global imaging may offer a complementary method of data collection to more traditional methods such as surface thermocouples. This paper reviews the process used by the engineering community to influence data collection methods and analysis of global infrared images of the Shuttle obtained during hypersonic entry. Emphasis is placed upon airborne imaging assets sponsored by the Shuttle program during Return to Flight. Visual and IR entry imagery were obtained with available airborne imaging platforms used within DoD along with agency assets developed and optimized for use during Shuttle ascent to demonstrate capability (i.e., tracking, acquisition of multispectral data, spatial resolution) and identify system limitations (i.e., radiance modeling, saturation) using state-of-the-art imaging instrumentation and communication systems. Global infrared intensity data have been transformed to temperature by comparison to Shuttle flight thermocouple data. Reasonable agreement is found between the flight thermography images and numerical prediction. A discussion of lessons learned and potential application to a potential Shuttle boundary layer transition flight test is presented.

Horvath, Thomas↗
NASA NTRS2015

Review of Exploration Systems Development (ESD) Integrated Hazard Development Process: Appendices - Volume 1

The Chief Engineer of the Exploration Systems Development (ESD) Office requested that the NASA Engineering and Safety Center (NESC) perform an independent assessment of the ESD's integrated hazard development process. The focus of the assessment was to review the integrated hazard analysis (IHA) process and identify any gaps/improvements in the process (e.g., missed causes, cause tree completeness, missed hazards). This document contains the outcome of the NESC assessment.

Smiles, Michael D.↗
NASA NTRS2015

Review of Exploration Systems Development (ESD) Integrated Hazard Development Process: Volume 2 - Appendices

The Chief Engineer of the Exploration Systems Development (ESD) Office requested that the NASA Engineering and Safety Center (NESC) perform an independent assessment of the ESD's integrated hazard development process. The focus of the assessment was to review the integrated hazard analysis (IHA) process and identify any gaps/improvements in the process (e.g. missed causes, cause tree completeness, missed hazards). This document contains the outcome of the NESC assessment.

Smiles, Michael D.↗
NASA NTRS1991

Advanced Turbine Technology Applications Project (ATTAP)

ATTAP activities were highlighted by test bed engine design and development activities; ceramic component design; materials and engine component characterization; ceramic component process development and fabrication; component rig testing; and test bed engine fabrication and testing. Specifically, ATTAP aims to develop and demonstrate the technology of structural ceramics that have the potential for competitive automotive engine life cycle cost and for operating for 3500 hours in a turbine engine environment at temperatures up to 1371 C (2500 F).

Source record↗
NASA NTRS1993

STS-56, RSRM-031, 360L031 KSC processing configuration and data report

KSC Processing Configuration and Data Report is being provided as a historical document and as an enhancement to future RSRM manufacturing and processing operations. The following sections provide information on segment receipt, aft booster build-up, booster assembly, and closeout for STS-56, RSRM flight set 36OL031. Section 2.0 contains a summary of RSRM-031 processing. Section 3.0 discusses any significant problems or special issues that require special attention. Sections 4.0 through 6.0 contain narrative descriptions of all key events, including any related processing problems. Appendix A provides engineering specifications and changes. A list and matrix of all problem reports (PR's) pertinent to this flight set is provided in Appendix B. The matrix was provided by the Thiokol LSS Quality Engineering office. Copies of the PR's generated during the processing of RSRM-031 will be provided upon request. Appendix C contains the motor set status matrix, which provides milestone dates for the RSRM-031 flow. Section 7.0 provides recommendations, if any, for the improvement of flight hardware processing. Section 8.0 contains data sheets that provide flight hardware parts and consumables information installed during the booster build-up and stacking operations by location, lot/serial number, expiration and cure dates/times, and installation dates.

Source record↗
NASA NTRS1993

STS-51, RSRM-033, 360T033 KSC processing configuration and data report

KSC Processing Configuration and Data Report is being provided as a historical document and as an enhancement to future RSRM manufacturing and processing operations. The following sections provide information on segment receipt, aft booster build up, motor assembly, and closeout for STS-51, RSRM flight set 360T033. Section 2.0 contains a summary of RSRM-033 processing. Section 3.0 discusses any significant problems or special issues that require special attention. Sections 4.0 through 6.0 contain narrative descriptions of all key events, including any related processing problems. Appendix A provides engineering specifications and changes. A list and matrix of all problem reports (PR's) pertinent to this flight set is provided in Appendix B. The matrix was provided by the Thiokol LSS Quality Engineering office. Copies of the PR's generated during the processing of RSRM-033 will be provided upon request. Appendix C contains the motor set status matrix, which provides milestone dates for the RSRM-033 flow. Section 7.0 provides recommendations for the improvement of flight hardware processing. Section 8.0 contains data sheets that provide flight hardware parts and consumable information installed during the booster build-up and stacking operations by location, lot/serial number, expiration and cure dates/times, and installation dates.

Hillard, Robert C.↗
NASA NTRS2008

Generating Safety-Critical PLC Code From a High-Level Application Software Specification

The benefits of automatic-application code generation are widely accepted within the software engineering community. These benefits include raised abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at Kennedy Space Center recognized the need for PLC code generation while developing the new ground checkout and launch processing system, called the Launch Control System (LCS). Engineers developed a process and a prototype software tool that automatically translates a high-level representation or specification of application software into ladder logic that executes on a PLC. All the computer hardware in the LCS is planned to be commercial off the shelf (COTS), including industrial controllers or PLCs that are connected to the sensors and end items out in the field. Most of the software in LCS is also planned to be COTS, with only small adapter software modules that must be developed in order to interface between the various COTS software products. A domain-specific language (DSL) is a programming language designed to perform tasks and to solve problems in a particular domain, such as ground processing of launch vehicles. The LCS engineers created a DSL for developing test sequences of ground checkout and launch operations of future launch vehicle and spacecraft elements, and they are developing a tabular specification format that uses the DSL keywords and functions familiar to the ground and flight system users. The tabular specification format, or tabular spec, allows most ground and flight system users to document how the application software is intended to function and requires little or no software programming knowledge or experience. A small sample from a prototype tabular spec application is shown.

Source record↗
NASA NTRS2020

Analysis of the Honeywell Uncertified Research Engine with Ice Crystal Cloud Ingestion at Simulated Altitudes

The Honeywell Uncertified Research Engine (HURE), a research version of a turbofan engine that never entered production, was tested in the NASA Propulsion System Laboratory (PSL), an altitude test facility at the NASA Glenn Research Center. The PSL is a facility that is equipped with water spray bars capable of producing an ice cloud consisting of ice particles, having a controlled particle diameter and concentration in the air flow. To develop the test matrix of the HURE, numerical analysis of flow and ice particle thermodynamics was performed on the compression system of the turbofan engine to predict operating conditions that could potentially result in a risk of ice accretion due to ice crystal ingestion. The goal of the test matrix was to provide operating conditions such that ice would accrete in either the fan-stator through the inlet guide vane region of the compression system or within the first stator of the high pressure compressor. The predictive analyses were performed with the mean line compressor flow modeling code (COMDESMELT) which includes an ice particle model. The HURE engine was tested in PSL with the ice cloud over the range of operating conditions of altitude, ambient temperature, simulated flight Mach number, and fan speed with guidance from the analytical predictions. The engine was fitted with video cameras at strategic locations within the engine compression system flow path where ice was predicted to accrete, in order to visually confirm ice accretion when it occurred. In addition, traditional compressor instrumentation such as total pressure and temperature probes, static pressure taps, and metal temperature thermocouples were installed in targeted areas where the risk of ice accretion was expected. The current research focuses on the analysis of the data that was obtained after testing the HURE engine in PSL with ice crystal ingestion. The computational method (COMDES-MELT) was enhanced by computing key parameters through the fan-stator at multiple span wise locations, in order to increase the fidelity with the current mean-line method. The Icing Wedge static wet-bulb temperature thresholds were applied for determining the risk of ice accretion in the fan-stator, which is thought to be an adiabatic region. At some operating conditions near the splitter-lip region, other sources of heat (non-adiabatic walls) were suspected to be the cause of accretion, and the Icing Wedge was not applied to predict accretion at that location. A simple order-of-magnitude heat transfer model was implemented into the COMDES-MELT code to estimate the wall temperature minimum and maximum thresholds that support ice accretion, as observed by video confirmation. The results from this model spanned the range of wall temperatures measured on a previous engine that experienced ice accretion at certain operating conditions. The goal of this study is to show that the computational process developed on earlier engine icing tests can be used to provide an icing risk assessment in adiabatic regions for other engines.

Turbofan engine↗
NASA NTRS2007

Decision Support Systems for Launch and Range Operations Using Jess

The virtual test bed for launch and range operations developed at NASA Ames Research Center consists of various independent expert systems advising on weather effects, toxic gas dispersions and human health risk assessment during space-flight operations. An individual dedicated server supports each expert system and the master system gather information from the dedicated servers to support the launch decision-making process. Since the test bed is based on the web system, reducing network traffic and optimizing the knowledge base is critical to its success of real-time or near real-time operations. Jess, a fast rule engine and powerful scripting environment developed at Sandia National Laboratory has been adopted to build the expert systems providing robustness and scalability. Jess also supports XML representation of knowledge base with forward and backward chaining inference mechanism. Facts added - to working memory during run-time operations facilitates analyses of multiple scenarios. Knowledge base can be distributed with one inference engine performing the inference process. This paper discusses details of the knowledge base and inference engine using Jess for a launch and range virtual test bed.

Thirumalainambi, Rajkumar↗