GMW15 862

WORLDWIDE
ENGINEERING General Specification GMW15862

STANDARDS
Bar Code Content, Format, and Label Requirements for

Traceability and Error Proofing (including VER and COM)
1 Introduction 5
1.1 Scope 5
1.2 Mission/Theme 5
1.3 Classification 5
1.4 New Sourced Parts, Components, Assemblies, and Modules 5
1.5 Carryover Parts, Components, Assemblies, and Modules 5
1.6 Control Module Software 5
1.7 Additional Label Content 5
1.8 Reasons for Bar Code Scanning 5
1.8.1 Traceability 5
1.8.2 Error Proofing 5
2 References 5
2.1 External Standards/Specifications 5
2.2 GM Standards/Specifications 6
2.3 Additional References 6
3 Parts, Components, Assemblies or Modules Requiring Bar Codes 6
3.1 When Bar Codes are Required 6
3.2 Label/Mark Anatomy 7
3.2.1 Human-Readable Content Requirements for Traceability (see Appendix J for Powertrain) 7
3.2.2 Human-Readable Content Requirements for Error-Proofing 8
3.2.3 Supplier Logo or Trademarks 8
3.2.4 Labeling Electronic Modules 8
3.2.5 Powertrain Released Components 8
3.2.6 Tire Trace Data 8
3.3 Bar code Symbologies and Encodation 8
3.3.1 Bar Code Symbology 8
3.3.2 Data Fields and Data Identifiers 9
3.4 Data Matrix and QR Code Physical Requirements 10
3.4.1 System/Subsystem/Component/Part Definition 10
3.4.2 Data Matrix and QR Code Quiet Zones 10
3.4.2.1 Data Matrix Quiet Zone 10
3.4.2.2 QR Code Quiet Zone 11
© Copyright 2013 General Motors Company All Rights Reserved
June 2013 Originating Department: GME Specification Center Page 1 of 52

GM WORLDWIDE ENGINEERING STANDARDS GMW15862
3.4.2.3 Error Correction Levels 11

3.5 Rectangular Data Matrix 11
3.6 Label Design Requirements 12
3.6.1 Printing 12
3.6.2 Label Construction 12
3.6.3 Human Readable Information (HRI) 13
3.6.4 Font Specification 13
3.7 Scanners/Imagers 13
4 Single Data Field Encodation 13
5 Linear 1D Bar Codes 14
6 Direct Part Marking (DPM) 14
7 Symbol (Bar Code) Quality Verification 14
7.1 Label Performance Testing 14
7.2 Bar Code Print Quality on Labels 14
8 Additional Product Characteristics 14
8.1 Additional Information 14
8.2 As-Built Label 14
9 Radio Frequency Identification (RFID) 15
10 Validation 15
10.1 Responsibility 15
10.2 Form 15
10.3 Process 15
10.4 Additional Information 15
11 Notes 15
11.1 Glossary 15
11.2 Acronyms, Abbreviations, and Symbols 17
12 Additional Paragraphs 19
13 Coding System 19
14 Release and Revisions 19
Appendix A 20
A1 Typical Data Identifiers 20
Appendix B 22
B1 JULIAN Calendar 22
Appendix C 24
C1 Vehicle Partitioning and Product Structure (VPPS) 24
C1.1 Compressed VPPS 24
C1.2 VPPS Location Code 25
Appendix D 27
D1 Data Matrix Reference Information 27
June 2013 Page 2 of 52

D1.1 Anatomy of a Data Matrix 27

D1.2 Allowable Data Characters 31
D1.3 Error Correction Levels. 31
D1.3.1 Data Matrix Error Correction Code (ECC) Level 31
D1.3.2 QR Code Error Correction (EC) Levels 31
Appendix E 32
E1 GMW15862 Traceability Code Structure and Content 32
E2 GMW15862 Error Proofing Structure 34
Appendix F 35
F1 Appending/Adding Additional Data to the 2D Bar Code 35
Appendix G 38
G1 “As-Built” Label/DPM 38
Appendix H 40
H1 GM1737 Traceability Structure (Phasing Out - See Traceability NOA 196B) 40
H2 GM1737 Enhanced Traceability Structure (Phasing Out - See Traceability NOA 196B) 40
H3 Linear 1D Bar Codes 41
H3.1 Code 128 and Code 39 41
H3.2 Characteristics of Code 128 41
H3.3 Characteristics of Code 39 41
H3.4 Code 128 and Code 39 Quiet Zones 42
H3.5 Check Digits 42
H3.6 Code 128 and Code 39 Print Quality 42
H3.7 Code 128 and Code 39 Data Format and Data Length 42
H3.8 Data Capacity 42
H3.9 Human Readable Information for Code 128 and Code 39 42
Appendix J 43
J1 Traceability Format for Powertrain Released Components Scanned at the Vehicle Manufacturing Plant or
VAA 43
J2 Traceability Format for Powertrain Released Components Scanned in the Powertrain Manufacturing Facility
46
J2.1 Trace Data Fields 46
J2.2 Human Readable Content 46
Appendix K 47
K1 Tire Labeling 47
K1.1 Long Range Scanning 47
K1.2 Tire Labeling Requirements 47
K1.3 Tire Lot Traceability Identification 47
K1.4 Tire Conicity 48
K1.5 Data Syntax Requirement 48

K1.6 Label Layout 48

Appendix L 50
L1 Direct Part Marking (DPM) 50
L1.1 Considerations 50
L1.2 Direct Mark and Human Readable Information 50
L1.3 Direct Part Marking Methods 50
L1.3.1 Scribing 50
L1.3.2 Dot-Peen 51
L1.3.3 Laser 51
L1.3.4 Inkjet 52
L1.4 Direct Part Mark Verification 52

1 Introduction
Note: Nothing in this standard supercedes applicable laws and regulations.
Note: In the event of conflict between the English and domestic language, the English language shall take
precedence.
Note: In this document, the word shall is a requirement and the word should is a recommendation.
Note: In this document, the word label refers to all marking methods and technologies (including all methods in
Appendix L).
Note: All label samples and examples used in this document as for demonstration purposes only.
1.1 Scope. This standard defines the bar code symbologies, data content, and label/Direct Part Marking
(DPM) layout for parts, components, assemblies, and modules used in the manufacturing of GM vehicles. This
standard also defines the performance standards for printed bar codes and Direct Part Marking. This standard
does not apply to packaging labels or service parts labels.
1.2 Mission/Theme. Not applicable.
1.3 Classification. Not applicable.
1.4 New Sourced Parts, Components, Assemblies, and Modules. All parts, components, assemblies, or
modules with KCDS codes TRA, AVG and/or VER shall comply with this document. When scanning is used for
COM components or assemblies, this standard shall apply.
1.5 Carryover Parts, Components, Assemblies, and Modules. Linear 1D Bar Code formats as specified in
GM1737 are allowed on carryover scanned parts, components, assemblies or modules until the beginning of
MY2014. See NOA QLT196B for additional information. See Appendix H for Linear Bar Code reference
information.
1.6 Control Module Software. Control Module Software shall comply with GMW4710. New data structure
shall go into effect beginning with Global B Architecture or upon new part sourcing for MY14.
1.7 Additional Label Content. This specification defines only TRACE/ERROR-PROOFING REQUIREMENTS
for labels and Direct Marked Parts (DPM). GM MAY allow additional information on the label / DPM under the
following conditions:
complies with all applicable GMWs and regulations
is visually separated / distinct from traceability / error proofing content
does NOT contain additional bar codes (only GM-required bar code is allowed unless others are required
by law)
does NOT interfere with bar code scannability
agreed to by General Motors via the CG2503 approval process
1.8 Reasons for Bar Code Scanning.
1.8.1 Traceability. Traceability refers to all categories of GM defined component tracking that require bar
codes (i.e. includes TRA, AVG and/or VER). The primary purpose of traceability is to precisely identify the
vehicles (VIN/trace number) involved in a spill or potential field action. Product Engineering is responsible for
defining which parts, components, assemblies, and modules require traceability.
1.8.2 Error Proofing. Error proofing provides the capability to validate the correct part/component/module/
assembly has been installed on the vehicle.
2 References
Note: Only the latest approved standards are applicable unless otherwise specified.
2.1 External Standards/Specifications.
ANSI MH 10.8.2 ISO/IEC 646 ISO/IEC 15418 ISO/IEC 16388
ANSI X12.3 ISO/IEC 15416 ISO/IEC 15434 ISO/IEC 18004
FMVSR 49 ISO/IEC 15417 ISO/IEC 16022

2.2 GM Standards/Specifications.
GM1737 GMW14089 GMW15862
GMW3059 GMW14573 GMW16331
GMW4710 GMW14574
2.3 Additional References.
AIM DPM Quality Guideline (available from www.aimglobal.org)
Dunn and Bradstreet (aka DUNS) available from http://www.dnb.com
Quality Requirement 22.00.00
Traceability NOA QLT/ELT 196B
APM – determine Vehicle Partitioning and Product Structure (VPPS); verify with Labels & Literature
website
Bar Code web site: https://gmweb.gm.com/sites/toolkit/48lnl/Pages/Barcodes.aspx
KCDS Master List
Compressed VPPS List
CG2503 Bar Code Validation Form
AIAG B-2
AIAG B-4
AIAG B-7
AIAG B-11
AIAG B-17
3 Parts, Components, Assemblies or Modules Requiring Bar Codes

3.1 When Bar Codes are Required. Parts, components, assemblies and modules identified as requiring
Traceability through the Key Characteristics Designation System (KCDS) shall be encoded in a Data Matrix or
optional Quick Response (QR) Code two-dimensional (2D) symbol (bar code) (see Table 1). These parts shall
have the label placement (or Direct Marked Part) identified on the part drawing / UG math. Consistent label
placement is essential when fixed mount scanners are used at the point of scan.
Table 1: Trace Bar Code requirements and Drivers
KCDS Code Driver
Product Engineering DFMEA,

Traceability - Standard Parts TRA
Other Business Case
Traceability – Electronic parts that must Product Engineering DFMEA,
AVG
comply with GM4710 Other Business Case
Product Engineering DFMEA,
Verification - Engineering VER Note 1
Other Business Case
Product Engineering; Only applicable when ME

Compliance - Engineering COM Note 2
approves scanning as method of confirmation
ME, PFMEA; only applicable when ME approves

Error Proofing – Manufacturing N/A
scanning as method of error proofing
Note 1: See paragraph 4 for Single Data Field Encodation
Note 2: Follow Appendix E2 format for error proofing
TRA: Traceability
AVG: Assembly Verification Group
VER: Verification
ME: Manufacturing Engineering
PFMEA: Process Failure Mode and Effects Analysis

DFMEA: Design Failure Mode Effects Analysis

Bar codes may be used for error-proofing purposes; however, all other possible error-proofing alternatives
should be considered first due to the cost associated with bar codes and scanning. Parts, components,
assemblies and modules identified by Manufacturing Engineering through the Process Failure Mode and
Effects Analysis (PFMEA) as sensitive to selection error may require a bar code for electronic verification. The
Manufacturing Engineer will initiate a PRTS to communicate to Product Engineering the need to add the bar
code. The Component DRE must fill out a CG2503 if a traceability or error-proofing bar code is required and
initiate an EWO as appropriate.
3.2 Label/Mark Anatomy. The label/mark shall be constructed in a layout most suitable for the part,
component, assembly, or module. The location and orientation of the symbol may be critical for applications
using automated fixed mount scanners. The Traceability Label/DPM format must be used for parts with
traceability requirements. Examples shown in this document are for illustration purposes only and are not to be
construed as specifications. Note that data identifiers such as Y, P, 12V, T, C, etc. shall not be printed on the
label in human-readable form.
3.2.1 Human-Readable Content Requirements for Traceability (see Appendix J for Powertrain). The
requirements for trace information shall include:
GM-required 2D Bar Code
GM assigned 8-digit part number
GM assigned compressed VPPS code with the last digit representing part location (see Appendix C2)
Manufacturing or assembly site’s Data Universal Numbering System (DUNS) identification
The 16-character traceability structure where L=Line, S=Shift, YY=Year, DDD=Julian Date (see
Appendix B for Julian Calendars) and the last 9 characters (last 8 for lot/batch) are supplier-defined data.
The Trace Code can be alpha and/or numeric.
Figure 1: Illustration of a Serialized Traceability Label/DPM
Figure 2: Illustration of a Lot/Batch Traceability Label/DPM
Figure 3: Anatomy of a Label/DPM with a Symbol

