Model Based E/E Architecture Development at Daimler

Transcription

1 Model Based E/E Architecture Development at Daimler...and a Look at the Broader Picture Markus Hemprich Gabriel Schwefer E/E Architecture & Standardisation (RD/EEP) Vector Congress Stuttgart,

2 Outline Status Model Based Architecture Development A Look at the Broader Picture 2

3 E/E Architecture Development E/E Concept Phase Entire Car Series Development Components / Systems Series Phase Central components Bus systems Power concept Segments for wiring harness Function distribution Placement of components Bus Load/Timing Cost Weight Allocation installation locations Decision and validation about basic concepts Integration of components and systems into the overall concept Optimisation of the overall concept 3

4 Model Based Architecture Development with PREEvision Data transfer from preceding architecture Requirements/Features Functions Networking Wiring Harness Topology Integrated formal Model Description Evaluation Metrics/Reports Data transfer to following process steps Integration of the relevant data in a consistent description Problem-oriented graphic visualisation Computer-based evaluation of the modeled data Fast execution and evaluation of architecture changes Comprehensive documentation of the E/E architecture PREEvision supports the architecture development with a frontloading approach: high maturity level in the concept phase by comprehensive description and evaluation. 4

5 PREEvision Modeling Results Used Automation Central Network Diagram Generation / routing of signal paths Generation / routing of wires Optimisation ground spots Setting of splices... ECU Network Diagram Topology Diagram Used Metrics Bus load Wiring harness costs Wiring harness weight Currents (power concept validation)... System Diagram Wiring Harness Diagram PDC Diagram Ground Diagram E/E Platform for S/E/C class: Electrical components: approx Wires: approx Pins: approx Diagrams: approx. 300 For Mercedes Benz Cars, an integrated digital development in the concept phase has been established. 5

6 Outline Status Model Based Architecture Development A Look at the Broader Picture 6

7 E/E Design Data and Tools Yesterday and Today Data Databases / Tools yesterday Database / Tools today Concept Phase Series Development Concept Phase Series Development Requirements/ Features System/ SW Design Networking Animation! Component Design (HW) Wiring Harness LCable LCable Topology The distributed data/tool environment was integrated into functional clusters. Currently, an integrated database exists only in the concept phase. 7

8 Exchange/Coordination of E/E Design Data Today Data Databases / Tools today Requirements/ Features System/ SW Design Networking Component Design (HW) Wiring Harness Topology Concept Phase XML Series Development Overlapping technical data Versions/Releases Variants Overall data integrity is addressed by loose tool coupling or manual exchange processes Today E/E series development works without a central database solution. 8

9 Trends and Options for the Future Trends Increasing amount of functions More variants Reduced development times Module approaches Reduction of prototypes Cooperation projects Internationalisation ISO Options for Tool-/Data Infrastructure Increased coupling Scenario 1 Overall central e/e database Scenario 2 Yesterday Today Tomorrow In which direction will the tool and data infrastructure advance? How is the development handled in other disciplines? E.g.: mechanical engineering? 9

10 Mechanical Design Today Aerodynamics Crash Digital Product Climatisation Strength/Reliab. Thermic Analysis Ride & Handling NVH All mechanical components are digitally integrated to a complete vehicle. 10

11 Infrastructure for Digital Mechanical Design All Use Cases are based on the same basic data model and are driven from a central data base Formal established within overall development process Responsible role for central data management with reporting line to the head of development Central version, release and variant management Integration of suppliers (mandatory data provision) Extensive training / support organisation Why has integrated digital design been established for mechanical engineering? Why are the infrastructure costs accepted? 11

12 Central Use Case Mechanics: Integration of Complete Vehicle Singular Components Background Innovation rates Integration within vehicle space Problem solving for design conflicts Crash requirements Increasing variety of variants Reduced development time Reduction of physical prototypes Concept examinations and conflict solving are not feasible without digital approaches given the short development timeframe. The mechanics of a state-of-the art premium vehicle can no longer be developed without integrated digital design approach. 12

13 Comparison: Digital Design of Mechanics and Electrics Mechanics Electrics Innovation Speed Variety of Variants Reduced development times Reduction of physical prototypes... Motivation/ Background Innovation Speed Variety of Variants Reduced development times Reduction of physical prototypes... Integrated Data Model VEC (OEM-specific PDM data models) Integration of complete vehicle Central Use Case Integration of complete E/E Mastering overall complexity Crash Thermal Analysis Wiring Harness Functions Fatigue Strength Assessment Validation Bus Load 13

14 Comparison of Future Scenarios Increased coupling Overall central e/e database Tomorrow Scenario 1 Scenario 2 Pros/Cons + Continuous integration of existing solutions + Usage of best in class tools possible + Flexible (changeable, extendable) -- Complex interfaces (maintenance, version dependency, ) -- Complex synchronization data flows -- No cross domain traceability + Tight data integration + Clearly defined single source concept + Integrated version and release management -- Initial costs -- Organisational impact -- High effort for IT change management process -- IT complexity risks (no standard solution available) 14

15 Summary Model based development and integrated data base lastingly established for E/E concept phase Formerly distributed E/E data and tool landscape integrated to a set of main clusters Evaluation of future scenarios: Extension of tool coupling vs. overall E/E data base ~4100 Signals ~6000 Signals Required Bandwidth Signals 2 ECU 7 ECU 1 Bus ~200 Signals 30 ECU 3 Busses 52 ECU 5 Busses 67 ECU 9 Busses ECU Busse W110/112 W120/121 W114/115 W123 W124 W210 W211 W212 15

16 Questions & Discussion 16