Harness Description List (KBL)

Transcription

1 VDA Recommendation 4964 st Edition, November 2005 Page of 69 Harness Description List (KBL) VDA 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 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 st Edition, November 2005 Project Group "Car Electric" of VDA Working Group "CAD/CAM" Published by: Verband der Automobilindustrie Copyright Westendstraße 6 Reprinting or reproduction in any Postfach form are permitted only if the Frankfurt source is cited. Phone: +49 (0)69/ Fax: +49 (0)69/ Internet: [email protected]

2 VDA Recommendation 4964 st Edition, November 2005 Page 2 of 69 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.

3 VDA Recommendation 4964 st Edition, November 2005 Page 3 of 69 Contents PREAMBLE GOALS OF THE RECOMMENDATION SCOPE AND RESPONSIBILITIES STRUCTURE OF THE RECOMMENDATION GLOSSARY OF TERMS Accessory (Zubehör) Alias part (Alternativ Sachnummer) Assembly part (Baugruppe) Block Diagram (Blockschaltbild) Bundle (Leitungsbündel) Cavity (Kontaktkammer) Cavity Plug (Blindstopfen) Cavity Seal (Kontaktkammerdichtung) Cable (Leitung) Cable Drawing (Kabelzeichnung) Circuit Diagram (Funktionszeichnung) Connection (Verbindung) Connection Diagram (Verbindungszeichnung) Connector (Steckverbinder) Connector housing (Steckergehäuse) Connector list (Steckerliste) Contact (Kontakt) Co pack part (Kabelbaumzubehör) Core (Kabelader) Extremity (Kabelende) Fixing (Kabelbefestigung) Function Diagram (Funktionsplan)...2

4 VDA Recommendation 4964 st Edition, November 2005 Page 4 of Harness (Kabelbaum) Harness configuration (Kabelbaum variante) Housing (Steckergehäuse) Form board (Formbrett) Module (Leitungsstrangmodul) Module configuration (Modulumfang) Module family (Modulfamilie) Netlist (Verbindungsliste) Node (Knotenpunkt) Part (Bauteil, Komponente) Part master data (Stammdaten eines Bauteils) Part list (Stückliste) Part substitution (Bauteiltausch) Plug (Steckeraufnahme) Protection area (Geschützter Bereich) Schematic Design (Schaltplan) Segment (Verbindungsabschnitt) Slot (Steckplatz) Special wire occurrence (Mehrdrahtleitung) System Design (Systemschaltplan) Terminal (Kontakt) Topology (3D Bauraum) Wire (Leitung) Wire length (Leitungslänge) Wire protection (Leitungsschutz) DEFINITION OF THE KBL OBJECTS AND ATTRIBUTES Packages harness and modules part master data part structure connectivity...7

5 VDA Recommendation 4964 st Edition, November 2005 Page 5 of topology and routing foundation Object definitions Accessory Accessory_occurrence Alias_identification Approval Assembly_part Assembly_part_occurrence B_spline_curve Cartesian_point Cavity Cavity_occurrence Cavity_plug Cavity_plug_occurrence Cavity_seal Cavity_seal_occurrence Change Co_pack_occurrence Co_pack_part Component Component_occurrence Connection Connector_housing Connector_occurrence Contact_point Core Core_occurrence Creation Cross_section_area Dimension_specification External_reference Extremity Fixing Fixing_assignment Fixing_occurrence General_terminal General_wire General_wire_occurrence Harness Harness_configuration Installation_instruction KBL_container Material Module Module_configuration Module_family Node Numerical_value Part Part_substitution Part_with_title_block Processing_instruction Protection_area Routing...43

6 VDA Recommendation 4964 st Edition, November 2005 Page 6 of Segment Slot Slot_occurrence Special_terminal_occurrence Special_wire_occurrence Specified_accessory_occurrence Specified_cavity_plug_occurrence Specified_cavity_seal_occurrence Specified_co_pack_occurrence Specified_component_occurrence Specified_connector_occurrence Specified_fixing_occurrence Specified_special_terminal_occurrence Specified_special_wire_occurrence Specified_terminal_occurrence Specified_wire_occurrence Specified_wire_protection_occurrence Terminal_occurrence Tolerance Transformation Unit Value_range Value_with_unit Wire_colour Wire_length Wire_occurrence Wire_protection Wire_protection_occurrence Wiring_group KBL REFERENCE MODEL XML REPRESENTATION OF THE HARNESS DESCRIPTION LIST...67 ANNEX A KBL XML SCHEMA...69 ANNEX B MAPPING TO ISO ANNEX C REFERENCES...69

7 VDA Recommendation 4964 st Edition, November 2005 Page 7 of 69 List of figures Figure : Harness Design Process...8 Figure 2: Scope of the KBL within the harness design process...0 Figure 3: High Level Planning Model...5 Figure 4: UML diagram : 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 0: UML diagram 7: Part usage list ()...59 Figure : UML diagram 8: Part usage list (2)...60 Figure 2: UML diagram 9: Part usage list (3)...60 Figure 3: UML diagram 0: Part usage list (4)...6 Figure 4: UML diagram : Part usage list (5)...62 Figure 5: UML diagram 2: Part usage list (6)...63 Figure 6: UML diagram 3: Topology and routing ()...64 Figure 7: UML diagram 4: Topology and routing (2)...65 Figure 8: UML diagram 5: Dimensions...65 Figure 9: UML diagram 6: Miscellaneous...66 Figure 20: UML diagram 7: KBL_Container...67 Figure 2: Example Mapping to the KBL XML Schema...68

8 VDA Recommendation 4964 st Edition, November 2005 Page 8 of 69 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. Functional Network (TA) System Layout & Spec. Diagram System Circuit Diagram Service Documentation Electrical Data Base STEP AP 22 KBL Harness Concept Harness Design Harness Detailing Harness Documentation Source: BMW AG Figure : 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 Electrical Design and Installation [ISO0303] should be used for this purpose.

9 VDA Recommendation 4964 st Edition, November 2005 Page 9 of 69 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

10 VDA Recommendation 4964 st Edition, November 2005 Page 0 of 69 System Diagram Wiring Diagram Electric Service Diagram Connection List Part List Component Library Module Konfiguration Mechanical CAD Digital Harness Mock-Up Layout Topoloiy 3D Wire List ideal length position segme ntation KBL V2 Component Library Harness Harness Harness Drawing Manufacturing Harness 2D Formboard 2,5D 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 Glossary of terms 5. 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: my23, alias part: your_part23

11 VDA Recommendation 4964 st Edition, November 2005 Page of 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 -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.0 Cable Drawing (Kabelzeichnung) 2D view of a single cable 5. Circuit Diagram (Funktionszeichnung) Diagram of functionality with all needed parts and their connections 5.2 Connection (Verbindung) A connection specifies the electrical connectivity between two or more contacts. 5.3 Connection Diagram (Verbindungszeichnung) Diagram with all connections, cables and bundles are shown with individual conductors. 5.4 Connector (Steckverbinder) CONNECTORS are components, which terminate conductors for the purpose of providing connection and disconnection to a suitable mating component. 5.5 Connector housing (Steckergehäuse) Body of the connector with -m slots containing -n cavities 5.6 Connector list (Steckerliste) The tabular representation of a circuit diagram. The table shows all point to point connections and the connector pins.

