OnlineTool BMW work needs information about the particular vehicle: its identification number, equipment, installed units and software versions. These data help prepare settings for the job.
VIN identifies the vehicle. FA describes its configuration. SVT describes the units and their software. This guide explains where the data come from and how to use them together when preparing NCD coding files.
What the VIN is for
VIN is the vehicle's 17-character identification number. It links information and received files to a particular car.
Check the complete VIN against the vehicle. If using a saved FA, check the VIN in that file. E-Sys displays it after FA is loaded.
VIN can be used to retrieve stored vehicle information. The Factory FA service provides the original FA only, without SVT. Preparing settings also requires suitable unit data, which must be obtained separately. FA and SVT describe these two parts of the job.
Understanding FA
FA describes the vehicle and its equipment configuration. It can be read from the vehicle or obtained from stored records. E-Sys saves FA as an XML file.
Check which configuration the file describes. Factory FA refers to the original configuration. Equipment fitted later may differ from it.
For example, if additional equipment has been installed, the description used to prepare settings must account for that work. Changing FA and writing the settings follow the relevant retrofit procedure.
Keep the original FA separate from the version prepared for changes. Note where each file came from and which job it is for. You can then distinguish the starting data from the data prepared for the work.
Understanding SVT
SVT describes electronic control units and their hardware and software components. E-Sys shows these data as a tree: expand a unit to see its entries.
There are two main labels:
- SVT Actual / Ist — the current unit and software state.
- SVT Target / Soll — the state intended by the selected procedure.
When working with installed units, use data that describe their state. A saved SVT may no longer be suitable after a unit replacement or software update. Check the data against the vehicle again.
A calculated SVT Target is used where the procedure needs to describe the future software configuration. When saving it, note which SVT you obtained so you can distinguish the current state from the calculated state later.
Why the source matters
Two files with the same VIN may describe the vehicle at different times. Its equipment, units or software may have changed.
| Data source | What it describes |
|---|---|
| Read from the vehicle | The state at the time of that read |
| Factory data | The original vehicle state |
| Latest known data in a source | The latest records available in that source |
| Calculated for a job | The state prepared for the selected procedure |
The latest known records may predate a repair. A source may still describe an old unit when its replacement is already installed.
The download date does not tell you the date of the vehicle state. A file downloaded today may contain factory data for a car built several years ago.
Keep a short note with the files: vehicle, source, read or retrieval date, and any changes made afterwards. For SVT, also record Actual or Target. This helps identify the data relevant to the job.
Choosing the right FA and SVT pair
When preparing NCD, the files have related roles. FA describes the configuration that needs settings. SVT describes the units and software involved.
For example, after a unit replacement, first check FA against the required configuration. Then obtain data for the installed unit and its software. An SVT saved before replacement may still describe the old unit.
The appropriate pair depends on the procedure. Factory FA may be suitable for work involving factory equipment, while a vehicle read describes the units actually installed. Both files must fit the job and the state of the units whose settings are being prepared.
A file name or the .xml extension cannot establish this. You need to know the source and view the data in the program.
Viewing saved files in E-Sys
In E-Sys 25.10.01, open saved FA in the FA/FP editor through File → Open. Its contents appear as a tree, and the program determines the vehicle profile. You can view the FA details and VIN here.
Load a saved SVT in the SVT Actual area of Coding. The unit tree appears after loading. Use SVT Target to view the calculated state.
This lets you inspect the files before using them. The introductory guide explains reading FA and SVT from a vehicle; this section concerns saved files.
Keep originals separately. If the job requires editing, use the appropriate editor and keep the prepared file with a note of the changes.
Example: preparing NCD files
The names FA.xml and SVT.xml below are examples. Keep the actual names of your files.
1. Prepare the input data
Save FA and SVT for the selected job. Note which configuration FA describes and which SVT is being used. Put both files in the job's input folder.
If units or software changed after the read, first check the vehicle data again for this operation. The preparation must use information about the units involved now.
2. Submit the appropriate pair for NCD preparation
Provide FA with the equipment configuration and SVT with the unit data. Check that both relate to the correct vehicle and job.
The service uses the pair to prepare the available signed NCD. The resulting files contain coding data for the corresponding units.
3. Keep the result with the input files
Create a separate folder for the received NCD, such as NCD_results. This preserves the link between the input pair and the prepared files. Keep the results of different jobs separately.
4. Check which units have data
Use the units and CAFD entries required in E-Sys as your reference. Suitable NCD must be available for those entries.
If two units need data but you receive data for only one, the set is incomplete for that job. One unit may have several files, so counting files alone is insufficient.
Preparation can produce a partial result. Resolve any missing data before applying coding to that unit. Check each file's purpose and suitability against the result description and the program's data.
Where file preparation ends
Keep the input FA/SVT and received NCD organised by job. Applying the data to the vehicle is a separate procedure.
The saved pair shows which records were used to prepare the result. The program report and vehicle checks show whether the actual work was completed.
Prepare NCD from FA and SVT
Provide a suitable FA/SVT pair. Compare the received NCD with the required CAFD entries. Applying it to the vehicle is a separate step.
Orders are handled through the Telegram bot. Open the bot from the service page, check the selected service and follow its input instructions. Keep the result for the original procedure.