Winsby Group LLC Corporate Logo

Usage Instructions

  1. Open ACES xml file to Optimize

  2. Show Header to determine VCdb used to create the ACES file (View > Show Header)

  3. Open VCdb database that matches the Header. Note: Only ACES files created with VCdb 2018-09-28 or later (with EngineBlock table).

  4. Select desired Output ACES Version (3.2 or 4.0)

  5. If ACES 4.0, select the desired Engine Preference (EngineBase or EngineBlock)

  6. The “Exclude Region” check boxes allow region-specific “optimization” and export. If the primary file has Approved For “US;CA”, then Mexico is checked in the “Exclude Regions” (and disabled). You can check other regions to further exclude CA, for example. If the file does not have “Approved For”, you can check Mexico to exclude Mexico from the results. Note, that if you Exclude Mexico but also check Include Invalid, the Mexico applications will be included in the output but will not be compressed.

  7. Select desired Compression Grouping (PartType is normally appropriate). Only use MfrLabel if its used exclusively as a subset of the PartType.

  8. Invalid applications are usually saved in a separate file, but you can Include in results if you want to deliver them together (default is to exclude).

  9. The “Include Comments” check box will add xml comments for make, model, etc. (Note: this option is for internal use only. Releasing VCdb id “values” may break the terms of your Auto Care License).

  10. The Full Filename (appending _full) and Net Change Filename (appending _delta) are automatically filled in using the same location as the ACES file. You can override these defaults.

  11. Press the “Compress” button to begin the optimization.

Compression Results

One thing to note is that with Make/Model/Year range applications, the number of applications will likely increase with compression. That’s because sometime one year in a range compresses and other years do not. For example, if an application has a year range of 2003-2001 and 2002 compresses while 2001 and 2003 do not, one application becomes three.

”Ref” attribute

When a source application is changed (or consolidated), the source app ids are included in the “ref” attribute of the new application. If more than one id is included, this indicates a consolidation.

Revised: 2019-08-12