Harness Description List (KBL)

(1)

VDA

Harness Description List (KBL)

4964

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

The recommendation deals with the following subject areas:

- Harness, variants and modules

- Components like connectors or wires

- Part lists

- Connectivity lists

- Topology

1st Edition, November 2005

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

Published by: Verband der Automobilindustrie Copyright

Westendstraße 61 Reprinting or reproduction in any

Postfach 17 05 63 form are permitted only if the

60079 Frankfurt source is cited.

Phone: +49 (0)69/97507-284 Fax: +49 (0)69/97507-300 Internet: [email protected]

(2)

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)

Contents

1 PREAMBLE...8

2 GOALS OF THE RECOMMENDATION...9

3 SCOPE AND RESPONSIBILITIES ...9

4 STRUCTURE OF THE RECOMMENDATION...10

5 GLOSSARY OF TERMS...10

5.1 Accessory (Zubehör)...10

5.2 Alias part (Alternativ Sachnummer) ...10

5.3 Assembly part (Baugruppe)...11

5.4 Block Diagram (Blockschaltbild) ...11

5.5 Bundle (Leitungsbündel)...11

5.6 Cavity (Kontaktkammer)...11

5.7 Cavity Plug (Blindstopfen) ...11

5.8 Cavity Seal (Kontaktkammerdichtung) ...11

5.9 Cable (Leitung) ...11

5.10 Cable Drawing (Kabelzeichnung)...11

5.11 Circuit Diagram (Funktionszeichnung)...11

5.12 Connection (Verbindung) ...11

5.13 Connection Diagram (Verbindungszeichnung)...11

5.14 Connector (Steckverbinder) ...11

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

5.16 Connector list (Steckerliste)...11

5.17 Contact (Kontakt) ...12

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

5.19 Core (Kabelader) ...12

5.20 Extremity (Kabelende) ...12

5.21 Fixing (Kabelbefestigung) ...12

(4)

5.23 Harness (Kabelbaum) ...12

5.24 Harness configuration (Kabelbaum variante) ...12

5.25 Housing (Steckergehäuse) ...12

5.26 Form board (Formbrett) ...12

5.27 Module (Leitungsstrangmodul) ...12

5.28 Module configuration (Modulumfang) ...12

5.29 Module family (Modulfamilie) ...13

5.30 Netlist (Verbindungsliste) ...13

5.31 Node (Knotenpunkt)...13

5.32 Part (Bauteil, Komponente) ...13

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

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

5.35 Part substitution (Bauteiltausch) ...13

5.36 Plug (Steckeraufnahme) ...13

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

5.38 Schematic Design (Schaltplan) ...13

5.39 Segment (Verbindungsabschnitt) ...13

5.40 Slot (Steckplatz) ...13

5.41 Special wire occurrence (Mehrdrahtleitung) ...13

5.42 System Design (Systemschaltplan) ...13

5.43 Terminal (Kontakt) ...14

5.44 Topology (3D Bauraum)...14

5.45 Wire (Leitung) ...14

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

5.47 Wire protection (Leitungsschutz)...14

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

6.1 Packages...15

6.1.1 harness and modules ...15

6.1.2 part master data ...16

6.1.3 part structure ...16

(5)

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

(6)

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

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

ANNEX A KBL XML SCHEMA...69

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

(7)

List of figures

Figure 1: Harness Design Process...8

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

Figure 3: High Level Planning Model...15

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

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

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

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

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

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

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

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

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

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

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

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

(8)

1 Preamble

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

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

Source: © BMW AG

Figure 1: Harness Design Process

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

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

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

Harness Concept Harness Design Harness Detailing Functional

Network (TA) System Layout &

Spec. Diagram System Circuit

Diagram Service Documentation

Harness Documentation

Electrical Data Base

STEP AP 212 KBL

(9)

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

(10)

