AAIA ACES Data Standard -- Fit Happens

6,088
-1

Published on

This seminar will help anyone who depends on electronic catalogs to match parts to specific vehicles or engines to understand how to use industry application standards to provide their customers with more accurate application data.

This seminar will also help explain the differences between AAIA Legacy and ACES data standards.

Published in: Automotive, Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
6,088
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
95
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • PIES for trading and orderingACES for fitment and lookup
  • PIES for trading and orderingACES for fitment and lookup
  • AAIA ACES Data Standard -- Fit Happens

    1. 1. AAIAACES Data Standard…Fit Happens<br />Gigi Ho<br />Founder & Data Goddess<br />Digital Performance Inc.<br />gigiho@digitalperformance.com<br />
    2. 2. Seminar Overview<br />This seminar will help anyone who depends on electronic catalogs to match parts to specific vehicles or engines to understand how to use industry application standards and provide their customers with more accurate application data.<br />This seminarwill also help explain the differences between AAIA Legacy and ACES data standards.<br />
    3. 3. Seminar Overview<br />What is AAIA?<br />Why do we need Data Standards?<br />Where does PIES Standard fit in?<br />What are a few industry and data terms?<br />What is Legacy?<br />What is the ACES Data Standard?<br />History<br />VCdb<br />PCdb<br />Qdb<br />
    4. 4. What is AAIA?<br />Automotive Aftermarket Industry Association<br />23,000 members and affiliates<br />Parts Manufacturers<br />Equipment Manufacturers<br />Retailers and Distributors<br />
    5. 5. Why should you care?<br />
    6. 6. Why do we need standards?<br />Vehicle Applications<br />2010 Chevy Camaro<br />New Camaro<br />‘10 Camero<br />2010 Chevrolet Camaro<br />
    7. 7. Why do we need standards?<br />Part Applications<br />02 Sensor<br />Lambda Sensor<br />Oxygen Sensor<br />
    8. 8. Why do we need standards?<br />Invalid Applications = Lost Sale$<br />
    9. 9. AAIA Legacy: original AAIA electronic catalog standard for vehicle year, make, model, and engine in a flat file format.<br />ACES (AAIA Catalog Enhanced Standard): current electronic cataloging standard comprised of vehicle year, make, model, engine and additional vehicle attributes in a relational database in an XML format.<br />PIES (Product Information Exchange Standards): standardized fields of product information, like part number, descriptions, price, dimensions, etc., in an XML format.<br />Delimited Text File: an array of data separated by any character; most common delimiters are tabs, commas, and vertical bars (aka, “pipe”). This is a flat file format.<br />XML (Extensible Mark-up Language): tags that define and validate data and facilitate transmission and interpretation of data between organizations.<br />Let’s get the terms down<br />
    10. 10. Enter the Data…standards<br />
    11. 11. Product data standard is used for trading between you and your business partners.<br />
    12. 12. Brand Identification<br />Part Number<br />Part Type<br />Part Description<br />Pricing<br />Universal Product Code (UPC)<br />Dimensions and Weight<br />Images<br />Sample PIES Product Fields<br />
    13. 13. Part Numbers<br />No special characters (*, /, $, ”, etc.)<br />Descriptions<br />Make them descriptive of the part and not just what vehicle it fits.<br />UPC/GTIN<br />Without this, your products can sit up to 72 hours before going to the shelf<br />Images<br />Minimum 400x400 pixels at 72dpi -- find out your customers’ needs<br />White background<br />Leave between 5-15 pixels around border<br />Keep shadows to a minimum<br />Pricing<br />Make sure your pricing is current<br />Key product fields<br />
    14. 14. Application (aka, vehicle fitment) data is used to determine what your part is and which vehicle or vehicles your parts fit.<br />
    15. 15. What is Legacy?<br />The original Vehicle Application Standard<br />Introduced in 1997<br />14 data fields covering vehicle and engine information<br />Tied to a 7-digit ID number – “Legacy ID”<br />
    16. 16. What is Legacy?<br />Part Type Table<br />List of parts compiled by the aftermarket community<br />Undisciplined<br />Vague<br />Switch<br />Sensor<br />
    17. 17. What is Legacy?<br />Legacy is…an old or outdated computer hardware, software or data that, while still functional, does not work well with up-to-date systems.<br /><ul><li>Legacy’s sunset date is December 2012.</li></li></ul><li>What is the ACES Data Standard?<br />
    18. 18. ACES Data Standard<br />ACES is the current Vehicle Application Standard<br />Introduced in 2003<br />Published monthly<br />Comprised of 3 databases<br />VCdb – Vehicle Configuration database<br />PCdb – Parts Categorization database<br />Qdb – Qualifier database<br />
    19. 19. ACES Data Standard<br />VCdb – Vehicle Configuration database<br />Published monthly<br />49 data fields covering:<br />Vehicle<br />Engine<br />Bed Length & Bed Style<br />Body Style & Body Code<br />Brake<br />Drive Type<br />Steering<br />Suspension<br />Transmission<br />Wheelbase<br />
    20. 20. ACES Data Standard<br />VCdb also classifies vehicle types:<br />Car, Truck & Van (USA, Canada & Mexico)<br />Medium Duty<br />Agricultural Equipment<br />Class 8 Trucks<br />Powersports<br />Lawn & Garden<br />more to come…<br />
    21. 21. ACES Data Standard<br />Vehicle<br />Year, Make and Model<br />Base Vehicle is the minimum level of detail required to deliver an ACES application<br />
    22. 22. ACES Data Standard<br />Engine<br />22 data fields making up an Engine Configuration<br />Tied to Vehicle<br />Linked to the Legacy Table<br />
    23. 23. ACES Data Standard<br />Transmission<br />6 data fields making up a Transmission Configuration<br />Tied to Vehicle<br />
    24. 24. ACES Data Standard<br />Brake<br />5 data fields making up a Brake Configuration<br />Tied to Vehicle<br />
    25. 25. ACES Data Standard<br />Steering<br />2 data fields making up a Steering Configuration<br />Tied to Vehicle<br />
    26. 26. ACES Data Standard<br />Suspension<br />2 data fields making up a Spring Configuration<br />Tied to Vehicle<br />
    27. 27. ACES Data Standard<br />Body Style<br />2 data fields making up a Body Style Configuration<br />Tied to Vehicle<br />
    28. 28. ACES Data Standard<br />Manufacturer Body Code<br />1 data field<br />Tied to Vehicle<br />
    29. 29. ACES Data Standard<br />Bed Length & Bed Style<br />2 data fields making up a Bed Configuration<br />Tied to Vehicle<br />For pickup trucks only<br />
    30. 30. ACES Data Standard<br />Drive Type<br />1 data field<br />Tied to Vehicle<br />
    31. 31. ACES Data Standard<br />Wheelbase<br />1 data field<br />Tied to Vehicle<br />For trucks and vans only<br />
    32. 32. ACES Data Standard<br />Vehicle Configuration<br />Ties all the VCdb components together<br />USA vehicles only<br />
    33. 33. ACES Data Standard<br />Details of coverage for vehicle data fields<br />1985 – Current model year<br />All VCdb attributes including Vehicle Configuration<br />1975 – 1984<br />All VCdb attributes except for Vehicle Configuration<br />1950 – 1974<br />Vehicle and Engine only<br />1896 – 1949<br />Vehicle only<br />
    34. 34. ACES Data Standard<br />Other Motive<br />Vehicle and Engine only<br />USA vehicles only<br />
    35. 35. ACES Data Standard<br />New vehicle data research sources<br />Vehicle manufacturer media sites<br />OEM service information<br />OEM parts information<br />Consumer sites (e.g., AutoTrader, Edmunds, etc.)<br />New vehicles within 30 days of sale<br />
    36. 36. ACES Data Standard<br />PCdb – Parts Categorization database<br />Published 2 time each month<br />Comprised of 5 tables<br />Category<br />Sub-category<br />Part Terminology<br />Position<br />CodeMaster ties it all together<br />
    37. 37. ACES Data Standard<br />Qdb – Qualifier database<br />Published as needed<br />Comprised of 2 tables<br />Qualifier<br />Qualifier Type<br />
    38. 38. What do standardized data exports look like?<br />
    39. 39. AAIA Legacy Sample (pipe delimited)<br />AAIA_BrandID|Product_Number|Description|AAIA_Legacy_ID|AAIA_PartTerminology|Attributes_Notes<br />BXYZ|ABC1001|Shock Absorber Jeep CJ Front|1180853|Shock Absorber|2 Door Sport Utility; 4WD; Front<br />BXYZ|ABC1002|Shock Absorber Jeep CJ Front|1180842|Shock Absorber|2 Door Sport Utility; 4WD; Front<br />BXYZ|ABC1003|Shock Absorber Jeep CJ Front|1181270|Shock Absorber|2 Door Sport Utility; 4WD; Front<br />BXYZ|DEF1001|Shock Absorber Jaguar XJ12 Front|1177848|Shock Absorber|4 Door Sedan; RWD; Front<br />BXYZ|DEF1002|Shock Absorber Jaguar XJ12 Front|1177860|Shock Absorber|4 Door Sedan; RWD; Front<br />BXYZ|DEF1003|Shock Absorber Jaguar XJ12 Front|1177871|Shock Absorber|4 Door Sedan; RWD; Front<br />BXYZ|GHI1001|Strut Porsche 911 Front|1351617|Suspension Strut Assembly|Front; 65-9/68<br />BXYZ|GHI1001|Strut Porsche 911 Front|1351628|Suspension Strut Assembly|Front; 65-9/68<br />BXYZ|GHI1001|Strut Porsche 911 Front|1351594|Suspension Strut Assembly|Front; 65-9/68<br />
    40. 40. <Item MaintenanceType="A”><br /> <HazardousMaterialCode>N</HazardousMaterialCode><br /> <PartNumber>ABC123</PartNumber><br /> <BrandAAIAID>BXYZ</BrandAAIAID><br /> <BrandLabel>Flowmaster</BrandLabel><br /> <PartTerminologyID>10727</PartTerminologyID><br /> <Descriptions><br /> <Description LanguageCode="EN" MaintenanceType="A" DescriptionCode="MKT">The marketing description is often the feature points of the product or part.</Description><br /></Descriptions><br /><Packages><br /> <Package MaintenanceType="A”><br /> <PackageLevelGTIN>700042055555</PackageLevelGTIN><br /> <Dimensions UOM="IN”><br /> <Height>12</Height><br /> <Width>17</Width><br /> <Length>66</Length><br /> </Dimensions><br /> <Weights UOM="PG”><br /> <Weight>49.4</Weight><br /> </Weights><br /> </Package><br /></Packages><br />. . .<br />PIES XML Sample<br />
    41. 41. <App id=“1” action=“A”><br /> <BaseVehicle id=“3109” /><br /> <SubModelID id=“450” /><br /> <EngineBase id=“417” /><br /> <Position id=“12” /><br /> <Transmission id=“1197” /><br /> <Note>65-9/68</Note><br /> <Qty>1</Qty><br /> <PartType id=“10727” /><br /> <Part>GHI1001</Part><br /></App><br /><App id=“2” action="A”><br /> <BaseVehicle id="3464” /><br /> <Position id=“12” /><br /> <BedType id=”5” /><br /> <Note>65-9/68</Note><br /> <Qty>1</Qty><br /> <PartType id="2864"/><br /> <Part>GHI1002</Part><br /></App><br />ACES XML Sample<br />
    42. 42. …but beautiful to the computer systems that process them.<br />They’re ugly to our eyes…<br />
    43. 43. …when someone is asking for your “electronic data”<br />What NOT to send…<br />
    44. 44. Excel spreadsheets made for human eyes<br />Why not this? – This *looks* great, but is completely unreadable by a computer, and therefore, will not be loaded into your customer’s inventory system for a looooong time...if ever.<br />
    45. 45. Fields of mixed product information<br />Why not this? -- Sub-model, year range, and fitment notes are all crammed into one cell! Again, completely unreadable by a computer.<br />
    46. 46. PDF Pages, Catalogs, Guides…PDFs.<br />
    47. 47. Questions?<br />
    48. 48. AAIA Technology Standards & Solutions Committee<br />Scott Luckett, VP and Committee Liaison<br />scott.luckett@aftermarket.org<br />SEMA Business Technology Committee<br />Staci Bostock, BTC Staff Liaison<br />stacib@sema.org<br />Websites and Bookmark Tool<br />AAIA - www.aftermarket.org/Technology.aspx<br />ACES – www.enhancedstandard.com<br />SEMA - www.sema.org/btc<br />NAFTA - http://bit.ly/wfuwU<br />Resources for Data Standards<br />
    49. 49. ACES Data Standard…Fit Happens<br />Gigi Ho<br />Founder & Data Goddess<br />Digital Performance Inc.<br />gigiho@digitalperformance.com<br />CATALOGING SOFTWARE<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×