69
VDA Recommendation 4964 1 st Edition, November 2005 Page 1 of 69 Copyright: VDA VDA Harness Description List (KBL) 4964 This current recommendation is not binding and describes the information needed to exchange harness design data within car manufacturers and suppliers. The recommendation defines the required objects with their descriptions and attributes, a formal information model, the mapping to ISO 10303-212 “Electrical Design and Installation”and the representation in XML. The recommendation deals with the following subject areas: - Harness, variants and modules - Components like connectors or wires - Part lists - Connectivity lists - Topology 1 st Edition, November 2005 Project Group "Car Electric" of VDA Working Group "CAD/CAM" Published by: Verband der Automobilindustrie Copyright Westendstraße 61 Reprinting or reproduction in any Postfach 17 05 63 form are permitted only if the 60079 Frankfurt source is cited. Phone: +49 (0)69/97507-284 Fax: +49 (0)69/97507-300 Internet: [email protected]

Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 1 of 69

Copyright: VDA

VDA

Harness Description List (KBL)

4964

This current recommendation is not binding and describes the information needed to exchange harness design data within car manufacturers and suppliers. The recommendation defines the required objects with their descriptions and attributes, a formal information model, the mapping to ISO 10303-212 “Electrical Design and Installation” and the representation in XML.

The recommendation deals with the following subject areas:

- Harness, variants and modules

- Components like connectors or wires

- Part lists

- Connectivity lists

- Topology

1st Edition, November 2005

Project Group "Car Electric" of VDA Working Group "CAD/CAM"

Published by: Verband der Automobilindustrie Copyright

Westendstraße 61 Reprinting or reproduction in any

Postfach 17 05 63 form are permitted only if the 60079 Frankfurt source is cited. Phone: +49 (0)69/97507-284 Fax: +49 (0)69/97507-300 Internet: [email protected]

Page 2: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 2 of 69

Copyright: VDA

Disclaimer

The VDA recommendation "Harness Description List (KBL)" is a recommendation, which is freely available in the public domain. Anybody applying this recommendation is responsible for ensuring that it is correctly applied in the case in hand.

It takes account of the current state of the art in technology at the time each edition is issued. The use of the VDA recommendations does not exonerate anybody from the responsibility for their own actions. In this respect, each person acts at his own risk. No liability can be accepted by the VDA and by those involved in producing the VDA recommendations.

Readers and users are requested to inform the VDA immediately if they notice any inaccuracies or statements, which can be interpreted incorrectly while using this VDA recommendation in order that any errors may be corrected.

Page 3: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 3 of 69

Copyright: VDA

Contents

1 PREAMBLE.............................................................................................................................8

2 GOALS OF THE RECOMMENDATION...................................................................................9

3 SCOPE AND RESPONSIBILITIES..........................................................................................9

4 STRUCTURE OF THE RECOMMENDATION........................................................................10

5 GLOSSARY OF TERMS........................................................................................................10

5.1 Accessory (Zubehör)........................................................................................................10

5.2 Alias part (Alternativ Sachnummer) ................................................................................10

5.3 Assembly part (Baugruppe).............................................................................................11

5.4 Block Diagram (Blockschaltbild) .....................................................................................11

5.5 Bundle (Leitungsbündel)..................................................................................................11

5.6 Cavity (Kontaktkammer)...................................................................................................11

5.7 Cavity Plug (Blindstopfen) ...............................................................................................11

5.8 Cavity Seal (Kontaktkammerdichtung) ...........................................................................11

5.9 Cable (Leitung) .................................................................................................................11

5.10 Cable Drawing (Kabelzeichnung).................................................................................11

5.11 Circuit Diagram (Funktionszeichnung)........................................................................11

5.12 Connection (Verbindung) .............................................................................................11

5.13 Connection Diagram (Verbindungszeichnung)...........................................................11

5.14 Connector (Steckverbinder) .........................................................................................11

5.15 Connector housing (Steckergehäuse).........................................................................11

5.16 Connector list (Steckerliste).........................................................................................11

5.17 Contact (Kontakt) ..........................................................................................................12

5.18 Co pack part (Kabelbaumzubehör) ..............................................................................12

5.19 Core (Kabelader) ...........................................................................................................12

5.20 Extremity (Kabelende) ..................................................................................................12

5.21 Fixing (Kabelbefestigung) ............................................................................................12

5.22 Function Diagram (Funktionsplan) ..............................................................................12

Page 4: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 4 of 69

Copyright: VDA

5.23 Harness (Kabelbaum) ...................................................................................................12

5.24 Harness configuration (Kabelbaum variante) .............................................................12

5.25 Housing (Steckergehäuse) ...........................................................................................12

5.26 Form board (Formbrett) ................................................................................................12

5.27 Module (Leitungsstrangmodul) ....................................................................................12

5.28 Module configuration (Modulumfang) .........................................................................12

5.29 Module family (Modulfamilie) .......................................................................................13

5.30 Netlist (Verbindungsliste) .............................................................................................13

5.31 Node (Knotenpunkt)......................................................................................................13

5.32 Part (Bauteil, Komponente) ..........................................................................................13

5.33 Part master data (Stammdaten eines Bauteils)...........................................................13

5.34 Part list (Stückliste).......................................................................................................13

5.35 Part substitution (Bauteiltausch) .................................................................................13

5.36 Plug (Steckeraufnahme) ...............................................................................................13

5.37 Protection area (Geschützter Bereich) ........................................................................13

5.38 Schematic Design (Schaltplan) ....................................................................................13

5.39 Segment (Verbindungsabschnitt) ................................................................................13

5.40 Slot (Steckplatz) ............................................................................................................13

5.41 Special wire occurrence (Mehrdrahtleitung) ...............................................................13

5.42 System Design (Systemschaltplan) .............................................................................13

5.43 Terminal (Kontakt) ........................................................................................................14

5.44 Topology (3D Bauraum)................................................................................................14

5.45 Wire (Leitung)................................................................................................................14

5.46 Wire length (Leitungslänge) .........................................................................................14

5.47 Wire protection (Leitungsschutz).................................................................................14

6 DEFINITION OF THE KBL OBJECTS AND ATTRIBUTES...................................................14

6.1 Packages...........................................................................................................................15 6.1.1 harness and modules ..................................................................................................15 6.1.2 part master data ..........................................................................................................16 6.1.3 part structure ...............................................................................................................16 6.1.4 connectivity..................................................................................................................17

Page 5: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 5 of 69

Copyright: VDA

6.1.5 topology and routing ....................................................................................................17 6.1.6 foundation....................................................................................................................17

6.2 Object definitions .............................................................................................................18 6.2.1 Accessory....................................................................................................................18 6.2.2 Accessory_occurrence ................................................................................................19 6.2.3 Alias_identification.......................................................................................................19 6.2.4 Approval ......................................................................................................................20 6.2.5 Assembly_part.............................................................................................................20 6.2.6 Assembly_part_occurrence .........................................................................................21 6.2.7 B_spline_curve............................................................................................................21 6.2.8 Cartesian_point ...........................................................................................................22 6.2.9 Cavity ..........................................................................................................................22 6.2.10 Cavity_occurrence.......................................................................................................22 6.2.11 Cavity_plug..................................................................................................................22 6.2.12 Cavity_plug_occurrence ..............................................................................................23 6.2.13 Cavity_seal..................................................................................................................23 6.2.14 Cavity_seal_occurrence ..............................................................................................23 6.2.15 Change........................................................................................................................24 6.2.16 Co_pack_occurrence...................................................................................................24 6.2.17 Co_pack_part ..............................................................................................................25 6.2.18 Component..................................................................................................................25 6.2.19 Component_occurrence ..............................................................................................25 6.2.20 Connection ..................................................................................................................26 6.2.21 Connector_housing......................................................................................................27 6.2.22 Connector_occurrence ................................................................................................27 6.2.23 Contact_point ..............................................................................................................28 6.2.24 Core ............................................................................................................................29 6.2.25 Core_occurrence .........................................................................................................30 6.2.26 Creation.......................................................................................................................30 6.2.27 Cross_section_area.....................................................................................................30 6.2.28 Dimension_specification ..............................................................................................31 6.2.29 External_reference ......................................................................................................31 6.2.30 Extremity .....................................................................................................................32 6.2.31 Fixing...........................................................................................................................33 6.2.32 Fixing_assignment.......................................................................................................33 6.2.33 Fixing_occurrence .......................................................................................................33 6.2.34 General_terminal .........................................................................................................34 6.2.35 General_wire ...............................................................................................................34 6.2.36 General_wire_occurrence............................................................................................35 6.2.37 Harness.......................................................................................................................36 6.2.38 Harness_configuration.................................................................................................36 6.2.39 Installation_instruction .................................................................................................37 6.2.40 KBL_container .............................................................................................................37 6.2.41 Material........................................................................................................................37 6.2.42 Module.........................................................................................................................37 6.2.43 Module_configuration ..................................................................................................38 6.2.44 Module_family .............................................................................................................39 6.2.45 Node............................................................................................................................39 6.2.46 Numerical_value..........................................................................................................40 6.2.47 Part..............................................................................................................................40 6.2.48 Part_substitution..........................................................................................................41 6.2.49 Part_with_title_block....................................................................................................41 6.2.50 Processing_instruction.................................................................................................42 6.2.51 Protection_area ...........................................................................................................43 6.2.52 Routing........................................................................................................................43

Page 6: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 6 of 69

Copyright: VDA

6.2.53 Segment ......................................................................................................................44 6.2.54 Slot ..............................................................................................................................45 6.2.55 Slot_occurrence...........................................................................................................45 6.2.56 Special_terminal_occurrence.......................................................................................46 6.2.57 Special_wire_occurrence.............................................................................................46 6.2.58 Specified_accessory_occurrence ................................................................................47 6.2.59 Specified_cavity_plug_occurrence...............................................................................47 6.2.60 Specified_cavity_seal_occurrence...............................................................................47 6.2.61 Specified_co_pack_occurrence ...................................................................................48 6.2.62 Specified_component_occurrence...............................................................................48 6.2.63 Specified_connector_occurrence.................................................................................48 6.2.64 Specified_fixing_occurrence........................................................................................49 6.2.65 Specified_special_terminal_occurrence.......................................................................49 6.2.66 Specified_special_wire_occurrence.............................................................................49 6.2.67 Specified_terminal_occurrence....................................................................................49 6.2.68 Specified_wire_occurrence..........................................................................................50 6.2.69 Specified_wire_protection_occurrence ........................................................................50 6.2.70 Terminal_occurrence...................................................................................................50 6.2.71 Tolerance ....................................................................................................................50 6.2.72 Transformation ............................................................................................................51 6.2.73 Unit..............................................................................................................................51 6.2.74 Value_range ................................................................................................................52 6.2.75 Value_with_unit ...........................................................................................................52 6.2.76 Wire_colour .................................................................................................................52 6.2.77 Wire_length .................................................................................................................52 6.2.78 Wire_occurrence .........................................................................................................53 6.2.79 Wire_protection ...........................................................................................................53 6.2.80 Wire_protection_occurrence........................................................................................53 6.2.81 Wiring_group ...............................................................................................................54

7 KBL REFERENCE MODEL...................................................................................................55

8 XML REPRESENTATION OF THE HARNESS DESCRIPTION LIST....................................67

ANNEX A KBL XML SCHEMA.................................................................................................69

ANNEX B MAPPING TO ISO 10303-212 .................................................................................69

ANNEX C REFERENCES ........................................................................................................69

Page 7: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 7 of 69

Copyright: VDA

List of figures

Figure 1: Harness Design Process............................................................................................8

Figure 2: Scope of the KBL within the harness design process ...............................................10

Figure 3: High Level Planning Model.......................................................................................15

Figure 4: UML diagram 1: Common part attributes and properties ..........................................55

Figure 5: UML diagram 2: Part specializations ........................................................................56

Figure 6: UML diagram 3: Harness and modules ....................................................................56

Figure 7: UML diagram 4: Part master data ............................................................................57

Figure 8: UML diagram 5: Connection overview......................................................................58

Figure 9: UML diagram 6: Connectivity ...................................................................................59

Figure 10: UML diagram 7: Part usage list (1)...........................................................................59

Figure 11: UML diagram 8: Part usage list (2)...........................................................................60

Figure 12: UML diagram 9: Part usage list (3)...........................................................................60

Figure 13: UML diagram 10: Part usage list (4).........................................................................61

Figure 14: UML diagram 11: Part usage list (5).........................................................................62

Figure 15: UML diagram 12: Part usage list (6).........................................................................63

Figure 16: UML diagram 13: Topology and routing (1) ..............................................................64

Figure 17: UML diagram 14: Topology and routing (2) ..............................................................65

Figure 18: UML diagram 15: Dimensions ..................................................................................65

Figure 19: UML diagram 16: Miscellaneous ..............................................................................66

Figure 20: UML diagram 17: KBL_Container.............................................................................67

Figure 21: Example Mapping to the KBL XML Schema.............................................................68

Page 8: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 8 of 69

Copyright: VDA

1 Preamble

Innovations in automotive industry like adaptive cruise control or multi media passenger entertainment systems nowadays define themselves by electric and electronic components. As the electrical wiring system builds the essential infrastructure for automobile electronics, the wire harness becomes increasingly complex. This need for increased complexity comes along with the minimizing of design time and shortening of lead times.

Therefore the collaboration of car manufacturers and harness suppliers is a challenge. The traditional way that a supplier receives harness design data from the car manufacturer has to change. Instead of various drawings and lists in proprietary formats he needs a specification, which describes the wire harness in its entirety so that the manufacturer can plan the manufacturing and build the harness, based on the data he receives. Such a specification should be based on standards to fulfil the requirements for open development partnerships.

Source: © BMW AG

Figure 1: Harness Design Process

The objectives of the VDA Working Group “Car Electric” are the harmonization of requirements and the development of recommendations for the exchange of product data in the area of car electrical systems.

This recommendation is a result of the working group and has been developed with the participation of major OEMs and harness suppliers: The “Harness Description List”. This specification is also known under the name “KBL”, which stands for “Kabelbaumliste”, the German translation for “Harness Description List”.

The recommendation defines how harness design data coming from various sources like 3D CAD systems or CAE system can be represented in an aggregated view. It also describes how the international standard ISO 10303-212 “Electrical Design and Installation” [ISO10303] should be used for this purpose.

HarnessConcept

HarnessDesign

Harness Detailing

Functional Network (TA) System Layout &

Spec. Diagram System Circuit Diagram Service

Documentation

Harness Documentation

Electrical Data Base STEP AP 212 KBL

Page 9: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 9 of 69

Copyright: VDA

2 Goals of the recommendation

