SEARCH · Search NASA

Results for “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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 145 records · Page 8

All sources NASA NTRS DOE OSTI

NASA NTRS2010

Core and Off-Core Processes in Systems Engineering

An emerging methodology of organizing systems-engineering plans is based on a concept of core and off-core processes or activities. This concept has emerged as a result of recognition of a risk in the traditional representation of systems-engineering plans by a Vee model alone, according to which a large system is decomposed into levels of smaller subsystems, then integrated through levels of increasing scope until the full system is constructed. Actual systems-engineering activity is more complicated, raising the possibility that the staff will become confused in the absence of plans which explain the nature and ordering of work beyond the traditional Vee model.

Breidenthal, Julian↗

NASA NTRS1990

An update of engine system research at the Army Propulsion Directorate

The Small Turboshaft Engine Research (STER) program provides a vehicle for evaluating the application of emerging technologies to Army turboshaft engine systems and to investigate related phenomena. Capitalizing on the resources at hand, in the form of both the NASA facilities and the Army personnel, the program goal of developing a physical understanding of engine system dynamics and/or system interactions is being realized. STER entries investigate concepts and components developed both in-house and out-of-house. Emphasis is placed upon evaluations which evolved from on-going basic research and advanced development programs. Army aviation program managers are also encouraged to make use of STER resources, both people and facilities. The STER personnel have established their reputations as experts in the fields of engine system experimental evaluations and engine system related phenomena. The STER facility has STER program provides the Army aviation community the opportunity to perform system level investigations, and then to offer the findings to the entire engine community for their consideration in next generation propulsion systems. In this way results of the fundamental research being conducted to meet small turboshaft engine technology challenges expeditiously find their way into that next generation of propulsion systems.

Bobula, George A.↗

NASA NTRS1990

An update of engine system research at the Army Propulsion Directorate

The Small Turboshaft Engine Research (STER) program provides a vehicle for evaluating the application of emerging technologies to Army turboshaft engine systems and to investigate related phenomena. Capitalizing on the resources at hand, in the form of both the NASA facilities and the Army personnel, the program goal of developing a physical understanding of engine system dynamics and/or system interactions is being realized. STER entries investigate concepts and components developed both in-house and out-of-house. Emphasis is placed upon evaluations which have evolved from on-going basic research and advanced development programs. Army aviation program managers are also encouraged to make use of STER resources, both people and facilities. The STER personnel have established their reputations as experts in the fields of engine system experimental evaluations and engine system related phenomena. The STER facility has demonstrated its utility in both research and development programs. The STER program provides the Army aviation community the opportunity to perform system level investigations, and then to offer the findings to the entire engine community for their consideration in next generation propulsion systems. In this way results of the fundamental research being conducted to meet small turboshaft engine technology challenges expeditiously find their way into that next generation of propulsion systems.

Bobula, George A.↗

NASA NTRS2014

Tailoring Enterprise Systems Engineering Policy for Project Scale and Complexity

Space systems are characterized by varying degrees of scale and complexity. Accordingly, cost-effective implementation of systems engineering also varies depending on scale and complexity. Recognizing that systems engineering and integration happen everywhere and at all levels of a given system and that the life cycle is an integrated process necessary to mature a design, the National Aeronautic and Space Administration's (NASA's) Marshall Space Flight Center (MSFC) has developed a suite of customized implementation approaches based on project scale and complexity. While it may be argued that a top-level system engineering process is common to and indeed desirable across an enterprise for all space systems, implementation of that top-level process and the associated products developed as a result differ from system to system. The implementation approaches used for developing a scientific instrument necessarily differ from those used for a space station. .

Cox, Renee I.↗

NASA NTRS2017

Human Factors Engineering and Ergonomics in Systems Engineering

The study, discovery, and application of information about human abilities, human limitations, and other human characteristics to the design of tools, devices, machines, systems, job tasks and environments for effective human performance.

Whitmore, Mihriban↗

DOE OSTI2025

System Engineers and Decisions: It?s All about Knowledge

In order to guarantee that a system meets adequate levels of reliability and availability, system performances are continuously monitored and analyzed thanks to the technological advancements driving the Industry 4.0 revolution. An Industry 4.0 approach is typically based on advanced statistical, big data mining, machine learning, and internet-of-things methods designed to detect anomalies in the behavior of system, detect the most likely failure modes, and provide indications to system engineers on when maintenance activities should be performed before system performance are deemed unacceptable (which can be generated by diagnostic and prognostic methods). However, these analyses, which are designed to automatize and increase the efficacy of the system maintenance program, require large amount of data which can come in various forms: numeric, textual, images, sounds etc. Such data constitutes the historic knowledge benchmark to track system performances and support system engineer decisions. Here we claim that data is not sufficient to support this kind of analyses when applied to systems characterized by complex architectures and behaviors. Robust system engineer decisions require the ability to understand the system operational context that lies behind the observed data elements. In this respect, system models are in fact necessary to “put data in context” and capture relationships between data elements. Industry 4.0 methods require in fact contextual knowledge as a basis upon which hypotheses can be generated and assumptions tested. In our view, for complex systems, model-based system engineering (MBSE) models can afford this contextual knowledge, as they are typically used to describe systems architecture and dynamic behaviors. System knowledge is here intended as the blending of collected data and system architecture which takes the form of a “knowledge graph”. A knowledge graph is a database which consists of a large set of nodes (in our case an entity can be either a data or an MBSE element) which are linked to each other. The types of nodes and links follow a pre-defined topology, sometimes also refers as an ontology, that is designed to fit the actual decisions that needs to be performed. We show here how a knowledge graph can be defined to support system engineer maintenance decisions and how the same graph can be built based on system MBSE models and pre-processed data from numeric (through anomaly detections and diagnostic methods) and textual elements (through technical language processing TLP).

97 - MATHEMATICS AND COMPUTING↗

NASA NTRS2007

The MSFC Systems Engineering Guide: An Overview and Plan

This paper describes the guiding vision, progress to date and the plan forward for development of the Marshall Space Flight Center (MSFC) Systems Engineering Guide (SEG), a virtual systems engineering handbook and archive that describes the system engineering processes used by MSFC in the development of ongoing complex space systems such as the Ares launch vehicle and forthcoming ones as well. It is the intent of this website to be a "One Stop Shop' for MSFC systems engineers that will provide tutorial information, an overview of processes and procedures and links to assist system engineering with guidance and references, and provide an archive of relevant systems engineering artifacts produced by the many NASA projects developed and managed by MSFC over the years.

Shelby, Jerry↗

NASA NTRS2005

Template for Systems Engineering Tools Trade Study

A discussion of Systems Engineering tools brings out numerous preferences and reactions regarding tools of choice as well as the functions those tools are to perform. A recent study of Systems Engineering Tools for a new Program illustrated the need for a generic template for use by new Programs or Projects to determine the toolset appropriate for their use. This paper will provide the guidelines new initiatives can follow and tailor to their specific needs, to enable them to make their choice of tools in an efficient and informed manner. Clearly, those who perform purely technical functions will need different tools than those who perform purely systems engineering functions. And, everyone has tools they are comfortable with. That degree of comfort is frequently the deciding factor in tools choice rather than an objective study of all criteria and weighting factors. This paper strives to produce a comprehensive list of criteria for selection with suggestions for weighting factors based on a number of assumptions regarding the given Program or Project. In addition, any given Program will begin with assumptions for its toolset based on Program size, tool cost, user base and technical needs. In providing a template for tool selection, this paper will guide the reader through assumptions based on Program need; decision criteria; potential weighting factors; the need for a compilation of available tools; the importance of tool demonstrations; and finally a down selection of tools. While specific vendors cannot be mentioned in this work, it is expected that this template could serve other Programs in the formulation phase by alleviating the trade study process of some of its subjectivity.

Michelle D Bailey↗

NASA NTRS2022

Design Thinking, Lean Startup, and High-Technology Marketing for Human-Centered Systems Engineering

The use of design thinking, lean startup, and high-technology marketing in systems engineering are presented as a case study. All were used and evaluated for their potential to improve systems engineering processes and design, address the challenges of culture change, increase the adoption rate of new technology, and engage with potential users and sponsors more effectively. Multiple examples of training and use on a model-based systems engineering initiative at a large government agency showcase how these approaches were tailored and used successfully for significant benefits such as enhanced collaboration and better problem definition and design solutions. Challenges remain for use by quiet thinkers and with virtual teams. These new ways of thinking are well aligned with creating and using new technologies and are suitable for situations involving innovation, uncertainty, and change within organizations. This case study intends to familiarize systems engineers with the application of these human-centered approaches, to interest systems engineers in incorporating these approaches into their work processes ,and to inspire the systems engineering research community to investigate further.

Karen J. Weiland↗

NASA NTRS2007

Mars Reconnaissance Orbiter Mission: Systems Engineering Challenges on the Mars Reconnaissance Orbiter Mission