12 VDA Recommendation 4964 st Edition, November 2005 Page 2 of Contact (Kontakt) Active part of the connector, which connects electrical --- equal to terminal 5.8 Co pack part (Kabelbaumzubehör) A part, which is supplied and installed together with the wiring harness, but without any electrical connection. 5.9 Core (Kabelader) A core is part of a cable. A cable consists of -n cores 5.20 Extremity (Kabelende) The endpoints of the wire or core. 5.2 Fixing (Kabelbefestigung) Accessory part of the harness, used to fix the position Function Diagram (Funktionsplan) Diagram that describes the functionality of a complex environment 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 Harness configuration (Kabelbaum variante) A superset of all available functions (50%) is described in function diagram. The harness configuration describes the harness of useful car configurations 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 Module configuration (Modulumfang) The set of attributes and the parts list of an individual module..

13 VDA Recommendation 4964 st Edition, November 2005 Page 3 of 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 Netlist (Verbindungsliste) List of all connections and connectors 5.3 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 Part master data (Stammdaten eines Bauteils) Database with the description of the part, metadata, datasheet, CAD drawings, etc 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 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 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 Slot (Steckplatz) A slot is a group of cavities within a connector housing, fitting to a mating housing or an electrical component 5.4 Special wire occurrence (Mehrdrahtleitung) Mechanism to describe multi core cables in a module part list System Design (Systemschaltplan) Top-level view of a complex environment

14 VDA Recommendation 4964 st Edition, November 2005 Page 4 of 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 Wire (Leitung) A solid or stranded group of solid cylindrical conductors, together with any associated insulation 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.

15 VDA Recommendation 4964 st Edition, November 2005 Page 5 of 69 Harness has has Connection routes has connects Module/ Configuration Cavity Routing has goes through controls Part is a Connector Segment Figure 3: High Level Planning Model 6. 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.. 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

16 VDA Recommendation 4964 st Edition, November 2005 Page 6 of 69 - KBL_container - Module - Module_configuration - Module_family 6..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..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

17 VDA Recommendation 4964 st Edition, November 2005 Page 7 of 69 - 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..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..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..6 foundation

18 VDA Recommendation 4964 st Edition, November 2005 Page 8 of 69 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 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 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.

19 VDA Recommendation 4964 st Edition, November 2005 Page 9 of 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 alias_id The alias_id specifies additional identifiers for the Accessory_occurrence description The description specifies additional information about the object id The id specifies the identifier of the Accessory_occurrence installation_information The installation_information provides additional information for the installation of the Accessory_occurrence part The part specifies the Accessory that serves as a definition for this particular occurrence 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] reference_element The reference_element specifies the Connector_occurrence objects supplemented by the Accessory_occurrence 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 alias_id The alias_id specifies the identifier used in the context specified by scope and description.

20 VDA Recommendation 4964 st Edition, November 2005 Page 20 of description The description specifies the type of the Alias_identification. Example: The description may be, e.g., 'inventory number' scope The scope specifies the organization in which the Alias_identification is valid 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 date The date specifies the date when the Approval actually became valid department The department specifies the department name of the personnel responsible for the Approval 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 name The name specifies the name of the personnel responsible for the Approval 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 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 components The components specifies the Parts of which the Assembly_part consists.

21 VDA Recommendation 4964 st Edition, November 2005 Page 2 of 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 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 alias_id The alias_id specifies additional identifiers for the Assembly_part_occurrence description The description specifies additional information about the object id The id specifies the identifier of the Assembly_part_occurrence installation_information The installation_information provides additional information for the installation of the Connection part The part specifies the Assembly_part that serves as a definition for this particular occurrence 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] 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 and they differ by a positive constant from the preceding knot. In this case the knot spacing is.0, starting at -d, where d is the degree. Note: polyline. If the B-spline curve is uniform and degree=, the B-spline is equivalent to a The data associated with a B_spline_curve are the following:

22 VDA Recommendation 4964 st Edition, November 2005 Page 22 of 69 - control_points - degree control_points The list of control points for the curve. The list shall contain at least 2 elements degree The algebraic degree of the basis functions 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 coordinates The coordinates specify the coordinates of the Cartesian_point. The third coordinate will not exist in the case of a two-dimensional point 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 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 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 associated_plug The associated_plug specifies the plug the cavity is equipped with part The part specifies the Cavity that serves as a definition for this particular occurrence 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:

23 VDA Recommendation 4964 st Edition, November 2005 Page 23 of 69 - colour - plug_type colour The colour specifies the colour of the Cavity_plug 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 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 part The part specifies the Cavity_plug that serves as a definition for this particular occurrence 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 colour The colour specifies the colour of the Cavity_seal 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 wire_size The wire_size specifies the size range of the wires the seal fits 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

24 VDA Recommendation 4964 st Edition, November 2005 Page 24 of part The part specifies the Cavity_seal that serves as a definition for this particular occurrence 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 approver_department The approver_department specifies the department of the personnel who approved the Part approver_name The approver_name specifies the name of the personnel who approved the Part change_date The change_date specifies the date the change was performed change_request The change_request specifies the activity, which triggers one or more changes. Example: Change request, AEKO, VV; Modellpflegepunkt description The description specifies additional information about the change designer_department The designer_department specifies the department of the responsible design engineer id The id specifies the identifier by which a certain change can be referenced. Example: Reference of a fax, note, etc responsible_designer The responsible_designer specifies the responsible design engineer 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

25 VDA Recommendation 4964 st Edition, November 2005 Page 25 of 69 - description - id - installation_information - part alias_id The alias_id specifies additional identifiers for the Co_pack_occurrence description The description specifies additional information about the object id The id specifies the identifier of the Co_pack_occurrence installation_information The installation_information provides additional information for the installation of the Co_pack_occurrence part The part specifies the Co_pack_part that serves as a definition for this particular occurrence 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 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 Component A Component is an object, which belongs to the harness. Example: Fuse, fusebox, relay sockets 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 alias_id The alias_id specifies additional identifiers for the Component_occurrence.

26 VDA Recommendation 4964 st Edition, November 2005 Page 26 of description The description specifies additional information about the object id The id specifies the identifier of the Component_occurrence mounting The mounting specifies the Cavity_occurrence, Slot_occurrence, or Connector_occurrence, which is associated with the Component_occurrence part The part specifies the Component_occurrence that serves as a definition for this particular occurrence 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 description The description specifies additional information about the object External_reference The external_references specifies references to documents. Example: Schematic diagram for the connection extremities The extremities specify Extremity objects, which reference the Contact_points connected by this Connection. Note: There shall be at least two objects specified 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 installation_information The installation_information provides additional information for the installation of the Connection processing_information

