Driver's License and ID Card System RFP - Attachments D through H.pdf

Customer enters branch, takes ticket number, and obtains application.

Customer completes application while waiting for number to be called

Customer called. Service Agent administers tests, reviews application, and verifies identity documents.

All data uploaded to State’s system, including scanned documents and signature.

Temporary instruction permit, temporary operating permit, or ID card receipt generated by branch office terminal.

Service Agent enters customer data into branch office terminal, scans documents, collects fee, and captures signature.

Future Card Issuance Process

General Office Flow

Does transaction require photo?

End of Process

Select data, including prior photo, sent by State’s system to ICW (Image Capture Workstation).

Service agent selects customer transaction at ICW.

Service Agent reviews data and visually compares prior photo to customer to verify applicant identity at ICW.

Is customer identity verified?

Customer photo is captured.

Service Agent and customer review photo for acceptability.

(ICW has two monitors, including a customer-facing monitor)

State’s system creates daily card request file and sends to Card Vendor. Which include hard card details, photos, and signatures.

Is photo acceptable?

Card Vendor produces card and places card in USPS for delivery to customer within 3 work days of receipt of data from State.

End of Process

Card Vendor sends file to State’s system to confirm card production.

Transaction is referred by CARS to Investigations after the completion of the transaction. The hard card is flagged.

No

Yes

NoYes

Yes

No

Hard card flag and pull procedure on next page:

Attachment D

Hard Card pull and flag procedure (Continued)

Customer photo is captured.

Service Agent and customer review photo for acceptability.

(ICW has two monitors, including a customer-facing monitor)

State’s system creates daily card request file and sends to Card Vendor. Which include hard card details, photos, and signatures.

Is photo acceptable?

End of Process

Yes

No

Card Vendor will send newly created picture and signature, back to CARS from ICS.

Hard Cards will be mailed back to MDOS from the Card

Vendor.

INTRODUCTION TO

ENHANCED DRIVER’S LICENSES,

ENHANCED TRIBAL CARDS

Document Number: 2600006-EDL Introduction v.2 December 5, 2016

Abstract This document provides card issuers with an overview of the programs.

Attachment E

WHTI Introduction to Enhanced Driver’s Licenses, Enhanced Tribal Cards

CBP-OIT-PSPD Official Use Only 1

Change Control Log Revised by Date Description of Revisions PSPD 03/30/2009 Initial Draft

PSPD 10/01/2012 Updated Document

PSPD 10/21/2014 Updated Document

PSPD 8/27/2015 Updated Document

PSPD 12/05/2016 Updated Cover and Contents

CBP-OIT-PSPD Official Use Only 2

Table of Contents

1. INTRODUCTION

1.1 Background ................................................................................................ Error! Bookmark not defined.

1.2 References .................................................................................................. Error! Bookmark not defined.

1.3 Project Objectives

1.4 Timeline

2. CREATING AN EDL PROGRAM – HIGH LEVEL TECHNICAL REQUIREMENTS

3. INFORMATION ON AN EDL – THE CARD

3.1 EDL Topographical Features

3.2 Visual Inspection Zone (VIZ)

3.3 Machine Readable Zone Minimum Requirements

3.3.1 EDL MRZ Standards

3.3.2 EDL MRZ Minimum Requirements

3.3.3 Radio Frequency Identification (RFID)

3.3.4 EDL Integrated Circuit Chip (ICC) Data Schema

3.3.5 Security Features of RFID: Preventing Cloning with the Tag Identifier (TID)

4. EDL DATA INTERFACE OPTIONS

4.1 EDL “Push” Model Data Interface (Preferred)

4.1.1 Reasons for Preferring the Push Model

4.2 EDL “Pull” Model Data Interface

5. EDL TESTING

5.1 New EDL Testing

5.2 Modified\Updated EDL Testing

5.3 Card Assembly and Printing Inspection

5.4 MRZ Testing

5.5 RFID Testing

5.6 Data Interface Testing

5.7 Final Steps

6. EDL/ETC OPERATIONAL USAGE

APPENDIX A. HOW TO POSITION AN RFID-ENABLED DOCUMENT AT A LAND BORDER

CROSSING

List of Figures Figure 3-1. Sample ID-1 Size Travel Card Figure 3-2. Enhanced Card back Figure 3-3. Construction of the ETC Machine Readable Zone Figure 3-4. Construction of the EDL Machine Readable Zone Figure 3-5. Integrated Circuit Chip Data Schema Figure 6-1. Standard Land Border Primary Design

CBP-OIT-PSPD Official Use Only 3

1. Introduction Welcome to the Enhanced Tribal Card (ETC) program, a federal identification card that securely denotes identity and citizenship. These cards can be used to cross U.S. land and sea borders and for domestic air travel. They aren’t acceptable for international air travel, however.

How to create one involves a myriad of standards, steps, forms, and agreements beyond the Memorandum of Agreement you signed. We’ll list all of the different facets and how them interlace and blend together along the path toward producing an ETC card. When it comes to the standards used, we’ll get into the nitty gritty technical details.

The one important thing to remember about producing an ETC card is that the steps do not always follow a linear path. Some of them can be done in parallel with other steps.

The speed with which you can go from start to finish is largely dependent on you. Of course, there are some steps in the process, such as the signatory process for an Interconnection Security Agreement, that falls within the purview of U.S. Customs and Border Protection and the U.S.

Department of Homeland Security.

1.1 Standards

There are several standards you’ll need to become familiar with.is summary references the following documentation needed when electing to participate in the issuance of an EDL:

• International Civil Aviation Organization (ICAO) Doc 9303 Part 3, Volume 1: Machine Readable Travel Documents Part 3 Machine Readable Official Travel Documents Volume 1 MRtds with Machine Readable Data Stored in Optical Character Recognition Format

• EPCglobal Tag Data Standards

• Western Hemisphere Travel Initiative Land and Sea Final Rule

• Use of Radio Frequency Identification Technology for Border Crossings Privacy Impact

Assessments.

• RFID Card Format Use of the EPCglobal Standard ‘Global Document Type Identifier’

(GDTI-96) Tag Data Format for International Travel Documents

• Gen 2 Air Interface Specification

• WHTI Enhanced Driver’s License (EDL) Data Submission Guideline “Push” Model or

WHTI Enhanced Driver’s License (EDL) Data Submission Guideline “Pull” Model

• Test Plan for Acceptance of Federal/State/Province/Territory Issued WHTI Travel

Documents

• Test Plan for Acceptance of Modifications to currently-issued WHTI-approved Travel

Documents

• Enhanced Driver’s License/Enhanced Tribal Card PUSH Data Exchange Test Plan

1.2 Project Objectives

The WHTI EDL program supports the following objectives:

• Create and implement a program for the issuance of an EDL document that meets the requirements of WHTI by any state or Federally Recognized Native American Entity.

CBP-OIT-PSPD Official Use Only 4

• Where possible, leverage an existing data sharing system, The International Justice and Public Safety Network (Nlets), which commonly interfaces with state Department of Motor Vehicle (DMV) databases, to obtain information on an EDL participant.

• Use standard interface in which CBP can receive data on EDL documents.

• Augment current graphical user interfaces development by CBP to display the EDL issuance information.

1.3 Timeline

Upon signature of an MOA, there is no specific time-frame in which an EDL program requires completion. For the technical process, it is necessary to set aside time for CBP to test the card (RFID & MRZ) and data exchange. There have been instances where the RFID chip does not read within the CBP-required parameters, which has required the manufacturer of the card to re-design the antenna in the card. CBP requests a 6-week time-frame to complete the card and data exchange testing. Once the testing is complete, CBP must schedule the placement of new information regarding the EDL in production. During this time, CBP will also prepare a Federal Register Notice (approximately 8 weeks) and Notice to CBP Officers in the Field (approximately 3 weeks).

CBP-OIT-PSPD Official Use Only 5

2. Creating an EDL Program – High Level Technical Requirements The basic technical requirements for creating an EDL include the physical document itself (the card) and sharing the following data with CBP: family and given names; date of birth; sex;

digital image (portrait); travel document type (e.g., EDL); issuing State/Nation, date of expiry;

citizenship; optical character read (OCR) identifier located in the Machine Readable Zone; and RFID tag numbers. This information is retrieved by CBP Officers only when a traveler presents his or her EDL when applying for admission to the United States at a land or sea port of entry.

CBP-OIT-PSPD Official Use Only 6

3. Information on an EDL – The Card

3.1 EDL Topographical Features

The EDL provides issuing authorities a new type of identification card. This card has facilitative technology to provide sufficient information for entry into the United States. Subject to acceptable standards for document issuance, the EDL can then be used for border crossing (land and sea) purposes as part of the Western Hemisphere Travel Initiative.

• The EDL shall be formatted according to specifications for ID-1 (credit card) size travel documents, as described in ICAO Document 9303, Part 3 - Volume 1: Machine Readable Official Documents of Identity. The card contains both eye readable and machine-readable information. The eye readable information is recorded in the Visual Inspection Zone (VIZ) on the front of the card. For machine reading and interoperability, information corresponding to data in the VIZ is printed in the Machine Readable Zone (MRZ) on the back of the card.

The core of this technology is a Radio Frequency Identification (RFID) chip embedded in the EDL that contains a unique identifier for each issued card. This RFID chip uses the “Global Document Type Identifier” (GDTI-96) data schema. For more detailed information, please reference EPCglobal Tag Data Standards Version and RFID Card Format Use of the EPCglobal Standard ‘Global Document Type Identifier’ (GDTI-96) Tag Data Format for International Travel Documents.

Figure 3-1 depicts a sample ID-1 size travel document showing the VIZ and MRZ.

An example of VIZ, front of card An example of MRZ (bottom) , back of card Figure 3-1. Sample ID-1 Size Travel Card

3.2 Visual Inspection Zone (VIZ)

The following items, displayed on the front of the EDL, are the required elements in the VIZ:

• Photograph: Portrait of the holder; no larger than 45 mm x 35 mm nor smaller than 32 mm x

26 mm

• First Name: Given Name or initials

• Last Name: Surname

• Date of Birth: Formatted as 2 digit day, 3 character month, 4 digit year (e.g., 01 JAN 1950)

• Date of Expiration: Document’s expiration date.

CBP-OIT-PSPD Official Use Only 7

• Gender: F = female; M = male; U = unspecified

• Issuing Authority: State or Federally Recognized Native American Entity responsible for issuing the document

• Document Type: Enhanced Drivers License or Enhanced Tribal Card

• Document Number: Uniquely identifies the document (Identification Card Number)

3.3 Machine Readable Zone Minimum Requirements

3.3.1 EDL MRZ Standards

The MRZ is standard to all travel documents and is a mandatory requirement for EDLs. It is located in Zone VII (by ICAO standards) on the non-portrait side of the EDL. The ICAO standards with EDL recommendations for the non-portrait side of an ID-1 sized document are below. A minimum white space of 23mm must be made available in Zone VII for the MRZ.

