Search NASA⌕ Search

SEARCH · Search NASA

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 775 records · Page 43
All sourcesNASA NTRSDOE OSTI
NASA NTRS1987

A computer program for performance prediction of tripropellant rocket engines with tangential slot injection

For the development of a Heavy Lift Launch Vehicle (HLLV) several engines with different operating cycles and using LOX/Hydrocarbon propellants are presently being examined. Some concepts utilize hydrogen for thrust chamber wall cooling followed by a gas generator turbine drive cycle with subsequent dumping of H2/O2 combustion products into the nozzle downstream of the throat. In the Space Transportation Booster Engine (STBE) selection process the specific impulse will be one of the optimization criteria; however, the current performance prediction programs do not have the capability to include a third propellant in this process, nor to account for the effect of dumping the gas-generator product tangentially inside the nozzle. The purpose is to describe a computer program for accurately predicting the performance of such an engine. The code consists of two modules; one for the inviscid performance, and the other for the viscous loss. For the first module, the two-dimensional kinetics program (TDK) was modified to account for tripropellant chemistry, and for the effect of tangential slot injection. For the viscous loss, the Mass Addition Boundary Layer program (MABL) was modified to include the effects of the boundary layer-shear layer interaction, and tripropellant chemistry. Calculations were made for a real engine and compared with available data.

Dang, Anthony↗
NASA NTRS1994

The Evolution of Technology in the Deep Space Network: A History of the Advanced Systems Program

The Deep Space Network (DSN) of 1995 might be described as the evolutionary result of 45 years of deep space communication and navigation, together with the synergistic activities of radio science and radar and radio astronomy. But the evolution of the DSN did not just happen - it was carefully planned and created. The evolution of the DSN has been an ongoing engineering activity, and engineering is a process of problem solving under constraints, one of which is technology. In turn, technology is the knowledge base providing the capability and experience for practical application of various areas of science, when needed. The best engineering solutions result from optimization under the fewest constraints, and if technology needs are well anticipated (ready when needed), then the most effective engineering solution is possible. Throughout the history of the DSN it has been the goal and function of DSN advanced technology development (designated the DSN Advanced Systems Program from 1963 through 1994) to supply the technology needs of the DSN when needed, and thus to minimize this constraint on DSN engineering. Technology often takes considerable time to develop, and when that happens, it is important to have anticipated engineering needs; at times, this anticipation has been by as much as 15 years. Also, on a number of occasions, mission malfunctions or emergencies have resulted in unplanned needs for technology that has, in fact, been available from the reservoir of advanced technology provided by the DSN Advanced Systems Program. Sometimes, even DSN engineering personnel fail to realize that the organization of JPL permits an overlap of DSN advanced technology activities with subsequent engineering activities. This can result in the flow of advanced technology into DSN engineering in a natural and sometimes almost unnoticed way. In the following pages, we will explore some of the many contributions of the DSN Advanced Systems Program that were provided to DSN Engineering and Implementation. These contributions are, for the most part, unique capabilities that have met the requirements of flight projects for 45 years. These unique capabilities include not only the world's best deep-space communications system, but also outstanding competency in the fields of radio metric measurement, radar and radio astronomy, and radio science.

Layland, J. W.↗
NASA NTRS1993

Repository-Based Software Engineering Program: Working Program Management Plan

Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents.

Source record↗
NASA NTRS2021

NASA Human Systems Integration Handbook

This handbook is intended to provide general guidance and information on Human Systems Integration (HSI) for the NASA community and the applicability of HSI to NASA programs and projects. The primary goals are to increase awareness and consistency across the Agency, advance the practice and implementation of HSI principles, and provide invaluable information and guidance to HSI practitioners in the performance of their duties. Specific aims of this handbook are to define HSI, illustrate the value of HSI in programmatic decisions, demonstrate how HSI fits into the NASA project life cycle process, describe how HSI applies across all three NASA Technical Authorities, provide guidance on HSI processes and products, and provide helpful information on HSI resources within the NASA community. Largely within the engineering community, a system is thought of as the integration or assemblance of hardware and software that together perform a function. HSI considers a system to be the integration of hardware, software, humans, data, and processes, where the human in HSI refers to all personnel involved with a given system, including system owners, users/customers, operators, maintainers, assemblers, support personnel, logistics suppliers, training personnel, test personnel, and others. This handbook should be used as a companion for implementing NPR 7123.1, Systems Engineering Processes and Requirements, the NASA Systems Engineering Handbook, NASA directives, and any Center-specific handbooks and directives developed for implementing programs and projects. As of 2021, both NPR 7123.1 and NPR 7120.5 require HSI to be implemented within NASA technical efforts.