The goal of this recommendation is to specify the information that an OEM should make available on harness design for suppliers or other down-stream processes like EMC (Electro-magnetic compatibility).

The specification abstracts from OEM specific processes. By that it provides the basis for

- Reference standards for data quality

- Standardized viewing solutions

- Independency of harness data from proprietary software tools

- Simple comparability of development status and variants

- Standardized data exchange processes

It further avoids thereby the repeated development of engineering data.

3 Scope and responsibilities

The typical harness development process starts with the system design where the functionality of the new developed system will be described. The top level view gives the overview of all items needed. With wiring diagrams engineers start to define the parts needed to fulfil the expected functions. Components are selected according to the required specification and are documented in part lists. Connections are defined to combine the components logically. The first harness concept takes place, the position of the components and paths for wires are planned and described in wire lists and harness layouts. The netlist (connection list) can be used to start the harness routing.

This recommendation defines how electrical/logical data coming from CAE systems (usages of components, connections, etc.) and topological data coming from 3D CAD systems (routing of cables and bundles) should be represented in an integrated way:

- Part identification including versioning, references to car projects or supplier information

- Harness, variants and options

- Modules to support modular design

- Harness components like connectors, wires, fixings, grommets or accessories

- Connectivity lists

- Part usage lists

- Topology and routing

- References to drawings or manufacturing documents

Page 10: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 10 of 69

Copyright: VDA

HarnessDrawing

HarnessManufacturing

Harness

DigitalMock-Up

HarnessLayout

Mechanical CAD

SystemDiagram

ServiceDiagram

ElectricWiring

Diagram

PartList

ComponentLibraryConnection

List

Wire List•ideal length•position•segme ntation

Harness 2D Formboard 2,5DTopoloiy 3D

ModuleKonfiguration

ComponentLibraryKBL V2

HarnessDrawing

HarnessManufacturing

Harness

DigitalMock-Up

HarnessLayout

Mechanical CAD

SystemDiagram

ServiceDiagram

ElectricWiring

Diagram

PartList

ComponentLibraryConnection

List

Wire List•ideal length•position•segme ntation

Harness 2D Formboard 2,5DTopoloiy 3D

ModuleKonfiguration

ComponentLibraryKBL V2

Figure 2: Scope of the KBL within the harness design process

This recommendation is directed to the harness design and IT departments of the OEMs and to the harness suppliers. The target auditoriums are the persons responsible for data exchange, IT systems and implementers of interfaces.

4 Structure of the recommendation

This document is structured in the following chapters:

- Glossary of terms

- Definition of the objects and attributes

- Specification of the KBL information model

- XML representation of the Harness Description List: The KBL Schema

- Mapping of the KBL to ISO 10303-212

5 Glossary of terms

5.1 Accessory (Zubehör)

Components, which may be used with connectors to facilitate their use in a wide range of applications. Accessories perform no electrical function and include such items as caps, covers, gaskets washers and boots.

5.2 Alias part (Alternativ Sachnummer)

Used to describe the part number of the part in another company

My part number: my123, alias part: your_part123

Page 11: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 11 of 69

Copyright: VDA

5.3 Assembly part (Baugruppe)

An assembly of multiple parts identified by a common part number

5.4 Block Diagram (Blockschaltbild)

Top-level function view of a complex infrastructure

5.5 Bundle (Leitungsbündel)

Multiple wires or cables sharing the same route can be combined to a bundle. A bundle is normally bound together mechanically by tape.

5.6 Cavity (Kontaktkammer)

Location for the contact in the housing, housings can contain 1-n cavities. Cavities can be grouped to slots.

5.7 Cavity Plug (Blindstopfen)

Connector accessory to fill and seal empty cavities

5.8 Cavity Seal (Kontaktkammerdichtung)

Connector accessory to fill and seal a populated cavity

5.9 Cable (Leitung)

Multiple physical conductors (-> Cores) can be combined in a cable. Cables are available in various technologies like twisted-pair, shielded, coax, etc.

5.10 Cable Drawing (Kabelzeichnung)

2D view of a single cable

5.11 Circuit Diagram (Funktionszeichnung)

Diagram of functionality with all needed parts and their connections

5.12 Connection (Verbindung)

A connection specifies the electrical connectivity between two or more contacts.

5.13 Connection Diagram (Verbindungszeichnung)

Diagram with all connections, cables and bundles are shown with individual conductors.

5.14 Connector (Steckverbinder)

CONNECTORS are components, which terminate conductors for the purpose of providing connection and disconnection to a suitable mating component.

5.15 Connector housing (Steckergehäuse)

Body of the connector with 1-m slots containing 1-n cavities

5.16 Connector list (Steckerliste)

The tabular representation of a circuit diagram. The table shows all point to point connections and the connector pins.

Page 12: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 12 of 69

Copyright: VDA

5.17 Contact (Kontakt)

Active part of the connector, which connects electrical --- equal to “terminal”

5.18 Co pack part (Kabelbaumzubehör)

A part, which is supplied and installed together with the wiring harness, but without any electrical connection.

5.19 Core (Kabelader)

A core is part of a cable. A cable consists of 1-n cores

5.20 Extremity (Kabelende)

The endpoints of the wire or core.

5.21 Fixing (Kabelbefestigung)

Accessory part of the harness, used to fix the position.

5.22 Function Diagram (Funktionsplan)

Diagram that describes the functionality of a complex environment.

5.23 Harness (Kabelbaum)

The assembly of all wires and parts needed to connect the ECU’s, sensors, switches, and actuators. The extent of the harness depends on the car configuration. Harnesses can be defined as variants with individual part numbers for each configuration or as modular Harness (a brick box system) that can be configured by the specific selection of a set of modules.

5.24 Harness configuration (Kabelbaum variante)

A superset of all available functions (150%) is described in function diagram. The harness configuration describes the harness of useful car configurations.

5.25 Housing (Steckergehäuse)

Body of the connector

5.26 Form board (Formbrett)

2D representation of the 3D car topology; used in harness manufacturing

5.27 Module (Leitungsstrangmodul)

A defined set of parts (e.g. wires, connectors, … ), which is grouped to serve the connectivity for a certain range of functionality. A module is a brick stone of a modular Harness and has an individual part number.

Example: Option: Audio System with CD Changer

The module contains the harness and the harness accessories used to install and use this option.

5.28 Module configuration (Modulumfang)

The set of attributes and the parts list of an individual module..

Page 13: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 13 of 69

Copyright: VDA

5.29 Module family (Modulfamilie)

A group of modules that cover similar functionality, which may have a partially redundant module part list. The Module family exists for logistical reasons.

5.30 Netlist (Verbindungsliste)

List of all connections and connectors

5.31 Node (Knotenpunkt)

A named position that is of interest for the placement of equipment

5.32 Part (Bauteil, Komponente)

An object with a part number.

5.33 Part master data (Stammdaten eines Bauteils)

Database with the description of the part, metadata, datasheet, CAD drawings, etc.

5.34 Part list (Stückliste)

List of all parts used in the design

5.35 Part substitution (Bauteiltausch)

A mechanism that describes the replacement of a sealing plug with a terminal. Typically usage: an optional module is added to a harness and a common connector will be used.

5.36 Plug (Steckeraufnahme)

Opposite contact side of a connector or terminal

5.37 Protection area (Geschützter Bereich)

Area on a bundle where a protection element is attached. Some segments of a harness are crossing areas with critical conditions like higher temperatures, higher humidity, etc. To prevent the damage of the cable, protect shields are mounted for that segment.

5.38 Schematic Design (Schaltplan)

Graphical description of the functions, the configuration and the connections

5.39 Segment (Verbindungsabschnitt)

A topological subdivision of the harnesses route. By definition a wire can enter or leave a segment only on its start and end node. In-between there can be no change of the wire content.

5.40 Slot (Steckplatz)

A slot is a group of cavities within a connector housing, fitting to a mating housing or an electrical component

5.41 Special wire occurrence (Mehrdrahtleitung)

Mechanism to describe multi core cables in a module part list.

5.42 System Design (Systemschaltplan)

Top-level view of a complex environment

Page 14: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 14 of 69

Copyright: VDA

5.43 Terminal (Kontakt)

Active part of the connector, which connects electrical --- equal to “contact”

5.44 Topology (3D Bauraum)

Abstraction from the harnesses 3D geometry into nodes and segments to transform the complex 3D shape of the harness e.g. into an outstretched 2D view, a data model for routing calculation or for other purposes.

5.45 Wire (Leitung)

A solid or stranded group of solid cylindrical conductors, together with any associated insulation.

5.46 Wire length (Leitungslänge)

Wire attribute, which describes the length of the wire

5.47 Wire protection (Leitungsschutz)

Shield to prevent the wire bundle from damage.

6 Definition of the KBL objects and attributes

This section specifies the information required for harness design processes. The information requirements are specified as a set of packages and class definitions.

Figure 3 shows the planning model for the Harness Description List. It provides a high level overview of the information supported.

Page 15: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 15 of 69

Copyright: VDA

Figure 3: High Level Planning Model

6.1 Packages

The classes of the KBL Information Model are grouped into logical packages. The packages are as follows:

- harness and modules

- part master data

- part structure

- connectivity

- topology and routing

- foundation

6.1.1 harness and modules

This package specifies the information needed to describe the exchange context, i.e. the harness with its decomposition into modules. It also includes the information needed to build variants and control the individual components with respect to options and logistic control information.

The following classes are used by the harness and modules package:

- Harness

- Harness_configuration

Harness

Part

has

Connector

Cavity

is a

has

Connection

has

connects

Routing

routes

Module/Configuration

has

controls Segment

goes through

Page 16: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 16 of 69

Copyright: VDA

- KBL_container

- Module

- Module_configuration

- Module_family

6.1.2 part master data

This package specifies the part master information of the harness components. It defines the attributes necessary to provide further information on parts like wires or accessories. It further provides the capability to describe the information, which is common to all kind of parts. This includes basic attributes like part number or mass and also more complex descriptions like material or change information.

The following classes are used by the part master data package:

- Accessory

- Assembly_part

- Cavity

- Cavity_plug

- Cavity_seal

- Co_pack_part

- Component

- Connector_housing

- Core

- Fixing

- General_terminal

- General_wire

- Part

- Part_with_title_block

- Slot

- Wire_protection

6.1.3 part structure

This package provides the information typically contained in bill of material lists. It describes how a harness is assembled.

The following classes are used by the part structure package:

- Accessory_occurrence

- Assembly_part_occurrence

- Cavity_plug_occurrence

- Cavity_seal_occurrence

- Co_pack_occurrence

- Component_occurrence

- Connector_occurrence

- Core_occurrence

Page 17: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 17 of 69

Copyright: VDA

- Fixing_occurrence

- General_wire_occurrence

- Part_substitution

- Special_terminal_occurrence

- Specified_accessory_occurrence

- Specified_cavity_plug_occurrence

- Specified_co_pack_occurrence

- Specified_component_occurrence

- Specified_fixing_occurrence

- Specified_special_terminal_occurrence

- Specified_terminal_occurrence

- Specified_wire_occurrence

- Terminal_occurrence

- Wire_occurrence

- Wire_protection_occurrence

6.1.4 connectivity

This concept specifies the concepts required to specify the connectivity among the connectors within a harness. The specification of contact points and wiring groups are included.

The following classes are used by the connectivity package:

- Cavity_occurrence

- Connection

- Contact_point

- Extremity

- Slot_occurrence

- Wiring_group

6.1.5 topology and routing

This package specifies the information contained in harness layouts and drawings. This includes the geometric description of bundles and the information how a specific wire is routed.

The following classes are used by the topology and routing package:

- Dimension_specification

- Fixing_assignment

- Node

- Protection_area

- Routing

- Segment

- Tolerance

6.1.6 foundation

Page 18: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 18 of 69

Copyright: VDA

This packages contains the basic classes for the KBL like numerical values, units, materials and also more complex descriptions like change information.

The following objects are used by the miscellaneous section:

- Alias_identification

- Approval

- B_spline_curve

- Cartesian_point

- Change

- Creation

- Cross_section_area

- External_reference

- Installation_instruction

- Material

- Numerical_value

- Processing_instruction

- Transformation

- Unit

- Value_range

- Value_with_unit

- Wire_colour

- Wire_length

6.2 Object definitions

This section specifies the objects of the KBL. For each object a textual definition is given. Where appropriate additional notes and examples are provided to support the understanding of the definition. The description of each object also lists the attributes of an object and their description.

6.2.1 Accessory

An Accessory is any supplementary portion of a connector with the obligation to help a Harness to perform its function: Components, which may be used with connectors to facilitate their use in a wide range of applications. Accessories perform no electrical function and include such items as caps, covers, gaskets washers and boots.

Example: An Accessory may be a sleeve, a cap, a cable strap or comparable parts, which are installed to a plug.

An Accessory is a type of Part.

The data associated with an Accessory are the following:

- accessory_type

6.2.1.1 accessory_type

The accessory_type specifies the type of an Accessory.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Page 19: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 19 of 69

Copyright: VDA

6.2.2 Accessory_occurrence

An Accessory_occurrence is the occurrence of an Accessory in a module part list.

The data associated with an Accessory_occurrence are the following:

- alias_id

- description

- id

- installation_information

- part

- placement

- reference_element

6.2.2.1 alias_id

The alias_id specifies additional identifiers for the Accessory_occurrence.

6.2.2.2 description

The description specifies additional information about the object.

6.2.2.3 id

The id specifies the identifier of the Accessory_occurrence.

6.2.2.4 installation_information

The installation_information provides additional information for the installation of the Accessory_occurrence.

6.2.2.5 part

The part specifies the Accessory that serves as a definition for this particular occurrence.

6.2.2.6 placement

The placement specifies the transformation information, which is used to locate and orient the occurrence in the car coordinate system. For further information see [CESAK].

6.2.2.7 reference_element

The reference_element specifies the Connector_occurrence objects supplemented by the Accessory_occurrence.

6.2.3 Alias_identification

An Alias_identification is a mechanism to associate an object with an additional identifier that is used to identify the object of interest in a different context, either in another Organization, or in some other context. The scope of the Alias_identification shall be specified by the attributes 'Scope' and/or by the attribute 'Description'.

The data associated with an Alias_identification are the following:

- alias_id

- description

- scope

6.2.3.1 alias_id

The alias_id specifies the identifier used in the context specified by scope and description.

Page 20: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 20 of 69

Copyright: VDA

6.2.3.2 description

The description specifies the type of the Alias_identification.

Example: The description may be, e.g., 'inventory number'.

6.2.3.3 scope

The scope specifies the organization in which the Alias_identification is valid.

6.2.4 Approval

