DLID Verification Systems DIVS

1
Concept of Operations This Document was
prepared under a grant from the Federal Emergency
Management Agency's (FEMA) Grant Programs
Directorate (GPD) United States Department of
Homeland Security. Points of view or opinions
expressed in this document are those of the
authors and do not necessarily represent the
official position of policies of FEMS/GPD or the
U.S. Department of Homeland Security. This
document and associated work product were
produced by Clerus Solutions, LLC as Interim
Program Manager to the DL/ID Verification
Systems, Inc. program under contract to the
Mississippi Department of Public Safety.
2

• Formed to organize, implement, and coordinate a
  system or systems to verify information provided
  by applicants for drivers licenses and
  identification cards.
• Board of Directors
• Representatives from the States of Mississippi,
  Indiana, Florida, Kentucky and Nevada.
• Business, Technical, Privacy/Security,
  Communications Subcommittees
• Subcommittees are a combination of DIVS and
  non-DIVS States
• All activities are funded by the State of
  Mississippi under a FY 2008 grant awarded by the
  Department of Homeland Security (DHS).

3

• Verification systems endorsed by DIVS must meet
  the needs of the states.
• DIVS will rely on work done by others, whenever
  possible.
• DIVS plans to endorse use of AAMVA's existing
  information systems and infrastructure.
• DIVS is committed to providing a high level of
  accountability and transparency regarding its
  direction and decisions.

4

• DIVS will make recommendations regarding
• Requirements, designs, and best practices to
  guide verification system acquisition,
  development, deployment, and operation.
• The long term governance of each verification
  system within its scope.
• DIVS is not intended to be a long standing
  program (3 year program).

5

• DIVS plans to accomplish its mission by endorsing
  a collection of systems.
• DIVS does not intend to actively address all
  possible validation methods or systems.

6

• Identity (Name and date of birth)
• Social Security Number
• Lawful status
• Issuance and validity of drivers licenses or
  identification cards issued by other DLAs
• These data items correspond to the minimum
  verification requirements of the REAL ID Act and
  reflect the shared business needs of all DLAs.
• Verification services endorsed by DIVS may
  contain features that are not strictly derived
  from the REAL ID legislation and regulation but
  are needed by the states to best combat DL/ID
  fraud.

7

• DIVS will foster cooperative development,
  governance and use of electronic verification
  systems by
• Recommending improvements to existing electronic
  verification systems and technical
  infrastructure.
• Supporting the development of new verification
  systems as required.
• Recommending and evaluating pilot projects, where
  appropriate.
• Developing state-based best practices for use of
  the verification systems.
• Providing guidance for the procurement of
  structured testing services that states can use
  to verify that they have made the correct
  modifications to their state driver license
  issuance information system.
• Planning for the long term governance of these
  systems, where needed.

8

• DIVS activities include
• Developing a Program Plan
• Overseeing program deliverables based on the
  Program Plan
• Developing state-defined requirements best
  practices
• Validating that any system development aligns
  with requirements
• Developing funding strategies and cost models,
  where appropriate
• Fostering cooperative relationships with
  stakeholders
• Developing an exit strategy for DIVS that
  includes recommending
• The entity that will provide long-term governance
  and
• How DIVS will transition its activities to that
  entity.

9

• DIVS will not operate any verification systems.
• System operators (ex. AAMVA, NAPHSIS, USCIS,
  etc.) will operate the verification systems.
• Fees
• DIVS will not collect fees from the states for
  participation in DIVS-endorsed verification
  systems.
• Each system operator (AAMVA, USCIS, NAPHSIS, etc)
  will determine its own fee structure.

10

• DIVS Subcommittees conduct the detail level work
  for the DIVS Program. They
• Provide detailed project planning
• Develop or enhance requirements
• Review contractor deliverables for adherence to
  requirements
• Conduct Pilot Program Evaluations
• Develop Best Practices
• Make recommendations to the Executive Committee
  regarding revisions to the Program Plan.

11

• The VLS system currently exists, but has not been
  used by state driver licensing agencies.
  Therefore, DIVS will focus on the following
• Recommend and provide guidance for a pilot
  program so that the VLS system can be validated
  and subsequently used by other jurisdictions.