27 VDA Recommendation 4964 st Edition, November 2005 Page 27 of 69 The processing_information provides additional information for the processing of the Connection signal_name The signal_name specifies logical information on a Connection. Example: Packet on a bus, analogue voltage (high/low, waved) on a wire wire The wire specifies the Wire_occurrence or Core_occurrence, which realizes the Connection Connector_housing A Connector_housing is a non-populated connector, i.e. without addressed/populated cavities. I.e., a body of the connector with -n cavities. Note: shell. A Connector_housing without any slot allows for the representation of a connector The data associated with a Connector_housing are the following: - housing_code - housing_colour - housing_type - slots housing_code The housing_code specifies a coding for the type of the Connector_housing housing_colour The housing_colour specifies the colour of the Connector_housing 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 slots The slots specifies the Slots which belong to the Connector_housing 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

28 VDA Recommendation 4964 st Edition, November 2005 Page 28 of 69 - slots - usage alias_id The alias_id specifies additional identifiers for the Connector_occurrence 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 description The description specifies additional information about the object id The id specifies the identifier of the Connector_occurrence installation_information The installation_information provides additional information for the installation of the Connector_occurrence part The part specifies the Connector_housing that serves as a definition for this particular occurrence 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. For further information see [CESAK] Reference_element The reference_element specifies further Connector_occurrence objects supplemented by the Connector_occurrence Slots The slots specifies the Slot_occurrence objects which belong to the Connector_occurrence 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 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

29 VDA Recommendation 4964 st Edition, November 2005 Page 29 of 69 - contacted_cavity - id associated_parts The associated_parts specifies the Cavity_seal_occurrences, Special_terminal_occurrences, or Terminal_occurrences associated with the Contact_point contacted_cavity The contacted_cavity specifies the Cavity_objects related with the Contact_point id The id specifies the identifier of the Contact_point 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 -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 bend_radius The bend_radius specifies the bend radius of a core cable_designator The cable_designator specifies additional information to refer to a Core core_colour The Core_colour specifies the Wire_colour objects of the core. There shall be at least one element cross_section_area The cross_section_area specifies the electrical cross section of the Core id The id specifies the identifier of the Core outside_diameter The outside_diameter specifies the outer width of the Core 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.

30 VDA Recommendation 4964 st Edition, November 2005 Page 30 of 69 Example: Core_occurrence protected wire, flat band. 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 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 part The part specifies the Core that serves as a definition for this particular occurrence 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 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 date The date specifies the creation date department The department specifies the department the creator belongs to 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 name The name specifies the name of the creator Cross_section_area

31 VDA Recommendation 4964 st Edition, November 2005 Page 3 of 69 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 area The area specifies the value of the Cross_section_area value_determination The value_determination specifies information on how the cross_section_area value shall be interpreted name The name specifies the name of the creator 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 origin The origin specifies the Node or the located component that is the origin for the Dimension_specification target The target specifies the Node or the located component that is the target for the Dimension_specification Tolerance_indication The tolerance_indication specifies the value of the distance between the two elements 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

32 VDA Recommendation 4964 st Edition, November 2005 Page 32 of change_level The change_level specifies the version of the document creating_system The creating_system specifies the computer application or the machine, which is used to create the document data_format The data_format specifies the convention that was used to structure the information in the document document_number The document_number specifies the identifier of the document 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 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 location The location specifies where a document can be found in a digital or physical data storage system 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 contact_point The contact_point specifies the Contact_point, which is associated with the Extremity, and by this with the connection 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.0 the end. Intermediate contact_points are defined relative to the first one by a value between 0.0 and.0. The position_on_wire defines the ordering of the Extremities within a Connection.

33 VDA Recommendation 4964 st Edition, November 2005 Page 33 of 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 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 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 fixing The fixing specifies the Fixing_occurrence or the Accessory_occurrence, which is assigned location The location specifies the position of the fixing on the Segment. The value is given in curve parameters running from 0.0 to 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 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 alias_id The alias_id specifies additional identifiers for the Fixing_occurrence description The description specifies additional information about the object.

34 VDA Recommendation 4964 st Edition, November 2005 Page 34 of id The id specifies the identifier of the Fixing_occurrence installation_information The installation_information provides additional information for the installation of the Fixing_occurrence part The part specifies the Fixing that serves as a definition for this particular occurrence 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] 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 cross_section_area The cross_section_area specifies the electrical cross section, which can be accommodated by the General_terminal outside_diameter The outside_diameter specifies the outer width of the isolation, which can be accommodated by the General_terminal 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 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 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.

35 VDA Recommendation 4964 st Edition, November 2005 Page 35 of 69 The data associated with a General_wire are the following: - bend_radius - cable_designator - core - cover_colour - cross_section_area - outside_diameter - wire_type bend_radius The bend_radius specifies the bend radius of a wire cable_designator The cable_designator specifies additional information to refer to a General_wire core The core specifies the constituents of the multi-core wire 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 cross_section_area The cross_section_area specifies the electrical cross section of the General_wire outside_diameter The outside_diameter specifies the outer width of the General_wire 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 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 installation_information The installation_information provides additional information for the installation of the Connection length_information

36 VDA Recommendation 4964 st Edition, November 2005 Page 36 of 69 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 part The part specifies the General_wire that serves as a definition for this particular occurrence 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 components The components specifies the part occurrences and connections which belong to the Harness content The content specifies the information covered by the Harness. The following values shall be used: - harness complete set - harness subset harness_configuration The harness_configuration specifies the configurations of the Harness 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 module_configuration The module_configuration specifies the direct control of components outside of modules Harness_configuration A superset of all available functions (50%) is described in function diagram. The harness configuration describes the harness of useful car configurations. A Harness_configuration is a variant of a harness.

37 VDA Recommendation 4964 st Edition, November 2005 Page 37 of 69 The data associated with a Harness_configuration are the following: - logistic_control_information - modules 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 modules The modules specify the Module objects, which build up the Harness_configuration 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 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 installation_value The installation_value specifies the value for the kind of the Installation_instruction defined by installation_type KBL_container The KBL_container is introduced to specify the information, which can be exchanged by one file 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 material_key The material_key specifies a code by which the material can be identified 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 Module A Module is a physical part of harness electrically defined by one or more module groups including required harness furniture.

38 VDA Recommendation 4964 st Edition, November 2005 Page 38 of 69 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 content The content specifies the information covered by the Module. The following values shall be used: - variant - module module_configuration The module_configuration specifies the Module_configuration the Module represents of_family The of_family specifies the Module_family to which the Module belongs 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 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 controlled_components The controlled_components specifies the components, which are grouped by the Module_configuration 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.

39 VDA Recommendation 4964 st Edition, November 2005 Page 39 of 69 Example: LOL/LOR+CFL 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 description The description specifies additional information about the Module_family id The id specifies the identifier of the Module_family 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 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 bend_radius The bend_radius specifies the maximum bend radius at the Node. Example: cartesian_point May be used for the routing of fiber optics. The cartesian_point specifies the position of the Node with respect to the absolute car coordinate system id The id specifies the identifier of the Node processing_information The processing_information provides additional information for the processing of the Node referenced_components

40 VDA Recommendation 4964 st Edition, November 2005 Page 40 of 69 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 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 value_component The value_component specifies the quantity of the Numerical_value 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 abbreviation The abbreviation specifies a short name for a Part alias_id The alias_id specifies an additional part_number that is used to identify the Part in another organizational context (e.g. company) change The change specifies the change history of the Part company_name The company_name specifies the name of the organizational context in which the Part_number is defined.

