Results for “model based systems engineering (MBSE)” — Page 2

DOE OSTI2025

A Model Based Approach to Extract Health Information from Textual Data

In current nuclear power plants (NPPs) a large amount of condition-based data is being generated and stored to assess and monitor component health and performance. The format of this data can be either numeric (e.g., pump vibration data) or textual (e.g., condition report which assess component health). While assessing component health from numeric data can be performed with a large variety of methods, the extraction of information from textual data still remains a challenge. Natural language processing (NLP) methods are starting to be deployed in current NPPs mainly to filter out incident reports (IRs) that are not safety related by employing supervised machine learning methods. However, these methods do not really provide the quantitative information that might be contained in IRs. This paper presents an approach to extract information from textual data (e.g., from IRs, maintenance reports) that is based on NLP data analytics methods coupled with model-based system engineer (MBSE) models. NLP methods are employed to perform syntactic and semantic analyses. Syntactic analysis analyzes the grammatical structure of a sentence; such analysis includes: part of speech (POS) tagging (i.e., identification of grammatic elements of each string - e.g., nouns, verbs), named entity recognition (i.e., identification of text entities - e.g., names, dates, events), and relation extraction (e.g., coreference resolution). On the other hand, semantic analysis is designed to analyze the logic structure of a sentence. Through a specific set of rules, our methods can identify whether a sentence contains health information of a component (e.g., degraded performance, anomaly behavior) or the causal relationship between two events (i.e., a cause-effect pair). An innovative element of our approach is that semantic analysis relies on MBSE models to identify links between textual elements. MBSE are diagrams designed to represent system and component dependencies (from both a form and functional point of view). In our approach, MBSE models emulate system engineer knowledge about component/system architecture. This paper presents in detail how the integration of NLP methods and MBSE models is performed. Few analysis examples focusing on centrifugal pumps are presented.

97 - MATHEMATICS AND COMPUTING↗

NASA NTRS2016

Model Based Mission Assurance: Emerging Opportunities for Robotic Systems

The emergence of Model Based Systems Engineering (MBSE) in a Model Based Engineering framework has created new opportunities to improve effectiveness and efficiencies across the assurance functions. The MBSE environment supports not only system architecture development, but provides for support of Systems Safety, Reliability and Risk Analysis concurrently in the same framework. Linking to detailed design will further improve assurance capabilities to support failures avoidance and mitigation in flight systems. This also is leading new assurance functions including model assurance and management of uncertainty in the modeling environment. Further, the assurance cases, a structured hierarchal argument or model, are emerging as a basis for supporting a comprehensive viewpoint in which to support Model Based Mission Assurance (MBMA).

Mission Assurance↗

DOE OSTI2025

Progress on the MARVEL Cybersecurity by Design Model-Based Systems Engineering Project

Formal model-based systems engineering (MBSE) combines a model, systems thinking, and systems engineering to visually depict the boundaries, context, and behavior of interconnected systems, facilitating effective design, development, and utilization of engineered systems throughout the systems engineering lifecycle. Although nuclear reactor vendors employ these tools to integrate functionality, performance, and safety, they are not yet addressing digital risk concerns introduced by use of operational technology, such as digital instrumentation and control systems. To accomplish this objective, the Microreactor Applications Research Validation and EvaLuation (MARVEL) microreactor was used as an MBSE case study. This real-world application provides a first-of-a-kind opportunity to demonstrate the benefits of integrating digital risk and cybersecurity into the MBSE design process of a nuclear reactor. This paper provides an update of the ongoing MARVEL Cyber MBSE project as it specifically relates to the integration of digital risk management and cybersecurity by design.

22 - GENERAL STUDIES OF NUCLEAR REACTORS↗

NASA NTRSDate not supplied

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↗

NASA NTRS2012

Model-Based Verification and Validation of Spacecraft Avionics

Our simulation was able to mimic the results of 30 tests on the actual hardware. This shows that simulations have the potential to enable early design validation - well before actual hardware exists. Although simulations focused around data processing procedures at subsystem and device level, they can also be applied to system level analysis to simulate mission scenarios and consumable tracking (e.g. power, propellant, etc.). Simulation engine plug-in developments are continually improving the product, but handling time for time-sensitive operations (like those of the remote engineering unit and bus controller) can be cumbersome.

