April 25 – 26, 2023 | Hanau, Germany

The workshop is booked up.

Workshop Model Version Control – Model Traceability

How to ensure process integrity by making sure that the exact same version of a CAE model is used within the whole Virtual Testing process.

July 05, 2022 | 16:00 – 17:30

In VT procedures currently applied for development within automotive regulatory or consumer assessment procedures the vehicle model as well as CAE models of assessment tools (dummy or human body model) will not be shared outside the vehicle manufacturer.

In this kind of VT process the quality and validity of the models will be checked and finally approved by some kind of certification procedure. Somehow it has to be made sure, that the same model is used in the model certification process and eventually in the VT-based assessment procedure.

This could be done in a first approach on a basis of trust and based on OEM internal documentation systems. However, if virtual testing will be more widely used in future it might be necessary that the models get a kind of “certified” label to guaranty that the same model is used within the whole VT process.

Different options will be discussed in the workshop. Eventually, the technical feasibility of possible proposals within the different IT environments and codes of different OEMs have to be considered. It also has to be ensured that it is still possible to work with the models. After certification of the vehicle model and certification of the HBM, it is still necessary to combine all models in a VT procedure to run the assessment or homologation load case simulation.

In this workshop contributions from IIHS, BASt, JSOL, ESI, IDIADA, LMU and automotive industry will introduce this topic from different points of view highlighting the relevance, possible solutions as well as requirements from the side of the users. This will further be discussed with all workshop participants in an open discussion.

Agenda

Opening/Welcome
Dr. Andre Eggers (BASt)

Part 1: Short intro presentations
Moderator: Prof. Steffen Peldschus (LMU)

Introduction/background from research projects (BASt, ESI Group, IDIADA, LMU Munich)
Dr. Andre Eggers (BASt)

Motivation for model traceability (IIHS, University of Virginia)
Dr. Daniel Perez Rapela (IIHS)

OEM perspective
Bart Peeters Weem (BMW)

Ideas for code-independent solutions (BASt, ESI Group, IDIADA, LMU Munich)
Simon Dussinger (ESI Group)

An example implementation of data traceability mechanisms into crash simulations
Dr. Masahiro Okamura (JSOL)

Part 2: Questions to speakers followed by open discussion:

Do we need an IT-based procedure for model version control / model traceability?

  • to guarantee integrity of the VT process
  • to ensure intellectual property rights?

Requirements from different stakeholder perspectives: users (industry), software vendors/developers, regulators, consumer testing organizations

  • What is needed for model version control / model traceability?
  • What are the specifications for implementation of procedures and tools?

Possible concerns from different stakeholder perspectives

  • What are potential resulting conflicts/ challenges?
  • Which limitations do we see?