Engineering Papers⌕ Search

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.

At least 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

Model Based Systems Engineering on the Europa Mission Concept Study

At the start of 2011, the proposed Jupiter Europa Orbiter (JEO) mission was staffing up in expectation of becoming an official project later in the year for a launch in 2020. A unique aspect of the pre-project work was a strong emphasis and investment on the foundations of Model-Based Systems Engineering (MBSE). As so often happens in this business, plans changed: NASA's budget and science priorities were released and together fundamentally changed the course of JEO. As a result, it returned to being a study task whose objective is to propose more affordable ways to accomplish the science. As part of this transition, the question arose as to whether it could continue to afford the investment in MBSE. In short, the MBSE infusion has survived and is providing clear value to the study effort. By leveraging the existing infrastructure and a modest additional investment, striking advances in the capture and analysis of designs using MBSE were achieved. In the process, the need to remain relevant in the new environment has brought about a wave of innovation and progress. The effort has reaffirmed the importance of architecting. It has successfully harnessed the synergistic relationship of architecting to system modeling. We have found that MBSE can provide greater agility than traditional methods. We have also found that a diverse 'ecosystem' of modeling tools and languages (SysML, Mathematica, even Excel) is not only viable, but an important enabler of agility and adaptability. This paper will describe the successful application of MBSE in the dynamic environment of early mission formulation, the significant results produced and lessons learned in the process.

Bayer, Todd J.↗
NASA NTRSDate not supplied

Developing Concepts of Operations Using Multi-Step Tool Techniques With Large Language Models

The National Aeronautics and Space Administration (NASA) Air Mobility Pathfinders (AMP) project is developing and evaluating concepts of operations (ConOps) for safe, secure, and scalable Urban Air Mobility (UAM) operations. The AMP project’s Operational Concepts, Architecture, and Requirements Integration (OCARI) Team is using a Model Based System Engineering (MBSE) approach for integration, interoperability, and traceability of Advanced Air Mobility (AAM) ecosystems centered around urban air taxi services. The team’s goal is to define structures and behaviors needed for system feasibility, readiness, and interoperability, establish a UAM knowledge base, and trace and validate assumptions and requirements relevant to AAM. NASA Langley Research Center (LaRC) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers together across organizational boundaries. It does so through the management of an information database defined by mathematical, data science, and system engineering principles. Machine Learning (ML) algorithms play a key role in this concept by extracting meaningful knowledge from relational and graph databases, document repositories, and system artifacts, which the human user leverages to greatly improve the efficiency and effectiveness of their research. Recent advancements in the field of Large Language Models (LLMs), specifically models trained for tool use, such as Command-R , now allow for the reliable implementation of single-step and multi-step tool-centric systems. These techniques provide the LLM with a set of tools, in our case Python functions, that can be called on to answer a much wider range of questions compared to LLMs implemented using a traditional single-source or Retrieval Augmented Generation (RAG) approach. Through this method, the LLM can pull information from multiple data sources, such as relational or graph databases, document repositories, application programming interfaces (APIs), and SysML artifacts depending on the user’s question. The LLM can also output the information in a variety of different formats, using output generation tools, such as CSV, UML, or SysML artifacts. Additionally, tools can be assigned roles and can work together to provide answers to queries in an “agent” like approach, similar to that implemented by Microsoft’s AutoGen framework where different agents can converse with each other to accomplish tasks. Previously, our team developed a chatbot system with “agent like” functionality in the form of different “modes” the user could select from a user interface (UI), this architecture can be seen on the left in figure 1. Three different modes were implemented, the first mode allowed the LLM to utilize the structures and algorithms within a graph database to trace UAM requirements. The second mode gave the LLM access to a vector search capable of providing relevant information from thousands of document pages related to UAM ConOps and requirements. The third mode served as a general assistant where users could enter open-ended questions and custom prompts to utilize the LLM for different use-cases. This system improved the process surrounding generating and analyzing information related to UAM requirements, however, the implementation provided a clunky user experience. Users were required to know what mode to select within the UI in advance before entering their question to the selected tool. Moreover, the different tools were isolated from each other, they lacked bidirectional links that would allow for tools to collaborate to generate better responses. Our team is working on a new architecture, seen on the right in the below figure, with the goal to address many of the UX shortcomings of our original system while improving the accuracy and depth of responses from the LLM. This new system will automatically select the appropriate tool to use based off the user’s question. Each tool will be capable of calling on any of the other tools available to the LLM, resulting in a collaborative pipeline where tools can pass data between other tools until enough data is received to generate an answer to the user’s question. Using a locally deployed, open-source, LLM, the NASA OCARI team, in collaboration with Collins Aerospace, will implement a prototype application that will bridge knowledge across multiple sources to assist System Engineers (SEs) with requirements discovery and tracing, research question and use case identification, and assumption validation. Such a system will also allow SEs to more easily, and intuitively, explore the AAM ecosystem, ultimately improving the efficiency and effectiveness of the SE's research and decision-making processes surrounding ConOps development and validation. In this session, our team will provide a video demonstration of our new prototype architecture in action. We will also present an overview of our prototype system architecture and talk about its advantages over traditional LLM deployments along with how those advantages can provide additional value to the field of System Engineering.

