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
| Property | SVT Actual | SVT Target |
|---|---|---|
| Source | Read from the vehicle | Calculated by the tool |
| Meaning | Current detected state | Planned desired state |
| Typical inputs | Vehicle connection | FA, I-Step selections, software data |
| Typical use | Diagnosis, documentation, coding input | TAL calculation and programming |
| Main risk | Stale or incomplete read | Wrong project, I-Step or software dataset |
Which SVT to use for NCD 2.0
For the standard BMW Online Tool NCD 2.0 workflow, use an SVT Actual read from the same vehicle as the FA. The purpose is to match the current ECU/CAFD structure, not to predict a future programming state.
If a specialist workflow explicitly asks for SVT Target, keep the associated FA, integration levels and TAL together. Do not interchange target files between vehicles, even when they share a model series.
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.
ONLINETOOL SERVICES
Use the related online service
Compare BMW SVT Actual and SVT Target, understand when each file is created, and choose the correct SVT for coding, NCD and programming workflows.
Frequently asked questions
Is SVT Target newer than SVT Actual?
Not necessarily. Target means calculated, not automatically newer. Its content depends on the selected integration level and software data.
Can SVT Target be used for normal coding?
Some engineering workflows use target data, but a current-state NCD request normally needs SVT Actual unless specified otherwise.
Does SVT Actual contain the FA?
No. They are separate data structures and should be saved as separate files.
Can I rename SVT_IST.xml?
Renaming normally does not change the XML, but keep a clear name so the file cannot be confused with SVT Target.