1. Jürgen Kaiser (Speaker)
EXEED:
Integrated, model based development of the E/E-System of CHERY‘s new vehicle platform
Authors
Jürgen Kaiser (Speaker)
Giselle Fernandez Soto (3E-motion Ventures)
Xiaojun Tang, Jay Li, George Guo, Cai Wen (CHERY Auto)
Joerg Brandscheid (Continental)

2. 1 2 3 CHERY EXEED (Presentation IAA Frankfurt 2017)
3E-motion: Partner of CHERY since 2014 1
Support of the development of the EXEED E/E-platform using ESCAPE / Virtual Solution Design 2
Integration of traditional methods (Excel, Visio, ...) with model based engineering and task-automation 3
Creation of all models and libraries, automatic generation of data, documents and diagrams 2

3. Jump start here! SoP ECU Parameters Bus-Communication Functions
Features
Architecture
Electrical
Jump start here!

4. Mechanical Engineering
Areas and Standard-Systems of an OEM
Finance
SAP
Mechanical Engineering
CATIA, NX
Production PDM/PLM
E/E-Engineering

5. No Standard-E/E-Engineering, Microsoft-Office used instead
Lots of tools, „Standards“ and interfaces
Document-based process, complex methods and tools
Model based tools developed for experts by experts
Developers use Excel, Visio and Word instead

6. Seamless!

7. Connected cars /ADAS: Vehicles become part of a huge network
Challenge: Ever shorter development time and many updates

11. V-Model (Theory) Features Requirements Subsystems Functions
Architecture
Communication
Design &
Simulation
Implementation
Validation
Production
Documentation
Configuration
V-Model
(Theory)

13. Product-Reference-model
Features
Integration platform: ESCAPE
One Tool, one method across the
whole process with the integration
of the state of the art-tools
in development
Remote Diagnosis
Requirements
Fault back tracking
Functions
Test case generation
Solutions
Debugging & Test
Architecture
Failure-Risk Analysis
Wire&harness-Design
Simulation
Automatic
Code-Generation
Model based Software-Design

14. Reuse solutions Product-Reference model
Features
Production
Requirements
Subsystems
Functions
Configuration
Architecture
Communication
Documentation
Design &
Simulation
Validation
Implementation
Engineering Data Backbone: Solution libraries

15. Interface Management & Data consistency
Product reference model
Features
Production
Requirements
Subsystems
Functions
Configuration
Architecture
Communication
Documentation
Design &
Simulation
Validation
Implementation
Engineering Data Backbone: Solution libraries

16. Automatic generation of product data and documents
Product reference model
Remote access
Features
Production
Requirements
Subsystems
Functions
Configuration
Architecture
Communication
Documentation
Life Cycle Data
Management
“Maintelligence”
Design &
Simulation
Validation
Implementation
Engineering Data Backbone: Solution libraries

17. Data management systems
Integration of process & product via engineering objects approach
Product Reference Model
Engineering Objects
Object Attributes
Features & functions
Solution Elements
(HW/SW)
Components
(ECUs, Busses, cables,…) C B A EO D
Process Steps
Task elements
(Tasks, People, Tools)
Organisation,
Data management systems
Process Reference Model

18. Engineering Process, Tasks & Resources Features and Requirements
Function network
Subsystems
Solutions (HW&SW)
System Architecture
Engineering Process, Tasks & Resources
Features and Requirements
Components
Busses & Nodes
Vehicle-Topology
Messages & Signals
Software Design

19. From document-based to integrated, model based process
Transformation
Integration
E/E-Platform
Reference-Model
XML
Excel
Word
Visio
PDF
CANdbc
Simulink
KBL
C-Code
Generation of Specification
Document-Generation
Code-Generation
Simulation
Wiring diagram generation
Bus-Configuration
Automation

20. Integration of traditional methods with model based engineering
Specification Data format [Excel]
Authoring
[Excel]
Data & Documents
Form, Rules
Excel-sheet
Transformation tool- Adaption
[FunTransformer]
Automatic
Model-
Generation
&
Validation
[Excel to XML]
Vehicle Reference model
Errors & Warnings
Product &
Process
Model &
Transformation
Document-Generation
[XSLT]

