Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

RDD-100 and the systems engineering process

An effective systems engineering approach applied through the project life cycle can help Langley produce a better product. This paper demonstrates how an enhanced systems engineering process for in-house flight projects assures that each system will achieve its goals with quality performance and within planned budgets and schedules. This paper also describes how the systems engineering process can be used in combination with available software tools.

Averill, Robert D.↗
NASA NTRS2013

Implementation of a Goal-Based Systems Engineering Process Using the Systems Modeling Language (SysML)

This paper describes the core framework used to implement a Goal-Function Tree (GFT) based systems engineering process using the Systems Modeling Language. It defines a set of principles built upon by the theoretical approach described in the InfoTech 2013 ISHM paper titled "Goal-Function Tree Modeling for Systems Engineering and Fault Management" presented by Dr. Stephen B. Johnson. Using the SysML language, the principles in this paper describe the expansion of the SysML language as a baseline in order to: hierarchically describe a system, describe that system functionally within success space, and allocate detection mechanisms to success functions for system protection.

Breckenridge, Jonathan T.↗
NASA NTRS2013

Implementation of a Goal-Based Systems Engineering Process Using the Systems Modeling Language (SysML)

Building upon the purpose, theoretical approach, and use of a Goal-Function Tree (GFT) being presented by Dr. Stephen B. Johnson, described in a related Infotech 2013 ISHM abstract titled "Goal-Function Tree Modeling for Systems Engineering and Fault Management", this paper will describe the core framework used to implement the GFTbased systems engineering process using the Systems Modeling Language (SysML). These two papers are ideally accepted and presented together in the same Infotech session. Statement of problem: SysML, as a tool, is currently not capable of implementing the theoretical approach described within the "Goal-Function Tree Modeling for Systems Engineering and Fault Management" paper cited above. More generally, SysML's current capabilities to model functional decompositions in the rigorous manner required in the GFT approach are limited. The GFT is a new Model-Based Systems Engineering (MBSE) approach to the development of goals and requirements, functions, and its linkage to design. As a growing standard for systems engineering, it is important to develop methods to implement GFT in SysML. Proposed Method of Solution: Many of the central concepts of the SysML language are needed to implement a GFT for large complex systems. In the implementation of those central concepts, the following will be described in detail: changes to the nominal SysML process, model view definitions and examples, diagram definitions and examples, and detailed SysML construct and stereotype definitions.

Patterson, Jonathan D.↗
NASA NTRS2013

Implementation of a Goal-Based Systems Engineering Process Using the Systems Modeling Language (SysML)

Building upon the purpose, theoretical approach, and use of a Goal-Function Tree (GFT) being presented by Dr. Stephen B. Johnson, described in a related Infotech 2013 ISHM abstract titled "Goal-Function Tree Modeling for Systems Engineering and Fault Management", this paper will describe the core framework used to implement the GFTbased systems engineering process using the Systems Modeling Language (SysML). These two papers are ideally accepted and presented together in the same Infotech session. Statement of problem: SysML, as a tool, is currently not capable of implementing the theoretical approach described within the "Goal-Function Tree Modeling for Systems Engineering and Fault Management" paper cited above. More generally, SysML's current capabilities to model functional decompositions in the rigorous manner required in the GFT approach are limited. The GFT is a new Model-Based Systems Engineering (MBSE) approach to the development of goals and requirements, functions, and its linkage to design. As a growing standard for systems engineering, it is important to develop methods to implement GFT in SysML. Proposed Method of Solution: Many of the central concepts of the SysML language are needed to implement a GFT for large complex systems. In the implementation of those central concepts, the following will be described in detail: changes to the nominal SysML process, model view definitions and examples, diagram definitions and examples, and detailed SysML construct and stereotype definitions.

Breckenridge, Jonathan T.↗
NASA NTRS2006

Selected Systems Engineering Process Deficiencies and Their Consequences

The systems engineering process is well established and well understood. While this statement could be argued in the light of the many systems engineering guidelines and that have been developed, comparative review of these respective descriptions reveal that they differ primarily in the number of discrete steps or other nuances, and are at their core essentially common. Likewise, the systems engineering textbooks differ primarily in the context for application of systems engineering or in the utilization of evolved tools and techniques, not in the basic method. Thus, failures in systems engineering cannot credibly be attributed to implementation of the wrong systems engineering process among alternatives. However, numerous systems failures can be attributed to deficient implementation of the systems engineering process. What may clearly be perceived as a system engineering deficiency in retrospect can appear to be a well considered system engineering efficiency in real time - an efficiency taken to reduce cost or meet a schedule, or more often both. Typically these efficiencies are grounded on apparently solid rationale, such as reuse of heritage hardware or software. Over time, unintended consequences of a systems engineering process deficiency may begin to be realized, and unfortunately often the consequence is system failure. This paper describes several actual cases of system failures that resulted from deficiencies in their systems engineering process implementation, including the Ariane 5 and the Hubble Space Telescope.