41 VDA Recommendation 4964 st Edition, November 2005 Page 4 of copyright_note The copyright_note specifies copyright information for a Part 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 description The description specifies additional information about the Part external_references The external_references specifies references to documents 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 material_information The material_information specifies the material of a Part part_number The part_number specifies the identifier of the Part. The format of the part number is user defined (OEM specific) predecessor_part_number The predecessor_part_number specifies the part number of the predecessor of the Part processing_information The processing_information provides additional information for the processing of the Part version The version specifies the version identifier of the Part. A version cumulates and consolidates one or more single changes 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 replaced The replaced specifies the Cavity_plug_occurrence that is replaced Part_with_title_block

42 VDA Recommendation 4964 st Edition, November 2005 Page 42 of 69 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 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 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 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 preconfigured 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 model_year The model_year specifies the year of the car model project_number The project_number specifies the development order number (car or engine project) 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 instruction_type The instruction_type specifies the kind of the Processing_instruction.

43 VDA Recommendation 4964 st Edition, November 2005 Page 43 of 69 Note: There are no values pre-defined. Special values have to be negotiated between exchange partners instruction_value The instruction_value specifies the value for the kind of the Processing_instruction defined by instruction_type 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 associated_protection The associated_protection specifies the Wire_protection_occurrence associated Segment objects 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 gradient The gradient specifies the gradient of the protection. Note: The gradient is defined in mm. Gradient 5 mms means that the winding screws within a turn 5 mms along the bundle processing_information The processing_information provides additional information for the processing of the Protection_area 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 taping_direction The taping_direction specifies the direction of the taping (left/right) regarding to the Segment direction 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:

44 VDA Recommendation 4964 st Edition, November 2005 Page 44 of 69 - routed_wire - segments routed_wire The routed_wire specifies the Connection for which the Routing is defined segments The segments specify the Segment objects the course follows 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 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 center_curve The center_curve specifies the mathematical definition of the set of center curves of the Segment 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 end_node The end_node specifies the Node defining the end of the Segment end_vector The end_vector specifies the tangent of the center curve at the end position.

45 VDA Recommendation 4964 st Edition, November 2005 Page 45 of 69 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 fixing_assignment The fixing_assignment specifies the Fixing_assignment objects associated with the Segment form The form specifies information on the geometric shape of the Segment. The following values shall be used: - 'circular' - 'noncircular' id The id specifies the identifier of the Segment physical_length The physical_length specifies the arc length of the neutral phase of the segment in 3d protection_area The Protection_area specifies the Protection_area objects associated with the Segment start_node The start_node specifies the Node defining the start of the Segment 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 virtual_length The virtual_length specifies the represented length of the neutral phase of the segment in 3d 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 cavities The cavities specifies the Cavity objects belonging to the Slot id The id specifies the identifier of the Slot number_of_cavities The number_of_cavities specifies the number of cavities associated with the Slot Slot_occurrence

46 VDA Recommendation 4964 st Edition, November 2005 Page 46 of 69 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 cavities The cavities specifies the Cavity_occurrence objects belonging to the Slot_occurrence part The part specifies the Slot that serves as a definition for this particular occurrence 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 alias_id The alias_id specifies additional identifiers for the Special_terminal_occurrence description The description specifies additional information about the object id The id specifies the identifier of the Special_terminal_occurrence installation_information The installation_information provides additional information for the installation of the Special_terminal_occurrence part The part specifies the General_terminal that serves as a definition for this particular occurrence 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. For further information see [CESAK] 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

47 VDA Recommendation 4964 st Edition, November 2005 Page 47 of 69 - special_wire_id core_occurrence The core_occurrence specifies the Core_occurrence contained in the Special_wire_occurrence special_wire_id special_wire_id='' special_wire_id=' '2 wire_number='' wire_number='3' A B part_number='234 A B part_number='234' wire_number='2' 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 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 wire_number='4' related_occurrence The related_occurrence specifies the Accessory_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Cavity_plug_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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:

48 VDA Recommendation 4964 st Edition, November 2005 Page 48 of 69 - related_occurrence - related_assembly related_occurrence The related_occurrence specifies the Cavity_seal_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Co_pack_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Component_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Connector_occurrence it is an occurrence of related_assembly The related_ assembly specifies the Assembly_part_occurrence in which the occurrence is used.

49 VDA Recommendation 4964 st Edition, November 2005 Page 49 of 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 related_occurrence The related_occurrence specifies the Fixing_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Terminal_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Special_wire_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence

50 VDA Recommendation 4964 st Edition, November 2005 Page 50 of 69 The related_occurrence specifies the Terminal_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Wire_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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 related_occurrence The related_occurrence specifies the Wire_protection_occurrence it is an occurrence of related_assembly The related_assembly specifies the Assembly_part_occurrence in which the occurrence is used 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: Cavity. The Part_usage object specifies the usage of a Terminal_occurrence for a particular The data associated with a Terminal_occurrence are the following: - part part The part specifies the General_terminal that serves as a definition for this particular occurrence Tolerance A Tolerance is the specification of the allowable range for a dimension. The data associated with a Tolerance are the following: - lower_limit

51 VDA Recommendation 4964 st Edition, November 2005 Page 5 of 69 - upper_limit lower_limit The lower_limit specifies the minimum allowed value Upper_limit The upper_limit specifies the maximum allowed value 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 cartesian_point The cartesian_point specifies the coordinates of the translation u The u specifies the rotation by means of the y-axis v The v specifies the rotation by means of the z-axis 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 si_ dimension The Dimension specifies the dimension of a SI_unit. Example: "square", "cubic" si_prefix The si_prefix specifies the prefix for a SI unit. Example: milli, kilo si_unit_name The si_unit_name specifies the name for a SI unit. Example: gram, metre

52 VDA Recommendation 4964 st Edition, November 2005 Page 52 of 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/00 pieces 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 maximum The maximum specifies the maximum acceptable value that is constrained by the Value_range minimum The minimum specifies the minimum acceptable value that is constrained by the Value_range 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 unit_component The unit_component specifies the unit in which the Value_with_unit is expressed 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 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: colour_value base colour, second, third 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 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).

53 VDA Recommendation 4964 st Edition, November 2005 Page 53 of 69 The data associated with a Wire_length are the following: - length_type - length_value 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 length_value The length_value specifies the length of the wire 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 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) 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 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 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 Wire_protection_occurrence A Wire_protection_occurrence is the occurrence of a Wire_protection in a module part list.

54 VDA Recommendation 4964 st Edition, November 2005 Page 54 of 69 The data associated with a Wire_protection_occurrence are the following: - alias_id - description - id - installation_information - protection_length - part alias_id The alias_id specifies additional identifiers for the Wire_protection_occurrence description The description specifies additional information about the object id The id specifies the identifier of the Wire_protection installation_information The installation_information provides additional information for the installation of the Wire_protection_occurrence protection_length The protection_length specifies the length of the Wire_protection_occurrence with respect to the wrapping 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 assigned_wire The assigned_wire specifies the Wire_occurrence and Core_occurrence objects, which are grouped together id The id specifies the identifier of the Wiring_group processing_information The processing_information provides additional information for the processing of the Wiring_group type The type specifies the type of the grouping. Example: twisted-pair.

