Search NASA⌕ Search

SEARCH · Search NASA

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

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

At least 109 records · Page 6

Model-Based Systems

Engineers, who design systems using text specification documents, focus their work upon the completed system to meet Performance, time and budget goals. Consistency and integrity is difficult to maintain within text documents for a single complex system and more difficult to maintain as several systems are combined into higher-level systems, are maintained over decades, and evolve technically and in performance through updates. This system design approach frequently results in major changes during the system integration and test phase, and in time and budget overruns. Engineers who build system specification documents within a model-based systems environment go a step further and aggregate all of the data. They interrelate all of the data to insure consistency and integrity. After the model is constructed, the various system specification documents are prepared, all from the same database. The consistency and integrity of the model is assured, therefore the consistency and integrity of the various specification documents is insured. This article attempts to define model-based systems relative to such an environment. The intent is to expose the complexity of the enabling problem by outlining what is needed, why it is needed and how needs are being addressed by international standards writing teams.

Frisch, Harold P.↗

System Safety Analysis of Complex NASA Systems with Model Based Engineering

The emergence of model-based engineering is transforming design and analysis methodologies [5]. A recognized benefit of model-based engineering is the existence of a “single source of truth” about the system that becomes the authoritative source of data and information for designers, analysts, and developers. This promotes consistency and efficiency as the design emerges and can be used to further optimize the design. Integrating System Safety Engineers to the “single source of truth” will ensure that the outputs of their assessments and analyses are relevant to the design as it evolves. Use of an integrated system model enables near immediate evaluation of a design change as well as development of operational processes for risk assessment and communication. Such models can enable efficient and timely analysis of system hazards (e.g., hazard fault tree analysis and procedure simulations) and produce complete, accurate, and more consistent products (e.g., hazard reports and safety requirement evaluations). Therefore, an agency-sponsored team at Goddard Space Flight Center (GSFC) recently completed a System Safety Study of modeling and testing capabilities as part of a Model-Based Safety and Mission Assurance Initiative (MBSMAI). Using an existing model developed for reliability analyses [1], GSFC modeling and system safety experts performed system safety analysis/modeling and produced safety products. The team evaluated model-based feasibility to support System Safety Engineering, developed safety analysis modeling processes, and identified tool capability advancement/development needs. These study results indicate model-based engineering is valid and useable for System

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

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↗

Medical System Foundation Overview for Long-Duration Lunar Orbit and Surface Operations Missions

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 long-duration lunar orbit and surface operation missions by employing a systems engineering approach using model-based systems engineering tools. This Foundation model includes a concept of operations; functional decomposition; clinical content (medical conditions, capabilities, and resources); associated functional, interface and non-functional technical requirements; and traces to the current versions of NASA standards documents and parent-level (Program- and Vehicle habitat system level) requirements. Collectively, these components constitute a foundation that serves as a starting point for a medical system that meets the Level of Care IV requirement. The Foundation was developed by a multidisciplinary team consisting of systems engineers, scientists, and clinicians across NASA, and information is presented in an easily accessible format that is understandable across disciplines. Stakeholders can use the Foundation to analyze the traces between medical capabilities, medical conditions, medical resources, and requirements and to identify medical system interfaces with other vehicle systems/subsystems. It can also be used as a basis for performing trades on risks vs. medical system mass and volume allocation. 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. The presentation also discusses Foundation modifications based on the recently updated versions of the NASA 3001 Standards.

S. Lumpkins↗

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↗

Integration of Uncertainty Quantification in a Model-Based Systems Analysis and Engineering Framework

This paper presents a technical approach to improve the confidence in the systems analysis process by integrating Uncertainty Quantification (UQ) techniques within a Model-Based Systems Analysis and Engineering (MBSA&E) framework. The MBSA&E architecture uses system models and multidisciplinary analytical solutions as central artifacts for system design and analysis. The integration of UQ enables engineers to assess and mitigate uncertainties associated with a system model, design parameters, and constraint inputs, leading to more complete design studies and further informed decision-making processes. The proposed approach leverages the strengths of MBSA&E and extends it with a UQ methodology to quantify uncertainties in the input parameters and to trace the uncertainties as they propagate throughout the system model. To demonstrate the effectiveness of an integrated MBSA&E-UQ approach, a case study involving a simplified analysis of a Transonic Truss-Braced Wing (TTBW) concept vehicle is performed. This integration enables a more comprehensive evaluation of system performance and behavior under uncertainty and a more robust approach for system design and analysis. Lastly, the paper addresses the challenges and considerations associated with integrating UQ into an MBSA&E framework.