An Approval is a judgment concerning the quality of those modules or harnesses that are subject of the Approval. An Approval represents a statement made by technical personnel or management personnel whether certain requirements are met. The absence of approval information does not imply any approval status by default.

The data associated with an Approval are the following:

- date

- department

- is_applied_to

- name

- type_of_approval

6.2.4.1 date

The date specifies the date when the Approval actually became valid.

6.2.4.2 department

The department specifies the department name of the personnel responsible for the Approval.

6.2.4.3 is_applied_to

The is_applied_to specifies the objects to which the Approval is assigned.

A particular Approval shall be applied to at least one object.

6.2.4.4 name

The name specifies the name of the personnel responsible for the Approval

6.2.4.5 type_of_approval

The type_of_approval specifies the terms characterizing the Approval.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.5 Assembly_part

An Assembly_part is a component that contains other subordinate objects: An assembly of multiple parts identified by a common part number. An Assembly_part is ordered as a part to be bought under a part number, due to limited functionalities of the CAD systems these must be described however with several individual parts.

An Assembly_part is a type of Part.

The data associated with an Assembly_part are the following:

- components

- part_type

6.2.5.1 components

The components specifies the Parts of which the Assembly_part consists.

Page 21: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 21 of 69

Copyright: VDA

6.2.5.2 part_type

The part_type specifies the type of an Assembly_part.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.6 Assembly_part_occurrence

An Assembly_part_occurrence is the occurrence of an Assembly_part in a module part list.

The data associated with an Assembly_part_occurrence are the following:

- alias_id

- description

- id

- installation_information

- part

- placement

6.2.6.1 alias_id

The alias_id specifies additional identifiers for the Assembly_part_occurrence.

6.2.6.2 description

The description specifies additional information about the object.

6.2.6.3 id

The id specifies the identifier of the Assembly_part_occurrence.

6.2.6.4 installation_information

The installation_information provides additional information for the installation of the Connection.

6.2.6.5 part

The part specifies the Assembly_part that serves as a definition for this particular occurrence.

6.2.6.6 placement

The placement specifies the transformation information, which is used to locate and orient the occurrence in the car coordinate system. For further information see [CESAK].

6.2.7 B_spline_curve

A B-spline curve is a piecewise parametric polynomial or rational curve described in terms of control points and basis functions. The B-spline curve has been selected as the most stable format to represent all types of polynomial or rational parametric curves. With appropriate attribute values it is capable of representing single span or spline curves of explicit polynomial, rational, Bezier or B-spline type.

Within the Harness Engineering Information Model the definition has been restricted to a uniform B_spline_curve, where the knots are evenly spaced. Suitable default values for the knots and knot multiplicities are derived in this case. A B-spline is uniform if and only if all knots are of multiplicity 1 and they differ by a positive constant from the preceding knot. In this case the knot spacing is 1.0, starting at -d, where d is the degree.

Note: If the B-spline curve is uniform and degree=1, the B-spline is equivalent to a polyline.

The data associated with a B_spline_curve are the following:

Page 22: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 22 of 69

Copyright: VDA

- control_points

- degree

6.2.7.1 control_points

The list of control points for the curve.

The list shall contain at least 2 elements.

6.2.7.2 degree

The algebraic degree of the basis functions.

6.2.8 Cartesian_point

A Cartesian_point is a point that is defined by its coordinates in a rectangular Cartesian coordinate system.

The data associated with a Cartesian_point is the following:

- coordinates

6.2.8.1 coordinates

The coordinates specify the coordinates of the Cartesian_point. The third coordinate will not exist in the case of a two-dimensional point.

6.2.9 Cavity

A cavity is a defined space in a housing for location of an electrical terminal, or an electrical terminal and seal, or a cavity plug (can be empty).

The data associated with a Cavity are the following:

- cavity_number

6.2.9.1 cavity_number

The cavity_number specifies the identifier of the Cavity.

Note: The uniqueness of a cavity id within a harness is fulfilled by the concatenation of the connector id, the slot id, and the cavity id.

6.2.10 Cavity_occurrence

A Cavity_occurrence is the occurrence of a Cavity in the context of a connector_occurrence.

The data associated with a Cavity are the following:

- associated_plug

- part

6.2.10.1 associated_plug

The associated_plug specifies the plug the cavity is equipped with.

6.2.10.2 part

The part specifies the Cavity that serves as a definition for this particular occurrence.

6.2.11 Cavity_plug

A Cavity_plug is a watertight non-electrical object to fill and seal an empty cavity.

A Cavity_plug is a type of Part.

The data associated with a Cavity_plug are the following:

Page 23: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 23 of 69

Copyright: VDA

- colour

- plug_type

6.2.11.1 colour

The colour specifies the colour of the Cavity_plug.

6.2.11.2 plug_type

The plug_type specifies the type of a Cavity_plug.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.12 Cavity_plug_occurrence

A Cavity_plug_occurrence is the occurrence of a Cavity_plug in a module part list.

Note: Cavity_plugs do not show up in a module bill of material.

The data associated with a Cavity_plug_occurrence are the following:

- part

6.2.12.1 part

The part specifies the Cavity_plug that serves as a definition for this particular occurrence.

6.2.13 Cavity_seal

A Cavity_seal is a watertight non-electrical object to fill and seal a populated Cavity.

A Cavity_seal is a type of Part.

The data associated with a Cavity_seal are the following:

- colour

- seal_type

- wire_size

6.2.13.1 colour

The colour specifies the colour of the Cavity_seal.

6.2.13.2 seal_type

The seal_type specifies the type of a Cavity_seal.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.13.3 wire_size

The wire_size specifies the size range of the wires the seal fits.

6.2.14 Cavity_seal_occurrence

A Cavity_seal_occurrence is the occurrence of a Cavity_seal in a module.

Note: The number of occurrences used in a specific module or harness can be calculated by the individual occurrences.

Note: The Part_usage object specifies the usage of a Cavity_seal_occurrence for a particular Cavity.

The data associated with a Cavity_seal_occurrence are the following:

- part

Page 24: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 24 of 69

Copyright: VDA

6.2.14.1 part

The part specifies the Cavity_seal that serves as a definition for this particular occurrence.

6.2.15 Change

A Change is a mechanism to keep track of the change history. The set of changes assigned to a Part covers all modification numbers up to the last modification level of the version of the Part.

The data associated with a Change are the following:

- approver_department

- approver_name

- change_date

- change_request

- description

- designer_department

- id

- responsible_designer

6.2.15.1 approver_department

The approver_department specifies the department of the personnel who approved the Part.

6.2.15.2 approver_name

The approver_name specifies the name of the personnel who approved the Part.

6.2.15.3 change_date

The change_date specifies the date the change was performed.

6.2.15.4 change_request

The change_request specifies the activity, which triggers one or more changes.

Example: Change request, AEKO, VV; “Modellpflegepunkt”

6.2.15.5 description

The description specifies additional information about the change.

6.2.15.6 designer_department

The designer_department specifies the department of the responsible design engineer.

6.2.15.7 id

The id specifies the identifier by which a certain change can be referenced.

Example: Reference of a fax, note, etc.

6.2.15.8 responsible_designer

The responsible_designer specifies the responsible design engineer.

6.2.16 Co_pack_occurrence

A Co_pack_occurrence is the occurrence of a Co_pack_part in a module part list.

The data associated with a Co_pack_occurrence are the following:

- alias_id

Page 25: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 25 of 69

Copyright: VDA

- description

- id

- installation_information

- part

6.2.16.1 alias_id

The alias_id specifies additional identifiers for the Co_pack_occurrence.

6.2.16.2 description

The description specifies additional information about the object.

6.2.16.3 id

The id specifies the identifier of the Co_pack_occurrence.

6.2.16.4 installation_information

The installation_information provides additional information for the installation of the Co_pack_occurrence.

6.2.16.5 part

The part specifies the Co_pack_part that serves as a definition for this particular occurrence.

6.2.17 Co_pack_part

A Co_pack_part is a Part, which is supplied and installed with the wiring harness, but without any electrical or mechanical connection.

The data associated with a Co_pack_part are the following:

- part_type

6.2.17.1 part_type

The part_type specifies the type of a Co_pack_part.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.18 Component

A Component is an object, which belongs to the harness.

Example: Fuse, fusebox, relay sockets

6.2.19 Component_occurrence

A Component_occurrence is the occurrence of a Component in a module part list.

The data associated with a Co_pack_occurrence are the following:

- alias_id

- description

- id

- mounting

- part

6.2.19.1 alias_id

The alias_id specifies additional identifiers for the Component_occurrence.

Page 26: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 26 of 69

Copyright: VDA

6.2.19.2 description

The description specifies additional information about the object.

6.2.19.3 id

The id specifies the identifier of the Component_occurrence.

6.2.19.4 mounting

The mounting specifies the Cavity_occurrence, Slot_occurrence, or Connector_occurrence, which is associated with the Component_occurrence.

6.2.19.5 part

The part specifies the Component_occurrence that serves as a definition for this particular occurrence.

6.2.20 Connection

A Connection is a mechanism to specify the electrical connectivity between two or more contact points.

The data associated with a Connection are the following:

- description

- external_reference

- extremities

- id

- installation_information

- processing_information

- signal_name

- wire

6.2.20.1 description

The description specifies additional information about the object.

6.2.20.2 External_reference

The external_references specifies references to documents.

Example: Schematic diagram for the connection.

6.2.20.3 extremities

The extremities specify Extremity objects, which reference the Contact_points connected by this Connection.

Note: There shall be at least two objects specified.

6.2.20.4 id

The id specifies the identifier of the Connectivity. The values are company specific. They can depend also on wire parameters.

Example: Electrical potential, start->destination

6.2.20.5 installation_information

The installation_information provides additional information for the installation of the Connection.

6.2.20.6 processing_information

Page 27: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 27 of 69

Copyright: VDA

The processing_information provides additional information for the processing of the Connection.

6.2.20.7 signal_name

The signal_name specifies logical information on a Connection.

Example: Packet on a bus, analogue voltage (high/low, waved) on a wire

6.2.20.8 wire

The wire specifies the Wire_occurrence or Core_occurrence, which realizes the Connection.

6.2.21 Connector_housing

A Connector_housing is a non-populated connector, i.e. without addressed/populated cavities. I.e., a body of the connector with 1-n cavities.

Note: A Connector_housing without any slot allows for the representation of a connector shell.

The data associated with a Connector_housing are the following:

- housing_code

- housing_colour

- housing_type

- slots

6.2.21.1 housing_code

The housing_code specifies a coding for the type of the Connector_housing.

6.2.21.2 housing_colour

The housing_colour specifies the colour of the Connector_housing.

6.2.21.3 housing_type

The housing_type specifies the type of a Connector_housing.

Example: Family series type like ‘MQS2.8’

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.21.4 slots

The slots specifies the Slots which belong to the Connector_housing.

6.2.22 Connector_occurrence

A Connector_occurrence is the occurrence of a Connector_housing in a module part list.

The data associated with a Connector_occurrence are the following:

- alias_id

- contact_points

- description

- id

- installation_information

- part

- placement

- reference_element

Page 28: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 28 of 69

Copyright: VDA

- slots

- usage

6.2.22.1 alias_id

The alias_id specifies additional identifiers for the Connector_occurrence.

6.2.22.2 Contact_points

The contact_points specify the Contact_points, which belong to the connector.

Note: All Contact_points of a Connector_occurrence shall reference Cavity_occurrence objects of this Connector_occurrence.

6.2.22.3 description

The description specifies additional information about the object.

6.2.22.4 id

The id specifies the identifier of the Connector_occurrence.

6.2.22.5 installation_information

The installation_information provides additional information for the installation of the Connector_occurrence.

6.2.22.6 part

The part specifies the Connector_housing that serves as a definition for this particular occurrence.

6.2.22.7 placement

The placement specifies the transformation information, which is used to locate and orient the occurrence in the car coordinate system. According to the CES definition, the reference point is pin 1. For further information see [CESAK].

6.2.22.8 Reference_element

The reference_element specifies further Connector_occurrence objects supplemented by the Connector_occurrence.

6.2.22.9 Slots

The slots specifies the Slot_occurrence objects which belong to the Connector_occurrence.

6.2.22.10 usage

The usage specifies how a Connector_housing shall be interpreted under certain conditions. For “normal” housings the usage attribute shall not be specified.

Where applicable the following values shall be used:

- ‘no end’: end of wire without any connector (“blunt cut”)

- 'ring terminal’:

- ‘splice’:

- ‘dangler’: terminal without any connector housing

6.2.23 Contact_point

A Contact_point defines the positions where electrical connectivity takes place.

The data associated with a Contact_point are the following:

- associated_parts

Page 29: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 29 of 69

Copyright: VDA

- contacted_cavity

- id

6.2.23.1 associated_parts

The associated_parts specifies the Cavity_seal_occurrences, Special_terminal_occurrences, or Terminal_occurrences associated with the Contact_point.

6.2.23.2 contacted_cavity

The contacted_cavity specifies the Cavity_objects related with the Contact_point.

6.2.23.3 id

The id specifies the identifier of the Contact_point.

6.2.24 Core

A Core is a single conductor of a multi-core wire including its insulation. A core is part of a cable. A cable consists of 1-n cores.

The data associated with a Core are the following:

- bend_radius

- cable_designator

- core_colour

- cross_section_area

- id

- outside_diameter

- wire_type

6.2.24.1 bend_radius

The bend_radius specifies the bend radius of a core.

6.2.24.2 cable_designator

The cable_designator specifies additional information to refer to a Core.

6.2.24.3 core_colour

The Core_colour specifies the Wire_colour objects of the core.

There shall be at least one element.

6.2.24.4 cross_section_area

The cross_section_area specifies the electrical cross section of the Core.

6.2.24.5 id

The id specifies the identifier of the Core.

6.2.24.6 outside_diameter

The outside_diameter specifies the outer width of the Core.

6.2.24.7 wire_type

The wire_type specifies the type of a Core.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Page 30: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 30 of 69

Copyright: VDA

Example: ‘protected wire’, ‘flat band’.

6.2.25 Core_occurrence

A Core_occurrence is the occurrence of a Core within a Special_wire_occurrence.

The data associated with a Core_occurrence are the following:

- length_information

- part

- wire_number

6.2.25.1 length_information

The length_information specifies the length of a Core_occurrence. For a core, as many Wire_length objects as required may be defined. There are two pre-defined types:

- DMU: By CAD model calculated wire length. Usually it is the Sum of the lengths of neutral fibers of the bundle sections, normally too short.

- Manufacturing: determination by means of correction algorithms or measurement of the prototype.

6.2.25.2 part

The part specifies the Core that serves as a definition for this particular occurrence.

6.2.25.3 wire_number

The wire_number specifies the identification of a wire. This number is unique within a vehicle and usually automatically generated (dependent on "from- to" information).

