00:00

From System to Simulation Architecture: MBSE and EDS Convergence Study

This document outlines a study on the convergence of Model-Based Systems Engineering (MBSE) and Electronic Data Sheets (EDS) in the context of developing simulation architectures for spacecraft systems. The study aims to automate information exchange between spacecraft subsystems, simulation models, and simulators. It identifies simulation model and simulator needs, equipment unit and system information mapping, and proof-of-concept integration between MBSE and simulation. The approach involves analyzing data overlap between simulation models and simulators, integrating information identified in the objectives, and mapping MBSE to simulation architectures. The document provides details on simulation needs, equipment unit and system information, and the ORM mapping between Capella and SAVOIR-EDS systems.

Download Presentation

From System to Simulation Architecture: MBSE and EDS Convergence Study

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. From System to Simulation Architecture Towards MBSE EDS and Simulation Convergence Hien Thong Pham, Juan Perez Rodriguez, Boris Wyszkowski , Délia Cellarier SESP@ESTEC - 22/04/2024 1 22-04-24 COMMERCIAL IN CONFIDENCE

  2. From System to Simulation Architecture (FS2SA) • Study initiated by RATIOSIM WG2 Understanding FS2SA Objectives And Approach Identification of Simulation Model and Simulator Needs Identification of Equipment Unit and System Information Mapping MBSE and Simulation Proof-of-Concept Conclusions Next Steps • • Kicked-off October 2021 Finalizing the PoC and preparing the Final Review… 2 2 22-04-24 COMMERCIAL IN CONFIDENCE

  3. UNDERSTANDING THE FS2SA OBJECTIVES OBJ1 To improve the automation of the information exchange between the spacecraft subsystems and units and the simulation model development, configuration and validation OBJ2 To improve the automation of the information exchange between the spacecraft system and the simulator assembly, scheduling and its mission specific configuration. MBSE EDS OBJ3 To define how the information identified in the above objectives can be integrated in the simulation architectures typically used in the European space domain. SSRA REFA ISIS Simulation Model = Spacecraft Equipment Unit Model <-> EDS Simulator = Spacecraft Simulator <-> MBSE 3 3 22-04-24 COMMERCIAL IN CONFIDENCE

  4. UNDERSTANDING THE FS2SA APPROACH Simulation Model Simulator Data Overlap (System Interfaces) Analysis PoC 4 4 COMMERCIAL IN CONFIDENCE

  5. SIMULATION NEEDS Sources: Virtual System Model from ECSS-E-TM-10-21 for various kinds of simulator Simulation experience of the study consortium (SPB, TPZG, TAS, ADS) Spacecraft architecture and design documentation ECSS-E-TM- 10-21 Simulator Needs Equipment unit documentation Number of equipment unit instances Simulation Model Needs Equipment unit properties Consortium simulation development experience Equipment unit interfaces (electrical, data), states, modes and behavior 5 5 22-04-24 COMMERCIAL IN CONFIDENCE

  6. EQUIPMENT UNIT AND SYSTEM INFORMATION What system and equipment unit information is modelled in CAPELLA? System Information CAPELLA Equipment Unit Information SAVOIR-EDS What equipment unit information is modelled in SAVOIR-EDS? 6 6 22-04-24 COMMERCIAL IN CONFIDENCE

  7. MAPPING MBSE - SIMULATION ORM Inside Mapping? 7 7 COMMERCIAL IN CONFIDENCE

  8. Introduction to Object Role Modelling (ORM) Conceptual Model defines concepts part of the universe of discourse  Logical Model: tables definitions for a relational database  Physical Model: tables are populated with data instantiating the concepts Entity Types Value Types Fact Types: relationships between Entity Types/Value Types Source: Wikipedia 8 8 COMMERCIAL IN CONFIDENCE

  9. Capella SAVOIR-EDS SSO MBSE SSRA Data Types EngineeringData X ValueType BehaviouralView/ Equipment Physical Component EquipmentModel PhysicalComponent MAPPING RESULTS ElectricalView/ Interface End Bus Signal Type EngineeringData/ NetworkPacket and Component AnalogEngineeringParameter DigitalEngineeringParameter ComponentPort ComponentPort Physical Port SystemIFLayerModel PhysicalPort BehaviouralView/ StateMachine Modes and Transitions StateMachine OperationalModel StateMachine Behavioural View/Functional Behaviour Functional View/External or Internal Signals Functional View/Functional Data Power View/ PowerConsumptionInEquipmentMode Power View/ PowerDissipationInEquipmentMode LocalFunction Function CoreFunctionalModel PhysicalFunction Actor or LogicalActor N/A Actor PhysicalModel X N/A X Central Solver PropertyValue PropertyValueGroup SimVarDefinition (type VT_PARAMETER) EngineeringData X 9 9 COMMERCIAL IN CONFIDENCE

  10. Capella SAVOIR-EDS SSO MBSE SSRA ComponentPort ComponentPort SimVarDefinition (types VT_INPUT, VT_OUTPUT) See EquipmentModel mapping ComponentExchange ComponentExchange ExchangeItem ComponentPort Interface ExchangeItem ComponentPort Standard Simulation Port See EquipmentModel mapping ComponentExchange TmTcStreamPort MAPPING RESULTS ExchangeItem ComponentPort PhysicalPort SystemIfPort See EquipmentModel mapping ComponentPort ComponentExchange Extensions ViewPoints FunctionalPort or ComponentPort ExchangeItem ComponentPort PhysicalIfPort See EquipmentModel mapping ComponentExchange DynamicsIfPort PowerIfPort ExchangeItem ThermalIfPort MagneticIfPort ExternalIfPort ComponentPort FunctionalPort or ComponentPort See EquipmentModel mapping ComponentExchange ExchangeItem X X Containment fact types X X Containment relationship N/A See SystemIFLayerModel mapping See EquipmentModel mapping ODE Port Calibration/Conversion Container X Error Model See Behavioural View See Functional View X X Schedulable Function LocalFunc FailureCase SimulationModelUsage or SimulationModelOccurrence REC and RPL feature to instantiate Components N/A X PhysicalLink LogicalSystem N/A N/A PhysicalLink X System I/F Network BenchDefinition PhysicalSystem BenchUsage BenchOccurrence System I/F Network PhysicalLink N/A PhysicalLink 10 10 COMMERCIAL IN CONFIDENCE

  11. NON COVERED MAPPING CONCLUSIONS • • • • • Physical models Data types Physical link detailed semantics Scheduling and dynamics Instantiation of equipment units and benches From the Simulation point of view, the SSO MBSE is Missing the Data Type concept Missing the Property (configuration parameter of a Simulation Model) concept Detailed semantics of the Connections between Equipment. (e.g. detailed definition for MilBus 1553, Spacewire… protocols not possible) Missing the Instantiation concept for Equipment Unit (Simulation Model) as well as for the complete Spacecraft (Bench or Simulator) From the Simulation point of view, mapping with SSO EDS and CAPELLA is ok None of the MBSE models supports Model scheduling aspects Spacecraft environment & dynamics simulation 11 11 COMMERCIAL IN CONFIDENCE

  12. UNIFIED SIMULATION-EDS-MBSE To define formally the MBSE- Simulation mapping, it is necessary to express all involved models in the same formalism: Create and integrate the SAVOIR-EDS and SSRA Universes of Discourse in the Space System Ontology I.e. expressing the resp. metamodel in the ORM formalism Then, the mapping can be performed within the SSO SSRA Conceptual Model (UML) Space System Ontology (ORM) Model Translation Simulation MBSE EDS SAVOIR-EDS Metamodel (UML) Unsurprisingly, same mapping results 12 12 COMMERCIAL IN CONFIDENCE

  13. PROOF-OF-CONCEPT One small PoC involving the SSO MBSE, SSO Simulation and SSO EDS to illustrate the mapping MBSE-Simulation NON COVERED? Non covered data are provided by population of the Simulation tables side only Software architecture using Python and PostgreSQL DB 13 13 COMMERCIAL IN CONFIDENCE

  14. CONCLUSIONS Information exchange between Simulation and CAPELLA possible: no major issues or gaps identified Information exchange between Simulation and the SSO MBE incomplete: gaps identified Data types Instantiation Properties Physical link semantics Further analysis or extensions of the SSO MBSE to cover specific discipline aspects (such as Data Handling, Power, Thermal, AOCS…) are necessary to complete the modelling SSO MBSE is a conceptual model defining generic concepts independent of MBSE infrastructures/tools Careful with the terminology/vocabulary used when exchanging information between MBSE and Simulation 14 14 COMMERCIAL IN CONFIDENCE

  15. NEXT STEPS Issues to address in a follow-up study Unclear EDS information source in the exchange with Simulation Model Simulation Model  (CCSDS EDS + SAVOIR-EDS)? Simulation Model  (MBSE model with support for EDS)? Parallel presence of SSO MBSE and SSO EDS models: strong overlap and duplicated information Long-term goal should be a seamless and close integration of Simulation in MBSE through a Data Hub Feedback from this FS2SA study as a first step to develop the MBSE Data Hub 15 15 COMMERCIAL IN CONFIDENCE

  16. THANK YOU FOR YOUR ATTENTION 16 16 22-04-24 COMMERCIAL IN CONFIDENCE

More Related