VDA Recommendation 5005 1st edition, July 2005

Traceability of vehicle components

VDA and identifiability of their technical 5005
design

This non-binding recommendation describes processes and procedures for the

traceability of vehicle components and the identifiability of their technical design.

The recommendation is divided into two parts.

Part 1 provides a general description of the processes for implementing
traceability and identifiability of a component design.

Part 2 discusses possible technical implementation procedures.

1st edition, July 2005

VDA “Logistical Processes” working group

Published by: German Association of the Automotive Industry Copyright

Behrenstrasse 35 Reprinting and any other form of
Postfach 8 04 62 duplication are only permitted
10004 Berlin if the source is cited.
Tel: +49 (0)30/897842-221
Fax: +49 (0)30/897842-606
Internet: www@vda.de

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 2 of 19

Contents

1. Introduction
1.1 Aim 3
1.2 Field of application for Parts 1 and 2 3
1.3 Normative references in Parts 1 and 2 3

2. General description of the processes (Part 1)

2.1 Processes for ensuring the traceability
of vehicle components 4
2.1.1 Documentation processes 4
2.1.2 Agreement on the documentation processes used
within the supply chain 4
2.1.3 Content of mark for traceability and its use 4
2.1.4 Action in the event of claims 5
2.2 Identifiability of components 5
2.3 Period of use of the mark 5
2.4 Miscellaneous 6
2.4.1 Mark as a quality feature 6
2.4.2 Specification 6

3. Possible technical implementation procedures (Part 2)

3.1 Mark content 7
3.1.1 Content for traceability of vehicle components 7
3.1.2 Content for identifying the technical execution 10
3.2 Data presentation and coding 12
3.3 Data structure 12
3.4 Direct access to a sub-contractor’s reference 12
3.5 Use of data identifiers 14

4. Normative references 18

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 3 of 19

1 Introduction

1.1 Aim
The aim of the recommendation is to define standardised processes which are
suitable throughout the entire supply chain for enabling the traceability and
identifiability of vehicle components. To this end suitable documentation processes
are described in accordance with possible applications and their framework
conditions, and general requirements on component marking are formulated.
Furthermore, fundamental aspects of using the processes, relating to customers and
suppliers, are specified.

The aim of the second part of the recommendation is to enable the minimum
requirements relating to marking specified above to be implemented in a technically
standardised manner, taking due account of existing standards on data structuring
and coding. The consistent, blanket use of the procedure outlined here will result in a
standardised marking system in the automotive industry and will render cost-
intensive customised solutions superfluous.

1.2 Field of application for Parts 1 and 2

The processes and procedures described in this recommendation are applicable to
all vehicle components (blanks, individual components, finished products, materials,
assemblies, batches, production batches and software – hereinafter termed product
–) within the automotive industry.

Implementation of the recommendation is agreed bilaterally between the

supplier/manufacturer and the customer for specific applications (products).
Individual components or assemblies to which it is essential to apply this
recommendation are not defined.
The mark described here does not replace already established marking methods in
the automotive sector (e.g. nameplates, operating/warning signs, company logos,
free text information).

1.3 Normative references in Parts 1 and 2

This recommendation borrows from existing international standards. The normative
references cited in section 4 deal with the data structure, coding form, label
standards and quality standards.

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 4 of 19

2 General description of the processes (Part 1)

2.1 Processes for ensuring the traceability of vehicle components

2.1.1 Documentation processes

The commonest documentation processes for traceability in the automotive industry
are based on

individual component marking

package marking

delivery note documentation
Different levels of demarcation precision apply, depending on the alternative chosen.

2.1.2 Agreement on the documentation processes used within the supply

chain
The customer and supplier/manufacturer select the documentation process for their
interface.
This means that different documentation processes may be used over the course of
the supply chain.

2.1.3 Content of the traceability mark and its use

