Reference Model for the Cooperative Exchange of Simulation Data

Transcription

1 Reference Model for the Cooperative Exchange of Simulation Data Partner Production 1

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 Proceeding 2

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) 3

4 Internal and External Data Exchange OEM 1 separate interface for every partner BoM CAD ERP OEM 2 emserver BoM DMU CAD ERP Supplier 1 EDM BoM CAD ERP RPT Supplier 2 VPM BoM VPT CAD ERP Source: MAGNA STEYR 4

5 Target: One Platform for Internal and External Exchange OEM 1 BoM CAD ERP OEM 2 emserver BoM VPT CAD ERP RPT Supplier 1 BoM CAD DMU ERP Supplier 2 BoM CAD ERP VPM EDM Source: MAGNA STEYR 5

6 Scope (1) Project Scope Reference Model VPT DMU Virtual Factory Geometric Integration Functional Integration Manufacturing Oriented Integration Digital Product and Process Data Reference 6

7 Scope (2) 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:.. 7

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 Different language of the project partners 8

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 VPT Reference Model Partner A (internal/external) Process mapping VPT Process Partner B (internal/external) VPT Reference Process VPT Process VPT Methods VPT Methods VPT Systems VPT Systems VPT Reference Data Model VPT Data VPT Data Data mapping 9

10 Process Oriented Solution Harmonized synchronisation with the VPT reference process and the data synchronization points Spezifischer Partner Specific VPTVPT-Prozess Process Partner 1 1 Coordinator Preparation Phase Data Collection Phase Participant VPT Reference Process Mapping Data Preparation Phase Solving Phase Postprocessing and Analysis Consolidation Phase Mapping Spezifischer Partner Specific VPTVPT-Prozess Process Partner 2 2 Source: PDTec, adapted 10

11 Example for an interaction scenario Scenario: External assembly of a module for crash simulation Preparation Data Collection Data Preparation Solving Postprocessing and analysis Consolidation VPT Coordinator Auftrag zur Modulerstellung Fertig parametrisiertes Modul Simulationsauftrag Firmenstandards relevante Teile Vorhandene Geometrie und FENetze Verbindungsdaten Werkstoffkennwerte Verwendete Geometrien Erstellte Netze Fertiggestelles Modul inkl. aller Parameter Eingearbeitete Verbindungsdaten VPT Participant 11

12 Data Model Overview Simulation Order order designated parts S[1:?] Simulation Task representated_through Vehicle component Component Usage task used parts S[1:?] Simulation Run Assembly Usage Input data CADGeometry derived from Simulation Model Input Data number status Output data Output Data Load Case Parameters Solver Settings Simulation class Simulation method Parameters Solver Output Simulation Report 12

13 Benefits (1) Partner Partner spezifischer spezific VPT Process Prozess internal OEM-dept. C Rec eiv e Reques t Creation ECR Tec hnic al A nalys is and Detailing ECR Comments of ECR ECR A c c eptanc e and A pprov al OEM-dept. B VPT Participant VPT Coordinator Receive Request Creation ECR Technic al A nalysis and Detailing ECR Comments of ECR Receive Request Creation ECR Technical A nalysis and Detailing ECR Comments of ECR ECR A cceptance and Approval Coordinator (other VPT) ECR A c ceptance and A pproval Participant (other VPT) OEM-dept. A external Receive Request Creation ECR Technical A nalysis and Detailing ECR Comments of ECR VPT Reference Process ECR A cceptance and A pproval Receive Request Creation ECR Technical Analysis and Detailing ECR Comments of ECR ECR Acceptance and Approval Tier 1 Rec eiv e Reques t Cr eation EC R Tec hnic al A nalys is and Detailing EC R Comments of EC R ECR A c c eptanc e and A ppr ov al Rec eiv e Reques t Cr eation EC R Tec hnic al A nalys is and Detailing EC R Comments of EC R ECR A c c eptanc e and A ppro va l Source: PDTec, Tier 3 Tier 2 adapted 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 13

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 Prepared interfaces for the involved IT-systems 14

15 Outlook VPT Reference Model is documented in the VPT Guideline Aim to establish a ProSTEP ivip project group based on the VPT Guideline VPT Reference Process VPT-Guideline VPT Interaction Scenarios Vorber eitung Datenbeschaffung Datenaufbereitung Simulation Ergebnisaufbereitung Konsolidierung VPT Coordinator Auftrag zur Modulerstellung Simulat ions auftrag Firmenstan dards relevante Teile Vorhanden e Geometrie und FENetze Verbindun gsdaten Werkstoffk ennwerte Fertig parametrisiertes Modul Verw endet e Geometrie n Erstellte Netze Fertiggeste lles Modul inkl. aller Parameter Eingearbeit ete Verbindun gsdaten VPT Participant VPT Reference Data Model Prototypical Data Exchange repräsentiert_durch Sim ulati onsauftr Fahr Sim ag zeug auftrag ulati vorgesehener_teileumfang S[1:?] onsbaut kom aufg eilpon Bau Sim abe simulationsklasse verw aufgabe ente benutzter_teileumf grup ulati end penons- simulationsverfahren ung ang S[1:?] num verw lauf kon mer end Sim stru eingabedaten ung statu ulati Inpu ausgabedaten Out ktive Solv onstdat sputd Solv Sim Para Geo Last abgeleitet ermod en aten Para erou ulati metr aus ellmet fall eins met tput onser ie tellu er repo nge rt n 15

16 Thank you for your Attention! Contact: Markus Hofer Vif the virtual vehicle research company phone: