Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “engineered systems”

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 163 records · Page 9

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↗

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↗

A Systems Engineering Approach to Accident Response Planning

This paper explores the Systems Engineering structure, strategies and tools for real world scenarios involving work with accident response groups. A systems engineering approach must be taken by the technical teams to prepare for a successful response and design the technical systems in support of the operations. The scope of this project is focused on laying out the foundation of the systems engineering approach taken to help the teams develop an accident response strategy and identify new engineering designs in support of these operations for the black box systems. This Master’s project involves several interdisciplinary teams & stakeholders across different areas. Identifying the proper tools to use is key to addressing the big picture needs of the multiple stakeholders. This project explores some of the key tools used by the integrated team. The integrated project work will primarily take place over the course of 8 weeks via integrated team meetings. Other work in support of this project will take place off-line as needed by the project lead. Details on the prospective timeline, milestones, key dates and work scope can be referenced in other sections of this paper. Key systems engineering methodologies and tools used thus far in support of this project includes: 1) Market Surveys and Interviews, 2) Project Charter, 3) Feasibility Study, 4) Swim Lane Diagram, and 5) Knowledge Management Plan.

42 ENGINEERING↗

A Systems Engineering Approach to Accident Response Planning.

This paper explores the Systems Engineering structure, strategies and tools for real world scenarios involving work with accident response planning. A systems engineering approach must be taken by the technical teams to prepare for a successful response and design the technical systems in support of the operations. The scope of this project is focused on laying out the foundation of the systems engineering approach taken to help the teams develop an accident response strategy and identify new engineering designs in support of these operations for the black box systems. This Masters project involved several interdisciplinary teams & stakeholders. Identifying the proper tools to use was key to addressing the big picture needs of the multiple stakeholders. The integrated project work primarily took place over the course of eight weeks via integrated team meetings. Other work in support of this project was conducted off-line as needed by the project lead. Details on the prospective timeline, milestones, key dates and work scope can be referenced in this paper. Key systems engineering methodologies and tools used in support of this project included but is not limited to: Market Surveys and Interviews Project Charter Feasibility Study Swim Lane Diagram Knowledge Management Plan. A full suite of tools and the details regarding the application of these tools and results of this study is provided in this report.

42 ENGINEERING↗

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.↗

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 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↗

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↗

About the Complex Natural and Engineered Systems Pillar

Los Alamos National Laboratory is a world leader in applying multi-disciplinary science to complex systems within the Complex Natural and Engineered Systems (CNES) challenge areas. Our search for solutions requires science and technology innovation, as well as an integrated experiment, theory, and modeling and simulation approach. Our research and development spans from improving engineered systems such as nuclear weapons and the power grid, to understanding the interface of human and engineered systems from the subsurface to space, to studying how complex natural systems such as disease and climate impact humanity.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

NuScale Systems Engineering Program Overview and Status

NuScale systems engineering program overview, including technical data management and model-based engineering, product structures, architecture views, and model-based systems engineering. Includes a discussion on technical risk and opportunity management and technical readiness levels, as well as risk-informed performance-based principles and methods.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

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.↗

L-Band Digital Aeronautical Communications System Engineering - Concepts of Use, Systems Performance, Requirements, and Architectures

This NASA Contractor Report summarizes and documents the work performed to develop concepts of use (ConUse) and high-level system requirements and architecture for the proposed L-band (960 to 1164 MHz) terrestrial en route communications system. This work was completed as a follow-on to the technology assessment conducted by NASA Glenn Research Center and ITT for the Future Communications Study (FCS). ITT assessed air-to-ground (A/G) communications concepts of use and operations presented in relevant NAS-level, international, and NAS-system-level documents to derive the appropriate ConUse relevant to potential A/G communications applications and services for domestic continental airspace. ITT also leveraged prior concepts of use developed during the earlier phases of the FCS. A middle-out functional architecture was adopted by merging the functional system requirements identified in the bottom-up assessment of existing requirements with those derived as a result of the top-down analysis of ConUse and higher level functional requirements. Initial end-to-end system performance requirements were derived to define system capabilities based on the functional requirements and on NAS-SR-1000 and the Operational Performance Assessment conducted as part of the COCR. A high-level notional architecture of the L-DACS supporting A/G communication was derived from the functional architecture and requirements.

Zelkin, Natalie↗

System Engineering Issues for Avionics Survival in the Space Environment

This paper examines how the system engineering process influences the design of a spacecraft's avionics by considering the space environment. Avionics are susceptible to the thermal, radiation, plasma, and meteoroids/orbital debris environments. The environment definitions for various spacecraft mission orbits (LEO/low inclination, LEO/Polar, MEO, HEO, GTO, GEO and High ApogeeElliptical) are discussed. NASA models and commercial software used for environment analysis are reviewed. Applicability of technical references, such as NASA TM-4527 "Natural Orbital Environment Guidelines for Use in Aerospace Vehicle Development" is discussed. System engineering references, such as the MSFC System Engineering Handbook, are reviewed to determine how the environments are accounted for in the system engineering process. Tools and databases to assist the system engineer and avionics designer in addressing space environment effects on avionics are described and usefulness assessed.

Pavelitz, Steven↗

Systems engineering overview for regenerative life-support systems applicable to space habitats

The Life-Support Systems Group of the 1977 NASA Ames Summer Study conducted analyses initially to identify areas where partial or complete closure of the life-support system, for various types of space habitats, should be considered, and to develop a sound methodology for identifying, screening, and evaluating alternative closure schemes. Results of these analyses, including the systems engineering considerations that affect technology-development planning and management for regenerative life-support systems, are discussed. A recommended methodology is also presented as a basis for future technology-development activities in this area.

Spurlock, J.↗