Harness Drawing Harness Manufacturing Harness Digital Mock-Up Harness Layout Mechanical CAD System Diagram Service Diagram Electric Wiring Diagram Part List Component Library Connection List Wire List •ideal length •position •segme ntation Harness 2D Formboard 2,5D Topoloiy 3D Module Konfiguration Component Library

KBL V2

Harness Drawing Harness Manufacturing Harness Digital Mock-Up Harness Layout Mechanical CAD System Diagram Service Diagram Electric Wiring Diagram Part List Component Library Connection List Wire List •ideal length •position •segme ntation Harness 2D Formboard 2,5D Topoloiy 3D Module Konfiguration Component Library

KBL V2

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

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

4 Structure of the recommendation

This document is structured in the following chapters:

- Glossary of terms

- Definition of the objects and attributes

- Specification of the KBL information model

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

- Mapping of the KBL to ISO 10303-212

5 Glossary of terms

5.1 Accessory (Zubehör)

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

5.2 Alias part (Alternativ Sachnummer)

Used to describe the part number of the part in another company My part number: my123, alias part: your_part123

(11)

5.3 Assembly part (Baugruppe)

An assembly of multiple parts identified by a common part number

5.4 Block Diagram (Blockschaltbild)

Top-level function view of a complex infrastructure

5.5 Bundle (Leitungsbündel)

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

5.6 Cavity (Kontaktkammer)

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

5.7 Cavity Plug (Blindstopfen)

Connector accessory to fill and seal empty cavities

5.8 Cavity Seal (Kontaktkammerdichtung)

Connector accessory to fill and seal a populated cavity

5.9 Cable (Leitung)

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

5.10 Cable Drawing (Kabelzeichnung)

2D view of a single cable

5.11 Circuit Diagram (Funktionszeichnung)

Diagram of functionality with all needed parts and their connections

5.12 Connection (Verbindung)

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

5.13 Connection Diagram (Verbindungszeichnung)

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

5.14 Connector (Steckverbinder)

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

5.15 Connector housing (Steckergehäuse)

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

5.16 Connector list (Steckerliste)

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

(12)

5.17 Contact (Kontakt)

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

5.18 Co pack part (Kabelbaumzubehör)

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

5.19 Core (Kabelader)

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

5.20 Extremity (Kabelende)

The endpoints of the wire or core.

5.21 Fixing (Kabelbefestigung)

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

5.22 Function Diagram (Funktionsplan)

Diagram that describes the functionality of a complex environment.

5.23 Harness (Kabelbaum)

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

5.24 Harness configuration (Kabelbaum variante)

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

5.25 Housing (Steckergehäuse)

Body of the connector

5.26 Form board (Formbrett)

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

5.27 Module (Leitungsstrangmodul)

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

Example: Option: Audio System with CD Changer

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

5.28 Module configuration (Modulumfang)

(13)

5.29 Module family (Modulfamilie)

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

5.30 Netlist (Verbindungsliste)

List of all connections and connectors

5.31 Node (Knotenpunkt)

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

5.32 Part (Bauteil, Komponente)

An object with a part number.

5.33 Part master data (Stammdaten eines Bauteils)

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

5.34 Part list (Stückliste)

List of all parts used in the design

5.35 Part substitution (Bauteiltausch)

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

5.36 Plug (Steckeraufnahme)

Opposite contact side of a connector or terminal

5.37 Protection area (Geschützter Bereich)

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

5.38 Schematic Design (Schaltplan)

Graphical description of the functions, the configuration and the connections

5.39 Segment (Verbindungsabschnitt)

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

5.40 Slot (Steckplatz)

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

5.41 Special wire occurrence (Mehrdrahtleitung)

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

5.42 System Design (Systemschaltplan)

(14)

5.43 Terminal (Kontakt)

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

5.44 Topology (3D Bauraum)

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

5.45 Wire (Leitung)

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

5.46 Wire length (Leitungslänge)

Wire attribute, which describes the length of the wire

5.47 Wire protection (Leitungsschutz)

Shield to prevent the wire bundle from damage.

