Search NASA⌕ Search

SEARCH · Search NASA

Results for “Process Systems 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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
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 NTRS2016

Expanded Guidance for NASA Systems Engineering. Volume 2: Crosscutting Topics, Special Topics, and Appendices

Historically, most successful NASA projects have depended on effectively blending project management, systems engineering, and technical expertise among NASA, contractors, and third parties. Underlying these successes are a variety of agreements (e.g., contract, memorandum of understanding, grant, cooperative agreement) between NASA organizations or between NASA and other Government agencies, Government organizations, companies, universities, research laboratories, and so on. To simplify the discussions, the term "contract" is used to encompass these agreements. This section focuses on the NASA systems engineering activities pertinent to awarding a contract, managing contract performance, and completing a contract. In particular, NASA systems engineering interfaces to the procurement process are covered, since the NASA engineering technical team plays a key role in the development and evaluation of contract documentation. Contractors and third parties perform activities that supplement (or substitute for) the NASA project technical team accomplishment of the NASA common systems engineering technical process activities and requirements outlined in this guide. Since contractors might be involved in any part of the systems engineering life cycle, the NASA project technical team needs to know how to prepare for, allocate or perform, and implement surveillance of technical activities that are allocated to contractors.

Steven R Hirshorn↗
NASA NTRS2011

Jupiter Europa Orbiter Architecture Definition Process

The proposed Jupiter Europa Orbiter mission, planned for launch in 2020, is using a new architectural process and framework tool to drive its model-based systems engineering effort. The process focuses on getting the architecture right before writing requirements and developing a point design. A new architecture framework tool provides for the structured entry and retrieval of architecture artifacts based on an emerging architecture meta-model. This paper describes the relationships among these artifacts and how they are used in the systems engineering effort. Some early lessons learned are discussed.

requirements analysis↗
NASA NTRS1989

Parametric Cost Analysis: A Design Function

