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.

1. AAIAACES Data Standard…Fit Happens Gigi Ho Founder & Data Goddess Digital Performance Inc. gigiho@digitalperformance.com

2. Seminar Overview 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. This seminarwill also help explain the differences between AAIA Legacy and ACES data standards.

3. Seminar Overview What is AAIA? Why do we need Data Standards? Where does PIES Standard fit in? What are a few industry and data terms? What is Legacy? What is the ACES Data Standard? History VCdb PCdb Qdb

4. What is AAIA? Automotive Aftermarket Industry Association 23,000 members and affiliates Parts Manufacturers Equipment Manufacturers Retailers and Distributors

5. Why should you care?

6. Why do we need standards? Vehicle Applications 2010 Chevy Camaro New Camaro ‘10 Camero 2010 Chevrolet Camaro

7. Why do we need standards? Part Applications 02 Sensor Lambda Sensor Oxygen Sensor

8. Why do we need standards? Invalid Applications = Lost Sale$

9. AAIA Legacy: original AAIA electronic catalog standard for vehicle year, make, model, and engine in a flat file format. 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. PIES (Product Information Exchange Standards): standardized fields of product information, like part number, descriptions, price, dimensions, etc., in an XML format. 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. XML (Extensible Mark-up Language): tags that define and validate data and facilitate transmission and interpretation of data between organizations. Let’s get the terms down

10. Enter the Data…standards

11. Product data standard is used for trading between you and your business partners.

12. Brand Identification Part Number Part Type Part Description Pricing Universal Product Code (UPC) Dimensions and Weight Images Sample PIES Product Fields

13. Part Numbers No special characters (*, /, $, ”, etc.) Descriptions Make them descriptive of the part and not just what vehicle it fits. UPC/GTIN Without this, your products can sit up to 72 hours before going to the shelf Images Minimum 400x400 pixels at 72dpi -- find out your customers’ needs White background Leave between 5-15 pixels around border Keep shadows to a minimum Pricing Make sure your pricing is current Key product fields

14. Application (aka, vehicle fitment) data is used to determine what your part is and which vehicle or vehicles your parts fit.

15. What is Legacy? The original Vehicle Application Standard Introduced in 1997 14 data fields covering vehicle and engine information Tied to a 7-digit ID number – “Legacy ID”

16. What is Legacy? Part Type Table List of parts compiled by the aftermarket community Undisciplined Vague Switch Sensor

18. ACES Data Standard ACES is the current Vehicle Application Standard Introduced in 2003 Published monthly Comprised of 3 databases VCdb – Vehicle Configuration database PCdb – Parts Categorization database Qdb – Qualifier database

19. ACES Data Standard VCdb – Vehicle Configuration database Published monthly 49 data fields covering: Vehicle Engine Bed Length & Bed Style Body Style & Body Code Brake Drive Type Steering Suspension Transmission Wheelbase

20. ACES Data Standard VCdb also classifies vehicle types: Car, Truck & Van (USA, Canada & Mexico) Medium Duty Agricultural Equipment Class 8 Trucks Powersports Lawn & Garden more to come…

21. ACES Data Standard Vehicle Year, Make and Model Base Vehicle is the minimum level of detail required to deliver an ACES application

22. ACES Data Standard Engine 22 data fields making up an Engine Configuration Tied to Vehicle Linked to the Legacy Table

23. ACES Data Standard Transmission 6 data fields making up a Transmission Configuration Tied to Vehicle

24. ACES Data Standard Brake 5 data fields making up a Brake Configuration Tied to Vehicle

25. ACES Data Standard Steering 2 data fields making up a Steering Configuration Tied to Vehicle

26. ACES Data Standard Suspension 2 data fields making up a Spring Configuration Tied to Vehicle

27. ACES Data Standard Body Style 2 data fields making up a Body Style Configuration Tied to Vehicle

28. ACES Data Standard Manufacturer Body Code 1 data field Tied to Vehicle

29. ACES Data Standard Bed Length & Bed Style 2 data fields making up a Bed Configuration Tied to Vehicle For pickup trucks only

30. ACES Data Standard Drive Type 1 data field Tied to Vehicle

31. ACES Data Standard Wheelbase 1 data field Tied to Vehicle For trucks and vans only

32. ACES Data Standard Vehicle Configuration Ties all the VCdb components together USA vehicles only

33. ACES Data Standard Details of coverage for vehicle data fields 1985 – Current model year All VCdb attributes including Vehicle Configuration 1975 – 1984 All VCdb attributes except for Vehicle Configuration 1950 – 1974 Vehicle and Engine only 1896 – 1949 Vehicle only