systems engineering↗
NASA NTRS2017

Digital Model-Based Engineering: Expectations, Prerequisites, and Challenges of Infusion

Digital model-based engineering (DMbE) is the use of digital artifacts, digital environments, and digital tools in the performance of engineering functions. DMbE is intended to allow an organization to progress from documentation-based engineering methods to digital methods that may provide greater flexibility, agility, and efficiency. The term 'DMbE' was developed as part of an effort by the Model-Based Systems Engineering (MBSE) Infusion Task team to identify what government organizations might expect in the course of moving to or infusing MBSE into their organizations. The Task team was established by the Interagency Working Group on Engineering Complex Systems, an informal collaboration among government systems engineering organizations. This Technical Memorandum (TM) discusses the work of the MBSE Infusion Task team to date. The Task team identified prerequisites, expectations, initial challenges, and recommendations for areas of study to pursue, as well as examples of efforts already in progress. The team identified the following five expectations associated with DMbE infusion, discussed further in this TM: (1) Informed decision making through increased transparency, and greater insight. (2) Enhanced communication. (3) Increased understanding for greater flexibility/adaptability in design. (4) Increased confidence that the capability will perform as expected. (5) Increased efficiency. The team identified the following seven challenges an organization might encounter when looking to infuse DMbE: (1) Assessing value added to the organization. Not all DMbE practices will be applicable to every situation in every organization, and not all implementations will have positive results. (2) Overcoming organizational and cultural hurdles. (3) Adopting contractual practices and technical data management. (4) Redefining configuration management. The DMbE environment changes the range of configuration information to be managed to include performance and design models, database objects, as well as more traditional book-form objects and formats. (5) Developing information technology (IT) infrastructure. Approaches to implementing critical, enabling IT infrastructure capabilities must be flexible, reconfigurable, and updatable. (6) Ensuring security of the single source of truth (7) Potential overreliance on quantitative data over qualitative data. Executable/ computational models and simulations generally incorporate and generate quantitative vice qualitative data. The Task team also developed several recommendations for government, academia, and industry, as discussed in this TM. The Task team recommends continuing beyond this initial work to further develop the means of implementing DMbE and to look for opportunities to collaborate and share best practices.

Hale, J. P.↗
NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a focused design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

systems engineering↗
NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a narrow design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

Iwata, Curtis↗
NASA NTRS2016

Early Engagement of Safety and Mission Assurance Expertise Using Systems Engineering Tools: A Risk-Based Approach to Early Identification of Safety and Assurance Requirements