Parametric cost analysis uses equations to map measurable system attributes into cost. The measures of the system attributes are called metrics. The equations are called cost estimating relationships (CER's), and are obtained by the analysis of cost and technical metric data of products analogous to those to be estimated. Examples of system metrics include mass, power, failure_rate, mean_time_to_repair, energy _consumed, payload_to_orbit, pointing_accuracy, manufacturing_complexity, number_of_fasteners, and percent_of_electronics_weight. The basic assumption is that a measurable relationship exists between system attributes and the cost of the system. If a function exists, the attributes are cost drivers. Candidates for metrics include system requirement metrics and engineering process metrics. Requirements are constraints on the engineering process. From optimization theory we know that any active constraint generates cost by not permitting full optimization of the objective. Thus, requirements are cost drivers. Engineering processes reflect a projection of the requirements onto the corporate culture, engineering technology, and system technology. Engineering processes are an indirect measure of the requirements and, hence, are cost drivers.

Dean, Edwin B.↗
NASA NTRS2007

Environmental Testing of the NEXT PM1R Ion Engine

The NEXT propulsion system is an advanced ion propulsion system presently under development that is oriented towards robotic exploration of the solar system using solar electric power. The subsystem includes an ion engine, power processing unit, feed system components, and thruster gimbal. The Prototype Model engine PM1 was subjected to qualification-level environmental testing in 2006 to demonstrate compatibility with environments representative of anticipated mission requirements. Although the testing was largely successful, several issues were identified including the fragmentation of potting cement on the discharge and neutralizer cathode heater terminations during vibration which led to abbreviated thermal testing, and generation of particulate contamination from manufacturing processes and engine materials. The engine was reworked to address most of these findings, renamed PM1R, and the environmental test sequence was repeated. Thruster functional testing was performed before and after the vibration and thermal-vacuum tests. Random vibration testing, conducted with the thruster mated to the breadboard gimbal, was executed at 10.0 Grms for 2 min in each of three axes. Thermal-vacuum testing included three thermal cycles from 120 to 215 C with hot engine re-starts. Thruster performance was nominal throughout the test program, with minor variations in a few engine operating parameters likely caused by facility effects. There were no significant changes in engine performance as characterized by engine operating parameters, ion optics performance measurements, and beam current density measurements, indicating no significant changes to the hardware as a result of the environmental testing. The NEXT PM1R engine and the breadboard gimbal were found to be well-designed against environmental requirements based on the results reported herein. The redesigned cathode heater terminations successfully survived the vibration environments. Based on the results of this test program and confidence in the engineering solutions available for the remaining findings of the first test program, specifically the particulate contamination, the hardware environmental qualification program can proceed with confidence

Snyder, John S.↗
NASA NTRS1998

Launch and Propulsion Systems Materials and Process Development for Rocket Engine Components: Turbomachinery

This presentation identifies the key materials with the highest payoff to advance the state-of-the-art in materials for turbomachinery. Current show stoppers for advancing the state of the art in materials and processes were identified. Technical issues associated with incorporating key materials into new systems are discussed. Opportunities, where they exist, are identified to overcome these technical challenges.

Cannon, James L.↗
NASA NTRS2016

Exposing Hidden Parts of the SE Process: MBSE Patterns and Tools for Tracking and Traceability

An interesting benefit of applying Model-Based Systems Engineering (MBSE) is that the rigor and coordination intrinsic to MBSE forces us to apply Systems Engineering to our own traditional activities, processes, and products, which results in richer, more expressive models, more powerful reasoning, and a clearer and more effective Systems Engineering (SE) process. Our MBSE frameworks and languages contain semantic richness sufficient to describe our systems at any particular point in time, often with an emphasis on the description of the system at major milestones. This is unarguably a real asset. However, when we apply MBSE in service of missions that are in development, rapidly evolving, of a larger scale, and where interpersonal communication is a critical part of the design process, we discover that our frameworks and languages are still not quite rich enough to enable us to ask the kinds of questions and get the kinds of answers we want in order to address the concerns of day to day work. This paper will discuss some patterns and tools we have developed to help address some of the not-always-explicit SE concerns that we have identified through our MBSE work. Particularly, this paper will discuss flexible yet practical methods for defining and capturing maturity, workflow, and agreement traceability within our system models, extensible ways to perform and track model audits, and ways to report and interact with this knowledge in the context of MBSE applied to support NASA’s Europa Project.

Jackson, Maddalena↗
NASA NTRS2016

Exposing Hidden Parts of the SE Process: MBSE Patterns and Tools for Tracking and Traceability

An interesting benefit of applying Model-Based Systems Engineering (MBSE) is that the rigor and coordination intrinsic to MBSE forces us to apply Systems Engineering to our own traditional activities, processes, and products, which results in richer, more expressive models, more powerful reasoning, and a clearer and more effective Systems Engineering (SE) process. Our MBSE frameworks and languages contain semantic richness sufficient to describe our systems at any particular point in time, often with an emphasis on the description of the system at major milestones. This is unarguably a real asset. However, when we apply MBSE in service of missions that are in development, rapidly evolving, of a larger scale, and where interpersonal communication is a critical part of the design process, we discover that our frameworks and languages are still not quite rich enough to enable us to ask the kinds of questions and get the kinds of answers we want in order to address the concerns of day to day work. This paper will discuss some patterns and tools we have developed to help address some of the not-always-explicit SE concerns that we have identified through our MBSE work. Particularly, this paper will discuss flexible yet practical methods for defining and capturing maturity, workflow, and agreement traceability within our system models, extensible ways to perform and track model audits, and ways to report and interact with this knowledge in the context of MBSE applied to support NASA’s Europa Project

Jackson, Maddalena↗
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.↗
NASA NTRS2008

System Engineering on the Use for Ares I,V - the Simpler, the Better

The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt & Whitney Rocketdyne Company. The J-2X is an improved higher power version of the original J-2 engine used during the Apollo program. With higher power and updated requirements for safety and performance, the J-2X becomes a new engine using state-of-the-art design methodology, materials and manufacturing processes. The implementation of Systems Engineering (SE) principles enables the rapid J-2X development program to remain aligned with the ARES I and V vehicle programs, Meeting the aggressive development schedule is a challenge. Coordinating the best expertise thai NASA and PWR have to offer requires effectively utilizing resources at multiple sites. This presents formidable communication challenges. SE allows honest and open discussions of issues and problems. This simple idea is often overlooked in large and complex SE programs. Regular and effective meetings linking SE objectives to component designs are used to voice differences of opinions with customer and contractor in attendance so that the best mutual decisions can be made on the shortest possible schedule. Regular technical interchange meetings on secure program wide computer networks and CM processes are effective,in the "Controlled Change" process that exemplifies good SE. Good communication is a key effective SE implementation. The System of Systems approach is the vision of the Orion program which facilitates the establishment of dynamic SE processes at all levels including the engine. SE enables requirements evolution by facilitating organizational and process agility. Flow down and distribution of requirements is controlled by Allocation Reports which breakdown numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements helps eliminate redundancy and potential mistakes inherent m separated systems. Another tool, the Architecture Design Description, is being used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof is in successful program accomplishment. The SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. The Ares I SE system of systems has delivered according to expectations thus far. All major design reviews (SRR. PDR, CDR) have been successfully conducted to satisfy overall program objectives using SE as the basis for accomplishment. The paper describes SE tools and techniques utilized to achieve this success.

Kelly, William↗
NASA NTRS2017

Control Design for an Advanced Geared Turbofan Engine

This paper describes the design process for the control system of an advanced geared turbofan engine. This process is applied to a simulation that is representative of a 30,000 lbf thrust class concept engine with two main spools, ultra-high bypass ratio, and a variable area fan nozzle. Control system requirements constrain the non-linear engine model as it operates throughout its flight envelope of sea level to 40,000 ft and from 0 to 0.8 Mach. The control architecture selected for this project was developed from literature and reflects a configuration that utilizes a proportional integral controller integrated with sets of limiters that enable the engine to operate safely throughout its flight envelope. Simulation results show the overall system meets performance requirements without exceeding system operational limits.

aerothermodynamics↗
NASA NTRS2017

Control Design for an Advanced Geared Turbofan Engine

This paper describes the design process for the control system of an advanced geared turbofan engine. This process is applied to a simulation that is representative of a 30,000 lbf thrust class concept engine with two main spools, ultra-high bypass ratio, and a variable area fan nozzle. Control system requirements constrain the non-linear engine model as it operates throughout its flight envelope of sea level to 40,000 ft and from 0 to 0.8 Mach. The control architecture selected for this project was developed from literature and reflects a configuration that utilizes a proportional integral controller integrated with sets of limiters that enable the engine to operate safely throughout its flight envelope. Simulation results show the overall system meets performance requirements without exceeding system operational limits.

gas path dynamics↗
NASA NTRS2014

A Systems Engineering Approach to Quality Assurance for Aerospace Testing

On the surface, it appears that AS9100 has little to say about how to apply a Quality Management System (QMS) to major aerospace test programs (or even smaller ones). It also appears that there is little in the quality engineering Body of Knowledge (BOK) that applies to testing, unless it is nondestructive examination (NDE), or some type of lab or bench testing associated with the manufacturing process. However, if one examines: a) how the systems engineering (SE) processes are implemented throughout a test program; and b) how these SE processes can be mapped to the requirements of AS9100, a number of areas for involvement of the quality professional are revealed. What often happens is that quality assurance during a test program is limited to inspections of the test article; what could be considered a manufacturing al fresco approach. This limits the quality professional and is a disservice to the programs and projects, since there are a number of ways that quality can enhance critical processes, and support efforts to improve risk reduction, efficiency and effectiveness. The Systems Engineering (SE) discipline is widely used in aerospace to ensure the progress from Stakeholder Expectations (the President, Congress, the taxpayers) to a successful, delivered product or service. Although this is well known, what is not well known is that these same SE processes are implemented in varying complexity, to prepare for and implement test projects that support research, development, verification and validation, qualification, and acceptance test projects. Although the test organization's terminology may vary from the SE terminology, and from one test service provider to another, the basic process is followed by successful, reliable testing organizations. For this analysis, NASA Procedural Requirements (NPR) 7123.1, NASA Systems Engineering Processes and Requirements is used to illustrate the SE processes that are used for major aerospace testing. Many of these processes are also implemented for smaller test projects, and this set of processes will also look familiar to those who have participated in launch site activation and flight demonstrations.

