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.

SourceResearch connectionFrom yearThrough year

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

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

ExMC Systems Engineering Developments

The Exploration Medical Capability (ExMC) Element within the Human Research Program (HRP) applies systems engineering (SE) principles along with the use of Model-Based Systems Engineering (MBSE) tools to identify and communicate the requirements for medical and crew health and performance (CHP) systems. In the past fiscal year, the MBSE approach sought to advance the digital engineering toolset for medical and CHP system representation. These digital artifacts provide enhanced views of the relationships among requirements, standards, functions, and capabilities, to name a few, that is best suited for a user’s objectives. The MBSE tools and SE practices were applied to the development of the revised Earth Independent Medical Operations (EIMO) medical system and the Artemis III and IV CHP System models. In addition, a System of Systems concept was integrated into the EIMO model to facilitate the identification of system interfaces that interact with the medical system. Finally, the ExMC SE team has initiated several efforts to bring operationally relevant digital engineering practices to the Human Health and Performance Directorate (HHPD). This included the development of a pilot program within the directorate to help foster utilization of tools such as MagicDraw for system modeling and Power BI for visualizing extracted data in an easily accessible dashboard format. Additionally, with the increase in complexity of the integration effort for Artemis missions, ExMC has endeavored to bring digital engineering strategies to potentially increase efficiency in review processes. This talk will provide a high-level overview of the ExMC SE team accomplishments since the last Investigators’ Workshop, an introduction to upcoming SE talks, and the ongoing systems engineering work.

systems engineering↗

NASA NTRS2019

Enabling Assurance in the MBSE Environment

Evans, John W.↗

NASA NTRS2020

Enabling Assurance in the MBSE Environment

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

Evans, John W.↗

NASA NTRSDate not supplied

Orion SysML Model, Digital Twin, and Lessons Learned for Artemis I

In 2015 it was recognized by NASA’s Orion Chief Engineer that NASA’s design insight into the Orion subsystems for Artemis I were not sufficient to provide traditional engineering support to flight operations. To address these concerns and provide an opportunity to apply emerging model-based systems engineering and digital twin methodologies and provide opportunities for employees across NASA to get hands-on training, an Orion digital twin pilot project was initiated in 2020. With the increase in complexities of spacecraft, and decreased time to made decisions during missions in critical or emergency situations, digital modeling and integration of design can reduce the time to answer questions by days and required human resources by an order of magnitude over historical approaches and was identified to be critical capability for NASA’s future. This paper describes the genesis of this digital twin pilot project, efforts undertaken, a reproducible methodology to take available system information from a mature program to create an executable SysML model that supports a link to unit-specific data, thus forming a connection to the physical asset, and associated lessons learned and project deliverables.

MBSE↗

NASA NTRSDate not supplied

Artemis III and IV Crew Health and Performance System Model Development

To maintain Crew Health and Performance (CHP) during an Artemis mission, the NASA Human Research Program (HRP) and Exploration Medical Capabilities (ExMC) element recognize the challenge that many different vehicles, habitats, and operational groups must come together to develop and implement cross program capabilities. To address this challenge, the ExMC team created the prototype 2023 Artemis CHP System Model to analyze how human system requirements are implemented throughout an Artemis mission and help understand the effects of changing an individual vehicle or habitat requirement on a full mission. Since presenting this work at the 2024 HRP Investigators’ Workshop, ExMC has continued this effort, now called the Artemis III and IV CHP System Model, to better support its operational end users within the NASA Human Health and Performance Directorate (HHPD) workforce. In this presentation, we will recapitulate how visualizing requirements and their relationships using a Model-Based Systems Engineering approach (MBSE) serves to improve understanding of an Artemis mission’s CHP capabilities along with discussion on updates made to the model to increase accessibility for users within HHPD so that it may be used in the development of cross program CHP capabilities at NASA.

Crew Health and Performance↗

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 NTRS2006

State Analysis Database Tool

