Reference Model for the Cooperative Exchange of Simulation Data

(1)

vif – The Virtual Vehicle

04.07.06

1 Reference Model for the Cooperative

Exchange of Simulation Data

Production

Partner

(2)

vif – The Virtual Vehicle

04.07.06

2 Content



Challenges



Situation



Project Aim



Scope of the Reference Model



Solution: VPT Reference Model (VPT = Virtual Prototype)



Reference Process



Data Synchronization Points



Reference Data Model



Interaction Scenarios



Expected Benefits

(3)

vif – The Virtual Vehicle

04.07.06

3 Challenges



Internal:



Coordination of the various simulation disciplines



Heterogeneous system environment



Consistent data management in functional, geometric and

manufacturing oriented integration



Insufficient access to existing knowledge/information



External:



Many different development partners (OEM - general contractor -

supplier)

(4)

vif – The Virtual Vehicle

04.07.06

4 Internal and External Data Exchange

BoM

ERP

CAD

OEM 1

BoM

ERP

CAD

OEM 2

BoM

ERP

CAD

Supplier 1

EDM

BoM

ERP

CAD

Supplier 2

emServer

DMU

VPT

VPM

RPT

Source: MAGNA STEYR

(5)

vif – The Virtual Vehicle

04.07.06

5 Target: One „Platform“ for Internal and External Exchange

BoM

ERP

CAD

OEM 1

BoM

ERP

CAD

OEM 2

_emServer

VPM

DMU

EDM

VPT

BoM

ERP

CAD

Supplier 1

BoM

ERP

CAD

Supplier 2

RPT

(6)

vif – The Virtual Vehicle

04.07.06

6 Reference Model

Geometric

Integration

_Integration

Functional

Manufacturing Oriented

_Integration

Scope (1)

DMU

Virtual Factory

VPT

Project Scope

(7)

vif – The Virtual Vehicle

04.07.06

7 

Project scope is



Functional Simulation



… with interfaces to



Production planning / production



Design (PDM)



Testing



Digital Mockup



Change & release management



Consideration of



Concept and serial development phase



Internal and external data exchange



Focused on exchange with customer/OEM



Simulation methods: MBS, CFD, FEA



OEMs: DC, VW, Audi, BMW, Porsche?



Verification with Use Cases



UC1: spotweld optimization (interdisciplinary)



UC2: virtual front axle simulation (brake disc, NVH, Crash,…)



UC3: pedestrian safety



UC4: …..

(8)

vif – The Virtual Vehicle

04.07.06

8 Situation in Cooperative Simulation



Synchronisation problems between project partners



Different partners along the simulation process



Structured data exchange necessary



Coordination of partner specific processes necessary



Different methods, systems and data per project and partner



Complex data conversion / quality losses



Difficult tracking of simulation maturity



No versioning of simulations



No direct reference of simulation results to the geometry



Long lead time for system integration

(9)

vif – The Virtual Vehicle

04.07.06

9 Solution: VPT Reference Model



Each partner works with his own VPT processes and methods and with

his own IT-systems.



the VPT reference process defines the „common language“ between the VPT

process of the OEM and the supplier



the VPT reference data model is neccessary for the communication of the

data in a neutral format

Partner A

(internal/external)

VPT Process

VPT Methods

VPT Systems

VPT Data

Partner B

(internal/external)

VPT Process

VPT Methods

VPT Systems

VPT Data

VPT Reference Model

VPT Reference

Process

VPT Reference

Data Model

Process mapping

Data mapping

(10)

vif – The Virtual Vehicle

04.07.06

10 Spezifischer VPT-Prozess Partner 1

Spezifischer VPT-Prozess Partner 2

Process Oriented Solution

Specific VPT Process Partner 1

Specific VPT Process Partner 2

Coordinator

Participant

VPT Reference

Process

Mapping

Consolidation

Phase

Postprocessing

and Analysis

Solving

Phase

Data Preparation

Phase

Data Collection

Phase

Preparation

Phase

Harmonized synchronisation with the VPT reference process and

the data synchronization points

Source: PDTec,

adapted

(11)

vif – The Virtual Vehicle

04.07.06

11 Example for an interaction scenario

VPT Coordinator

VPT Participant

Scenario: External assembly of a module for crash simulation

Auftrag zur

Modulerstellung

• Simulationsauftrag

• Firmenstandards

• relevante Teile

• Vorhandene

Geometrie und

FE-Netze

• Verbindungsdaten

• Werkstoffkennwerte

• …

Preparation

Data Collection

Data Preparation

Solving

Postprocessing and

_analysis

Consolidation

Fertig

parametrisiertes

Modul

• Verwendete

Geometrien

• Erstellte Netze

• Fertiggestelles Modul

inkl. aller Parameter

• Eingearbeitete

Verbindungsdaten

• …

(12)

vif – The Virtual Vehicle

04.07.06

12 Data Model Overview

Simulation

Order

Simulation

Task

Simulation class

Simulation method

Input Data

Output Data

task

number

status

Simulation

Run

Input data

Output data

order

CAD-Geometry

Simulation

Model

Component

Usage

Assembly

Usage

used parts S[1:?]

Vehicle

component

re

pr

es

en

ta

ted_

th

rou

gh

designated parts S[1:?]

derived

from

Load Case

Solver

Settings

Parameters

Solver

Output

Simulation

Report

(13)

vif – The Virtual Vehicle

04.07.06

13 Benefits (1)

OEM-dept. A

OEM-dept. B

Tier 2

Tier 3

Tier 1

OEM-dept. C

Receive Request Creation ECR Technic al Analysis and Detailing ECR Comments of ECR ECR Ac ceptance and Approval Receive Request

