SSJF 22-0100 TRMMP Attachment A.pdf

TRMMP - ATTACHMENT A

Section VI - Business Rationale #2. Provide a list and describe in detail the specifications required to satisfy the need:

1. The TRMMP contract encompasses a complex combination of hardware, customized and proprietary software applications, and extensive maintenance services to ensure complete and sufficient collection of toll transactions and revenue, along with enforcement and pursuit of toll violators. This system is made up of various applications and, now that a contract for the lane aspects has been awarded, the remaining segments to be addressed in 2023-2024 include the Host System for aggregating all toll transactions and revenue collection as well as the legacy Violation Processing System (and its associated Customer Service Center System) for managing aged debt.

These systems make it possible to collect approximately $1.4 billion annually in toll and violation revenue.

2. An RFP to replace this system is in development. Until a replacement system has been implemented, it is necessary to keep the current Host System in compliance with all regulatory, financial, technical and/or security requirements. The Host System is customized and proprietary and includes a scope of work that is continuous and evolving. The specific scope for 2023 is anticipated to be similar to services provided in previous years. Requirements to satisfy this need include:

a. Interoperable tolling testing/upgrade. This is necessary to remain in compliance with the Interoperability/Intergovernmental Agreement.

i. Lane integration work that will prepare the Tollway to read non-I-PASS transponders (e.g., SunPass from Florida and TollTags from Texas). This initiative will reduce costs for issuing expensive violation notices and allow patrons from any account across the U.S. to utilize our system.

ii. Expected work effort: 400 hours for initial modifications and testing; up to 600 hours integration/implementation.

b. 6C protocol testing. This is necessary to remain in compliance with the Interoperability/ Intergovernmental Agreement.

i. Lane and Host integration work that will allow use of new transponder and reader technology for I-PASS. ISTHA can than issue “sticker tags” to patrons instead of standard transponders which will lead to significant cost savings as sticker tags cost one-eighth the price of standard I-PASS transponders.

ii. Expected work effort: 400-800 hours development/testing/implementation.

3. In addition to the customized and proprietary Host System, this sole economically feasible source procurement also accommodates support and maintenance of the legacy Violation Processing System (and its associated Customer Service Center System) for managing aged debt. The goal for 2023 includes continuing projects to enable the sunsetting of the legacy systems. Requirements to satisfy this need include:

a. Data archiving and cleanup.

TRMMP - ATTACHMENT A

i. Compliance requirement with State data archiving mandate. This initiative will prepare the Tollway for the migration to a successor vendor.

ii. Estimated work effort: 1,000+ hours development/implementation.

b. Consolidation of aged receivables (factoring uncollectible debt). This is necessary for financial compliance and risk mitigation (litigation and revenue risk avoidance).

i. Initiative to close out aged, uncollectible receivables from the Tollway’s violation program.

This will address the Tollway’s efforts to improve toll violations enforcement equity.

ii. Estimated work effort: 800+ hours development/implementation/monitoring.

4. Other scopes of work requested are similar to previous years as the dynamics of the IT security and compliance environment continue to be a regular aspect of ensuring system and data integrity.

Further, with more than one billion transactions to be processed annually, there is a continual need to assess the sizing and processing capacity of the legacy system. Therefore, the need to continuously monitor and maintain these systems is imperative to the financial integrity of the Tollway. Recurring support and maintenance requirements include:

a. Monthly security patch/upgrade review. Implementation of security patches and/or upgrades occur as needed (which is typically once per quarter). This is necessary for PCI and PII security compliance.

b. Test and implement minor system updates. This work takes place when additional tolling lanes are opened and when new interoperable partners are onboarded. This is necessary to remain in compliance with the Interoperability/Intergovernmental Agreement.

c. Test and implement minor support requests (e.g., year-end reporting). This happens as needed throughout the year.

d. Conduct monthly status meetings of the Host System and the Violation Process System (and its associated Customer Service Center System).

e. Provide monthly reports of the Host System and the Violation Process System (and its associated Customer Service Center System).

f. Provide annual software license renewal paperwork and processing.