Decades of systems engineering practice have demonstrated that the earlier the identification of requirements occurs, the lower the chance that costly redesigns will needed later in the project life cycle. A better understanding of all requirements can also improve the likelihood of a design's success. Significant effort has been put into developing tools and practices that facilitate requirements determination, including those that are part of the model-based systems engineering (MBSE) paradigm. These efforts have yielded improvements in requirements definition, but have thus far focused on a design's performance needs. The identification of safety & mission assurance (S&MA) related requirements, in comparison, can occur after preliminary designs are already established, yielding forced redesigns. Engaging S&MA expertise at an earlier stage, facilitated by the use of MBSE tools, and focused on actual project risk, can yield the same type of design life cycle improvements that have been realized in technical and performance requirements.

Requirement↗
NASA NTRS2016

Identifying Where Mission Assurance Can Benefit from Model Based Systems Engineering

Model Based Systems Engineering (MBSE) is being introduced and used to support many aspects of the engineering of complex systems. Our focus is on space systems, with a particular interest in Mission Assurance of those systems. We seek to identify where Mission Assurance can potentially benefit when a space system is developed using an MBSE approach. To do so we consider how MBSE can help provide the evidence that Mission Assurance needs, using the recently developed NASA Reliability and Maintainability Objective Hierarchy as the exposition of those needs. We illustrate this MBSE’s potential contributions using examples drawn from our prior survey of the MBSE literature addressing space mission assurance concerns. The overall conclusion we draw from this is that there are numerous ways in which MBSE may, and in some cases already does, support Mission Assurance.

Feather, Martin S.↗
NASA NTRS2020

Strategic Perspectives on the Future of Systems Engineering at NASA

NASA’s Model-Based Systems Engineering (MBSE) Infusion and Modernization Initiative (MIAMI) chartered a strategy group comprising early to mid-career NASA subject matter experts with diverse experiences to look into the future of systems engineering at NASA. The purpose of the group was to provide a vision for the future state of systems engineering practices and to develop a strategic plan to enable the evolution of the art up to 20 years in the future. The group used a design thinking approach to gather ideas and obtained insight into current engineering processes and domain outlook by interviewing engineers of varying expertise and experiences who had worked on teams of different sizes for missions large and small. The group built a roadmap to highlight future needs, projected capabilities, and technology and competency gaps and developed a strategic plan to ensure the expedient introduction of these capabilities. The resulting strategic plan recommends capability development and workforce strategies and provides guidance for Agency-wide SE policy. Artifacts, details, and raw data from the strategy team’s work are contained in NASA/TM-20205002911/SUPPL, Strategic Perspectives on the Future of Systems Engineering at NASA: Supplemental Information: Appendixes A to K.

Anupa R Bajwa↗
NASA NTRSDate not supplied

Exploration Medical Capability Systems Engineering Overview and Update

Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element’s approach to enabling the necessary autonomy. The ExMC Systems Engineering (SE) team’s mission is to “Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds.” The Element’s work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS and what they are focusing on for the upcoming year.

Kerry McGuire↗
NASA NTRS2021

System Validation on the Europa Clipper mission in Early Implementation Phase

NASA’s next flag-ship mission - Europa Clipper, will embark on a journey to Jupiter’s icy moon Europa in 2024 to assess its environment and habitability with a highly capable spacecraft. Post Jupiter-Orbit-Insertion, the spacecraft will be commanded to perform intricate, yet meticulously planned Europa flybys to perform science investigations using a suite of instruments, while withstanding Jupiter’s harsh radiation environment. The success of this mission is dependent on a well-coordinated project and its elements such as the flight hardware and software, the ground support and mission operations teams, procedures and other cross-cutting elements. The Europa Clipper project needs to ensure that these elements are realized at a reasonable confidence level prior to launch and other mission critical events. System Validation test and analysis activities exercise and confirm the integrity of the system of all project elements in the expected flight environment with reasonable stressing conditions. These activities go beyond system design requirements verification and are driven by validation objectives that describe the end-to-end functional and operational capabilities required during nominal and off-nominal flight-like scenarios and critical events. The challenges associated with validating that the Europa Clipper project as a whole can function and perform correctly to meet the intended mission objectives with the as-delivered capabilities of all of its elements are daunting. This paper discusses the systematic methodology established in the early implementation phase of the Europa Clipper project for developing System Validation activities and their validation objectives, and addressing any validation-related challenges on the project. Approaches include decomposition of mission objectives using activity timelines in the Mission Design plan for developing nominal scenarios, use of fault trees for exploring off-nominal cases and system boundaries, and use of Model-based Systems Engineering (MBSE) tools for planning and prioritizing these activities.