34. ACES Data Standard Other Motive Vehicle and Engine only USA vehicles only

35. ACES Data Standard New vehicle data research sources Vehicle manufacturer media sites OEM service information OEM parts information Consumer sites (e.g., AutoTrader, Edmunds, etc.) New vehicles within 30 days of sale

36. ACES Data Standard PCdb – Parts Categorization database Published 2 time each month Comprised of 5 tables Category Sub-category Part Terminology Position CodeMaster ties it all together

37. ACES Data Standard Qdb – Qualifier database Published as needed Comprised of 2 tables Qualifier Qualifier Type

38. What do standardized data exports look like?

39. AAIA Legacy Sample (pipe delimited) AAIA_BrandID|Product_Number|Description|AAIA_Legacy_ID|AAIA_PartTerminology|Attributes_Notes BXYZ|ABC1001|Shock Absorber Jeep CJ Front|1180853|Shock Absorber|2 Door Sport Utility; 4WD; Front BXYZ|ABC1002|Shock Absorber Jeep CJ Front|1180842|Shock Absorber|2 Door Sport Utility; 4WD; Front BXYZ|ABC1003|Shock Absorber Jeep CJ Front|1181270|Shock Absorber|2 Door Sport Utility; 4WD; Front BXYZ|DEF1001|Shock Absorber Jaguar XJ12 Front|1177848|Shock Absorber|4 Door Sedan; RWD; Front BXYZ|DEF1002|Shock Absorber Jaguar XJ12 Front|1177860|Shock Absorber|4 Door Sedan; RWD; Front BXYZ|DEF1003|Shock Absorber Jaguar XJ12 Front|1177871|Shock Absorber|4 Door Sedan; RWD; Front BXYZ|GHI1001|Strut Porsche 911 Front|1351617|Suspension Strut Assembly|Front; 65-9/68 BXYZ|GHI1001|Strut Porsche 911 Front|1351628|Suspension Strut Assembly|Front; 65-9/68 BXYZ|GHI1001|Strut Porsche 911 Front|1351594|Suspension Strut Assembly|Front; 65-9/68

40. <Item MaintenanceType="A”> <HazardousMaterialCode>N</HazardousMaterialCode> <PartNumber>ABC123</PartNumber> <BrandAAIAID>BXYZ</BrandAAIAID> <BrandLabel>Flowmaster</BrandLabel> <PartTerminologyID>10727</PartTerminologyID> <Descriptions> <Description LanguageCode="EN" MaintenanceType="A" DescriptionCode="MKT">The marketing description is often the feature points of the product or part.</Description> </Descriptions> <Packages> <Package MaintenanceType="A”> <PackageLevelGTIN>700042055555</PackageLevelGTIN> <Dimensions UOM="IN”> <Height>12</Height> <Width>17</Width> <Length>66</Length> </Dimensions> <Weights UOM="PG”> <Weight>49.4</Weight> </Weights> </Package> </Packages> . . . PIES XML Sample

41. <App id=“1” action=“A”> <BaseVehicle id=“3109” /> <SubModelID id=“450” /> <EngineBase id=“417” /> <Position id=“12” /> <Transmission id=“1197” /> <Note>65-9/68</Note> <Qty>1</Qty> <PartType id=“10727” /> <Part>GHI1001</Part> </App> <App id=“2” action="A”> <BaseVehicle id="3464” /> <Position id=“12” /> <BedType id=”5” /> <Note>65-9/68</Note> <Qty>1</Qty> <PartType id="2864"/> <Part>GHI1002</Part> </App> ACES XML Sample

42. …but beautiful to the computer systems that process them. They’re ugly to our eyes…

43. …when someone is asking for your “electronic data” What NOT to send…

44. Excel spreadsheets made for human eyes 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.

45. Fields of mixed product information Why not this? -- Sub-model, year range, and fitment notes are all crammed into one cell! Again, completely unreadable by a computer.

46. PDF Pages, Catalogs, Guides…PDFs.

47. Questions?

48. AAIA Technology Standards & Solutions Committee Scott Luckett, VP and Committee Liaison scott.luckett@aftermarket.org SEMA Business Technology Committee Staci Bostock, BTC Staff Liaison stacib@sema.org Websites and Bookmark Tool AAIA - www.aftermarket.org/Technology.aspx ACES – www.enhancedstandard.com SEMA - www.sema.org/btc NAFTA - http://bit.ly/wfuwU Resources for Data Standards

49. ACES Data Standard…Fit Happens Gigi Ho Founder & Data Goddess Digital Performance Inc. gigiho@digitalperformance.com CATALOGING SOFTWARE