6 Definition of the KBL objects and attributes

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

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

(15)

Figure 3: High Level Planning Model

6.1 Packages

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

- harness and modules

- part master data

- part structure

- connectivity

- topology and routing

- foundation

6.1.1 harness and modules

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

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

- Harness - Harness_configuration

Harness

Part

has

Connector

Cavity

is a has

Connection

has connects

Routing

routes

Module/

Configuration

has controls

Segment

goes through

(16)

- KBL_container

- Module

- Module_configuration

- Module_family

6.1.2 part master data

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

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

- Accessory - Assembly_part - Cavity - Cavity_plug - Cavity_seal - Co_pack_part - Component - Connector_housing - Core - Fixing - General_terminal - General_wire - Part - Part_with_title_block - Slot - Wire_protection 6.1.3 part structure

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

The following classes are used by the part structure package:

- Accessory_occurrence - Assembly_part_occurrence - Cavity_plug_occurrence - Cavity_seal_occurrence - Co_pack_occurrence - Component_occurrence - Connector_occurrence - Core_occurrence

(17)

- Fixing_occurrence - General_wire_occurrence - Part_substitution - Special_terminal_occurrence - Specified_accessory_occurrence - Specified_cavity_plug_occurrence - Specified_co_pack_occurrence - Specified_component_occurrence - Specified_fixing_occurrence - Specified_special_terminal_occurrence - Specified_terminal_occurrence - Specified_wire_occurrence - Terminal_occurrence - Wire_occurrence - Wire_protection_occurrence 6.1.4 connectivity

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

The following classes are used by the connectivity package:

- Cavity_occurrence - Connection - Contact_point - Extremity - Slot_occurrence - Wiring_group

6.1.5 topology and routing

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

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

- Dimension_specification - Fixing_assignment - Node - Protection_area - Routing - Segment - Tolerance 6.1.6 foundation

(18)

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

The following objects are used by the miscellaneous section:

- Alias_identification - Approval - B_spline_curve - Cartesian_point - Change - Creation - Cross_section_area - External_reference - Installation_instruction - Material - Numerical_value - Processing_instruction - Transformation - Unit - Value_range - Value_with_unit - Wire_colour - Wire_length 6.2 Object definitions

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

6.2.1 Accessory

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

Example: An Accessory may be a sleeve, a cap, a cable strap or comparable parts,

which are installed to a plug.

An Accessory is a type of Part.

The data associated with an Accessory are the following:

- accessory_type

6.2.1.1 accessory_type

The accessory_type specifies the type of an Accessory.

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

(19)

6.2.2 Accessory_occurrence

An Accessory_occurrence is the occurrence of an Accessory in a module part list. The data associated with an Accessory_occurrence are the following:

- alias_id - description - id - installation_information - part - placement - reference_element 6.2.2.1 alias_id

The alias_id specifies additional identifiers for the Accessory_occurrence.

6.2.2.2 description

The description specifies additional information about the object.

6.2.2.3 id

The id specifies the identifier of the Accessory_occurrence.

6.2.2.4 installation_information

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

6.2.2.5 part

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

6.2.2.6 placement

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

6.2.2.7 reference_element

The reference_element specifies the Connector_occurrence objects supplemented by the Accessory_occurrence.

6.2.3 Alias_identification

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

The data associated with an Alias_identification are the following:

- alias_id

- description

- scope

6.2.3.1 alias_id

(20)

The description specifies the type of the Alias_identification.

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

6.2.3.3 scope

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

6.2.4 Approval

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

The data associated with an Approval are the following:

- date - department - is_applied_to - name - type_of_approval 6.2.4.1 date

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

6.2.4.2 department

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

6.2.4.3 is_applied_to

The is_applied_to specifies the objects to which the Approval is assigned. A particular Approval shall be applied to at least one object.

6.2.4.4 name

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

6.2.4.5 type_of_approval

The type_of_approval specifies the terms characterizing the Approval.

