Search NASA⌕ Search

SEARCH · Search NASA

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

At least 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
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 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 functionspresent 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).

In-time Aviation Safety Management System↗
NASA NTRS2022

UAM Airspace Research Roadmap - Rev. 1.2

The UAM Airspace research roadmap is being developed as a new System Engineering methodology leveraging Model Based System Engineering (MBSE) capabilities to help organize, integrate, and communicate NASA's UAM airspace research, with the goal of evolving UAM airspace to UML-4. It provides a basis for prioritizing and coordinating research efforts, and for integrating results that build towards NASA’s research goals. Version 1.2 is a development version of the roadmap, shared publicly to serve as a focal point for discussion and feedback leading to a future baselined version (v2.0). This version supersedes earlier publications, and will be superseded itself by later versions.

UAM↗
NASA NTRSDate not supplied

Digital Assistance for System Requirement Discovery and Analysis using Machine Learning Natural Language Processing Algorithm

NASA’s Air Traffic Management-Exploration (ATM-X) Urban Air Mobility (UAM) Airspace Subproject is conducting research that evolves UAM airspace towards a highly automated and operationally flexible system of the future (see https://www.nasa.gov/uam-overview/ for more information). The complexity of UAM airspace, and its evolution through a series of transformative epochs, requires a planning tool to effectively organize, integrate, and communicate the research that will guide the evolution of UAM operations in the National Airspace System (NAS). The planning tool, called the UAM airspace research roadmap (or just roadmap), is being developed as a new system engineering methodology leveraging model based system engineering (MBSE) and machine learning natural language processing (ML NLP, or just NLP) capabilities. This presentation gives an overview of the NLP application within this system engineering methodology and will describe how it is being used to meet the ATM-X UAM Airspace Subproject’s overarching research goals.

ATM↗
NASA NTRS2023

UAM Airspace Research Roadmap - Rev. 2.0

The UAM Airspace research roadmap is being developed as a new System Engineering methodology leveraging Model Based System Engineering (MBSE) capabilities to help organize, integrate, and communicate NASA's UAM airspace research, with the goal of evolving UAM airspace to UML-4. It provides a basis for prioritizing and coordinating research efforts, and for integrating results that build towards NASA’s research goals. Version 2.0 is a baseline version of the roadmap, shared publicly to serve as a focal point for discussion and feedback. This version supersedes earlier publications, and will be superseded itself by later versions.

UAM↗
NASA NTRSDate not supplied

2023 Artemis Crew Health and Performance System Model Development

While the NASA Human Research Program (HRP) utilizes a Crew Health and Performance (CHP) System to represent all the Agency’s efforts to ensure the health and performance of NASA astronauts, there is no shared mental model of a CHP system at NASA. Some groups may consider a CHP system to be only a medical kit, while others may not be using the concept at all. To facilitate the integration of functions and capabilities to ensure astronaut health and performance during vehicle development, HRP has proposed a CHP Shared Mental Model derived from the NASA Human Health, Medical, and Performance Spaceflight Standards (NASA-STD-3001 Vol.1/Vol.2). [1] Even though many vehicle, ground, and communication systems as well as mission operations are modeled for the Artemis Campaigns, no mission level CHP system model was created to achieve the intent of the HRP CHP Shared Mental Model. The lack of this model renders it difficult to visualize and understand how the many programs work together to provide the necessary cross program functions and capabilities to ensure the health and performance of the crew throughout an Artemis mission. For this purpose, the Exploration Medical Capability (ExMC) element of HRP developed a CHP system model for the Artemis III and IV missions to provide a view of how each program contributes to and interacts with the overall CHP system. To develop the 2023 Artemis CHP system model, ExMC leveraged existing data and models from the Moon to Mars Program Office, the Office of the Chief Health and Medical Officer (OCHMO) and the Orion, Gateway, Extravehicular Activity and Human Surface Mobility (EHP) and Human Landing System (HLS) programs. By using a Model-Based Systems Engineering (MBSE) approach, existing requirements, functions, and concepts of operations were combined to create a single system model focused on representing CHP from the launch to the return to Earth segments of the Artemis III and IV missions. Additionally, by incorporating the HRP Systems Platform for Aggregating and Relating Capabilities, or SPARC tool, the data from the programs was also related back to the 2nd volume of the NASA Human Health, Medical, and Performance Spaceflight Standard (NASA-STD-3001, Vol.2) and the human system risks identified by the Human System Risk Board (HSRB). The first version of the 2023 Artemis CHP system model was baselined in Fall of 2023 after the model was demonstrated to be a potentially useful tool for systems engineers integrating CHP capabilities in vehicle development as well as members of the Health and Medical Technical Authority providing oversight of those programs. The model may also be useful to any stakeholder of astronaut health and performance by providing insights on how an Artemis mission satisfies the NASA Human Health, Medical, and Performance Spaceflight Standards as well as how they mitigate the HSRB Human System Risks. This presentation highlights how the model was developed and the possible benefits of the model. [1] NASA HRP (2022), Crew Health and Performance System Whitepaper

Systems engineering↗
NASA NTRS2024

2023 Artemis Crew Health and Performance (CHP) System Model Development

While the NASA Human Research Program (HRP) utilizes a Crew Health and Performance (CHP) System to represent all the Agency’s efforts to ensure the health and performance of NASA astronauts, there is no shared mental model of a CHP system at NASA. Some groups may consider a CHP system to be only a medical kit, while others may not be using the concept at all. To facilitate the integration of functions and capabilities to ensure astronaut health and performance during vehicle development, HRP has proposed a CHP Shared Mental Model derived from the NASA Human Health, Medical, and Performance Spaceflight Standards (NASA-STD-3001 Vol.1/Vol.2). [1] Even though many vehicle, ground, and communication systems as well as mission operations are modeled for the Artemis Campaigns, no mission level CHP system model was created to achieve the intent of the HRP CHP Shared Mental Model. The lack of this model renders it difficult to visualize and understand how the many programs work together to provide the necessary cross program functions and capabilities to ensure the health and performance of the crew throughout an Artemis mission. For this purpose, the Exploration Medical Capability (ExMC) element of HRP developed a CHP system model for the Artemis III and IV missions to provide a view of how each program contributes to and interacts with the overall CHP system. To develop the 2023 Artemis CHP system model, ExMC leveraged existing data and models from the Moon to Mars Program Office, the Office of the Chief Health and Medical Officer (OCHMO) and the Orion, Gateway, Extravehicular Activity and Human Surface Mobility (EHP) and Human Landing System (HLS) programs. By using a Model-Based Systems Engineering (MBSE) approach, existing requirements, functions, and concepts of operations were combined to create a single system model focused on representing CHP from the launch to the return to Earth segments of the Artemis III and IV missions. Additionally, by incorporating the HRP Systems Platform for Aggregating and Relating Capabilities, or SPARC tool, the data from the programs was also related back to the 2nd volume of the NASA Human Health, Medical, and Performance Spaceflight Standard (NASA-STD-3001, Vol.2) and the human system risks identified by the Human System Risk Board (HSRB). The first version of the 2023 Artemis CHP system model was baselined in Fall of 2023 after the model was demonstrated to be a potentially useful tool for systems engineers integrating CHP capabilities in vehicle development as well as members of the Health and Medical Technical Authority providing oversight of those programs. The model may also be useful to any stakeholder of astronaut health and performance by providing insights on how an Artemis mission satisfies the NASA Human Health, Medical, and Performance Spaceflight Standards as well as how they mitigate the HSRB Human System Risks. This presentation highlights how the model was developed and the possible benefits of the model. [1] NASA HRP (2022), Crew Health and Performance System Whitepaper

Systems engineering↗
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 NTRS2010

Re-Engineering Complex Legacy Systems at NASA

The Flight Production Process (FPP) Re-engineering project has established a Model-Based Systems Engineering (MBSE) methodology and the technological infrastructure for the design and development of a reference, product-line architecture as well as an integrated workflow model for the Mission Operations System (MOS) for human space exploration missions at NASA Johnson Space Center. The design and architectural artifacts have been developed based on the expertise and knowledge of numerous Subject Matter Experts (SMEs). The technological infrastructure developed by the FPP Re-engineering project has enabled the structured collection and integration of this knowledge and further provides simulation and analysis capabilities for optimization purposes. A key strength of this strategy has been the judicious combination of COTS products with custom coding. The lean management approach that has led to the success of this project is based on having a strong vision for the whole lifecycle of the project and its progress over time, a goal-based design and development approach, a small team of highly specialized people in areas that are critical to the project, and an interactive approach for infusing new technologies into existing processes. This project, which has had a relatively small amount of funding, is on the cutting edge with respect to the utilization of model-based design and systems engineering. An overarching challenge that was overcome by this project was to convince upper management of the needs and merits of giving up more conventional design methodologies (such as paper-based documents and unwieldy and unstructured flow diagrams and schedules) in favor of advanced model-based systems engineering approaches.

Ruszkowski, James↗
NASA NTRS2011

The Development of NASA's Fault Management Handbook

Disciplined approach to Fault Management (FM) has not always been emphasized by projects, contributing to major schedule and cost overruns. Progress is being made on a number of fronts outside of Handbook effort: (1) Processes, Practices and Tools being developed at some Centers and Institutions (2) Management recognition . Constellation FM roles, Discovery/New Frontiers mission reviews (3) Potential Technology solutions . New approaches could avoid many current pitfalls (3a) New FM architectures, including model ]based approach integrated with NASA fs MBSE efforts (3b) NASA fs Office of the Chief Technologist: FM identified in seven of NASA fs 14 Space Technology Roadmaps . opportunity to coalesce and establish thrust area to progressively develop new FM techniques FM Handbook will help ensure that future missions do not encounter same FM ]related problems as previous missions Version 1 of the FM Handbook is a good start.