The content of the mark is a reference which does not contain any quality and/or
process data itself.
The supplier/manufacturer establishes a cross-reference to the finished product’s
quality and production data via its reference/mark. This cross-reference is
documented and archived.
The customer uses the reference/mark of the supplied product to establish a cross-
reference to his end product in which it has been fitted. This cross-reference is
documented and archived.
The mark therefore forms the reference between the quality and production data (e.g.
batch of raw materials used, manufacturer of bought-in components, inspection
result, settings, production site and equipment etc.) of the products supplied by the
supplier and the customer’s end product. The content of the mark must be unique
over the agreed period of the customer/supplier relationship.
The saved data should be retained by the supplier and customer in compliance with
the statutory provisions in force in the various countries in which the products are
sold. The data retention period shall be contractually agreed between the customer
and supplier.

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 5 of 19

In the event of a claim the customer and the supplier/manufacturer exchange the
necessary references to enable the cause to be analysed and to minimise damage.

2.1.4 Action in the event of claims

In the event of a production or process fault identified by the supplier, the supplier
notifies the customer of the references for the products affected.

The customer informs the supplier if he discovers faulty components (in his plant or
at his customers). The supplier carries out the necessary investigations (research)
using his own tracking system in order to notify the customer of the references to
products affected.
In both cases the data exchanged by the supplier and the customer includes the
following:

References of the faulty components (derived from the delivery note, packaging
or individual component)

The reference numbers, type of fault and number of parts affected

2.2 Identifiability of components

The product is clearly described by the reference number (also sometimes termed
article number, item number or part number) and the revision index / revision number
(also termed revision status). Multiple reference numbers may be necessary to
identify more complex assemblies.
If no unique reference number exists, it is necessary to specify a blank number, a
type code, a generation number, an assembly number, a dimensional group, a
weight group or a control number in addition to or in place of the reference number.
To enable the supplier/manufacturer and customer to identify the product, it is
recommended that both the supplier’s and the customer’s reference number, if
necessary including the respective revision index, be applied to the product,
packaging unit or delivery note.

2.3 Period of use of the mark

During the manufacturing process all the specified marking information remain
associated with the individual component/assembly (on the individual component
itself, via the packaging unit with packaging item number/licence plate containing the
component or via the delivery note number on the packaging containing the
component) until installed in the next higher assembly.

After fitting, the mark may be separated from the product, as a result of which
traceability can only be guaranteed via the end product.

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 6 of 19

2.4 Miscellaneous

2.4.1 Mark as a quality feature

The mark is a quality feature that requires monitoring.
Important aspects include:

Type and legibility of code

Correct content of data string

Application of mark

2.4.2 Specification
The tracking process and necessary details for marking individual components is a
necessary element of the customer’s specification to the supplier/manufacturer to
enable the latter to take account of the chosen procedure in his product design and
production process.
If the packaging item or delivery note procedure is chosen, this selection must be
documented when a contract is concluded between the customer and
supplier/manufacturer (logistics agreements).

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 7 of 19

3 Possible technical implementation procedures (Part 2)

3.1 Mark content

3.1.1 Content for traceability of vehicle components

Depending on the selected documentation processes (see 2.1.1), the information
content which permits a unique reference to the process and quality data must be
chosen. The necessary information content per documentation process is listed in
Table 1.

Table 1: Mark content by documentation process

Documentation Individual Packaging Delivery note
component mark documentatio
process mark
n
Content
Obligatory content

Supplier number
Supplier code
(unique globally)

Supplier’s serial no.

Serial no. per Packaging item
Unique
component no.
Delivery note
no.
Non-unique Group serial no. Batch no.

Reference no.
Customer’s reference no.
(part number)
Other fields are possible – please see ANSI MH 10.8.2 (DIs) in this context.

Tables 2 to 8 are used to describe the chosen information content.

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 8 of 19

Table 2: Description of the globally unique supplier code:

Supplier code in compliance with ISO/IEC 15418 and ISO/IEC 15459
Data field Content DI Data string

13Vzzzzzzzzz
DUNS supplier no. DUNS no. =zzzzzzzzz 13V
z=9 digits / 13 digits

DI = data identifier. This is an abbreviation designating the data field and precedes
the actual reference data item (see data string). Grouping various DIs + reference
content sequentially results in a data string which permits easy selective access to its
content. See para. 3.5.

Table 3: Description of the serial number for individual component marking

Data field Content DI Data string
3 alternatives
Serial no. Sxxxxxx…
Serial no. xxxxxx... S
- unique

Serial no. 1Tyyyyyy…

Group serial no. yyyyyy... 1T
- group

