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, 28.11.2012
 Outline

Status Model Based Architecture Development

A Look at the Broader Picture

2 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012

 E/E Architecture Development
E/E Concept Phase Series Development
Series Phase
Entire Car Components / Systems

Function distribution
Bus Load/Timing
Central components

Bus systems Cost

Power concept
Weight
Segments for
wiring harness Allocation
installation locations
Placement of components

Decision and validation about basic concepts

Integration of components and systems into the overall concept
Optimisation of the overall concept
3 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 Model Based Architecture Development with PREEvision

Description Evaluation
Integration of the relevant data in
Requirements/Features a consistent description

Data transfer to following process steps

Data transfer from preceding architecture

Functions Problem-oriented graphic

visualisation

Metrics/Reports
Networking

Computer-based evaluation of the

Wiring Harness
modeled data
Fast execution and evaluation of
Topology architecture changes
Comprehensive documentation of
Integrated formal Model
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 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 PREEvision Modeling Results

Central Used Metrics

Network
Diagram Bus load
Used Automation
Wiring harness costs
Generation / routing of signal
Wiring harness weight
paths
Currents (power concept
Generation / routing of wires Topology Diagram
validation)
OptimisationECU
ground spots
Network
Diagram
...
System Diagram
Setting of splices
...
Ground Diagram

E/E Platform for S/E/C class:

PDC Diagram Electrical components: approx. 1000
Wiring Harness Wires: approx. 4000
Diagram Pins: approx. 6000
Diagrams: approx. 300

For Mercedes Benz Cars, an integrated digital development in the concept phase has been established.
5 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 Outline

Status Model Based Architecture Development

A Look at the Broader Picture

6 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012

 E/E Design Data and Tools Yesterday and Today
Data Databases / Tools yesterday Database / Tools today

Concept Series Development Concept Series Development

Phase Phase

Requirements/
Features
System/
SW Design
Animation!
Networking

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 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 Exchange/Coordination of E/E Design Data Today
Data Databases / Tools today

Concept Series Development

Phase

Requirements/
Features
System/
SW Design
Overall data integrity is
Networking Overlapping technical
addressed by loose tool
Component
data
coupling or manual exchange
Design (HW) Versions/Releases
processes
Variants
Wiring Harness
XML
Topology

Today E/E series development works without a central database solution.

8 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 Trends and Options for the Future
Trends

Increasing amount of functions Module approaches Internationalisation

More variants Reduction of prototypes ISO 26262
Reduced development times Cooperation projects ...

Options for Tool-/Data Infrastructure

Scenario 1
Increased
coupling

Scenario 2
Overall
central e/e database

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 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 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 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 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 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 Central Use Case Mechanics: Integration of Complete Vehicle

Singular Components

Background

Innovation rates
Crash requirements
Integration within vehicle space
Problem solving for design conflicts 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-theart premium vehicle can no longer be developed
without integrated digital design approach.
12 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
 Comparison: Digital Design of Mechanics and Electrics
Mechanics Electrics
Innovation Speed Innovation Speed
Variety of Variants Motivation/ Variety of Variants
Reduced development times Background Reduced development times
Reduction of physical prototypes Reduction of physical prototypes
... ...

Integrated
Data Model
VEC (OEM-specific
PDM data models)

Integration of Integration of
complete
Central complete E/E
vehicle Use Case Mastering
overall complexity

Crash Thermal Analysis Wiring Harness Functions

Assessment
Fatigue Strength Validation Bus Load

Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012
13
 Comparison of Future Scenarios
Pros/Cons
+ Continuous integration of existing solutions
+ Usage of best in class tools possible
+ Flexible (changeable, extendable)
-- Complex interfaces (maintenance, version

Scenario 1
dependency, )
Increased
-- Complex synchronization data flows
coupling
-- No cross domain traceability

+ Tight data integration

Overall Scenario 2 + Clearly defined single source concept
central e/e database + Integrated version and release management
-- Initial costs
Tomorrow -- Organisational impact
-- High effort for IT change management process
-- IT complexity risks (no standard solution available)

14 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012

 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
Required
Evaluation of future scenarios: Extension of tool coupling Bandwidth

vs. overall E/E data base

Signals
~4100 Signals
~6000 Signals

7 ECU ~200 Signals 67 ECU ECU

1 Bus 52 ECU
9 Busses Busse
2 ECU 30 ECU 5 Busses
3 Busses

W110/112
W120/121 W114/115 W123 W124 W210 W211 W212

15 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012

 Questions & Discussion

16 Markus Hemprich, Gabriel Schwefer - Vector Congress 28.11.2012