MRO project is a system of systems requiring system engineering team to architect, design, integrate, test, and operate these systems at each level of the project. The challenge of system engineering mission objectives into a single mission architecture that can be integrated tested, launched, and operated. Systems engineering must translate high-level requirements into integrated mission design. Systems engineering challenges were overcome utilizing a combination by creative designs built into MRO's flight and ground systems: a) Design of sophisticated spacecraft targeting and data management capabilities b) Establishment of a strong operations team organization; c) Implementation of robust operational processes; and d) Development of strategic ground tools. The MRO system has met the challenge of its driving requirements: a) MRO began its two-year primary science phase on November 7, 2006, and by July 2007, met it minimum requirement to collect 15 Tbits of data after only eight months of operations. Currently we have collected 22 Tbits. b) Based on current performance, mission data return could return 70 Tbits of data by the end of the primary science phase in 2008.

systems engineering↗

NASA NTRSDate not supplied

ExMC Systems Engineering Status

The Exploration Medical Capability (ExMC) Element within the Human Research Program (HRP) applies systems engineering principles along with the use of Model-Based Systems Engineering (MBSE) tools to identify and communicate the requirements for medical and crew health and performance (CHP) systems. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and a human health and performance system. In addition, the MBSE tools provide a means in which systems engineers can develop different views of the relationships between and among requirements, standards, functions, and capabilities, to name a few, that is best suited for a user’s objectives. Applying these tools, ExMC Systems Engineering (SE) developed three MBSE models in support of multiple projects in fiscal year (FY) 2023. These included the Long-Duration Lunar Orbit and Lunar Surface (LDLOLS) Medical System Foundation, Earth-Independent Medical Operations (EIMO) medical system ConOps, and the 2023 Artemis CHP System model. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last Investigators’ Workshop, an introduction to upcoming SE talks, and the ongoing systems engineering work.

Systems engineering↗

NASA NTRSDate not supplied

ExMC Systems Engineering Status

Systems engineering↗

NASA NTRS2016

A Process for Capturing the Art of Systems Engineering

There is both an art and a science to systems engineering. The science of systems engineering is effectively captured in processes and procedures, but the art is much more elusive. We propose that there is six step process that can be applied to any systems engineering organization to create an environment from which the "art" of that organization can be captured, be allowed to evolve collaboratively and be shared with all members of the organization. This paper details this process as it was applied to NASA Launch Services Program (LSP) Integration Engineering Branch during a pilot program of Confluence, a Commercial Off The Shelf (COTS) wiki tool.

Commercial Off The Shelf↗

NASA NTRS2006

Systems Engineering and Integration for Technology Programs

The Architecture, Habitability & Integration group (AH&I) is a system engineering and integration test team within the NASA Crew and Thermal Systems Division (CTSD) at Johnson Space Center. AH&I identifies and resolves system-level integration issues within the research and technology development community. The timely resolution of these integration issues is fundamental to the development of human system requirements and exploration capability. The integration of the many individual components necessary to construct an artificial environment is difficult. The necessary interactions between individual components and systems must be approached in a piece-wise fashion to achieve repeatable results. A formal systems engineering (SE) approach to define, develop, and integrate quality systems within the life support community has been developed. This approach will allow a Research & Technology Program to systematically approach the development, management, and quality of technology deliverables to the various exploration missions. A tiered system engineering structure has been proposed to implement best systems engineering practices across all development levels from basic research to working assemblies. These practices will be implemented through a management plan across all applicable programs, projects, elements and teams. While many of the engineering practices are common to other industries, the implementation is specific to technology development. An accounting of the systems engineering management philosophy will be discussed and the associated programmatic processes will be presented.

Kennedy, Kruss J.↗

NASA NTRS1997

Toward Mass Customization in the Age of Information: The Case for Open Engineering Systems

In the Industrial Era, manufacturers used "dedicated" engineering systems to mass produce their products. In today's increasingly competitive markets, the trend is toward mass customization, something that becomes increasingly feasible when modern information technologies are used to create open engineering systems. Our focus is on how designers can provide enhanced product flexibility and variety (if not fully customized products) through the development of open engineering systems. After presenting several industrial examples, we anchor our new systems philosophy with two real engineering applications. We believe that manufacturers who adopt open systems will achieve competitive advantage in the Information Age.

Simpson, Timothy W.↗

NASA NTRS2007

NASA Systems Engineering Handbook

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

Source record↗

NASA NTRS2015

Systems Engineering

This short course provides information on what systems engineering is and how the systems engineer guides requirements, interfaces with the discipline leads, and resolves technical issues. There are many system-wide issues that either impact or are impacted by the thermal subsystem. This course will introduce these issues and illustrate them with real life examples.

Thermal↗

NASA NTRS2013

Goal-Function Tree Modeling for Systems Engineering and Fault Management

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM).

Johnson, Stephen B.↗