ESBD_385003_1737157694648_TexasSure Pre-Proposal Conference1-7-25 (1).pdf

Pre-Proposal Conference TexasSure - Vehicle Financial Responsibility

Verification System

RFO 454-25-0102-28587-TS

January 7, 2025

TexasSure Pre-Proposal Conference

Agenda

• Introductions

• General Procurement Information

• Project Overview

• Scope of Work

• Security Requirements

• Proposal Submission

• Questions

Introductions

• Tricia Schulze, Procurement Director (sole point of contact)

• Joe McElrath, Deputy Commissioner of Information Technology Services

• Melissa Herrera, Director, Property and Casualty – Operations and Planning Office

• Max Marchlewski, Information Security Officer

General Procurement Information

Procurement Schedule

Anticipated Schedule of Events December 13, 2024 Issuance of solicitation January 8, 2025 Deadline for submission of questions January 16, 2025 (or as soon thereafter as practical)

Release of official responses to questions

January 17, 2025 Deadline to submit HSP for courtesy review

January 20, 2025 Deadline for HSP Outreach Notification

January 31, 2025, 3:00 p.m.

Central Standard Time

Deadline for Submission for Proposals

Procurement Schedule

Anticipated Schedule of Events February 10-14, 2025 Presentations by top-ranked respondents May 1, 2025 Anticipated Award Date

Contract Term

• Initial contract term: Execution date to August 31, 2027

• Optional terms: Three (3) one (1) year renewals

Project Overview

Major Information Resources Project

• Contract subject to the requirements for a major information resource project (MIRP)

• Project monitored by the Quality Assurance Team (QAT) oDepartment of Information Resources o Legislative Budget Board oComptroller of Public Accounts oState Auditors’ Office in an advisory capacity

• TDI will use the Texas project delivery framework for this project

Major Information Resources Project

• Quarterly monitoring report to QAT on project:

o schedule o budget o scope o quality

• QAT provides publicly available reporting to the legislature on the progress of MIRPs

• Contractor must supply TDI any information requested by TDI or the QAT

Scope of Work

TexasSure Overview

• Mandated by Texas Transportation Code Chapter 601, Subchapter N.

• Implementing Agencies – TDI, DPS, TxDMV, and DIR.

• Verifies whether owners of motor vehicles have established financial responsibility.

• Used for vehicle registrations, and by Texas law enforcement and justice and municipal courts.

Project Overview Software as a Service solution (NIST 800-145) that:

• Correctly matches vehicle registration information to insurance information and financial responsibility information.

• Adheres to established conditions for query responses.

• Responds to insurance verification queries within 5 seconds.

• Uses existing query and data formats.

• Is available 24/7/365.

TexasSure Data from Reporting Entities

• Insurance policy information from Texas-licensed insurers.

• Self-insured and financial responsibility certificate information from DPS.

• Vehicle registration information from TxDMV.

Insurer and DPS Data

• Receive data weekly via SFTP and PGP encrypted files.

• Enroll and maintain insurers and DPS (data providers).

• Test with each data provider before regular reporting.

• Work with each data provider to troubleshoot and resolve data submission problems.

• Process the data and send notices and reports to data providers to report the status of weekly files.

TxDMV Data

• Receive and process vehicle registration information from

TxDMV.

• Full vehicle registration and title database (master file) provided quarterly.

• Updates to the database provided weekly.

• Provided via SFTP.

Match Data

• Match a registered vehicle to an insured vehicle.

• Use a vehicle link and person link.

• Vehicle link – match the registered vehicle’s VIN to an insured vehicle’s VIN. An exact VIN to VIN link is preferable.

• Person link – match names or addresses between the registered vehicle data and insured vehicle data.

• Incorporate logic and algorithms to identify the most reasonable link.

• 95% accuracy rate required.

Query Response

• Query elements - license plate, VIN, TxDMV document number.

• Apply conditions in Table 1, page 19 to determine response.

• Include query response data elements listed in Table 2, pages 20-21.

• Respond within 5 seconds.

• 99.8% uptime and availability.

Interfaces

• DPS interface o Interface with the Texas Law Enforcement Telecommunication System (TLETS).

oWork with DPS to implement a connection using a REST interface.

• TxDMV interface o Interface with the Registration and Title System.

oUses a web service protocol.

Interactive Web Portal

• Web application for implementing agency staff.

• Query function using license plate, VIN, TxDMV document number.

