25-0137_ Attachment A_TRMMP ETC.docx
DOCX document 20 KB Posted
- Solicitation number
- 26-557THA-BUSSY-B-49685
- Issued by
- Illinois
About this file
This document is a Business Rationale Attachment A for a Toll Revenue Management and Maintenance Procurement (TRMMP) contract involving a state or regional tollway organization. The contract covers the maintenance and support of an existing toll transaction and revenue collection system, with a focus on the Host System and legacy Violation Processing System. The project term is anticipated for 2026-2028, involving critical system updates, interoperability improvements, and system maintenance to support approximately $1.6 billion in annual toll and violation revenue collection.
The procurement is structured as a sole economically feasible source procurement, emphasizing continuous system compliance, security, and operational requirements. Key technical initiatives include lane integration to read non-I-PASS transponders, data archiving to meet state mandates, consolidation of aged receivables, and ongoing monthly security patch reviews. The scope involves comprehensive system support, including processing over one billion transactions annually, implementing security upgrades, testing system updates, conducting monthly status meetings, providing monthly reports, and managing annual software license renewals. The primary objectives are to maintain financial integrity, ensure regulatory compliance, and prepare for potential future system migrations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 25-0137_Sole Source Hearing Details Form_TRMMP~1.pdf | ||
| 25-0137_Signed SSJF Part I_ TRMMP ETC~1.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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 ensures the complete and sufficient collection of toll transactions and revenue. This system is made up of various applications and 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.6 billion annually in toll and violation revenue.
2. 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 2026-2028 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. 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: 1200 hours for initial modifications and testing; up to 1800 hours integration/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 2026-2028 will include projects to enable the sunsetting of the legacy systems. Requirements to satisfy this need include:
a. Data archiving and cleanup.
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: 3,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: 2400+ 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.
File details come from the government source that posted it. Updated .