Fault Management↗
NASA NTRS2013

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

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

State-Based Behavior Modeling of the Integrated SLS-MPCV System

In NASA's effort to foster a human spaceflight capability beyond Earth's orbit, two space systems are being developed - the Space Launch System (SLS) and the Multi-Purpose Crew Vehicle (MPCV). As of this time, the interactions between the two systems during launch are not fully detailed. To remedy this situation, a Systems Engineering approach utilizing models was developed to investigate the behavior of the integrated SLS-MPCV stack during ascent and abort situations. Specifically, this innovative approach combines aspects of Model-Based Systems Engineering (MBSE) and state analysis to simultaneously model the physical, functional, and behavioral aspects of systems. This approach focuses solely on the interactions between the systems, leaving much of the internal workings of either system at a logical level (i.e., black box). By utilizing this newly defined approach, a behavior model for the integrated SLS-MPCV stack was developed, emphasizing only the subset of interactions between the systems that impact behavior. Finally, analysis is performed within the model to investigate requirements gaps and examine the execution times of key behaviors related to various ascent phases and abort scenarios. The work described in this paper is merely a portion of the outlined effort being undertaken for this project; only a segment of the SLS-MPCV system behavior will be described.

Space Launch System (SLS)↗
NASA NTRS2012

Model-Based Systems Engineering Approach to Managing Mass Margin