• Scheduled reports.

• On-demand reports.

• 99.8% uptime availability.

Documentation

• Project management documentation and program documentation (table on pages 28-29).

• Follow best practices and industry standards.

• Follow the submission and update frequency detailed in the table.

• Use the Texas Project Delivery Framework templates where applicable.

Texas Office of the Attorney General

• Texas Transportation Code Section 601.454(c)(3) authorizes

OAG to have access to TexasSure information.

• Contractor will negotiate directly with the OAG.

• Provide TDI with a copy of the statement of work and purchase order.

Optional Services

• Implemented solely at TDI’s discretion.

• Uninsured Notices oNotices to owners of vehicles that may be uninsured.

oResponse portal for consumers to respond to an uninsured notice.

• Access to TexasSure Data by Courts oWeb portal for justice and municipal courts.

oQuery function as described in Part F, Item 5, Query Response.

Other

• Maintenance

• Technical help desk

• Disaster recovery plan

• Communication protocols

• Testing and acceptance

• Transition and implementation

Security Requirements

Security

• Security (Part II, Section K) o Data must stay in contiguous USA o Destroy unnecessary data on devices according to DoD

5220.22.M data wiping guidelines o Encrypt data in transit (TLS) and at rest o Transfer all data to TDI after contract o Private Cloud – TDI data segmented (isolated) from other data o Passwords – NIST 800-63B rev. 3 or better o Single Sign-on with SAML, OpenID, OAuth or other common protocols o Meet Criminal Justice Information Services (CJIS) requirements

• Security Incidents o Annual Cloud Security Alliance validation, or equivalent o Penetration tests

• Driver’s License #

• Insurance Policy #

• Vehicle ID # (“VIN”)

• DOCNO – open deed vehicle identification #

• Name

• Birthdate

• Street Address

• Email Address

• Security Incident Reporting o Unauthorized use, exposure, access, disclosure, compromise, modification, or loss of PII

• Security incident may or may not be a data breach o TDI notification of incident within 24 Hours of discovery o Security incident report to TDI within 5 Business Days

• Report:

o Detailed description o Type of information o Where the data went o Timeline – start > discovery > mitigation o Future steps o Logs – 3 months and current o Point of contact

• Possible Post-incident Actions o Disconnection of services o Notice to Texas residents or reimbursement for TDI notifications o Identity protection o Independent investigation o Contractor is responsible for all costs

• Tx-RAMP Certification (Part II, Section J and Part VI, Section

A) o Product must be Tx-RAMP Level 2 certified prior to contract execution o Approximately six month certification process o tx-ramp@dir.texas.gov to get started

• Employee training (Part II, Section J and Part VI, Section A) o CJIS level 4 training prior to access

• Evidence to TDI in 14 calendar days

• Annually thereafter mailto:tx-ramp@dir.texas.gov

• Employee training (Part II, Section J and Part VI, Section

A) o Annual TDI Security Training

• Texas Government Code 2054.5192

• Prior to accessing State systems

• Must be DIR-approved training (TDI’s)

• Email: ISO@tdi.texas.gov

• Certified Security Officer o Must be employed by contractor at all times o Acceptable organizations:

• Employee Fingerprinting – 30 days of assignment to project

Accessibility

• Accessibility Requirements (Part II, Section J) o Solution must meet or exceed the Texas accessibility requirements of TAC 206 and 213

• (Requirements are similar to Federal “Section 508” of

Rehabilitation 1973 Act.)

o Must complete a Voluntary Product Accessibility

Templates (VPAT) o Commissioner may approve exceptions to these requirements with a detailed remediation plan

Proposal Submission

Submission of Proposals

• Proposal should be submitted via by email to contracts@tdi.Texas.gov

• Email size is limited to 50 megabytes (50MB)

• If multiple emails are submitted, please ensure the subject line indicates x of y (example: TexasSure Proposal 1 of 4)

• Deadline for proposal submission is January 31, 2025 at

3:00 p.m.

mailto:contracts@tdi.texas

Friendly Reminders

• Proposals MUST include a Project Work Plan/Project Schedule

• Title page must be signed

• Execution of Proposal signed and submitted with proposal

• Completed HUB Subcontracting Plan included with proposal

• Conflict of Interest form signed and submitted with proposal

• Certification Regarding Public Nature of the Proposal signed and submitted with proposal

• All Addenda to the solicitation are included and signed in the submitted proposal

Questions?