Search NASA⌕ Search

SEARCH · Search NASA

Results for “engineering process”

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 505 records · Page 28
All sourcesNASA NTRSDOE OSTI
NASA NTRS1990

Reliability growth modeling analysis of the space shuttle main engines based upon the Weibull process

The Weibull process, identified as the inhomogeneous Poisson process with the Weibull intensity function, is used to model the reliability growth assessment of the space shuttle main engine test and flight failure data. Additional tables of percentage-point probabilities for several different values of the confidence coefficient have been generated for setting (1-alpha)100-percent two sided confidence interval estimates on the mean time between failures. The tabled data pertain to two cases: (1) time-terminated testing, and (2) failure-terminated testing. The critical values of the three test statistics, namely Cramer-von Mises, Kolmogorov-Smirnov, and chi-square, were calculated and tabled for use in the goodness of fit tests for the engine reliability data. Numerical results are presented for five different groupings of the engine data that reflect the actual response to the failures.

Wheeler, J. T.↗
NASA NTRS1992

Practical quality control tools for curves and surfaces

Curves (geometry) and surfaces created by Computer Aided Geometric Design systems in the engineering environment must satisfy two basic quality criteria: the geometric shape must have the desired engineering properties; and the objects must be parameterized in a way which does not cause computational difficulty for geometric processing and engineering analysis. Interactive techniques are described which are in use at Boeing to evaluate the quality of aircraft geometry prior to Computational Fluid Dynamic analysis, including newly developed methods for examining surface parameterization and its effects.

Small, Scott G.↗
NASA NTRS1992

Fortran for the nineties

Fortran has largely enjoyed prominence for the past few decades as the computer programming language of choice for numerically intensive scientific, engineering, and process control applications. Fortran's well understood static language syntax has allowed resulting parsers and compiler optimizing technologies to often generate among the most efficient and fastest run-time executables, particularly on high-end scalar and vector supercomputers. Computing architectures and paradigms have changed considerably since the last ANSI/ISO Fortran release in 1978, and while FORTRAN 77 has more than survived, it's aged features provide only partial functionality for today's demanding computing environments. The simple block procedural languages have been necessarily evolving, or giving way, to specialized supercomputing, network resource, and object-oriented paradigms. To address these new computing demands, ANSI has worked for the last 12-years with three international public reviews to deliver Fortran 90. Fortran 90 has superseded and replaced ISO FORTRAN 77 internationally as the sole Fortran standard; while in the US, Fortran 90 is expected to be adopted as the ANSI standard this summer, coexisting with ANSI FORTRAN 77 until at least 1996. The development path and current state of Fortran will be briefly described highlighting the many new Fortran 90 syntactic and semantic additions which support (among others): free form source; array syntax; new control structures; modules and interfaces; pointers; derived data types; dynamic memory; enhanced I/O; operator overloading; data abstraction; user optional arguments; new intrinsics for array, bit manipulation, and system inquiry; and enhanced portability through better generic control of underlying system arithmetic models. Examples from dynamical astronomy, signal and image processing will attempt to illustrate Fortran 90's applicability to today's general scalar, vector, and parallel scientific and engineering requirements and object oriented programming paradigms. Time permitting, current work proceeding on the future development of Fortran 2000 and collateral standards will be introduced.

Himer, J. T.↗
NASA NTRS1999

Ninth Thermal and Fluids Analysis Workshop Proceedings

The Ninth Thermal and Fluids Analysis Workshop (TFAWS 98) was held at the Ohio Aerospace Institute in Cleveland, Ohio from August 31 to September 4, 1998. The theme for the hands-on training workshop and conference was "Integrating Computational Fluid Dynamics and Heat Transfer into the Design Process." Highlights of the workshop (in addition to the papers published herein) included an address by the NASA Chief Engineer, Dr. Daniel Mulville; a CFD short course by Dr. John D. Anderson of the University of Maryland; and a short course by Dr. Robert Cochran of Sandia National Laboratories. In addition, lectures and hands-on training were offered in the use of several cutting-edge engineering design and analysis-oriented CFD and Heat Transfer tools. The workshop resulted in international participation of over 125 persons representing aerospace and automotive industries, academia, software providers, government agencies, and private corporations. The papers published herein address issues and solutions related to the integration of computational fluid dynamics and heat transfer into the engineering design process. Although the primary focus is aerospace, the topics and ideas presented are applicable to many other areas where these and other disciplines are interdependent.