DUNS code = “UN”

Licence plate with
25SUNzzzzzzzzzkkkkkk....
DUNS DUNS supplier no. = 25S
zzzzzzzzz z=9 digits / 13 digits
- unique
Serial no. = kkkkkk...

Note on serial number: The serial number must be selected by the supplier such
that it is unique when combined with the supplier number and the reference number
(part number). This unique status must be ensured over the documentation period.
Note on group serial number: The group serial number represents a batch number
in its widest sense with which each individual component of the batch is marked. See
also “Note on serial number”.
Note on licence plate: The licence plate combines the supplier code and the serial
number to form a sequential number. Separate specification of the supplier number
and the serial number is therefore unnecessary. See also “Note on serial number”.

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 9 of 19

Table 4: Description of serial numbers for packaging item mark

Data field Content DI Data string

3 alternatives
Packaging item no. Packaging item no.
3S 3Sxxxxxx…
- unique xxxxxx...

Batch no. on
packaging item Batch no. yyyyyy... 1T 1Tyyyyyy…
- non-unique

DUNS code = “UN”

1JUNzzzzzzzzzkkkkkk...
Licence plate with DUNS supplier no. =
DUNS 1J or
zzzzzzzzz 6J z=9 - 13 digits
- unique
Packaging item no. =
kkkkkk...

Note on licence plate data identifier: 1J describes a container which cannot be

broken down further. 6J describes packaging types which may contain smaller
containers (same reference number).

Note on uniqueness: The packaging item numbers, batch numbers and licence
plate must be unique within a supplier over the agreed documentation period.

Table 5: Description of the serial number for delivery note documentation

Data field Content DI Data string

Delivery note no. Delivery note no. xxxxxx... 2K 2Kxxxxxx…

Note on delivery note number: The delivery note numbers must be unique within a
supplier over the agreed documentation period.

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 10 of 19

Table 6: Description of the reference number

Data field Content DI Data string
Alternatively or jointly

Component reference P
no. defined by Reference no.: xxxxxx... Pxxxxxx…
customer

Software reference no. Software reference no.: 21P

21Pwwwwww…
defined by customer wwwwww...

The software reference number can also be specified as a supplement to a hardware

reference number.

Note on software reference number: The content of this recommendation is only

applicable if the software reference number/version is to be a feature which must be
externally marked. In this case the mark content must be updated appropriately in the
event of software updates (Flash-ROM). If the software reference number and its
version are only used managed in ROM/Flash-ROM, this recommendation for the
traceability of software is not applicable.

Note on reference number: Combining the globally unique supplier number and the
supplier’s reference number enables a globally unique reference to the technical
design of the component to be generated.

3.1.2 Content for identifying the technical design

Depending on requirements and the agreement between the customer and supplier,
one or multiple reference numbers (part numbers) and revision indices for the same
component build the mark (e.g. customer and supplier reference number).

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 11 of 19

Table 7: Description of the reference number

Data field Content DI Data string
Reference numbers to describe the technical design of the component
Component reference
no. defined by Reference no.: xxxxxx... P Pxxxxxx…
customer

Component reference
Reference no.: yyyyyy... 1P 1Pyyyyyy…
no. defined by supplier

Software reference no. Reference no.:

21P 21Pwwwwww…
defined by customer wwwwww...

Software reference no.

Reference no.: zzzzzz... 31P 31Pzzzzzz…
defined by supplier

General note on DIs: Each DI may only be used once (exception: see Appendix 1:
“Direct access to a sub-contractor’s reference” – DIs in connection with the DI: “F”)

Table 8: Description of the revision indices

Data field Content DI Data string
Revision indices to define reference number more specifically

Component revision
index defined by Revision index: xx... 20P 20Pxx…
customer

Component revision
Revision index: yy... 30P 30Pyy…
index defined by supplier

Software revision index of

component defined by Revision index: ww... 22P 22Pww…
customer

Software revision index of

component defined by Revision index: zz... 32P 32Pzz...
supplier

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 12 of 19

Note on reference numbers and revision index: If the revision index is part of the
reference number, it is included as such.

Note on DIs 20P, 21P, 22P, 30P, 31P, 32P (general, freely definable DIs): After
official specification these should be replaced by precisely specified DIs in ISO/IEC
15418.