Shepherd, Christena C.↗
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 NTRS2013

Virtual Construction of Space Habitats: Connecting Building Information Models (BIM) and SysML

Current trends in design, construction and management of complex projects make use of Building Information Models (BIM) connecting different types of data to geometrical models. This information model allow different types of analysis beyond pure graphical representations. Space habitats, regardless their size, are also complex systems that require the synchronization of many types of information and disciplines beyond mass, volume, power or other basic volumetric parameters. For this, the state-of-the-art model based systems engineering languages and processes - for instance SysML - represent a solid way to tackle this problem from a programmatic point of view. Nevertheless integrating this with a powerful geometrical architectural design tool with BIM capabilities could represent a change in the workflow and paradigm of space habitats design applicable to other aerospace complex systems. This paper shows some general findings and overall conclusions based on the ongoing research to create a design protocol and method that practically connects a systems engineering approach with a BIM architectural and engineering design as a complete Model Based Engineering approach. Therefore, one hypothetical example is created and followed during the design process. In order to make it possible this research also tackles the application of IFC categories and parameters in the aerospace field starting with the application upon the space habitats design as way to understand the information flow between disciplines and tools. By building virtual space habitats we can potentially improve in the near future the way more complex designs are developed from very little detail from concept to manufacturing.

space architecture↗
NASA NTRS1990

SE and I system testability: The key to space system FDIR and verification testing

The key to implementing self-diagnosing design is a systems engineering task focused on design for testability concurrent with design for functionality. The design for testability process described here is the product of several years of DOD study and experience. Its application to the space station has begun on Work Package II under NASA and McDonnell direction. Other work package teams are being briefed by Harris Corporation with the hope of convincing them to embrace the process. For the purpose of this discussion the term testability is used to describe the systems engineering process by which designers can assure themselves and their reviewers that their designs are TESTABLE, that is they will support the downstream process of determining their functionality. Due to the complexity and density of present-day state-of-the-art designs, such as pipeline processors and high-speed integrated circuit technology, testability feature design is a critical requirement of the functional design process. A systematic approach to Space systems test and checkout as well as fault detection fault isolation reconfiguration (FDFIR) will minimize operational costs and maximize operational efficiency. An effective design for the testability program must be implemented by all contractors to insure meeting this objective. The process is well understood and technology is here to support it.

Barry, Thomas↗