Applications of GRID Technologies in Automotive Product Development

1
Applications of GRID Technologiesin Automotive
Product Development

• OGF23
• June 3rd 2008, Barcelona
• Automotive Activity - EC Research Project SIMDAT
• Josef Reicheneder AUDI AG

2
Contents

• Introduction
• Conversion of Car Product Structures into
  Simulation Model Structures
• Meshing Brokering Service
• Virtual Organisations with OEMs, Suppliers and
  Engineering Services
• Simulation Data Management Systems on Distributed
  Locations
• Heterogeneous Data Structures of Simulation Data
  Management and Test Data Management
• Summary

3
Motivation
Derivatisation
A3/S3 A3 Sportback A3 Cabrio TT Coupé TT
Roadster TTS Coupé TTS Roadster A4/S4/RS4 A4/S4/RS
4 Avant A5/S5 A6/S6 A6/S6/RS6 Avant A6
Allroad A8/S8 R8 Q7 ...
Numbers of Variants
Audi 80 Audi 100 Audi 100 Avant Audi Cabrio Audi
Coupé
Audi 80 Audi 100 Audi Coupé
1980
1990
2000
2010
Model offensive for customer orientation and
answer on tightened competition
4
Attributes in Car Simulation
5
Simulation Data Management
CAE Process
Audi CAE Data- and Process Management
Preprocessing
Solving
Postprocessing
Meshes
Compute Solver Pamcrash Nastran Abaqus Permas St
arCDPowerflow Kuli Saber MagmaSoft
Models
Plots Cross sections Movies Images Values
Preprocessing Applikationen Ansa, Medina,
Scripts vi-Editor
Postprocessing Programme Animator,
Evaluator Pamview, FeGraph Scripts
Input decks
Output decks
Load Cases
Individual Files
Simulations
Solver
6
Grid Challengesin Automotive Industry
AUDI External Engineering Companies VW Group
External System Developers World System
Suppliers
distributed Data Bases
Inquiries Transparency Access Control Search
Reliability Load Balancing Notifications
Accounting
Information Management
7
Grid Challengesin Automotive Industry

• The challenge of integrating
• different disciplines
• Design (CAD)
• Simulation (CAE)
• Test (CAT)
• different locations
• different organisations

8
Product Structure- Simulation Structure

• CAD CAE Integration
• Situation
• For build-up of a simulation model
• structural information
• geometric and
• material data
• from CAD are needed
• Structure differs from load case to load case
• Geometric representation of the parts differs
  from load case to load case

Only the CAE engineer knows,which part is used
and in which form it is represented
9
Product Structure- Simulation Structure
A6_PFF_F_EU_W16_1005.pc - A6_b2_barriere_EU_1016
.inc 1K1.863.353.M TM 320.02.2003
1.01K1.872.463.M TM 323.02.2003 1.3
1K1.892.389.M TM 327.02.2003 1.1 -
A6_b2_fwk_hi_EU_W16_1035.inc 1K1.863.353.M TM
320.02.2003 1.01K1.872.463.M TM 323.02.2003
1.3 1K1.892.389.M TM 327.02.2003 1.1 -
A6_b2_motor_w16_1035.inc -
A6_b2_sitze_1011.inc - A6_b2_tuer_hi_1011.inc
- A6_b2_tuer_vo_1011.inc -
A6_pff_dummy_1000.inc - A6_pff_frontsf_1000.inc
- A6_pff_function_1000.inc -
A6_pff_fwk_vo_1005.inc - A6_pff_karo_1001.inc
- A6_pff_lenkung_1000.inc -
A6_pff_motorpac_w16_1000.inc -
A6_pff_mqtr_1000.inc - A6_pff_pedalerie_1000.in
c - A6_pff_tank_1000.inc -
A6_pff_verbindungen_1001.inc
A6_1 1.0 A6_Projekt ZSB11.0
A6_Z_Vorbau_UTFlur ZSB11.0
A6_M09_R4_FSI_VU ZSB11.0
A6_M09_HG8_VU ZSB11.0
A6_M09_Abt_VU ZSB11.0
A6_M09_Abt_DAE_VU ZSB11.0
A6_M09_Abt_DAEM ZSB11.0

A6_M09_Abt_DA_LL_V ZSB11.0
1K1.863.353.M
Teil11.0
- 1K1.863.353.M TM 320.02.2003 1.0
A6_M09_Abt_VKL_VU ZSB11.0
A6_M09_VKL_BO_VU
ZSB11.0
1K0.825.202.R TZ 318.06.2004 1.0
A6_M09_Abt_WAS_VU ZSB 11.0
A6_M09_Abt_WAS_U__ ZSB 11.0
1K0.825.675.L-
Teil01.0
1K0.825.675.L TM 128.04.2004 1.0
A6_M09_Abt_VKL_VU ZSB11.0
A6_M09_VKL_BO_VU ZSB11.0
1K0.825.202.R TZ
318.06.2004 1.0
1K0.825.675.L- Teil01.0
CAE structure(e.g. Trimmed Body)
CAD structure