55 VDA Recommendation 4964 st Edition, November 2005 Page 55 of 69 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]. Materi al (from 6_Foundation) M aterial_key : String Material_reference_system [0..] : String + Material_i nf ormati on +Pr oces sing_i nformatio n Processing _instruction ( from 6_Foundation ) Instruction_type : String Instruction_value : String 0.. Exter nal _r eference (from 6_Foundation) Document_type : String Document_number : String Change_level : String Fi le_name [0..] : String Location [0..] : String Data_format : Stri ng Creating _system [0..] : String Part + External_references (from 2_Parts) Part_number : String Company_name : String Alias_id [] : Alias_identification Version : String Abbreviation : String Description : String Predecessor_part_number [0..] : String Degree_of_maturity [0..] : String Copyrig ht_note [0..] : String Mass_information [0..] : Numerical_value + Change Change (from 6_Foundation) Id [0..] : String Description [0..] : String Change_request [0..] : String Change_date [0..] : String Responsible_designer : String Designer_department : String Approver_name [0..] : String Approver_department [0..] : String Creation ( from 6_Fo undation) Name : String Department : String Date : String +I s_applied_to..* Par t_with_title_block (from 2_Parts) Project_number [0..] : String Car_classification_level_2 : String Car_classification_level_3 [0..] : String Car_classification_level_4 [0..] : String Model_year : String +Is_ap plied_to..* Approval (fr om 6_Fo und at ion) Name [0..] : String Department [0..] : String Date : String Type_of_approval : String M odule ( from _Harness) Content : Module_content +Module 0..* + Harness_configuration Harness Harness_config uration (from _Harness) (from _Harness) Content : Harness_content Logistic_control _information [0.]: Str ing..* +M odules Figure 4: UML diagram : Common part attributes and properties