Sakowski, Barbara↗
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↗
NASA NTRS1992

In the soft-to-hard technical spectrum: Where is software engineering?

In the computer journals and tabloids, there have been a plethora of articles written about the software engineering field. But while advocates of the need for an engineering approach to software development, it is impressive how many authors have treated the subject of software engineering without adequately addressing the fundamentals of what engineering as a discipline consists of. A discussion is presented of the various related facets of this issue in a logical framework to advance the thesis that the software development process is necessarily an engineering process. The purpose is to examine more of the details of the issue of whether or not the design and development of software for digital computer processing systems should be both viewed and treated as a legitimate field of professional engineering. Also, the type of academic and professional level education programs that would be required to support a software engineering discipline is examined.

Leibfried, Theodore F.↗
NASA NTRS1998

The Isothermal Dendritic Growth Experiment

The growth of dendrites is one of the commonly observed forms of solidification encountered when metals and alloys freeze under low thermal gradients, as occurs in most casting and welding processes. In engineering alloys, the details of the dendritic morphology directly relates to important material responses and properties. Of more generic interest, dendritic growth is also an archetypical problem in morphogenesis, where a complex pattern evolves from simple starting conditions. Thus, the physical understanding and mathematical description of how dendritic patterns emerge during the growth process are of interest to both scientists and engineers. The Isothermal Dendritic Growth Experiment (IDGE) is a basic science experiment designed to measure, for a fundamental test of theory, the kinetics and morphology of dendritic growth without complications induced by gravity-driven convection. The IDGE, a collaboration between Rensselaer Polytechnic Institute, in Troy NY, and NASA's Lewis Research Center (LeRC) was developed over a ten year period from a ground-based research program into a space flight experiment. Important to the success of this flight experiment was provision of in situ near-real-time teleoperations during the spaceflight experiment.

Glicksman, M. E.↗
NASA NTRS2002

New Method Developed to Measure Contact Angles of a Sessile Drop

The spreading of an evaporating liquid on a solid surface occurs in many practical processes and is of importance in a number of practical situations such as painting, textile dyeing, coating, gluing, and thermal engineering. Typical processes involving heat transfer where the contact angle plays an important role are film cooling, boiling, and the heat transfer through heat pipes. The biological phenomenon of cell spreading also is analogous to a drop spreading (ref. 1). In the study of spreading, the dynamic contact angle describes the interfacial properties on solid substrates and, therefore, has been studied by physicists and fluid mechanics investigators. The dynamic contact angle of a spreading nonvolatile liquid drop provides a simple tool in the study of the free-boundary problem, but the study of the spreading of a volatile liquid drop is of more practical interest because the evaporation of common liquids is inevitable in practical processes. The most common method to measure the contact angle, the contact radius, and the height of a sessile drop on a solid surface is to view the drop from its edge through an optical microscope. However, this method gives only local information in the view direction. Zhang and Yang (ref. 2) developed a laser shadowgraphy method to investigate the evaporation of sessile drop on a glass plate. As described here, Zhang and Chao (refs. 3 and 4) improved the method and suggested a new optical arrangement to measure the dynamic contact angle and the instant evaporation rate of a sessile drop with much higher accuracy (less than 1 percent). With this method, any fluid motion in the evaporating drop can be visualized through shadowgraphy without using a tracer, which often affects the field under investigation.

Chao, David F.↗
NASA NTRS2011

Model-Based Systems Engineering for Capturing Mission Architecture System Processes with an Application Case Study - Orion Flight Test 1