systems analysis↗

Integration of Uncertainty Quantification in a Model-Based Systems Analysis and Engineering Framework

This paper presents a technical approach to improve the confidence in the systems analysis process by integrating Uncertainty Quantification (UQ) techniques within a Model-Based Systems Analysis and Engineering (MBSA&E) framework. The MBSA&E architecture uses system models and multidisciplinary analytical solutions as central artifacts for system design and analysis. The integration of UQ enables engineers to assess and mitigate uncertainties associated with a system model, design parameters, and constraint inputs, leading to more complete design studies and further informed decision-making processes. The proposed approach leverages the strengths of MBSA&E and extends it with a UQ methodology to quantify uncertainties in the input parameters and to trace the uncertainties as they propagate throughout the system model. To demonstrate the effectiveness of an integrated MBSA&E-UQ approach, a case study involving a simplified analysis of a Transonic Truss-Braced Wing (TTBW) concept vehicle is performed. This integration enables a more comprehensive evaluation of system performance and behavior under uncertainty and a more robust approach for system design and analysis. Lastly, the paper addresses the challenges and considerations associated with integrating UQ into an MBSA&E framework.

systems analysis↗

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

Implementation of a Goal-Based Systems Engineering Process Using the Systems Modeling Language (SysML)

Building upon the purpose, theoretical approach, and use of a Goal-Function Tree (GFT) being presented by Dr. Stephen B. Johnson, described in a related Infotech 2013 ISHM abstract titled "Goal-Function Tree Modeling for Systems Engineering and Fault Management", this paper will describe the core framework used to implement the GFTbased systems engineering process using the Systems Modeling Language (SysML). These two papers are ideally accepted and presented together in the same Infotech session. Statement of problem: SysML, as a tool, is currently not capable of implementing the theoretical approach described within the "Goal-Function Tree Modeling for Systems Engineering and Fault Management" paper cited above. More generally, SysML's current capabilities to model functional decompositions in the rigorous manner required in the GFT approach are limited. The GFT is a new Model-Based Systems Engineering (MBSE) approach to the development of goals and requirements, functions, and its linkage to design. As a growing standard for systems engineering, it is important to develop methods to implement GFT in SysML. Proposed Method of Solution: Many of the central concepts of the SysML language are needed to implement a GFT for large complex systems. In the implementation of those central concepts, the following will be described in detail: changes to the nominal SysML process, model view definitions and examples, diagram definitions and examples, and detailed SysML construct and stereotype definitions.

Patterson, Jonathan D.↗

Implementation of a Goal-Based Systems Engineering Process Using the Systems Modeling Language (SysML)

Building upon the purpose, theoretical approach, and use of a Goal-Function Tree (GFT) being presented by Dr. Stephen B. Johnson, described in a related Infotech 2013 ISHM abstract titled "Goal-Function Tree Modeling for Systems Engineering and Fault Management", this paper will describe the core framework used to implement the GFTbased systems engineering process using the Systems Modeling Language (SysML). These two papers are ideally accepted and presented together in the same Infotech session. Statement of problem: SysML, as a tool, is currently not capable of implementing the theoretical approach described within the "Goal-Function Tree Modeling for Systems Engineering and Fault Management" paper cited above. More generally, SysML's current capabilities to model functional decompositions in the rigorous manner required in the GFT approach are limited. The GFT is a new Model-Based Systems Engineering (MBSE) approach to the development of goals and requirements, functions, and its linkage to design. As a growing standard for systems engineering, it is important to develop methods to implement GFT in SysML. Proposed Method of Solution: Many of the central concepts of the SysML language are needed to implement a GFT for large complex systems. In the implementation of those central concepts, the following will be described in detail: changes to the nominal SysML process, model view definitions and examples, diagram definitions and examples, and detailed SysML construct and stereotype definitions.