Note: Each interior conductor of a multi-core wire produces an own wire number.

6.2.26 Creation

A Creation assigns creation information to a Module or Harness.

The data associated with a Creation are the following:

- date

- department

- is_applied_to

- name

6.2.26.1 date

The date specifies the creation date.

6.2.26.2 department

The department specifies the department the creator belongs to.

6.2.26.3 is_applied_to

The is_applied_to specifies the harness or module objects to which the Creation is assigned.

A Creation shall be applied to at least one object.

6.2.26.4 name

The name specifies the name of the creator.

6.2.27 Cross_section_area

Page 31: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 31 of 69

Copyright: VDA

A Cross_section_area provides information about the value and the interpretation of a cross section.

The data associated with a Creation are the following:

- area

- value_determination

6.2.27.1 area

The area specifies the value of the Cross_section_area.

6.2.27.2 value_determination

The value_determination specifies information on how the cross_section_area value shall be interpreted.

6.2.27.3 name

The name specifies the name of the creator.

6.2.28 Dimension_specification

A Dimension_specification is the definition of the distance between two elements.

The data associated with a Creation are the following:

- origin

- target

- tolerance_indication

6.2.28.1 origin

The origin specifies the Node or the located component that is the origin for the Dimension_specification.

6.2.28.2 target

The target specifies the Node or the located component that is the target for the Dimension_specification.

6.2.28.3 Tolerance_indication

The tolerance_indication specifies the value of the distance between the two elements.

6.2.29 External_reference

An External_reference is a mechanism to provide information about the documents associated with the Part.

Example: 3D model, form board drawings, etc.

The data associated with an External_reference are the following:

- change_level

- creating_system

- data_format

- document_number

- document_type

- file_name

- location

Page 32: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 32 of 69

Copyright: VDA

6.2.29.1 change_level

The change_level specifies the version of the document.

6.2.29.2 creating_system

The creating_system specifies the computer application or the machine, which is used to create the document.

6.2.29.3 data_format

The data_format specifies the convention that was used to structure the information in the document.

6.2.29.4 document_number

The document_number specifies the identifier of the document.

6.2.29.5 document_type

The document_type specifies the kind of the document.

Where applicable the following values shall be used:

- 3D-Data set (wiring, construction unit)

- 2D-Data set (cable design, symbol, plug face)

- cable connection diagram

- set of cables database (VW: LCS-Container)

- specification of set of cables

- standards, technical guidelines

6.2.29.6 file_name

The file_name specifies the name, which is used to locate the file either on a computer system or in a repository of paper documents.

6.2.29.7 location

The location specifies where a document can be found in a digital or physical data storage system.

6.2.30 Extremity

The Extremity specifies the Contact_point, which is connected by a specific Connection.

The data associated with an extremity are the following:

- contact_point

- position_on_wire

6.2.30.1 contact_point

The contact_point specifies the Contact_point, which is associated with the Extremity, and by this with the connection.

6.2.30.2 position_on_wire

The Position_on_wire describes the position where the contacting takes place. That is important for contacts like IDC, where the contacting is not at the beginning or end of the wire.

Note: A value of 0.0 designates the beginning of the wire, a value of 1.0 the end. Intermediate contact_points are defined relative to the first one by a value between 0.0 and 1.0.

The position_on_wire defines the ordering of the Extremities within a Connection.

Page 33: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 33 of 69

Copyright: VDA

6.2.31 Fixing

A Fixing is an accessory part of the harness, used to fix the position. Fixing elements cover all parts that are used in cable section.

Example: clips, sleeves, cable ducts, grommet, etc.

The data associated with a Fixing are the following:

- fixing_type

6.2.31.1 fixing_type

The fixing_type specifies the type of a Fixing.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Example: Examples are ‘fastening part’, ‘channel’, ‘sleeve’, ‘shaft’, ‘conduct’, ‘pine-tree’

6.2.32 Fixing_assignment

A Fixing_assignment assigns a Fixing_occurrence or an Accessory_occurrence to a Segment.

The data associated with a Fixing_assignment are the following:

- fixing

- location

- orientation

6.2.32.1 fixing

The fixing specifies the Fixing_occurrence or the Accessory_occurrence, which is assigned.

6.2.32.2 location

The location specifies the position of the fixing on the Segment. The value is given in curve parameters running from 0.0 to 1.0.

6.2.32.3 orientation

The orientation specifies the direction of the z-axis and is given by 2 or 3 values. The y-axis is defined by the tangent of the center curve at the location.

6.2.33 Fixing_occurrence

A Fixing_occurrence is the occurrence of a Fixing in a module part list.

The data associated with a Fixing_occurrence are the following:

- alias_id

- description

- id

- installation_information

- part

- placement

6.2.33.1 alias_id

The alias_id specifies additional identifiers for the Fixing_occurrence.

6.2.33.2 description

The description specifies additional information about the object.

Page 34: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 34 of 69

Copyright: VDA

6.2.33.3 id

The id specifies the identifier of the Fixing_occurrence.

6.2.33.4 installation_information

The installation_information provides additional information for the installation of the Fixing_occurrence.

6.2.33.5 part

The part specifies the Fixing that serves as a definition for this particular occurrence.

6.2.33.6 placement

The placement specifies the transformation information, which is used to locate and orient the occurrence in the car coordinate system. For further information see [CESAK].

6.2.34 General_terminal

A General_terminal is a device designed to terminate a conductor. That covers any type of terminal: those that fit to a cavity in a slot of a Connector_housing and those that are affixed directly to a post, stud, chassis, or other conductor or the like in order to establish electrical connection.

Note: A General_terminal describes the active part of the connector, which connects electrical, equal to "contact".

The data associated with a General_terminal are the following:

- cross_section_area

- outside_diameter

- plating_material

- terminal_type

6.2.34.1 cross_section_area

The cross_section_area specifies the electrical cross section, which can be accommodated by the General_terminal.

6.2.34.2 outside_diameter

The outside_diameter specifies the outer width of the isolation, which can be accommodated by the General_terminal.

6.2.34.3 plating_material

The plating_material specifies the overlaying of a thin coating of metal on components to improve conductivity, provide for easy soldering or prevent rusting or corrosion.

6.2.34.4 terminal_type

The terminal_type specifies the type of a General_terminal.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Example: ‘Pin’, ‘Blade’, ‘male’, ‘female’, ‘grease’, ‘FL - flat contact’, ‘KK - box contact’, ‘SK - ring wire’, ‘RK - ring lug’, ‘KS - lug’, ‘BK - battery clamp’, ‘OL - open line end of frame’, ‘SP - splice’, ‘MK - multiple contact’

6.2.35 General_wire

A General_wire is a physical wire, performing electrical connection. A General_wire can either be used to define a single wire or a multi-core wire.

Page 35: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 35 of 69

Copyright: VDA

The data associated with a General_wire are the following:

- bend_radius

- cable_designator

- core

- cover_colour

- cross_section_area

- outside_diameter

- wire_type

6.2.35.1 bend_radius

The bend_radius specifies the bend radius of a wire.

6.2.35.2 cable_designator

The cable_designator specifies additional information to refer to a General_wire.

6.2.35.3 core

The core specifies the constituents of the multi-core wire.

6.2.35.4 cover_colour

The cover_colour specifies the Wire_colour objects of a General_wire. In the case of a single wire it specifies the colour of the conductor. In case of a multi-core wire it specifies the colour of the cover.

6.2.35.5 cross_section_area

The cross_section_area specifies the electrical cross section of the General_wire.

6.2.35.6 outside_diameter

The outside_diameter specifies the outer width of the General_wire.

6.2.35.7 wire_type

The wire_type specifies the type of a General_wire.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Example: ‘individual wire’, ‘multi-core wire’, ‘protected wire’, ‘flat band’.

6.2.36 General_wire_occurrence

A General_wire_occurrence is the occurrence of a Wire_occurrence or a Special_wire_occurrence in a module part list.

The data associated with a General_wire_occurrence are the following:

- installation_information

- length_information

- part

6.2.36.1 installation_information

The installation_information provides additional information for the installation of the Connection.

6.2.36.2 length_information

Page 36: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 36 of 69

Copyright: VDA

The length_information specifies the length of a General_wire_occurrence. For a wire, as many Wire_length objects as required may be defined. There are two pre-defined types:

- DMU: By CAD model calculated wire length. Usually it is the Sum of the lengths of neutral fibers of the bundle sections, normally too short.

- Manufacturing: determination by means of correction algorithms or measurement of the prototype.

There shall be at least one Wire_length of type DMU be defined for each wire.

6.2.36.3 part

The part specifies the General_wire that serves as a definition for this particular occurrence.

6.2.37 Harness

All wires in the car need to connect the ECU's, sensors, switches, and actuators. The harness depends on the car configuration. A Harness is an assembly of insulated conductors formed to a predetermined pattern or configuration.

A Harness is a type of Part_with_title_block.

The data associated with a Harness are the following:

- components

- content

- harness_configuration

- module

- module_configuration

6.2.37.1 components

The components specifies the part occurrences and connections which belong to the Harness.

6.2.37.2 content

The content specifies the information covered by the Harness.

The following values shall be used:

- ‘harness complete set’

- ‘harness subset’

6.2.37.3 harness_configuration

The harness_configuration specifies the configurations of the Harness.

6.2.37.4 module

The modules specifies the modules belonging to the harness.

Note: NOTE A Module belongs to one harness, only. This is no restriction, as there can be only one harness object exchanged by one file.

6.2.37.5 module_configuration

The module_configuration specifies the direct control of components outside of modules.

6.2.38 Harness_configuration

A superset of all available functions (150%) is described in function diagram. The harness configuration describes the harness of useful car configurations. A Harness_configuration is a variant of a harness.

Page 37: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 37 of 69

Copyright: VDA

The data associated with a Harness_configuration are the following:

- logistic_control_information

- modules

6.2.38.1 logistic_control_information

The logistic_control_information specifies the calculated combination of the configuration codes reflecting customer, market or country requirements associated with a Harness_configuration.

Example: ‘LOL/LOR+CFL’

6.2.38.2 modules

The modules specify the Module objects, which build up the Harness_configuration.

6.2.39 Installation_instruction

An Installation_instruction is the description of the methods that can be used to install a Part.

The data associated with an Installation_instruction are the following:

- installation_type

- installation_value

6.2.39.1 installation_type

The installation_type specifies the kind of the Installation_instruction.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.39.2 installation_value

The installation_value specifies the value for the kind of the Installation_instruction defined by installation_type.

6.2.40 KBL_container

The KBL_container is introduced to specify the information, which can be exchanged by one file.

6.2.41 Material

A Material is the substance out of which a Part is or can be made.

The data associated with a Material are the following:

- material_key

- material_reference_system

6.2.41.1 material_key

The material_key specifies a code by which the material can be identified.

6.2.41.2 material_reference_system

The material_reference_system specifies the system in which the material_key and its meaning is defined.

Example: ‘IMDS’ for the International Material Database System.

6.2.42 Module

A Module is a physical part of harness electrically defined by one or more module groups including required harness furniture.

Page 38: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 38 of 69

Copyright: VDA

A Module is a type of Part_with_title_block.

The data associated with a Module are the following:

- content

- Module_configuration

- of_family

- of_harness

6.2.42.1 content

The content specifies the information covered by the Module.

The following values shall be used:

- ‘variant’

- ‘module’

6.2.42.2 module_configuration

The module_configuration specifies the Module_configuration the Module represents.

6.2.42.3 of_family

The of_family specifies the Module_family to which the Module belongs.

6.2.43 Module_configuration

Module_configuration is a grouping of wires and components fulfilling a specific functionality of a harness.

Example: Option: Audio System with CD Changer

The data associated with a Module_configuration are the following:

- configuration_type

- controlled_components

- logistic_control_information

6.2.43.1 configuration_type

The configuration_type specifies further information on the type of the logistic_control_information.

Note: NOTE To control completion parts, which are only used if a specific combination of modules, occur, a Module_configuration can be used with a logistic_control_information containing the Boolean expression for the combination and a configuration_type ‘module list’.

Where applicable the following values shall be used:

- ‘option code’: the logistic_control_information contains configuration codes reflecting customer, market or country requirements

- ‘module list’: the logistic_control_information contains a list of modules, to which a completion part controlled by the Module_configuration belongs to

6.2.43.2 controlled_components

The controlled_components specifies the components, which are grouped by the Module_configuration.

6.2.43.3 logistic_control_information

The logistic_control_information specifies the calculated combination of the configuration codes reflecting customer, market or country requirements, or a list of modules associated with a Module_configuration. The meaning of the string is further described by the configuration_type.

Page 39: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 39 of 69

Copyright: VDA

Example: ‘LOL/LOR+CFL’

6.2.44 Module_family

A Module_family is a mechanism to group mutually exclusive modules.

Example: ‘audio equipment’

The data associated with a Module_family are the following:

- description

- id

6.2.44.1 description

The description specifies additional information about the Module_family.

6.2.44.2 id

The id specifies the identifier of the Module_family.

6.2.45 Node

A node forms begin and end of a Segment.

The data associated with a Node are the following:

- alias_id

- bend_radius

- cartesian_point

- id

- processing_information

- referenced_components

6.2.45.1 alias_id

The alias_id specifies additional identifiers for the Node.

Example: Node Ids may vary from one CAD system export to another. Therefore the CAD system Id is improper for Id attribute. Id shall have a value, which is unique within the harness. Alias_id may be used for the CAD system Id.

6.2.45.2 bend_radius

The bend_radius specifies the maximum bend radius at the Node.

Example: May be used for the routing of fiber optics.

6.2.45.3 cartesian_point

The cartesian_point specifies the position of the Node with respect to the absolute car coordinate system.

6.2.45.4 id

The id specifies the identifier of the Node.

6.2.45.5 processing_information

The processing_information provides additional information for the processing of the Node.

6.2.45.6 referenced_components

Page 40: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 40 of 69

Copyright: VDA

The referenced_components specifies the Accessory_occurrences, Assembly_part_occurrences, Connector_occurrences, Fixing_occurrences, Special_terminal_occurrences, and Wire_protection_occurrences located at the node.

Note: NOTE Different elements can lead to a node, e.g. plug, Splice, perhaps clip.

6.2.46 Numerical_value

A Numerical_value is a quantity expressed with a numerical value and a unit.

The data associated with a Numerical_value are the following:

- value_component

6.2.46.1 value_component

The value_component specifies the quantity of the Numerical_value.

6.2.47 Part

A part is an element of a product relevant for a bill-of material.

The data associated with a Part are the following:

- abbreviation

- alias_id

- change

- company_name

- copyright_note

- degree_of_maturity

- description

- external_references