Receive Request Creation ECRCreation ECR Technic al Analysis and Detailing ECRTechnic al Analysis and Detailing ECR Comments of ECRComments of ECR ECR Ac ceptance and ApprovalECR Ac ceptance and Approval

Receive Request Creation ECR Technical Analysis and Detailing ECR Comments of ECR ECR Acceptance and Approval Receive Request

Receive Request Creation ECRCreation ECR Technical Analysis and Detailing ECRTechnical Analysis and Detailing ECR Comments of ECRComments of ECR ECR Acceptance and ApprovalECR Acceptance and Approval Receive Request Creation ECR Technical A nalysis and Detailing ECR Comments of ECR ECR A cceptance and A pproval

Receive Request

Receive Request Creation ECRCreation ECR Technical A nalysis and Detailing ECRTechnical A nalysis and Detailing ECR Comments of ECRComments of ECR ECR A cceptance and A pprovalECR A cceptance and A pproval

VPT

Coordinator

VPT

Participant

Partner spezifischer

VPT Prozess

Partner spezific

VPT Process

VPT Reference

Process

Receive Request Creation ECR Technical A nalysis and Detailing ECR Comments of ECR ECR A cceptance and A pproval Receive Request

Receive Request Creation ECRCreation ECR Technical A nalysis and Detailing ECRTechnical A nalysis and Detailing ECR Comments of ECRComments of ECR ECR A cceptance and A pprovalECR A cceptance and A pproval

Rec eiv e Reques t Cr eation ECR Tec hnic al A nalys is and Detailing ECR Comments of ECR ECR A c c eptanc e and A ppr ov al Rec eiv e Reques t

Rec eiv e Reques t Cr eation ECRCr eation ECR Tec hnic al A nalys is and Detailing ECRTec hnic al A nalys is and Detailing ECR Comments of ECRComments of ECR ECR A c c eptanc e and A ppr ov alECR A c c eptanc e and A ppr ov al Rec eiv e Reques tRec eiv e Reques tRec eiv e Reques t Cr eation ECRCr eation ECRCr eation ECR Tec hnic al A nalys is and Detailing ECRTec hnic al A nalys is and Detailing ECRTec hnic al A nalys is and Detailing ECR Comments of ECRComments of ECRComments of ECR ECR A c c eptanc e and A ppro va lECR A c c eptanc e and A ppro va lECR A c c eptanc e and A ppro va l

Receive Request Creation ECR Technical A nalysis and Detailing ECR Comments of ECR ECR A cceptance and Approval Receive Request

Receive Request Creation ECRCreation ECR Technical A nalysis and Detailing ECRTechnical A nalysis and Detailing ECR Comments of ECRComments of ECR ECR A cceptance and ApprovalECR A cceptance and Approval

Coordinator

(other VPT)

_Participant

(other VPT)

in

te

rn

al

ex

te

rn

al



Standardized interaction patterns (process templates) in a VPT network according

to the VPT Reference Model



Cost reduction with reduction of the variants of processes and communication between

OEM and supplier



Transparent VPT-status for all involved partners independent from their internal

processes (CAE-supplier-monitoring)



Re-use of process definitions, interfaces and tools

Source: PDTec,

adapted

(14)

vif – The Virtual Vehicle

04.07.06

14 Benefits (2)



Minimization of time and cost for integration of customers or suppliers

in a vehicle development project



Shorter start-up phase for vehicle development projects



Integration support of internal and external partners



Pre-defined and transparent information flow with data

synchronization points



Based on process templates and process interfaces for cross-department

and cross-company collaboration



Quicker integration of other systems (e.g. OEMs, suppliers, service

providers, mergers…)



Improvement of data- process- and result quality



Less information losses at interfaces

(15)

vif – The Virtual Vehicle

04.07.06

15 Outlook

VPT Reference Process

VPT Reference Data Model

Prototypical Data Exchange

VPT-Guideline

Sim

ulati

ons-auftr

ag

Sim

ulati

ons-aufg

abe

simulationsklasse

simulationsverfahren

Inpu

tdat

en

Out

putd

aten

aufgabe

num

mer

statu

s

Sim

ulati

ons-lauf

eingabedaten

ausgabedaten

auftrag

kon

stru

ktive

Geo

metr

ie

Sim

ulati

ons-mod

ell

Baut

eil-verw

end

ung

Bau

grup

pen-verw

end

ung

benutzter_teileumf

ang S[1:?]

Fahr

zeug

-kom

pon

ente

re

pr

äs

en

tie

rt

_d

ur

ch

vorgesehener_teileumfang S[1:?]

abgeleitet

aus

Last

fall

Solv

er-eins

tellu

nge

n

Para

met

er

Para

met

er

Solv

erou

tput

Sim

ulati

ons-repo

rt

VPT Interaction Scenarios

VPT Coordinator VPT Participant

Auftrag zur Modulerstellung

• Simulat ions auftrag • Firmenstan dards • relevante Teile • Vorhandene Geometrie und FE-Netze • Verbindun gsdaten • Werkstoffk ennwerte • …

Vorber eitung Datenbeschaffung Datenaufbereitung Simulation Ergebnisaufbereitung Konsolidierung Fertig parametrisiertes Modul • Verwendete Geometrie n • Erstellte Netze • Fertiggeste lles Modul inkl. aller Parameter • Eingearbeit ete Verbindun gsdaten • …



VPT Reference Model is documented in the VPT Guideline



Aim to establish a ProSTEP iViP project group based on the

(16)

vif – The Virtual Vehicle

04.07.06

16

Thank you for your

Attention!

Contact:

Markus Hofer

Vif – the virtual vehicle – research company

phone: +43 316 873-9060