00067208 DMV DL ID RFI _final.doc

Oregon Department of Transportation

ODOT Procurement Office

355 Capitol Street NE, MS #33 Salem, OR, 97301

REQUEST FOR INFORMATION (RFI)

Driver License Issuance/ Identification Cards

RFI Number: S-73000-00010698 RFI Issue Date: June 10, 2024 Response Due Date: July 2, 2024 at 12:00 PM PST Written responses to this RFI are due no later than the date identified above. Responses must be submitted via Oregon Buys:

ODOT Procurement Office

Attn: Stephanie Lemhouse

355 Capitol Street NE MS 33

Salem, OR 97301 Email: stephanie.k.lemhouse@odot.oregon.gov NOTE: All proposed information, methodology, and options presented in this RFI are subject to change based upon the Agency’s ability, discretion and need.

Table of Contents

31.

Project Name:

32.

Purpose

33.

High-Level Description of the Current System

34.

Feedback Requested on the Following:

55.

Response Content

66.

Public Records

67.

OregonBuys

78.

Public Notice

79.

Submitting RFI Response to ODOT

710.

Questions and Answers

711.

Notes

1. Project Name:

Request for Information (RFI) for Driver License and Identification (DL/ID) Card Production

2. Purpose The Oregon Department of Transportation (ODOT), through its Driver and Motor Vehicle Services Division (DMV), is interested in learning about available services for production and central issuance of digital driver licenses and identification cards (DL/ID), including facial recognition.

The information provided may assist the DMV in preparing and issuing a formal Request for Proposal (RFP).

3. High-Level Description of the Current System

The information gained from this RFI could be used to develop an RFP to procure a new third-party vendor system and replace the current Agency Digital Photo License (DPL) System.

Functionality and process modifications that enhance Agency business activities, DL/ID security or improve system efficiency will be considered.

1) DMV Systems are comprised of Windows-based applications with SQL Server databases hosted in Salem by the Department of Administrative Services Enterprise Information Services (EIS) Division. Field office and headquarter (HQ) employee workstations consist of personal computers running MS Windows. There are 59 field office locations throughout Oregon with several workstations at most locations. There are DPL workstations located at HQ for testing.

2) The current DPL is a mixture of client-server and browser-based systems. Servers are hosted and maintained in the AWS cloud by the vendor. DPL software is also located on HQ and field office PC workstations that allows for initiating transactions and looking up customer photo history.

3) The current in-office issuance system includes a PC, fingerprint reader (for user access), camera, signature capture device, and interim card printer. There is one system per field office.

4) In 2023, DMV issued, renewed, or replaced approximately 933,000 DL/IDs.

5) DMV’s current contract will expire December 30, 2027.

6) DL/IDs must meet current American Association of Motor Vehicle Administrators (AAMVA) DL/ID Card Design Standards.

4. Feedback Requested on the Following:

a) High-level DPL system architecture

i) Describe how data and images are managed within the DPL system.

b) Issuance system hardware and software solutions

i) Issuance system PC options and software capabilities.

ii) Signature capture equipment options and software capabilities.

iii) Image capture (camera) equipment options.

iv) Options for quick logins to the issuance system. The log-in must verify the identity of the user for each image captured/card produced (e.g., fingerprint reader).

v) Other functions or features provided by the issuance system not requested above.

c) Facial recognition solution options.

i) Capabilities of the one-to-one check (1:1) function.

ii) Capabilities of an automated one-to-many check (1:N) that compares newly captured customer images against all the images (or templates) stored. Include statistics on the system’s ability to reduce false positives.

iii) Process for converting stored images templates to your system.

iv) Compliance with AAMVA facial recognition requirements.

v) Capabilities of manual one-to-many checks and how those will occur without slowing DMV or DPL systems during business hours.

vi) Other functions or features provided by the facial recognition solution not requested above.

d) Integration options with DMV systems.

i) The software and hardware requirements that allow for the DPL system to integrate with SQL Server database systems.