When designing a flight system from concept through implementation, one of the fundamental systems engineering tasks ismanaging the mass margin and a mass equipment list (MEL) of the flight system. While generating a MEL and computing a mass margin is conceptually a trivial task, maintaining consistent and correct MELs and mass margins can be challenging due to the current practices of maintaining duplicate information in various forms, such as diagrams and tables, and in various media, such as files and emails. We have overcome this challenge through a model-based systems engineering (MBSE) approach within which we allow only a single-source-of-truth. In this paper we describe the modeling patternsused to capture the single-source-of-truth and the views that have been developed for the Europa Habitability Mission (EHM) project, a mission concept study, at the Jet Propulsion Laboratory (JPL).

cloud comu↗
NASA NTRS2011

The Development of NASA's Fault Management Handbook

Disciplined approach to Fault Management (FM) has not always been emphasized by projects, contributing to major schedule and cost overruns: (1) Often faults aren't addressed until nominal spacecraft design is fairly stable. (2) Design relegated to after-the-fact patchwork, Band-Aid approach. Progress is being made on a number of fronts outside of Handbook effort: (1) Processes, Practices and Tools being developed at some Centers and Institutions (2) Management recognition. Constellation FM roles, Discovery/New Frontiers mission reviews (3) Potential Technology solutions. New approaches could avoid many current pitfalls (3a) New FM architectures, including model-based approach integrated with NASA's MBSE (Model-Based System Engineering) efforts (3b) NASA's Office of the Chief Technologist: FM identified in seven of NASA's 14 Space Technology Roadmaps. Opportunity to coalesce and establish thrust area to progressively develop new FM techniques. FM Handbook will help ensure that future missions do not encounter same FM-related problems as previous missions. Version 1 of the FM Handbook is a good start: (1) Still need Version 2 Agency-wide FM Handbook to expand Handbook to other areas, especially crewed missions. (2) Still need to reach out to other organizations to develop common understanding and vocabulary. Handbook doesn't/can't address all Workshop recommendations. Still need to identify how to address programmatic and infrastructure issues.

