Skip to content

Latest commit

 

History

History
84 lines (59 loc) · 3.43 KB

BB_Digital_Twin.md

File metadata and controls

84 lines (59 loc) · 3.43 KB

Digital Twin

BB Tags(s)

BB-SC-TC

Functional Clusters

Virtualization

Layer

MWLayer

Known Implementation

Eclipse Ditto

ID (unique name)

Description

The digital twin is considered as a digital representation of a vehicle (or the vehicle's configuration) as prerequisite for validation and test of SW variants prior to their deployment to a live vehicle.
Proposal for standardization are execution model with regard to simulation level (Prostep standardization https://www.prostep.org/), handling of distributed simulation, co-simulation bus and services for controller including services to extract and inject data, extract and inject algorithm dynamically (or static) during simulation, services to guarantee at least software alignment between digital and vehicle.
Defines embed service services to ensure connection with digital twin.

A digital twin models a virtual representation of a physical object, system, or process.

Rationale

Enables rapid prototyping, validation, and test of vehicle configurations. In scope of OTA updates, validating as many SW variants as possible (all?) to ensure the error-prone deployment of SW updates to the live fleet. Cost saving by eliminating HIL tests with a huge amount of variants.

Governance Applicable S-BB(s)

TDB

Compose BB(s)

What is needed to Design and Implement

What is needed to build and run

Non-Functional Requirements

Dependencies to other Clusters

Vehicle API Relevant

Author/Company

Conti

Priority

High

Related Project(s)

Availability of Source Code

Availability of API

Potential obstacles