The automotive industry faces two critical challenges in product development: (1) Consistency and traceability across all involved domains / disciplines and throughout the whole development process to manage the complex interrelationships among architecture, components, features, and functions. (2) The pressure to increase development speed and efficiency to stay competitive. There are solutions addressing both challenges: Model-based systems engineering (MBSE) addresses consistency and traceability, while virtualization and simulation address development speed and efficiency. In state-of-the-art industrial practice, however, these two solutions are still applied in isolation from one another, leading to inconsistencies, missing traceability and high effort and resource investment (due to redundant or manual modeling work, finding and correcting inconsistencies etc.). To address these industry challenges, the prostep ivip SmartSE project—an established multi-year cross-industry initiative—has been working on integrating MBSE with simulation to enhance traceability, consistency and efficiency in product development processes. We will present our industry experiences and the obtained results from the SmartSE project, where our companies collaborate on solving the real-world challenges that drive the urgent need for a standards-based integration of MBSE and simulation. Related standardization efforts include the "Simulation Credibility Standard and Recommendation" [1] from SmartSE, the SysML specification for creating MBSE system architecture models [2], and the SSP Traceability Standard [3]. The unique value of this presentation lies in bringing together industry perspectives from OEMs, suppliers and tool vendors to share their experiences, challenges and targets with the integration of MBSE and simulation. Rather than only presenting theoretical solutions, we will also show working proof-of-concepts created within the SmartSE project. The proposed solutions are based on standards (SysML, XMI, SSP, SSP-Traceability, FMI) and thus applicable across industries, irrespective of the specific tool set used in an organization. Our presentation will reveal how the integration of MBSE and simulation enables consistency and traceability between quantitative (i.e., system architecture model) and qualitative (i.e., simulation models) models, whilst increasing development speed and efficiency due to auto-generation of artifacts. We provide industry insights into why the integration of MBSE and simulation is an essential means for traceability, consistency and development speed, and how it can be put into practice.

References [1] White Paper: SmartSE - Guard Rails for "Simulation Credibility Standards and Recommendation", prostep ivip Association. (2024) [2] OMG Systems Modeling Language (OMG SysML), Object Management Group (2019) SYSML SPEC. Available at https://www.omg.org/spec/SysML/1.6/About-SysML/ [3] Prototype Standard: SSP Traceability Standard (An SSP layered Standard). (2024, in development). Available at: https://github.com/modelica/ssp-ls-traceability

Virtualization in development of ever more complex products is becoming increasingly important. Therefore, the use of modeling & simulation activities as part of product development and release is also increasing. Traceability is for these activities a keystone for quality tracking and reuse for efficiency. This presentation shows how this can be realized by applying the SSP Traceability layered standard (i.e., which information is involved related to the modeling and simulation activity, where does it come from and where shall it be propagated) in conjunction with the MIC Core standard for metadata. At the beginning, the Credible Simulation Process Framework developed as part of the prostep SmartSE project is presented, which enables integration into company processes. We will show this using the example of the challenges of developing a simulation model Due to different reasons, the development of a simulation model typically consists of the design and the implementation in a simulation tool (e.g. Dymola), the model being then immediately used for simulation purposes, skipping essential activities like the requirement specification (e.g. relevant application area, relevant physical effects, …), the documentation for the end-user and/or the model verification respectively the model validation. Often, the user documentation is written afterwards from the model implementation, leading, e.g. to potential transcription issues, inconsistent content respectively versions between implementation and documentation, and high review efforts to ensure the high quality of the developed model. We will then present the solution approach based on the SSP 2.0 and SSP Traceability Layered Standard and show it as a demonstration. Another important point for traceability and reuse is the use of standardized metadata to find and evaluate information. We will present a solution based on the MIC-Core Metadata Standard. We will close with an overview, which of these solution elements are implemented and publicly available.