Fault Management↗
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↗
NASA NTRS2013

Domain-Specific Languages and Diagram Customization for a Concurrent Engineering Environment

A major open question for advocates of Model-Based Systems Engineering (MBSE) is the question of how system and subsystem engineers will work together. The Systems Modeling Language (SysML), like any language intended for a large audience, is in tension between the desires for simplicity and for expressiveness. In order to be more expressive, many specialized language elements may be introduced, which will unfortunately make a complete understanding of the language a more daunting task. While this may be acceptable for systems modelers, it will increase the challenge of including subsystem engineers in the modeling effort. One possible answer to this situation is the use of Domain-Specific Languages (DSL), which are fully supported by the Unified Modeling Language (UML). SysML is in fact a DSL for systems engineering. The expressive power of a DSL can be enhanced through the use of diagram customization. Various domains have already developed their own schematic vocabularies. Within the space engineering community, two excellent examples are the propulsion and telecommunication subsystems. A return to simple box-and-line diagrams (e.g., the SysML Internal Block Diagram) are in many ways a step backward. In order allow subsystem engineers to contribute directly to the model, it is necessary to make a system modeling tool at least approximate in accessibility to drawing tools like Microsoft PowerPoint and Visio. The challenge is made more extreme in a concurrent engineering environment, where designs must often be drafted in an hour or two. In the case of the Jet Propulsion Laboratory's Team X concurrent design team, a subsystem is specified using a combination of PowerPoint for drawing and Excel for calculation. A pilot has been undertaken in order to meld the drawing portion and the production of master equipment lists (MELs) via a SysML authoring tool, MagicDraw. Team X currently interacts with its customers in a process of sharing presentations. There are several inefficiencies that arise from this situation. The first is that a customer team must wait two weeks to a month (which is 2-4 times the duration of most Team X studies themselves) for a finalized, detailed design description. Another is that this information must be re-entered by hand into the set of engineering artifacts and design tools that the mission concept team uses after a study is complete. Further, there is no persistent connection to Team X or institutionally shared formulation design tools and data after a given study, again reducing the direct reuse of designs created in a Team X study. This paper presents the underpinnings of subsystem DSLs as they were developed for this pilot. This includes specialized semantics for different domains as well as the process by which major categories of objects were derived in support of defining the DSLs. The feedback given to us by the domain experts on usability, along with a pilot study with the partial inclusion of these tools is also discussed.

Cole, Bjorn↗
NASA NTRS2018

A SysML Model Template for NASA Concurrent Engineering Studies

Systems Engineers at NASA Langley’s Engineering Design Studio (EDS) have been developing a SysML** template that models both the EDS concurrent engineering study process and the system of interest for the study. Specifically, the model template is used to develop end-to-end space-based mission concepts. The model template evolved through targeted use and technical feedback during several EDS studies in 2016-17. This year, a model template version was completed that is being tested for use throughout EDS studies. It features ease of navigation through the documented study process to create the logistical articles (e.g. session agenda) and technical articles (e.g. system requirements) connected in the study SysML model, resulting in demonstrable and trackable relationships between the system design and the study goals and objectives. The model template allows easy release of the system of interest portion at the end of the EDS study. The customers may use this as a starter model as their project moves forward. The model template design details and the motivation for them will be explained in this paper. This will be followed by the results of the first trials of the model template in an EDS study, and discussion of the integration of this template into the NASA MBSE Community of Practice.

Infeld, Samantha I.↗