Thomas, Lawrence Dale↗
NASA NTRS1972

Methodology for the systems engineering process. Volume 1: System functional activities

Systems engineering is examined in terms of functional activities that are performed in the conduct of a system definition/design, and system development is described in a parametric analysis that combines functions, performance, and design variables. Emphasis is placed on identification of activities performed by design organizations, design specialty groups, as well as a central systems engineering organizational element. Identification of specific roles and responsibilities for doing functions, and monitoring and controlling activities within the system development operation are also emphasized.

Nelson, J. H.↗
NASA NTRS1971

Integrating system safety into the basic systems engineering process

The basic elements of a systems engineering process are given along with a detailed description of what the safety system requires from the systems engineering process. Also discussed is the safety that the system provides to other subfunctions of systems engineering.

John W. Griswold↗
NASA NTRS2005

The Systems Engineering Process for Human Support Technology Development

Systems engineering is designing and optimizing systems. This paper reviews the systems engineering process and indicates how it can be applied in the development of advanced human support systems. Systems engineering develops the performance requirements, subsystem specifications, and detailed designs needed to construct a desired system. Systems design is difficult, requiring both art and science and balancing human and technical considerations. The essential systems engineering activity is trading off and compromising between competing objectives such as performance and cost, schedule and risk. Systems engineering is not a complete independent process. It usually supports a system development project. This review emphasizes the NASA project management process as described in NASA Procedural Requirement (NPR) 7120.5B. The process is a top down phased approach that includes the most fundamental activities of systems engineering - requirements definition, systems analysis, and design. NPR 7120.5B also requires projects to perform the engineering analyses needed to ensure that the system will operate correctly with regard to reliability, safety, risk, cost, and human factors. We review the system development project process, the standard systems engineering design methodology, and some of the specialized systems analysis techniques. We will discuss how they could apply to advanced human support systems development. The purpose of advanced systems development is not directly to supply human space flight hardware, but rather to provide superior candidate systems that will be selected for implementation by future missions. The most direct application of systems engineering is in guiding the development of prototype and flight experiment hardware. However, anticipatory systems engineering of possible future flight systems would be useful in identifying the most promising development projects.

Jones, Harry↗
NASA NTRS1995

Generic Health Management: A System Engineering Process Handbook Overview and Process

Health Management, a System Engineering Process, is one of those processes-techniques-and-technologies used to define, design, analyze, build, verify, and operate a system from the viewpoint of preventing, or minimizing, the effects of failure or degradation. It supports all ground and flight elements during manufacturing, refurbishment, integration, and operation through combined use of hardware, software, and personnel. This document will integrate Health Management Processes (six phases) into five phases in such a manner that it is never a stand alone task/effort which separately defines independent work functions.

Wilson, Moses Lee↗
NASA NTRS2011

Space Shuttle Systems Engineering Processes for Liftoff Debris Risk Mitigation

This slide presentation reviews the systems engineering process designed to reduce the risk from debris during Space Shuttle Launching. This process begins the day of launch from the tanking to the vehicle tower clearance. Other debris risks (i.e., Ascent, and micrometeoroid orbital debit) are mentioned) but are not the subject of this presentation. The Liftoff debris systems engineering process and an example of how it works are reviewed (i.e.,STS-119 revealed a bolt liberation trend on the Fixed Service Structure (FSS) 275 level elevator room). The process includes preparation of a Certification of Flight Readiness (CoFR) that includes (1) Lift-off debris from previous mission dispositioned, (2) Flight acceptance rationale has been provided for Lift-off debris sources/causes (3) Lift-off debris mission support documentation, processes and tools are in place for the up-coming mission. The process includes a liftoff debris data collection that occurs after each launch. This includes a post launch walkdown, that records each liftoff debris, and the entry of the debris into a database, it also includes a review of the imagery from the launch, and a review of the instrumentation data. There is also a review of the debris transport analysis process, that includes temporal and spatial framework and a computational fluid dynamics (CFD) analysis. which incorporates a debris transport analyses (DTA), debris materials and impact tests, and impact analyses.

Mitchell, Michael↗
NASA NTRS2012