Systems Modeling Language (SysML↗

NASA NTRSDate not supplied

Architectural Framework for Conceptualizing Exploration Class Medical Operations

Currently, discrete projects within NASA’s Human Research Program (HRP) take aim at providing future exploration missions with the capabilities necessary to operate within a progressively Earth-independent operative environment. Realizing an entire ecosystem that can accomplish these goals requires a clear visualization on how each project contributes to the overall objectives of Human Health and Performance (HH&P) in that context. The Exploration Medical Capability (ExMC) Element has developed an architectural framework for exploration class medical operations by utilizing a systems engineering approach using model-based systems engineering (MBSE). This model, a System of Systems Architecture (SoSA), captures a means of integrating various independent but related efforts into a comprehensive view associated with HRP’s goal of providing progressively Earth-Independent Medical Operations (EIMO). This level of visibility is realized by identifying interfaces between development efforts and existing programs that contribute to the overall mission of EIMO even if those extend past the traditional boundary of HRP. Potential interfaces that are considered important when constructing an architecture include program/project Needs, Goals, and Objectives (NGOs), capabilities, envisioned use cases/scenarios, and system/subsystem structure. This presentation will focus on the processes that were used to generate the SoSA along with a means to realize its utility amongst other MBSE products from ExMC. Evaluation of the best architecture moving forward can then be achieved that promotes cohesion between various functional areas of HH&P. Additionally, the SoSA is developed with a long-term vision for the dynamic integration of novel technological developments that may be implemented in the future. The SoSA is intended to enable Stakeholders the ability to view the broader interconnections that exist and begin to create avenues of communication between various efforts. The benefits of a SoSA provide an essential step towards addressing the unique challenges of attaining the goals of broader exploration class medical missions of the future.

Systems engineering↗

NASA NTRS2024

Architectural Framework for Conceptualizing Exploration Class Medical Operations

Currently, discrete projects within NASA’s Human Research Program (HRP) take aim at providing future exploration missions with the capabilities necessary to operate within a progressively Earth-independent operative environment. Realizing an entire ecosystem that can accomplish these goals requires a clear visualization on how each project contributes to the overall objectives of Human Health and Performance (HH&P) in that context. The Exploration Medical Capability (ExMC) Element has developed an architectural framework for exploration class medical operations by utilizing a systems engineering approach using model-based systems engineering (MBSE). This model, a System of Systems Architecture (SoSA), captures a means of integrating various independent but related efforts into a comprehensive view associated with HRP’s goal of providing progressively Earth-Independent Medical Operations (EIMO). This level of visibility is realized by identifying interfaces between development efforts and existing programs that contribute to the overall mission of EIMO even if those extend past the traditional boundary of HRP. Potential interfaces that are considered important when constructing an architecture include program/project Needs, Goals, and Objectives (NGOs), capabilities, envisioned use cases/scenarios, and system/subsystem structure. This presentation will focus on the processes that were used to generate the SoSA along with a means to realize its utility amongst other MBSE products from ExMC. Evaluation of the best architecture moving forward can then be achieved that promotes cohesion between various functional areas of HH&P. Additionally, the SoSA is developed with a long-term vision for the dynamic integration of novel technological developments that may be implemented in the future. The SoSA is intended to enable Stakeholders the ability to view the broader interconnections that exist and begin to create avenues of communication between various efforts. The benefits of a SoSA provide an essential step towards addressing the unique challenges of attaining the goals of broader exploration class medical missions of the future.

Systems engineering↗

NASA NTRSDate not supplied

Introduction to an MBSE Case Study

During this interactive activity, we will review real-world challenges decision-makers have faced and work together in small groups to develop solutions to those challenges by applying the principles of model-based systems engineering (MBSE).

systems engineering↗

NASA NTRS2013

Model-based Systems Engineering: Creation and Implementation of Model Validation Rules for MOS 2.0

Model-based Systems Engineering (MBSE) is an emerging modeling application that is used to enhance the system development process. MBSE allows for the centralization of project and system information that would otherwise be stored in extraneous locations, yielding better communication, expedited document generation and increased knowledge capture. Based on MBSE concepts and the employment of the Systems Modeling Language (SysML), extremely large and complex systems can be modeled from conceptual design through all system lifecycles. The Operations Revitalization Initiative (OpsRev) seeks to leverage MBSE to modernize the aging Advanced Multi-Mission Operations Systems (AMMOS) into the Mission Operations System 2.0 (MOS 2.0). The MOS 2.0 will be delivered in a series of conceptual and design models and documents built using the modeling tool MagicDraw. To ensure model completeness and cohesiveness, it is imperative that the MOS 2.0 models adhere to the specifications, patterns and profiles of the Mission Service Architecture Framework, thus leading to the use of validation rules. This paper outlines the process by which validation rules are identified, designed, implemented and tested. Ultimately, these rules provide the ability to maintain model correctness and synchronization in a simple, quick and effective manner, thus allowing the continuation of project and system progress.

Model-based Systems Engineering (MBSE)↗

NASA NTRS2024

How the INCOSE Model-Based Capability Matrix Has Steered Model-Based Systems Engineering Transformation at NASA

The National Aeronautics and Space Administration (NASA) is embarking on new, complex, and diverse missions to accomplish its scientific and exploration objectives, and it views digital transformation as a key enabler for those missions. The NASA Model-Based Systems Engineering (MBSE) Lead-ership Team (MLT) is leading the charge in the digital transformation of the systems engineering domain at NASA, and it is using the INCOSE Model-Based Capability Matrix (MBCM) as a roadmap. This paper discusses the modifications and tailoring of the INCOSE MBCM (Hale & Hoheb, 2020) for use at NASA, the process the team has taken on multiple rounds of assessment, findings to date, and work products that have been generated as a result of the assessment. The paper will also discuss findings and potential changes that should be made to the original product.

MBSE↗

NASA NTRS2023

An MBSE Approach for Developing an Autonomous Rover Platform

The proliferation of increasingly autonomous systems calls for new ways to address how safety is assured. As these systems become more advanced and complex, it becomes more important to model and prototype autonomous functions at the systems level and the functions that assure they are operating safely and as expected. To that effect, researchers at the National Aeronautics and Space Administration (NASA) 's Robust Software Engineering (RSE) group are working on prototyping a Research Autonomous Vehicle, commonly referred to as R-RAV. The R-RAV is an autonomous rover platform designed to act as a case study for assured autonomy research. Moreover, an overarching goal is for the R-RAV to serve as a training ground for other mission projects. In this paper, we will detail how we have used a Model-Based Systems Engineering (MBSE) approach to model a prototype of the R-RAV and test and verify its different functionalities.

MBSE↗

DOE OSTI2024

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↗

NASA NTRSDate not supplied

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System (IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation function present in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

IASMS↗

NASA NTRS2019

Enabling Assurance in the MBSE Environment

A number of specific benefits that fit within the hallmarks of effective development are realized with implementation of model-based approaches to systems and assurance. Model Based Systems Engineering (MBSE) enabled by standardized modeling languages (e.g., SysML®) is at the core. These benefits in the context of spaceflight system challenges can include: Improved management of complex development, Reduced risk in the development process, Improved cost management, Improved design decisions. With appropriate modeling techniques the assurance community can improve early oversight and insight into project development. NASA has shown the basic constructs of SysML in an MBSE environment offer several key advantages, within a Model Based Mission Assurance (MBMA) initiative.

Evans, John W.↗

NASA NTRS2020

Enabling Assurance in the MBSE Environment

A number of specific benefits that fit within the hallmarks of effective development are realized with implementation of model-based approaches to systems and assurance. Model Based Systems Engineering (MBSE) enabled by standardized modeling languages (e.g., SysML®) is at the core. These benefits in the context of spaceflight system challenges can include [1]: • Improved management of complex development • Reduced risk in the development process • Improved cost management • Improved design decisions With appropriate modeling techniques the assurance community also can improve early oversight and insight into project development. NASA has shown the basic constructs of SysML in an MBSE environment offer several key advantages, within a Model Based Mission Assurance (MBMA) initiative [2, 3]. These include the following: • Model viewpoints that promote rapid and systematic assessment of requirements coverage, hazard tagging and risk management • Embedded safety assessments for launch vehicles • Deployment of model assisted development of reliability products - Failure Modes and Effects Analyses (FMEAs) and Fault Trees • Test Planning • Validation and Verification of complex functions • Support of Assurance Case development for complex systems In addition, while there are benefits to be harvested, there is a realization that these do not come without effort and cost. Enabling model-based approaches requires structure, not only in an organizational context, but in a modeling context as well. There can be a steep learning curve and costs associated to train skilled modelers. But, on the other hand, not all of the assurance community need to be modelers. Models themselves must conform to ontologies that enable assurance. This places constraints upon the models and modelers. Optimums have yet to be developed where resources and constraints on modeling must be traded off in the organization and modeling efforts for projects. A number of barriers need to be overcome, as well, which pose challenges to the developers of the software that supports MBSE/MBMA. Information and data must be made to flow seamlessly through the life cycle. Because there is a wide variety of tools used in the community, to avoid the problems of the past of silos, delays, and diverging interests, information should flow among these tools to support the “single source of truth” paradigm of MBSE. This will greatly facilitate MBMA and advancement of assurance functions.

Evans, John W.↗

NASA NTRS2016

The Value of Successful MBSE Adoption

The value of successful adoption of Model Based System Engineering (MBSE) practices is hard to quantify. Most engineers and project managers look at the success in terms of cost. But there are other ways to quantify the value of MBSE and the steps necessary to achieve adoption. The Glenn Research Center (GRC) has been doing Model-Based Engineering (design, structural, etc.) for years, but the system engineering side has not. Since 2010, GRC has been moving from documents centric to MBSE/SysML. Project adoption of MBSE has been slow, but is steadily increasing in both MBSE usage and complexity of generated products. Sharing of knowledge of lessons learned in the implementation of MBSE/SysML is key for others who want to be successful. Along with GRC's implementation, NASA is working hard to increase the successful implementation of MBSE across all the other centers by developing guidelines, templates and libraries for projects to utilize. This presentation will provide insight into recent GRC and NASA adoption efforts, lessons learned and best practices.

MBSE↗

NASA NTRSDate not supplied

A Model-Based Systems Engineering Journey to Developing a Concept of Operations

Starting in 2017, NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) element began a systems engineering transition from traditional, document-centric development to model-centric development when defining its foundation medical systems. These foundation medical systems define a Concept of Operations (ConOps) and identify the generic requirements for a medical system based on assumptions about a generic crew and mission environments and guidance from NASA standards (e.g., Medical “Levels of Care”). By making the transition, ExMC intends to improve communication among stakeholders about foundation medical system requirements and content. In addition, this transition will enable ExMC to lower both development and crew treatment risks for future, mission-specific medical systems. ExMC followed a Model Based Systems Engineering (MBSE) paradigm when developing the foundation medical systems. A model-based approach provides several advantages over a traditional, document-centric approach. First, when Systems Engineers (SE) develop diagrams in a model using a standard modeling language, they produce information dense pictures that facilitate understanding much more efficiently with less room for misinterpretation than text. Second, due to the evolving nature of projects, documentation becomes out of date the minute it is published. This can result in people making decisions based on information that is no longer current, especially if they are referencing a locally-stored copy of a document. A model, on the other hand, is always up to date with the latest approved changes and information. It serves as a single point of truth. Third, a model-centric approach centralizes all important information in one place. Rather than having to flip through separate ConOps documents, design specifications, requirements specifications, and the like to coordinate information, a model captures the content in one, integrated spot. This integration makes tracing information from end-to-end easier with greater reliability. The ExMC Systems Engineering Lifecycle follows a well-defined process. ExMC Systems Engineers perform all major steps of the process, regardless of the development methodology. One of the first steps in the process is developing the ConOps that describes the operation of the system from the point of view of the users. It includes a list of the users and their needs, the goals of the medical system, key assumptions about the system, and definitions of the medical system’s operational environments. For this development effort, ExMC chose to replace the traditional text-based ConOps document with a model. While the decision to change the development workflow was not difficult, implementing the structural and organizational workflows were. It required showing ExMC’s users, most of whom are not Systems Engineers, how the information they require would be presented in the model and to gain their acceptance of this approach. This paper documents key lessons learned during the ConOps transformation by focusing on how the model represents information, the agile workflow used by SEs when developing the model and how it integrates into a project plan, how leadership influenced key users to accept the transformation, and how the users interact with the model information.

Jeffrey Robert Cohen↗

NASA NTRS2013

Modeling Complex Cross-Systems Software Interfaces Using SysML

The complex flight and ground systems for NASA human space exploration are designed, built, operated and managed as separate programs and projects. However, each system relies on one or more of the other systems in order to accomplish specific mission objectives, creating a complex, tightly coupled architecture. Thus, there is a fundamental need to understand how each system interacts with the other. To determine if a model-based system engineering approach could be utilized to assist with understanding the complex system interactions, the NASA Engineering and Safety Center (NESC) sponsored a task to develop an approach for performing cross-system behavior modeling. This paper presents the results of applying Model Based Systems Engineering (MBSE) principles using the System Modeling Language (SysML) to define cross-system behaviors and how they map to crosssystem software interfaces documented in system-level Interface Control Documents (ICDs).

Earth orbit↗