ii) The workflows and technology used to manage data transfers between DPL and DMV systems.

iii) Options for automation and workflow integration with current DMV systems and processes.

e) The central card factory and card distribution point.

i) General locations (in the United States) of the vendor factories that are currently producing DL/ID for a jurisdiction.

ii) Distribution options and services at the factory.

1. Note that DMV requires that DL/IDs be distributed by the United States Postal Service except when cards are expedited or for special circumstances.

iii) Data, material, and product security at the factory.

iv) Employee screening and internal security controls.

v) Other services provided by the central card factory not requested above.

f) DL/ID Card(s) used for driver licenses and identification.

(1) Card product samples of cards currently in production may be requested from Suppliers if DMV elects to proceed with system demonstrations.

ii) DL/ID card materials that are AAMVA compliant.

iii) Compliance with AAMVA requirements on data content.

iv) DL/ID Card layout options that are AAMVA compliant.

v) DL/ID Card security feature options that are AAMVA compliant.

(1) Level 1 which requires cursory examination without tools or aids and that allows for rapid inspection at point of usage.

(2) Level 2 which requires examination by trained inspectors with relatively simple equipment.

(3) Level 3 which requires inspection by forensic specialists.

vi) Options for producing DL/ID for undercover law enforcement officers.

vii) Other DL/ID card features and options not requested above.

g) Options for generating recurring and custom and/or queried reports.

(1) Actual report samples if possible.

h) Options for machine-readable technology (MRT), such as a magnetic stripe, bar code, optical memory, and integrated circuit card.

i) The technical requirements of the DPL and facial recognition solutions

(1) Examples include operating systems, system/server requirements, network requirements, workstation options, space required for hardware, etc.

j) Upcoming functions and features that are being added in the future.

5. Response Content

Responses must be submitted via OregonBuys and will be reviewed by ODOT. Responses submitted hereunder create no binding obligations and confer no rights on any party. This RFI does not constitute a solicitation for bids or proposals, or a guarantee for a solicitation. At any time, ODOT may request additional information from any Responder and may terminate this RFI without incurring any liability to any Responder. By submitting a response, each Responder expressly waives claims for any costs and expenses the Responder incurs in connection with preparation and submission of a response.

It is the supplier’s responsibility to verify receipt of a submitted response.

At a minimum, Suppliers should include the following general information in their response.

1) Legal name and address of the company.

2) Name, telephone number, and email addresses of key contact person(s).

3) A short description of Supplier’s general experience and qualifications.

4) A general description of the functionality by your Company.

5) Please provide written responses that include information that correspond to the Agency’s information described in this RFI.

RFI Criteria:

1) Describe the Supplier’s software that is relevant to this RFI. Include additional modules that may apply.

2) Describe the technical experience, background, and capabilities of Supplier and its principles. Highlight relevant work with other government entities.

3) Estimated project duration – describe how long Supplier anticipates software design, configuration, implementation, data integration and migration, and user testing and training, typically take to complete.

4) Total estimated budget for IT Professional Services (including activities in #3) and annual licensing, support, and maintenance fees, for up to 10 years – line-item costs are preferable.

5) Respond to the items in Section 3, Feedback Requested

6) Describe any additional information, relevant to this RFI, which would be useful for ODOT to better understand available DL/ID issuance hardware and software.

6. Public Records

This RFI, and responses received from Suppliers shall be kept by ODOT and made a part of the public record.

ODOT REQUESTS THAT INTERESTED FIRMS NOT SUBMIT INFORMATION IN THEIR RESPONSE THAT THEY CONSIDER PROPRIETARY OR CONFIDENTIAL.

However, if a Supplier chooses to submit information they consider exempt from public disclosure as specified in Oregon Public Records Law ORS 192.410 through 192.505, or under the grounds set forth in ORS 367.800 through 367.824, then the Supplier must clearly designate the portion of its response that it considers exempt and provide a justification consistent with the statutes identified. ODOT will not accept or consider responses from Suppliers that attempt to exempt the response in whole from disclosure.