- mass_information

- material_information

- part_number

- predecessor_part_number

- processing_information

- version

6.2.47.1 abbreviation

The abbreviation specifies a short name for a Part.

6.2.47.2 alias_id

The alias_id specifies an additional part_number that is used to identify the Part in another organizational context (e.g. company).

6.2.47.3 change

The change specifies the change history of the Part.

6.2.47.4 company_name

The company_name specifies the name of the organizational context in which the Part_number is defined.

Page 41: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 41 of 69

Copyright: VDA

6.2.47.5 copyright_note

The copyright_note specifies copyright information for a Part.

6.2.47.6 degree_of_maturity

The degree_of_maturity specifies the degree of maturity of a Part.

Where applicable the following values shall be used:

- ‘draft’

- ‘planning’

- ‘equipment order’

- ‘disposition’

6.2.47.7 description

The description specifies additional information about the Part.

6.2.47.8 external_references

The external_references specifies references to documents.

6.2.47.9 mass_information

The mass_information specifies the mass of a Part.

Example: Valid values for the unit of the Numerical_value specifying the mass are ‘g’, ‘kg’, or also ‘kg/piece’, ‘g/m’

6.2.47.10 material_information

The material_information specifies the material of a Part.

6.2.47.11 part_number

The part_number specifies the identifier of the Part. The format of the part number is user defined (OEM specific).

6.2.47.12 predecessor_part_number

The predecessor_part_number specifies the part number of the predecessor of the Part.

6.2.47.13 processing_information

The processing_information provides additional information for the processing of the Part.

6.2.47.14 version

The version specifies the version identifier of the Part. A version cumulates and consolidates one or more single changes.

6.2.48 Part_substitution

A Part_substitution is a mechanism that describes the replacement of a sealing plug with a terminal. Typically usage: an optional module is added to a harness and a common connector will be used.The data associated with a Part_substitution are the following:

- replaced

6.2.48.1 replaced

The replaced specifies the Cavity_plug_occurrence that is replaced.

6.2.49 Part_with_title_block

Page 42: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 42 of 69

Copyright: VDA

A Part_with_title_block is a mechanism to assign additional information to a Harness, a Harness_configuration or a Module.

The data associated with a Part_with_title_block are the following:

- car_classification_level_2

- car_classification_level_3

- car_classification_level_4

- model_year

- project_number

6.2.49.1 car_classification_level_2

The car_classification_level_2 provides a classification according to “CC8 Recommended Practices Specification and Configuration, Product Structures” ([CC8Rec]). Car classification is the identification of a set of similar cars to be offered to the market. Level 2 stands for “Technical information / platform” and reflects the level of a product class in a BoM system which represents a main technical product base (e.g. project, platform, engineering series etc.). In some cases this level carries a complete BoM ("Maximum BoM") for a project, platform, engineering series etc. This level is in some cases called technical documentation.

6.2.49.2 car_classification_level_3

The car_classification_level_3 provides a classification according to “CC8 Recommended Practices Specification and Configuration, Product Structures”. Car classification is the identification of a set of similar cars to be offered to the market. Level 3 stands for “Configuration information / product family” where all variant control mechanism are attached.

6.2.49.3 car_classification_level_4

The car_classification_level_4 provides a classification according to “CC8 Recommended Practices Specification and Configuration, Product Structures”. Car classification is the identification of a set of similar cars to be offered to the market. Level 4 stands for “Furthest pre-configured abstract product class” and represents the furthest configured class of a product, which is not yet a real product. E.g. this could be a complete vehicle, engine, gearbox etc. that has not been evaluated against customer special choices or a abstract vehicle, engine, gear-box etc. which could become a real one after the associated BoM is evaluated. The purpose of this level of a product class instance is in any case to reflect that level of product class of a BoM system, which leads to the individual BoM for a single product.

6.2.49.4 model_year

The model_year specifies the year of the car model.

6.2.49.5 project_number

The project_number specifies the development order number (car or engine project)

6.2.50 Processing_instruction

A Processing_instruction is the description of the methods that can be used to process a Part.

The data associated with a Processing_instruction are the following:

- instruction_type

- instruction_value

6.2.50.1 instruction_type

The instruction_type specifies the kind of the Processing_instruction.

Page 43: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 43 of 69

Copyright: VDA

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.50.2 instruction_value

The instruction_value specifies the value for the kind of the Processing_instruction defined by instruction_type.

6.2.51 Protection_area

A Protection_area is a mechanism to describe the area on a Segment covered by a Wire_protection_occurrence. Some segments of a harness are crossing areas with critical conditions like higher temperatures, higher humidity, etc. To prevent the damage of the cable, protect shields are mounted for that segment.

Note: For each Segment covered by a particular Wire_protection_occurrence a separate Protection_area has to be instantiated.

The data associated with a Protection_area are the following:

- associated_protection

- end_location

- gradient

- processing_information

- start_location

- taping_direction

6.2.51.1 associated_protection

The associated_protection specifies the Wire_protection_occurrence associated Segment objects.

6.2.51.2 end_location

The end_location specifies the end position of the Wire_protection_occurrence on the Segment. The value is given in curve parameters running from 0.0 to 1.0.

6.2.51.3 gradient

The gradient specifies the gradient of the protection.

Note: The gradient is defined in mm. Gradient 15 mms means that the winding screws within a turn 15 mms along the bundle.

6.2.51.4 processing_information

The processing_information provides additional information for the processing of the Protection_area.

6.2.51.5 start_location

The start_location specifies the start position of the Wire_protection_occurrence on the Segment. The value is given in curve parameters running from 0.0 to 1.0.

6.2.51.6 taping_direction

The taping_direction specifies the direction of the taping (left/right) regarding to the Segment direction.

6.2.52 Routing

A Routing is a course taken to get from a starting point to a destination.

The data associated with a Routing are the following:

Page 44: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 44 of 69

Copyright: VDA

- routed_wire

- segments

6.2.52.1 routed_wire

The routed_wire specifies the Connection for which the Routing is defined.

6.2.52.2 segments

The segments specify the Segment objects the course follows.

6.2.53 Segment

A Segment is a section of a Connection where no intermediate electrical contacts appear. At the beginning and at the end the same wires go in and out. Cables and wires are divided in segments. Every segment has its conditions like length, temperature range, etc.

The data associated with a Segment are the following:

- alias_id

- center_curve

- cross_section_area_information

- end_node

- end_vector

- fixing_assignment

- form

- id

- physical_length

- protection_area

- start_node

- start_vector

- virtual_length

6.2.53.1 alias_id

The alias_id specifies additional identifiers for the Segment.

Example: Segment Ids may vary from one CAD system export to another. Therefore the CAD system Id is improper for Id attribute. Id shall have a value, which is unique within the harness. Alias_id may be used for the CAD system Id.

6.2.53.2 center_curve

The center_curve specifies the mathematical definition of the set of center curves of the Segment.

6.2.53.3 cross_section_area_information

The cross_section_area_information specifies the cross-sectional area of the route.

Note: This information is needed for noncircular Segments.

6.2.53.4 end_node

The end_node specifies the Node defining the end of the Segment.

6.2.53.5 end_vector

The end_vector specifies the tangent of the center curve at the end position.

Page 45: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 45 of 69

Copyright: VDA

Note: The value can be derived from the center_curve. To avoid that the receiving system has to calculate the value, it can be explicitly specified.

6.2.53.6 fixing_assignment

The fixing_assignment specifies the Fixing_assignment objects associated with the Segment.

6.2.53.7 form

The form specifies information on the geometric shape of the Segment.

The following values shall be used:

- 'circular'

- 'noncircular'

6.2.53.8 id

The id specifies the identifier of the Segment.

6.2.53.9 physical_length

The physical_length specifies the arc length of the neutral phase of the segment in 3d.

6.2.53.10 protection_area

The Protection_area specifies the Protection_area objects associated with the Segment.

6.2.53.11 start_node

The start_node specifies the Node defining the start of the Segment.

6.2.53.12 start_vector

The start_vector specifies the tangent of the center curve at the start position.

Note: The value can be derived from the center_curve. To avoid that the receiving system has to calculate the value, it can be explicitly specified.

6.2.53.13 virtual_length

The virtual_length specifies the represented length of the neutral phase of the segment in 3d.

6.2.54 Slot

A Slot is a mechanism to group the Cavity objects of a Connector_housing.

The data associated with a Slot are the following:

- cavities

- id

- number_of_cavities

6.2.54.1 cavities

The cavities specifies the Cavity objects belonging to the Slot.

6.2.54.2 id

The id specifies the identifier of the Slot.

6.2.54.3 number_of_cavities

The number_of_cavities specifies the number of cavities associated with the Slot.

6.2.55 Slot_occurrence

Page 46: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 46 of 69

Copyright: VDA

A Slot_occurrence is the occurrence of a Slot in a module part list.

The data associated with a Slot are the following:

- cavities

- part

6.2.55.1 cavities

The cavities specifies the Cavity_occurrence objects belonging to the Slot_occurrence.

6.2.55.2 part

The part specifies the Slot that serves as a definition for this particular occurrence.

6.2.56 Special_terminal_occurrence

A Special_terminal_occurrence is the occurrence of a General_terminal with an identifier in a module part list.

The data associated with a Special_terminal_occurrence are the following:

- alias_id

- description

- id

- installation_information

- part

- placement

6.2.56.1 alias_id

The alias_id specifies additional identifiers for the Special_terminal_occurrence.

6.2.56.2 description

The description specifies additional information about the object.

6.2.56.3 id

The id specifies the identifier of the Special_terminal_occurrence.

6.2.56.4 installation_information

The installation_information provides additional information for the installation of the Special_terminal_occurrence.

6.2.56.5 part

The part specifies the General_terminal that serves as a definition for this particular occurrence.

6.2.56.6 placement

The placement specifies the transformation information, which is used to locate and orient the occurrence in the car coordinate system. According to the CES definition, the reference point is pin 1. For further information see [CESAK].

6.2.57 Special_wire_occurrence

A Special_wire_occurrence is the occurrence of a multi-core wire in a module part list.

The data associated with a Special_wire_occurrence are the following:

- core_occurrence

Page 47: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 47 of 69

Copyright: VDA

- special_wire_id

6.2.57.1 core_occurrence

The core_occurrence specifies the Core_occurrence contained in the Special_wire_occurrence.

6.2.57.2 special_wire_id

A special_wire_id specifies the identifier of the individual occurrence of multi-core wire. In contrast to the occurrence of a single wire, which does not need to be identified in the module part list, each multi-core wire occurrence must be identified.

6.2.58 Specified_accessory_occurrence

A Specified_accessory_occurrence is the occurrence of a Accessory_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_accessory_occurrence are the following:

- related_occurrence

- related_assembly

6.2.58.1 related_occurrence

The related_occurrence specifies the Accessory_occurrence it is an occurrence of.

6.2.58.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.59 Specified_cavity_plug_occurrence

A Specified_cavity_plug_occurrence is the occurrence of Cavity_plug_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_cavity_plug_occurrence are the following:

- related_occurrence

- related_assembly

6.2.59.1 related_occurrence

The related_occurrence specifies the Cavity_plug_occurrence it is an occurrence of.

6.2.59.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.60 Specified_cavity_seal_occurrence

A Specified_cavity_seal_occurrence is the occurrence of a Cavity_seal_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_cavity_seal_occurrence are the following:

part_number='1234‘AB part_number='1234'

AB

wire_number='1'

wire_number='2'

wire_number='3'

wire_number='4'

special_wire_id='1' special_wire_id=' '2

part_number='1234‘AB part_number='1234‘AB part_number='1234'

AB part_number='1234'AB

wire_number='1'

wire_number='2'

wire_number='3'

wire_number='4'

special_wire_id='1' special_wire_id=' '2special_wire_id='1' special_wire_id=' '2

Page 48: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 48 of 69

Copyright: VDA

- related_occurrence

- related_assembly

6.2.60.1 related_occurrence

The related_occurrence specifies the Cavity_seal_occurrence it is an occurrence of.

6.2.60.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.61 Specified_co_pack_occurrence

A Specified_co_pack_occurrence is the occurrence of a Co_pack_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_co_pack_occurrence are the following:

- related_occurrence

- related_assembly

6.2.61.1 related_occurrence

The related_occurrence specifies the Co_pack_occurrence it is an occurrence of.

6.2.61.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.62 Specified_component_occurrence

A Specified_component_occurrence is the occurrence of a Component within an Assembly_part_occurrence.

The data associated with a Specified_component_occurrence are the following:

- related_occurrence

- related_assembly

6.2.62.1 related_occurrence

The related_occurrence specifies the Component_occurrence it is an occurrence of.

6.2.62.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.63 Specified_connector_occurrence

A Specified_connector_occurrence is the occurrence of a Connector_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_connector_occurrence are the following:

- related_occurrence

- related_assembly

6.2.63.1 related_occurrence

The related_occurrence specifies the Connector_occurrence it is an occurrence of.

6.2.63.2 related_assembly

The related_ assembly specifies the Assembly_part_occurrence in which the occurrence is used.

Page 49: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 49 of 69

Copyright: VDA

6.2.64 Specified_fixing_occurrence

A Specified_fixing_occurrence is the occurrence of a Fixing_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_fixing_occurrence are the following:

- related_occurrence

- related_assembly

6.2.64.1 related_occurrence

The related_occurrence specifies the Fixing_occurrence it is an occurrence of.

6.2.64.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.65 Specified_special_terminal_occurrence

A Specified_ terminal _occurrence is the occurrence of a Terminal_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_special_terminal_occurrence are the following:

- related_occurrence

- related_assembly

6.2.65.1 related_occurrence

The related_occurrence specifies the Terminal_occurrence it is an occurrence of.

6.2.65.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.66 Specified_special_wire_occurrence

A Specified_special_wire_occurrence is the occurrence of a Special_wire_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_special_wire_occurrence are the following:

- related_occurrence

- related_assembly

6.2.66.1 related_occurrence

The related_occurrence specifies the Special_wire_occurrence it is an occurrence of.

6.2.66.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.67 Specified_terminal_occurrence

A Specified_terminal_occurrence is the occurrence of a Terminal_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_connector_occurrence are the following:

- related_occurrence

- related_assembly

6.2.67.1 related_occurrence

Page 50: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 50 of 69

Copyright: VDA

The related_occurrence specifies the Terminal_occurrence it is an occurrence of.

6.2.67.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.68 Specified_wire_occurrence

A Specified_wire_occurrence is the occurrence of a Wire_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_wire_occurrence are the following:

- related_occurrence

- related_assembly

6.2.68.1 related_occurrence

The related_occurrence specifies the Wire_occurrence it is an occurrence of.

6.2.68.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.69 Specified_wire_protection_occurrence