Figure 3-2 depicts the recommended non-portrait side layout for an enhanced document. For more detailed information, please reference ICAO 9303 Part 3 Volume 1.

Figure 3-2. Enhanced Card back

3.3.2 EDL MRZ Minimum Requirements

The following are the required elements in the Machine Readable Zone (MRZ), which is located on the back of the EDL card:

• Document Code: Two characters, the first “I” and the second “D”, indicating an ICAO-compliant ID

Card.

• Issuing Country: USA.

• Document Number: Document number should be composed of an alpha/numeric nine character string that uniquely identifies the document. Characters occupy all nine positions of the document number field. As a lesson learned and current best practice, the use of the alpha character “O”(oh) is not permitted in the document number field, and the document number shall not contain the same character for all nine positions (e.g. 000000000, 111111111, etc).

• ETC Note: In an ETC, the first two characters (pos. 6-7) of the Document Number are assigned by CBP to distinguish individual issuing entities of ETCs. This is required to determine the correct

14 Message Regarding Limits of Card Use (Optional Data Elements)

MRZ

Zone VI

Zone VII

Pre-printed Serial

CBP-OIT-PSPD Official Use Only 8 database to retrieve the data from in the case of an MRZ swipe, because the state codes are the same

(II).

• Check Digit1: Check digit for the document number.

• Optional Data Elements: The EDL card may include optional data elements; unused character positions are to be filled with the filler character (<).

• Date of Birth (DOB): Format is YYMMDD.

• Check Digit (verifies DOB): Check digit to verify date of birth.

• Gender/Sex: F = female; M = male; < = unspecified.

• Date of Expiration: Formatted as YYMMDD.

• Check Digit (verifies document expiry): Check digit on date of document expiry.

• Nationality/Citizenship: USA.

• Optional Data Elements: The EDL Card may include optional data elements; unused character positions are to be filled with the filler character (<).

• State Code: 2-character state code (i.e. MI for Michigan).

• ETC Note: II (Independent Indian Nation) is the federally-recognized state code that shall be used on all ETCs.

• Composite Check Digit (overall check digit to verify data elements in line 1 and 2 of MRZ):

Overall check digit to verify the data elements of the upper and middle machine readable lines.

• Name: The name consists of the primary and secondary identifiers that are separated by two filler characters (<<). Name components within the primary or secondary identifier shall be separated by a single filler character (<). Example: Mary Jane Hilton-Smith would be printed:

HILTON<SMITH<<MARY<JANE<<<<<<<

• Figure 3-3 and Figure 3-4 illustrate the ETC and EDL MRZs in greater detail.

1 Check digits are used in the MRZ to provide verification that the entered data is correctly interpreted – for more information please see ICAO 9303 Part 3 Volume 1

CBP-OIT-PSPD Official Use Only 9

Figure 3-3. Construction of the ETC Machine Readable Zone

CBP-OIT-PSPD Official Use Only 10

Figure 3-4. Construction of the EDL Machine Readable Zone

CBP-OIT-PSPD Official Use Only 11

3.3.3 Radio Frequency Identification (RFID)

3.3.3.1 Use of RFID in the EDL

Radio Frequency Identification (RFID) is a wireless technology that stores and retrieves data remotely on devices. An RFID system typically includes an RFID tag with a microchip and antenna embedded in a card or other item, an RFID reader with an antenna, and a database. The EDL is embedded with a passive RFID tag, which means it does not have a power source. CBP selected vicinity RFID technology because it facilitates cross border travel by allowing documents to be read automatically, with minimal action by travelers as they drive toward the inspection booth at a land port. Vicinity RFID allows CBP officers to quickly read the advanced information on all travelers presenting RFID-enabled cards, and allows for automated back-end queries. In addition, multiple cards can be read simultaneously with vicinity RFID, allowing an entire car of people to be processed at once.

The RFID tag embedded in an EDL does not contain any personally identifiable information (PII), just a unique reference number that is used by the secure CBP system. Tampering with, or deactivating the RFID tag will invalidate the EDL for purposes of border crossing.

An RFID reader at the border crossing sends a signal to the tag in the EDL and collects the unique reference number so it can be matched to CBP’s records to verify the information printed on the front of the EDL. Data encryption, secure networks, and firewalls protect the information while it is being retrieved from the database. Vicinity RFID tags can be read up to 30 feet from a reader; however, CBP reader antennas are tuned to read at a distance of 10 – 15 feet. For added security, an RF-attenuation security sleeve should be provided to protect the RFID tag from being read when the cardholder is not using it for border crossing.

Generally, if the document with an embedded RFID chip is in an attenuation sleeve, held close to the body, or is blocked by anything composed of metal or water, it cannot be read. While a risk of the RFID tag being read without the owner’s knowledge is minimal, education and the use of an RFID attenuation sleeve helps protect the traveling public from unauthorized reads.

For further information, please reference RFID Card Format Use of the EPCglobal Standard ‘Global Document Type Identifier’ (GDTI-96) Tag Data Format for International Travel Documents.

3.3.4 EDL Integrated Circuit Chip (ICC) Data Schema

Among participating government entities, EPCglobal standards are used to determine the information stored on the RFID chip. EPCglobal is a not-for-profit organization that develops and promotes standards used in the RFID community. Adherence to EPCglobal standards makes it easier to work with a wide choice of vendors, and helps promote interoperability among vendors.