Lisa O Rippy↗
NASA NTRS1922

Engine Pistons of Light Metal

This report presents the results of testing 32 sets of light metal pistons from 16 different aluminum and magnesium alloys, 2 sets of cast iron pistons, and one piston of pure electrolytic copper. The many-fold mutual relations between material properties, shape, thermic and dynamic processes in the engine were clarified by comprehensive technical, thermic, chemical, physical and metallographic investigations of pistons and piston materials.

PISTONS↗
NASA NTRS1996

Contamination control engineering design guidelines for the aerospace community

Thermal control surfaces, solar arrays, and optical devices may be adversely affected by a small quantity of molecular and/or particulate contamination. What is rarely discussed is how one: (1) quantifies the level of contamination that must be maintained in order for the system to function properly, and (2) enforces contamination control to ensure compliance with requirements. This document is designed to address these specific issues and is intended to serve as a handbook on contamination control for the reader, illustrating process and methodology while providing direction to more detailed references when needed. The effects of molecular contamination on reflecting and transmitting surfaces are examined and quantified in accordance with MIL STD 1246C. The generation, transportation, and deposition of molecular contamination is reviewed and specific examples are worked to illustrate the process a design engineer can use to estimate end of life cleanliness levels required by solar arrays, thermal control surfaces, and optical surfaces. A similar process is used to describe the effect of particulate contamination as related to percent area coverage (PAC) and bi-directional reflectance distribution function (BRDF). Relationships between PAC and surface cleanliness, which include the effects of submicron sized particles, are developed and BRDF is related to specific sensor design parameters such as Point Source Transmittance (PST). The pros and cons of various methods of preventing, monitoring, and cleaning surfaces are examined and discussed.

Tribble, A. C.↗
NASA NTRS1980

Combustion and operating characteristics of spark-ignition engines

The spark-ignition engine turbulent flame propagation process was investigated. Then, using a spark-ignition engine cycle simulation and combustion model, the impact of turbocharging and heat transfer variations or engine power, efficiency, and NO sub x emissions was examined.

Heywood, J. B.↗
NASA NTRS1981

Process feasibility study in support of silicon material task 1

Results for process system properties, chemical engineering and economic analyses of the new technologies and processes being developed for the production of lower cost silicon for solar cells are presented. Analyses of process system properties are important for chemical materials involved in the several processes under consideration for semiconductor and solar cell grade silicon production. Major physical, thermodynamic and transport property data are reported for silicon source and processing chemical materials.

Yaws, C. L.↗
NASA NTRS2011

Multi-Center Implementation of NPR 7123.1A: A Collaborative Effort

Collaboration efforts between MSFC and GRC Engineering Directorates to implement the NASA Systems Engineering (SE) Engine have expanded over the past year to include other NASA Centers. Sharing information on designing, developing, and deploying SE processes has sparked further interest based on the realization that there is relative consistency in implementing SE processes at the institutional level. This presentation will provide a status on the ongoing multi-center collaboration and provide insight into how these NPR 7123.1A SE-aligned directives are being implemented and managed to better support the needs of NASA programs and projects. NPR 7123.1A, NASA Systems Engineering Processes and Requirements, was released on March 26, 2007 to clearly articulate and establish the requirements on the implementing organization for performing, supporting, and evaluating SE activities. In early 2009, MSFC and GRC Engineering Directorates undertook a collaborative opportunity to share their research and work associated with developing, updating and revising their SE process policy to comply and align with NPR 7123.1A. The goal is to develop instructions, checklists, templates, and procedures for each of the 17 SE process requirements so that systems engineers will be a position to define work that is process-driven. Greater efficiency and more effective technical management will be achieved due to consistency and repeatability of SE process implementation across and throughout each of the NASA centers. An added benefit will be to encourage NASA centers to pursue and collaborate on joint projects as a result of using common or similar processes, methods, tools, and techniques.

Hall, Phillip B.↗
NASA NTRS1994

Lessons learned in transitioning to an open systems environment

Software development organizations, both commercial and governmental, are undergoing rapid change spurred by developments in the computing industry. To stay competitive, these organizations must adopt new technologies, skills, and practices quickly. Yet even for an organization with a well-developed set of software engineering models and processes, transitioning to a new technology can be expensive and risky. Current industry trends are leading away from traditional mainframe environments and toward the workstation-based, open systems world. This paper presents the experiences of software engineers on three recent projects that pioneered open systems development for NASA's Flight Dynamics Division of the Goddard Space Flight Center (GSFC).

