vobes process
-
Upload
luizneto27 -
Category
Documents
-
view
124 -
download
23
description
Transcript of vobes process
-
Fo
l
i
e
1
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
ProSTEP iViP Symposium 2006
Integration of the Electrical System Development
Processes with KBLOEMs Viewpoint
Jorgos KyriazisVOBES Development Team
-
Fo
l
i
e
2
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
Overview
Some words about the electrical system, harnesses and their development process
The Classic VOBES Process (1st generation) Challenges and optimization potentials How KBL helps us implement a modular tool
chain (VOBES 2nd generation) Examples for KBL driven applications Conclusion
-
Fo
l
i
e
3
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
The Electrical Net of a car
The electrical net is the infrastructure for signaland energy transport between all electricalcomponents
The electrical net consists of various wireharnesses. The main harness is normally a combination of
modules that are configured due to the customers choice. Some million valid configurations can bepossible.
Minor harnesses are designed in variants, whereeach configuration has a specified part number.
-
Fo
l
i
e
4
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
The Design Process and Design Tools
Nearly every car manufacturer has a different approach to design harnesses that fits to his specific logistic concept.
All core design processes can be split into these phases: Functional Design System Design Installation and DMU Harness Design Documentation / Data Output to Manufacturing
There is no end-to-end design tool available, that offers applicable solutions to all of these phases.
Thats the reason, why VW developed VOBES.
-
Fo
l
i
e
5
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
VOBES Core Process (1st Generation)VOBES - Volkswagen Bordnetz-Entwicklungssystem
E3LCable
Interface
+ S
oftware
byVW
3D Harness Installation (ELV)CATIA V4 by Dassault Systemes
Wiring Schematics (KAB)LCable by Mentor Graphics
with VW-Userware
System Schematics (SYS)LCable by Mentor Graphics
with VW-Userware
Drawing Generation (ELZ) CATIA V4 + VW-Userware
-
Fo
l
i
e
6
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
Aspects Of VOBES Until 2003
VOBES 1st generation integrated ECAD and MCAD data achieved a consistent design data flow from system
design to documentation had a lot of outstanding functionality
used proprietary internal interfaces used proprietary internal data formats needed complex userware in CATIA and LCable was expensive to maintain
-
Fo
l
i
e
7
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
Evolution Into The 2nd Generation Of VOBES
Key Challenges extract more value from the existing data by extended
use of design data within the design process improvement of performance integration of new generations of CAD editors smooth evolution with parallel use of tools
Key Solution modular toolchain with neutral interfaces integration of the best tools available for each phase
-
Fo
l
i
e
8
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
Transition Towards The Modular Toolset
Volkswagen builds the future Electrical System Development Process
on standard data formats and on amodular software architekture
with a file-based exchange ofdesign data.
Implementation of KBLXML
Integration of LDoradoas documentation module
Implementation of Digital ChangeDocumentation based on LDorado
ECAD/MCAD Integrationwith ELENA
NewSchematics Editor
Simulation of theElectrical System
1
2
3
4
5
6
-
Fo
l
i
e
9
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
VOBES Core Process (2nd Generation)
ELENAElectrologic Domain
C
o
n
n
e
c
t
i
v
i
t
y
Mechanical Domain
Harness Documentation
LCable
New Tool VDAELog
VDT
CATIA V5
CATIA V4VDT
KBL*
KBL
KBL*
VDT2KBL
ELog2KBL
any other processor tool, that requiresharness data inKBLXML formatParts&Instances
Merge Route
E
d
i
t
&
E
n
r
i
c
h
LDoradoLayout
Digital ChangeDocumentation
LDoradoDesign
K
B
L
K
B
L
E
x
p
o
r
t
K
B
L
X
M
L
Topology
KBL based data flow proprietary data flow
-
Fo
l
i
e
1
0
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
ELENA Sub-modules
LCable
VDT-Interface
ModuleEditor
WireEditor
ContactSelection
CATIA V5
XML
Merger
XML
Router AssemblyEditorModule
AssignerAlias Editor
VDT
Cntct&WireCalculation
KBL-CheckerKBL
Export
LDorado
KB
L
Import/Update
TopologyExport
E L E N A
-
Fo
l
i
e
1
1
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
Change Notification Digital Change Documentation
accurately versioned storage in System42
KBLXML
PQ46 Autumn 2005
partially automated generationBOM and Wirelist automatically
in the background
100% digital availabilityfor FASD and VELEA
Frontpage
-
Fo
l
i
e
1
2
J
o
r
g
o
s
K
y
r
i
a
z
i
s
,
V
o
l
k
s
w
a
g
e
n
A
G
,
G
O
E
3
1
0
8
.
0
6
.
2
0
0
6
ELEKTRIK / ELEKTRONIK ENTWICKLUNGELEKTRIK / ELEKTRONIK ENTWICKLUNG
Conclusion
KBL and its derivates
have a data model to represent harness data,
help us build neutral interfaces between applicationswith different scope and
enable us to modularize the tool chain,
allow us to extend the usage of design data along the product process and
can also be used to forward harness data to our suppliers