Tailoring Systems Engineering Processes in a Conceptual Design Environment: A Case Study at NASA Marshall Spaceflight Center's ACO

This paper provides an overview of Systems Engineering as it is applied in a conceptual design space systems department at the National Aeronautics and Space Administration (NASA) Marshall Spaceflight Center (MSFC) Advanced Concepts Office (ACO). Engineering work performed in the NASA MFSC's ACO is targeted toward the Exploratory Research and Concepts Development life cycle stages, as defined in the International Council on Systems Engineering (INCOSE) System Engineering Handbook. This paper addresses three ACO Systems Engineering tools that correspond to three INCOSE Technical Processes: Stakeholder Requirements Definition, Requirements Analysis, and Integration, as well as one Project Process Risk Management. These processes are used to facilitate, streamline, and manage systems engineering processes tailored for the earliest two life cycle stages, which is the environment in which ACO engineers work. The role of systems engineers and systems engineering as performed in ACO is explored in this paper. The need for tailoring Systems Engineering processes, tools, and products in the ever-changing engineering services ACO provides to its customers is addressed.

Mulqueen, John↗
NASA NTRS1989

Dynamic systems-engineering process - The application of concurrent engineering

A system engineering methodology is described which enables users, particulary NASA and DOD, to accommodate changing needs; incorporate emerging technologies; identify, quantify, and manage system risks; manage evolving functional requirements; track the changing environment; and reduce system life-cycle costs. The approach is a concurrent, dynamic one which starts by constructing a performance model defining the required system functions and the interrelationships. A detailed probabilistic risk assessment of the system elements and their interrelationships is performed, and quantitative analysis of the reliability and maintainability of an engineering system allows its different technical and process failure modes to be identified and their probabilities to be computed. Decision makers can choose technical solutions that maximize an objective function and minimize the probability of failure under resource constraints.

Wiskerchen, Michael J.↗
NASA NTRS2010

Risk Informed Design as Part of the Systems Engineering Process

This slide presentation reviews the importance of Risk Informed Design (RID) as an important feature of the systems engineering process. RID is based on the principle that risk is a design commodity such as mass, volume, cost or power. It also reviews Probabilistic Risk Assessment (PRA) as it is used in the product life cycle in the development of NASA's Constellation Program.

Deckert, George↗
NASA NTRS2018

Assessing Alternatives in the Systems Engineering Process: Case Study of an Earth Observing Satellite Concept

Defining design alternatives constitutes one of the critical initial steps of the systems engineering process. Once these design alternatives have been identified, assessing which alternatives best satisfy the project’s objectives can prove to be challenging when dealing with complex decision frameworks. Complex systems often involve the participation of different interest groups, who have different value systems and are focused on distinct aspects of the project. For example, design alternatives might be assessed predominantly for their technical merit by one group of stakeholders, while a different group might be more inclined to assess the design alternatives primarily based on programmatic values. MESCAL (Monitoring the Evolving State of Clouds and Aerosol Layers) is an ongoing NASA / CNES (Centre National d’Etudes Spatiales) joint study for an active remote sensing Earth observing satellite. Several design alternatives have been identified and the assessment of these alternatives requires consideration of a variety of factors. This paper presents the approach that was used to support a global assessment of the MESCAL design alternatives. A mapping of the interactions between mission, instrument, and science requirements was modeled to support the assessment of the trade space. In addition, a set of metrics was developed to structure the assessment that was conducted. Finally, this paper also discusses the general applicability of these metrics to other science mission concepts in the formulation phase.

Ivanco, Marie L.↗
NASA NTRS1992

Systems engineering process and organization assessment

The purpose of this report is to briefly summarize the results of an eight week assessment of NASA/MSFC Phase A and Phase B systems engineering processes, methodologies, and activities. Specifically, fourteen inconsistencies or weaknesses were identified and recommendations for corrective action were generated. A 1.5 hour briefing on these results was given in EL51 on 8-11-92; that documentation is available from the author or either NASA Colleague.

Batson, Robert G.↗
NASA NTRS1993

The importance of cost considerations in the systems engineering process

This paper examines the question of cost, from the birth of a program to its conclusion, particularly from the point of view of large multi-center programs, and suggests how to avoid some of the traps and pitfalls. Emphasis is given to cost in the systems engineering process, but there is an inevitable overlap with program management. (These terms, systems engineering and program management, have never been clearly defined.) In these days of vast Federal budget deficits and increasing overseas competition, it is imperative that we get more for each research and development dollar. This is the only way we will retain our leadership in high technology and, in the long run, our way of life.

Hodge, John D.↗