A Specified_wire_protection_occurrence is the occurrence of a Wire_protection_occurrence within an Assembly_part_occurrence.

The data associated with a Specified_wire_protection_occurrence are the following:

- related_occurrence

- related_assembly

6.2.69.1 related_occurrence

The related_occurrence specifies the Wire_protection_occurrence it is an occurrence of.

6.2.69.2 related_assembly

The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used.

6.2.70 Terminal_occurrence

A Terminal_occurrence is the occurrence of a General_terminal in a module part list.

Note: The number of occurrences used in a specific module or harness can be calculated by the individual occurrences.

Note: The Part_usage object specifies the usage of a Terminal_occurrence for a particular Cavity.

The data associated with a Terminal_occurrence are the following:

- part

6.2.70.1 part

The part specifies the General_terminal that serves as a definition for this particular occurrence.

6.2.71 Tolerance

A Tolerance is the specification of the allowable range for a dimension.

The data associated with a Tolerance are the following:

- lower_limit

Page 51: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 51 of 69

Copyright: VDA

- upper_limit

6.2.71.1 lower_limit

The lower_limit specifies the minimum allowed value.

6.2.71.2 Upper_limit

The upper_limit specifies the maximum allowed value.

6.2.72 Transformation

A Transformation is a geometric transformation composed of translation and rotation. Scaling is not included.

The data associated with a Transformation are the following:

- cartesian_point

- u

- v

6.2.72.1 cartesian_point

The cartesian_point specifies the coordinates of the translation.

6.2.72.2 u

The u specifies the rotation by means of the y-axis.

6.2.72.3 v

The v specifies the rotation by means of the z-axis.

6.2.73 Unit

A Unit is a quantity chosen as a standard in terms of which other quantities may be expressed.

Example: A unit of square milli metre is defined as a SI_unit with Si_unit_name "metre", Si_prefix "milli" and Si_dimension "square".

The data associated with a Unit are the following:

- si_dimension

- si_prefix

- si_unit_name

- unit_name

6.2.73.1 si_ dimension

The Dimension specifies the dimension of a SI_unit.

Example: "square", "cubic".

6.2.73.2 si_prefix

The si_prefix specifies the prefix for a SI unit.

Example: ‘milli’, ‘kilo’

6.2.73.3 si_unit_name

The si_unit_name specifies the name for a SI unit.

Example: ‘gram’, ‘metre’

Page 52: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 52 of 69

Copyright: VDA

6.2.73.4 unit_name

The unit_name specifies the name for a non-SI unit.

Note: NOTE This attribute shall be used to specify units like ‘kg/100 pieces’

6.2.74 Value_range

A Value_range is a pair of numerical values representing the range in which the value shall lie.

The data associated with a Value_range are the following:

- maximum

- minimum

6.2.74.1 maximum

The maximum specifies the maximum acceptable value that is constrained by the Value_range.

6.2.74.2 minimum

The minimum specifies the minimum acceptable value that is constrained by the Value_range.

6.2.75 Value_with_unit

A Value_with_unit is either a single numerical measure, or a range of numerical measures with upper, lower, or upper and lower bounds.

The data associated with a Value_with_unit are the following:

- unit_component

6.2.75.1 unit_component

The unit_component specifies the unit in which the Value_with_unit is expressed.

6.2.76 Wire_colour

A Wire_colour is a mechanism to define a colour for a wire together with a description of the kind of the colour.

The data associated with a Wire_colour are the following:

- colour_type

- colour_value

6.2.76.1 colour_type

The colour_type specifies the type of the colour.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Example: ‘base colour’, ‘second’, ‘third’

6.2.76.2 colour_value

The colour_value specifies the value of the colour.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Example: ‘red’

6.2.77 Wire_length

A Wire_length is a mechanism to define a length for a wire together with a description of the kind of the length (e.g. for DMU, for manufacturing).

Page 53: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 53 of 69

Copyright: VDA

The data associated with a Wire_length are the following:

- length_type

- length_value

6.2.77.1 length_type

The length_type specifies the type of the length.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

6.2.77.2 length_value

The length_value specifies the length of the wire.

6.2.78 Wire_occurrence

A Wire_occurrence is the occurrence of a single wire in a module part list.

The data associated with a Wire_occurrence are the following:

- wire_number

6.2.78.1 wire_number

The wire_number specifies the identification of a wire. This number is unique within a vehicle and usually automatically generated (dependent on "from-to" information).

6.2.79 Wire_protection

A Wire_protection is a mechanism to describe harness wrappings, a shield to prevent the wire from damaging.. It covers all kinds of wrappings modeled by CAD systems.

The data associated with a Wire_protection are the following:

- protection_type

- type_dependent_parameter

6.2.79.1 protection_type

The protection_type specifies the type of the Wire_protection.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Example: ‘coil’, ‘corrugated pipe’, ‘foam rubber strip’

6.2.79.2 type_dependent_parameter

The type_dependent_parameter specifies further information dependent on the type of the Wire_protection.

Note: There are no values pre-defined. Special values have to be negotiated between exchange partners.

Example: For corrugated pipe: wave shape, for pull-push rule: width

6.2.80 Wire_protection_occurrence

A Wire_protection_occurrence is the occurrence of a Wire_protection in a module part list.

Page 54: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 54 of 69

Copyright: VDA

The data associated with a Wire_protection_occurrence are the following:

- alias_id

- description

- id

- installation_information

- protection_length

- part

6.2.80.1 alias_id

The alias_id specifies additional identifiers for the Wire_protection_occurrence.

6.2.80.2 description

The description specifies additional information about the object.

6.2.80.3 id

The id specifies the identifier of the Wire_protection.

6.2.80.4 installation_information

The installation_information provides additional information for the installation of the Wire_protection_occurrence.

6.2.80.5 protection_length

The protection_length specifies the length of the Wire_protection_occurrence with respect to the wrapping.

6.2.81 Wiring_group

A Wiring_goup is a mechanism to group wire or core occurrences together.

Example: Twisted pairs.

The data associated with a Wire_protection_occurrence are the following:

- assigned_wire

- id

- processing_information

- type

6.2.81.1 assigned_wire

The assigned_wire specifies the Wire_occurrence and Core_occurrence objects, which are grouped together.

6.2.81.2 id

The id specifies the identifier of the Wiring_group.

6.2.81.3 processing_information

The processing_information provides additional information for the processing of the Wiring_group.

6.2.81.4 type

The type specifies the type of the grouping.

Example: twisted-pair.

Page 55: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 55 of 69

Copyright: VDA

7 KBL Reference Model

This section defines the reference model for the Harness Description List. It represents the objects, attributes and relations between objects, as defined in section 6.2, in a graphical way. The notation used for this representation is UML [Fowler].

Figure 4: UML diagram 1: Common part attributes and properties

Exter nal_r eference

Document_type : Str ingDocument_number : StringChange_level : StringFi le_name [0..1] : StringLocation [0..1] : Stri ngData_format : StringCreating_system [0..1] : String

(from 6_F oundation)

Materi al

Material_key : StringMaterial_reference_system [0..1] : Str ing

(from 6_Foundat ion)

Processing _instruction

Instruction_type : StringInstruction_value : String

( fr om 6_Fo undat ion )

Part

Part_number : StringCompany_name : StringAlias_id [0..*] : Alias_identificationVersion : StringAbbreviation : StringDescription : StringPredecessor_part_number [0..1] : StringDegree_of_maturity [0..1] : StringCopyright_note [0..1] : StringMass_information [0..1] : Numerical_value

(fr om 2_Parts)

0..*

0..*

0..*

+External_references0..*

1

0..1

1+Material_i nformati on

0..1

1

0..*

1+Pr oces sing_i nformat io n

0..*

Change

Id [0..1] : StringDescription [0..1] : StringChange_request [0..1] : StringChange_date [0..1] : StringResponsible_designer : StringDesigner_department : StringApprover_name [0..1] : StringApprover_department [0..1] : String

(f rom 6_Foundation)

1

0..*

1

+Change

0..*

Approval

Name [0..1] : StringDepartment [0..1] : StringDate : StringType_of_approval : String

(fr om 6_Fo und at ion)Creation

Name : Str ingDepartment : Str ingDate : String

( from 6_Fo undation)

Par t_wit h_titl e_bloc k

Project_number [0..1] : Stri ngCar_classi fication_level_2 : StringCar_classi fication_level_3 [0..1] : StringCar_classi fication_level_4 [0..1] : StringModel_year : String

(from 2_Parts)

0..*1..* 0..*

+Is_ap plied_to

1..*

0..* 1..*0..*

+Is_applied_to

1..*

Harness

Content : Harness_content(f rom 1_Harness)

Harness_configuration

Log istic_control_informat ion [0 ..1] : Str ing(from 1_Harness)

1 0..*1

+Harness_configuration

0..*

Module

Content : Module_content( from 1_Harness)

10. .* 1

+Module

0. .*

0..*1..* 0..*+M odules1..*

Page 56: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 56 of 69

Copyright: VDA

Accesso ry

(from 2_Parts)

Assembly _part

( from 2_Parts)

Cav ity _plug(from 2_Parts)

Cav ity _seal

(from 2_Parts)

Co_pack_part

(from 2_Parts)

Connector_housing

( from 2_Parts)

Fixing

( from 2_Parts)...)

General_terminal

( from 2_Parts)

General_wire

(from 2_Parts)

Par t_wit h_t it le_bloc k

( from 2_Part s)

W ire_protect ion( from 2_Parts)

H arness

(from 1_H arness)...)

Module

(from 1_Harness)...)

10..* 1

+Module

0..*

Par t

( from 2_Parts)

Component

(from 2_Parts)

Figure 5: UML diagram 2: Part specializations

Assembly_p ar t_occu rre nc e

Id : Strin gAlias _id [0..*] : Alias _id en tificationD es c rip tio n [0..1] : StringPlac emen t [0..1] : Tran s fo rmation

