Driver License Data Verification (DLDV) Pilot Program Update AAMVA Workshop and Law Institute March 2013

Agenda Background DLDV System Pilot Approach Pilot Participants Pilot Status Next Steps Jurisdiction Participation 2

Background DLDV provides non-AAMVA entities with real-time capability to verify DL/ID credentials with data from the issuing Jurisdiction DLDV aims to meet AAMVA member goals Curb identity theft Prevent documentation fraud Protect integrity of credentials issued by the Jurisdictions DLDV targets three goals from the AAMVA Strategic Plan Goal Identify, develop, and deliver new top-prioritized solutions Goal Develop and implement a funding allocation methodology that enables financial return to Jurisdiction members Goal Mitigate risk of net income shortfalls from contracts expected to end before September

DLDV System Name Document # DOB Issuing State Optional Attributes AAMVA DLDV Verification Engine Retail SSA DOS Gateway Provider 4 Name Document # DOB Issuing State Optional Attributes

Pilot Approach 5 Returns “Match”/“No-Match” indicator for each attribute on the verification request  Required Attributes Last Name Date of Birth License/Document Number State Code  Optional Attributes (depending on availability from Jurisdiction) Address, Document Type (License/Permit/ID Card), First Name, Middle Name, Expiration Date, Eye Color, Gender, Height and Weight

Pilot Approach (cont’d) 6 Working groups organized from End-Users and Jurisdictions  End-User Working Group Financial Services Sector Coordinator Council (FSSCC) Defense Installation Access Control (DIAC) Social Security Administration (SSA) National Association of Public Health Statistics and Information Services (NAPHSIS) Vital Records Agencies (VRA)  Jurisdiction Working Group California, Florida, Iowa, Maryland, Mississippi, Pennsylvania, Texas, and Virginia

Pilot Participants 7  End-Users Gateway/aggregator for financial institutions Gateway/aggregator for retail sector Proof-of-Concept with DHS in parallel for open market use  Jurisdictions Florida, Idaho, Iowa, Mississippi and Nebraska

Pilot Status Development, Integration, and Testing of DLDV Verification Engine Complete ParticipantsAgreements Testing Complete Accept/Send Verification Requests Pilot Evaluation Florida Jurisdiction Pilot Service Agreement XXX Idaho Jurisdiction Pilot Service Agreement XXX Iowa Jurisdiction Pilot Service Agreement XXX Mississippi Jurisdiction Pilot Service Agreement XXX Nebraska Jurisdiction Pilot Service Agreement XXX Appriss Participant Pilot Service Agreement Interconnection Security Agreement XXMarch 2013 EWS Participant Pilot Service Agreement Interconnection Security Agreement XXMarch 2013 AAMVA Execute Commercial Agreements AddressX Prepare evaluation for April 2013 AAMVA BOD Meeting 8

Next Steps Pilot Evaluation Jurisdictions Pilot participants AAMVA Commercial Model Actual market rates and AAMVA/Jurisdictions share dependent on market need for verification services, the application, and negotiations with each partner License Fee/Royalty to Jurisdictions is based on a percentage of AAMVA net revenue Commercial Launch Develop business plan and pilot evaluation report AAMVA Board of Directors approval Jurisdiction and participant outreach 9

Jurisdiction Participation 10 Meets Jurisdiction goals *Curb identity theft *Prevent documentation fraud *Protect integrity of credential *Delivers diversified revenue Streamlined solution for End- users that desire or require access to motor vehicle agency data Limited effort for Jurisdictions to participate *Leverages the AAAMVA Problem Driver Pointer System (PDPS) *Pilot findings Jurisdiction revenue *Jurisdictions receive License Fees/Royalties *End-user fees billed/collected by AAMVA Key Reasons for Jurisdictions to Participate in DLDV Strong interest across multiple markets

Contact Information 11 Philip Quinlan Vice President, Business Solutions AAMVA 4301 Wilson Boulevard, Suite 400 Arlington, VA (o) (703) (c) (571)