Phone: +1 (302) 907-9950 Email: [email protected]  Skype: anzaelllc


AAIA has developed an Aftermarket Catalog Exchange Standard for hassle free management and exchange of automobile attributes such as vehicle parts, makes, models and qualifier statement. Sometimes retailers need vehicle catalog for customers to ensure that they are getting quality auto parts. It increase sales and more trust in business.
Thus, suppliers use ACES application to manage and exchange of data with trading partners. Catalog data will be available in ACES XML format. Do you know or not but ACES xml format has its own benefits such as:

• It can be viewed online anytime without need of reloading the file again.
• XML format is readable by humans as well as machines.
• You can verify your catalog data before submitting to your trading partner.
• It can be converted into any flat file format.
• It helps to generate buyers guide report.
• You can cross check of report by your trading partner.
VCdb (Vehicle Configuration Database) and PCdb (Parts Configuration Database) can be accessible without having an account.

The Aftermarket Catalog Exchange Standard has been updated monthly with fresh information of automobile attributes in the aftermarket industry. Automotive Aftermarket Industry Association has launched latest version called ACES 3.1. It has been integrated with some advanced features in compare to the old version ACES 3.0. Let’s discuss what differentiates these two versions.

Difference between ACES 3.0 & ACES 3.1

ACES version 3.0 has been integrated with several updates in Vehicle Configuration Database (VCdb) and new data delivery specifications such as:

• Addition of othermotive’s eight segments in two different phases: Phase 1 launched in 2009 that includes Class 8 trucks, Powersports, Lawn & Garden and Farm & Agriculture Equipment. Phase 2 was launched in 2010 that include Construction equipment, Marine Engines, Material Handling and Stationary Equipment.
• Addition of Mexican light duty vehicles in 2009.
• Vehicle Type Group and Power Output have been introduced as new tables which include multiple vehicle types and values expressed in Horsepower and Kilowatts.
• Added supports for exchanging and managing application data for one brands in single file.
• Power Output and Vehicle Sub Type have been updated with XML delivery tags.

However, ACES 3.1 has been released with minor changes in compare to ACES 3.0.The latest version comes with little updates in ACES delivery specification document and removal of vehicle configuration table.

What’s New Inside ACES 3.1?

ACES 3.1 put more emphasis on consistency and grammatical punctuations in the ACES delivery specification document. VCDB Field Definition Document is another factor which has been victimized data type updates in the Engine Config Table and removal of Vehicle Config Table. To reflect the removal of vehicle config table, the VCDB ER Diagram also been updated.

Why ACES XML Validation is Require?

ACES Application contains huge data files of manufacturers and suppliers of aftermarket industry.Sometimes, it increases the chances of including wrong automotive attributes which results into the delivering wrong information to the trading partners. It can create distrust between suppliers and trading partners. To get rid of it, ACES XML validation is important.With XML format it is very easy to customize wrong information in compare to other data formats.

ACES XML validation thus helps you to keep updated and boost your business ROI (Return on Investment) as well.

Leave a Reply