(from 3_Part_struct...

C onn ec ti on

Id [0 ..1] : Strin gD es c r iption [0..1 ] : Strin gSignal_n a me [0..1] : Strin g

(from 4_Connectiv ...

Fix ing_ oc cur renc e

Id : Strin gAlias _id [0 ..*] : Alias _ide n tific ationD es c r iption [0..1] : Str ingPlac emen t [0..1 ] : Trans for mation

(from 3_Part_struct...

Gen e ra l_w ire _o c cur r en ce(from 3_Part_struct...

C o_ pack _oc curr e nc e

Id : StringAlias _id [0..*] : Alias _ide ntifica tionD es c rip tion [0..1] : Strin g

(from 3_Part_struct...

C av ity_ sea l_oc cur re nc e(from 3_Part_structure)

W ire _ protec tion_o cc ur r en ce

Id : Str ingA lias _ id [0. .*] : A lias _ iden tific a tionD esc riptio n [0.. 1] : S tringP rotec tion_ leng th [0 ..1 ] : Num er ic al_v a lue

(from 3_Part_struct...

C av ity_p lug_ oc cur r en ce(from 3_Part_struct...

Terminal_o cc ur r en ce(from 3_Part_structure)

Spec ial_te rminal_o ccur ren ce

Id : StringAlia s_id [0..*] : Alias _ide ntifica tionD es c r iption [0..1] : StringPlac emen t [0 ..1] : Tran s formation

(from 3_Part_struct...

C ompo ne nt_o ccur r en ce(fro m 3_P art_s tructure)

Acces so ry _o c cur r en ce

Id : Strin gAli as _i d [0..*] : Alia s_i den t ific ationD es c r iption [0 ..1] : Strin gPlac emen t [0..1] : Tra ns fo rmation

(from 3_Part_struct...

C on nec t or_o ccur ren c e

Id : Str ingAlias _ id [0 ..*] : Alias _ide ntific ationD esc ripti on [0 ..1] : StringU sag e [0 ..1] : C onn ecto r _us agePlace men t [0 .. 1] : T rans fo rm ation

(from 3_Part_struct...

0..*

0 ..*

0..*

+Re fe renc e _e lement0 ..*

Modu le_c on tent

module

var ia

(from 1_Harn...

<< en umera tion>>

Modu le_c on figur ation _ty pe

op tion

cod e

(from 1_Harn...

<<en umer ation>>

C on ne c tion_o r _o ccur renc e(from 1_H arn...

<<Selec tor >>

H arn ess _ con figur ation

Lo gis tic _

(from 1_Harn...

H arn e ss_ co nt ent

ha rnes s co mplete s etha rnes s su bs et

(from 1_Harn...

<<en u mer ation >>

M odu le

C on ten t :

(from 1_Harn...

0..*

1..*

0..*

+Mod ules 1..* 11

Modu le_c on figur ation

Lo gis tic_c on trol_ infor mation : Str ingC on fig uration_ type [0..1 ] : Mod ule _c on figura tion_ type

(from 1_Harn...

0..*

0..*

0..*

+C on tro lled_c ompo ne nts

0..*

1

1

1

+Mod ule _c on figura tion

1

Modu le_family

Id : StringD es c rip tion [0..1] : Strin g

(from 1_Harn...

0..*

0..1

0..*

+Of_family

0..1

H ar ne ss

C on te nt : Ha rnes s _c on tent

(from 1_Harn...1

0 ..*

1

+C ompo n en ts

0 ..*

1

0..*

1

+H ar ne ss_ con fig uration 0..*

11

1

0..*

1

+Mod ule

0..*

1 0..*1

+Mod ule_ co nfigur ation

0..*

0..*

1

+Mod ule_ families

0..*

1

W ir in g _g roup

Id : StringTy pe [0..1] : String

(from 4_Connectiv ...

Figure 6: UML diagram 3: Harness and modules

Page 57: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 57 of 69

Copyright: VDA

Accessory

Accessory_type [0.. 1] : St ring

(f rom 2_ Pa.. .

Assembly_part

Part_type [0.. 1] : St ring

(from 2_Pa...

F ixing

Fixing_type [0.. 1] : St ring( fr om 2_Pa...

Wire_protection

Protect ion_type [0. .1] : S tringType_dependent_parameter [0. .1] : St ring

(from 2_Pa...

Cavit y_plug

Colour [0. .1] : S tr ingPlug_t ype [0. .1] : S tr ing

(from 2_Pa...

Co_pack_part

P art_t ype [0. .1] : S tr ing

( fr om 2_Pa...

Wire_colour

Colour_type : S tringColour_value : String

( fro m 6_Fou ndat...

General_wire

Cable_designator [ 0. .1] : StringWire_type [0. .1] : StringBend_radius [0..1] : Numerical_valueCross_sect ion_area [0. .1] : Numerical_valueOutside_diameter [0. .1] : Numerical_value

( fro m 2_Pa...

1 1.. *1

+Cover_colour

1.. *

Core

Id : St ringCable_designator [0. .1] : St ringWire_type [0..1] : St ringCross_sect ion_area : Numerical_valueOutside_diameter [0. .1] : Numerical_valueBend_radius [0.. 1] : Numerical_value

( fr om 2_Pa...

1

1. .*

1

+ Core_colour1. .*

1

0..*

1

+ Core 0..*

Cavity_seal

Colour [ 0..1] : S tr ingSeal_type [ 0..1] : StringWire_size [0..1] : Value_range

(from 2_Pa...

General_terminal

Terminal_type [0. .1] : S tringPlating_material [0. .1] : St ringCross_sect ion_area [0. .1] : Value_rangeO utside_diameter [0. .1] : Value_range

(from 2_Pa...

Connector_housing

Housing_colour [0. .1] : StringHousing_code [0. .1] : StringHousing_type [0. .1] : S tring

(from 2_Pa... Cavity

Cavity_number : String

(from 2_Pa...

Slot

Id [0..1] : StringNumber_of_cavities : Integer

( fr om 2_Pa...1 0..*1

+Slots

0..*

1..*1

+Cavit ies

1..*1

Alias_identif icat ion

Alias_id : S tr ingScope [0.. 1] : St ringDescription [0. .1] : St ring

( fr om 6_Foundat...

Figure 7: UML diagram 4: Part master data

Page 58: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 58 of 69

Copyright: VDA

P art(from 2_Parts)

Terminal _occurrence(f rom 3_Part_st ructure)

General_terminal(from 2_Parts)

1..* 11..*

+Part

1

Module(f rom 1_Harness). .. )

Mo dule _conf igurati on(f rom 1_Harness)

1

1

1

+Module_conf iguration1

Harness(f rom 1_Harness).. . )

1

0..*

1

+Modu le

0. .*

1 0..*1

+Module_conf igurat ion

0..*

Connec ti on_or_occ urrenc e(f rom 1_Harness)

<<Se lect or>>

0..*

0. .*

0. .*

+Controlled_components 0. .*

1

0. .*

1

+Compo nent s

0. .*

Seg ment(from 5_Topology). .. )

Rout ing(f rom 5_Topology).. .)

0..* 0. .*0. .*

+Segments

0. .*{ordered}

Slot(from 2_Parts)

Cav ity(from 2_Parts)

1

1..*

1

+Cav ities 1..*

Connec tion( fr om 4 _Con nec ti vity )

0..*

1

0. .*

+Routed_wi re 1

Cav ity _occurrence(from 4_Connectivity )

1..*

1

1. .*

+Part 1

Extrem ity(from 4_Connectivity).. .)

2 ..*

1

+Ex tremities

2 ..*

1

Connector_housing(f rom 2_Parts)

1

0..*

1

+Slots 0..*

Slot_occurrence(from 4_Connectivit y)

1..*

1

1. .*

+Par t

1

1

1. .*

1

+Cav ities

1. .*

Contact_point(from 4_Connectivity)

0..* 1. .*0..*

+Contacted_cav ity

1. .*

1

0..*

+Contac t_point 1

0..*

Connec tor_oc cur ren ce(f rom 3_Part_structure)

0..*

0..*

+Ref erenc e_elem ent

0. .*

0..*

1. .*

1

1. .*

+Pa rt 1

1

0. .*

1

+Slots

0. .*

0. .*

1+Contact_points

0. .*

1

Figure 8: UML diagram 5: Connection overview

Page 59: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 59 of 69

Copyright: VDA

Core_occurrence

Wire_number : String

(fr om 3_Par t_st ruc ture )

Wire_occurrence

Wire_number : String

(from 3_Part_st ructure)

Wir ing_group

Id : StringType [0..1] : String

(from 4_Connectivity)

Cavity_plug_occurrence(from 3_Part _st ructure)

Processing_instruction

Instr uc tion_t ype : Str ingInstr uc tion_value : S tring

(from 6_F oundation)

0..*

1

+ Process ing_i nformation0..*

1

W ire_or_core_occurrence

(from 4_Connect ivity)

<<Selector> >2..* 0..*

+Assigned_wire

2..* 0..*

External_reference

Document_type : Str ingDocument_number : StringChange_level : StringFile_name [0..1] : StringLocation [0..1] : StringData_format : StringCreating_system [0..1] : String

(fr om 6_F ounda tion )

Connection

Id [0..1] : StringDescr iption [0..1] : StringSig nal_name [0..1] : String

(fr om 4_Connec tivit y) 1 0. .*1

+Processing_information

0. .*

1

0..*

+Wire 1

0..*

0..*

0..*

+ Exter nal _re ferences0..*

0..*

Instal lation_instruction

Instruction_type : Str ingInstruction_value : String

(from 6_Foundation)

1

0..*

1

+Installation_information

0..*

Part_usage_select(fr om 3_Par t_st ruc ture )

<<Selector> >

Cavity_occurrence(from 4_Connectivity)

1..*

0..1

1..*

+Associated_plug 0..1

Extremity

Position_on_wire : Double

(from 4_Connect ivity)12..* 1

+Extremities

2..*Connector_occurrence(f rom 3_Part_st ructure)

Contact_point

Id : Str ing

(from 4_Connect ivity)

0..*

1..*

+Associated_parts 0..*

1..*

0..*

1..*

0..*

+Contacted_cavit y1..*

0..*

1

0..*

+Contact_point

1

1

0..*

1

+Contact_points

0..*

Figure 9: UML diagram 6: Connectivity

Cavi ty_plug_occurrence(f r om 3_Part _st ruct ure)

Cav ity_seal_occurrence( fr om 3_Par t_st r uct ure)

Component_occurrence

Id : S tringA lias_id [0..* ] : A lias_identifica tion

Description [0..1] : String

(f r om 3_Part _st ruct . ..

Terminal_occurrence(f rom 3_Par t _str uct ure)

Harn ess

Content : Harness_content

(f rom 1_Harn. . .

Connection_or_occurrence( from 1_Har ness)

<<Selector>>

1

0..*

1

+Components

0..*

A ssembly_part

P art_type [0..1] : S tring

(f rom 2_Pa. . .

0..*

1

+Components

0..*

1

Co_pack_occurrence

Id : S tring

Al ias_id [0..* ] : Al ias_identifica tionDescription [0..1] : String

(f r om 3_Par t _st ruct . ..

Fixing_occurrence

Id : S tringAl ias_id [0..* ] : Al ias_identifica tion

Description [0..1] : StringPlacement [0..1] : Transformation

(f r om 3_Par t _st ruct . ..

Ge neral_wir e_occu rrence( f rom 3_Pa r t_st r uct ur e)

S pecial_terminal_occurrence

Id : S tring

A li as_id [0..* ] : Al ias_identifica tionDe scription [0..1] : StringP lacement [0..1] : Transformation

(f rom 3_Par t _str uct .. .

W ire_protection_occurrence

Id : S tringA li as_id [0..* ] : Al ias_identifica tion

De scription [0..1] : StringP rotection_length [0..1] : Numerical_value

( fr om 3_Part _st ruc t. ..

A ssembly_part_occurrence

Id : S tringA lias_id [0..*] : A lias_identification

Des cription [0..1] : StringP lacement [0..1] : Transformation

(f r om 3_Part _st ruc t. ..

1..*

1

1..*

+Part1

A ccessory_occurrence

Id : S tring

A lias_id [0..* ] : Al ias_identificationDesc ription [0..1] : StringP lacement [0..1] : Transformation

( fr om 3_ Par t_st r uct. . .

Connector_occurrence

Id : S tringA lias_id [0..* ] : A lias_identification

Desc ription [0..1] : S tringUsage [0..1] : Connector_usageP lacement [0..1] : Transformation

( fr om 3_ Part _st r uct. . .

Installation_instruction

Instruction_type : S tringInstruction_value : S tring

( f rom 6_Foundat. ..

1

0..*

1

+Installation_information0..*

1

0..*

1

+Installation_information

0..*

1

0..*

1

+Installation_information

0..*

1

0..*

1

+Installation_information

0..*

1

0..*

1

+Installation_information

0..*

1

0..*

1

+Installation_information

0..*

1

0..*

1

+Installation_information

0..*

1

0..*

1

+Installation_information0..*

Figure 10: UML diagram 7: Part usage list (1)

Page 60: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 60 of 69

Copyright: VDA

Cav ity

C av ity_numb er : Strin g

(from 2_P a...

C a v ity _pl ug_o ccurre nce(from 3_Part_structure)

Ass embly _par t_oc currenc e

Id : Strin gAlias_id [0..*] : Alias_iden tificationD esc r iption [0..1] : Str ingPlacement [0..1] : Transfor mation

(from 3_P art_struct...

Ac c es s or y

Ac ces sory _type [0..1] : String

(from 2_P a...

Spec ified_ac c es s ory _occ urr...(from 3_Part_structure)

0 ..*

1

0 ..*

+R elated_as s embly

1

Slot

Id [0..1] : Str ingN umber_of_c avities : Integer

(from 2_P a...

1 1..*1

+Cavi tie s

1..*

Cav ity_oc curr ...(from 4_Connectivi ty)

1..*

1

1..*

+Par t 1

0..1

...

+Ass oc iated_ plug 0..1

...

Spec ified _c onnec tor_occ urrence(from 3_P art_structure)

0..*

1

0..*

+R ela ted_ass embly1

Ac c ess ory _occ urrence

Id : Stri ngA lias _id [0..*] : A lias _i denti fic ationDe scrip tion [0.. 1] : Strin gP la ceme nt [ 0. .1 ] : Tra ns for mation

(from 3_P art_struct...

1..*

1

1..*

+Par t1

0..*

1

0..*

+R elated_oc currenc e1

C onnector _housing

Housing _col ou r [0..1 ] : Str ingHousing _cod e [0 .. 1] : S trin gHousing _ty pe [0..1] : Str ing

(from 2_P a...

1 0..*1

+Slots

0..*

Slot_o cc urr ence(from 4_Connectivi ty)

1

1..*

+Part1

1..*

1..*1

+C avities

1..*1

C onnector _us age

no endr ing termin als plicedang le r

(f rom 3 _Pa rt_ str uc t...

<< enumeration>>

Connec tor_occ urrence

Id : Strin gAlias_id [0..*] : Alias_iden tificationD esc r iption [0..1] : Strin gU s age [0..1] : Connec tor_usagePlacement [0..1] : Transfor mation

(f rom 3 _P art_str uct...

0..*

1

0..*

+R elated_oc c ur renc e

1

0..* 0..*0..*

+R eferenc e_element

0..*

1..*

1

1..*

+Part1

0..*

0..*

+Refer enc e_element

0..*

0..*

1 0..*1

+Slots

0..*

11

Figure 11: UML diagram 8: Part usage list (2)

Wire_occurrence

Wire_number : Str ing

( from 3_Part_s truc t...

Sp ecifi ed_wire_occ ur rence( from 3_Part_s truc t...

0..*

1

0..*

+Related_occurr ence1

As sembly_part_occ ur rence

Id : StringAlias_id [0..*] : Alias_identificationDescription [0..1] : StringPlacement [0..1] : Transformation

( from 3_Part_s truc t...

0..*

1

0..* +Related_assembly

1

Sp ecifi ed_spec ial_wire_occ urren ce( from 3_Par t_struct...

0..*

1

0..*

+Related_assembly1

Sp ecia l_wire_occur rence

Special_wire_id : String(from 3_Part_struct...

0..*

1

0..*

+Related_occur rence1

Wire_length

Length_type : StringLength_value : Numerical_value

( from 6 _Foun da t...General_w ire_occurrence

( from 3_Part_s truct...

1 1..*1

+Length_information

1..*

Core_occurrence

Wire_number : String( from 3_Part_s truc t...

1 0..*1

+Core_occurr ence

0..* 1

1..*

1

+Length_information

1..*G eneral _wir e

Cable_designator [0..1] : Str ingWire_type [0..1] : StringBend_radius [0..1] : Numerical_valueCr oss_section_area [0..1] : Numerical_value...Outside_diameter [0..1] : Numerical_value

( from 2_Pa...

1..*1 1..*

+P art

1

Core

Id : StringCable_designator [0..1] : StringWire_type [0..1] : Str ingCross_section_area : Numerical_valueOutside_diameter [0..1] : Numerical_valueBend_radius [0..1] : Numerical_value

( from 2_Pa...

1..*

1

1..*

+Part 1

1

0..*

1

+Core 0..*

Figure 12: UML diagram 9: Part usage list (3)

Page 61: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 61 of 69

Copyright: VDA

Co_ pack _pa rt

Part _ty pe [0 ..1] : S tr in g...(fr om 2_Parts)

Cav it y _se al

Colour [0..1] : St ringSea l_ typ e [0. .1] : St ringWire_s ize [0 ..1] : Value_range...

(from 2_Parts)Wire_protection

Prot ectio n_ty pe [0..1] : St ringTyp e_depen dent_parameter [0..1] : Str ing. ..

(from 2_Parts)

Fix ing

Fix ing_ty pe [0..1] : St ring...(from 2_Parts)

Co_pack_oc currence

Id : St ringAlias_id [0..* ] : Alias_identif ication...

Descript ion [0..1] : St ring

(f rom 3_Part_st ructure)

1..*

1

1..*

+Part1

Cav ity _seal_occurrence(from 3_Part_structure)

1.. *

1

1.. *

+Part1

W ire_ pro te ction _oc cur re nce

Id : St ring

Alias_id [0..* ] : Alias_identif icat ionDescript ion [0..1] : St ring

Protection_length [0..1] : Num erical_v alue...

(from 3_Part_st ructure)

1..*

1

1..*

+Part 1

Fixing_occurrence

Id : St ring

Alias_id [0..* ] : Alias_identif icat ion. ..Descript ion [0..1] : St ringPlacem ent [0. .1] : Trans f ormation. ..

(f rom 3_Part_structure)

1..*

1

1..*

+Part 1

Specif ied_ co_ pack_oc curre nce(f rom 3_Part_structure)

0..*

1

0..*

+Re la ted _oc cur re nce 1

Specif ied_ cav i ty _seal_oc curre nce(f rom 3_Part_structure)

0..*

1

0..*

+R e la ted_oc currence 1

Specif ied_wire_protection_occurrence(from 3_Part_st ructure)

0..*

1

0..*

+Related_occurrence 1

Spec if ied_f ix ing_occurrence(f rom 3_Part_structure)

0..*

1

0..*

+Related _occurrence 1

Assembly _part_oc currence

Id : St ringAlias_id [0..* ] : Alias_identif ication...

Descript ion [0..1] : St ringPlacem ent [0..1] : Transf ormation...

( fro m 3_ Pa rt_ str uct ure) 0..*1

0..*

+Related_assembly

1

0..*1 0..*

+Related_assembly

1

0..* 10..*

+R e la ted _as sembly

1

0..* 10..*

+Related_assembly

1

Figure 13: UML diagram 10: Part usage list (4)

Page 62: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 62 of 69

Copyright: VDA

Cavity_seal_occurrence(from 3_Par t_s tr uc tur e)

General_terminal

Terminal_type [0..1] : StringPlating_material [0..1] : StringCross_section_area [0..1] : Value_rangeOutside_diameter [0..1] : Value_range

(from 2_Pa...

Special_terminal_occurrence

Id : StringAlias_id [0..*] : Alias_identificationDescription [0..1] : StringPlacement [0..1] : Transformation

( fr om 3_Par t_s truc t...

1..*

1

1..*

+Part 1

Terminal_occurrence( fr om 3_Par t_s truc ture)

1..*

1

1..*

+Par t 1

Specified_special_terminal_occurrence(from 3_Par t_s truc ture )

0..*

1

0..*

+Related_occurrence 1

Specified_terminal_occurrence( fr om 3_Par t_s truc ture)

0..*

1

0..*

+Rel ated _occurr ence

1 Assembly_part_occurrence

Id : StringAlias_id [0..*] : Alias_identificationDescription [0..1] : StringPlacement [0..1] : Transformation

( fr om 3_Par t_s truc t...

0..*

1

0..*

+Related_assembly

1

0..*

1

0..*

+Related_assembly

1

Cavity_plug

Colour [0..1] : StringPlug _type [0..1] : String

( fr om 2_Pa...

Specified_cavity_plug_occurrence( fr om 3_Par t_s truc ture)

0..*

1

0..*

+Related_assembly

1

Cavity_plug_occurrence(from 3_Par t_s truc ture) 1.. * 11.. *

+Part

1

0..*

1

0..*

+Related_occurrence1

Part_substitution( fr om 3_Par t_s truc ture)

1

0.. *

+Replaced 1

0.. *

Part_usage_select( fr om 3_Par t_s truc ture)

<<Sel ector>>

0..*

1

+Repl acing0..*

1

Figure 14: UML diagram 11: Part usage list (5)

Page 63: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 63 of 69

Copyright: VDA

Cavity_occurrence(from 4_Connecti vity)

S lo t_ occurrence(from 4_Connectivity)

1 1. .*1

+Cavi ties

1. .*

Connector_occurrence

Id : StringAl ias_id [0..*] : Al ias_identi fica tion...Description [0..1] : StringUsage [0..1] : Connecto r_usagePlacem ent [0..1] : T ransform ation

(from 3_Part_structure)

1 0.. *1

+S lots

0.. *

0..*

0..*

+Reference_element0..*

0..*

Mou ntin g_e le m ent(from 3_Part_structure)

<<S elector>>

Compo nen t(fr om 2_Par ts)

Component_occurrence

Id : StringAl ias_id [0..*] : Al ias_identi fication...Description [0..1 ] : String

(from 3_Part_structure)

1..*

0.. *

+Mounting 1..*

0.. *

1 1..*

+Part

1 1..*

Assembly_part_occurrence

Id : StringAlias_id [0..*] : A lias_identi fi ca tion...Description [0..1] : StringPlacement [0..1] : T ransformation

(from 3_Part_structure)Speci fied_com ponent_occurrence(from 3_Part_structure)

1

0..*

+Related_occurrence1

0..*

10. .*

+Related_assembly

10. .*

Figure 15: UML diagram 12: Part usage list (6)

Page 64: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 64 of 69

Copyright: VDA

Assembly_part _occurrence

Id : StringAlias_id [ 0. .*] : Alias_identificat ionDescription [0.. 1] : StringPlacement [ 0.. 1] : Transformation

(from 3_P art_struct. ..

Special_terminal_occurrence

Id : StringAlias_id [0.. *] : Alias_ident if icationDescription [0. .1] : StringPlacement [0. .1] : Transformation

(from 3_P art_struct...

Fixing_occurrence

Id : StringAlias_id [0. .*] : Alias_identif icat ionDescript ion [0.. 1] : StringPlacement [ 0. .1] : T ransformation

(from 3_P art_struct...

W ire_protection_occurrence

Id : S tr ingAlias_id [0.. *] : Alias_identificat ionDescription [0.. 1] : St ringProtect ion_length [0. .1] : Numerical_value

(from 3_Part_struct...

Connection

Id [0. .1] : StringDescript ion [0. .1] : StringSignal_name [ 0. .1] : S tr ing

(from 4_Connecti v.. .

Rout ing(from 5_Topology)

0.. *

1

0.. *

+Routed_wire1

Segment_form

circularnoncircular

(from 5_Topol...

<<enum era t io n>>

Value_determinat ion

calculatedreservedmeasured

(from 6_Foundat...

<<enumeration>>Cross_sect ion_area

Value_determinati on : Value_de terminat ionArea : Numerical_value

(from 6_Foundat...

11

Acc es so ry_occurre nc e

Id : StringAlias_id [0.. *] : Alias_identif icationDescription [0. .1] : StringPlacement [0 . .1] : Transformation

(from 3_P art_struct...

Connector_occurrence

Id : StringAlias_id [0. .*] : Alias_identif icationDescript ion [0. .1] : StringUsage [0. .1] : Connector_usagePlacement [0. .1] : T ransformat ion

(from 3_P art_struct...

0..*

0.. *

+Reference_element

0..*

0.. *

0. .*

0. .*

0. .*

+Reference_element 0. .*

Located_component(from 5_Topology)

<<Selector> >

Processing_inst ruction

Instruction_type : StringInstruction_value : St ring

(from 6_Foundat...

1

0.. *

1

+Processing_information0.. *

Segment

Id : StringAlias_id [0. .*] : Alias_identif icationSt art_vector [ 0.. 3] : DoubleEnd_vector [0. .3] : DoubleVirt ual_length [0. .1] : Numerical_valuePhysical_length [ 0.. 1] : Numerical_valueForm [ 0.. 1] : Segment_form

(from 5_Topol...

0..*0.. * 0..*

+Segments

0.. *

{ordered}11

0..*

1

+Cross_sect ion_area_informat ion0..*

1

B_spline_curve

D eg ree : Inte ger

(from 6_Foundat...

1

0..*

1

+Center_curve

0. .*

{ordered}

Cartesian_point

Coordinates [2.. 3] : Double

(from 6_Foundat...

0..*2.. * 0. .*

+Control_points

2.. * {ordered}

Node

Id : StringAlias_id [0. .*] : Alias_identif icat ionBend_radius [0. .1] : Numerical_value

(from 5_Topol ...

0..*

0..*

+ referenced_com ponents0..*

0..*

1

0. .*

1

+Processing _i nformat ion 0. .*

0.. *

1

0.. *

+St art_node1

0.. *

1

0.. *

+End _n ode1

1

0..*

+Cartesian_point1

0..*

Figure 16: UML diagram 13: Topology and routing (1)

Page 65: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 65 of 69

Copyright: VDA

Accessory_occu rrence

Id : St ringAl ias_id [0..*] : Al ia s_identi fi cationDescri ption [0..1] : StringPlacem ent [0..1 ] : T ransformati on

(from 3_Part_structure)

Fixing_occurren ce

Id : StringAl ias_id [0..*] : Alias_ident i ficationDescription [0.. 1] : StringPlacement [0..1] : T ransformation

(from 3_Part_structure)

Fixed_component(from 5_Topology)

<<Selector>>Fixing_assignment

L oca ti on : Dou bleOri ent at ion [2. .3 ] : Dou bl e

(from 5_Topology)

1 0..*

+Fixing

1 0..*

Pro cessi ng_ instruc ti on

Instruction_type : StringInstruction_value : String

(from 6_Foundation)

Se gment

Id : StringAl ias_id [0 ..*] : Al ias_identi fica tionStart_vector [0..3 ] : DoubleEnd_vector [0..3 ] : Double

Virtual_length [0..1 ] : Numerical_va luePhysical_ length [0..1] : Nu merical_va lueForm [0..1] : Segment_form

(from 5_Topology)

1

0.. *

1

+Fixing_assignment 0.. *

Protecti on_ are a

Start_ location : DoubleEnd_loca tion : DoubleT aping_di rection [0..1] : StringGradient [0..1 ] : Value_wi th_uni t

(from 5_Topology)

10..* 1

+Processing_information

0..* 10..* 1

+Protection_area

0..*

Wi re_prot ecti on_o ccurrence

Id : StringAl ias_id [0..*] : Ali as_ident i ficat ionDescription [0 .. 1] : StringProte ction_length [0 ..1] : Num erica l_val ue

(from 3_Part_structure)

0..*

1

0..*

+Associated_protection 1

Figure 17: UML diagram 14: Topology and routing (2)

Node

Id : St rin gAli as_id [ 0. .* ] : A li as_ id entif i catio nBend_ ra diu s [0 .. 1] : Num erical_ val ue

(f rom 5_Topology)

Located_component(from 5_Topology)

<<Selector>>

0..*0..* 0..*

+referenced_com ponents

0..*

Placed_element(from 5_Topology)

<< Sel ector>>

Tolerance

Lowe r_l im it [ 0..1 ] : Nume rical _valueUppe r_l im it [ 0..1 ] : Nume rical _value

(f rom 5_Topology)

Dimensi on_spec if icat ion(from 5_Topolog y) 1

0..* +origin

1

0..* 1

0..* +targ et

1

0..*

0..1

1

+Tolerance_indication

0..1

1

Figure 18: UML diagram 15: Dimensions

Page 66: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 66 of 69

Copyright: VDA

Nu merica l_ val ue

Value_component : Double

(f rom 6_Foundation)Value_range

Minimum : DoubleMaxi mum : Double

(from 6_Foundation)

B_spl ine_curve

Degree : I ntege r

(from 6_Foundation)

Cartesian_point

Coordinates [2..3 ] : Double

(f rom 6_Foundation)

2..*

0..*

+Cont rol_poi nts2..*

{ordered}

0..*

T ransf ormation

U [2..3 ] : DoubleV [2..3 ] : Double

(from 6_Foundation)

1

0..*

+Cartesian_point1

0..*

Value_wi th_unit( from 6_Foundation)

SI_unit_name

metregram

(f rom 6_Foundation)

<<enumeration>>

SI_prefix

mi l l icentim icroki lo

(f rom 6_Foundation)

<<enumeration>>

Unit_dim ension

squarecubic

(from 6_Foundation)

<<enumeration>>

Unit

Un it_na me [0..1 ] : StringSi_un it_na me [0.. 1] : SI_unit_nam eSi_prefi x [0.. 1] : S I_p re fixSi_d imensi on [0 ..1] : Uni t_d imen sion...

(from 6_Foundation)

1

0..*

+Unit_component1

0..*

11

11

11

Figure 19: UML diagram 16: Miscellaneous

Page 67: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 67 of 69

Copyright: VDA

Ha rne ss(f rom 1_Harness) Accessory

(from 2_Parts)

Assem bly_part(from 2_Parts)

Cavity_plug(from 2_Parts)

Cavity_seal(from 2_Parts)

Co_pack_part(from 2_Parts)

Fi xing(f rom 2_Parts)

General_terminal(f rom 2_Parts)

General _wi re(from 2_Parts)

Wire_protection(from 2_Parts )

Approval(from 6_Foundation)

Crea ti on(from 6_Foundation)

External_reference(from 6_Foundation)

Node(f rom 5_Topo log y)

Routi ng(f rom 5_Topolog y)

Unit(from 6_Foundation)

Connector_housing(from 2_Parts)

Segment(from 5_Topolog y)

Com ponent(from 2_Parts)

Cartesian_point(from 6_Foundation)

Dimension_specifi cati on(from 5_Topology)

KBL_conta iner(from 1_Harness)

0 .. 1

1

+Harness

0 .. 1

1

0..*

1

+Accessory

0..*

1

0..*

1

+Assembly_part

0..*

1

0.. *

1

+Cav it y_ plu g

0.. *

1

0.. *1

+Cavity_seal

0.. *1

0 .. *

1

+Co_pack_part

0 .. *

1

0.. *

1

+Fixing

0.. *

1

0..*

1

+General_terminal

0..*

1

0..*

1

+General_wire

0..*

1

0..*

1

+Wire_protection

0..*

1

0..*

1

+Approval

0..*

1

0..*

1

+Creation

0..*

1

0..*

1

+ Ext ernal _refe re nce

0..*

1

0.. * 1

+Node

0.. * 1

0 .. *

1

+Routing

0 .. *

1

0..*

1

+Uni t

0..*

1

0..*

1 +Connector_housing

0..*

10..* 1

+Segm ent

0..* 1

0..*

1

+Component0..*

1

0..*

1

+Cartesi an_ point

0..*

1

0..*

1

+Dime nsi on_ spe ci fi ca ti on

0..*

1

Figure 20: UML diagram 17: KBL_Container

8 XML Representation of the Harness Description List

This recommendation specifies a XML schema for the XML based exchange of harness design data. The XML schema has been derived from the objects defined in section 6 and the UML model given in section 7.

The projection onto XML schema has been guided by the rules given in the OMG standard PLM Services ([OMGPLM]). Figure 21 shows the mapping exemplary for the object Part.

A complete listing of the XML Schema is given in Annex A.

Page 68: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 68 of 69

Copyright: VDA

Figure 21: Example Mapping to the KBL XML Schema

Page 69: Copyright: VDA - Harness Description List... · - Independency of harness data from proprietary software tools - Simple comparability of development status and variants - Standardized

VDA Recommendation 4964 1st Edition, November 2005 Page 69 of 69

Copyright: VDA

Annex A KBL XML Schema

This annex is distributed as a separate document.

Annex B Mapping to ISO 10303-212

This annex is distributed as a separate document.

Annex C References

[CC8Rec] Fischer, Manfred; Sachers, Markus: CC8 Recommended Practices - Specification

and Configuration / Product Coding / Documents and Transformation Matrices.

ProSTEP iViP Recommendation, 2002.

[CESAK] N.N.: Leitfaden zur Erstellung von Elektrikbauteilen mit CATIA V5. CES-AK der dt.

Automobilindustrie, 2004.

[Fowler] Fowler, Martin: UML Distilled, Second Edition: A brief Guide to the Standard Object

Modeling Language; Addison-Wesley, 2003.

[ISO10303] N.N.: Industrial automation systems and integration – product data representation

and exchange – Part 212: Application protocol: Electrical Design and installation.

ISO, Geneva, 2000.

[OMGPLM] N.N.: Product Lifecycle Management Services Specification. OMG Adopted

Specification dtc/04-11-04, November 2004