Boland, Dillard E.↗
NASA NTRS2011

Fault Management Guiding Principles

Regardless of the mission type: deep space or low Earth orbit, robotic or human spaceflight, Fault Management (FM) is a critical aspect of NASA space missions. As the complexity of space missions grows, the complexity of supporting FM systems increase in turn. Data on recent NASA missions show that development of FM capabilities is a common driver for significant cost overruns late in the project development cycle. Efforts to understand the drivers behind these cost overruns, spearheaded by NASA's Science Mission Directorate (SMD), indicate that they are primarily caused by the growing complexity of FM systems and the lack of maturity of FM as an engineering discipline. NASA can and does develop FM systems that effectively protect mission functionality and assets. The cost growth results from a lack of FM planning and emphasis by project management, as well the maturity of FM as an engineering discipline, which lags behind the maturity of other engineering disciplines. As a step towards controlling the cost growth associated with FM development, SMD has commissioned a multi-institution team to develop a practitioner's handbook representing best practices for the end-to-end processes involved in engineering FM systems. While currently concentrating primarily on FM for science missions, the expectation is that this handbook will grow into a NASA-wide handbook, serving as a companion to the NASA Systems Engineering Handbook. This paper presents a snapshot of the principles that have been identified to guide FM development from cradle to grave. The principles range from considerations for integrating FM into the project and SE organizational structure, the relationship between FM designs and mission risk, and the use of the various tools of FM (e.g., redundancy) to meet the FM goal of protecting mission functionality and assets.

principles↗
NASA NTRS2010

Characterization and Evaluation of Lunar Regolith and Simulants

A NASA-ESMD (National Aeronautics and Space Administration-Exploration Systems Mission Directorate) funded senior design project "Mineral Separation Technology for Lunar Regolith Simulant Production" is directed toward designing processes to produce Simulant materials as close to lunar regolith as possible. The eight undergraduate (junior and senior) students involved are taking a systems engineering design approach to identifying the most pressing concerns in simulant needs, then designing subsystems and processing strategies to meet these needs using terrestrial materials. This allows the students to, not only learn the systems engineering design process, but also, to make a significant contribution to an important NASA ESMD project. This paper will primarily be focused on the implementation aspect, particularly related to the systems engineering process, of this NASA EMSD senior design project. In addition comparison of the NASA ESMD group experience to the implementation of systems engineering practices into a group of existing design projects is given.

Cross, William M.↗
NASA NTRS1987

The evolution of the Mission Control Center

A discussion of the function and history of the Space Shuttle Mission Control Center describes the communications and data processing facilities, with an emphasis on display system changes. The current display system will be replaced by new technology as part of a project called the Mission Control Center Upgrade. That upgrade will implement a set of high-performance Local Area Networks (LANs) which transmit real-time and historical data to engineering workstations for processing and display. The benefits from such an architecture include a more flexible software development environment and a more modular system which will promote future upgrades. The proposed upgrade architecture is explored, and the engineering and project management challenges of that effort are described, emphasizing the local area networks task.

Kearney, Michael W., III↗
NASA NTRS2003

The Role of Design-of-Experiments in Managing Flow in Compact Air Vehicle Inlets

It is the purpose of this study to demonstrate the viability and economy of Design-of-Experiments methodologies to arrive at microscale secondary flow control array designs that maintain optimal inlet performance over a wide range of the mission variables and to explore how these statistical methods provide a better understanding of the management of flow in compact air vehicle inlets. These statistical design concepts were used to investigate the robustness properties of low unit strength micro-effector arrays. Low unit strength micro-effectors are micro-vanes set at very low angles-of-incidence with very long chord lengths. They were designed to influence the near wall inlet flow over an extended streamwise distance, and their advantage lies in low total pressure loss and high effectiveness in managing engine face distortion. The term robustness is used in this paper in the same sense as it is used in the industrial problem solving community. It refers to minimizing the effects of the hard-to-control factors that influence the development of a product or process. In Robustness Engineering, the effects of the hard-to-control factors are often called noise , and the hard-to-control factors themselves are referred to as the environmental variables or sometimes as the Taguchi noise variables. Hence Robust Optimization refers to minimizing the effects of the environmental or noise variables on the development (design) of a product or process. In the management of flow in compact inlets, the environmental or noise variables can be identified with the mission variables. Therefore this paper formulates a statistical design methodology that minimizes the impact of variations in the mission variables on inlet performance and demonstrates that these statistical design concepts can lead to simpler inlet flow management systems.