The unique identifier of each card to be electronically written should comply with EPCglobal Tag Data Standards. The key to be used is the Global Document Type Identifier (GDTI-96), a simple tool to identify a document by type. RFID chips which meet the GDTI-96 EPCglobal Tag Data Standards are referred to as “Gen 2” tags. The following represents a high-level overview of the GDTI-96 data schema. For more detail, please reference EPCglobal Tag Data Standards.

CBP-OIT-PSPD Official Use Only 12

In order to maintain the critical one-to-one correspondence between the encoded RFID number and the corresponding data records, there can be no duplicate use of RFID numbers across a given document issuing authority.

The data schema primarily consists of (see the table below):

• EPCglobal Header specifying the tag data is encoded as a GDTI-96 96-bit tag construct.

• EPCglobal Filter Value of 001 identifying a tag as a ‘travel document’. All WHTI-compliant RFID-enabled travel documents contain ‘001’ for the Filter Value Field. CBP lane equipment is designed to filter out all other Gen 2 RFID numbers.

• Company Prefix: Every state, agency, or organization issuing RFID-enabled travel documents must request a Company Prefix from the GS1/EPCglobal organization. The Company Prefix is a 6 to 12 digit number that uniquely identifies an organization throughout the world. The Company Prefix block of the GDTI-96 tag contains this number. The number is assigned only once; the issuing authority uses the same company prefix for all RFID-enabled travel documents. [Note: This number can be used for all state-designated identification purposes – i.e. barcodes, equipment, casino chips, etc.]

• Document Type: For each issuing authority, GS1 issues only one Company Prefix. The Document Type field allows differentiation among different types or series of travel documents for each issuing authority. The Document Type field is a variable-length field controlled by the length of the Company Prefix. The number of digits available to use in the document field is 12 minus the length of the Company Prefix.

• Use of this field is not required; however, CBP recommends all participating agencies consider its use for future filtering capabilities. For example, when an issuing authority changes card manufacturer, using a different Document Type code will help ensure duplicate GDTI-96 numbers are not created and issued.

• Serial Number: 41 bits offers 2

= 2,199,023,255,552 (2.1+ trillion) unique numbers that are managed by the issuing organization. Serial numbers are unique per organization, so any organization can issue a serial number in the range [1 - 2,199,023,255,552]. Each managing organization is responsible to ensure unique serial numbers are encoded across a set of issued travel documents.

CBP recommends serial numbers be assigned using a random number generator. Once a number is assigned, the issuing authority is required to use the permalock feature to prevent subsequent rewriting of data on the chip.

• Figure 3-5 provides the chip data schema format and elements.

CBP-OIT-PSPD Official Use Only 13

Figure 3-5. Integrated Circuit Chip Data Schema

ICC Data Schema

Header Filter Value

Partition Company Prefix

Document Type

Serial Number

Bit Size 8 bits 3 bits 3 bits 20-40 bits 21-1 bits 41 bits

Value Range

0010 1100

(Static, Binary Value)

001 Indicates lengths in Company Prefix and Document Type fields1.

999,999 – 999,999,999,999

(Max. decimal range1)

999,999-0

(Max. decimal range1)

2.1+ trillion

Assigned By

EPCglobal EPCglobal EPCglobal EPCglobal Tag Owner Tag Owner

The Company Prefix and Document Type fields are both variable length. The Partition field indicates which lengths can be found in each of the fields.

3.3.5 Security Features of RFID: Preventing Cloning with the Tag Identifier (TID)

The Tag Identifier (TID) found on all Gen 2 chips is an immutable number that uniquely identifies each individual RFID chip. This unique number, when used in conjunction with the GDTI-96 electronic product code (EPC) value, is a very powerful tool that can be used to negate the ability to clone a WHTI GDTI-96 encoded RFID card.

Issuing authorities should ensure that all Gen 2 cards used with WHTI include a 64-bit TID memory bank initialized with the following values (per the Gen 2 Air Interface Specification):

• 8 bits are for ISO class identifier (a unique number indicating the tag is following the Gen 2 specification)

• 8 bits are for manufacturer identifier (assigned by EPCglobal)

• 48 bits are for unique serial number Refer to the RFID Card Format Use of the EPCglobal Standard ‘Global Document Type Identifier’ (GDTI-96) Tag Data Format for International Travel Documents.

CBP-OIT-PSPD Official Use Only 14

4. EDL Data Interface Options Establishment of an EDL data interface provides information (i.e., photo and information of the EDL holder) and supports transfer of new or updated EDL information from an issuing authority to CBP for display at various land or sea ports. An issuing authority may elect to provide CBP with a mirror copy of all issued EDL records to be forwarded in a standard format and kept in CBP (referred to as the “PUSH” model) or the issuing authority may elect to use Nlets to provide CBP with real-time access to issued EDL records (referred to as the “PULL” model).

When an EDL-holder crosses the border, the data extracted from the RFID or MRZ will be used to trigger access to the EDL data. When a document is read at the border, name, date of birth, gender, citizenship and photo, along with the results of law enforcement queries, will be presented to the CBP Officer in the inspection booth for review.

CBP’s use, retention and sharing of EDL information under both models is explained in the Privacy Impact Assessments and System of Records Notices prepared by CBP as part of WHTI implementation, including the Western Hemisphere Travel Initiative Land and Sea Final Rule, Use of Radio Frequency Identification Technology for Border Crossings Privacy Impact Assessments. These documents are available through the DHS Privacy Office and online at the Privacy Office section of the DHS website, www.dhs.gov.