• Develop best practices post pilot.
• Provide guidance and recommendations for the
  procurement of structured testing services to
  support state implementation.

12

• Includes requirements founds in Section 37.13 (b)
  (5) and Section 37.29 of the REAL ID Final Rule
  (verify that the DL/ID card is not a phony and
  look for multiple cards held by the applicant).
• DIVS has endorsed
• The Design Alternatives White Paper developed
  under Kentuckys pilot program.
• Combining S2S with CDLIS Modernization.
• DIVS will
• Recommend and validate requirements.
• Provide guidance and recommendations for system
  design and development.
• Recommend and evaluate a Pilot Program.
• Provide guidance and recommendations for the
  procurement of structured testing services to
  support state implementation.
• Recommend funding amounts needed to support early
  adopters, if needed.

13

• DHS and US Department of State (DOS) have reached
  agreement that these documents will be
  electronically verified via an upgrade to VLS
  interface.
• DIVS will
• Recommend and validate requirements.
• Provide guidance and recommendations for system
  design and development.
• Recommend and evaluate a Pilot Program.
• Provide guidance and recommendations for the
  procurement of structured testing services to
  support state implementation.

14

• EVVE/EVVER has been pilot tested in three states
  and a pilot evaluation has been conducted.
• Information gained from the pilot is being used
  to modify EVVE and EVVER. Funding for that
  modification is being provided by Kentucky.
• For EVVE/EVVER, DIVS will
• Provide guidance and recommendations for the
  procurement of structured testing services to
  support state implementation.
• Recommend funding amounts needed to support early
  adopters, if needed.
• Provide guidance and recommendations for
  connecting the US DOS to the NAPHSIS EVVE system.

15

• States can verify an SSN either through a direct
  batch transaction with SSA or by using the
  AAMVAnet based SSOLV system.
• The DIVS program endorses the use of SSOLV to
  verify an SSN.
• The DIVS subcommittees will examine the
  possibility of recommending upgrades to SSOLV in
  the future, but these upgrades are not essential
  for REAL ID.

16

• States currently use a shared infrastructure
  operated by AAMVA for a variety of information
  systems (e.g., CDLIS, PDPS, SSOLV, and EVVER).
• Upgrades to the shared infrastructure are
  required to support the added capacity and
  capabilities.
• For the Shared infrastructure upgrades, DIVS
  will
• Recommend and validate requirements.
• Provide guidance and recommendations for system
  design and development.

17

• Integration of these systems occurs within each
  state.
• States choose
• Which systems to use
• How to integrate each system into its issuance
  process

18
(No Transcript)
19

• The complete DIVS Conops along with two versions
  of an executive summary can be found on AAMVAs
  website
• http//www.aamva.org/KnowledgeCenter/Driver/Driver
  LicensingAutomatedSystems/DIVSProgramOverview.htm
• You will need your user ID and password to access
  the information.

20
S2S Business Requirements

• Enable a State to determine if a person holds a
  credential in another State.
• For each record identified as a potential hit,
  provide the inquiring state with enough
  information to determine whether the hit does or
  does not pertain to the applicant.
• States will determine action based on state law
• If the state is taking action to limit a person
  to one REAL ID credential or one customary DL
• The state will interact with the central pointer
  file
• If the state is taking action to limit a person
  to one credential and a non-REAL ID ID card is
  involved
• The inquiring state will send a request directly
  to the state of record to terminate a DL/ID.

21
S2S Work Plan
Business Requirements
IT Review
Privacy/Security
System Requirements V 1.0
Compare to CDLIS
Independent Validation
System Requirements V 2.0
22
State to State Verification System

• Business Requirements have been defined.
• System Requirements have been drafted.
• Next Steps
• DIVS Needs to finalize SRD (v 2.0)
• DHS needs to review SRD
• FMCSA and AAMVA need to review the impact on CDLIS

23
S2S Schedule

• Complete draft of SRD
• Gap analysis vs CDLIS
• AAMVA committee independent review
• DIVS Exec Committee
• Final Approval

• Mid September 2009
• Late September 2009
• Early October 2009
• Mid October 2009

24
Questions?