Technical Service Bulletin
00 Software Version Management (SVM), operating instructions
00 14 65 2011732/10 July 15, 2014. Supersedes Technical Service Bulletin Group 00 number 12-32 dated
February 7, 2012 for reasons listed below.
Model(s)

Year

VIN Range

Vehicle-Specific Equipment

All

2002 - 2016

All

Not Applicable

Condition
REVISION HISTORY
Revision

Date

Purpose

10

-

Revised entire bulletin to include ODIS information

9

2/7/2012

Revised header data (Added model years)
Revised Technical Background
Revised Service (Added image)

8

3/24/2010

Revised Technical Background
Revised Service (Added Response Codes section)

7

5/13/2009

Revised Service (Step 6)

6

12/15/2008

Revised Service (Step 3 – added information concerning use of wireless VAS
5054A transmitter head)

5

11/17/2008

Revised Title to include Repair Group

4

10/21/2008

Revised Service (Step 3 – added information concerning Windows power savings
settings)

This Technical Service Bulletin (TSB) details the general process for carrying out a Software Version Management
(SVM) software update for any TSB or Update.
Troubleshooting information is included in the Additional Information section.

© 2014 Audi of America, Inc.

Page 1 of 13

All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of
Audi of America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior
expressed written permission of the publisher.

Technical Service Bulletin
Technical Background
Glossary of Terms & Acronyms used in this service bulletin
SVM:

Software Version Management

ODIS:

Offboard Diagnostic Information System

ECU:

Electronic Control Unit (i.e. ECM, TCM,
BCM, gateway, cluster, etc.)

ECM:

Engine Control Module

TCM:

Transmission Control Module

CARPORT:

The database that stores the last known
good configuration for each VIN.

XCHG: Abbreviation for “exchange” or
replacement (i.e. SVM Code
XCHG15A005)

ASAM-MCD: ASAM - Measurement, Calibration, and
Diagnostics

ETKA: ET = Ersatzteil (Spare Parts) & KA =
Katalog (Catalog)

MMI:

Multi-Media Interface

ASAM: Association for Standardization of
Automation and Measuring Systems

MIB:

Modular Infotainment System (ENG)

MOST: Media-Oriented System Transport

Service42:

Server hosting the SVM application

VAS:

Volkswagen Automotive Service
Equipment

Version42:

Engineering database hosting the ECU data
and configuration files

ZUG:

Refers to the software package, or train,
of an ECU. “Zug” is a German word for
train.

© 2014 Audi of America, Inc.

Modularer Infotainment Baukasten (GER)

Page 2 of 13

All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of
Audi of America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior
expressed written permission of the publisher.

Technical Service Bulletin
SVM Basics
SVM was developed to ensure that the hardware and software of each ECU is correct before the vehicle leaves
the dealership repair facility.
A VAS 5051B, VAS 5052A, VAS 6150(A/B/C) or VAS 6160 diagnostic tool is required for reading the vehicle
control unit data and sending it to the SVM server (also called an “SVM communication”). The SVM
communication data flow is illustrated below (Figure 1).

Figure 1. SVM communication data flow.

© 2014 Audi of America, Inc.

Page 3 of 13

All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of
Audi of America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior
expressed written permission of the publisher.

Technical Service Bulletin
SVM Menu Options
There are five main menu options (Figure 2). The display
order may vary:
1. SVM - Activations
2. SVM - Code input
3. SVM - Direct input: SVM code for vehicle conversion
4. SVM - Specified/actual comparison or SVM - Check
vehicle configuration (This function is named differently
depending on the type of vehicle connected).
5. SVM - communication, checking
Figure 2. Five SVM main menu options
See the corresponding section below for an explanation of each menu option.

SVM - Activations
Purpose:

Used to recover existing activations or to activate new features/functions in an installed control
unit.
• When used to recover an existing activation, no activation code is required because the
license authorization is already on the server.
• When used to activate a new function/feature, a new activation code (and possibly a PIN or
customer code) may be required.

How it works:

Currently, SVM activation codes are only being used with navigation map data updates for
vehicles with MMI3G/3G+. Recovery activation is also used with MIB systems.
Instead of purchasing navigation map data, the customer must purchase an “activation packet”
to unlock the map update in the MMI system. The activation packet consists of an activation
code, activation number, and PIN. Once the activation packet information is used on a vehicle, it
is permanently connected to that vehicle in the SVM database and cannot be used on any other
vehicle.

SVM - Code input
Purpose:

Code input is used to update the software in the vehicle. It is used for any updates that cannot
be performed with SVM - Specified/actual comparison (or SVM - Check Vehicle Configuration,
depending on model).

How it works:

When an SVM code is entered, a “Quick Test” is automatically performed. This test immediately
verifies whether or not the SVM code is valid (before the update is attempted) by sending the
VIN and SVM code for rough verification before other information is read out of the car and sent
to SVM.
• If a hardware change is necessary, the software update will not be performed and a response
of “the SVM code is not valid for the vehicle” or “check hardware against ETKA” is provided.

© 2014 Audi of America, Inc.

Page 4 of 13

All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of
Audi of America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior
expressed written permission of the publisher.

Technical Service Bulletin
• If SVM determines that it will not be able to code and/or parameterize the control unit after the
update, it will indicate that the SVM code is valid for the vehicle, but the update cannot be
completed. (In such cases, contact TAC for assistance).
• If no issue is found, SVM will perform the update.
• After the update is complete, a specified/actual comparison is performed for the updated
1
diagnostic addresses in order to calculate the new coding and parameter data set for the
control unit, and to set a new reference in the CARPORT database.
Additional
Information:

