GenericBanner2

ACES® and PIES™ - Manufacturer/Equipment Model Applications Only

ACPN Content Excellence Award

About the Award

This *NEW* award category is intended to recognize excellent source data and is separate from the “Receiver’s Choice Award.” Each submission will be one ACES® xml file (and its matching PIESTM xml file). The ACES® xml file must ONLY contain Manufacturer/Equipment Model (EquipmentBaseID) applications. This award judges ACES® and PIESTM files on a variety of areas that ACPN deems as essential when creating best in class ACES® and PIESTM data. Please see the judging guidelines for this award for more details.

Eligibility 

Submissions must meet these requirements 100% to be considered for judging:

  • Company Type: Manufacturer/Remanufacturer
  • Company Membership: Auto Care Association member in good standing
  • Subscription Status: Must have active VCdb and PAdb subscriptions.
  • Each submission will be one ACES® XML file (and its matching PIESTM XML file)
  • Both ACES® and PIESTMXML files must be a file produced for a trading partner
  • Both ACES® and PIESTM XML files must pass XSD validations
  • The ACES® XML file must be version 4.2
  • The ACES® XML file must ONLY contain Manufacturer/Equipment Model (EquipmentBaseID) applications
  • The PIESTM XML file must be versions 7.1 or 7.2
  • Both ACES® and PIESTM XML files must utilize September 2023 or newer published database versions (VCdb, Qdb, PCdb, PAdb)
  • The ACES® XML file must use Qdb qualifiers partially or fully. (If the ACES® file does not use Qdb and does not Fitment Notes for any application, the file passes)
  • The PIESTM XML file must use PAdb attributes partially or fully
  • The ACES® XML file must use valid Part Terminology / Position combinations according to the PCdb.
  • The PIESTM XML file must use valid PartTerminologyID / PAID combinations according to the PAdb.

Award Format

Gold

(Over 500 Applications)

Judging

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 PIESTM XML files. The ACPN Leadership Council then takes the raw scoring information provided 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 version of ACES® and PIESTM, and effective use of the PAdb.)

 

Submission Requirements

  1. Each parent company may submit one entry per ACES® application-count bracket.
  2. At least one representative from the submitting company must be present during the ACPN conference program at the Auto Care Connect Conference to accept the award in the event that the company is selected as an award recipient. If there is no representative present, the company will be restricted from submitting for any awards the following year.
  3. Entries must be received in full by the deadline (Entry Form, Participant Release Form, ACES® and PIESTM Files)

 

 
For questions about this specific award, please contact ACPN Leadership Council Member:
Courtney Pedler

 

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 PIESTM XML Files. If the submission does not meet the eligibility requirements 100%, the submission will be disqualified.

The ACES® and PIESTM XML files are judged on multiple general areas listed below with weighted percentages.

 

10% - ACES® -  Applications are invalid VCdb coded configurations free

Scoring Note

Based on percentage of application records with invalid coded configurations. Over 5% will get a score of "0".

 

Additional Notes

  • 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 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 the Vehicle Configuration database (VCdb).
25% - ACES® -  Applications are overlap/duplicate free
Scoring Note
Based on percentage of application records that are overlaps. Over 5% will get a score of "0".

Additional Notes
The MFR Label is considered in differentiating applications.
15% - ACES® - Qdb Level of Usage

Scoring Note

Based on the percentage use of QualifierID instances versus the sum of QualifierID instances and fitment note instances.

10% - ACES® and PIESTM - All part numbers in the ACES® file are present in the PIESTM file

Scoring Note

Based on percentage of part numbers found in the ACES® file that are also found in the PIESTM file.

15% - PIESTM - All part numbers have an Asset Type of (P04) Photo - Primary provided in the Digital Asset Segment (ASST) of PIESTM

Scoring Note

Based on percentage of part numbers in the PIESTM file that have an Asset Type of (P04).

10% - PIESTM - All part numbers have both Marketing Descriptions and Features and Benefits

Scoring Note

Based on percentage of part numbers in the PIESTM file that have BOTH FAB and MKT/GCC.

Additional Notes
  • Marketing Descriptions can be sent in two places in PIESTM.
    • Market Copy Segment (MKTC) - using Market Copy Codes (BRD), Market Copy Sub-Codes (PTI), and Market Copy Type (GCC).
    • Description Segment (DESC) - using the Description Code (MKT)
  • Features and Benefits can be sent in two places in PIESTM.
    • Market Copy Segment (MKTC) - using Market Copy Codes (BRD), Market Copy Sub-Codes (PTI), and Market Copy Type (FAB).
    • Description Segment (DESC) - using the Description Code (FAB)
10% - PIESTM - PAdb Level of Usage

Scoring Note

Based on the percentage use of PAID instances versus the sum of PAID instances and user defined attribute instances.

Additional Notes

  • Prop 65 Statements will NOT count towards this criteria point, as it is best practice to place these statements in the Attribute Segment of PIESTM per Auto Care best practices.
5% - PIESTM - All part numbers have Package Segment content

Scoring Note

Based on percentage of part numbers with package segment content.

highlights from previous award ceremonies

you could be next!

past winners

Each award-winning company is eligible to use the ACPN Content Excellence logo on company literature, mobile apps and websites. Contact ACPN@autocare.org for image files.

2023 Winner
  • Gold - Old World Industries