Judging of this award is done in-house by the Auto Care Association, utilizing the
AutoCareVIP.com catalog assessment tool to process the ACES and PIES XML files. All files will be assessed within a week of the submission. All ACES files will be validated against the most recent release of VCdb, Qdb and PCdb at the time of file submission. All PIES files will be validated against the live Autocarevip.com database at the time of file submission. The ACPN Leadership Council then takes the raw scoring information provided by the catalog assessment tool and applies weighted percentages to the general area scores to determine the winners of the award. The submission with the highest score is considered the winner. (
In the case of a tie, the contenders will be re-examined to arrive at a subjective assessment of appropriate levels of over-mapping, effective use of the Qdb, appropriate use of the Note and MfrLabel tags, use of most recent versions of ACES and PIES,
effective use of the PAdb, and more.)
Judging Guidelines
If the eligibility requirements listed above are met 100% for the award submission, the following judging guidelines are then utilized to judge the submission's ACES and PIES XML Files. If the submission does not meet the eligibility requirements 100%, the submission will be disqualified.
The ACES and PIES XML files are judged on multiple general areas listed below with weighted percentages.
45%
ACES
- 1%
Header and Footer
- Header and Footer Error Free
- Company, Sender Name, Sender Phone populated
App Segment
- 7%
Applications are VCdb Config Error Free
Make / Year-Range Applications - Applications that use Make / Year-Range combinations (using optional vehicle attributes such as Model, Engine or Transmission) will be split into individual applications, and will be validated and counted towards the score.
Validate "No" Applications - Applications that are flagged as Validate "No" will be automatically flagged as "Yes", and will be validated and counted towards the score. Although the standard allows for this, it is highly recommended that you request to have vehicles added to the Vehicle Configuration database (VCdb).
- 4%
Applications are VCdb Vehicle Attribute Error Free
- 2%
Applications are Base Vehicle Error Free
- 10%
Applications are Fitment Logic Error Free
The MFR Label is considered in differentiating applications.
- 5%
Applications are Part Terminology Error Free
- 5%
Applications are Qdb Qualifier Error Free
- 2%
Applications are Note Error Free
- 6%
Qdb Qualifier Utilization (Unique ID Count)
- 3%
All ACES Part Numbers found in PIES
55%
PIES
- 1%
Header and Trailer
- Header and Trailer Error Free
- Header populated with Company, Sender Name, Sender Phone
- 8%
Item
- Item Segment Error Free
- All part numbers have the field "ACESApplications" populated
- 8%
EXPI
- EXPI Segment Error Free
- All part numbers have the EXPI Codes CTO, LIF, NPC, PRC populated
- 12%
Product Attribute
- Product Attribute Segment Error Free
- All part numbers have product attributes
- PAdb Utilization
- All records are sequenced
- 10%
Marketing Copy and Description
- Marketing Copy Segment Error Free
- Description Segment Error Free
- All part numbers have both Marketing Descriptions and Features and Benefits.
- All records are sequenced
- 10%
Digital Assets
- Digital Asset Segment Error Free
- All part numbers have a single primary product image (AssetTypeCode "P04")
- All part numbers have at least one secondary product image (AssetTypeCodes P01, P02, P03, P05, P06, P07, 360)
- All part numbers have at least one non-product image digital asset (All AssetTypeCodes except P01, P02, P03, P04, P05, P06, P07, 360, and RGL)
- 6%
Package
- Package Segment Error Free
- All part numbers have at least one package level communicated
- All package records have BOTH weight and dimensions