Anderson, Bernhard H.↗
NASA NTRS1991

Lessons learned for composite structures

Lessons learned for composite structures are presented in three technology areas: materials, manufacturing, and design. In addition, future challenges for composite structures are presented. Composite materials have long gestation periods from the developmental stage to fully matured production status. Many examples exist of unsuccessful attempts to accelerate this gestation period. Experience has shown that technology transition of a new material system to fully matured production status is time consuming, involves risk, is expensive and should not be undertaken lightly. The future challenges for composite materials require an intensification of the science based approach to material development, extension of the vendor/customer interaction process to include all engineering disciplines of the end user, reduced material costs because they are a significant factor in overall part cost, and improved batch-to-batch pre-preg physical property control. Historical manufacturing lessons learned are presented using current in-service production structure as examples. Most producibility problems for these structures can be traced to their sequential engineering design. This caused an excessive emphasis on design-to-weight and schedule at the expense of design-to-cost. This resulted in expensive performance originated designs, which required costly tooling and led to non-producible parts. Historically these problems have been allowed to persist throughout the production run. The current/future approach for the production of affordable composite structures mandates concurrent engineering design where equal emphasis is placed on product and process design. Design for simplified assembly is also emphasized, since assembly costs account for a major portion of total airframe costs. The future challenge for composite manufacturing is, therefore, to utilize concurrent engineering in conjunction with automated manufacturing techniques to build affordable composite structures. Composite design experience has shown that significant weight savings have been achieved, outstanding fatigue and corrosion resistance have been demonstrated, and in-service performance has been very successful. Currently no structural design show stoppers exist for composite structures. A major lesson learned is that the full scale static test is the key test for composites, since it is the primary structural 'hot spot' indicator. The major durability issue is supportability of thin skinned structure. Impact damage has been identified as the most significant issue for the damage tolerance control of composite structures. However, delaminations induced during assembly operations have demonstrated a significant nuisance value. The future challenges for composite structures are threefold. Firstly, composite airframe weight fraction should increase to 60 percent. At the same time, the cost of composite structures must be reduced by 50 percent to attain the goal of affordability. To support these challenges it is essential to develop lower cost materials and processes.

Whitehead, R. S.↗
NASA NTRS1996

Spaceflight Safety on the North Coast of America

Spaceflight Safety (SFS) engineers at NASA Lewis Research Center (LeRC) are responsible for evaluating the microgravity fluids and combustion experiments, payloads and facilities developed at NASA LeRC which are manifested for spaceflight on the Space Shuttle, the Russian space station Mir, and/or the International Space Station (ISS). An ongoing activity at NASA LeRC is the comprehensive training of its SFS engineers through the creation and use of safety tools and processes. Teams of SFS engineers worked on the development of an Internet website (containing a spaceflight safety knowledge database and electronic templates of safety products) and the establishment of a technical peer review process (known as the Safety Assurance for Lewis Spaceflight Activities (SALSA) review).

Ciancone, Michael L.↗
NASA NTRS1994

STEP: A Futurevision, Today

STEP (STandard for the Exchange of Product Model Data) is an innovative software tool that allows the exchange of data between different programming systems to occur and helps speed up the designing in various process industries. This exchange occurs easily between those companies that have STEP, and many industries and government agencies are requiring that their vendors utilize STEP in their computer aided design projects, such as in the areas of mechanical, aeronautical, and electrical engineering. STEP allows the process of concurrent engineering to occur and increases the quality of the design product. One example of the STEP program is the Boeing 777, the first paperless airplane.

Source record↗
NASA NTRS1984

An investigation of enhanced capability thermal barrier coating systems for diesel engine components

Material systems and processes for the development of effective and durable thermal barriers for heavy duty diesel engines were investigated. Seven coating systems were evaluated for thermal conductivity, erosion resistance, corrosion/oxidation resistance, and thermal shock resistance. An advanced coating system based on plasma sprayed particle yttria stabilized zirconia (PS/HYSZ) was judged superior in these tests. The measured thermal conductivity of the selected coating was 0.893 W/m C at 371 C. The PS/HYSZ coating system was applied to the piston crown, fire deck and valves of a single cylinder low heat rejection diesel engine. The coated engine components were tested for 24 hr at power levels from 0.83 MPa to 1.17 MPa brake mean effective pressure. The component coatings survived the engine tests with a minimum of distress. The measured fire deck temperatures decreased 86 C (155 F) on the intake side and 42 C (75 F) on the exhaust side with the coating applied.

Holtzman, R. L.↗