3.2.2 Human-Readable Content Requirements for Error-Proofing. The requirements for Error-Proofing
information shall include (see paragraph 4 for Verification):
GM assigned 8-digit part number
GM assigned compressed VPPS code with the last digit representing part location (see Appendix C2)
Manufacturing or assembly site’s Data Universal Numbering System (DUNS) identification
Optional Year and Julian Date (YYDDD) the part was manufactured (See Appendix B for Julian Calendars)
Figure 4: Illustration of an Error-Proofing Label/DPM
Note: Error-proofing and Part Verification bar code applications can utilize either the Julian date of
manufacture/assembly or the traceability code; however, the format shown in Figure 4 cannot be used for
traceability applications.
3.2.3 Supplier Logo or Trademarks. Supplier shall comply with GMW16331 for branding requirements and
policies.
3.2.4 Labeling Electronic Modules. Reference GMW4710 for the method to program electronic modules with
traceability information. Exterior labeling of electronic modules shall conform to the traceability structure as
detailed in paragraph 3.2.1 except for carryover electronic parts. Carryover electronic parts shall use the
format detailed in Appendix H. The data on the label must match what is stored electronically in the device.
3.2.5 Powertrain Released Components. The last nine characters of the traceability code are defined
according to Appendix J. See Appendix J for additional information.
3.2.6 Tire Trace Data. See Appendix K for Tire Data trace syntax.
3.3 Bar code Symbologies and Encodation. Bar code symbologies shall consist of the proper data syntax,
data identifiers, control characters, and data fields. See Appendix E, H and J for additional information on bar
code symbology and proper encodation.
3.3.1 Bar Code Symbology. The information in this section applies to the two-dimensional (2D) bar code
symbologies defined in this Standard. Data Matrix (preferred symbology) ISO/IEC 16022 Symbology
Specification (Appendix D) or QR Code (with GM approval) ISO/IEC 18004, Symbology Specification, shall be
used (Figure 5). QR Codes provide decreased error correction, hence, Data Matrix is the preferred symbology.
Figure 5: Two-Dimensional (2D) Symbologies Data Matrix (Preferred) and QR Code
The data syntax structure used for Message Header, etc. is defined by ISO/IEC 15434. Table 2 shows the
primary data syntax used in GM traceability encodation. See Appendix D, E and J for additional information.

Table 2: Data Syntax Structure

Start of Transmission ASCII ISO/IEC 646 Characters Decimal Hex
[ (left bracket) [ 91 5B
) (right parenthesis) ) 41 29
> (greater than) > 62 3E
Non-Printable ASCII control characters
E
End Of Transmission OT 04 04
G
Group Separator (Data field separator) S 29 1D
R
Record Separator S 30 1E
3.3.2 Data Fields and Data Identifiers. A data field shall consist of a Data Identifier (DI) followed by the
associated data. Data Identifiers (DI) complying with ISO/IEC 15418 (ANSI MH 10.8.2) shall be used. All data
defined in this standard are FIXED length and shall be padded with zeros if necessary to meet the fixed length
requirements. When used, the fields in Table 3 shall NOT exceed the data length shown.
The bar code shall contain four data fields with their associated Data Identifiers (DI): VPPS (Y), Part Number
(P), Supplier DUNS (12V), and Traceability (T) or Julian Date of Manufacture or Assembly (4D). Parts with
traceability requirements must use the Traceability format (T) while parts labeled for error-proofing or part
verification can use with either T or 4D. Each GM-required data identifier can only be used once within a single
record.
Table 3: Restricted Length Data Fields
Data Data Total Field
Description
Identifier DI Length Length incl. DI
GM assigned Compressed Y4730300000000R
Y 14 15
VPPS Code
P GM-Assigned Part Number 8 9 P12345678
Manufacturing or
12V 9 12 12V987654321
Assembly Site DUNS
TLSYYDDDTRACEDATA or
T Traceability Code 16 17
TLSYYDDD@LOTTRACE
4D Julian Date of Manufacture or 4DYYDDD

5 7
Assembly in YYDDD Format
GM1737 Part Verification and
20T 16 19 20TCI5678VA2B4C6D8E
Traceability Code
GM1737 Part Verification and
21T 16 19 21TCI5678VLSDDDA2B
Enhanced Traceability Code
Part Version or
2P 3 5 2P00C
Part Number Suffix
22Z Broadcast Code 4 7 22ZA1B2
Continuation of Data
C Variable Variable CL83
(used for Option Code / RPO)
Vehicle Identification
I 17 18 I1G1A2B3C4D5E6F7EX
Number (VIN)
Note 1: See Appendix C2 for additional VPPS location codes.

Note 2: Julian date of manufacture or assembly is contained within the Trace Code. See Appendix B for Julian calendar.
Note 3: For additional data identifiers, see Appendix A.
Note 4: See Appendix K for Tire Data trace syntax. See Appendix J for Powertrain syntax.
Note 5: Data Identifier C can be used for GM RPO codes.
The VPPS data field (Y) shall be right padded with zeros to meet the fixed length requirement of 14 with the
location code always appearing as the last character. For 7-digit part numbers, the part number data field (P)
shall be left padded with a zero to meet the fixed length requirement of 8. The data identifier “2P” shall be used
for part version and/or suffix where the length is 3 characters alpha and/or numeric and zero padded to the left
as required. Unless otherwise specified, all additional data identifiers shall be padded to the left with zeros.
See Table 4 for proper syntax structure and bar code encodation for the various formats reviewed in this
specification. Note that all information is preceded by a data identifier. The label samples in Figure 6
correspond with the samples in Table 4. The samples contain the proper bar code encodation for the format
specified. See Appendix E, H, and J for additional information.
Table 4: Bar Code
Format Bar Code Syntax and Encodation
Traceability [)>RS06GSY9320000000000XGSP22798287GS12V813026986GST3212212000000009RSEOT
Lot/Batch Trace [)>RS06GSY9320000000000XGSP22798287GS12V813026986GST3212212@00000009RSEOT
Error-Proofing [)>RS 06GSY7329800000000JGSP22801229GS12V825134604GS4D12258RSEOT
GM1737 Trace 20TAS5309E050000001
Powertrain [)>RS 06GSY1210000000000XGSP24257888GS12V138440180GST11120934ACOX0043 RSEOT
Figure 6: Examples of Label Formats and Bar Code Encodations
3.4 Data Matrix and QR Code Physical Requirements.

3.4.1 System/Subsystem/Component/Part Definition. The 2D symbol density (size) is determined by many
factors including the marking area available, the method used to create the mark, the surface type, the
environment, and the imaging device(s) used. To allow for the best possible imager performance, the largest
practical size element/cell dimension that fits within the available area shall be used. Depending on available
area, the element/cell size for printed label should be 0.51 mm (0.02 in) or larger but shall NOT be smaller than
0.381 mm (0.015 in).
Note: If space constraints dictate a smaller element/cell size, then it shall be agreed to by GM and Supplier
and tested using the GM specified imager.
3.4.2 Data Matrix and QR Code Quiet Zones. The 2D symbol shall include a quiet zone around the entire
perimeter (all four sides). Failure to comply with the minimum quiet zone requirements may result in a non-
decodable symbol.
3.4.2.1 Data Matrix Quiet Zone. The Data Matrix quiet zone is equal to two times the symbol cell dimension
(Figure 7).

Figure 7: Quiet Zone Requirement for Data Matrix
3.4.2.2 QR Code Quiet Zone. The QR Code quiet zone is equal to four (4) times the symbol cell dimension
(Figure 8).
Figure 8: Quiet Zone Requirement for QR Code
3.4.2.3 Error Correction Levels. Refer to Appendix D for information on error correction levels.
3.5 Rectangular Data Matrix. For labeling/DPM and reading, flat surfaces are preferred over curved surfaces.
Although square symbols are more efficient, rectangular symbols may be used when the space available will
not accommodate a square, particularly when the part is cylindrical (Figure 9). The curvature of an item may
prohibit proper labeling or DPM and may distort the code to the point that it cannot be decoded. If the label or
DPM is on a round/curved surface, the symbol height SHOULD be < 16% of the part’s circumference
(Figure 9). The bar code content, cell size and quiet zone requirements specified in paragraph 3 apply to
rectangular matrices. See Figure 10 for a sample label image.
Figure 9: Guideline for Label or DPM on a Curved Surface

Figure 10: Example of Rectangular Data Matrix
3.6 Label Design Requirements. This specification defines the label requirements for part/component labels
that contain bar code information. For labels that contain additional information, the label needs to meet the
design requirements of GMW14089 in addition to those in this standard. Labels should not be visible to the
customer after component/assembly installation.
Trace labels can be combined with other part label requirements (example: information, warning, regulatory)
provided the trace content is visibly separate from the other information. See Figure 11 for label samples with
warning and/or regulatory requirements included. Additional bar codes (supplier internal tracking) shall NOT be
included. Only the GM-required bar code is allowed on the label; however, additional supplier information can
be included in the GM-required bar code (Figure 12). See Appendix F for instructions on how to include
additional information into the GM-required 2D bar code.
Figure 11: Label Samples with Regulatory and/or Warning requirements included
Figure 12: Label Samples Demonstrating Proper and Improper Methods of Adding Supplier Information
A This label is acceptable where the additional supplier information is added to the 2D bar code.
B This label is unacceptable as it contains three bar codes.
3.6.1 Printing. When printing with thermal transfer printers, resin or resin/wax compound based ribbon shall
be used. Wax based ribbons should be avoided for many reasons including smearing, decreased scratch
resistance, and poor solvent resistance. Printed bar codes shall meet minimum ANSI Grade C at GM point of
scan as detailed in paragraph 7. Label performance characteristics shall comply with GMW14573. If additional
information is combined into one single label, the most stringent performance testing shall apply.
3.6.2 Label Construction.
Best imager/scanner performance is achieved with white background and black print or black background
and white print (reverse image). Deviations from this scheme require rigorous testing and GM approval.
Label material with a reflective or shiny surface should be avoided when possible as glare from the label
may interfere with the scannability of the bar code. Labels with a matte finish offer improved scannability.

Distinct graphic images should be used in place of color when visual error proofing is needed. Use of
graphic indicators or visual error proofing will be reviewed on an individual basis. See Figure 6 for
examples.
3.6.3 Human Readable Information (HRI).
HRI may be printed in the area surrounding the symbol but shall NOT interfere with the symbol or quiet
zones.
Data Identifiers (i.e. Y, 12V, P, T, 4D) shall NOT appear in the HRI. Data Identifiers shall be encoded in the
bar code only.
The Message Header, Data Field Separators, and Message Trailers shall NOT appear in the HRI.
3.6.4 Font Specification.
The font shall be as large as practical.
Human Readable Information (HRI) shall be uppercase (capital letters) Arial Narrow BOLD, Helvetica
Condensed or equivalent.
All reference to font type and size is based on MS Office fonts for reference purposes only. Font size is
based on a system termed points.
To facilitate quick visual product identification and/or error proofing of the GM part number, the last four
digits of a GM assigned part number shall be printed/DPM in a larger font size as illustrated in Table 5.
Table 5: Enhanced GM Part Number Font Guideline
MS Office Font Size EXAMPLES of Fonts
(First 4 numbers/Last 4 numbers) Arial Narrow Bold
8 point / 14 point 12345678
12 point / 18 point 12345678
14 point / 24 point 1234 5678

3.7 Scanners/Imagers.
Bar Code scanners/imagers, either handheld or stationary mounted, used in GM plants shall meet the
requirements of and have their Bill of Material (BOM) included in GM&Q IT Standards. BOM information
shall be made available to the suppliers.
Imagers have the capability to edit data within the device by the use of scripts which may be encoded into
a special 2D programming symbol. Scripts can add, delete, parse, and/or modify data and may include
prefix/suffix characters. The use of scripts may be necessary to modify the VPPS position code in
instances where the same part will be installed in multiple locations on a single vehicle. In these situations,
the supplier codes the VPPS position code as “N”. Assembly center operations manage the installation
location via the VPPS position code using a script to convert location code “N” to the assembled/installed
location of the part. See Appendix C2 for VPPS position codes.
4 Single Data Field Encodation