Model-based Systems Engineering (MBSE) is an emerging methodology that can be leveraged to enhance many system development processes. MBSE allows for the centralization of an architecture description that would otherwise be stored in various locations and formats, thus simplifying communication among the project stakeholders, inducing commonality in representation, and expediting report generation. This paper outlines the MBSE approach taken to capture the processes of two different, but related, architectures by employing the Systems Modeling Language (SysML) as a standard for architecture description and the modeling tool MagicDraw. The overarching goal of this study was to demonstrate the effectiveness of MBSE as a means of capturing and designing a mission systems architecture. The first portion of the project focused on capturing the necessary system engineering activities that occur when designing, developing, and deploying a mission systems architecture for a space mission. The second part applies activities from the first to an application problem - the system engineering of the Orion Flight Test 1 (OFT-1) End-to-End Information System (EEIS). By modeling the activities required to create a space mission architecture and then implementing those activities in an application problem, the utility of MBSE as an approach to systems engineering can be demonstrated.

Orion Flight Test 1 (OFT-1)↗
NASA NTRS2023

Human Systems Integration: Managing Risk in Anesthesia

The practice of anesthesia relies on clinicians’ ability to safely manage increasingly complex equipment. Devices such as ventilators, drug infusion pumps, and physiologic monitors use sophisticated algorithms to deliver care, but most clinicians are only trained to manage automated systems during normal operation. Few if any receive training on how to manage system failures. Although manufacturers are required to consult with human factors engineers as part of the equipment design process, most pieces of equipment are ultimately brought to market without extensive input from clinicians. Systems in the operating room can be as simple as an oxygen tank, or as complex as a multi-institutional healthcare organization. Humans are also a complex system, and play a critical role in the domains of operations, design, fabrication, maintenance, repair, and ultimately, dismantling and closeout. HSI seeks to provide a means for advocating the human side of the system. Human Systems Integration (HSI) is the cross disciplinary process used as part of the Systems Engineering process to reduce risk in systems. HSI professionals consider the human, hardware, and software elements of system design to optimize system performance and improve safety. HSI professionals work in domains of study that include training, management, human factors engineering, safety, and occupational health, among others. This article discusses the role of systems in the practice of anesthesia, and how consideration of the human during all phases of the system life cycle helps manage risks and promote a better patient outcome.

Human Factors↗
NASA NTRS2016

Meanline Analysis of Turbines with Choked Flow in the Object-Oriented Turbomachinery Analysis Code

The prediction of turbomachinery performance characteristics is an important part of the conceptual aircraft engine design process. During this phase, the designer must examine the effects of a large number of turbomachinery design parameters to determine their impact on overall engine performance and weight. The lack of detailed design information available in this phase necessitates the use of simpler meanline and streamline methods to determine the turbomachinery geometry characteristics and provide performance estimates prior to more detailed CFD (Computational Fluid Dynamics) analyses. While a number of analysis codes have been developed for this purpose, most are written in outdated software languages and may be difficult or impossible to apply to new, unconventional designs. The Object-Oriented Turbomachinery Analysis Code (OTAC) is currently being developed at NASA Glenn Research Center to provide a flexible meanline and streamline analysis capability in a modern object-oriented language. During the development and validation of OTAC, a limitation was identified in the code's ability to analyze and converge turbines as the flow approached choking. This paper describes a series of changes which can be made to typical OTAC turbine meanline models to enable the assessment of choked flow up to limit load conditions. Results produced with this revised model setup are provided in the form of turbine performance maps and are compared to published maps.

Choked Flow↗
NASA NTRS2009

Human Factors Interface with Systems Engineering for NASA Human Spaceflights

This paper summarizes the past and present successes of the Habitability and Human Factors Branch (HHFB) at NASA Johnson Space Center s Space Life Sciences Directorate (SLSD) in including the Human-As-A-System (HAAS) model in many NASA programs and what steps to be taken to integrate the Human-Centered Design Philosophy (HCDP) into NASA s Systems Engineering (SE) process. The HAAS model stresses systems are ultimately designed for the humans; the humans should therefore be considered as a system within the systems. Therefore, the model places strong emphasis on human factors engineering. Since 1987, the HHFB has been engaging with many major NASA programs with much success. The HHFB helped create the NASA Standard 3000 (a human factors engineering practice guide) and the Human Systems Integration Requirements document. These efforts resulted in the HAAS model being included in many NASA programs. As an example, the HAAS model has been successfully introduced into the programmatic and systems engineering structures of the International Space Station Program (ISSP). Success in the ISSP caused other NASA programs to recognize the importance of the HAAS concept. Also due to this success, the HHFB helped update NASA s Systems Engineering Handbook in December 2007 to include HAAS as a recommended practice. Nonetheless, the HAAS model has yet to become an integral part of the NASA SE process. Besides continuing in integrating HAAS into current and future NASA programs, the HHFB will investigate incorporating the Human-Centered Design Philosophy (HCDP) into the NASA SE Handbook. The HCDP goes further than the HAAS model by emphasizing a holistic and iterative human-centered systems design concept.