Breckenridge, Jonathan T.↗

Towards a Reference Architecture for Model-Based Engineering Environments

A key aspect of adopting model-based systems engineering as a practice in an organization is the design and development, and adoption of corresponding processes and tools that support the model-based paradigm. In an effort to enable the unified implementation of such processes and tools, this paper introduces a reference architecture model that serves as a specification for a model-based engineering environment. Current systems engineering practices, products, processes and technologies are used as input for continuously refining the architecture model. In the paper, we introduce and report on the current status of this reference architecture model, and present the methodology applied in developing the reference architecture. We conclude that while there are a very large number of domain- or application-specific processes requiring specialized behavior, these can be reduced through abstraction to a small set of core functions that need to be supported by a realization of a model-based engineering environment. Only very few organization-domain- or application-specific aspects require specialized consideration.

Herzig, Sebastian J. I.↗

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↗

NASA Aeronautics Research Mission Directorate System Security Engineering Approaches

System security engineering (SSE) is a set of formal engineering methods and is considered a subset of systems engineering. It is a relatively new development in systems engineering with the initial NIST (National Institute of Standards) standard published in November of 2016 with updates in 2018, and 2022. The guiding principles in our methodology are based in NIST Special Publication 800-160 Vol. 1 “Systems Security Engineering: Considerations For A Multidisciplinary Approach In The Engineering Of Trustworthy Secure Systems” and integrate methodologies from common IT (Information Technology) threat modeling approaches utilizing MBSE (Model-Based Systems Engineering). The presentation will discuss how our teams utilize SSE and MBSE (Model-Based Systems Engineering) to develop secure architectures for systems under development in our NASA aeronautics research environment. This includes the activities to develop Protection Needs (PN) that, in turn result in security requirements in the design context and policies for the future state operational context for system protection. The process of applying SSE to analyze project architectures and ConOps (Concept of Operations) is intended to ensure the transferred research is both secure and securable in a “real-world” setting.

Systems Security Engineering↗

Model-Based SMA Initiative Phase 1 Report: Reliability Tips Excerpt

The emergence of model-based engineering, with Model- Based Systems Engineering (MBSE) leading the way, is transforming design and analysis methodologies. [7] The recognized benefits to systems development include moving from document-centric information systems and document-centric project communication to a model-centric environment in which control of design changes in the life cycles is facilitated. In addition, a “single source of truth” about the system, that is up-to-date in all respects of the design, becomes the authoritative source of data and information about the system. This promotes consistency and efficiency in regard to integration of the system elements as the design emerges and thereby may further optimize the designs. Therefore Reliability Engineers (REs) supporting NASA missions must be integrated into model-based engineering, using these recommended modeling techniques, to ensure the outputs of their analyses are relevant and value-needed to the design, development, and operational processes for failure risk assessment and communication.

Nancy J. Lindsey↗

A Model-Based Approach to Engineering Behavior of Complex Aerospace Systems

One of the most challenging yet poorly defined aspects of engineering a complex aerospace system is behavior engineering, including definition, specification, design, implementation, and verification and validation of the system's behaviors. This is especially true for behaviors of highly autonomous and intelligent systems. Behavior engineering is more of an art than a science. As a process it is generally ad-hoc, poorly specified, and inconsistently applied from one project to the next. It uses largely informal representations, and results in system behavior being documented in a wide variety of disparate documents. To address this problem, JPL has undertaken a pilot project to apply its institutional capabilities in Model-Based Systems Engineering to the challenge of specifying complex spacecraft system behavior. This paper describes the results of the work in progress on this project. In particular, we discuss our approach to modeling spacecraft behavior including 1) requirements and design flowdown from system-level to subsystem-level, 2) patterns for behavior decomposition, 3) allocation of behaviors to physical elements in the system, and 4) patterns for capturing V&V activities associated with behavioral requirements. We provide examples of interesting behavior specification patterns, and discuss findings from the pilot project.

SysML↗

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↗