BMW SVT Actual vs SVT Target: What Is the Difference?

What SVT means

SVT is the software variant table used in BMW engineering and service workflows to describe control units and their software elements. Depending on the task, the table can represent the vehicle as it is now or a state calculated for a planned programming operation.

The labels vary by tool and language. SVT Actual, SVT ist and actual vehicle SVT generally refer to the detected state. SVT Target or SVT soll refers to a calculated desired state.

SVT Actual

SVT Actual is obtained by reading the connected vehicle. It is evidence of the current ECU and software structure at the moment of the read. It can include bootloader, application software and coding application references reported for each ECU.

Use it when a workflow needs to know what is actually present: documenting the vehicle, preparing an NCD request from current data, diagnosing a missing CAFD, or comparing the vehicle with a target plan.

SVT Target

SVT Target is generated by a calculation. The calculation considers the vehicle order, selected chassis/project, shipment and target integration levels, and the software data available to the tool. It expresses what the software structure should become if the corresponding programming plan is carried out.

A target table is not proof that its software is already installed. It belongs with the TAL and programming context that created it.

Side-by-side comparison

Which SVT to use for NCD 2.0

For coding installed software, start with fresh SVT Actual and FA from the vehicle. An old SVT may describe different software after an ECU update.

SVT Target is relevant when the task explicitly uses a calculated future state. The FA, integration levels and programming plan must agree. Do not choose Target merely because it sounds newer.

How to identify a saved file

A filename such as SVT_IST... or SVT_ACTUAL... is a useful clue, while SVT_SOLL... or SVT_TARGET... usually indicates a target. The filename is not authoritative because users can rename it. Open the file only for inspection, not editing, and check its root structure and metadata if the source is uncertain.

Common mismatch scenarios

• FA from the current vehicle combined with a target SVT calculated for another integration level.
• SVT Actual saved before a control unit replacement and reused after the replacement.
• Target SVT created with software data that does not cover the vehicle platform.
• Two files with similar VIN7 endings but different full VINs.

The solution is usually to return to the vehicle, read a fresh FA and SVT Actual, and keep them as a pair.

Avoid mixing up Actual and Target

Identify the failing stage first: exporting input, placing the order or applying the response. Then use the relevant check below.

You only have a file named SVT.xml

Check how it was created: by reading the vehicle or calculating a target state. If its origin is unknown, do not identify its type from the filename.

Target was calculated, but programming has not been performed

This file describes a plan, not a confirmed installed state. Use a read SVT Actual for a standard current-state NCD request.

The file was saved before an ECU replacement

Compare it with a new vehicle read. The old file is useful history, but does not establish the structure after replacement.

What to include when asking for help

Record the service name, the failing stage, the complete error text, local tool version and request time. Keep the original input and returned result. Share vehicle files through the existing support channel, rather than publishing them in an open comment.