21. Rapid Creation Transformation Automation Functional Reference- Model
Systems Engineering Team
Automatic generation of models
Rules, consistency- & plausibility checks
FunTransformer
Excel-sheet
Subsystems (67)
Function groups
Functions (662)
Interfaces
Signals (1972)
Functional
Reference-
Model
(XML)
Function oriented view, component oriented view, ...
Electrical System Team (harness)
System Architecture Team (Communication)
Automatic Document generation
Rapid Creation
Transformation
Automation

22. Hierarchical Model of all subsystems, function groups, functions, signals (physical, internal, CAN/LIN)

23. Information filtering
Failure risk analysis and fault back tracking in product reference model

24. Rapid Creation Transformation Automation Realtime Communication Model
System-Architecture-Team
Automatic Model Generation
Rules, Consistency & Plausibility-Check
Dbc-files
Diagnosis, Network-Management,
System Architecture Configuration
Excel-Sheet
Busses
Nodes
Messages
Signals
Datatypes
Value tables
Communication matrix
Realtime
Communication
Model
(XML)
Suppliers
Automatic Generation of dbc-files for all Busses incl. Interaction-Layer-Attributes
Automatic Generation of Gateway-Tables
(Communication matrix)
Automatic document generation
Rapid Creation
Transformation
Automation

25. Automatic Generation from model
CAN/LIN Busses, Nodes, Messages, Signals, Value tables,...
Vehicle level: Busses
Bus-Level: Nodes
Node-Level: Messages and Signals
Automatic Generation from model
.dbc/.ldf-files for each bus, signal matrix, Gateway-Tables, Excel-sheets, Documentation

26. Message Type Library / PDM-compatible
Message-Type (Sender)
Static Attributes
Message Instance (Receiver)
with „mapped RX-signals“
Dynamic Attributes
Interaction-Layer Support
Vector-Format compatible in both directions

27. Signal type library / PDM compatible
Signal-Library (Datatypes)
Significations (Value tables)
ODX-Support
Vector-Format compatible in both directions

28. Product Reference Model [ESCAPE]
Marketing
Feature design
Variants & Options
Systems
Engineering
Subsystems & Functions
Architecture- Design
System Architecture
Communication
Realtime-Busses Configuration
Software design
Model based SW-development
Electrical Engineering
Components, Cables, Fuses, Power supply
Diagnosis design
ODX/PDX, Services
Product Reference Model [ESCAPE]
Feature Model
Function network
Electric-Model
Communication model
Architecture, Topology
Software Models
Diagnosis Model
Requirements Model
Documents
ECU Specification
Simulation
CAN .dbc
LIN .ldf
ODX .cdd
Schematics
RAPTOR
The whole Engineering-Process with all Data and Tools is integrated using a model based
Product Reference Model
Remote access to Data (TCP/IP)
Functional Testing & Diagnosis

29. Integrated Model Based Engineering

30. Mission level Solution level Data Data Implementation level
Feature-, Requirements-, Function network
Data
Data
Solution level
Solution models, architecture design & evaluation
Implementation level
ECU development, onboard network

31. Function network: Hierarchical decomposition of functions
Example
Network nodes
Seat belts
Airbags
Seat control
Doors
lock/unlock
Lights
Power
Windows
Exterior
lights
Exterior Indicators
Adaptive
Interior Lights
Leave node
High beam
Rear lights
Low Beam

32. Model elements: Function
Model elements are defined as simple as possible to keep the entry level to model based technologies low.
Basic principles: data flow from left to right (inputs left, outputs right), clearly defined graphical representation of information in shape and colour, all data of a function accessible via the graphical object
Crash_detected
lock
Power
Back light
Alarm_on
Alarm_off
Sensor_front
Sensor_back
Error_1
Error_2
Error_3
Error_4
Error_5
Error_6
Light
Function

