ACES® and PIES™ - Manufacturer/Equipment Model Applications Only
About the Award
This award category is intended to recognize excellent source data and proper use of the ACES® and PIESTM data standards. This award 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.
- To check your subscription status, please contact membership@autocare.org. To purchase a subscription, please visit our subscriptions page.
- Each submission will be one ACES® XML file that must ONLY contain Manufacturer/Equipment Model (EquipmentBaseID) applications 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 PIESTM XML file must be versions 7.1 or 7.2
- Both ACES® and PIESTM XML files must utilize October 2024 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
- No Labels for reference database ID's present in ACES® and/or PIES™ XML
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. 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. All PIES files will be validated against the live Autocarevip.com database. 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 PIESTM, effective use of the PAdb, and more)
Submission Requirements
- Each parent company may submit one entry per ACES® application-count bracket.
- 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.
- Entries must be received in full by the deadline (Entry Form, Participant Release Form, ACES® and PIESTM Files)
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.
Scoring Note
Based on if Company, Sender Name, Sender Phone are all populated or not.
Scoring Note
Based on percentage of application records with invalid coded configurations. Over 1% will get a score of "0".
Based on percentage of application records that are overlaps/duplicates. Over 1% will get a score of "0".
Additional Notes
The MFR Label is considered in differentiating applications.
Scoring Note
Based on the percentage use of unique QualifierID 's versus the sum of unique QualifierIDs and unique fitment notes.
Scoring Note
Based on the percentage of part numbers that use valid PartTerminologyID's and PositionID combinations.
Scoring Note
Based on percentage of part numbers found in the ACES® file that are also found in the PIESTM file.
- Header is populated with Technical Contact and Contact Email.
Scoring Note
Based on if Technical Contact and Contact Email are all populated or not.
- All part numbers use valid PartTerminologyID's
- All ACES® part numbers are flagged as "Y" in PIES Element "ACESApplication"
- All part numbers have unique GTINs
Scoring Note
All criteria for this segment are based on a percentage of the segments whole.
- All part numbers have EXPI Code "CTO"
- All part numbers have EXPI Code "LIF"
- All part numbers have EXPI Code "NPC"
- All part numbers have EXPI Code "PRC"
- All EXPICodes used are valid
- All EXPI records that use PIES™ Coded Values (List of values) are valid.
Scoring Note
All criteria for this segment are based on a percentage of the segments whole.
- All part numbers have attributes (Prop65 Statements are not counted against due to Auto Care best practices)
- PAdb Level of Usage (Prop 65 Statements are not counted against due to Auto Care best practices)
- All part numbers that use PAdb Attributes use valid PartTerminology/PAID/ ValidValueID/UOMCode combinations
- All part numbers that have records with the element "PAdbAttribute" flagged "Y" have PAID's populated in the element "AttributeID"
- All records are sequenced
Scoring Note
All criteria for this segment are based on a percentage of the segments whole.
- All part numbers have Both Marketing Descriptions and Features and Benefits.
- Marketing Descriptions can be sent in two places in PIESTM.
- Market Copy Segment (MKTC) - using Market Copy Code/Sub-Code (PTI), and Market Copy Type (GCC).
- Description Segment (DESC) - using the DescriptionCode (MKT)
- Features and Benefits can be sent in two places in PIESTM.
- Market Copy Segment (MKTC) - using Market Copy Code/Sub-Codes (PTI), and Market Copy Type (FAB).
- Description Segment (DESC) - using the DescriptionCode (FAB)
- Marketing Descriptions can be sent in two places in PIESTM.
- All DescriptionCodes used are valid
- All records are sequenced
Scoring Note
All criteria for this segment are based on a percentage of the segments whole.
- All part numbers have a single primary product image (AssetTypeCode "P04")
- All part number 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)
- All AssetTypeCodes used are valid
Scoring Note
All criteria for this segment are based on a percentage of the segments whole.
- All part numbers have at least one package level communicated
- All PackageUOMCodes used are valid
Scoring Note
All criteria for this segment are based on a percentage of the segments whole.
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.
- Gold - Old World Industries
- Gold - Old World Industries