4.1 EDL “Push” Model Data Interface (Preferred)

An issuing authority may elect to provide CBP with a mirror copy of all issued EDL records;

EDLs issued and updated are forwarded in a standard format and kept in the CBP data center (referred to as the “PUSH” model). In the “Push” model, issuing authorities will push EDL data at time of issuance or update to CBP, which will insert and store the EDL data into a secure database for access as mentioned above. CBP takes full responsibility for transference of the data to officers at ports at the time an EDL is presented to the officer. CBP logically separates the issuing authorities’ data from all other data in CBP systems for a number of reasons, performance and response time being principal drivers.

The EDL data provided by this interface is intended for use at primary (i.e. initial) screening of the presented EDL data. Any issues or questions arising during this primary screen will be referred to secondary CBP screening processes, which are supported by additional data sources outside of the scope of this interface.

There are a variety of options for interfacing with CBP in the Push model.

The preferred interface method is via Nlets, which is a message switching system that uses message keys to transmit data between issuing authorities’ databases and other criminal justice systems. The use of Nlets for the data exchange interface requires only a Service Level Agreement (SLA) be signed between CBP and the issuing authority.

An alternate method of interface is the Virtual Private Network (VPN) which would create a direct link between CBP and the issuing authority. This requires both an SLA and an Interagency Security Agreement (ISA) be signed between CBP and the issuing authority.

Refer to the WHTI Enhanced Driver’s License (EDL) Data Submission Guideline “Push” Model for detailed requirements for the data interface using the “push” model.

http://www.dhs.gov/

CBP-OIT-PSPD Official Use Only 15

4.1.1 Reasons for Preferring the Push Model

In brief, the reasons for implementing the Push model for EDL data sharing initiatives between an issuing authority and CBP are:

• Performance – The data needs to be accessible, processed, and presented to the CBP primary officer in milliseconds. The burden to attain performance requirements is with CBP.

• Availability – The data needs to be available 24x7. The burden to have resources on standby is with CBP.

• Reliability – The data is resident on CBP server. The burden to trust and ensure reliability of systems is with CBP.

• Response – The burden to respond to problems is with CBP; CBP will have the ability and control to solve problems without requiring the use of issuing authorities’ resources (unless related to updates or data synchronization).

• Retention – The data is resident on the CBP database, logically separated from other databases. The burden to retain data for a minimum period of 10 years with backup processes, and 24x7 accesses for internal affairs purposes, is with CBP.

• Redundancy – CBP has redundant systems capability designed in to the enterprise ensuring no single point of failure can disrupt border operations.

• Data Security – The burden to maintain data in a 24x7 physically secure location (to include fencing, armed guards, cameras, restricted access controls), and to store this data on secure databases meeting federal information processing standards is with CBP.

• Disaster Recovery – CBP maintains a Disaster Recovery capability that ensures border operations remain possible after a catastrophic event.

• Maintenance – The burden to maintain most critical hardware, software, performance levels, service levels, etc., is with CBP.

• Cost – This model introduces the least cost burden on the issuing authority in terms of coding, workforce, additional information technology infrastructure needed, etc., in relation to the above. The majority of cost and responsibility is with CBP.

• CBP Processing – Biographic data collected and stored at border crossings today does not change with WHTI implementation, or as a result of EDL data sent to CBP systems.

• Safeguards – All officers making inquiries have had a full field background investigation and are given information on a “need-to-know” basis only, and only in performance of official duties.

As stated, CBP believes the PUSH model is the least burdensome route for an issuing authority to take, and the best approach to support border operations.

4.2 EDL “Pull” Model Data Interface

In the “Pull” model, the issuing authority stores their data in their own database, and CBP retrieves the data via Nlets when an EDL is presented real-time at a border crossing. Nlets uses a driver inquiry message key to inquire the appropriate issuing authority; the authority receives the inquiry, retrieves the data from their database and forwards the EDL data to CBP along the same route. CBP receives the response and the data is displayed on the CBP Officer’s workstation.

CBP-OIT-PSPD Official Use Only 16

This approach requires a 99.99% up time 24/7 with a 500 millisecond response time, requiring issuing authorities to provide support 24/7 in the event a data transfer problem occurs at the border crossing when an EDL-holder presents his or her document to the CBP Officer. For standardization, the Pull model uses XML schemas.

Nlets, a message switching system that uses message keys to transmit data, is commonly used for connectivity between state DMV databases and other criminal justice systems, to CBP.

Refer to the WHTI – Enhanced Driver’s License (EDL) Data Submission Guideline “Pull” Model for detailed requirements for the data interface using the “pull” model.

The election of the “Pull” Model will require participating organizations to develop and enter into an SLA with CBP. Key to the success of a Pull model is response time; participating organizations will need to respond to a CBP EDL query from a port of entry, at the time of crossing, in less than 500ms.

CBP-OIT-PSPD Official Use Only 17

5. EDL Testing CBP performs two different series of tests on EDL documents. The issuance of a new EDL by a State or Nation requires comprehensive testing. In instances where a State or Nation has modified an existing EDL (i.e.: changing print design, security features, manufacturers, card material substrate, chip or antenna, etc.), testing of the modified EDL involves a limited subset of tests.

5.1 New EDL Testing

CBP requires formal life cycle testing complete with independent testing. In order to complete full testing of sample cards, CBP requires test card samples, as close to production construction, artwork and printing as possible and printed with correct MRZ, GDTI-96 and TID data. A minimum number of 20 cards are required for testing, but a set of 100 test cards is preferred.