3.2 Data presentation and coding

The data contents are shown in machine-readable form. 1D and 2D barcodes and
the 2D matrix code are suitable for this. Common symbologies are:
• 1D barcode : code 128
• 2D barcode: PDF417
• 2D matrix code: Data Matrix – ECC200

Transponder technology can also be used as an alternative.

The following must be agreed between the customer and supplier:

• Which parts of the encoded information content must also be shown in free
text
• Where the mark is to be applied to the component
• What form the mark is to take (label, direct marking, tag etc.)

Vehicle-related products can only be marked insofar as their surface finish, shape
and size permit it. Any resulting restrictions on the mark must be agreed between the
customer and supplier/manufacturer. An essential prerequisite of any restriction is a
guarantee of unrestricted product traceability with the aid of the restricted
information.

3.3 Data structure

The information shall be presented as in ISO/IEC 15434 and ISO/IEC 15418 (which
refer to ANSI MH 10.8.3M and ANSI MH 10.8.2) – data format 06 “Data using data
identifier”. The AIAG B4 standard refers to the ANSI MH standards.

3.4 Direct access to a sub-contractor’s reference

If documentation of components which have already been pre-installed by a supplier
is necessary (e.g. an airbag in seats), the following procedure may be used:
A hierarchical code is used in compliance with ANSI FACT-ISO/IEC 15418. The
module reference is shown at the first level. The references of the sub-contractor’s
component are included at the second level (as a successor to the module). The data
identifier F can be used to organise the hierarchy:

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 13 of 19

Data identifier F
F## ## 1 #
F for manufacturer components

1 = successor exists
0 = successor does not exist
Element number of parent component
(00 =number
Element no predecessors)
of child component

The references that follow this descriptor belong to the child component (element
number).

Example (hierarchical structure):

F01001F GS (Element no. 01)

G
13V … S

P …. GS
S …. GS
F02011F GS (Element no. 02, child/sub-element of element 01)

13V … GS
P …. GS
S …. GS
F03020F GS (Element no. 03, child/sub-element of element 02)

13V… GS
P … GS
S … GS
F04010F GS (Element no. 04, child/sub-element of element 01)
13V … GS
P …. GS
S …. RS EOT

Example (flat structure with various data elements per structural element):

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 14 of 19

F01000F GS (Element no. 01)

G
13V … S

P …. GS
S …. GS
F02000F GS (Element no. 02)
13V … GS
P …. GS
S …. GS
F03000F GS (Element no. 03)
13V … GS
P …. GS
S …. RS EOT

Example (flat structure with serial numbers of various components):

F01000X GS
25S.... GS
25S.... GS
25S.... RS EOT

See also the examples in the next paragraph.

3.5 Use of data identifiers

The following information is an extract from the above-mentioned standards and is
merely intended to show how the information structuring system works:

The marking system is based on presentation of the content as a data string, with
each item of information being preceded by a data identifier (DI) and followed by a
data separator/trailer. The DI and separator enable the individual data items to be
separated from each other and their contents to be interpreted. The string can
therefore be composed individually to take account of the requirements of the
information to be disseminated.

Apart from the information, the DIs and the data separator, there is also a message
header and a message trailer which mark the beginning and end of the message. In

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 15 of 19

addition, the ANSI standard also specifies a format header and a format trailer to
indicate which standard is to be applied in interpreting the data string (i.e. the DIs).
Message structure:
Message header
Format header
DI
Information
Data separator
DI
Information
Data separator
DI
…
Data separator
Format trailer
Message trailer

Selected formats:
• Always the same message header and format header (7 characters):

R G
ASCII/ISO Table 646 char.: [ ) > S 0 6 S

->Decimal output: 9141 62 30 48 54 29

->Hex output: 5B 29 3E 1E 30 36 1D

Data separator
FACT1 format
Message header

• Always the same format trailer + message trailer (2 characters):

1
FACT: Federation of Automatic Coding Technology: Development of Data Identifiers (DIs) in 1989
described in ANSI MH10.8.2 – ISO/IEC 15418

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 16 of 19

R
ASCII/ISO Table 646 characters: S EOT
-> Decimal output: 30 04
-> Hex output: 1E 04

