Search NASA⌕ Search

SEARCH · Search NASA

Results for “model base 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 217 records · Page 12

SinhaRoy_TechPresentation_2024 [Slides]

DOME is a planned microreactor test facility at INL’s Materials and Fuels Complex. It is a complex system with several interdependent sub-systems such as the reactor (up to 20 MWth), radioactive confinement, temperature and pressure regulation system, ventilation system, etc. The engineering design process for such a system traditionally involves several documents from various sources and the system information is scattered across these documents. Digital engineering represents a paradigm shift through which systems are designed using digital models and integrated data. The digital engineering vision for DOME utilizes a model-based systems engineering (MBSE) approach. The system architecture, physical components, control logic, and verification experiments are all designed using MathWorks MATLAB and Simulink. This hierarchical model can combine data from multiple sources at various levels of abstraction. It can be used to simulate the facility’s operations and to test the system using different sets of parameters. Its capabilities can be expanded by interfacing it with high-fidelity multi-physics models, risk analysis tools, etc. The same model can evolve into a digital twin that can monitor operations and conduct predictive analysis using real-time sensor data from the facility. The eventual goal of this effort is to transform the end-to-end engineering of nuclear facilities in every phase of their lifecycle, including design, deployment, and operations.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

How ExMC Communicates a System Model to Non-Modelers

NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and mission planners. Many of these stakeholders have neither access to MBSE modeling tools nor experience with SE modeling techniques. The challenge faced by ExMC SE team was how to present the content in the model to non-modelers in a way they would understand the content with limited training in MBSE and without using the modeling tool. ExMC SE team created a Hypertext Markup Language (HTML) report that shows key model content and is accessible to anyone with a browser. When creating the HTML report, the ExMC SE received stakeholder feedback on what content they wanted and how to display this content. Incorporating this feedback, the report arranges the content in a way that directs readers through the SE process taken to derive the requirements and helps them to understand the fundamental steps in an SE approach. The report includes links to source information (e.g., NASA documentation that describes levels of care) and other SE products (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This presentation outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

J. Cohen↗

A PPE Use Case on Configuration Management Approach for MBSE

Systems engineers worldwide have been working to implement Model-based Systems Engineering (MBSE) environments, tools, and methodologies. MBSE is a formalized application of modeling to support systems engineering, including requirements, design, analysis, verification, and validation activities over the project’s lifecycle[1]; MBSE captures the system data into a digital environment. Significant benefits of MBSE includes a reduction in the time in performing systems engineering activities and an improvement higher fidelity data production. As more Systems Engineers are using MBSE, the models it produces are becoming the source of truth for Systems Engineering artifacts. As we move towards using these models as the source of truth, a more rigorous Configuration Management (CM) infrastructure is needed. Many of the MBSE tools provide CM options but utilizing them efficiently and effectively can be challenging. More rigorous methods and tools are needed to assist with keeping track of changes in the model, making sure inadvertent changes to baseline data did not occur, visibility of changes in the different model versions, and the impacts of changes to the models. System engineers and configuration management personnel from the Power and Propulsion Element (PPE) project at NASA Glenn Research Center have been working to develop a modeling construct that allows models to be the source of truth and maintain a configuration managed baseline. This paper presents a process that leverages the existing CM tools and describes how PPE used this process to manage changes more rigorously. It will describe the process behind building the model architecture that utilizes the MBSE tool capabilities and the configuration management process. It will contain some of the advantages and disadvantages of the architecture that the PPE project had settled upon utilizing, as well as some enhanced capabilities that the PPE MBSE team has developed.

MBSE↗

Developing a Medical System Foundation for Level of Care IV: Short-Duration Lunar Orbit

The Human Research Program (HRP) Exploration Medical Capability (ExMC) element has developed a Medical System Foundation for Level of Care IV, as defined by NASA’s space flight human-system standards, for short-duration lunar orbit missions by employing a systems engineering approach using model-based systems engineering tools. This Foundation includes a concept of operations, medical system architecture, associated functional and non-functional requirements and rationales, and medical conditions, capabilities, and resources. Collectively, these serve as a starting point (“Foundation”) for a medical system that meets the Level of Care IV requirement. The Foundation also includes traces to the current versions of NASA standards documents and lower (e.g., sub-system) and higher (e.g., vehicle system) level requirements. Stakeholders can use the Foundation to analyze the traces between medical capabilities, medical conditions, medical resources, and requirements; identify medical system interfaces with other vehicle systems/subsystems; and as a basis for performing trades on risks vs. medical system mass and volume allocation. To facilitate communication of the Foundation to stakeholders who do not have access to the modeling tools used, an HTML representation of the Foundation was created. This discussion will focus on the processes through which the Medical System Foundation was developed, how the Foundation builds a bridge between the medical and engineering domains and facilitates communication between these communities, and how these processes can be applied more broadly to a crew health and performance system and other system domains.

S. Lumpkins↗

Advanced Shock Position Control for Mode Transition in a Turbine Based Combined Cycle Engine Inlet Model

A dual flow-path inlet system is being tested to evaluate methodologies for a Turbine Based Combined Cycle (TBCC) propulsion system to perform a controlled inlet mode transition. Prior to experimental testing, simulation models are used to test, debug, and validate potential control algorithms. One simulation package being used for testing is the High Mach Transient Engine Cycle Code simulation, known as HiTECC. This paper discusses the closed loop control system, which utilizes a shock location sensor to improve inlet performance and operability. Even though the shock location feedback has a coarse resolution, the feedback allows for a reduction in steady state error and, in some cases, better performance than with previous proposed pressure ratio based methods. This paper demonstrates the design and benefit with the implementation of a proportional-integral controller, an H-Infinity based controller, and a disturbance observer based controller.

Csank, Jeffrey T.↗

Integrated Concurrent Engineering Teams for Increased Efficiency in Flight Projects

A highly integrated Concurrent Engineering Team (CET) within a flight project evolves in its function and has the potential to provide many benefits through the project lifecycle. The benefits include superior systems-oriented design products, as well as overall improved project efficiency and higher-performing interpersonal relationships within the project. If physically integrated, this can manifest as a Concurrent Engineering Center (CEC) centrally located within a project’s physical office space. Here we discuss the process to establish and maintain a tightly integrated engineering and design team for providing highly streamlined service to the project, including a cost/benefits analysis discussion.

Flight Project↗

Integrated Concurrent Engineering Teams for Increased Efficiency in Flight Projects

A highly integrated Concurrent Engineering Team (CET) within a flight project evolves in its function and has the potential to provide many benefits through the project lifecycle. The benefits include superior systems-oriented design products, as well as overall improved project efficiency and higher-performing interpersonal relationships within the project. If physically integrated, this can manifest as a Concurrent Engineering Center (CEC) centrally located within a project’s physical office space. Here we discuss the process to establish and maintain a tightly integrated engineering and design team for providing highly streamlined service to the project, including a cost/benefits analysis discussion.

Flight Project↗

What Has ExMC Systems Engineering Been Up To Since Last IWS?

Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element’s approach to enabling the necessary autonomy. This element promotes human health and performance in space by advancing medical systems design and risk-informed decision-making for long-duration deep-space exploration missions (LDEMs). ExMC is using system engineering processes and Model-Based System Engineering (MBSE) tools to identify the user needs and requirements of LDEM medical systems. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant International Space Station operations to the Earth-independent operations envisioned for LDEMs. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS, an introduction to upcoming SE talks, and the ongoing systems engineering work.

K. McGuire↗

ENABLING ARCHITECTURE TRADES AND DESIGN EXPLORATION FOR NUCLEAR ELECTRIC PROPULSION

Recent renewed interest in Nuclear Electric Propulsion (NEP) at NASA has driven the need for design space exploration and analysis of alternative architectures to evaluate performance and feasibility of NEP concepts. It has been over a decade since NASA last invested in Nuclear Electric Propulsion development efforts, and the landscape has shifted in both mission objectives and technology readiness levels. This also means that many of the engineering analyses and design frameworks tailored to NEP date back to the Jupiter Icy Moons Orbiter (JIMO) days of the early 2000s. Thus, a need was identified for updating and modernizing the modeling and simulation toolsets for NEP. This paper will detail the development efforts in the Marshall Space Flight Center’s Advanced Concepts Office, with a particular focus on the development of the NEP stage of the NEP-Chem vehicle. The paper will cover the various models used, and their current development status, as well as provide an overview of the integrated vehicle model and plans for further development.

Nuclear↗

Enabling Architecture Trades and Design Exploration for Nuclear Electric Propulsion

Recent renewed interest in Nuclear Electric Propulsion (NEP) at NASA has driven the need for design space exploration and analysis of alternative architectures to evaluate performance and feasibility of NEP concepts. It has been over a decade since NASA last invested in Nuclear Electric Propulsion development efforts, and the landscape has shifted in both mission objectives and technology readiness levels. This also means that many of the engineering analyses and design frameworks tailored to NEP date back to the Jupiter Icy Moons Orbiter (JIMO) days of the early 2000s. Thus, a need was identified for updating and modernizing the modeling and simulation toolsets for NEP. This paper will detail the development efforts in the Marshall Space Flight Center’s Advanced Concepts Office, with a particular focus on the development of the NEP stage of the NEP-Chem vehicle. The paper will cover the various models used, and their current development status, as well as provide an overview of the integrated vehicle model and plans for further development.

Nuclear↗

Innovation Connection Hub: DE + MBSE at Goddard

Systems are changing and engineering practices must mind the balance between evolutionary and revolutionary change as we move towards increasingly agile processes, enabled by interconnected tools, to best provide for partnered collaboration. This is the first example of Goddard's alignment between Digital Engineering strategy and Model-Based Systems Engineering strategy.

Digital Engineering↗

Using Maxwell's Demon to Tame the "Devil in the Details" that are Encountered During System Development

Model-Based Systems Engineering (MBSE) is the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases . This presentation will discuss the value proposition that MBSE has for Systems Engineering, and the associated culture change needed to adopt it.

Model Based Systems Engineering↗

A Model-Based Anomaly Detection Approach for Analyzing Streaming Aircraft Engine Measurement Data

This paper presents a model-based anomaly detection architecture designed for analyzing streaming transient aircraft engine measurement data. The technique calculates and monitors residuals between sensed engine outputs and model predicted outputs for anomaly detection purposes. Pivotal to the performance of this technique is the ability to construct a model that accurately reflects the nominal operating performance of the engine. The dynamic model applied in the architecture is a piecewise linear design comprising steady-state trim points and dynamic state space matrices. A simple curve-fitting technique for updating the model trim point information based on steadystate information extracted from available nominal engine measurement data is presented. Results from the application of the model-based approach for processing actual engine test data are shown. These include both nominal fault-free test case data and seeded fault test case data. The results indicate that the updates applied to improve the model trim point information also improve anomaly detection performance. Recommendations for follow-on enhancements to the technique are also presented and discussed.

Propulsion System Performance↗

A Model-Based Anomaly Detection Approach for Analyzing Streaming Aircraft Engine Measurement Data

This paper presents a model-based anomaly detection architecture designed for analyzing streaming transient aircraft engine measurement data. The technique calculates and monitors residuals between sensed engine outputs and model predicted outputs for anomaly detection purposes. Pivotal to the performance of this technique is the ability to construct a model that accurately reflects the nominal operating performance of the engine. The dynamic model applied in the architecture is a piecewise linear design comprising steady-state trim points and dynamic state space matrices. A simple curve-fitting technique for updating the model trim point information based on steadystate information extracted from available nominal engine measurement data is presented. Results from the application of the model-based approach for processing actual engine test data are shown. These include both nominal fault-free test case data and seeded fault test case data. The results indicate that the updates applied to improve the model trim point information also improve anomaly detection performance. Recommendations for follow-on enhancements to the technique are also presented and discussed.

Propulsion System Performance↗

Lessons Learned from Medical System Foundation Development for Long-Duration Lunar Orbit and Lunar Surface Missions

The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has been tasked with the development of Medical System Foundations for Level of Care IV for both short-duration lunar orbital missions and, subsequently, long-duration lunar orbital and surface operations missions. These Medical System Foundations serve as a framework to aid in early medical system design and mission planning. The content of both Foundation models is similar, consisting of a concept of operations, functional decomposition, clinical content (medical conditions, capabilities, and resources), technical requirements (interface, non-functional, and functional), and traces between these components and to the NASA standards documents and parent-level (Program- and Vehicle habitat system-level) requirements. Additionally, the development of both Foundations employed systems engineering principles and a model-based systems engineering (MBSE) approach. Throughout the development of these Foundations, ExMC has strived to improve the efficiency and robustness of its processes and to be more responsive to change (i.e., in design reference mission parameters and assumptions) and to stakeholders’ feedback. The most significant improvements made between the short- and long-duration Foundation models during this transformation process are the following: • Replacement of the traditional document-based ConOps with a model-based ConOps according to MBSE principles, which facilitated more efficient understanding of the material and the consolidation of all relevant information into a centralized location. • Utilization of an agile approach with tasks organized into sprints. This approach enabled solicitation of more frequent usability feedback from stakeholders, incorporation of more human factors reviews into the sprints, and more efficient tasking of team members. This presentation will discuss the journey of developing both Foundation models, as well as the lessons learned and resulting improvements made between the Short- and Long-Duration models.

M Kaetzer↗

Design Basis Model for Hosting Small Modular Reactors

An aggressive transition from fossil fuels to other types of energy implies the need to construct a large number of nuclear power plants in the near future. However, the real and perceived risks of nuclear energy remain a significant impediment to this transition. This paper describes a comprehensive work process that combines the rigor of model-based systems engineering (MBSE) with 1) the Idaho National Laboratory's (INL) decades of experience with small reactors and with 2) modern project delivery processes. The objective is to reduce the risk of building new facilities or converting existing facilities to nuclear power generation.

42 ENGINEERING↗

State Analysis Database Tool

The State Analysis Database Tool software establishes a productive environment for collaboration among software and system engineers engaged in the development of complex interacting systems. The tool embodies State Analysis, a model-based system engineering methodology founded on a state-based control architecture (see figure). A state represents a momentary condition of an evolving system, and a model may describe how a state evolves and is affected by other states. The State Analysis methodology is a process for capturing system and software requirements in the form of explicit models and states, and defining goal-based operational plans consistent with the models. Requirements, models, and operational concerns have traditionally been documented in a variety of system engineering artifacts that address different aspects of a mission s lifecycle. In State Analysis, requirements, models, and operations information are State Analysis artifacts that are consistent and stored in a State Analysis Database. The tool includes a back-end database, a multi-platform front-end client, and Web-based administrative functions. The tool is structured to prompt an engineer to follow the State Analysis methodology, to encourage state discovery and model description, and to make software requirements and operations plans consistent with model descriptions.

Rasmussen, Robert↗