Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
1
OEM – Supplier Model Based
Collaboration AUTOSAR Methodology
Rosa Gragossian
DASSAULT SYSTEMES, North America
10/22/2015
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
2
Model Based Collaboration – partial models
• OEM asks Supplier to implement a subsystem
– SYSTEM-EXTRACT: From the complete System, OEM extracts and shares only the
information defining that subsystem
• OEM is interested in the function and its interfaces
– SYSTEM-EXTRACT may contain empty components (black box), partial model
• Supplier delivers component implementation and ECU HW
– Tier1 implementation usually contains IP, not to be disclosed
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
3
Virtual Functional Bus (VFB) System
data1 data2
data3
data4
data5
OEM’s Abstract System Description – Functional View
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
4
Virtual Functional Bus (VFB) System
data1
data2
data3
data4
data5
OEM’s model SWCs (Black Box)
Inter-Connections
Interfaces
Data Exchange
OEM’s VFB System Description – SW View (based on AUTOSAR templates)
SWCs as Black Boxes or with some level of refinement
OEM’s Abstract System Description – Functional View
data1 data2
data3
data4
data5
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
5
System Constraint Description owned by OEM
ECU-1 ECU-2 ECU-3 ECU-4
Can Bus 1
ECU-7 ECU-6 ECU-5
OEM’s model Network Topology
ECUs & Buses
Communication Matrix
Signals, PDUs, Frames
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
6
ECU-1 ECU-2 ECU-3 ECU-4
Can Bus 1
ECU-7 ECU-6 ECU-5
data1
data2
data3
data4
data5
System Mapping by OEM
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
7
ECU-1 ECU-2 ECU-3 ECU-4
Can Bus 1
ECU-7 ECU-6 ECU-5
data1
data2
data3
data4
data5
sig1-sig2 sig3-sig4
System Mapping by OEM
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
8
ECU-4
Can Bus 1
ECU-7 ECU-6 ECU-5
sig1-sig2 sig3-sig4
ECU-1
ECU-2
ECU-3
OEM’s model Root Composition and
Topology
SW-C to ECU Mappings
Communication Matrix
Data – Signal Mappings
System Configuration by OEM
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
9
ECU-3 ECU-1 ECU-4
Can Bus 1
ECU-7 ECU-6 ECU-5
Tier1 Implements the ECU
HW & SW
OEM’s Partial Model
SYSTEM-EXTRACT OEM’s model SYSTEM-EXTRACT
Root Composition
FLM Composition
ECU & Connected Bus
Communication Matrix
SWC to ECU Mapping
Data to Signal Mappings
OEM Transfers to Tier1 a System-Extract
including one or more Functions
sig1-sig2 sig3-sig4
FLM
Composition
ECU-2
SWComp-2
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
10
New Frontiers for Model Based Processes
• System-Extract is OEM’s specification
• System-Extract is an executable model instead of a document
• Tier1 merges with OEM’s model seamlessly and refines it
• OEM’s artifact remains intact
• Tier1’s detailed design remains protected
• Any AUTOSAR tool can be used by different parties
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
11
Tier1 - Implements the ECU SW and HW
ECU-2
Refines the model:
Decomposes the function into atomic level SW components
Can Bus 1 sig1-sig2 sig3-sig4
Tier1’s model Refined SWC SWC Internal Communications
ECU Extract
Refined SWC SWC Communications
Communication Matrix
Data – Signal Mappings
Signal – Frame Mappings
FML
Composition
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
12
Tier1 populates/refines OEM’s partial model
Includes a black box Composition, only delegation ports OEM’s Partial Model, Root Composition
Root_Composition
FLM_Composition_Type
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
13
Tier1 populates/refines OEM’s partial model
Includes a black box Composition, only delegation ports OEM’s Partial Model, Root Composition
Root_Composition
FLM_Composition_Type
Tier1 adds a refined Composition prototype
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
14
New Frontiers for Model Based Processes
• OEM only transfers required content: Ports and Mapping
OEM’s Partial Model
FLM_Composition_Type
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
15
New Frontiers for Model Based Processes
OEM’s Partial Model
FLM_Composition_Type
Tier1’s Refined Model
• OEM only transfers required content: Ports and Mapping
• Tier1 splits the Composition to refine the content in separate files
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
16
New Frontiers for Model Based Processes
• OEM only transfers required content: Ports and Mapping
• Tier1 splits the Composition to refine the content in separate files
OEM’s Partial Model
FLM_Composition_Type
Tier1’s Refined Model
+
Merged Model
OEM’s file
Tier1’s file
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
17
New Frontiers for Model Based Processes
• Merge is in the tool not in the files
• OEM’s artifact remains intact
• Tier1 sends back only needed info
• Separate Version Control
• Exchange only what is needed
• Compare files for relevant content
Merged Model
OEM’s file
Tier1’s file Split in a different file for IP protection
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
18
New Frontiers for Model Based Processes
• Merge is in the tool not in the files
• OEM’s artifact remains intact
• Tier1 sends back only needed info
• Separate Version Control
• Exchange only what is needed
• Compare files for relevant content
Merged Model
OEM’s file
Tier1’s file Replace with an empty composition
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
19
ECU-Extract
ECU Extract by Tier1 Tier1 extracts only ECU specific information from merged model to generate ECU-Extract
Merged Model
Root_Composition
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
20
ECU-Extract
ECU Extract by Tier1 Tier1 extracts only ECU specific information from merged model to generate ECU-Extract
Merged Model
Next Step Connect Service SWCs
Configure services for functional needs
Root_Composition
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
21
Tier1 – Tier2 Collaboration – one possible scenario Merge ECU–Extract with Tier2 Services model
Tier1 or Tier2
• In merged model creates connections
• Configures Services in merged model
• Merged model used for generation of BSW configuration
ECU-Extract
+
Tier 2’s Model Tier 1 – Tier 2 Merged Model
Tier2’s file
Tier1’s file
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
22
A Use Case with AUTOSAR Builder™
System Extract contains a Function
sent to the Tier1 for the first time
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
23
• Root Composition, from OEM Contains a prototype of FLM_CompositionType
• OEM’s FLM_CompositionType Contains only Delegation Ports
System Extract from OEM
FLM_Composition
Root_Composition
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
24
System Extract Mapping • OEM’s FLM_Composition_PT is mapped to an ECU
• The data from its delegation ports are mapped to system signals
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
25
Split out Tier1 model from System Extract OEM - file
FLM_Composition_Type
Tier1’s starts by creating an empty Composition Type (to be refined)
with no ports, in a file belonging to the Tier1
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
26
Split out Tier1 model from System Extract OEM - file
FLM_Composition_Type
Tier1’s Refined Composition Type
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
27
FLM_Composition_Type
Tier1 - file
Split out Tier1 model from System Extract OEM - file
FLM_Composition_Type
Tier1’s Refined Composition Type
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
28
System Extract split in OEM and Tier1 model
OEM - file FLM_Composition_Type
Tier1 - file FLM_Composition_Type
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
29
Root Composition contains a prototype of FLM_CompositionType populated by Tier1’s refinement
System Extract Mapping is propagated through the refined model
System Extract from OEM merged with Tier1 model
FLM_Composition
Root_Composition
• Perform Ecu_Extract
• OEM’s file is intact
• No mapping by Tier1
• Same process to integrate
service SWCs and their
connectors
3DS
.CO
M/C
AT
IA ©
Das
saul
t Sys
tèm
es |
Con
fiden
tial I
nfor
mat
ion
| 10/
27/2
014
| re
f.: 3
DS
_Doc
umen
t_20
14
30