Single data field encodation shall only be used for scanning the Vehicle Identification Number (VIN) or for
components identified with a KCDS code of VER.
An ANSI MH 10.8.2 Data Identifier shall be used. For VIN, the appropriate Data Identifier assigned is “I”. The
encoded DI shall be the first character preceding the data, and headers or trailers shall not be used in the
encodation. The Vehicle Identification Number (VIN) is quite often a stand-alone bar code on the VIN plate or
on an emission label. Reference GMW14574 for VIN specifications. See Figure 13 for an example of a single
data field encodation and bar code.

Figure 13: Single Data Element Encoded for 17 Character VIN
5 Linear 1D Bar Codes

GM is phasing out 1D bar codes for component parts. See Appendix H as a reference for carryover parts.
6 Direct Part Marking (DPM)

DPM may be used in place of labels in certain situations. Examples include:
The part is too small to be labeled with traditional bar code labels.
The part is subjected to environmental conditions that preclude the use of labels.
DPM may be more cost efficient than individual item labels.
Refer to Appendix L for guidelines and considerations for DPM.
7 Symbol (Bar Code) Quality Verification

7.1 Label Performance Testing. Verification devices are quality control tools for verifying the readability and
standards compliance of printed bar code symbols. Scanning is not considered verification. Verification testing
shall be performed on labels and direct marked parts. QR Codes are NOT permitted on DPM applications at
this time. Testing must be done on production intent labels (i.e. VPPS, Part Number, DUNS, and
Traceability/Date must be shown on sample).
7.2 Bar Code Print Quality on Labels. Label Samples Demonstrating Proper Method of Adding Supplier
Information. ISO/IEC 15415 (Print Quality Test Specification - Two-dimensional symbols), ISO/IEC 16022
(Data Matrix), and ISO/IEC 18004 (QR Code) shall be used to determine Data Matrix and QR Code print
quality. The grades are the result of specific measurements made according to the AIM International
Symbology Specification Document quality definition for:
Symbol decode
Symbol contrast (modulation)
Symbol print (fixed pattern damage)
Symbol axial non-uniformity
Symbol error correction
8 Additional Product Characteristics

8.1 Additional Information. Additional information may be added to the label to demonstrate product
characteristics. See Appendix F for additional information and examples of current, pressure, voltage,
temperature, etc.
Note: Tires shall follow Appendix K.
8.2 As-Built Label. The “As-Built” label/DPM provides a means of capturing the trace data as part of an
external assembly process such as a Value Added Assembler (VAA). The 2D bar code is structured to include
(“roll up”) individual trace records for each component in the assembly that requires traceability into a single
label. For example, a fuel tank assembly consists of five (5) traceable components. Since those components
are delivered to the GM facility as an assembly, a single label must be created that encompasses the
traceability data for all five components. See Appendix G for instructions to develop an as-built label.

9 Radio Frequency Identification (RFID)

When RFID tags become cost effective for identification of parts, components, assemblies and modules, the
Data Syntax and data fields will be encodable in passive or active RFID tags containing user memory. The
standard used to encode data into the 2D symbologies has been incorporated into the AIAG B-11 RFID
Standard making the two technologies interchangeable from a data/IT perspective. AIAG B-11 is fully ISO/IEC
compliant.
10 Validation
10.1 Responsibility. The component Design Release Engineer (DRE) is responsible for releasing bar codes/
labels/ DPM compliant to this standard.
10.2 Form. The CG2503 Bar Code Content and Format Validation Form shall be used to ensure the correct
bar code content, bar code scan quality and plant readiness.
The DRE shall initiate the form as part of the SOR or EWO process by filling out Section 1 of the form.
The supplier shall complete the required sections and submit the form with scanned label samples for GM
Validation.
Upon final content and quality validation, the DRE shall approve the form.
The Supplier shall provide the approved form as part of the PPAP submission process.
The form along with production intent labels shall be sent to each affected assembly center for scanner
configuration and testing when necessary.
10.3 Process. CG2503 is stored in the GDM General Forms and Templates folder. The CG2503 process and
RASIC are documented on the Bar Code web site:
https://gmweb.gm.com/sites/toolkit/48lnl/Pages/Barcodes.aspx
10.4 Additional Information. Additional information such as a compressed VPPS link, KCDS Requirements
and training materials can also be found on the Labels and Literature Website indicated above.
11 Notes
11.1 Glossary.
2D (Two-dimensional) Symbols: Optically readable symbols that must be examined both vertically and
horizontally to read the entire message. Two-dimensional symbols may be one of two types: matrix symbols
and multi-row symbols. Two-dimensional symbols have error detection and may include error correction
features. (See matrix symbol.)
AIAG: Automotive Industry Action Group www.aiag.org.
AIM: Automatic Identification Manufacturers Association www.aimglobal.org.
Alphanumeric: A character set that contains both alphabetic character (letters) and numeric digits (numbers)
and usually other characters such as punctuation marks.
ANSI or ANS: American National Standards Institute.
Auto-discrimination: The ability of a bar code scanner/imager to automatically distinguish between two or
more symbologies (e.g., Code 128, Code 39, Data Matrix and QR Code).
Bar Code (also barcode): An optically machine-readable representation of data. Traditionally, bar codes
represented data in the widths (lines) and the spacings of parallel lines and may be referred to as linear or
one-dimensional (1D) bar codes or symbologies. But they also come in patterns of squares, dots, hexagons
and other geometric patterns within images termed two-dimensional (2D) matrix codes or symbologies. It is
important to note that both the patterns (lines, squares, dots, etc.) and spacings constitute the data encodation
schema.
Bar Code Label: A generic term covering labels that have 1D and/or 2D bar code symbols, with or without
human readable data, printed on them.
Batch: Batch production is a manufacturing method used to produce or process any product in batches, as
opposed to a continuous production process, or a one-off production. Examples of batch are castings (based
on pour), paint (based on a single blend of ingredients), adhesives, steel, etc.
Cell: See module.

Component: A part, assembly, or raw material that is a constituent of a higher level assembly.
Data Field: A message consisting of a data identifier immediately followed by its associated data.
Data Format: Letters and numbers used to denote the type of data allowed within the referenced data field,
and the total quantity of that type of data allowed in the data field.
Data Format Examples:
"an.6" means up to six characters of alpha-numeric data are allowed.
"n.12" means up to 12 characters of only numeric data are allowed.
Data Identifier (DI): A specified character, or string of characters, that defines the intended use of the data
element that follows. For the purposes of automatic data capture technologies, Data Identifier means the
alphanumeric identifiers, as defined in ISO/IEC 15418, UCC/EAN Application Identifiers and FACT Data
Identifiers and Maintenance and ANSI MH10.8.2.
Data Matrix: Specific two-dimensional bar code symbology.
Data Syntax Codes: ASCII characters used in ISO/IEC 15434 to denote specific functions within the data
enveloping structure.
Decimal: A base 10 numbering system, whose numbers are represented by X10, when a decimal number
needs to be denoted from a hexadecimal number (X16).
Direct Part Marking: A marking applied directly to a part’s surface using intrusive or non-intrusive marking
techniques.
DOT: Department of Transportation (US).
DUNS: A nine digit site specific trading partner identification code assigned by Dun and Bradstreet
www.dnb.com.
Error Correction: Mathematical techniques used to reconstruct missing or damaged data.
Hex: Hexadecimal describes a base 16 number system. The hexadecimal numbers are 0 thru 9 and then the
letters A thru F, whose numbers are represented by X16, when a hexadecimal number needs to be denoted
from a decimal number (X10).
Human Readable Information: Information that may appear and be associated with a machine readable
medium, typically on a label (e.g., bar code, 2D symbol, RF tag) intended to convey information to a person.
IEC: International Electrotechnical Commission. International standards and conformity assessment for
government, business, and society for all electrical, electronic, and related technologies.
ISO: International Organization for Standardization. ISO is a network of the national standards institutes of 156
countries, on the basis of one member per country, with a Central Secretariat in Geneva, Switzerland, that
coordinates the system.
ISO/IEC: Represents work done and/or supported by both the ISO and IEC organizations.
Imager (See scanner): A type of bar code scanner used to read linear bar codes and 2D symbols using
optical imaging technology (typically a camera based matrix array or linear array optical sensor technology).
Individual Part: A single part, item, or material purchased, manufactured, and/or distributed.
Intrusive Marking: Any device designed to alter a material surface to form a human or machine readable
symbol. This marking category includes, but is not limited to: devices that abrade, burn, corrode, cut, deform,
dissolve, etch, melt, oxidize, or vaporize a material surface.
Julian Date: In the commercial world the term "Julian date" is the number of the day in a particular year, so
that January 1st = day 1, February 28th = day 59, and so on. It is the actual day of manufacture/assemble.
Label: Produced by any means, on a piece of paper, cloth, polymer, metal, or other material, affixed to
something via a pressure-sensitive backing or heat application, uses black images on a white background or
white images on a black background (reverse image) to indicate its contents, destination, or other information.
Laser: Light amplification by stimulated emission of radiation.
Linear Bar Code Symbol (1D): An optically readable array of parallel rectangular bars and spaces of varying
thickness and spacing that are arranged in a predetermined pattern following specific rules to represent
elements of data that are referred to as characters. A linear bar code symbol typically contains a leading quiet
zone, start character, data character(s), stop character, and a trailing quiet zone, and is read in only one axis.

Lot: See Batch.

Manufacturer: The actual producer or fabricator of an item, not necessarily the supplier in a transaction.
Manufacturing or Assembly Site DUNS Number: The numeric DUNS ID code used to identify the specific
location where a part was created by the supplier/vendor.
Matrix Symbol: A collection of polygonal or circular elements in a regular pattern to represent data for retrieval
by a vision scanning system.
Module: In a linear or multi-row bar code symbology, the nominal unit of measure in a symbol character. In
certain symbologies, element widths may be specified as multiples of one module. Equivalent to X Dimension.
In a matrix symbology, a single cell or element used to encode one bit of the codeword.
Multi-row symbology (also known as stacked symbology), a bar code symbology in which the symbol
consists of two or more vertically adjacent rows of symbol characters.
Mutually Defined: A meaning that is agreed upon by all appropriate parties to a transaction.
NASA: National Aeronautics and Space Administration (US).
Non-Intrusive Marking: A method of forming markings by adding material to a surface. Non-intrusive methods
include ink-jet, laser bonding, liquid metal jet, silk screen, and thin film deposition.
Part: An identifiable item that has a unique name and/or number assigned to it.
QR Code: Specific two-dimensional bar code symbology.
Revision Level: Code assigned such as Engineering Change Level, revision or edition or software version.
RS232: A standard for serial binary data signals. It is commonly used in computer serial ports.
Scanner (See Imager): An input device that sends signals proportional to the reflectivity of each successive
element of the symbol (linear or 2D) to the decoder.
Serial Number: A unique code assigned to an entity for the life of the entity, such as an air bag module,
engine or transmission assembly, for the differentiation of that specific entity from any other like entity.
Supplier/vendor: In a transaction, the party that produces, provides, or furnishes a product or service.
Supplier/Vendor ID: The numeric DUNS ID code used to identify the supplier/vendor.
Symbology: A standard means of representing data in an optically readable form. Each symbology
specification sets out its particular rules of composition or symbol architecture.
Two-Dimensional Symbol (2D): An optically readable symbol that must be examined both vertically and
horizontally to read the entire message. Two-dimensional symbols differ from linear bar codes in that they are
made up of “pixel elements” that are comparable to the bars in linear bar codes.
Vehicle Partitioning and Product Structure (VPPS): Represents a globally consistent means for describing
vehicle content. VPPS is a hierarchical structure that has consistency across major vehicle areas (Powertrain,
Chassis, etc.) VPPS is a mechanism that allows data sharing/comparing across systems globally (GMNA,
GME, GMLAAM, GMAP, etc.) VPPS is a standard global product breakdown structure approved by GEDOC
(NOA 002) and GADVC (NOA 012). Changes are managed via global process.
X Dimension: The specified width of the narrow elements in a bar code symbol or the specified width of a
single element/cell in a two-dimensional symbol.
Year: In the context of traceability, year is the actual year of manufacture/assemble as opposed to "model
year".
11.2 Acronyms, Abbreviations, and Symbols.
1D One-Dimensional or also termed a linear bar code symbol
2D Two-Dimensional
AIAG Automotive Industry Action Group
AIDC Automatic Identification Data Collection Technology
AIM Automatic Identification Manufacturers Association
ANS American National Standard
ANSI American National Standards Institute