The State Analysis Database Tool software establishes a productive environment for collaboration among software and system engineers engaged in the development of complex interacting systems. The tool embodies State Analysis, a model-based system engineering methodology founded on a state-based control architecture (see figure). A state represents a momentary condition of an evolving system, and a model may describe how a state evolves and is affected by other states. The State Analysis methodology is a process for capturing system and software requirements in the form of explicit models and states, and defining goal-based operational plans consistent with the models. Requirements, models, and operational concerns have traditionally been documented in a variety of system engineering artifacts that address different aspects of a mission s lifecycle. In State Analysis, requirements, models, and operations information are State Analysis artifacts that are consistent and stored in a State Analysis Database. The tool includes a back-end database, a multi-platform front-end client, and Web-based administrative functions. The tool is structured to prompt an engineer to follow the State Analysis methodology, to encourage state discovery and model description, and to make software requirements and operations plans consistent with model descriptions.

Rasmussen, Robert↗

NASA NTRS1984

Engineering model system study for a regenerative fuel cell: Study report

Key design issues of the regenerative fuel cell system concept were studied and a design definition of an alkaline electrolyte based engineering model system or low Earth orbit missions was completed. Definition of key design issues for a regenerative fuel cell system include gaseous reactant storage, shared heat exchangers and high pressure pumps. A power flow diagram for the 75 kW initial space station and the impact of different regenerative fuel cell modular sizes on the total 5 year to orbit weight and volume are determined. System characteristics, an isometric drawing, component sizes and mass and energy balances are determined for the 10 kW engineering model system. An open loop regenerative fuel cell concept is considered for integration of the energy storage system with the life support system of the space station. Technical problems and their solutions, pacing technologies and required developments and demonstrations for the regenerative fuel cell system are defined.

Chang, B. J.↗

NASA NTRS2016

MBSE-Driven Visualization of Requirements Allocation and Traceability

In a Model Based Systems Engineering (MBSE) infusion effort, there is a usually a concerted effort to define the information architecture, ontologies, and patterns that drive the construction and architecture of MBSE models, but less attention is given to the logical follow-on of that effort: how to practically leverage the resulting semantic richness of a well-formed populated model to enable systems engineers to work more effectively, as MBSE promises. While ontologies and patterns are absolutely necessary, an MBSE effort must also design and provide practical demonstration of value (through human-understandable representations of model data that address stakeholder concerns) or it will not succeed. This paper will discuss opportunities that exist for visualization in making the richness of a well-formed model accessible to stakeholders, specifically stakeholders who rely on the model for their day-to-day work. This paper will discuss the value added by MBSE-driven visualizations in the context of a small case study of interactive visualizations created and used on NASA's proposed Europa Mission. The case study visualizations were created for the purpose of understanding and exploring targeted aspects of requirements flow, allocation, and comparing the structure of that flow-down to a conceptual project decomposition. The work presented in this paper is an example of a product that leverages the richness and formalisms of our knowledge representation while also responding to the quality attributes SEs care about.

Model Based Systems Engineering↗

NASA NTRS2016

MBSE-Driven Visualization of Requirements Allocation and Traceability

In a Model Based Systems Engineering (MBSE) infusion effort, there is a usually a concerted effort to define the information architecture, ontologies, and patterns that drive the construction and architecture of MBSE models, but less attention is given to the logical follow-on of that effort: how to practically leverage the resulting semantic richness of a well formed populated model to enable systems engineers to work more effectively, as MBSE promises. While ontologies and patterns are absolutely necessary, an MBSE effort must also design and provide practical demonstration of value (through human-understandable representations of model data that address stakeholder concerns) or it will not succeed. This paper will discuss opportunities that exist for visualization in making the richness of a well-formed model accessible to stakeholders, specifically stakeholders who rely on the model for their day-to-day work. This paper will discuss the value added by MBSE-driven visualizations in the context of a small case study of interactive visualizations created and used on NASA’s proposed Europa Mission. The case study visualizations were created for the purpose of understanding and exploring targeted aspects of requirements flow, allocation, and comparing the structure of that flow-down to a conceptual project decomposition. The work presented in this paper is an example of a product that leverages the richness and formalisms of our knowledge representation while also responding to the quality attributes SEs care about.

