pcdb data rules
Category (CategoryID and CategoryName): PCdb Categories are a logical collection of related vehicle components that perform together as a system or a top-level classification of similar non-application products. For example, Cooling System or Tools and Equipment
Subcategory (SubCategoryID and SubCategoryName): PCdb Subcategories are vehicle assemblies or subsystems related to a high level Category, and intermediate classification of related non-application products. For example, Water Pump and related Components or Tire Service Tools. This allows the user to filter across categories.
Part Terminology (PartTerminologyID and PartTerminologyName): Part Terminology (formerly referred to as Part Type) defines the most granular product classification of vehicle parts and components as well s all other non-applications parts, supplies, accessories, components and consumables traded in the vehicle aftermarket industry. For example, Water Pump Pulley or Tire Valve Stem Replacement Tool
Position: The Position data element is only referenced in an ACES catalog application record. The field refers to the position of a part or component, from a forward-facing view, relative to others of the same part terminology on a vehicle. For example, Left Front for Brake Caliper or Inner for Wheel Bearing
Position N/A: The default Position value for all Part Terminologies is N/A (not applicable). This is the appropriate Position when: 1) there is only one instance of the part type in the application r 2) when multiples of the same part type are symmetrical and there is no need to differentiate the position of one from another of the same part type. It is possible for a Part Terminology to have one or more valid positions and for N/A to be valid; it depends on how the part is engineered to the vehicle.
Use: Use indicates if a Part Terminology is valid for an ACES application file (UseID 1) or for a PIES product information file (UseID 2).
PartsDescription: Allows the subscriber to submit a reason and or description when adding a new Part Terminology. This allows the reviewer more context and information regarding this part terminology request and is informational in nature. If the request is approved, the content in this table will not be edited or changed by the reviewer and will be published as submitted.
PartsRelationship: Defines a relationship between a Multi Purpose part terminology, utilized in a PIES file, to the related application specific part terminology, utilized in an ACES file.
PartsToAlias: Defines a relationship between a part terminology and its aliases used through the auto care industry.
PartsSupersession: Defines a relationship between a part terminology that is no longer in use and its replacement part terminology.
Data relationship rules
- Every part terminology record is associated with only one subcategory which is in turn associated with only one category. This does not limit users of the database in listing parts under multiple categories in their user interface. The standard does not impose limits on “presentation” of content – merely on the standardized classification of terminology.
- No part terminology shall be orphaned or left without a subcategory and category relationship
- No part terminology shall have more than one subcategory and category relationship
- Any part terminology may have one or more Positions associated with it, in addition to the N/A position
- It is acceptable for a PartTerminologyID to carry a UseID of both 1 and a 2 in the PartsToUse table. These cases represent part terminologies that are suitable for both ACES and PIES and therefore they will be allowed to carry both product attributes (PAdb) and positions.
- No PartTerminologyID shall exist without a Use relationship.
- Part terminologies used explicitly for PIES can only have a position of N/A associated with that part terminology.
- Independent Terminology: A part terminology record must be self-describing and not dependent on its relationship to a category or subcategory for context or uniqueness.
- Case: All entries in the PCdb are Title Case – with the first letter of each word capitalized
- Redundancy: The PCdb includes one unique part terminology record for each item in the database. The PCdb does not include brand-specific references or jargon. The PCdb includes the PartsToAlias table to record aliases or alternative terminology. As a reference coding table, the PCdb includes a single unique record of each part terminology – not an exhaustive list of alternative terminology
- Consistency: Terminology of similar part terminology should be classified consistently throughout the database. For example, all Brake Hardware part terminologies should be classified in the subcategory: Brake Hardware and category: Brake
- Abbreviations:Commonly used abbreviations are widely used in commerce and recognized in the auto care industry. Auto Care Association has a standardized and recognized list of acceptable abbreviations. These are the only abbreviations approved for use in the PCdb
- Acronyms: Acronyms are acceptable for use in the PCdb when they are: a) widely used and recognized by most in industry b) refer to the generic (not brand-specific) part terminology and c) are used consistently throughout the PCdb for the same part terminology. For example, EGR is approved for reference to Exhaust Gas Recirculation provided it is used consistently for EGR Valve, EGR Valve Gasket, EGR Valve Flange, etc.
- Multi Purpose Parts: A Multi Purpose part is a single physical item that is used in more than one way on one or more vehicles.
One use of the PCdb is to classify products in an ACES file (application catalog data). In this scenario, it is important to classify Multi Purpose parts exactly as they are used on a vehicle. The use of the part on the vehicle is how the search will be done. Therefore, the PCdb must include all of the uses of a part in all vehicle applications.
Example - A specific electrical Relay is used in more than one way across multiple vehicle applications. A valid ACES catalog record must refer to the Relay by the specific use of the product on the vehicle, e.g., Wiper Motor Relay, Horn Relay, Window Lift Relay. Therefore, the PCdb supports these specific terminologies for Multi Purpose parts. Terms that describe what the product does.
The PCdb is also used to classify product information exchanged by way of the PIES specification. In this scenario, it is appropriate to classify a Multi Purpose part with a more general term that describes what the product is, regardless of how it is used.
Example - In the example above the same Relay product performs multiple tasks on a vehicle. The attributes of the product do not change when it performs multiple functions. Therefore, the PCdb also includes a Multi Purpose part terminology that describes what the product is, irrespective of what the product does. In this example, the product is always a Relay.
PartstoUse table: The PartsToUse table indicates whether each Part Terminology is appropriate for an ACES application file, a PIES Product Information file or both. The PartToUse table joins PartTerminologyID’s with UseID's from the Use table in valid combinations.
Use ID 1 indicates the part terminology is appropriate for an ACES application file
Use ID 2 indicates the part terminology is appropriate for a PIES product information file
If the Use is unclear it will be coded for both ACES and PIES (Use ID 1 and Use ID 2)
- Position / Location: Reference to a position should only be part of the part terminology name when it is an integral component of the name and helps define an item that is found in only one location in all applications.
- Position Descriptions: Position descriptions are used to clarify the exact location of a particular part application when the same part terminology may be used more than once on a vehicle. Positions always refer to a forward-facing perspective. For example, it is helpful to indicate that Part#1 is the Left Front Disc Brake Caliper and Part#2 is the Right Front Disc Brake Caliper
The part terminology name should not include extended information that is conveyed in other elements of either ACES or PIES or the Product Attribute Database (PAdb). Examples of prohibited content include:
- OE Manufacturer references - A/C O-Ring Green - Ford FX15 Compressor Ports
- Brand references - Kicker Shock Bracket Kit - Rear – Rancho
- Product Attribute references - A/C Compressor & Component Kit - New
- Application Segment references - Intermediate Unit Bushing – Marine
- Position references - Headlight Bezel Set - Right Front
- Product Material references - A/Trans Kit, Sealing Ring (Teflon)
- Product Construction references - Oil Bath Seal - Scotseal - Front - L/D Truck
- Size references - Exhaust Pipe Extension 5'
- Color references – Mud Flap, Black
- No XML reserved characters
- No use of the word Style (reserved for PAdb use)
Questions? Please email firstname.lastname@example.org.