ASCII American Standard Code for Information Interchange

BOM Bill of Material
CI Component Identifier
CO2 Carbon Dioxide
CR Change Request
DFMEA Design Failure Mode Effects Analysis
DI Data Identifier
DNB Dun and Bradstreet
DOT Department of Transportation
DPM Direct Part Marking
DUNS Data Universal Numbering System
DRE Design Release Engineer
EC Error Correction
ECC Error Correction Code
EDM Electric Discharge Machining
EOT End of Transmission
FMVSR Federal Motor Vehicle Safety Regulation
GM&Q Global Manufacturing and Quality
GPDS Global Product Description System
HRI Human Readable Information
IEC International Electrotechnical Commission
in inch
ISO International Organization for Standardization
IT Information Technology
KCDS Key Characteristics Designation System
ME Manufacturing Engineering
NASA National Aeronautics and Space Administration (US)
NOA Notice of Action
OEM Original Equipment Manufacturer
PE Process Engineering
PFMEA Process Failure Mode and Effects Analysis
PRTS Problem Reporting and Tracking System
pt Points
QR Quick Response
RF Radio Frequency
RFID Radio Frequency Identification
SOR Statement of Requirements
TRA Traceability
UCC/EAN Uniform Code Council/European Article Number
USB Universal Serial Bus
ULD Unit Load Device
UV Ultraviolet
V Vendor/Supplier Identifier
VAA Value Added Assembler

VDC Voltage Direct Current

VER Verification
VIN Vehicle Identification Number
VPPS Vehicle Partitioning and Product Structure
12 Additional Paragraphs
12.1 All parts or systems supplied to this standard must comply with the requirements of GMW3059,
Restricted and Reportable Substances for Parts.
13 Coding System
This standard shall be referenced in other documents, drawings, etc., as follows:
GMW15862
14 Release and Revisions

This standard was originated in March 2008. It was first approved by Interiors Global Technology Engineering
in November 2008. It was first published in December 2008.
Issue Publication Date Description (Organization)
1 DEC 2008 Initial publication.
2 OCT 2009 Revised to add VPPS code to the bar code content. Identified structure for
lot/batch traceability. Examples added. Sections 2.1, 2.3, 9, 11 updated;
Major rewrites to Sections 3, 4, 5, 6, 7. Sequence of appendices modified to
enhance usability. (Interior)
3 NOV 2010 Removed the Transition Label formats.
Replaced Appendix J with Powertrain formats.
Added references to the Powertrain traceability formats.
Added the Validation section requiring CG2503.
Modified Table C2. Corrected bar code figures. (Labels &Literature GSSLT)
4 APR 2013 Updated content, conversion into new template. (Interior)
5 JUN 2013 Appendix J: Statement “Position 13…, an ‘X’ shall be used.” exchanged by
“For engines, …In all other cases, an ‘X’ shall be used.
For transmissions, …to maintain trace code uniqueness for Transmission
Programs.”

Appendix A
A1 Typical Data Identifiers

ANSI MH10.8.2 defines more than 100 Data Identifiers for many purposes in many industries. GM requires the
use of Data Identifiers. The following table includes some of the typical DIs in ANSI MH10.8.2 frequently used
in the automotive industry. Due to frequent updates to ANSI MH10.8.2, a draft copy is maintained at
www.autoid.org at the following url: http://www.autoid.org/ANSI_MH10/ansi_mh10sc8_wg2.htm.
Table A1: Typical Data Identifiers Used in the Automotive Industry
DI Description
B Container type (internally assigned or mutually defined)
1B Returnable container identification code assigned by the container owner or the appropriate regulatory
agency (e.g., a metal tub, basket, reel, Unit Load Device (ULD), trailer, tank, or intermodal container)
(excludes gas cylinders) (See "2B")
2B Gas Cylinder Container Identification Code assigned by the manufacturer in conformance with U.S.
Department of Transportation DOT standards
C Continuation of Data
D Date, in the format YYMMDD (Mutually defined significance)
1D Date in the format DDMMYY (Mutually defined significance)
2D Date in the format MMDDYY (Mutually defined significance)
3D Date in the format YDDD (Julian mutually defined significance)
4D Date in format YYDDD (Julian mutually defined significance)
5D Date in ISO format YYMMDD immediately followed by an X12.3 Data Element Number 374 Qualifier
providing a code specifying type of date (e.g., ship date, manufacturing date)
1E Air pressure expressed in Pascal’s as the standard international measure
I Vehicle Identification Number (VIN)
2I Abbreviated VIN Code (example PVI, order ID. sequence ID)
5N Coding Structure and Formats in Accordance with AIAG Recommendations. The full Data Identifier is in
the form 5Nxx where xx is found in the full code list that can be found at www.aiag.org
P Item Identification Code assigned by GM
1P Item Identification Code assigned by Supplier
2P Code assigned to specify the revision level of the part (e.g., Engineering Change Level, revision or
edition, software revision level)
20P Legacy GM1737 Verification/Error Proofing code/structure as defined by GM
Q Quantity, Number of Pieces, or Amount (numeric only)(unit of measure and significance mutually
defined)
1Q Theoretical Length/Weight (numeric only) (historically used in the shipment of primary metals)
2Q Actual Weight (numeric only)
7Q Quantity and unit of measure in the format: Quantity followed by the two-character Unit of Measure
code as defined in Data Element number 355 of the ANSI X12.3 Data Element Dictionary standard
S Serial Number assigned by Supplier to an entity for its lifetime
10S Machine, work cell or tool ID code
11S Fixed Asset ID Code

DI Description
T Traceability code/structure as defined by GM
1T Traceability number assigned by the Supplier/Manufacturer
20T Legacy GM1737 Part Verification and Traceability code/structure as defined by GM
21T Legacy GM1737 Part Verification and Enhanced Traceability code/structure as defined by GM
12V DUNS number identifying Manufacturing/Assembly site
14V DUNS number identifying specific GM site as the customer
Y GM Internal applications -- Assigned to VPPS compressed code.
Z Mutually defined between GM and Supplier (title to reflect mutually agreed-to meaning)
22Z Broadcast Code
20Z Frame Code (GM Specific)
21Z Caster/Camber Code (GM Specific)

Appendix B
B1 JULIAN Calendar
Table B1: Perpetual Julian Date Calendar
Day Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Day
1 001 032 060 091 121 152 182 213 244 274 305 335 1
2 002 033 061 092 122 153 183 214 245 275 306 336 2
3 003 034 062 093 123 154 184 215 246 276 307 337 3
4 004 035 063 094 124 155 185 216 247 277 308 338 4
5 005 036 064 095 125 156 186 217 248 278 309 339 5
6 006 037 065 096 126 157 187 218 249 279 310 340 6
7 007 038 066 097 127 158 188 219 250 280 311 341 7
8 008 039 067 098 128 159 189 220 251 281 312 342 8
9 009 040 068 099 129 160 190 221 252 282 313 343 9
10 010 041 069 100 130 161 191 222 253 283 314 344 10
11 011 042 070 101 131 162 192 223 254 284 315 345 11
12 012 043 071 102 132 163 193 224 255 285 316 346 12
13 013 044 072 103 133 164 194 225 256 286 317 347 13
14 014 045 073 104 134 165 195 226 257 287 318 348 14
15 015 046 074 105 135 166 196 227 258 288 319 349 15
16 016 047 075 106 136 167 197 228 259 289 320 350 16
17 017 048 076 107 137 168 198 229 260 290 321 351 17
18 018 049 077 108 138 169 199 230 261 291 322 352 18
19 019 050 078 109 139 170 200 231 262 292 323 353 19
20 020 051 079 110 140 171 201 232 263 293 324 354 20
21 021 052 080 111 141 172 202 233 264 294 325 355 21
22 022 053 081 112 142 173 203 234 265 295 326 356 22
23 023 054 082 113 143 174 204 235 266 296 327 357 23
24 024 055 083 114 144 175 205 236 267 297 328 358 24
25 025 056 084 115 145 176 206 237 268 298 329 359 25
26 026 057 085 116 146 177 207 238 269 299 330 360 26
27 027 058 086 117 147 178 208 239 270 300 331 361 27
28 028 059 087 118 148 179 209 240 271 301 332 362 28
29 029 088 119 149 180 210 241 272 302 333 363 29
30 030 089 120 150 181 211 242 273 303 334 364 30
31 031 090 151 212 243 304 365 31

Table B2: Leap Year Julian Date Calendar
Day Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Day
1 001 032 061 092 122 153 183 214 245 275 306 336 1
2 002 033 062 093 123 154 184 215 246 276 307 337 2
3 003 034 063 094 124 155 185 216 247 277 308 338 3
4 004 035 064 095 125 156 186 217 248 278 309 339 4
5 005 036 065 096 126 157 187 218 249 279 310 340 5
6 006 037 066 097 127 158 188 219 250 280 311 341 6
7 007 038 067 098 128 159 189 220 251 281 312 342 7
8 008 039 068 099 129 160 190 221 252 282 313 343 8
9 009 040 069 100 130 161 191 222 253 283 314 344 9
10 010 041 070 101 131 162 192 223 254 284 315 345 10
11 011 042 071 102 132 163 193 224 255 285 316 346 11
12 012 043 072 103 133 164 194 225 256 286 317 347 12
13 013 044 073 104 134 165 195 226 257 287 318 348 13
14 014 045 074 105 135 166 196 227 258 288 319 349 14
15 015 046 075 106 136 167 197 228 259 289 320 350 15
16 016 047 076 107 137 168 198 229 260 290 321 351 16
17 017 048 077 108 138 169 199 230 261 291 322 352 17
18 018 049 078 109 139 170 200 231 262 292 323 353 18
19 019 050 079 110 140 171 201 232 263 293 324 354 19
20 020 051 080 111 141 172 202 233 264 294 325 355 20
21 021 052 081 112 142 173 203 234 265 295 326 356 21
22 022 053 082 113 143 174 204 235 266 296 327 357 22
23 023 054 083 114 144 175 205 236 267 297 328 358 23
24 024 055 084 115 145 176 206 237 268 298 329 359 24
25 025 056 085 116 146 177 207 238 269 299 330 360 25
26 026 057 086 117 147 178 208 239 270 300 331 361 26
27 027 058 087 118 148 179 209 240 271 301 332 362 27
28 028 059 088 119 149 180 210 241 272 302 333 363 28
29 029 060 089 120 150 181 211 242 273 303 334 364 29
30 030 090 121 151 182 212 243 274 304 335 365 30
31 031 091 152 213 244 305 366 31

Appendix C
C1 Vehicle Partitioning and Product Structure (VPPS)