exchange partners.

6.2.5 Assembly_part

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

An Assembly_part is a type of Part.

The data associated with an Assembly_part are the following:

- components

- part_type

6.2.5.1 components

(21)

6.2.5.2 part_type

The part_type specifies the type of an Assembly_part.

exchange partners.

6.2.6 Assembly_part_occurrence

An Assembly_part_occurrence is the occurrence of an Assembly_part in a module part list. The data associated with an Assembly_part_occurrence are the following:

- alias_id - description - id - installation_information - part - placement 6.2.6.1 alias_id

The alias_id specifies additional identifiers for the Assembly_part_occurrence.

6.2.6.3 id

The id specifies the identifier of the Assembly_part_occurrence.

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

6.2.6.5 part

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

6.2.7 B_spline_curve

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

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

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

(22)

- control_points

- degree

6.2.7.1 control_points

The list of control points for the curve. The list shall contain at least 2 elements.

6.2.7.2 degree

The algebraic degree of the basis functions.

6.2.8 Cartesian_point

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

The data associated with a Cartesian_point is the following:

- coordinates

6.2.8.1 coordinates

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

6.2.9 Cavity

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

The data associated with a Cavity are the following:

- cavity_number

6.2.9.1 cavity_number

The cavity_number specifies the identifier of the Cavity.

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

6.2.10 Cavity_occurrence

A Cavity_occurrence is the occurrence of a Cavity in the context of a connector_occurrence. The data associated with a Cavity are the following:

- associated_plug

- part

6.2.10.1 associated_plug

The associated_plug specifies the plug the cavity is equipped with.

6.2.10.2 part

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

6.2.11 Cavity_plug

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

(23)

- colour

- plug_type

6.2.11.1 colour

The colour specifies the colour of the Cavity_plug.

6.2.11.2 plug_type

The plug_type specifies the type of a Cavity_plug.

exchange partners.

6.2.12 Cavity_plug_occurrence

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

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

The data associated with a Cavity_plug_occurrence are the following:

- part

6.2.12.1 part

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

6.2.13 Cavity_seal

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

The data associated with a Cavity_seal are the following:

- colour

- seal_type

- wire_size

6.2.13.1 colour

The colour specifies the colour of the Cavity_seal.

6.2.13.2 seal_type

The seal_type specifies the type of a Cavity_seal.

exchange partners.

6.2.13.3 wire_size

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

6.2.14 Cavity_seal_occurrence

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

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

by the individual occurrences.

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

particular Cavity.

The data associated with a Cavity_seal_occurrence are the following:

(24)

6.2.14.1 part

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

6.2.15 Change

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

- approver_department - approver_name - change_date - change_request - description - designer_department - id - responsible_designer 6.2.15.1 approver_department

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

6.2.15.2 approver_name

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

6.2.15.3 change_date

The change_date specifies the date the change was performed.

6.2.15.4 change_request

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

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

The description specifies additional information about the change.

6.2.15.6 designer_department

The designer_department specifies the department of the responsible design engineer.

6.2.15.7 id

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

Example: Reference of a fax, note, etc.

6.2.15.8 responsible_designer

The responsible_designer specifies the responsible design engineer.

6.2.16 Co_pack_occurrence

A Co_pack_occurrence is the occurrence of a Co_pack_part in a module part list. The data associated with a Co_pack_occurrence are the following:

(25)

- description

- id

- installation_information

- part

6.2.16.1 alias_id

The alias_id specifies additional identifiers for the Co_pack_occurrence.

6.2.16.3 id

The id specifies the identifier of the Co_pack_occurrence.

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

6.2.16.5 part

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

6.2.17 Co_pack_part

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

The data associated with a Co_pack_part are the following:

- part_type

6.2.17.1 part_type

The part_type specifies the type of a Co_pack_part.

exchange partners.

6.2.18 Component

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

Example: Fuse, fusebox, relay sockets

6.2.19 Component_occurrence