Model Based Systems Engineering↗

NASA NTRS2016

The Value of Successful MBSE Adoption

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

MBSE↗

NASA NTRS2011

Dynamic Gate Product and Artifact Generation from System Models

Model Based Systems Engineering (MBSE) is gaining acceptance as a way to formalize systems engineering practice through the use of models. The traditional method of producing and managing a plethora of disjointed documents and presentations ("Power-Point Engineering") has proven both costly and limiting as a means to manage the complex and sophisticated specifications of modern space systems. We have developed a tool and method to produce sophisticated artifacts as views and by-products of integrated models, allowing us to minimize the practice of "Power-Point Engineering" from model-based projects and demonstrate the ability of MBSE to work within and supersede traditional engineering practices. This paper describes how we have created and successfully used model-based document generation techniques to extract paper artifacts from complex SysML and UML models in support of successful project reviews. Use of formal SysML and UML models for architecture and system design enables production of review documents, textual artifacts, and analyses that are consistent with one-another and require virtually no labor-intensive maintenance across small-scale design changes and multiple authors. This effort thus enables approaches that focus more on rigorous engineering work and less on "PowerPoint engineering" and production of paper-based documents or their "office-productivity" file equivalents.

XML↗

NASA NTRSDate not supplied

NASA’s MBSE Approach for Advanced Air Mobility

NASA’s Aeronautics Research Mission Directorate (ARMD) has a significant research effort for advanced air mobility (AAM). AAM involves bringing aviation closer to where people live and work and offers the possibility of making aviation a normal part of everyday life. The scope of AAM is broad, including transformations in aircraft, airspace operations, and in how these new aviation capabilities will integrate into local communities. Due to the nature of AAM cutting across multiple aspects of the aircraft, airspace, and community domains, NASA is applying tools and techniques aligned with a model-based systems engineering approach. These are intended to capture and organize applicable system architectures and potential requirements in order to deliver a validated system architecture and recommended set of requirements that enable sustainable and scalable medium density AAM operations.

Advanced Air Mobility↗

NASA NTRS2016

Multidisciplinary Model Transformation Through Simplified Intermediate Representations

There has long been a challenge of making engineering tools from multiple disciplines interoperate. This problem extends to system modeling practices. This challenge has been confronted with a wide variety of techniques. These techniques include attempting to interface tools together into combined suites, attempting to find underlying commonalities in mathematics, supporting connections through semantic encoding, various graph mappings and transformations, and code wrappers. All of these approaches have strengths and weaknesses. These are measured in multiple areas: relative freedom of action of individual domain engineers in developing their own tools, speed of execution, ease of creation, traceability, fidelity of information transfer, and degree of alignment between the concepts of different domains. This paper presents an approach to this interoperation problem currently being used in the World-Wide Web. The approach is to develop easy-to-parse formats that allow flexibility to both the file author and file interpreter. Many of the formats that are currently deployed sacrifice runtime performance for the ability of third parties to easily understand what to do with the data. XML became popular earlier as a de-facto standard format for many web applications, but is now being replaced by JSON to enhance human readability and provide a simpler data model. This is the basis for work in this paper. Our approach, which provides the key to interoperation, is a simplified “shrapnel” intermediate collection of objects and relationships that is the result of a breakdown of the system model into minimal pieces. It is then reassembled on the destination side, forming a two-step transformation. Previous efforts with single-step transformations have proven too difficult to create efficiently. In contrast, the use of this approach leads to an almost automatic procedure for transformation development. The Europa project is a large engineering project that must coordinate the efforts of many different teams with different specialties. The traditional form of exchanging engineering information has been documentation. The vision of model-based systems engineering is to make this information exchange much more digital. This paper presents the application of our simplified format to connecting two different engineering tools to the system model, with a focus on a dynamic mission simulation encoded in Modelica.

Cole, Bjorn↗

NASA NTRS2023

Identifying and Documenting Expert Knowledge, A Practical Study of Design Patterns