The Vehicle Partitioning and Product Structure (VPPS) is a globally consistent means for describing vehicle
content (http://gmna1.gm.com/eng/grc/vpps/index.html). VPPS is a hierarchical structure that has consistency
across major vehicle areas (Powertrain, Chassis, etc.). VPPS is a mechanism that allows data
sharing/comparing across systems globally (GMNA, GME, GMLAAM, GMAP, etc.). VPPS is a standard global
product breakdown structure. Changes are managed via global process.
C1.1 Compressed VPPS. GMW15862 assigns the Data Identifier Y to Compressed VPPS codes and right
pads the data with zeros (0) for the remaining levels to make a total of 14 data characters including the 14 th
character location code. The VPPS code can be determined by searching the part number in APM utilizing the
‘Part Where Used Inquiry’. See Table C1 for a sample.
Table C1: Example of APM ‘Part Where Used Inquiry’
APM shows the expanded VPPS; however, this specification requires that all VPPS codes be displayed as
compressed. In addition, some categories in APM do not directly correlate to the compressed VPPS (such as
fuel tanks). The GM DRE can confirm the correct VPPS is being used by cross-referencing the VPPS code in
APM to the compressed VPPS code provided at the following website:
https://pd.gm.com/vpps/vppsapp/browseClassification.do
This same web site can be used to determine the correct VPPS for parts that do not have part numbers
established yet.
The Compressed VPPS Structure is as follows:

Decimals are implied (not encoded) in the compressed VPPS.
The first three zeros (the first three ‘layers of hierarchy’) of the expanded VPPS shall not be shown in the
compressed VPPS format.
The 14th character of the VPPS is the location code (see Appendix C2 for available location codes).
For example, the VPPS shown in Table C1 would have a Compressed VPPS of 4710000000000000X.
An expanded VPPS of 40.07.03.02.01 would be compressed to read 4730201000000X (see Figure C1).
Figure C1: Compressed VPPS Structure

C1.2 VPPS Location Code. The last (14th) character of the VPPS code shall be used to reference part
installation location.
When a single part number with a single VPPS code can be installed in different locations, but only ONCE
on a vehicle, “X” shall be used to indicate the location code is not applicable. (See Scenario 1 in Table C3.)
For example, a steering wheel airbag will have a VPPS location code of “X” since there can be only one
steering wheel in a vehicle. Depending on whether a vehicle is built as left-hand drive or right-hand drive,
the steering wheel installation location (which includes the steering wheel airbag) may change, but the part
will always remain singular on the vehicle.
When a single part number with a single VPPS code will be installed more than once on a vehicle, “N” shall
be used, indicating that the scanning station must be programmed to modify the final character encodation
according to Table C2. The actual location code will be forced into the data string at the scanning station or
when electronic module information is transferred to the database. (See Scenario 2 in Table C3.)
For example, a seat belt buckle assembly that is used on both sides of the vehicle may have the
compressed VPPS of 462.02. The encodation within the data field and on the Human Readable portion of
the label is 4620200000000N. For the assembly installed on the right side of the vehicle, the scanning
station will be configured to encode the VPPS as 4620200000000R. The identical assembly installed on the
left side of the vehicle will have its scanning station configured to encode the VPPS as 4620200000000L.
In all other cases, the 14th character location code shall be assigned according to the position codes listed
in Table C2 based on what is most appropriate for the part. (See Scenarios 3, 4 and 5 in Table C3.)
See Table C3 for additional example scenarios.
Table C2: 14th Character Compressed VPPS Position Codes for Vehicle Mounting Location
Character Definition Character Definition
PLANT ACTION
A Side Left Rear N REQUIRED (multiple
installation locations)
B Side Left Front O Do Not Use
C Side Right Rear P Center Left
D Side Right Front Q Do Not Use
E Roof Left Rear R Right
F Roof Left Front S Center Right
G Roof Right Rear T Left Rear
H Roof Right Front U Left Front
I Do Not Use V Right Rear
J Center W Right Front
K Roof Rear X Not Applicable
L Left Y Front
M Roof Front Z Rear
Note: “N” shall be the trigger for assembly centers, VAAs, etc. that scanning stations shall be configured to
convert the 14th position to the actual installation position.

Table C3: Examples of Position Code Application under different Part Usage Scenarios
Position Code
Part Position
Examples: VPPS on Label Notes
Number(s) on vehicle
& Bar Code
Scenario 1: Single VPPS and left side X Part could be used in various locations
part number, location varies; based on vehicle configuration (example:
but only one part per vehicle 477.02 55555555 OR same steering wheel or knee air bag used
on a LHD vehicle and a RHD vehicle, but
right side X only used once per vehicle)
Scenario 2: Same VPPS, same Plant MUST program scan station to

33333333 left side N
part numbers change position code to L
472.05
Plant MUST program scan station to
33333333 right side N
change position code to R
Scenario 3: Same VPPS, Use position code to uniquely identify the

11111111 left side L
different part numbers install location of the part. (The part
477.02
number does NOT do this for the scanning
22222222 right side R system.)
Scenario 4: Different VPPS, While a unique location code is not
477.02 11111111 left side L
same part numbers required by the system to identify the
scan, L and R codes would assist the
477.04 22222222 Right Side R plant.
Scenario 5: Different VPPS,

477.02 11111111 left side L
same part numbers While a unique location code is not
required by the system to identify the
477.03 44444444 Center J scan, L, J, and R codes would assist the
plant.
477.04 22222222 right side R

Appendix D
D1 Data Matrix Reference Information

D1.1 Anatomy of a Data Matrix. The following is intended as an aide in understanding some of the
characteristics of the Data Matrix symbology. Included is a procedure to estimate the symbol size for planning
the area required for the Data Matrix symbol.
Figure D1: Anatomy of a Data Matrix Symbol and Eight Bits of Each Byte
are Distributed within a 10 x 10 Data Matrix Symbol
Table D1: Data Matrix Data Capacity (Square Symbol)

Symbol Size
Rows 10 12 14 16 18 20 22 24 26 32 36 40 44 48 52 64 72 80 88 96 104 120 132 144
Columns 10 12 14 16 18 20 22 24 26 32 36 40 44 48 52 64 72 80 88 96 104 120 132 144
Data Capacity
Numeric 6 10 16 24 36 44 60 72 88 124 172 228 288 348 408 560 736 912 1152 1392 1632 2100 2608 3116
Alphanumeric 3 6 10 16 25 31 43 52 64 91 127 169 214 259 304 418 550 682 862 1024 1222 1573 1954 2335
Byte 1 3 6 10 16 20 28 34 42 60 84 112 142 172 202 278 366 454 574 694 814 1048 1302 1556
Table D2: Data Matrix Data Capacity (Rectangular Symbol)

Symbol Size
Rows 8 8 12 12 16 16
Columns 18 32 26 36 36 48
Data Capacity
Numeric 10 20 32 44 64 98
Alphanumeric 6 13 22 31 46 72
Byte 3 8 14 20 30 47
The maximum data capacity already takes into account the control character fields as part of the character
count. To estimate the Data Matrix symbol size (Length x Height) use the following procedure. Actual results
will depend on printing/DPM system used.

a. Count the number of data characters to be encoded____________.

b. Go to Table D1 for a square or D2 for a rectangular Data Matrix symbol.
c. Find the alphanumeric number equal to or next greater than the character count.
d. Rows = __________.
e. Columns = __________.
f. Cell/element size = __________.
g. Multiply number of Rows (d) by Cell/element size =__________width.
h. Multiply number of Columns (e) by Cell/element size =__________height.
i. Quiet Zone = 4 x Cell/element size = _________.
j. Add Quiet Zone (i) to width (g) = _________estimated total width.
k. Add Quiet Zone (i) to height (h) = __________estimated total height.
Table D3 shows reference encodation and number of characters for the following:
1. Traceability with Serial Number
2. Traceability with Lot or Batch identification
3. Verification (Error Proof)
4. Product Identification
5. VIN (Vehicle Identification Number)
Use Table D3 to work through Examples 1 to 4 to determine Data Matrix symbol size.
Table D3: Reference Data Encodation
Character Count
Function Data Content Encoded Data Syntax
Alphanumeric (an)
1 Traceability Compressed VPPS With 06 Macro = 57 an
Serial GM Part Number
[)>RS06GSY0000000000000XGS
Number P12345678GS12V987654321GS
Manufacturing or assembly site DUNS
TLSYYDDDA2B4C6000RSEOT Without 06 Macro = 65 an
GM defined trace code
2 Traceability Compressed VPPS With 06 Macro = 57 an

Lot or Batch GM Part Number
[)>RS06GSY0000000000000XGS
P12345678GS12V987654321GS
TLSYYDDD@2B4C6000RSEOT Without 06 Macro = 65 an
GM defined trace code
3 Part Compressed VPPS With 06 Macro = 47 an

Verification GM Part Number
[)>RS06GSY0000000000000XGS
(Error P12345678GS2V987654321GS4
Proofing) DYYDDD RSEOT Without 06 Macro = 55 an
Julian date manufacturing /assembly
4 Product Compressed VPPS

Identification GM Part Number [)>RS06GSY0000000000000XGS With 06 Macro = 47an
with Julian
date of Manufacturing or assembly site DUNS P12345678GS2V987654321GS4
manufacture Julian manufacturing or assembly date DYYDDD RSEOT
or assembly Without 06 Macro = 55 an
5 VIN (Vehicle 17 character vehicle identification IA2B4C6D8E0F2G4H6I 18 an
Identification number
Number)
Example 1: Error-Proofing (Julian Date) with 06 Macro and Square Data Matrix Symbol
a. Count the number of data characters to be encoded: 47.
d. Rows = 24.

e. Columns = 24.
f. Cell/element size = 0.5 mm.
g. Multiply number of Rows (d) by Cell/element size = 12 mm width.
h. Multiply number of Columns (e) by Cell/element size = 12 mm height.
i. Quiet Zone = 4 x Cell/element size = 2 mm.
j. Add Quiet Zone (i) to width (g) = 14 mm estimated total width.
k. Add Quiet Zone (i) to height (h) = 14 mm estimated total height.
Note: In this example using the 06 Macro allowed for a smaller overall symbol size. Without the 06 Macro, the
symbol would have been 26 rows x 26 columns with a symbol size of 15 mm x 15 mm.
Figure D2: Using 06 Macro Resulting in Small Symbol Size
Example 2: Error-Proofing (Julian Date) with 06 Macro Rectangular Data Matrix for a Curved Surface
d. Rows = 16.
e. Columns = 48.
g. Multiply number of Rows (d) by Cell/element size = 6.08 mm width.
h. Multiply number of Columns (e) by Cell/element size = 18.24 mm height.
i. Quiet Zone = 4 x Cell/element size = 1.52 mm.
j. Add Quiet Zone (i) to width (g) = 7.6 mm estimated total width.
k. Add Quiet Zone (i) to height (h) = 19.76 mm estimated total height.
Note: Without the 06 Macro the symbol would have still be the same size as 55 characters would have
required the same 16 rows x 48 columns; however 06 Macro shall be used.
Figure D3: Data Matrix Symbol Size With and Without Macro
Example 3: Traceability with 06 Macro and Square Data Matrix Symbol

d. Rows = 26.
e. Columns = 26.


g. Multiply number of Rows (d) by Cell/element size = 13 mm width.
h. Multiply number of Columns (e) by Cell/element size = 13 mm height.
i. Quiet Zone = 4 x Cell/element size = 2 mm.
j. Add Quiet Zone (i) to width (g) = 15 mm estimated total width.
k. Add Quiet Zone (i) to height (h) = 15 mm estimated total height.
Note: In this example using the 06 Macro allowed for a smaller overall symbol size. Without the 06 Macro the
symbol would have been 32 rows x 32 columns with a symbol size of 18 mm x 18 mm.
Figure D4: Not Using 06 Macro has a Significant Impact on the Data Matrix Symbol Size
Example 4: Vehicle Identification Number (VIN) with a Limitation Not to Exceed 14 mm x 14 mm

a. Count the number of data characters to be encoded = 18
b. Go to Table D1 for a square symbol: 18 rows x 18 columns
c. Overall dimension = 4 x cell size + (number row/column for 18 characters x cell size)
d. 14 mm = 4x + (18x) where x = cell size
e. 14 mm = 22x
f. x = 0.6363 mm
g. Cell size shall not be larger than 0.6363 mm
h. Go to Table D2 for a rectangular symbol: 12 rows x 26 columns
i. Overall width dimension = 4 x cell size + (number column for 18 characters x cell size)
j. 14 mm = 4x + (26x) where x = cell size
k. 14 mm = 30x
l. x = 0.4666 mm
m. Cell size shall not be larger than 0.4666 mm
n. The calculation for height need not be made because the width is the limiting factor.
o. Select the larger cell size between the two calculations, the square symbol with a cell size of 0.6363 mm.
Note: In this example, there is only one data field. As a result, there is no need to use the ISO/IEC 15434 Data
Syntax standard or 06 Macro. Furthermore, given the restriction on the area available, a square Data Matrix
symbol was the logical choice. In addition, a square symbol is preferable for scanning purposes as the
resulting increase in cell/element size improves the read distance. When applicable, a Data Matrix square
symbol is preferred over a rectangular symbol for readability.
Figure D5: Data Matrix Square Symbol v. Data Matrix Rectangular Symbol

D1.2 Allowable Data Characters. The ISO/IEC 646 American Standard Code for Information Interchange
(ASCII) character set for this standard shall consist of any of the following:
Uppercase alpha characters
Numbers 0 to 9
Dash (-)
Period (.)
Underscore (_)
Space ( )
Note: The ASCII characters dollar sign ($), forward slash (/), plus (+), and percent (%) are not recommended
for use with Code 39 and therefore SHOULD be avoided in data fields that may be encoded in both linear 1D
and 2D symbols. This recommendation is based on the potential of Code 39 character substitution errors for
these specific characters (see Appendix H).
The full ASCII character set shall NOT be used for data.
The full ASCII character set is allowed in the Message Header, Message Trailer, and Field Separator, as
defined by ISO/IEC 15434 for High Capacity Media (Data Syntax). These specific ASCII characters are termed
"non-printable control characters" and require different techniques to encode, dependent upon the software
and printer being used.
D1.3 Error Correction Levels.
D1.3.1 Data Matrix Error Correction Code (ECC) Level. ECC 200 shall be used on printed labels and Direct
Part Marking (DPM).
D1.3.2 QR Code Error Correction (EC) Levels. Error correction Level M is recommended in this standard for
QR Codes (Table D4).
Table D4: Error Correction Levels for QR Code
EC Level % EC Description
L 7% Smallest possible symbol size. Requires high level of print/DPM quality
RECOMMENDED
M 15%
Good compromise between small size and level of Error Correction (EC)
Q 25% Suitable for critical or poor print/DPM quality applications providing a high level of EC
H 30% Maximum

Appendix E
Bar Code Structure and Content

The general principle for the order data fields shall be encoded is fixed length data fields first with variable
length data fields to follow. The first data field shall always be the VPPS followed by the part number, DUNS,
and Traceability Data or Julian Date (in that order). For example:
Traceability: Macro 06 (Y) VPPS GS (P) GM Part Number GS (12V) DUNS GS (T) GM Trace Structure GS
(7Q or Q) Product Characteristic(s) GS (DI or DIs) Supplier Data
Part Verification/Error-Proofing: Macro 06 (Y) VPPS GS (P) GM Part Number GS (12V) DUNS GS (4D)
Julian Date of Production/Assembly GS (7Q) Product Characteristic(s) GS (DI or DIs) Supplier Data
E1 GMW15862 Traceability Code Structure and Content

Compressed VPPS with location code (see Appendix C2)
GM assigned part number (8 digits) of the part, component, module, or assembly
DUNS ID of the site that manufactured/assembled the part, component, module, or assembly
The GMW15862 defined trace code (Figures E1 and E2)
The encoded data looks like this:

Compliance Header = [)>RS
[)>RS
Format Header = 06GS
[)>RS06GS
VPPS DI = Y
[)>RS06GSY
VPPS Data = 0000000000000X
[)>RS06GSY0000000000000X
Part Number DI = P
[)>RS06GSY0000000000000XGSP
Part Number Data = 12345678
[)>RS06GSY0000000000000XGSP12345678
Group separator = GS
[)>RS06GSY0000000000000XGSP12345678GS
DUNS DI =12V
[)> S06GSY0000000000000XGSP12345678GS12V
R
DUNS Data =987654321

[)>RS06GSY0000000000000XGSP12345678GS12V987654321
G
Group separator = S
R G
[)> S06 SY0000000000000XGSP12345678GS12V987654321GS
GM Trace Code DI = T
[)>RS06GSY0000000000000XGSP12345678GS12V987654321GST
GM Trace Data = LSYYDDDA2B4C6000
[)> S06GSY0000000000000XGSP12345678GS12V987654321GSTLSYYDDDTRACEDATA
R
Record Separator = RS
[)> S06GSY0000000000000XGSP12345678GS12V987654321GSTLSYYDDDTRACEDATARS
R
End of Transmission = EOT

[)>RS06GSY0000000000000XGSP12345678GS12V987654321GSTLSYYDDDTRACEDATARSEOT

GM DEFINED TRACE STRUCTURE: The Compressed VPPS including the location code, the GM assigned
eight character part number, the manufacturer/assembler site specific DUNS ID, and the GMW15862 defined
trace structure constitutes the complete traceability record. Figure E1 shows the traceability label content and
encodation. Figure E2 shows a sample traceability label with data. Figure E3 details the bar code encodation
for the label sample shown in Figure E1. Figure E3 shows a sample label for batch or lot traceability
requirements.
Figure E1: GMW15862 Traceability Label/DPM Content and Encodation
Figure E2: GMW15862 Serial Number Traceability Sample with Bar Code Encodation
Figure E3: GMW15862 Lot/Batch Traceability Sample with Bar Code Encodation

E2 GMW15862 Error Proofing Structure

Figure E4 shows a sample label of the Error-Proofing structure.
Figure E4: GMW15862 Error Proofing/Part Verification Label/DPM Content and Encodation
Figure E5: GMW15862 Error-Proofing Label with Julian Year and Date Shown
Figure E6: GMW15862 Error-Proofing Label without Optional Julian Year and Date
Note: When the optional Julian Date and Year is not used, the Data Identifier 4D with placeholder values
YYDDD must be included in the bar code encodation as shown in the example in Figure E6.

Appendix F
F1 Appending/Adding Additional Data to the 2D Bar Code

The following procedures (Examples 1 and 2) shall be followed to append data to the 2D bar code. Examples
of types of additional data are product characteristics (voltage, current, pressure, flow rate, dimensional, etc.)
or supplier specific data (supplier part number, supplier internal traceability code, etc.). Encodation follows
ISO/IEC 15434 Syntax for High Capacity AIDC Media and ISO/IEC 15418 Information Technology – UCC/EAN
Application Identifiers and Fact Data Identifiers and Maintenance. The product characteristic field shall be
added after the GM-required data fields (T or 4D) but before the Record Separator (RS).
Example 1: Appending Supplier Data to a GM-Required Bar Code

Scenario: Various supplier data has been approved to be added to the GM-required bar code.
Data Identifiers selected: S, 14Z, 16Z, 17Z, 18Z, 2D, and 1P (see Table A1 in Appendix A for additional data
identifiers or visit ANSI MH10.8.2 website for available Data Identifiers)
The 2D bar code has the following data encodation before any additional data is added.
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006RSEOT
Step 1. Insert group separator GS after the traceability data field (remove RSEOT )
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GS
Step 2. Insert Data Identifier S
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GSS
Step 3. Insert supplier data 207KSVZ400143
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GSS207KSVZ400143
Step 4. Insert group separator GS
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GSS207KSVZ400143GS
Step 5: Insert Data Identifier for next piece of supplier information 14Z
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GSS207KSVZ400143GS14Z
Step 6. Insert supplier data 097601807
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GSS207KSVZ400143GS14Z097601807
Step 7. Repeat steps 4-6 to append additional data with the appropriate data identifiers to the bar code encodation
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GSS207KSVZ400143GS14Z097601807GS
16Z352076050005226GS17Z8934072379000135759FGS18Z214074200356367GS2D062012GS1PTG97AAJUED
R E
Step 8 Reinsert the record separator and end of transmission ( S OT )
[)>RS06GSY7520400000000XGSP22947632GS12V544948685GST1112172000000006GSS207KSVZ400143GS14Z097601807GS
16Z352076050005226GS17Z8934072379000135759FGS18Z214074200356367GS2D062012GS1PTG97AAJUEDRSEOT
The bar code label/DPM for the above appended data can be shown in multiple formats. Figure F1 shows a
label with bar code encodation as indicated above. The label to the left shows minimal human-readable
information. The label to the right shows the same bar code encodation but with more HRI approved as a
deviation or exception request. Adding additional human-readable information not only increases the size of
the label, but it may also result in a smaller bar code which can lead to bar code quality/scanning issues.
Figure F1: Sample Labels with Appended Supplier Data in the 2D Bar Code

Example 2: Appending Supplier Data – Supplier Part Number and Serial Number
Scenario: To help support their process, the supplier has requested to add their part number and serial
number to the error-proofing label. Since the GM policy is not to include supplier data on the label, it is
permissible to put the data in the 2D bar code.
Additional Data – Supplier Part Number: 1A2B3C4D5E6F7G8H9

Additional Data – Serial Number: A2B4C000E0
Data Identifiers selected: 1P and S (see Table A1 in Appendix A for additional data identifiers)
[)>RS06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDRSEOT
Step 1. Insert group separator GS after the traceability data field (remove RSEOT )
[)>RS 06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDGS
Step 2. Insert Data Identifier for supplier part number 1P
[)>RS 06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDGS1P
Step 3. Insert supplier part number 1A2B3C4D5E6F7G8H9
[)>RS 06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDGS1P1A2B3C4D5E6F7G8H9
Step 4. Insert group separator GS
[)>RS 06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDGS1P1A2B3C4D5E6F7G8H9GS
Step 5: Insert Data Identifier for supplier serial number S
[)>RS 06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDGS1P1A2B3C4D5E6F7G8H9GSS
Step 6. Insert supplier serial number A2B4C000E0
[)>RS 06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDGS1P1A2B3C4D5E6F7G8H9GSSA2B4C000E0
Step 7. Since this is the last data field it is closed by the Format Trailer
[)>RS 06GSY0000000000000XGSP12345678GS12V987654321GS4DYYDDDGS1P1A2B3C4D5E6F7G8H9GSSA2B4C000E0RSEOT
Figure F2: Sample with Product Characteristic Data Embedded in 2D Bar Code
Note: Supplier data is not printed in the Human Readable Information but encoded in the 2D bar code only.
Appending Information with Data Identifier 7Q:
Data Identifier 7Q shall be used with the appropriate appended unit of measure qualifier ANSI X12.3 Data
Element Number 355 Unit of Measure. An excerpt of the ANSI X12.3 table is posted to the AIAG web site at
the following url: http://www.autoid.org/ANSI_MH10/ansi_mh10sc8_wg2.htm. The data may contain a decimal
point for the required precision.
For DI 7Q, the last two characters of the data field shall be the ANSI X12.3 Data Element Number 355 Unit of
Measure (qualifier). See Table 15 for examples. The data elements between the DI 7Q and the two character
qualifier constitutes the value.
To add a voltage measurement of 14.7 V Direct Current, the encodation would look like this:
[)> S06GSY0000000000000XGSP12345678GS12V987654321GSTLSYYDDDA2B4C000EGS7Q14.72HRSEOT.
R
where 7Q14.72H which translates to 14.7 V DC.

Table F1: Examples of ANSI X12.3 355 Data Element Number 355 Unit of Measure (Qualifier)
Qualifier Definition Qualifier Definition
2G Volts (AC) (V AC) 68 Ampere (A)
2H Volts (DC) (V DC) CE Centigrade (°C)
2N Decibels (dB) Deci Newton-Meter
DN
(dNm)
2P Kilobyte FA Fahrenheit (F)
2Z Millivolts (mV) G9 Gigabyte
4K Milliamperes (mA) HJ Horsepower (hp)
4L Megabytes HP Millimeter (mm) H20
4S Pascal (Pa) HZ Hertz (Hz)
70 Volt (V) NU Newton-Meter (Nm)
Example 3: Appending Product Characteristic - Pressure Final Test Results

Scenario: The supplier and the GM release engineer agreed that having the final test stand pressure would
support product matching for the application and enhance warranty issues.
Additional Data: 14.7 Pascal.
Data Identifier selected: 7Q (see Table A1 in Appendix A for additional data identifiers)
Qualifier from Table: 4S
[)>RS06GSY0000000000000XGSP12345678GS12V987654321GSTLSYYDDDTRACEDATARSEOT
Step 1. Insert group separator GS after the traceability data field (remove RSEOT)
G
[)>RS06GSY0000000000000X SP12345678GS12V987654321GSTLSYYDDDTRACEDATAGS.
Step 2. Insert Data Identifier 7Q.
G
[)>RS06GSY0000000000000X SP12345678GS12V987654321GSTLSYYDDDTRACEDATAGS7Q.
Step 3. Insert data value including decimal 14.7.
G
[)>RS06GSY0000000000000X SP12345678GS12V987654321GSTLSYYDDDTRACEDATAGS7Q14.7.
Step 4. Insert qualifier from ANSI X12.3 4S.
G
[)>RS06GSY0000000000000X SP12345678GS12V987654321GSTLSYYDDDTRACEDATAGS7Q14.74S.
Step 5. Since this is the last data field, it is closed by the Format Trailer.
G
[)>RS06GSY0000000000000X SP12345678GS12V987654321GSTLSYYDDDTRACEDATAGS7Q14.74SRSEOT.
Figure F3: Sample with Product Characteristic Data Embedded in 2D Bar Code
Note: Supplier data is not printed in the Human Readable Information but encoded in the 2D bar code only.

Appendix G
G1 “As-Built” Label/DPM
The "As-Built" label/DPM provides a means of capturing the trace data as part of an external assembly
process such as a Value Added Assembler (VAA). The 2D bar code is structured to have an individual trace
record for each component that requires traceability. A fuel tank assembly, which consists of five (5) traceable
components (Figure G1), will be used as an example of how to create an "As-Built" 2D label/DPM with Human
Readable Information.
Figure G1: Illustration of a Fuel Tank Assembly Consisting of Five Traceable Components
The fuel tank is the primary link that the remaining four components will be associated with. The data collection
system captures each component with its bar code encodation as it is assembled to the tank (Table G1).
Table G1: Captured Data from Each of the Components with the Fuel Tank as the Primary Link

Using the captured data, the data is encoded into a single 2D symbol following the ISO/IEC 15434 Data
Syntax standard with the Record Separator character RS (ASCII ISO/IEC 646 Character decimal 30, 1Eh)
between the captured bar code encodations from each component (Figure G2).
Figure G2: Data Encodation for the 2D Symbol following ISO/IEC 15434 Data Syntax Standard
Note: The ASCII non-printable character (RS; 30 decimal, 1E hex) is used to separate each record.
The “As-Built” label/DPM shall contain the component information from all trace parts which make up the “as-
built” part. The "As Built" label/DPM shall be attached to the fuel tank. The plant system will scan the 2D bar
code and the data will be sent as a complete traceability record for each of the components that were
assembled to the fuel tank. The net effect is it appears as though the tank was assembled at the scan station
(Figure G3).
Figure G3: Completed "As-Built" Label/DPM Affixed to the Fuel Tank

Appendix H
GM1737 Defined Traceability and Error Proofing Code Structures
H1 GM1737 Traceability Structure (Phasing Out - See Traceability NOA 196B)

The following traceability structure, formerly defined in GM1737, is only to be used for existing electronic
modules or powertrain parts until end of their lifecycle. See NOA 196B for complete details.
Figure H1: GM1737 Traceability Structure to be Phased Out per Traceability NOA
Figure H2: GM1737 20T Traceability Label/DPM Examples (Encoded Data 20TCI5678VA2B4C6D8E)
H2 GM1737 Enhanced Traceability Structure (Phasing Out - See Traceability NOA

196B)
The following enhanced traceability structure, formerly defined in GM1737, is only to be used for existing
electronic modules or powertrain parts until end of their lifecycle. See NOA 196B for complete details.
Figure H3: Enhanced GM1737 Defined Traceability Structure to be Phased Out per Traceability NOA

Figure H4: GM1737 21T Traceability Label/DPM Examples (Encoded Data 21TCI5678VLS7282A2B)
H3 Linear 1D Bar Codes.

Note: GM is phasing out Linear 1D bar codes and phasing in to 2D symbologies with new part releases. This
information is for reference of carryover parts only.
H3.1 Code 128 and Code 39. For linear (1D) Symbologies, ISO/IEC 15417 Bar Code Symbology Specification
- Code 128 or ISO/IEC 16388 Bar Code Symbology Specification - Code 39 shall be used. Reference AIAG B4
for additional linear 1D bar code details. UCC/EAN Code 128 Symbology shall NOT be used. Code 128 is
preferred over Code 39 principally because of space efficiency and built-in check digit. See Figure H5 for bar
code samples.
Figure H5: Codes 128 and 39
Note 1: Code 128 and Code 39 shall NOT be used for Direct Part Marking.
Note 2: Code 128 is typically 25% shorter than Code 39 given the same data and X-Dimension.
H3.2 Characteristics of Code 128. Bar height for both symbologies can be varied to suit the particular
application requirements. The minimum bar height shall be 6.4 mm (0.25 in) or 15 % of the bar code length
whichever is greater, including quiet zone, and should not exceed 13 mm (0.5 in).
Code 128 is a Four Ratio Bar Code which is automatically determined via the Symbology Standard. Each
Code 128 data character consists of 1X, 2X, 3X, and 4X elements in width (bars and spaces). For each Code
128 symbol, the average width of the 1X narrow element SHOULD be within the range of (0.191 to 0.382) mm
((0.0075 to 0.0150) in). Code 128 has three modes- the labeling software or the printer shall determine which
mode to use and when to switch modes.
Historically, manual intervention results in Code 128 space efficiency being sub-optimized. Base specification
for Code 128:
X-dimension (narrow bar)
Height of symbol
H3.3 Characteristics of Code 39. Code 39 is a Two Ratio Bar Code and the Ratio shall be specified. The
significant parameters of Code 39 symbol are the average width of the narrow elements (bars and spaces) and
the average ratio of wide elements to narrow elements. For each Code 39 symbol, the average width of the
narrow elements shall be within the range of (0.191 to 0.382) mm ((0.0075 to 0.0150) in). The ratio of the wide
elements to the narrow elements should be 3:1. The measured ratio shall be between 2.8:1 and 3:1.
Note: Ratio has been the most common specification error. If the ratio falls below 2.8:1, the scanner may
incorrectly decode the data resulting in character substitution errors.
Base specification for Code 39:

X-dimension (narrow bar)

Ratio shall be in the range of 2.8:1 to 3:1
Height of symbol
H3.4 Code 128 and Code 39 Quiet Zones. Each of the leading and trailing quiet zones for a Code 128 and
Code 39 symbol should be 6.4 mm (0.25 in) and shall be a minimum of ten (10) times the width of the narrow
element (Figure H6).
Figure H6: 1D Quiet Zone and Height Requirement
H3.5 Check Digits. Code 128 includes a Built-in Check Digit, per the Symbology Standard, as the last
character before the stop character. The check digit shall NOT be shown in the HRI and it generally is not
transmitted by the decoder/reader. Check digits shall NOT be used in Code 39 Symbols.
H3.6 Code 128 and Code 39 Print Quality. The ISO/IEC 15416 Bar Code Print Quality Test Specification for
Linear Symbols shall be used to determine Code 128 and Code 39 symbol print quality. The minimum symbol
grade shall be 2.0/05/660 at GM point of scan where:
Minimum print quality grade = 2.0 (C).
Measurement aperture = 0.12 mm (0.005 in).
Inspection wavelength = (660 /+10) nm.
The above symbol quality and measurement parameters ensure scannability over a broad range of scanning
environments.
Note: Previous AIAG standards specified an inspection wavelength of 900 nm to accommodate existing
infrared scanners. In most cases, compliance at 900 nm is an indicator of compliance at 660 nm. When
discrepancies occur, measurements shall be made at 660 nm.
H3.7 Code 128 and Code 39 Data Format and Data Length. Data in a compliant symbol SHOULD consist of
the appropriate ANSI MH10.8.2 Data Identifier followed by user data.
H3.8 Data Capacity. A Code 128 or a Code 39 symbol should not exceed 20 characters including the data
identifier. However, available marking space may limit the possible data length to fewer data characters.
H3.9 Human Readable Information for Code 128 and Code 39. The HRI in a Code 128 or Code 39 symbol
should be printed. When printed, the HRI:
shall represent all of the encoded information
should be consistently placed directly above or below the Code 128 or Code 39 symbol
should display the Data Identifier in parentheses ( ) when the DI is part of the HRI
shall not display the start or stop characters or check digit
shall be upper case alpha and/or numeric Arial Narrow Bold, Helvetica Condensed or equivalent
The parentheses used in the HRI to separate the data identifier from the user information shall not be encoded
in the symbol.

Appendix J
Powertrain Traceability Format

Powertrain released components that are scanned at the vehicle manufacturing plant or value added assembly
(VAA) shall use the format shown in Figure J1. Powertrain released components that are scanned in the
Powertrain manufacturing location may use the format shown in Figure J8, space permitting. The format
shown in Figure J9 shall be used as an alternative if the Figure J8 format does not fit on the component.
Appendix J1 format labels shall go through the CG2503 process. Appendix J2 format labels shall be validated
through the Powertrain MRE for that component.
J1 Traceability Format for Powertrain Released Components Scanned at the Vehicle

Manufacturing Plant or VAA
The Powertrain trace code definition and RPO are different from the standard GM Traceability content.
Table J1: Encodation Definition for Powertrain Released Components Scanned by the Vehicle
Data
Data Definition Characteristics DI Encodation (with DI)
GM assigned VPPS Compressed Code 14 alphanumeric Y Y0000000000000X
GM Part Number 8 Numeric P P12345678
Manufacturing or Assembly Site DUNS 9 Numeric 12V 12V987654321
Trace Code (for Powertrain released components scanned at the manufacturing
16 alphanumeric T TLSYYDDD9AAKX1234
plant or VAA)
RPO (for engines only) 3 alphanumeric C CRPO
Figure J1: Encodation Layout Showing Control Character and DI Placement for Powertrain Released
Components Scanned at the Vehicle Manufacturing Plant or VAA
Figure J2: GM Defined Trace Code for Powertrain Released Components Scanned by the Vehicle
Note: If used for a part that does not track model year (for example, manual transmissions), an ‘X’ shall be
used in position 9.
th
For engines, position 13 in the Trace String is reserved for the 4 digit of a potential 4-character Broadcast
Code (BCC). In all other cases, an ‘X’ shall be used. For transmissions, position 13 is reserved for the Site ID,
to maintain trace code uniqueness for Transmission Programs.

Figure J3: Label Layout for Transmission Released Components Scanned by the Vehicle
Manufacturing Plant or VAA (ATK95040)
Figure J4: Example of a Compliant Transmission Label
Figure J5: Label Layout for Engine Released Components

Scanned by the Vehicle Manufacturing Plant or VAA
Area 3 is the 2D bar code matrix. The information embedded in 2D bar code shall comply with format shown in
Figure J1.

Figure J6: Label Layout for Engine Released Components

Scanned by the Vehicle Manufacturing Plant or VAA

J2 Traceability Format for Powertrain Released Components Scanned in the

Powertrain Manufacturing Facility
Table J2: Encodation Definition for Powertrain Released Components Scanned at the Powertrain Plant
Data Data
Definition Characteristics DI Encodation
GM Defined Trace Code (for Powertrain released
16 alphanumeric T PCLL936512340000
components scanned at Powertrain plant
Figure J7: Encodation Layout Showing the DI Placement and Data for
Powertrain Released Components Scanned at the Powertrain Plant
Figure J8: GM Defined Trace Code for Powertrain Released Components

Scanned at the Powertrain Plant – Base Pun
Figure J9: GM Defined Trace Code for Powertrain Released Components

Scanned at the Powertrain Plant – Alternate Pun
J2.1 Trace Data Fields. The seven data fields in the Powertrain trace code are identified as follows:
Base PUN shall be the starting format. The alternate to be used if there are additional things that need to
be in positions 13 through 16 rather than the last four digits of part number.
Program ID, Component Type and Site ID shall be supplied by the Powertrain Release Engineer.
Powertrain engineers can reference Quality Requirement 22.00.00 for the standard ID lists.
Build Year is the last digit of the calendar year
Julian Day per Appendix B
Sequence Number is four digits and left padded with zeros. The sequence starts with zero (0) at the
beginning of each day.
The optional characters in alternate PUN shall be the same format for all sites within a program. If optional
characters are not used, then place zeros in fields 13 through 16.
J2.2 Human Readable Content. For format J2, the layout of the human readable content is flexible provided
the human readable characters are legible.

Appendix K
K1 Tire Labeling
K1.1 Long Range Scanning. Data Matrix and QR Codes are scalable. By increasing cell/element size and
using the appropriate imager configuration, distances of 3 m can be obtained. A Data Matrix symbol using
3 mm (0.120 in.) element/cell measuring 70.3 mm x 70.3 mm can be scanned at 1.4 m (4.5 ft.) using the
current Global Manufacturing and Quality (GM&Q) standard handheld imager.
Figure K1: Scaling Cell Size (3 mm)
Note: This Data Matrix Symbol Scanned at 1.4 m using GM Standard Hand Held Imager.
K1.2 Tire Labeling Requirements. AIAG B-11 standard provides the guideline for the printing and placement
of tire and wheel identification bar code labels and read/write Radio Frequency Identification (RFID) Tags. This
standard is designed to help automate the collection of tire and wheel information and the mounting and
assembly process of tires and wheels with vehicles in the GM environment. The standard provides information
about the manufacturer, tire and wheel size, type, and additional optional information as outlined in this
standard and as agreed to by the supplier and GM. This tire and wheel application standard is based on the
AIAG B-4 Parts Identification and Tracking Standard, with additional information specific to the printing,
programming, and placement of tire and wheel identification bar code labels and RFID Tags.
K1.3 Tire Lot Traceability Identification. When identifying tires, the data field shall consist of the Data
Identifier "21S" followed by the full Department of Transportation (DOT) code (Federal Motor Vehicle Safety
Regulation (FMVSR) 49 CFR § 574.5), which is a 12-character coding structure defined by DOT as follows
(Figure K2):
The first two characters define the manufacturer by plant.
Characters 3 and 4 identify the tire size. Characters 3 and 4 may also be defined by the tire manufacturer.
Characters 5, 6, 7, and 8 are optional for the tire manufacturer. If the tire manufacturer uses a 3-digit option
code, then this shall be padded with a leading "underscore" character (5F HEX or 95 DEC). Definition of the
option code is left up to the tire Original Equipment Manufacturer (OEM) and GM.
Characters 9, 10, 11, and 12 are date of manufacture (2-digit week/2-digit year).

Figure K2: DOT Tire Lot Traceability Data Structure
K1.4 Tire Conicity. GM Tire Engineering group may sort tires based on an engineering value termed "conicity"
(Table K1). The DI assigned to conicity and selected by tire engineering is 5N01. The "5Nxx" set of DIs are
assigned to AIAG and are managed and published at http://www.aiag.org.
Table K1: Trailing Conicity Values To Be Used With DI 5N01

Qualifier Definition
A No split
B +
C -
D Low +
E Hi +
F Low -
G Hi -
H Not available
K1.5 Data Syntax Requirement. Data encoded in the 2D bar code for tires shall BE as shown in Table K2
with the final bar code encodation appearing as follows:
[)>RS06GSY2310100000000NGSP12345678GS12V987654321GS21SW2CU_XLT2508GS5N01BRSEOT
Table K2: Data Syntax Bar Code Encodation
Header DI Information Content Data Field Trailer

Separator
GM Defined VPPS
[)> S06GS
R G
Y S
23101000000000N
G
P GM defined part number 12345678 S
Manufacturing or assembly site DUNs G

12V S
number 987654321
DOT Defined Trace Code Example G
21S S
W2CU_XLT2508
G R E
5N01 Conicity Value Example B S S OT
K1.6 Label Layout. Tire labels shall conform to print quality and font rules detailed in paragraph 3.6. Bar code
cell/element shall be 0.51 mm minimum (0.02 in minimum). Label layout should conform to Figure K3.

Figure K3: Tire Label Layout (Label Size Approximately 27.9 x 27.9 mm (1.1 x 1.1 in)

Appendix L
L1 Direct Part Marking (DPM)

This portion of the standard describes general guidelines for Direct Part Marking (DPM), factors to consider,
and how to select the most appropriate DPM technique for a given application. Symbologies for DPM shall BE
Data Matrix or QR Code. Reference AIAG B-17 for more details and NASA-STD-6002C - Applying Data Matrix
Identification Symbols on Aerospace Parts.
L1.1 Considerations. The following are typical criteria for using DPM.
The part is too small to be labeled with traditional bar code labels.
The part is subjected to environmental conditions that preclude the use of labels.
DPM may be more cost efficient than individual item labels.
Identification is required for the life cycle of the part and labels are not acceptable for the reasons stated
above.
DPM is integrated as part of the manufacturing process rather than a secondary or manual process.
L1.2 Direct Mark and Human Readable Information. Bar Code content or direct marks on parts shall follow
the coding scheme of Section 3. Available area for marking and/or process cycle time may eliminate or reduce
the amount of human readable information required. Mutual agreement between Supplier and GM shall be
required.
L1.3 Direct Part Marking Methods. The guideline in Table L1 identifies suggested marking methods for
different materials.
Table L1: Guideline for Material Marking Process
Material Metallic Non-Metallic
FIBERGLASS
MAGNESIUM
ALUMINUM
CERAMICS
PLASTICS
FERROUS
TITANIUM
RUBBER
GLASS
Direct Part
Marking Process
Scribing X X X X X X X X X
Dot-Peen X X X X
Laser X X X X X X X X X
Inkjet X X X X X X X X X
L1.3.1 Scribing. Scribe DPM technology provides the ability to scribe or draw an image on a part’s surface by
displacing the material. DPM of Data Matrix symbols can be scribed using the three allowed methods in
ISO/IEC 16022 which are square, circular, or octagonal. Generally, a square symbol is preferred when scribing
because they are easier to decode/read. The symbol’s appearance is affected by the marking force and
material hardness. Ambient noise is typically reduced compared to dot-peen method. Marking noise is
dependent on part geometry and fixture tooling. This process uses a pneumatically or electromechanically
driven stylus. The pointed stylus strikes the surface at a beginning point on the square, and then continues to
make four connected straight lines outlining a square element/cell. The element/cell size can be adjusted. The
typical fill rate is 80 %.

L1.3.2 Dot-Peen. Dot-peen marking is faster than scribe marking, but it has density limitations. Dot-peen
marking technology typically produces round indentations on a part’s surface with a pneumatically or
electromechanically driven stylus, otherwise known as a pin. Critical to the readability of dot-peen, marked
symbols are the indented dot’s shape, size, and spacing. The dot size and appearance are determined mostly
by the stylus cone angle, marking force, and material hardness. The indented dot created SHOULD be suitable
to trap or reflect light and be large enough to be distinguishable from the part’s surface roughness. It SHOULD
also have spacing wide enough to accommodate varying module sizes, placement, and illumination.
The issues involved in DPM and reading dot-peen-marked symbols on metals are different than symbols
printed on paper. The first fundamental difference is that the contrast between dark and light fields is created
by artificial illumination of the symbol (see Figure L1). Consequently, the module’s shape, size, spacing, and
part surface finish can all affect symbol readability.
Figure L1: Dot-peen Illustrating Importance of Lighting
The key to a successful dot-peen marking and reading project is to tightly control the variables affecting the
consistency of the process. Symbol reading verification systems can provide feedback of the process
parameters to some extent. Marking system operating and maintenance procedures and schedules shall be
established and followed to help ensure consistent symbol quality.
L1.3.3 Laser. Laser marking is faster than dot-peen marking and does not have the same density limitations
as dot-peen marking. Lasers can be used to create a mark on some materials (see Figure L2). This is done by
directing a beam of coherent, collimated, focused light energy onto an item’s surface. In general, when a
laser’s beam comes into contact with an item, its light energy is converted into heat energy, which creates a
DPM either by melting, ablation, carbon migration, or chemical reaction. Various materials may react differently
to each type of laser and/or laser marking technique. All lasers will not create readable marks on all substrates.
When considering a laser marking system, the following factors SHOULD be taken into consideration:
Type of material to be marked
Laser type and marking process type
Laser power
Cycle time
Information (volume of data) to be marked
Laser safety
Figure L2: Laser Etch on Plastic

Different materials absorb or reflect specific laser wavelengths at different rates. The amount of absorption is
directly proportional to the laser’s ability to heat the material and cause a change in its appearance. The type
of lasing medium will determine a laser’s light wavelength. Laser marking generally produces the fastest
marking cycle.
L1.3.4 Inkjet. Inkjet technology, a non-intrusive DPM technology, sprays precisely controlled drops of ink
through the air in a pattern capable of creating a symbol. These drops are made of pigment suspended in fluid
that evaporates, leaving the colored dye on the surface of the item.
There are two primary methods for generating these drops: Drop-on-Demand and Continuous. The Drop-on-
Demand method uses valves or Piezo-electric technology to force ink through an orifice. This method has
significant printing resolution advantages over the Continuous method. The distance the ink can be "shot" is
usually limited to 3.1 mm ( 1/8 in). This limits the use of Drop-on-Demand in industrial DPM applications
(Figure L4).
Figure L4: Inkjet Example Speaker with Rectangular Data Matrix on Metal
The issues involved in marking and reading inkjet symbols placed directly on parts are somewhat different
from those of symbols printed on paper. Particular attention must be paid to the condition of the substrate on
which the ink is to be deposited. Cleaning the part surfaces prior to marking with an abrasive pad to remove
coatings, rust, and discoloration, or using an air knife to blow away excess machining fluids, debris, or oil can
improve mark and adhesion reliability.
Inkjet marking SHOULD not be considered a permanent marking method and is typically limited to parts that
will not be exposed to harsh manufacturing conditions. In particular, it SHOULD not be used on Electric
Discharge Machining (EDM), grit-blasted, machined, and shot-peened surfaces. Many of these conditions
change surface properties and/or color and may make it necessary to reapply the mark. In addition, care must
be exercised to ensure that the part will not go through any paint-dissolving fluid.
Another limitation to inkjet marking is that typically a part must be moving at a consistent speed in one direction
past the marking head during the marking process. Systems where the marking head moves and the part
being marked remains stationary are available.
Inkjet marking is suitable for applications requiring security by using Ultraviolet (UV) inks requiring special
lighting to read.
L1.4 Direct Part Mark Verification. A DPM verifier is a system consisting of lighting, optics, camera (imager)
verification software, and calibration references. The resolution of the verification system SHOULD be at least
twice that of the imager (reader). This may be accomplished with either higher magnification optics or an
imaging device with twice the resolution of the reader. AIAG B-17 shall be referenced as the process guideline
for direct marking using laser, peening, or ink jet. Direct part marking shall be mutually agreed to by GM and
supplier. Imaging (scanning) requirements for direct mark may require special lighting and specialized imagers.
Note: DPM systems shall require verification immediately following the creation of the mark to maintain quality
and downstream scannability.

GMW15 862

Uploaded by

Copyright:

Available Formats

GMW15 862

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GMW15 862

Uploaded by

Copyright:

Available Formats

WORLDWIDE

ENGINEERING General Specification GMW15862

Bar Code Content, Format, and Label Requirements for

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Originating Department: GME Specification Center Page 1 of 52

3.4.2.3 Error Correction Levels 11

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 2 of 52

D1.1 Anatomy of a Data Matrix 27

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 3 of 52

K1.6 Label Layout 48

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 4 of 52

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 5 of 52

3 Parts, Components, Assemblies or Modules Requiring Bar Codes

KCDS Code Driver

Product Engineering DFMEA,

Product Engineering; Only applicable when ME

ME, PFMEA; only applicable when ME approves

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 6 of 52

DFMEA: Design Failure Mode Effects Analysis

Figure 2: Illustration of a Lot/Batch Traceability Label/DPM

Figure 3: Anatomy of a Label/DPM with a Symbol

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 7 of 52

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 8 of 52

Table 2: Data Syntax Structure

4D Julian Date of Manufacture or 4DYYDDD

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 9 of 52

Lot/Batch Trace [)>RS06GSY9320000000000XGSP22798287GS12V813026986GST3212212@00000009RSEOT

Error-Proofing [)>RS 06GSY7329800000000JGSP22801229GS12V825134604GS4D12258RSEOT

GM1737 Trace 20TAS5309E050000001

Powertrain [)>RS 06GSY1210000000000XGSP24257888GS12V138440180GST11120934ACOX0043 RSEOT

Figure 6: Examples of Label Formats and Bar Code Encodations

3.4 Data Matrix and QR Code Physical Requirements.

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 10 of 52

Figure 7: Quiet Zone Requirement for Data Matrix

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 11 of 52

Figure 10: Example of Rectangular Data Matrix

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 12 of 52

12 point / 18 point 12345678

14 point / 24 point 1234 5678

4 Single Data Field Encodation

© Copyright 2013 General Motors Company All Rights Reserved

June 2013 Page 13 of 52

Figure 13: Single Data Element Encoded for 17 Character VIN

5 Linear 1D Bar Codes

6 Direct Part Marking (DPM)

7 Symbol (Bar Code) Quality Verification

8 Additional Product Characteristics

© Copyright 2013 General Motors Company All Rights Reserved