A Component_occurrence is the occurrence of a Component in a module part list. The data associated with a Co_pack_occurrence are the following:

- alias_id - description - id - mounting - part 6.2.19.1 alias_id

(26)

6.2.19.3 id

The id specifies the identifier of the Component_occurrence.

6.2.19.4 mounting

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

6.2.19.5 part

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

6.2.20 Connection

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

The data associated with a Connection are the following:

- description - external_reference - extremities - id - installation_information - processing_information - signal_name - wire 6.2.20.1 description

6.2.20.2 External_reference

The external_references specifies references to documents.

Example: Schematic diagram for the connection.

6.2.20.3 extremities

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

Note: There shall be at least two objects specified.

6.2.20.4 id

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

Example: Electrical potential, start->destination

(27)

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

6.2.20.7 signal_name

The signal_name specifies logical information on a Connection.

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

6.2.20.8 wire

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

6.2.21 Connector_housing

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

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

The data associated with a Connector_housing are the following:

- housing_code

- housing_colour

- housing_type

- slots

6.2.21.1 housing_code

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

6.2.21.2 housing_colour

The housing_colour specifies the colour of the Connector_housing.

6.2.21.3 housing_type

The housing_type specifies the type of a Connector_housing.

Example: Family series type like ‘MQS2.8’

exchange partners.

6.2.21.4 slots

The slots specifies the Slots which belong to the Connector_housing.

6.2.22 Connector_occurrence

A Connector_occurrence is the occurrence of a Connector_housing in a module part list. The data associated with a Connector_occurrence are the following:

- alias_id - contact_points - description - id - installation_information - part - placement - reference_element

(28)

- slots

- usage

6.2.22.1 alias_id

The alias_id specifies additional identifiers for the Connector_occurrence.

6.2.22.2 Contact_points

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

Note: All Contact_points of a Connector_occurrence shall reference Cavity_occurrence

objects of this Connector_occurrence.

6.2.22.4 id

The id specifies the identifier of the Connector_occurrence.

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

6.2.22.6 part

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

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

6.2.22.8 Reference_element

The reference_element specifies further Connector_occurrence objects supplemented by the Connector_occurrence.

6.2.22.9 Slots

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

6.2.22.10 usage

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

Where applicable the following values shall be used:

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

- 'ring terminal’:

- ‘splice’:

- ‘dangler’: terminal without any connector housing

6.2.23 Contact_point

A Contact_point defines the positions where electrical connectivity takes place. The data associated with a Contact_point are the following:

(29)

- contacted_cavity

- id

6.2.23.1 associated_parts

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

6.2.23.2 contacted_cavity

The contacted_cavity specifies the Cavity_objects related with the Contact_point.

6.2.23.3 id

The id specifies the identifier of the Contact_point.

6.2.24 Core

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

The data associated with a Core are the following:

- bend_radius - cable_designator - core_colour - cross_section_area - id - outside_diameter - wire_type 6.2.24.1 bend_radius

The bend_radius specifies the bend radius of a core.

6.2.24.2 cable_designator

The cable_designator specifies additional information to refer to a Core.

6.2.24.3 core_colour

The Core_colour specifies the Wire_colour objects of the core. There shall be at least one element.

6.2.24.4 cross_section_area

The cross_section_area specifies the electrical cross section of the Core.

6.2.24.5 id

The id specifies the identifier of the Core.

6.2.24.6 outside_diameter

The outside_diameter specifies the outer width of the Core.

6.2.24.7 wire_type

The wire_type specifies the type of a Core.

(30)

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

6.2.25 Core_occurrence

A Core_occurrence is the occurrence of a Core within a Special_wire_occurrence. The data associated with a Core_occurrence are the following:

- length_information

- part

- wire_number

6.2.25.1 length_information

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

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

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

6.2.25.2 part

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

6.2.25.3 wire_number

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

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

6.2.26 Creation

A Creation assigns creation information to a Module or Harness. The data associated with a Creation are the following:

