Confident product decisions require trust in the underlying simulations. This talk presents how SSP Traceability—based on the System Structure and Parameterization (SSP) standard— creates a digital thread of trust—linking simulation models, processes, requirements, and KPIs. We demonstrate how orchideo | easySSP implements this approach by enabling modular, step-by-step traceable simulation workflows, that document and connect all relevant artifacts, providing the basis for trustworthy, simulation-driven product development.

Extended abstract for a User Presentation at the SSP User Meeting. The potential of the SSP standard to describe system structures to drive an end-to-end credible simulation process from the definition of an abstract analysis architecture to the evaluation of the overall system behavior in a co-simulation setup, is evaluated in this application to a heat pump system. From practitioners perspective the benefits and short-comings are compared against current best practices using proprietary solutions.

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.