Wong, Douglas T.↗
NASA NTRS1972

Integration of safety engineering into a cost optimized development program.

A six-segment management model is presented, each segment of which represents a major area in a new product development program. The first segment of the model covers integration of specialist engineers into 'systems requirement definition' or the system engineering documentation process. The second covers preparation of five basic types of 'development program plans.' The third segment covers integration of system requirements, scheduling, and funding of specialist engineering activities into 'work breakdown structures,' 'cost accounts,' and 'work packages.' The fourth covers 'requirement communication' by line organizations. The fifth covers 'performance measurement' based on work package data. The sixth covers 'baseline requirements achievement tracking.'

Ball, L. W.↗
NASA NTRS2006

Characterization and Analyses of Valves, Feed Lines and Tanks used in Propellant Delivery Systems at NASA SSC

Accurate modeling of liquid rocket engine test processes involves assessing critical fluid mechanic and heat and mass transfer mechanisms within a cryogenic environment, and accurately modeling fluid properties such as vapor pressure and liquid and gas densities as a function of pressure and temperature. The Engineering and Science Directorate at the NASA John C. Stennis Space Center has developed and implemented such analytic models and analysis processes that have been used over a broad range of thermodynamic systems and resulted in substantial improvements in rocket propulsion testing services. In this paper, we offer an overview of the analyses techniques used to simulate pressurization and propellant fluid systems associated with the test stands at the NASA John C. Stennis Space Center. More specifically, examples of the global performance (one-dimensional) of a propellant system are provided as predicted using the Rocket Propulsion Test Analysis (RPTA) model. Computational fluid dynamic (CFD) analyses utilizing multi-element, unstructured, moving grid capability of complex cryogenic feed ducts, transient valve operation, and pressurization and mixing in propellant tanks are provided as well.

Ryan, Harry M.↗
NASA NTRS2010

General Pressurization Model in Simscape

System integration is an essential part of the engineering design process. The Ares I Upper Stage (US) is a complex system which is made up of thousands of components assembled into subsystems including a J2-X engine, liquid hydrogen (LH2) and liquid oxygen (LO2) tanks, avionics, thrust vector control, motors, etc. System integration is the task of connecting together all of the subsystems into one large system. To ensure that all the components will "fit together" as well as safety and, quality, integration analysis is required. Integration analysis verifies that, as an integrated system, the system will behave as designed. Models that represent the actual subsystems are built for more comprehensive analysis. Matlab has been an instrument widely use by engineers to construct mathematical models of systems. Simulink, one of the tools offered by Matlab, provides multi-domain graphical environment to simulate and design time-varying systems. Simulink is a powerful tool to analyze the dynamic behavior of systems over time. Furthermore, Simscape, a tool provided by Simulink, allows users to model physical (such as mechanical, thermal and hydraulic) systems using physical networks. Using Simscape, a model representing an inflow of gas to a pressurized tank was created where the temperature and pressure of the tank are measured over time to show the behavior of the gas. By further incorporation of Simscape into model building, the full potential of this software can be discovered and it hopefully can become a more utilized tool.

Servin, Mario↗
NASA NTRSDate not supplied

Probabalistic Risk Analysis and Thermal Margin Process for an Inflatable Aeroshell