Globalization, powered by digitization, is increasing technology growth and knowledge transfer rates to levels not seen in the previous 3500 years, obscuring absolute truth and accelerating rates of innovation and production. Competing,or remaining competitive, in this global marketplace requires a learning organization adopt a method of capture, retention, and reuse for demonstrated tacit knowledge to accelerate the development of increasingly complex systems of high quality at a reasonable cost. The architectural theory of Patterns and Pattern Language is a validated methodology for mining tacit domain knowledge from a proven system. This work applies architectural theory to a multi-year development experiment and captures exposed knowledgeas a design patternin a model based systems engineering tool, demonstrating applicability ofdigital engineering initiativesin thedescription and reuse of expert design knowledge.By creating and archiving model based expressions of expert knowledge,a learning organization canimprovepractical decision making and avoid uninformed concept phase decision making

systems engineering↗

NASA NTRS2015

A Tool for Model-Based Generation of Scenario-driven Electric Power Load Profiles

Power consumption during all phases of spacecraft flight is of great interest to the aerospace community. As a result, significant analysis effort is exerted to understand the rates of electrical energy generation and consumption under many operational scenarios of the system. Previously, no standard tool existed for creating and maintaining a power equipment list (PEL) of spacecraft components that consume power, and no standard tool existed for generating power load profiles based on this PEL information during mission design phases. This paper presents the Scenario Power Load Analysis Tool (SPLAT) as a model-based systems engineering tool aiming to solve those problems. SPLAT is a plugin for MagicDraw (No Magic, Inc.) that aids in creating and maintaining a PEL, and also generates a power and temporal variable constraint set, in Maple language syntax, based on specified operational scenarios. The constraint set can be solved in Maple to show electric load profiles (i.e. power consumption from loads over time). SPLAT creates these load profiles from three modeled inputs: 1) a list of system components and their respective power modes, 2) a decomposition hierarchy of the system into these components, and 3) the specification of at least one scenario, which consists of temporal constraints on component power modes. In order to demonstrate how this information is represented in a system model, a notional example of a spacecraft planetary flyby is introduced. This example is also used to explain the overall functionality of SPLAT, and how this is used to generate electric power load profiles. Lastly, a cursory review of the usage of SPLAT on the Cold Atom Laboratory project is presented to show how the tool was used in an actual space hardware design application.

power load profile↗

NASA NTRS2013

Virtual Construction of Space Habitats: Connecting Building Information Models (BIM) and SysML

Current trends in design, construction and management of complex projects make use of Building Information Models (BIM) connecting different types of data to geometrical models. This information model allow different types of analysis beyond pure graphical representations. Space habitats, regardless their size, are also complex systems that require the synchronization of many types of information and disciplines beyond mass, volume, power or other basic volumetric parameters. For this, the state-of-the-art model based systems engineering languages and processes - for instance SysML - represent a solid way to tackle this problem from a programmatic point of view. Nevertheless integrating this with a powerful geometrical architectural design tool with BIM capabilities could represent a change in the workflow and paradigm of space habitats design applicable to other aerospace complex systems. This paper shows some general findings and overall conclusions based on the ongoing research to create a design protocol and method that practically connects a systems engineering approach with a BIM architectural and engineering design as a complete Model Based Engineering approach. Therefore, one hypothetical example is created and followed during the design process. In order to make it possible this research also tackles the application of IFC categories and parameters in the aerospace field starting with the application upon the space habitats design as way to understand the information flow between disciplines and tools. By building virtual space habitats we can potentially improve in the near future the way more complex designs are developed from very little detail from concept to manufacturing.

space architecture↗

NASA NTRS2010

Systems Engineering and Application of System Performance Modeling in SIM Lite Mission

The SIM Lite Astrometric Observatory will be the first space-based Michelson interferometer operating in the visible wavelength, with the ability to perform ultra-high precision astrometric measurements on distant celestial objects. SIM Lite data will address in a fundamental way questions such as characterization of Earth-mass planets around nearby stars. To accomplish these goals it is necessary to rely on a model-based systems engineering approach - much more so than most other space missions. This paper will describe in further detail the components of this end-to-end performance model, called "SIM-sim", and show how it has helped the systems engineering process.

Exoplanet↗