56 VDA Recommendation 4964 st Edition, November 2005 Page 56 of 69 Par t (from 2_Parts) Fixing (from 2_Parts)...) C o_pack_part (fr om 2_Parts) Cav ity _plug (fr om 2_Parts) Accesso ry (fr om 2_Parts) W ire_protection (from 2_Parts) C om ponent (fr om 2_Parts) General_wire (fr om 2_Parts) C onnector_housing (from 2_Parts) Cav ity _seal (fr om 2_Parts) Assembly _part (from 2_Parts) General_t erminal (from 2_Parts) Part_wit h_t it le_block (from 2_Part s) Module +Module (fr om _Harness)...) H arness (fr om _H arness)...) Figure 5: UML diagram 2: Part specializations W irin g _g roup (from 4_Connectiv... Id : String Ty pe [0..] : String Spec ial_te rminal_o c c ur re n c e (from 3_Part_struct... Id : String Alia s _id [] : Alias _ide ntifica tion Description [0..] : String Plac emen t [0..] : Tran s formation C av ity _ s ea l_oc c ur re nc e (from 3_Part_structure) Terminal_o c c ur r en c e (from 3_Part_structure) Conn ection (from 4_Connectiv... Id [0..] : Strin g D es cr iption [0.. ] : Strin g Signal_n a me [0..] : Strin g C o_ pack _oc c urr e nc e (from 3_Part_struct... Id : String Alias _id [] : Alias _ide ntifica tion Des cription [0..] : String W ire _ pr otec tion_o c c ur r en c e (from 3_Part_struct... Id :Str ing A lias _ id [0..*] : A lias _ iden tifica tion D esc riptio n [0.. ] : S tring P rotec tion_leng th [0.. ] : Num er ic al_v a lue +C ompo n en ts 0..* <<Selector >> C on ne ction_o r _o ccur renc e (from _H arn... +C on tro lled_c ompo ne nts C on nec t or _o c cur ren c e (from 3_Part_struct... Id :Str ing Alias _id[0..*] : Alias _ide ntific ation D esc ripti on [0..] : String Usag e [0..] : C onn ecto r _us age Place men t [0.. ] : T rans fo rm ation 0..* + Re fe re nc e _e lement C ompo ne nt_o c c ur r en c e (fro m 3_P art_s tructur e) Acc es s o ry _o c c ur r en c e (from 3_Part_struct... Id :Strin g Ali as _i d []: Alia s _i den t ific ation D es cr iption [0..] : Strin g Plac emen t [0..] : Tra nsfo rmation C av ity_p lug_ oc curren ce (from 3_Part_struct... Fix ing_ oc c ur re nc e (from 3_Part_struct... Id : Strin g Alias _id [0..*] : Alias _ide n tific ation Des cription [0..] : String Plac emen t [0.. ] : Tra ns for mation Gen e ra l_w ire _o c c ur r en c e (from 3_Part_struct... Ass embly _p ar t_oc c u rre nc e (from 3_Part_struct... Id : Strin g Alias _id [] : Alias _id en tification D es crip tio n [0..] : String Plac emen t [0..] : Tran s fo rmation <<en umer ation>> H ar ne s s (from _Harn... C on te nt : Ha rn es s _c on tent +Mod ule_ c o nfigur ation Modu le_c on figur ation (from _Harn... Lo gistic_c on trol_ infor mation : Str ing Configuration_ type [0.. ] : Module _configura tion_ type Modu le_c on figur ation _ty pe (from _Harn... op tio n c od e <<en u mer ation >> H arn e ss _ co nt ent (from _H arn... ha rnes s co mplete s et ha rnes s subs et +Mod ule_ families Modu le_family (from _H arn... +Of_family +Mod ule _c on figura tion Id : String Des cription [0..] : String 0.. +H ar ne s s _ c on fig ur ation H arn ess _ con figur ation (from _Harn... Lo gi s tic _ M odu le (from _Harn... C on t en t : +Mod ule << en umer a tion>> Modu le_c on tent (from _Harn... +Mod ules..* mod ule v ar ia Figure 6: UML diagram 3: Harness and modules

57 VDA Recommendation 4964 st Edition, November 2005 Page 57 of 69 Connector_housing (from 2_Pa... Housing_colour [0..] : String Housing_code [0..] : String Housing_type [0..] : String +Slots Slot ( fr om 2_ Pa... Id [ 0..] : String Number_of_cavities : Integer +Cavities..* Cavity (from 2_ Pa... Cavity_number : String General_wire ( fro m 2_Pa... Cable_designator [0..] : String Wire_type [0..] : String Bend_radius [0..] : Numerical_value Cross_section_area [0..] : Numerical_value Outside_diameter [0..] : Numerical_value +Cover_colour.. * W ire_colour ( fro m 6_Fou ndat... Colour_type : String Colour_value : String..* + Core_colour + Core Core ( fr om 2_ Pa... Id : St ring Cable_designator [0..] : String Wire_type [0..] : String Cross_section_area : Numerical_value Outside_diameter [0..] : Numerical_value Bend_radius [0..] : Numerical_value General_terminal (from 2_ Pa... Terminal_type [0..] : String Plating_material [0..] : String Cross_section_area [0..] : Value_range Outside_diameter [0..] : Value_range Cavity_seal (from 2_ Pa... Colour [ 0..] : S tr ing Seal_type [0..] : String Wire_size [0..] : Value_range Cavit y_plug (from 2_ Pa... Colour [0.. ] : S tr ing Plug_t ype [0..] : S tr ing Co_pack_part ( from 2_Pa.. Accessory (from 2_ Pa.. Accessory_type [0..] : String Assembly_part (from 2_ Pa... P art_t ype [0..] : S tr ing Part_type [0..] : String Alias_identif icat ion ( fr om 6_ Foundat.. Alias_id : String Scope [0.. ] : St ring Description [0..] : String F ixing ( from 2_Pa.. Fixing_type [0..] : String W ire_prot ection (from 2_ Pa... Protection_type [0..] : String Type_dependent_paramet er [0..] : St ring Figure 7: UML diagram 4: Part master data

58 VDA Recommendation 4964 st Edition, November 2005 Page 58 of 69 +Modu le Module (from _Harness)...) P art (from 2_Parts) Harness (from _Harness)...) +Module_conf iguration Mo dule _conf igurati on (from _Harness) +Module_conf iguration +Controlled_com ponents <<Se lect or>> +Compo nent s Connection_or_occ urrenc e (from _Harness) Connector_housing (from 2_Parts) +Pa rt +Slots Slot (from 2_Parts) +Par t Terminal _occurr ence (from 3_Part_structure) +Part..* General_terminal (from 2_Parts) +Cav ities..* Cav ity (from 2_Parts) Connection ( fr om 4 _Con nec ti vity ) +Routed_wi re +Ex tremities 2..* Extrem ity (from 4_Connectivity)...) +Contac t_point Contact_point (from 4_Connectivity) +Part +Ref erence_element +Contact_points..* Cav ity _occurrence Connec tor_oc currence +Contacted_cav ity (from 4_Connectivity ) (from 3_Part_structure)..*..*..* +Cav ities Routing +Segments (from 5_Topology)...) {ordered} Seg me nt (from 5_Topology)... ) Slot_occurrence (from 4_Connectivity) +Slots..* Figure 8: UML diagram 5: Connection overview

59 (f rom _Harn... (f rom 2_Pa... (f r om 3_Part _st ruc t... ( fr om 3_ Par t_st r uct... (f r om 3_Part _st ruct ure) ( from _Har ness) ( fr om 3_Par t_st r uct ure) (f r om 3_Par t _st ruct... (f r om 3_Part _st ruct... ( fr om 3_ Part _st r uct... ( f rom 6_Foundat... (f r om 3_Par t _st ruct... ( f rom 3_Pa r t_st r uc t ur e) (f rom 3_Par t _str uct... (f rom 3_Par t _str uct ure) ( fr om 3_Part _st ruc t... VDA Recommendation 4964 st Edition, November 2005 Page 59 of 69 External_reference (fr om 6_ F ounda tion ) Document_type : String Document_number : String Change_level : String File_name [0..] : String Location [0..] : String Data_format : String Creating_system [0..] : String Cavity_plug_occurrence (from 3_Part _structure) + Exter nal _references 0.. +Associated_plug Connector_occurrence (from 3_Part_structure)..* Cavity_occurrence (from 4_Connectivity)..* +Contact ed_cavit y Extremity (from 4_Connectivity) Position_on_wire : Double 2..* +Extremities Connection (fr om 4_ Con nec tivit y) 0..* Id [0..] : String Description [0..] : String Sig nal_name [0..] : String +Processi ng_information +Installation_information Installation_instruction (from 6_Foundation) Instruction_type : String Instruction_value : String Processing _instruction (from 6_Foundation) Instruction_type : Str ing Instruction_value : String + Process ing _i nformation +Contact_points Contact_point (from 4_Connectivity) Id : Str ing..* +Contact_point +Wire <<Selector> > W ire_or_core_occurrence (from 4_Connectivity) 2..* +Assigned_wire Wiring_g roup (from 4_Connectivity) Id : String Type [0..] : String +Associated_parts <<Selector> > Part_usage_select (fr om 3_ Par t _st ruc ture ) Core_occurrence (fr om 3_ Par t_st ruc ture ) Wire_number : String Wire_occurrence (from 3_Part_structure) Wire_number : String Figure 9: UML diagram 6: Connectivity +Components +Components <<Selector>> Connection_or_occurrence A ssembly_part_occurrence Id : String A lias_id [] : A lias_identification Des cription [0..] : String P lacement [0..] : Transformation Id : String A ccessory_occurrence A lias _id [ ] : Al ias_identification Desc ription [0..] : String P lacement [0..] : Transformation Cav ity_seal_occurrence Component_occurrence Id : S tring A lias_id [] : A lias_identification Description [0..] : String Fixing_occurrence Id : S tring Alias_id [ ] : Al ias_identifica tion Description [0..] : String Pl acement [0..] : Transformation S pecial_terminal_occurrence Id : String A li as_id [ ] : Al ias_identifica tion De scription [0..] : String P lacement [0..] : Transformation W ire_protection_occurrence Id : String A li as_id [ ] : Al ias_identifica tion De scription [0..] : String P rotection_length [0..] : Numerical_value..* Cavi ty_plug_occurrence Co_pack_occurrence Connector_occurrence +Pa rt Id : S tring Alias_id [ ] : Al ias_identifica tion Description [0..] : String Id : String A lias _id [ ] : A lias _identification Desc ription [0..] : S tring Usage [0..] : Connector_usage P lacement [0..] : Transformation Ge neral_wir e_occu rrence Terminal_occurrence Harn ess A ssembly_part Content : Harness_content P art_type [0..] : String +Installation_information +Installation_information +Installation_information +Installation_information +Installation_information Installation_instruction Instruction_type : String Instruction_value : String +Installation_information +Installation_information +Installation_information Figure 0: UML diagram 7: Part usage list ()

60 VDA Recommendation 4964 st Edition, November 2005 Page 60 of 69 C on nector _h ousing (from 2_P a... Housing _col ou r [0.. ] : Str ing Housing _cod e [0. ] : S trin g Housing _type [0..] : String +Slots Slot (from 2_P a... Id [0..] : String Number _of_cavities : Integer +Cavitie s..* Cav ity (from 2_P a... Cavity_number : String << enumeration>> C on nector _u s age (f rom 3 _Pa rt_ str uc t.. +Part +Part +Par t no end ring termin al s plice dang le r..* Ac c ess ory _occ urre nce (from 3_P art_struct... Id : Stri ng Alias _id [] : Alias _i denti fic ation De scription [0.. ] : String P la ceme nt [ 0.. ]: Tra ns for mation +R eferenc e_ele ment..* Conne c tor_occ urre nce (f rom 3 _P art_str uct.. Id : Strin g Alias_id [] : Alias_identification Description [0..] : String Usage [0..] : Connector_usage Placement [0..] : Transfor mation..* Slot_o cc urr ence (from 4_Connectivity) +Slots +Refer en c e_ element +C avities..*..* Cav ity_ oc curr.. (from 4_Connectivity)... +R elated_o c curren c e Spe c ified_ac c es s ory _occ urr... (from 3_Part_structure) 0.* +R elated_o c c ur renc e Spec ified _c onne c tor_occ urre nce (from 3_P art_structure) +Ass oc iated_ plu g 0.. C a v ity _pl ug_ o ccu rre nce (from 3_Part_structure) +Par t Ac c es s or y (from 2_P a... Ac ces sory _type [0..] : String +R elated_a s s embly Ass embly _p art_oc curren c e (from 3_P art_struct... Id : Strin g Alias_id [] : Alias_iden tification Description [0..] : String Placement [0..] : Transfor mation +R ela ted_ass embly Figure : UML diagram 8: Part usage list (2) G eneral _wir e (fro m 2_Pa... Cable_designator [0..] : String..* Wire_type [0..] : String Bend_radius [0..] : Numerical_value Cr oss_section_area [0..] : Numerical_value... Outside_diameter [0..] : Numerical_value +P art General_wire_occurrence (from 3_Part_s truct.....* +Length_information Wire_length ( from 6 _Fo un da t... Length_type : String Length_value : Numerical_value..* +Length_information Wire_occurrence (from 3_ Part_s truc t... Wire_number : String +Related_occurr ence Sp ecia l_wire_occur rence (from 3_Part_ struct... Special_wire_id : String Cor e_occurrence + Core_occurr ence (fro m 3_Part_s truc t... Wire_number : String..* +Related_occurrence Sp ecifi ed_wire_occ ur rence (from 3_ Part_s truc t... Sp ecifi ed_spec ial_wire_occ urren ce (from 3_Par t_ struct... +Related_assembly As sembly_part_occ ur rence (from 3_ Part_s truc t... Id : String Alias_id [] : Alias_identification Description [0..] : String Placement [0..] : Transformation +Related_assembly Core +Part (from 2_ Pa... Id : String Cable_designator [0..] : String Wir e_type [0..] : String Cross_section_area : Numerical_value Outside_diameter [0..] : Numerical_value Bend_radius [0..] : Numerical_value + Cor e Figure 2: UML diagram 9: Part usage list (3)

61 VDA Recommendation 4964 st Edition, November 2005 Page 6 of 69 Fixing (from 2_Parts) Fixing_ty pe [0..] : String... Co_ pack _part (fr om 2_Parts) Part _ty pe [0..] : Strin... g +Part +Part..* Fixing_occurrence (from 3_Part_structure) Id : String Alias_id [] : Alias _identif ication... Description [0..] : String Placement [0..] : Transformation... +Related _oc currence..* Co_pack_oc currence (from 3_Part_structure) Id : String Alias_id [] : Alias_identif ication... Description [0..] : String +Related _oc currence Specif ied_f ixing_occurrence +Related_as sembly (from 3_Part_structure) Assembly _part_occurrence +Related_assembly Specif ied_ co_ pack_oc currence (from 3_Part_structure) ( fro m 3_ Pa rt_ str uct ure) Id : String Alias_id [] : Alias _identif ication... Specif ied_wire_protection_occurrence Description [0..] : String +Related_assembly Placement [0..] : Transf ormation... Specif ied_ cav ity _seal_oc currence (from 3_Part_structure) (from 3_Part_structure) +Related _as sembly +Related_occurrenc e W ire_ protection _oc currence (from 3_Part_structure) Id : String Alias_id [] : Alias _identif ication Description [0..] : String Protection_length [0..] : Numerical_v... alue..* +Part Wire_protection (from 2_Parts) Protection_ty pe [0..] : String Type_dependent_parameter [0..] : String... +Rela ted_oc currence Cav ity _seal_occurrence (from 3_Part_structure)..* +Part Cav it y _se al (from 2_Parts) Colour [0..] : String Seal_ typ e [0..] : String Wire_size [0..] : Value_range... Figure 3: UML diagram 0: Part usage list (4)

62 VDA Recommendation 4964 st Edition, November 2005 Page 62 of 69 Part_substitution ( fr om 3_Part_s truc ture) +Repl acing <<Sel ector>> Part_usage_select ( fr om 3_Part_s truc ture) Cavity_seal_occurrence (from 3_Part_s tr uc tur e) General_terminal (from 2_Pa... Terminal_type [0..] : String Plating _material [0..] : String Cross_section_area [0..] : Value_range Outside_diameter [0..] : Value_range +Replaced Cavity_plug_occurrence +Part (from 3_Par t_s truc ture)..* +Related_occurrence +Related_assembly Cavity_plug ( fr om 2_Pa... Colour [0..] : Stri ng Plug _type [0..] : String +Part +Par t Specified_cavity_plug_occurrence ( fr om 3_Part_s truc ture) +Related_occurrence..* Special_terminal_occurrence ( fr om 3_Part_s truc t.. Id : String Alias_id [] : Alias_identification Description [0..] : String Placement [0..] : Transformation..* Terminal_occurrence ( fr om 3_Part_s truc ture) Assembly_part_occurrence +Rel ated _occurr ence ( fr om 3_Part_s truc t... Id : String Alias_id [] : Alias_identification Description [0..] : String Placement [0..] : Transformation +Related_assembly Specified_terminal_occurrence +Related_assembly ( fr om 3_Part_s truc ture) Specified_special_terminal_occurrence (from 3_Par t_s truc ture ) Figure 4: UML diagram : Part usage list (5)

63 VDA Recommendation 4964 st Edition, November 2005 Page 63 of 69 Speci fied_co m ponent_occurrence (from 3_Part_structure) +Related_assembly Assembly_part_occurrence (from 3_Part_structure) Id : String Alias_id [] : Alias_identification... Description [0..] : String Placement [0..] : T ransformation C ompo nen t (fr om 2_Parts) +Part..* +Related_occurrence Component_occurrence (from 3_Part_structure) Id : String Alias_id [] : Alias_identification... Description [0..] : String 0.. * +Mounting..* <<S elector>> Mou ntin g_element (from 3_Part_structure) Connector_occurrence (from 3_Part_structure) Id : String Alias_id [] : Alias_identification... Description [0..] : String Usage [0..] : Connector_usage Placement [0..] : Transformation +S lots 0.. * S lot_ occurrence (from 4_Connectivity) +Cavi ties..* Cavity_ occurrence (from 4_Connecti vity) +Reference _element Figure 5: UML diagram 2: Part usage list (6)

64 VDA Recommendation 4964 st Edition, November 2005 Page 64 of 69 Assembly_part _occurrence (from 3_P art_struct... Id : String Alias_id [] : Alias_identification Description [0..] : String Placement [0..] : Transformation Connector_occurrence (from 3_P art_struct... Id : String Alias_id [0..*] : Alias_identification Description [0..] : String Usage [0..] : Connector_usage Placement [0..] : Transformation 0.. * Fixing_occurrence (from 3_P art_struct... Id : String Alias_id [0..*] : Alias_identification Description [0..] : String Placement [0..] : T ransformation W ire_protection_occurrence (from 3_Part_struct... Id : S tring Alias_id [0.. *] : Alias_identification Description [0..] : St ring Protection_length [0..] : Numerical_value + Reference_element Acc es so ry_occurre nc e (from 3_P art_struct... Id : String Alias_id [0.. *] : Alias_identification Description [0..] : String Placement [0..] : Transformation + Reference_element Special_terminal_occurrence (from 3_P art_struct... Id : String Alias_id [0.. *] : Alias_identification Description [0..] : String Placement [0..] : Transformation < < Selector> > Locat ed_component (from 5_Topology) + referenced_com ponents Node (from 5_Topol... Id : String Alias_id [0..*] : Alias_identification Bend_radius [0..] : Numerical_value + Processing _i nformation Processing_inst ruction (from 6_Foundat... Instruction_type : String Instruction_value : String + St art_node + End _n ode 0.. * + Processing_information < < enum era tio n> > Segment_form (from 5_Topol... circular noncircular 0.. * Segment (from 5_Topol * Id : String Alias_id [0..*] : Alias_identification Start_vector [0..3] : Double End_vect or [0..3] : Double Virtual_length [0..] : Numerical_value Physical_length [0..] : Numerical_value Form [0..] : Segment_form + Segments {ordered} 0.. * Connection (from 4_Connecti v.. Id [0..] : String Description [0..] : String Signal_name [0..] : S tring 0.. * Routing (from 5_Topology) + Routed_wire + Cartesian_point Cartesian_point (from 6_Foundat... Coordinates [2..3] : Double + Control_points 2.. * {ordered} {ordered} + Center_curve B_spline_curve (from 6_Foundat... D eg ree : Inte ger + Cross_section_area_information Cross_section_area (from 6_Foundat... Value_determinati on : Value_de termination Area : Numerical_value < < enumeration>> Value_determination (from 6_Foundat... calculated reserved measured Figure 6: UML diagram 3: Topology and routing ()

65 VDA Recommendation 4964 st Edition, November 2005 Page 65 of 69 Wi re_protecti on_o ccurrence (from 3_Part_structure) Id : String Alias_id [] : Alias_identification Description [0..] : String Prote ction_length [0..] : Numerical_value +Associated_protection Pro cessi ng_ instructi on (from 6_Foundation) Instruction_type : String Instruction_value : String Protection_ are a (from 5_Topology) +Processing_information Start_location : Double End_location : Double Taping_direction [0..] : String Gradient [0..] : Value_with_unit +Protection_area Se gment (from 5_Topology) Id : String Alias_id [] : Alias_identification Start_vector [0..3] : Double End_vector [0..3] : Do uble Virtual_length [0..] : Numerical_value Physical_length [0..] : Numerical_value Form [0..] : Segment_form <<Selector>> Fixed_component (from 5_Topology) +Fixing +Fixi ng_assignment 0.. * Fixi ng_assig nment (from 5_Topology) L oca ti on : Do u ble Ori ent ation [2..3 ] : Dou bl e Fixing_occurren ce (from 3_Part_structure) Id : String Alias_id [] : Alias_identification Description [0..] : String Placement [0..] : Transformation Accessory_occu rrence (from 3_Part_structure) Id : St ring Alias_id [] : Alia s_identification Descri ption [0..] : String Placement [0.. ] : Transformati on Figure 7: UML diagram 4: Topology and routing (2) <<Selector>> Located_co mponent (from 5_Topology) +referenced_com ponents Node (from 5_Topology) Id : St rin g Ali as_id [ ] : A li as_ id entif i catio n Bend_ ra diu s [0.. ] : Num eric al_ val ue Dimensi on_specif ication +origin (from 5_Topology) +targ et << Sel ector>> Place d_el ement (from 5_Topology) 0.. T olerance (from 5_Topology) +T olerance_indication Lowe r_l im it [ 0.. ] : Nume rical _val ue Uppe r_l im it [ 0.. ] : Nume rical _val ue Figure 8: UML diagram 5: Dimensions

66 VDA Recommendation 4964 st Edition, November 2005 Page 66 of 69 <<enumeration>> SI_unit_ name (from 6_Foundation) metre gram <<enumeration>> Unit_dim ension (from 6_Foundation) square cubic B_spline_curve (from 6_Foundation) Degree : I ntege r {ordered} <<enumeration>> SI_prefix (from 6_Foundation) milli ce nti micro kilo Unit (from 6_Foundation) Un it_ na me [0.. ] : String Si_un it_na m e [0.. ] : SI_unit_nam e Si_prefi x [0.. ] : S I_p re fix Si_dim ensi on [0..] : Uni t_d im en si... on 2..* Cartesian_point (from 6_Foundation) +Cont rol_poi nt s Coordinates [2..3] : Double +Cartesian_point +Unit_ co m ponent Value_ wi th_unit (from 6_Foundation) Transf ormation (from 6_Foundation) U [2..3] : Do uble V [2..3] : Do uble Nu merica l_ val ue (from 6_Foundation) Value_component : Double Val ue_range (from 6_Foundation) Minimum : Double Maxi mum : Double Figure 9: UML diagram 6: Miscellaneous

67 VDA Recommendation 4964 st Edition, November 2005 Page 67 of 69 Approval (from 6_Foundation) Crea ti on (from 6_Foundation) External_reference (from 6_Foundation) Node (f rom 5_Topolog y) Segment (from 5_Topolog y) Routi ng (from 5_Topolog y) Cartesian_point (from 6_Foundation) Unit (from 6_Foundation) Dimension_specifi cati on (from 5_Topology) +Approval +Creation + Ext ernal _refe re nce +Node 0.. * +Segm ent 0.. * +Routing +Cartesi an_ point +Unit Ha rne ss (from _Harness) 0.. +Harness +Dime nsi on_ spe ci fi ca ti on +Accessory +Assembly_part +Cav it y_ plu g +Cavity_seal +Co_pack_part +Fixing +General_terminal +General_wire 0.. * KBL_container (from _Harness) +Component 0.. * +Connector_housing 0.. * 0.. * Accessory (from 2_Parts) Assem bly_part (from 2_Parts) Cavity_plug (from 2_Parts) Cavity_seal (from 2_Parts) Com ponent (from 2_Parts) Connector_housing Co_pack_part (from 2_Parts) Fi xing (from 2_Parts) (from 2_Parts) General_terminal (from 2_Parts) General _wi re (from 2_Parts) +Wire_protection Wire_protection (from 2_Parts ) Figure 20: UML diagram 7: 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 2 shows the mapping exemplary for the object Part. A complete listing of the XML Schema is given in Annex A.

68 VDA Recommendation 4964 st Edition, November 2005 Page 68 of 69 Figure 2: Example Mapping to the KBL XML Schema

69 VDA Recommendation 4964 st Edition, November 2005 Page 69 of 69 Annex A KBL XML Schema This annex is distributed as a separate document. Annex B Mapping to ISO This annex is distributed as a separate document. Annex C [CC8Rec] References Fischer, Manfred; Sachers, Markus: CC8 Recommended Practices - Specification and Configuration / Product Coding / Documents and Transformation Matrices. ProSTEP ivip Recommendation, [CESAK] [Fowler] [ISO0303] [OMGPLM] N.N.: Leitfaden zur Erstellung von Elektrikbauteilen mit CATIA V5. CES-AK der dt. Automobilindustrie, Fowler, Martin: UML Distilled, Second Edition: A brief Guide to the Standard Object Modeling Language; Addison-Wesley, N.N.: Industrial automation systems and integration product data representation and exchange Part 22: Application protocol: Electrical Design and installation. ISO, Geneva, N.N.: Product Lifecycle Management Services Specification. OMG Adopted Specification dtc/04--04, November 2004