Uncertainties always exist in atmospheric entry aeroheating environments and the thermal response of thermal protection system (TPS) material. These uncertainties are mitigated in the design by ap-plying margin and factors of safety to the TPS. Entry vehicle TPS is often conservatively over-sized for the heat loads that are experienced along the entry trajectory by stacking worst-case scenarios together. Additionally, the current TPS design and margin process used by NASA offers very little insight into the risk of over-temperature during flight and the reliability of the heat shield performance [1,3]. A probabilistic margin process can be used to calculate the amount of TPS margin necessary to survive a given entry heat load at a specified level of risk [2,3,4]. The vehicle’s initial entry state (entry velocity, flight path angle, and entry mass) determines the expected atmospheric entry environmental conditions and resulting heat load that the entry vehicle will experience. If there is flexibility in the entry state, then this process can be used to select an appropriate combination of entry state parameters and TPS size to target a desired reentry reliability. This probabilistic margin process allows engineers to make informed aeroshell design, entry-trajectory design, and TPS performance risk trades while preventing excessive TPS margin from being applied. The probabilistic TPS margin process has been performed to determine TPS thickness and entry heating constraints given an acceptable risk level for the Low Earth Orbit Flight Experiment of an Inflatable Decelerator (LOFTID) flight project. The process is used in a manner to size the entry heat load for a given flexible TPS (FTPS) thickness so that it meets project reliability standards while allowing the FTPS and the underlying inflatable structure (IS) to be pushed to adequately high temperatures. Since the LOFTID project is an experimental flight demonstration, it is de-sired to drive the FTPS and IS to temperatures that cover a large range of their thermal response models’ applicability. This will allow the thermal response models to be better improved and validated post-flight using LOFTID’s extensive instrumentation embedded within the aeroshell. The presentation demonstrates how uncertainty analysis is carried out using an end-to-end Monte Carlo process where three separate Monte Carlo simulations are run in sequence. The first Monte Carlo simulation operates on the entry trajectory model to generate trajectory parameter dispersions that are fed into the second Monte Carlo simulation. The second Monte Carlo simulation operates on the aerothermodynamics model to generate aeroheating parameter dispersions that are fed into the third Monte Carlo simulation. The third Monte Carlo simulation operates on the FTPS material thermal response model to generate the final FTPS/IS thermal response dispersions. The end-to-end Monte Carlo simulation propagates the uncertainties of each model into the next to quantify the resulting uncertainty of the FTPS/IS thermal response. The fractional contributions of the uncertain parameters in the trajectory, aerothermal, and thermal response models to the variance in the FTPS/IS thermal response is determined as a byproduct of the Monte Carlo analysis. The structural uncertainty of the FTPS thermal response model is evaluated by flight relevant ground testing and model error analysis using test measurements. This probabilistic TPS margin process had never been applied to an entry vehicle and it is one of the LOFTID project’s goals to demonstrate its merits.

Steven A. Tobin↗
NASA NTRS2016

A Structured, Model-Based Systems Engineering Methodology for Operations System Design

Two widely accepted techniques for lowering the cost and risk of developing systems are (1) the use of a defined systems engineering (SE) process or methodology and (2) the reuse of existing (previously built) system components. The first technique is represented, for example, in materials published by NASA (e.g., NASA Systems Engineering Handbook) or by professional societies such as INCOSE (International Council on Systems Engineering). Well-formed SE techniques provide value by establishing the proper scope of the system (e.g., requirements), and by identifying and resolving problems relatively early in project lifecycles, when fixes are less expensive. The second technique (reuse) is applied most commonly to hardware and software; it seeks to avoid replicating design and implementation costs while also reducing risk by placing proven capabilities into operational use. In this paper, we outline a methodology combining these two techniques and extending reuse beyond hardware and software to foundational aspects of a Mission Operation System’s (MOS) design. We describe the system design artifacts that result (e.g., requirements, design documentation), as well as the reusable patterns and elements of the design, and their interrelationships. This approach is enabled by model-based systems engineering (MBSE) techniques and tools and is currently available in SysML form as a plug-in to MagicDraw. Additionally, usage of a rigorous MBSE approach allows for training materials and tutorials to be packaged within the overall model itself. The results of such an approach include decreased cost and risk during the design phase, improved ability of the MOS development team to investigate trade spaces and identify impacts to important flight-ground trade studies. Such results extend into decreased costs and risk in later phases due to improved design, decreased need for late fixes or development of "glue-ware" or scripts to fill unanticipated gaps in functionality, and improved ability to identify and plan testing and other validation activities. Finally, lower operational costs can be expected, both due to improved quality of the MOS, increased ease of maintaining updated knowledge of system configuration, and the fact that training and procedural materials are also updated at the same time as accepted system changes.

Bindschadler, Duane L.↗