- date

- department

- is_applied_to

- name

6.2.26.1 date

The date specifies the creation date.

6.2.26.2 department

The department specifies the department the creator belongs to.

6.2.26.3 is_applied_to

The is_applied_to specifies the harness or module objects to which the Creation is assigned. A Creation shall be applied to at least one object.

6.2.26.4 name

The name specifies the name of the creator.

(31)

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

The data associated with a Creation are the following:

- area

- value_determination

6.2.27.1 area

The area specifies the value of the Cross_section_area.

6.2.27.2 value_determination

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

6.2.27.3 name

The name specifies the name of the creator.

6.2.28 Dimension_specification

A Dimension_specification is the definition of the distance between two elements. The data associated with a Creation are the following:

- origin

- target

- tolerance_indication

6.2.28.1 origin

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

6.2.28.2 target

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

6.2.28.3 Tolerance_indication

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

6.2.29 External_reference

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

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

The data associated with an External_reference are the following:

- change_level - creating_system - data_format - document_number - document_type - file_name - location

(32)

6.2.29.1 change_level

The change_level specifies the version of the document.

6.2.29.2 creating_system

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

6.2.29.3 data_format

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

6.2.29.4 document_number

The document_number specifies the identifier of the document.

6.2.29.5 document_type

The document_type specifies the kind of the document. Where applicable the following values shall be used:

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

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

- cable connection diagram

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

- specification of set of cables

- standards, technical guidelines

6.2.29.6 file_name

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

6.2.29.7 location

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

6.2.30 Extremity

The Extremity specifies the Contact_point, which is connected by a specific Connection. The data associated with an extremity are the following:

- contact_point

- position_on_wire

6.2.30.1 contact_point

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

6.2.30.2 position_on_wire

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

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

(33)

6.2.31 Fixing

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

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

The data associated with a Fixing are the following:

- fixing_type

6.2.31.1 fixing_type

The fixing_type specifies the type of a Fixing.

exchange partners.

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

6.2.32 Fixing_assignment

A Fixing_assignment assigns a Fixing_occurrence or an Accessory_occurrence to a Segment. The data associated with a Fixing_assignment are the following:

- fixing

- location

- orientation

6.2.32.1 fixing

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

6.2.32.2 location

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

6.2.32.3 orientation

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

6.2.33 Fixing_occurrence

A Fixing_occurrence is the occurrence of a Fixing in a module part list. The data associated with a Fixing_occurrence are the following:

- alias_id - description - id - installation_information - part - placement 6.2.33.1 alias_id

The alias_id specifies additional identifiers for the Fixing_occurrence.

(34)

6.2.33.3 id

The id specifies the identifier of the Fixing_occurrence.

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

6.2.33.5 part

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

6.2.34 General_terminal

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

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

The data associated with a General_terminal are the following:

- cross_section_area

- outside_diameter

- plating_material

- terminal_type

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

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

6.2.34.3 plating_material

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

6.2.34.4 terminal_type

The terminal_type specifies the type of a General_terminal.

exchange partners.

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

6.2.35 General_wire

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

(35)

The data associated with a General_wire are the following: - bend_radius - cable_designator - core - cover_colour - cross_section_area - outside_diameter - wire_type 6.2.35.1 bend_radius

The bend_radius specifies the bend radius of a wire.

6.2.35.2 cable_designator

The cable_designator specifies additional information to refer to a General_wire.

6.2.35.3 core

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

6.2.35.4 cover_colour

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

The cross_section_area specifies the electrical cross section of the General_wire.

The outside_diameter specifies the outer width of the General_wire.

6.2.35.7 wire_type

The wire_type specifies the type of a General_wire.

exchange partners.

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

6.2.36 General_wire_occurrence

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

The data associated with a General_wire_occurrence are the following:

- installation_information

- length_information

- part

(36)

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

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

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

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

6.2.36.3 part

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

6.2.37 Harness

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