33. Engineering Object: Function
Engineering Objects know all of its data and the tools for editing
Simulation
Requirements
Implementation
Crash_detected
lock
Power
Back light
Alarm_on
Alarm_off
Sensor_front
Sensor_back
Error_1
Error_2
Error_3
Error_4
Error_5
Error_6
Light
User specific
Attributes
Access Rights
Dependencies
Documentation
Costs

34. Model element : Terminal
Inputs and outputs are represented by Information Objects, socalled „Terminals“. Terminals are Objects, which can not exist on its own, but possess attributes like Datatype (e.g. Bool, Byte, UINT, Current, Voltage, Temperature,…) or Terminaltype (Software-, Hardware-, Process terminal). Terminals can own or transport Information.
Input-Terminal
Output-Terminal
Crash_detected
lock
Power
Back light
Alarm_on
Alarm_off
Sensor_front
Sensor_back
Error_1
Error_2
Error_3
Error_4
Error_5
Error_6
Light
Function

35. Function nodes can have an unlimited number of subsystems
Function nodes can have an unlimited number of subsystems. The dataflow between the subsystems is represented by „connections“.
Connection
Crash-Detection
Crash_detected
Lock_vehicle
Rear_gear
Alarm_on
Alarm_off
Light
Diagnosis
Alarm System
Crash_detected
lock
Power
Back light
Alarm_on
Alarm_off
Sensor_front
Sensor_back
Error_1
Error_2
Error_3
Error_4
Error_5
Error_6
Sensor_f_defect
Sensor_b_defect
Error_1
Error_2
Error_3
Error_4
Error_5
Error_6
Door lock
Gear

36. Process chain: Transformation of information
SW-Type
Virtual Solution Design: HW / SW- solution model
Function: Rear window heating
Process type
Hardware type
Software type
Hardware type
Process type
LED
[Sensor]
[ECU1]
[ECU2]
[Actuator]
[Indication]
Hardware type
Process type
Heater
Process chain: Transformation of information

37. Marketing features Engineering features
Feature design from marketing department point of view
Features, variants, options
Engineering features
Feature design from engineering point of view.
Feature library, constraints, requirements, identification, versioning, implementation

38. Automatic generation of 67 Subsystems
Model based subsystems & functions design
Automatic generation of 67 Subsystems
graphical models for function view

39. Automatic generation of 67 Subsystems
Model based subsystems & functions design
Automatic generation of 67 Subsystems
graphical models for component view

40. ESC: Function View ESC: Component View
Model based subsystems & functions design
ESC: Function View ESC: Component View

41. Virtual Solution Design: HW / SW- co-design model
Example: Solution model [Door lock / unlock] , QOROS 5

42. Model based Failure Effects Analysis / Fault back tracking
Example: Connection to ground faulty
Affected model elements shown in orange
Example: Door unlock motor doesn‘t work
Possible reasons for the fault shown in orange

43. Model based electrical and cable & harness design
Example: Relay
Schematics
ESCAPE
86: Coil plus (12V)
85: Coil minus (Gnd)
30: Input
87a: output (not switched)
87: output (switched)
Interface
Interface
Dependency matrix

44. Example: Maintenance light relay /Combine harvester
Model based electrical and cable & harness design
Example: Maintenance light relay /Combine harvester
Schematics
ESCAPE Virtual Solution Design model

45. Automatic generation of wiring diagrams

46. Systems architecture design & analysis: Communication

47. Systems architecture design & analysis: Topology
Rear right
Front left
Components & mapping Topological view on components & buses

48. Automatic Generation of Simulink-Models
ESCAPE-Model
Simulink-Model

49. Requirements are Engineering Objects / Part of a function/Solution
Requirements Model
Automatically generated Requirements document

50. Reduction of development time
Reduction of the development time of E/E-Systems from 3 years to 1 year
Reduction of development effort
Reduction of the development effort (OEM) up to 70% by Automation of engineering-tasks
Reduction of development risk
Elimination of errors and iteration cycles by integrated, data based Engineering