What’s happening?

We are excited to confirm that the June release of AutovistaSPEC UK is now available for testing via our SFTP server. This release includes valuable enhancements designed to simplify your migration and align the UK dataset fully with the AutovistaSPEC standard, ahead of the official launch in October 2025.

Here’s what’s new:

Updated Handling of Metric and Imperial Power

The UK market traditionally uses imperial brake horsepower (bhp), unlike the metric units (kW or PS) used in other European markets.

To represent this distinction clearly:

• Imperial brake horsepower values have been moved from the field “TYPHP“, in the type.txt data table, to the new field “TIEBrakeHP” within the typeinformationextended.txt table.
• Metric power values remain in the “TYPHP” field within the type.txt content table, consistent with other markets.

Removal of Engine Power from Vehicle Names (Special Attention for Hybrids and EVs)

Historically, engine power values were included in vehicle names (fields “TYPName” and “TYPName2“) in the type.txt data table.

To align with AutovistaSPEC market-wide standard, engine power has now been removed from vehicle names. Power details are now exclusively contained in specific fields such as “TYPHP” or “TYPKW” held in the table type.txt.

For Hybrid and Electric Vehicles (EVs):

• Combined system performance or peak power values will appear in dedicated fields (“TIEHybridSystKW“, “TIEHybridSystHP“, “TIEEPeakPowerkW“, “TIEEPeakPowerHP“) within the new typeinformationextended.txt table.
• Please note, this specific information will start being populated from October 2025, coinciding with the official AutovistaSPEC launch.

Additionally, AutovistaSPEC will introduce a new table, electricengine.txt, capturing detailed information on electric motors, such as the number of engines and their individual power outputs. This data will also become available starting October 2025.

Model Year Information Now in modelyear.txt content table

Model year data has always been essential for UK vehicle identification and was traditionally included in the vehicle name (e.g., “330e xDrive Sport Aut. 2021.25MY“). To improve consistency and reduce NatCode duplication, model year details will now be stored in a dedicated table: modelyear.txt.

From a content perspective:

• Each NatCode (“MOYNatCode “) may be associated with one or more model years
• Each entry will include a corresponding validity date (“MOYNatCode “), enabling accurate identification.
• This structure will be introduced from October 2025, delivering greater efficiency across the dataset.

Going forward, please refer to modelyear.txt to determine the correct model year.

Important to note:

• For existing vehicles, model year text will remain in the vehicle name (“TYPName”) in type.txt.
• This new approach will apply only to new vehicles introduced from October 2025 onwards.
• Model year data will only be captured where it is explicitly provided in the OEMs’ official price lists.

Below is an example illustrating how the current model year methodology will evolve from October 2025:

Model Name 2 (“MODName2”) No Longer Used for Validity Dates

Previously, vehicle models included validity date information within the “MODName2” field in the model.txt table (e.g. “4 door Saloon Model 2021“).

Going forward, the “MODName2” field will no longer contain any information—neither the model description nor the date—and will be left empty. Instead, please refer to the “MODImpBegin” field, which indicates the model’s official import/sale start date.

Below is an example illustrating how this information should now be interpreted:

Please note that comprehensive details of these changes are documented within the SFTP documentation folder: “/autovistaspec_allcountries_documentation/United Kingdom – Core & Full”.

Ongoing Transition to September 2025

To support a seamless migration, AutovistaSPEC UK will continue to be updated at regular intervals until September 2025.

• Consistent Structure: While we continue refining and expanding the content, the structural format of AutovistaSPEC (e.g., tables and fields) remains unchanged.
• Daily Deliveries: AutovistaSPEC UK will continue to be delivered daily, with periodic updates introducing the latest enhancements.
• Advance Notifications: We will keep you informed of updates and new releases in advance through our regular communications.
  
  

Accessing the AutovistaSPEC Portal and SFTP

If you require access to AutovistaSPEC UK and have not yet received your credentials, please contact us at customer@autovistagroup.com.

Access Instructions:

AutovistaSPEC Portal

1. Use the Login button provided in the email from Autovista Data (noreply@glass.co.uk) to access the Autovista Portal:
   https://www.autovistaspec.autovistacloud.net/auth/login
2. Enter the credentials provided in the email.
3. Upon first login, update your temporary password to a permanent one.
   • Please note: The temporary password expires after 7 days.

Within the portal, you can view the data packages to which you are subscribed. Access to AutovistaSPEC is governed by Autovista’s standard license terms unless otherwise agreed in writing.

For further details, visit: https://glass.co.uk/terms-conditions.

AutovistaSPEC SFTP

To access your data packages (AutovistaSPEC UK Core or AutovistaSPEC UK Full):

• Use an SFTP client with your portal username and password to connect to:
  files.autovistaspec.autovistacloud.net
• Navigate to the appropriate folders, such as autovistaspec_uk_****, where you will find your subscribed packages and accompanying technical documentation.
  

Help & Support