A Harness is a type of Part_with_title_block.

The data associated with a Harness are the following:

- components - content - harness_configuration - module - module_configuration 6.2.37.1 components

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

6.2.37.2 content

The content specifies the information covered by the Harness. The following values shall be used:

- ‘harness complete set’

- ‘harness subset’

6.2.37.3 harness_configuration

The harness_configuration specifies the configurations of the Harness.

6.2.37.4 module

The modules specifies the modules belonging to the harness.

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

6.2.37.5 module_configuration

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

6.2.38 Harness_configuration

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

(37)

The data associated with a Harness_configuration are the following:

- logistic_control_information

- modules

6.2.38.1 logistic_control_information

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

Example: ‘LOL/LOR+CFL’

6.2.38.2 modules

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

6.2.39 Installation_instruction

An Installation_instruction is the description of the methods that can be used to install a Part. The data associated with an Installation_instruction are the following:

- installation_type

- installation_value

6.2.39.1 installation_type

The installation_type specifies the kind of the Installation_instruction.

exchange partners.

6.2.39.2 installation_value

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

6.2.40 KBL_container

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

6.2.41 Material

A Material is the substance out of which a Part is or can be made. The data associated with a Material are the following:

- material_key

- material_reference_system

6.2.41.1 material_key

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

6.2.41.2 material_reference_system

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

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

6.2.42 Module

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

(38)

A Module is a type of Part_with_title_block.

The data associated with a Module are the following:

- content

- Module_configuration

- of_family

- of_harness

6.2.42.1 content

The content specifies the information covered by the Module. The following values shall be used:

- ‘variant’

- ‘module’

6.2.42.2 module_configuration

The module_configuration specifies the Module_configuration the Module represents.

6.2.42.3 of_family

The of_family specifies the Module_family to which the Module belongs.

6.2.43 Module_configuration

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

Example: Option: Audio System with CD Changer

The data associated with a Module_configuration are the following:

- configuration_type

- controlled_components

- logistic_control_information

6.2.43.1 configuration_type

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

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

Where applicable the following values shall be used:

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

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

6.2.43.2 controlled_components

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

6.2.43.3 logistic_control_information

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

(39)

Example: ‘LOL/LOR+CFL’

6.2.44 Module_family

A Module_family is a mechanism to group mutually exclusive modules.

Example: ‘audio equipment’

The data associated with a Module_family are the following:

- description

- id

The description specifies additional information about the Module_family.

6.2.44.2 id

The id specifies the identifier of the Module_family.

6.2.45 Node

A node forms begin and end of a Segment.

The data associated with a Node are the following:

- alias_id - bend_radius - cartesian_point - id - processing_information - referenced_components 6.2.45.1 alias_id

The alias_id specifies additional identifiers for the Node.

Example: Node Ids may vary from one CAD system export to another. Therefore the

CAD system Id is improper for Id attribute. Id shall have a value, which is unique within the harness. Alias_id may be used for the CAD system Id.

6.2.45.2 bend_radius

The bend_radius specifies the maximum bend radius at the Node.

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

6.2.45.3 cartesian_point

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

6.2.45.4 id

The id specifies the identifier of the Node.

6.2.45.5 processing_information

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

(40)

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

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

6.2.46 Numerical_value

A Numerical_value is a quantity expressed with a numerical value and a unit. The data associated with a Numerical_value are the following:

- value_component

6.2.46.1 value_component

The value_component specifies the quantity of the Numerical_value.

6.2.47 Part

A part is an element of a product relevant for a bill-of material. The data associated with a Part are the following:

- abbreviation - alias_id - change - company_name - copyright_note - degree_of_maturity - description - external_references - mass_information - material_information - part_number - predecessor_part_number - processing_information - version 6.2.47.1 abbreviation

The abbreviation specifies a short name for a Part.

6.2.47.2 alias_id

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

6.2.47.3 change

The change specifies the change history of the Part.

6.2.47.4 company_name

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