Organizations expecting to issue more than 10,000 Cards must provide a set of 100 cards.

For each EDL, a correlating record should also be available to CBP to ensure thorough software interface testing before production. CBP will provide a list of names that should be on the test cards to facilitate MRZ and data interface testing.

CBP welcomes interim construction cards to assist card and antenna design and development.

These tests, though, are only considered interim testing and do not constitute any level of acceptance testing. CBP does not intend to test the physical characteristics of an EDL, durability of such documents, or to provide an analysis of any proposed security features introduced into an

EDL.

A complete set of sample cards must be on location at CBP and data available to CBP for the 6-week testing timeframe to begin. Approximately 7 business days are allocated for each of the following tests:

1. EDL Testing Subject Matter Experts take the final cards and completes the RFID / MRZ / visual inspection tests on all cards in accordance with the Test Plan for Acceptance of Federal/State/Province/Territory Issued WHTI Travel Documents.

2. The Software Development Testing team completes tests in the development environment using cards to test the MRZ swipe to ensure data in the MRZ is correct, readable and matches corresponding data in the database. Testing is also performed to ensure that the name of the EDL holder is formatted correctly in accordance with the International Civil Aviation Organization (ICAO) Doc 9303 Part 3, Volume 1: Machine Readable Travel Documents Part 3 Machine Readable Official Travel Documents Volume 1 MRtds with Machine Readable Data Stored in Optical Character Recognition Format.

3. The software is then released to the System Acceptance Testing team who complete tests against all the databases and the systems, using both MRZ and RFID to access the data.

4. Finally, the Quality Assurance Testing team performs the tests in a test environment that mimics the ‘real world’ environment as much as possible.

5. Any issues that arise could require CBP to start the cycle over again (depending on the severity/complexity of the issue, the changes/testing could be quick or cause further delay).

CBP-OIT-PSPD Official Use Only 18

6. Once all of this is complete, CBP schedules release to production.

While CBP may complete testing early, experience has shown that the standard 6-week timeframe allows working through unanticipated issues that have risen based on different interpretations of requirements, setting up test environments and connectivity, etc. between CBP and enhanced card issuers in the past. CBP will certainly work towards an earlier deployment to production if testing is concluded early.

For more detailed information, please refer to Test Plan for Acceptance of Federal/State/ Province/Territory Issued WHTI Travel Documents.

5.2 Modified\Updated EDL Testing

When an existing EDL is modified, limited testing is performed to ensure no significant areas of card production have been negatively impacted. See the Test Plan for Acceptance of Modifications to currently-issued WHTI-approved Travel Documents for a detailed description of these tests.

5.3 Card Assembly and Printing Inspection

Card assembly involves the lamination of an RFID inlay (the chip and antenna) between layers of card stock material. A visual inspection is conducted on each card to ensure that there are no imperfections that would otherwise expose the RFID components to the elements or impede the use of an EDL in CBP processing.

Visual inspection of the document’s printing characteristics includes the following: photo is easily recognizable (not obstructed by security features), the minimum biographic data required for WHTI travel document exists, data on the front and back of the card is organized into appropriate zones, etc.

5.4 MRZ Testing

The three-line MRZ must meet International Civil Aviation Organization (ICAO) specifications.

MRZ testing includes the following: printed using OCR-B size 1 font used according to specifications; at least 23 mm of white space is in the MRZ zone; MRZ text is 5 mm +/- 1mm from the left side of the card; names in the MRZ Line #3 are correctly formatted and parsed using the naming rules convention; etc.

The MRZ is also swiped in a card reader and database results are checked: the MRZ data matches the information on the front of the card; the four check digits are calculated correctly;

and the information retrieved from the test database matches the data on the card.

5.5 RFID Testing

Each WHTI card will contain a Gen 2 RFID chip with 96 bits of Electronic Product Code (EPC) memory and 64 to 112 bits of uniquely serialized, factory programmed tag identification (TID) memory.

RFID testing covers the following: the number is formatted correctly and matches the appropriate company prefix; the scanned EPC number and unique TID number match the

CBP-OIT-PSPD Official Use Only 19 number provided by the issuing authority; the information retrieved from the test database matches the data on the card.

RFID security testing includes the following: RFID is correctly permalocked; the kill command does not work and the kill password is locked; the attenuation sleeve appropriately stops reads.

RFID sensitivity testing is also conducted to ensure cards will be readable at the ports. The acceptable average Power on Tag for a Card should fall between -12 dBm to -7 dBm.

5.6 Data Interface Testing

Data interface testing involves ensuring the cards provided match the data retrieved from the test database (either data pushed to the CBP testing environments or data pulled from the issuing entity’s own test environment, depending on the model followed).

For the Push model, the load process will be tested in three regions: Development, System Acceptance and Quality Assurance regions. As each region is loaded, the appropriate team will test the cards and resulting data retrieved to ensure no mis-interpretation of requirements exists.

Refer to the Enhanced Driver’s License/Enhanced Tribal Card PUSH Data Exchange Test Plan for detailed information on the data interface testing.

5.7 Final Steps

Once testing is complete, CBP prepares the changes for production. This process can take a minimum of 2 weeks, depending on the level of changes required for CBP systems.

CBP-OIT-PSPD Official Use Only 20

6. EDL/ETC Operational Usage The processing of an enhanced card takes place at designated entry points, specifically at inspection booths located at land border ports of entry (POE) vehicle primary inspection lanes.

