1. Robert Budd, Michael St. Denis, D.Env., Joe Roeschen - Revecorp Inc. I/M Solutions May 5-8, 2013 Schaumberg, Illinois

2.  Every jurisdiction running an I/M program has a few common components, among those being:  Vehicle Information Database (VID) – the repository for information attained and related to your program operations (test results, safety results, etc.)  A Vehicle Registry (aka: DMV, RMV, etc…) -- the repository of consumer and vehicle titling and registration information  These common components run on database management platforms, most commonly:  Oracle  Microsoft SQL Server Revecorp Inc.

3.  Every jurisdiction has to collect, aggregate, store and index information related to your programs.  Every jurisdiction therefore has to both provide and consume information with multiple interested parties.  An I/M program usually needs to know titling or registration information  A Vehicle Registry needs to know about vehicle emissions (particularly in registration denial jurisdictions)  Communication is two way. Sometimes real-time, some times overnight “batch” oriented – it depends on the program design  Every I/M program needs to report their statistics and data to regulators (EPA). Revecorp Inc.

4.  Now we’ve established that you have multiple data systems, multiple data paths, multiple providers of data and multiple consumers of data.  You magically make it all work (or your vendor does) when they design and implement your system. All good yes? Revecorp Inc.

5.  Program changes?  Infrequent  Never happen  Perpetual contract renewals.  Data sharing?  Islands of data  Never talk to each other  Never share data Revecorp Inc. You never experience:  New requirements?  Infrequent  Never happen  Not my problem

6.  Truth is – you do experience all these things.  Just as you put out specs in an RFP to explain to Vendors what you want, you need specs (standards) to explain how you want data stored. Revecorp Inc.

7.  Why create an I/M Data Format Standard?  Ensure consistency in data definition  Meaning of the data  Usefulness of the data  Transfer relevant I/M Information  Enable data to be collected and used by different types of systems using systems from multiple vendors (facilitate interoperability) Revecorp Inc.

8.  We have all these standards for data collection (SAE, ISO) ▪ Where is the OBD connector? ▪ What shape is the OBD connector? ▪ What data can I get from the onboard Systems, ▪ etc., etc…  But as you’ve seen, and are all aware – you have to store, transmit, share and interpret that data too. Revecorp Inc.

9.  Where are the standards in our I/M industry for data storage (data at rest) ?  About the closest I’ve seen is J2012 for diagnostic trouble codes name/value pairs.  Even something as simple as VIN decoding  Multiple providers (Polk, Revecorp, VinPower, Experian, Motor)  No standardization of naming conventions  Yet – the OEM was very prescribed on how to interpret their VIN and what to call the vehicle. Revecorp Inc.

10.  Are you alone?  Is this normal?  Have others had to solve these problems after years of frustration? Revecorp Inc.

11.  FBI / CA-DOJ  Largest combined fingerprint repositories in the world.  Hierarchy of “search” through FMP’s (start local, then State, then regional and then finally Federal)  Needed a way to all “speak the same language” with regards to attributes associated with such items as: ▪ Scars / marks / tattoos (SMT) ▪ Hair colors, Eye Colors, Skin Colors, etc. ▪ Binary image data transfer (10 print, latent prints) Revecorp Inc.

13.  How to solve the issue of communicating data upstream/downstream?  STANDARDIZE your data format and storage  National Institute of Standards and Technology (NIST) helped out  ANSI/NIST ITL 1-2000 AMERICAN NATIONAL STANDARD FOR INFORMATION SYSTEMS – DATA FORMAT FOR THE INTERCHANGE OF FINGERPRINT, FACIAL, & SCAR MARK & TATOO (SMT) INFORMATION Revecorp Inc.

14.  Perhaps a more relevant example, one that is related to Automotive applications? Revecorp Inc.

15.  Sponsored by Automobile Aftermarket Industry Association, ACES – the Aftermarket Catalog Enhanced Standard - is the North American Industry Standard for the management and exchange of automotive catalog applications data. With ACES, suppliers can publish automotive data with standardized vehicle attributes, parts classifications and qualifier statements. ACES also prescribes a machine-readable format (XML) for trading partners to use in exchanging vast amounts of catalog information electronically Revecorp Inc.

16.  The VCdb represents nearly 50 unique attributes, organized into vehicle systems or attribute groups that are validated against base vehicle and sub-model combinations.  AAIA sponsored, but designed and developed by Motor Information Systems. Revecorp Inc.

17.  The structure of the database allows aftermarket companies to communicate applications with as much or as little detail necessary. The result is more precise, accurate data. The VCdb is an essential element of any data solution that aims to manage and communicate complex vehicle information in a industry standardized format. Revecorp Inc.

19.  A Data Format and Storage Standard that applies to the I/M world.  Shorter migration timelines during vendor changes  NO data mapping  NO (or limited) data validation  NO mistakes  Less complexity when exchanging information  Internally jurisdiction to jurisdiction  Externally with vendors / partners  Increased usefulness of data  Accurate internal/external reporting (think EPA …) Revecorp Inc.

20.  If we organize and standardize our data at rest, what more can we effectively do?  What more can we provide to our customers?  Technical Service Bulletins (TSB’s)  Vehicle Recall Information (Recall’s) Revecorp Inc.

21.  When data is stored in a standard format  When vehicle attributes are structured and known and homogenous across systems  You can search/match effectively and provide more information to customers. Revecorp Inc.

22.  Provide more data, accurately  Greater push for public information services  Technical Service Bulletins (TSB’s)  Safety Recall Information (Recall’s)  If a vehicle is sold, unless the new owner contacts the vehicle manufacturer, recall data does not get to the new owner.  Repair information related to an inspection Failure Revecorp Inc.

23.  I/M specific data storage standard(s) – we need this to further mature as an industry.  You are not alone.  Don’t tackle it alone, get help.  The benefits to both our industry and the public are real. Revecorp Inc.

24. Contact: Revecorp Inc. Robert “Budd” Budd 5732 Lonetree Blvd Rocklin, CA 95765 (916) 786-1006 www.Revecorp.com RBudd@Revecorp.com Revecorp Inc.