Message trailer
Trailer

• Note:
R
S, EOT and GS are the print letters from ASCII/ISO Table 646 – these letters
are used by programmers to extract the various data elements in a data
string.

• This document contains details of the data identifier set recommended for
identification and traceability. Each DI may only be used once in a string.
Which DIs are used depends on the particular information which actually has
to be presented. The character set to be used is ASCII/ISO Table 646.

The following characters may be used as user data:

0 to 9 ASCII decimal 48 to 57
A to Z Only upper-case letters ASCII decimal 65 to 90
- ASCII decimal 45
. ASCII decimal 46
$ ASCII decimal 36 – avoid since it cannot be represented
in Code 39
/ ASCII decimal 47 – avoid since it cannot be represented
in Code 39
+ ASCII decimal 43 – avoid since it cannot be represented
in Code 39
% ASCII decimal 37 – avoid since it cannot be represented
in Code 39
Space ASCII decimal 32

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 17 of 19

• Always the same data separator (1 character):

G
. ASCII/ISO 646 letter: S

-> Decimal output: 29

-> Hex output: 1D

Trailer

• Example:

Supplier number: 999 999 999 assigned by Dun & Bradstreet

Part number (specified by the customer): 0POS-40
Serial number: 123456
Production date: 30 July 2003
=> Code:
[)>RS06GS13V999999999GSP0POS-40GSD030730
G
S S123456RS EOT

If the reference for a sub-contractor’s component is also to be

passed on to the customer, the DI “F” is used.
e.g. sub-contractor code: 888 888 888
e.g. part number of sub-contractor component: sub123
e.g. serial number: 67891011

=> The code would look as follows:

[)>RS06GS F01001F GS13V999999999GSP0POS-40
G G
SD030730 S S123456 GSF02010F GS 13V888888888
G R E
SPSub123 S67891011 S OT

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 18 of 19

4 Normative references
AIAG B-4:2003-02 Parts Identification and Tracking Application Standard

AIAG B-17:2003-02 2D Direct Parts Marking Guideline

AIAG B-16: 2002-11

Global Transport Label; Standard for the Automotive
Industry (Odette, AIAG, JAMA, JAPIA)

ANSI MH10.8.2: 1995

Data Application Identifier Standard

ANSI MH10.8.3M: 1996

Unit Loads and Transport Packages – Two-Dimensional
Symbols

ISO/FDIS 22742:2004-10
Packaging - Linear Bar Code and Two-Dimensional
Symbols for Product Packaging

ISO/IEC 15415:2004-06
Automatic Identification and Data Capture Techniques –
Bar Code Print Quality Test Specification – Two-
Dimensional Symbols

ISO/IEC 15417:2000-06
Automatic Identification and Data Capture Techniques –
Bar Code Symbology Specification – Code 128

ISO/IEC 15418:1999-12
EAN/UCC Application Identifiers and FACT Data
Identifiers and Maintenance

ISO/IEC 15434:1999-10
Transfer Syntax for High Capacity ADC Media

Copyright: VDA
VDA Recommendation 5005 1st edition, July 2005 Page 19 of 19

ISO/IEC 15438:2001-09
Automatic Identification and Data Capture Techniques –
Bar Code Symbology Specifications; PDF417

ISO/IEC 15459-1:1999-12
Unique Identification of Transport Units - Part 1: General

ISO/IEC 15459-2:1999-12
Unique Identification of Transport Units - Part 2:
Registration Procedures

ISO/IEC 16022:2000-05
International Symbology Specification – Data Matrix

ISO/IEC 16388:1999-05
Automatic Identification and Data Capture Techniques –
Bar Code Symbology Specifications - Code 39

ISO/IEC 18004:2000-05
Automatic Identification and Data Capture Techniques –
Bar Code Symbology – QR Code

ISO/TS 16949:2002-03
Quality Management Systems – Particular Requirements
for the Application of ISO 9001:2000 for Automotive
Production and Relevant Service Part Organisations

Odette Transport Label version 1

Odette UPI Unique Parts Identification

Note: AIAG B4 is restricted in that one of the two matrix code types, i.e. ECC200
(Technical Encoding of the Matrix Code) is permitted since it is more modern, smaller
and more functional.

Copyright: VDA