Inspections are composed of both primary and secondary inspections. Primary inspections are required of all vehicle traffic, both commercial and private. Secondary inspections are more detailed and are performed upon referral from primary.

Figure 6-1 depicts the standard setup at a POE.

CBP-OIT-PSPD Official Use Only 21

Figure 6-1. Standard Land Border Primary Design In the pre-primary zone, RFID antennas and readers in the vehicle approach lane detect and read RFID-enabled travel documents (such as an EDL), capture and transmit the unique number from the chip to the appropriate databases to retrieve associated traveler biographic and photo data.

See Appendix A for the detailed instructions on how the EDL should be presented to ensure that the RFID is accurately read. Accurate RFID ensure that the EDL holder’s data is presented to the CBP officer prior to the vehicle’s arrival at the booth, which can reduce traveler processing time. Distribution of these instructions to EDL holders when they receive their EDL can both the EDL holder. This information could also be posted on the issuing authority’s web site so that EDL holders are aware of the proper manner in which to present their document in Pre-Primary arrival.

Upon capture of the travelers’ data, queries are automatically performed and the results are displayed to the CBP officer. At the primary booth, travelers in vehicles may be required to:

• Present identity/travel documentation

• Declare intent and purpose of travel

• Make an oral customs declaration

The data that is shared with U.S. Customs about an EDL cardholder is basically the same data found in a U.S. Passport:

CBP-OIT-PSPD Official Use Only 22

• Given Name

• Middle Name (optional)

• Surname

• Date of Birth

• Sex

• Citizenship (USA)

• Card Expiration Date

• Issuing State

• Issuing Country (USA)

• Photo

• Encoded Document number (number in the Machine Readable Zone)

• Chip RFID and TID numbers

CBP officers in the booth review documents presented by the travelers, confirm identity and citizenship, conduct an interview of each traveler to determine compliance with immigration and other laws, and may perform an inspection of the vehicle. The CBP officer then makes a determination whether the vehicle and occupants should be admitted into the United States or be referred to Secondary for further processing.

CBP-OIT-PSPD Official Use Only 23

Appendix A. How to Position an RFID-Enabled Document at a Land Border Crossing This section presents a one-page overview of the use of an RFID-enabled document at a land border crossing.

Attachment- G Glossary of Terms

1D One Dimensional 2D Two Dimensional AAMVA American Association of Motor Vehicle Administrators ADA Americans with Disabilities Act

ANSI INCITS

322-2015

Card durability test method established by American National Standard Institute, InterNational Committee for information Technology Standard, as referenced in the AAMVA North American DL/ID 2016 Card Design Standard.

API Application Program Interface Business Days

All days except Saturday, Sunday, and State of Michigan holidays.

CARS Customer and Automotive Records System Contractor Company or individual submitting a proposal in response to this RFP Days Any calendar day.

DHS Department of Homeland Security DL/ID Driver’s License/Identif ication Card DTMB Department of Technology, Management and Budget. Includes business functions that provide IT services to all State of Michigan agencies. Also provides contract and procurement services.

EDL/EID Enhanced Driver’s License/Enhanced Identif ication Card HARD CARD Driver’s License, Identif ication or Vehicle Salvage Agent Card ICAO International Civil Aviation Organization ICW Image Capture Workstation ISO/IEC International Organization for Standardization/International Electrotechnical Commission JEC Joint Evaluation Committee JPEG Joint Photographic Experts Group – Standard for image compression MDOS Michigan Department of State. The terms “MDOS” and “the State” are used interchangeably.

Mobile Office A trailer that travels to events throughout the State and of fers services otherwise performed at stationary MDOS branch of f ices.

MRZ Machine Readable Zone NASPO North American Security Products Organization REAL ID Act of 2005

Federal law that mandates that three years af ter enactment (May 2008), a state driver's license or ID card cannot be used for any federal purpose unless it meets specif ic federal requirements.

RFID Radio Frequency Identif ication RFP Request for Proposal SSI Sensitive Security Information. As def ined in the Code of Federal Regulations, Part 49:

Transportation, Section 1520.5. Sensitive security information. In general, in accordance with 49 U.S.C. 114(s), SSI is information obtained or developed in the conduct of security activities, including research and development, the disclosure of which TSA has determine would: (1) Constitute an unwarranted invasion of privacy (including , but not limited to, information contained in any personnel, medical, or similar f ile); (2) Reveal trade secrets or privileged or conf idential information obtained f rom any person; or (3) Be detrimental to the security of transportation.

State State of Michigan WHTI Effective June 1, 2009, the Department of Homeland Security (DHS) and the Federal

Department of State endorsed a federal law requiring travelers to present a valid passport or other secure identif ication document when entering the United States at land and seaports of entry.

BR # Branch Name Address Hours 100 Adrian 1040 S Winter St Suite 2200 Adrian, MI 49221 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 101 Inkster 26603 Michigan Ave, Inkster, MI 48141 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 109 Ann Arbor 295 North Maple Rd, Ann Arbor, MI 48103 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 110 Trenton 3040 Van Horn, Trenton, MI 48183 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 111 Belleville 164 E Columbia Belleville, MI 48111 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 112 Chelsea 1113 M-52 Village Plaza, Chelsea, MI 48118 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 113 Ypsilanti 4675 Washtenaw, Ann Arbor , MI 48108 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 115 Monroe 1107 S Telegraph Rd, Monroe, MI 48161 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 116 Temperance 7200 Lewis Ave C-6, Temperance, MI 48182 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 117 Redford 25700 Joy Rd, Redford, MI 48239 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 118 Westland 6090 N Wayne Rd, Westland, MI 48185 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm

120 Livonia 17176 Farmington Rd, Livonia, MI 48152 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm, S:

9:00 am - 2:00 pm

121 Novi 31164 Back Rd, Novi, MI 48377 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 125 Brownstown 18412 Telegraph Rd, Brownstown, MI 48174 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 128 Canton 8565 N Lilley Rd, Canton, MI 48187 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 131 West Bloomfield 4297 Orchard Lake Rd., Suite 220, MI 48323 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 133 Detroit-Livernois 17500 Livernois Detroit, MI 48221 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 135 Detroit-W. 7 Mile Rd. 20220 West 7 Mile, Detroit, MI 48219 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 138 Detroit-Bagley St. 2835 Bagley, Detroit, MI 48216 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 141 Taylor 21572 Ecorse Rd, Taylor, MI 48180 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 142 Oak Park 13401 W 10 Mile Rd, Oak Park, MI 48237 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 143 Southfield 25263 Telegraph Rd, Southfield, MI 48034 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 144 Dearborn 5094 Schaefer, Dearborn, MI 48126 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 151 Hamtramck 9001 Joseph Campau, Hamtramck, MI 48212 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 153 Hazel Park 20809 Dequindre Rd Hazel Park, MI 48030 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 154 Detroit-Mack Ave. 14634 Mack Ave, Detroit, MI 48215 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm

157 Detroit-W. Grand Blvd. 3046 W Grand Blvd, Detroit, MI 48202 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm, S:

9:00 am - 2:00 pm

158 Warren 11533 E. 12 Mile Rd, Warren, MI 48092 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 162 Eastpointe 18809 E 9 Mile Rd. Eastpointe, MI 48021 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 163 Port Huron 2887 Krafft Rd, Port Huron, MI 48060 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm

Attachment H Branch Locations and Hours

164 Shelby Township 50640 Schoenherr Rd, Shelby Township, MI 48315 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm

166 Clinton Township 37015 S Gratiot Ave, Clinton Township, MI 48036 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm, S:

9:00 am - 2:00 pm

168 Rochester Hills 2250 Crooks Rd, Rochester Hills, MI 48309 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 169 Sterling Heights 7917 19 Mile Rd, Sterling Heights, MI 48314 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 170 Romeo 71130 Van Dyke Bruce, MI 48065 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 171 Chesterfield 51305 Gratiot Ave, Chesterfield Township, MI 48051 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 175 Troy 1111 E Long Lake, Troy, MI 48085 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 176 Lapeer 301 W Genesee St., Lapeer, MI 48446 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm

181 Pontiac 1270 Pontiac Rd Pontiac, MI 48340 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm, S:

9:00 am - 2:00 pm

182 Highland 672 N. Milford Rd, Highland, MI 48357 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 185 Davison 300 N Main St, Davison, MI 48423 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 187 Clio 4256 W Vienna Rd, Clio, MI 48420 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 189 Clarkston 7090 Shabaaw rd, Clarkston, MI 48348 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm

194 Flint-Fenton Rd. 5512 Fenton Rd, Flint, MI 48507 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm, S:

9:00 am - 2:00 pm

195 Flint-S. Saginaw St. 408 S. Saginaw Flint, MI 48502 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 201 Kalamazoo 3298 Stadium Drive, Kalamazoo, MI 49008 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 202 Portage 603 Rommence Rd, Portage, MI 49024 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 203 Paw Paw 32849 Red Arrow Hwy, Paw Paw, MI 49079 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 205 Sturgis 931 S Centerville Rd Sturgis, MI 49091 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 206 Dowagiac 601-C N. Front St. Dowagiac, MI 49047 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 207 Niles 110 E Main St, Niles, MI 49120-2200 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 208 Benton Harbor 1960 Mall Drive, Benton Harbor, MI 49022 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 216 Battle Creek 5420 Beckley Road, Suite L, Battle Creek MI 49015 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 219 Albion 308 S. Superior St. Albion, MI 49224 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 220 Jackson 1184 Jackson Crossing, Jackson, MI 49202 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 223 Coldwater 7 Vans Ave, Coldwater, MI 49036-1724 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 224 Hillsdale 59 E St Joe Ave Hillsdale, MI 49242 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 226 Lansing-Executive Court 8158 Executive Court, Lansing, MI 48917 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm

Attachment H

228 Lansing-East Michigan Ave. 3315 E Michigan Ave, Lansing, MI 48912 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm, S:

9:00 am - 2:00 pm

229 Mason 806 Hogsback Rd, Mason, MI 48854 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 230 Howell 1448 Lawson Rd, Howell, MI 48843 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 237 Alma 1586 Wright Avenue Alma, MI 48801 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 239 Greenville 701 S Greenville West Dr, Greenville, MI 48838 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 243 Mt Pleasant 1245 N Mission, Mt Pleasant, MI 48858 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 244 Muskegon 1485 Apple Ave, Muskegon, MI 49442 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 247 Sparta 534 S State St, Sparta, MI 49345 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 254 Midland 1832 N Saginaw, Midland, MI 48640 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 255 Hudsonville 5211 Cherry Avenue Plaza, Hudsonville, MI 49426 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 256 Holland 587 E Eighth Street, Holland, MI 48423 M-T-TH-F: 9:00 am - 5:00 pm, W: 11:00 am - 7:00 pm 257 Grand Haven 1110 Robbins Rd.