Model Based Systems Engineering (MBSE)
Explore the source record for details and available documents.
Software Tools↗
SEARCH · Engineering Papers
Results for “model based systems engineering (MBSE)”
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.
Model Based Mission Assurance in a Model Based Systems Engineering (MBSE) Framework: State-of-the-Art Assessment
This report explores the current state of the art of Safety and Mission Assurance (S&MA) in projects that have shifted towards Model Based Systems Engineering (MBSE). Its goal is to provide insight into how NASA’s Office of Safety and Mission Assurance (OSMA) should respond to this shift. In MBSE, systems engineering information is organized and represented in models: rigorous computer-based representations, which collectively make many activities easier to perform, less error prone, and scalable. S&MA practices must shift accordingly. The “Objective Structure Hierarchies” recently developed by OSMA provide the framework for understanding this shift. Although the objectives themselves will remain constant, S&MA practices (activities, processes, tools) to achieve them are subject to change. This report presents insights derived from literature studies and interviews. The literature studies gleaned assurance implications from reports of space-related applications of MBSE. The interviews with knowledgeable S&MA and MBSE personnel discovered concerns and ideas for how assurance may adapt. Preliminary findings and observations are presented on the state of practice of S&MA with respect to MBSE, how it is already changing, and how it is likely to change further. Finally, recommendations are provided on how to foster the evolution of S&MA to best fit with MBSE.
Aerospace engineering↗
Method for Tracking and Communicating Aggregate Risk Through the Use of Model-Based Systems Engineering (MBSE) Tools
Large, complex projects can identify a significant number and variety of risks, throughout the project life cycle. These risks are analyzed, mitigated, closed or accepted as independent uncertainties. Once closed or accepted, it is easy for projects to lose awareness of their impact. In reality, each of these risks contributes some amount to the overall risk posture of the project. The ability to track and effectively communicate this aggregate risk has represented a challenge to project management. There have been previous attempts to create a schema to communicate the aggregate effect of risks, without notable success. Most of these attempts have centered on some additive metric derived from the scoring of likelihood and consequence values. This, in and of itself, is a logical approach, but all too often the scores were then aggregated to a level where all context was lost. One weakness has been a lack of attempt to create linkages or logical groups of the risks upon which useful aggregation could then occur. The overall move to model-based (systems) engineering (MBSE) has opened up a vast frontier of opportunities to better integrate all project data. MBSE provides an underlying layer that links data items to each other. Objectives link to requirements, which then link to functions, functions to physical architecture items, and so on, as far down as projects want to model. While it started with a focus on modeling requirements based on things like use cases, efforts are now underway to integrate safety and mission assurance (S&MA) information and analyses, such as risks. This effort, called Model Based Mission Assurance (MBMA), is yielding models that are more useful and are a more accurate representations of the systems. MBSE models, with this ability to link related items, provide a new means of tracking and communicating aggregate risks. In the proposed method, risks are added into the models as distinct items, having attributes that communicate a scoring derived from the likelihood and consequence values as charted on the standard NASA 5x5 risk matrix. Like earlier efforts, each box in the 5x5 has an associated scoring, which may include both a current score and potential post-mitigation/control score. The risk items are then linked to elements of the model, such as system objectives/goals, requirements, functions, or physical architecture items, with "Risk to" relationships. These risks will then be communicated by use of reports generated from the model, detailing all risks and/or hazards linked to model elements. These reports can include aggregate impacts, including a current scoring and potential future state scoring based on the planned mitigations and/or controls. These reports will show all risks, open, accepted, and closed, linked to project objectives or requirements. When run as part of an upcoming risk acceptance discussion, these reports will serve to remind the team of all previous risks that relate to the effected portion of the system. When included as part of periodic program or project reviews, risk reviews, and safety reviews, this method can improve the overall understanding of the system's true risk posture. This proposed method takes full advantage of the advances that modern modeling techniques provide, with a minimal investment of additional time. Utilizing the model environment also enables a near constant access to current state of aggregate risks.
model based mission assurance↗
Model-Based Systems Engineering (MBSE) 101
No abstract available
Integrated Model-Centric Engineering Environment↗
Interface Management for a NASA Flight Project Using Model-Based Systems Engineering (MBSE)
The goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven-step approach to interface management used in several NASA flight projects. The seven-step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment-X (MISSE-X) project. The MISSE-X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition, writing good interface requirements, utilizing interface working groups, developing and controlling interface documents, handling interface agreements, the use of shadow documents, the importance of interface requirement ownership, interface verification, and product transition.
Vipavetz, Kevin↗
A Model-Based Systems Engineering (MBSE) Journey to Developing a Concept of Operations
Explore the source record for details and available documents.
Mary Susan Kaetzer↗
NASA Space Nuclear Propulsion (SNP) MBSE Initiatives
NASA’s Space Nuclear Propulsion (SNP) program is developing several MagicDraw SysML models to support the development of high performance Nuclear Thermal Rocket Engines (NTRE). Currently, the Demonstration Rocket for Agile Cislunar Operations (DRACO) project is aiming to perform the first ever flight demonstration of an NTRE, and NASA is developing a DRACO Insight Project Model Based Systems Engineering (MBSE) model to capture, define, analyze, and report on the flight and ground test system architecture, functional behavior, requirements, risks, and lessons learned. Additional models are in work for engine component trade trees, fault detection sensor coverage analysis using a Goal Function Tree (GFT) plugin, stakeholder engagement, and technology maturation projects. The GFT plugin is the Galois, Inc. Failure Recovery Instruction Generation using Automata derived from Traditional Engineering models (FRIGATE) tool. A new capability for Jira to MagicDraw data sharing using the OpenPDM collaboration platform is under development with partner Victory Solutions, Inc. to enhance risk impact analysis.
Space Nuclear Propulsion (SNP)↗
Relating MBSE to Spacecraft Development: A NASA Pathfinder
The NASA Engineering and Safety Center (NESC) has sponsored a Pathfinder Study to investigate how Model Based Systems Engineering (MBSE) and Model Based Engineering (MBE) techniques can be applied by NASA spacecraft development projects. The objectives of this Pathfinder Study included analyzing both the products of the modeling activity, as well as the process and tool chain through which the spacecraft design activities are executed. Several aspects of MBSE methodology and process were explored. Adoption and consistent use of the MBSE methodology within an existing development environment can be difficult. The Pathfinder Team evaluated the possibility that an "MBSE Template" could be developed as both a teaching tool as well as a baseline from which future NASA projects could leverage. Elements of this template include spacecraft system component libraries, data dictionaries and ontology specifications, as well as software services that do work on the models themselves. The Pathfinder Study also evaluated the tool chain aspects of development. Two chains were considered: 1. The Development tool chain, through which SysML model development was performed and controlled, and 2. The Analysis tool chain, through which both static and dynamic system analysis is performed. Of particular interest was the ability to exchange data between SysML and other engineering tools such as CAD and Dynamic Simulation tools. For this study, the team selected a Mars Lander vehicle as the element to be designed. The paper will discuss what system models were developed, how data was captured and exchanged, and what analyses were conducted.
Othon, Bill↗
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↗
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↗
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↗
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↗
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↗
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↗
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)↗
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↗
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↗