• Before an SVM code input is attempted, it is important that the condition is correctly
diagnosed and that only a valid code from an applicable TSB is used. Incorrect SVM codes
can cause conflicts in the SVM database.
• SVM codes can be used to document manual software updates (which are performed with a
CD, DVD, or SD card), such as MMI software package (ZUG) updates. An SVM code for an
MMI update will document changes in the SVM database and provide coding and/or
parameterization suggestions, but it does not perform software updates.
SVM codes for MMI software package (ZUG) updates will only be successful if all control
units are already updated to the correct level (including those that were recently replaced).
• SVM exchange codes (XCHG) may be used to aid in the installation of new service parts
when a specified/actual comparison cannot code or parameterize the replacement control
unit (such as with all Audi airbag control units). XCHG codes can be found with the parts
bulletin listed in ETKA, or in an applicable TSB.
It is critical that the XCHG code is run immediately after a new control unit is installed in the
vehicle. If a specified/actual comparison is performed instead of the XCHG code, an invalid
vehicle reference can be created in the SVM database which can prevent the XCHG code
from functioning. (In such cases, contact TAC for assistance). Typically, GFF runs the XCHG
code in the control unit replacement routine automatically, or it will ask if an XCHG code was
provided.

SVM - Direct input: SVM code for vehicle conversion
Purpose:

Allows for a factory-approved retrofitting of additional control units by using a valid SVM code for
vehicle conversion. This option is only used when a new control unit is added to the vehicle. It is
not used for spare parts needed at repairs.

How it works:

• When a code for vehicle conversion is entered, SVM performs a check of all hardware. It is
important to note that ALL hardware is checked. This is to ensure there are no incorrect
ECU’s installed in the vehicle prior to the retrofit. An incorrect ECU in the vehicle can
potentially create unwanted functionality or behavior of the newly retrofitted ECU.
• The installation instructions for the new control unit contain information about the SVM code
for vehicle conversion. This code is typically documented in the last installation step.

Additional
Information:

SVM codes for conversion are typically named “050XXX”.

© 2014 Audi of America, Inc.

Page 5 of 13

All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of
Audi of America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior
expressed written permission of the publisher.

Technical Service Bulletin
SVM - Specified/actual comparison
Purpose:

(Note that this option is not available on model year 2015 and newer A3 vehicles -- see SVM Check vehicle configuration, below, for A3 information).
• By comparing the current vehicle data with the stored server data, a specified/actual
comparison ensures that all control units that are installed in the vehicle have the same part
numbers, software versions, coding, and parameter data that were last recorded. If any
discrepancies are found, SVM displays a notification.
• Specified/actual comparison does not suggest software updates; it only looks for the last
recorded hardware/software part numbers and last recorded software versions.

How it works:

• When a specified/actual comparison is performed, the actual part numbers and actual
software versions in the vehicle (the “actual” data) are sent to the servers. This “actual” data
is compared to the “specified” data stored for the vehicle in the CARPORT database.
• The specified/actual comparison will document any changes that have been made to a
control unit’s hardware part numbers and software versions, if they are valid supersessions. It
will also inform the user if the changes are accepted or rejected.
• When a new control unit is installed, the specified/actual comparison calculates the coding
and new parameter data set. If a “hardware change suggestion” is given, a conflict exists
within the vehicle reference for the control unit (SVM expects a different part number or
software version).

Additional
Information:

• SVM will not allow a new control unit to be installed if it has an older version of the software,
even if the control unit has the same hardware/software part numbers. In this case, SVM will
suggest a hardware change, and a CARPORT reference must be manually set by an Audi
Product Support Engineer but only if an SVM code for software update is available after the
reference is manually updated. (In such cases, contact TAC for assistance).
• If any hardware changes are suggested as a result of an SVM code being executed, a new
vehicle reference will not be set in the CARPORT database (in order to prevent any bad data
from being documented). As a result, repeat coding and/or parameterization suggestions may
be given with all subsequent SVM communications. It is recommended that all hardware
change suggestions be resolved before any SVM codes are entered. Once the hardware
change issue is resolved, the SVM code must be run again in order to set the reference. This
process is complete when a message appears explaining that no further actions are needed.

SVM - Check vehicle configuration
Purpose:

(Note that this option is only available on model year 2015 and newer A3 vehicles -- see SVM Specified/actual comparison, above, for other vehicles).
• This function ensures that all control units that are installed in the vehicle have the correct
part numbers, software versions, coding, parameter data, and adaptation values by
comparing the current vehicle data with the stored server data.
• Check vehicle configuration does not suggest software updates; it only looks for the last
recorded hardware/software part numbers, last recorded software versions, and performs all
necessary adaptations.

© 2014 Audi of America, Inc.

Page 6 of 13

All rights reserved. Information contained in this document is based on the latest information available at the time of printing and is subject to the copyright and other intellectual property rights of
Audi of America, Inc., its affiliated companies and its licensors. All rights are reserved to make changes at any time without notice. No part of this document may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites, without the prior
expressed written permission of the publisher.

Technical Service Bulletin
How it works:

The functionality is the same as that of a specified/actual comparison (see above), but there are
separate communications from each control module, rather than one communication from the
entire vehicle.

Additional