Wang, Xu↗
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 NTRSDate not supplied

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

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

K. McGuire↗
NASA NTRSDate not supplied

Analysis of Input from Wildfire Incident Experts to Identify Key Risks and Hazards in Wildfire Emergency Response

The United States Department of Agriculture (USDA) describes wildland fires as, “a force of nature that can be nearly as impossible to prevent, and as difficult to control, as hurricanes, tornadoes and floods.” Existing challenges in managing wildland fires often put first responders’ lives at risk. The emergence of drones and their capabilities to supplement human efforts could alleviate some, if not all, of those risks that first responders face during wildfire management efforts. However, the process of adding drones to wildfire response has come with its own challenges as well. NASA’s System-Wide Safety Project is working towards overcoming these challenges to enable routine transfer of risk from responders to aviation assets. The concept of operations and model-based systems engineering (MBSE) effort for this shift is underway. To inform and to validate the MBSE effort, we delivered a questionnaire to wildland firefighting experts on the hazards they currently face. This questionnaire has given us insight and a better understanding of the challenges related to the use of drones from a first responder’s point of view. We are using this information to better address responders’ concerns, develop a safety management system, and eliminate the roadblocks that prevent the use of drones in wildfire management.

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

Requirement Discovery Using Embedded Knowledge Graph with ChatGPT

- 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 artificial intelligence capabilities. This presentation gives an overview of the Knowledge Graph and ChatGPT applications 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.

systems engineering↗
NASA NTRSDate not supplied

ExMC Digital Engineering

Future missions beyond Artemis II will become increasingly complex as multiple vehicles (e.g., Gateway, Human Landing System (HLS), and Extravehicular Activity and Human Surface Mobility Program (EHP)), each having their own Program requirements and other associated documentation, which will need to be integrated into a single mission. Currently, the Human Health and Performance Directorate (HHPD)Program Support Teams mostly use documents to manage, perform, and archive their analyses. Identifying an opportunity for efficiency, ExMC demonstrated the ability to utilize MagicDraw, a Model-Based Systems Engineering (MBSE) tool, as a requirements database with traceability, dependencies, and relationships in one place. Rather than existing in documents, emails, and historical knowledge, ExMC pursued a Digital Engineering (DE) effort in coordination with HHPD by combining MBSE tools with other digital platforms to manage and develop user-defined databases and interfaces. This DE approach is aimed to simplify processes and reduce risk through the unification of requirements into a centralized digital network, improving collaboration, decision-making, and transparency compared to isolated documents and knowledge. However, manipulating data views and content in MagicDraw requires a steep learning curve not needed by all users and even the user-friendly web view comes with downsides due to the static views. To provide a more dynamic user interface, ExMC investigated the use of Microsoft Power Platform which does not require as steep of a learning curve to become proficient. This introduces analytics to the DE infrastructure, offering customizable and dynamic data dashboards. ExMC continues developing these dashboards and tailoring the DE infrastructure in alignment with HHPD workforce needs.

M Krihak↗
NASA NTRS2019

MBSE for the Gateway Program

The Gateway Program and many of its module developers are using Magic Draw to coordinate functions, requirements, and interfaces between the various elements that make up the Gateway Platform. This also extends to the visiting vehicles (Human Lander System, Logistics Module, and Orion). The Propulsion and Power Element (PPE) is using Magic Draw to coordinate the design activities at NASA GRC (Glenn Research Center) and the contractor. This discussion will provide an overview of the MBSE (Model-Based Systems Engineering) efforts and how we are interfacing the various MBSE models into a single integrated model.

Systems Engineering↗