• ontologies- if bottom plate in description,
  part is for body-include and represented by a
  mesh
• if mass lt 5 g part is not needed

use ontologies
for every part
file KVS xyz.CATPart representation
mesh mass 1,1 kg material St37 centre of
gravity -140 40 180 creator CAD Maier,
A. creator model Schmid, B. position -110
45 209 description bottom plate front right
file KVS xyz.CATPart mass 1,1 kg material
St37 creator Maier, A. position -110 45
209 description bottom plate front right

• possibly creation of missing attributes
• centre of gravity from geometry and material
• matrix of inertia from geometry and material

for everypart
10
Product Structure- Simulation Structure

• Selection of detected rules
• Structure parts are parts with the middle group
  number801-806, 807-810, 813, 814, 817
• Structure parts were modelled physically (mesh)
• Structure parts go into the include body

• Status
• CAD-CAE mapping of more than 80 of a car with
  1500 parts for NVH trimmed body
• prototype with ontobroker realised
• 35 rules only from structural information
• in progress search for more rules using more
  attributes

11
Meshing Brokering Service
shares CAD data
publishes meshing results
OEM DMZ
Data Service
estimates and records work
negotiates tasks
monitors task status
Meshing Broker
Meshing Service
notifies work done
uses SLAs
SLA Service
OEM
Supplier
monitors usage
12
Virtual Organisations
Service Provider
OEM 1
OEM 2
13
Virtual Organisations
Workflow
Workflow
GRIA Client
GRIA Client
Data services
Analysis services
GRIA Server
Visual DSS
Data services
Analysis services
Sim Manager
PAM-CRASH
Trusted site
14
Distributed Locations
Audi Use Case for Distributed Data Access

• Audi SEAT collaboration
• e.g. display of SEAT projects in Audi system
• Network limitations
• Bandwidth 10 MBit/s for all Audi SEAT issues
• Data amounts

Example Variant_1_EuroNCAP/Input 117.660 KB
Input Data Variant_1_EuroNCAP/Output
1.943.986 KB Results Variant_1_EuroNCAP/Mi
sc 2.797 KB Descriptions Variant_1_Euro
NCAP 2.064.446 KB Sum
15
SIMDAT AutoMotive Demonstrator (SAMD)
Distributed Locations

• Data used
• SAMD Car (Sedan Coupe)
• 2 SimManager systems running on two separate
  systems
• Audi SEAT

16
Distributed Locations
MSC.SimManager Audi
MSC.SimManager Seat
Oracle Data Grid
Replicated and Synchronized Meta Data
A
S
S
A
Webservice / rvs with OFTP
Webservice / rvs with OFTP
Vault A
Vault A
Vault B
A
S
Each file up to 500 GB
17
HeterogeneousData Structures
Test Simulation
head accelerationvs. time
chest accelerationvs. time
pelvis accelerationvs. time
validation of the complete system
18
HeterogeneousData Structures

• Audi use case forCAE/CAT integration
• View and use CAT data inthe same manner as CAE
  data in the CAE data management system

A3 (1354) A4 (356) A5 (170) A6 (107) A8 (325) TT
(211)
A3 (54) A4 (56) A5 (70) A6 (107) A8 (35) TT
(27) Q7 (21)
Convertible
Coupe
19
HeterogeneousData Structures

• CAT (Test)
• Vehicle configuration
• Test case
• Measured results
• Sensor output files
• Channels
• Movies
• Measured Values
• Evaluation of measured results
• Curves
• Images
• Values

• CAE (Simulation)
• Input Deck
• Model
• Design variant
• Load case
• Results
• Output files
• Post Process Objects
• Curves
• Animations
• Pictures
• Values
• Cross sequences

20
HeterogeneousData Structures
CAE System
CAT System

1. CAE System formulates request according to own
   data model

1. Request is transformed into data model of the CAT
   system

1. CAT System answers request. The answer is
   transformed again and sent back

21
HeterogeneousData Structures
Bus Grid Middleware
Registry-Service
Ontology Service
Semantic Layer
OGSA-DAI-Connector
OGSA-DAI-Connector
OGSA-DAI-Connector
Transport Layer
CAE-System (MSC.SimManager)
PDM-System
CAT-System (LMS Tec.Manager)
22
Summary

• Important steps for mastering the challengesin
  virtual car development
• Conversion of car product structures into
  simulation model structures by use of ontologies.
• Meshing brokering service based on GRIA.
• Grid solutions for Virtual Organisations with
  OEMs, suppliers and engineering services.
• Coupling of Simulation Data Managementsystems on
  distributed locationsby use of Grid Technology.
• Coupling of heterogeneous datastructures of
  Simulation and Test DataManagement via
  ontologies.

23
Applications of GRID Technologies in Automotive
Product Development

• Thanks a lot
• www.simdat.eu
• Josef.Reicheneder_at_audi.de