Responses are voluntary and non-binding. Comments by suppliers will not bind the supplier to the State contractually, monetarily or in any other way. The State cannot guarantee confidentiality of any documents or written comments submitted by suppliers in response to this Request for Information, as it is available under the "Public Records Law”.

7. OregonBuys

All Suppliers must be registered in OregonBuys to do business with the state and to respond to this RFI. Registration is free. To create a Supplier account, click the blue “Register” button in the top right corner of the OregonBuys website: https://oregonbuys.gov/bso . For registration assistance see Supplier registration guidance (https://www.oregon.gov/das/ORBuys/Documents/SupplierRegistrationGuide.pdf ). Suppliers are responsible for ensuring that their Supplier information is current and correct in OregonBuys. ODOT will accept no responsibility for incorrect Supplier information.

See OregonBuys User Guides located on OPO’s Contracting with ODOT page (https://www.oregon.gov/odot/Business/Procurement/Pages/HowTo.aspx ) for quick reference information regarding common questions from Suppliers when using OregonBuys.

8. Public Notice The RFI and attachments are published in the OregonBuys eProcurement system (https://oregonbuys.gov/bso ). RFI documents will not be mailed to prospective suppliers.

Modifications, if any, to this RFI will be made by written Addenda published in OregonBuys. Supplier is solely responsible for checking OregonBuys to determine whether or not any Addenda have been issued. Addenda are incorporated into the RFI by this reference.

9. Submitting RFI Response to ODOT

Supplier is solely responsible for ensuring its RFI and all required submittal items are submitted through OregonBuys in accordance with the RFI requirements before the RFI Opening Date. RFIs submitted by any other means will be rejected.

Agency is not responsible for any delays by transmission errors or delays, or for any mis-delivery for any reason. Additional information may be found in the OregonBuys Terms of Use.

ODOT reserves the right to invite Suppliers for system demonstrations/ presentations and card product samples for further information gathering.

10. Questions and Answers

All inquiries, whether relating to the RFI process, administration, deadline, the intent or technical aspects of the RFI, or any other provision must:

· Be submitted in writing via email to the Purchaser identified in OregonBuys for this RFI. The email must include the RFI number and identify supplier’s name and contact information;

· Refer to the specific area of the RFI being questioned (i.e. page, section and paragraph number); and

· Be received by Monday, June 24, 2024 at 12:00 PM Pacific Time by email to the Single Point of Contact. All questions and answers will be posted on OregonBuys.

11. Notes

OregonBuys: This RFI is advertised as an “Open Market Bid” in the OregonBuys web-based eProcurement system (https://oregonbuys.gov/bso/ ).

Accessibility: The Oregon Department of Transportation is committed to complying with all statutory requirements to ensure that it is providing information that is more accessible to people with disabilities, as required by Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d), and 36 C.F.R. 1194 Appendix A. This includes information regarding the solicitation process. Please contact the Single Point of Contact (“SPC”) identified in OregonBuys (see “Purchaser” and “Info Contact”) to request reasonable accommodation for access, due to a disability, to information related to this solicitation, or the solicitation process, or both. Accommodation requests must be received by the SPC 3 business days prior to the Proposal Submission Deadline (see “Bid Opening Date” and time in OregonBuys).

Non-Discrimination: [Required by USDOT for all ODOT solicitations, regardless of funding source] Agency, in accordance with the Title VI of the Civil Rights Act of 1964, 78 Stat. 252. 42 U.S.C. 2000d to 2000d-4 and Title 49, Code of Federal Regulations, Department of Transportation, Subtitle A, Office of the Secretary, Part 21, Nondiscrimination in Federally-Assisted programs of the Department of Transportation issued pursuant to such Act, hereby notifies all suppliers that it will affirmatively ensure that all business enterprises will be afforded full opportunity to submit proposals in response to this solicitation and will not be discriminated against on the grounds of race, color, sex, or national origin in consideration for an award.