24-0082 Oral Presentation Agenda_Traffic Incident Management System_TIMS.docx
DOCX document 39 KB Posted
- Solicitation number
- 24-557THA-INFOT-B-50038
- Issued by
- Illinois
About this file
This is an Oral Presentation Agenda for RFP 24-0082 Traffic Incident Management System (TIMS) issued by the Illinois Tollway. The presentation will be held at Central Administration located at 2700 Ogden Ave. Downers Grove, IL 60515, with the specific room number and date to be determined. Selected vendors participating in Phase II Technical Analysis are required to demonstrate all content via live Teams meeting, with 30 minutes allocated for setup of slides and media prior to the 255-minute presentation that includes both demonstration and question-and-answer session. The presentation must be conducted primarily by the proposed Project Manager who will represent the vendor during implementation. The Tollway seeks a qualified Third-Party Administrator to provide a comprehensive Traffic Incident Management System, with all vendor questions to be submitted via email to the Information Contact no later than 1:00 pm on 7/16/2026.
The agenda specifies nine major demonstration areas totaling 545 possible evaluation points: Roles/Privileges (30 points, 10 minutes), Admin Functions and Login Access (40 points, 15 minutes), Events/CAD Bridge (100 points, 40 minutes), Interfaces (200 points, 40 minutes), Queue Detection/Flasher Activation (10 points, 10 minutes), Video Functionality (100 points, 60 minutes), TIMS2GO mobile application (30 points, 15 minutes), Reporting (15 points, 10 minutes), and Technical Support (20 points, 15 minutes). Vendors must demonstrate capabilities including CAD system integration, multi-factor authentication, SAML and SSO integration with Okta, real-time video management with pan-tilt-zoom functionality, mobile app operations, traffic data integration from multiple sources, queue detection automation with Sensys sensors, and comprehensive reporting and archival functions. Vendors are explicitly instructed not to mention any pricing information during presentations, as the pricing portion of the RFP has not been opened or reviewed, and should not demonstrate any third-party software or add-ons not included in their proposal unless specifically directed.
View the file
Other files
Show all 21
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
AGENDA
24-0082 Traffic Incident Management System (TIMS) Presentation Date: TBD Location: Central Administration 2700 Ogden Ave.
| Downers Grove IL 60515 |
| Room # TBD |
The Tollway will allow 30 minutes for set up of slides and/or media prior to the presentation start time. Followed by a maximum of 255 minutes (presentation and minutes of Q&A).
REMINDER: PLEASE DO NOT MENTION ANY PRICING AS THE PRICING PORTION OF THIS RFP HAS NOT BEEN OPENED/REVIEWED.
This document provides presentation instructions for vendors selected to participate in the Phase II Technical Analysis for RFP 24-0082 Traffic Incident Management System (TIMS). Vendors must demonstrate all content via a live Teams meeting. The proposed PM should be the primary presenter.
Vendors should not demonstrate any tools, third-party software or add-ons not included in their proposal and price proposal unless specifically directed to do so within these instructions.
A. Presentation Schedule: (approximate durations)
| Item# |
| Description |
| Points |
| Duration |
| 1 |
| Introductions |
| 2 |
| Roles/Privileges |
| 30 |
| 10 |
| 3 |
| Admin Functions and Login Access |
| 40 |
| 15 |
| 4 |
| Events/CAD Bridge |
| 100 |
| 40 |
| 5 |
| Interfaces |
| 200 |
| 40 |
| 6 |
| Queue Detection/Flasher Activation |
| 10 |
| 10 |
| 7 |
| Break |
| 8 |
| Video Functionality |
| 100 |
| 60 |
| 9 |
| TIMS2GO |
| 30 |
| 15 |
| 10 |
| Reporting |
| 15 |
| 10 |
| 11 |
| Technical |
| 20 |
| 15 |
| 12 |
| Q&A |
| Total |
| 545 |
| 255 |
B. Vendor Introductions:
Please take a moment to introduce your company to the evaluation committee. Specific points to include in your introduction are detailed below.
· Presentations should be conducted primarily by the project manager who intends to represent your company during implementation,
· Discuss or introduce other key staff who will facilitate in the presentation.
C. Presentation Instructions:
Traffic Management System – Oral Presentation (duration two hundred fifty five (250) minutes)
| No. |
| RFP Requirement |
| Questions the Vendor needs to answer in the presentation |
| 1. |
| Roles/Privileges |
POSSIBLE POINTS: 30
ALLOTED TIME: 10 minutes
Demonstrate the following scenario regarding Role and Privilege management:
1. Creation of test accounts.
2. Creation of various roles to access different parts of the system.
3. Assignment of the new roles to the test accounts.
4. Demonstrate having different permissions for different functionalities.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 2. |
| Admin Functions and Login Access |
POSSIBLE POINTS: 40
ALLOTED TIME: 15 minutes
Present an overview of the following:
1. Ability to access the application.
2. Demonstrate how the Tollway can control the password rules.
3. Demonstrate the creation of an Admin user who can manage the user rights/user groups/access of the groups.
4. Ability to use Active Directory for user authentication.
5. Multi-Factor Authentication (MFA).
6. Okta.
7. Demonstrate SAML integration.
8. Demonstrate how SSO is set up with OKTA.
9. Ability to set permissions for recording access per user.
10. Ability to set user-specific permissions for camera and destination access for video.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 3. |
| Events/CAD Bridge |
POSSIBLE POINTS: 100
ALLOTED TIME: 40 minutes
Demonstrate the following scenario regarding the Events and CAD Bridge functions:
1. Demonstrate connection to a CAD system and functionality that allows filtering of events based on nature from CAD.
2. Explain how sensitive law enforcement information will be filtered from becoming an event note in TIMS.
3. Demonstrate the ability to filter which event types are displayed in TIMS.
4. Demonstrate the creation of events originating from CAD and mapping from CAD nature codes to specific event types in TIMS and vice versa.
5. Demonstrate how events are created that do not originate from an outside source, such as CAD.
6. Demonstrate the response plan generation and activation (DMS, email, Twitter, RTIS, Waze, text messaging).
7. Ability to download lane closure information and create events.
8. Ability to auto-generate events from other main processes such as Waze, wrong-way driver, etc.
9. Demonstrate the ability to differentiate between Active Traffic Management (ATM) vs non-ATM events and applicable response plans.
10. Ability to link and/or associate events.
11. Ability to resurrect terminated events.
12. Show the ability to map events on a map user interface.
13. Show ability to recommend ITS devices (DMS, camera, etc.) based on event location and severity.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 4. |
| Interfaces |
POSSIBLE POINTS: 200
ALLOTED TIME: 40 minutes
Demonstrate the following via a scenario regarding interfaces:
1. Demonstrate ability to pull asset information from Cartegraph or similar asset inventory software.
2. Demonstrate using information for devices and event mapping.
3. Demonstrate using information from Cartegraph to create and display trouble ticket information.
4. Demonstrate the ability to show real-time diagnostics for devices via the applicable user interface, as well as an alarm.
5. Demonstrate the ability to pull traffic data from third-party vendors (iPass, Inrix, Bluetooth, etc.) to use for travel time and queue information.
6. Ability to pull data from Tollway-owned vehicle detection system (VDS) including Sensys, RTMS, and any other applicable sensors.
7. Ability to pull AVL data from the vendor and display it in a searchable table and on a map layer.
8. Ability to provide authorized outside agencies, such as media outlets, DOTs, and first responders, with TIMS access.
9. Demonstrate adding new DMS to the system and show automated travel time target logic based on location.
10. Ability to post and retrieve DMS messages using NTCIP, including using color and graphics. Allow management via the user interface.
11. Demonstrate the method of storing saved messages and response plans in a retrievable library of messages and associated signs.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 5. |
| Queue Detection/Flasher Activation |
POSSIBLE POINTS: 10
Demonstrate the following via a scenario regarding Queue Detection/Flasher Activations:
1. Demonstrate the manual control of the queue flashers.
2. Demonstrate automated queue detection and explain the types of detectors that have been used in the past for queue detection. The Tollway currently uses the following Sensys models:
· VSN240-F-2 (last generation In-Pavement sensor)
· VSN240-F-3 (current generation In-Pavement sensor)
· VSN240-CUP-3 (Cup/Sleeve for VSN240-F-3)
· AP240-E (Access Point).
3. Demonstrate automatic activation of queue flashers and/or DMS response plan.
4. Demonstrate the ability to set the timer for the deactivation of flashers manually.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 6. |
| Video Functionality |
POSSIBLE POINTS: 100
ALLOTED TIME: 60 minutes
Demonstrate the following via a scenario regarding Video Functionality:
1. Demonstrate the ability to Pan, Tilt, Zoom, Focus, and reboot cameras.
2. Demonstrate the functionality that allows for tracking camera configuration, including IP address and camera make and model, etc.
3. Ability to set and override park positions and set preset positions.
4. Ability to partition cameras by roadway and camera device state.
5. Ability to sort/filter cameras by location characteristics.
6. Ability to route video to any authorized destination.
7. Ability to record, view, and store routed videos automatically.
8. Allow the ability to schedule manual recordings of cameras regardless of the current viewing status.
9. Ability to export stored video.
10. Ability to integrate ATMS with video wall (currently Activu).
11. Ability to create and play customizable video tours.
12. Ability to display real-time device diagnostics for cameras, including operational and recording status.
13. An interface that allows for the recognition of layouts and allows for the routing of video to multiple destinations.
14. Ability to collect and publish snapshots from selected cameras, as well as pause scheduled snapshots.
15. Ability to block video and lock PTZ for media users.
16. Ability to export current camera inventory to external data sources, including a spreadsheet.
17. Perform video analytics for wrong-way drivers, stall, roadway departure, and debris, etc., detection, including methodology for showing alerts.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 7. |
| TIMS2GO |
POSSIBLE POINTS: 30
Demonstrate the following via a scenario regarding TIMS2GO (mobile app):
1. Provide an overview of your mobile-supported environment for the following:
a. Discuss the recommended mobile devices and OS for phones and tablets.
b. Clarify if the solution is a native app, web app or hybrid.
c. Present the performance limitations for each device type.
2. Demonstrate the user access and session control, including user login workflow, authentication method (SSO, etc.), Session persistence, timeout settings and logout procedure.
3. Demonstrate the operational map awareness within the mobile app by showing: the main map interface upon login, the live display of the roadway assets/events, layer controls (events, devices, vehicles, etc.), and how to zoom/pan the cameras and their responsiveness.
4. Demonstrate the capabilities of Event & Incident interactions using the following as an example: how a user identifies an incident/event, show the event detail view, what key operational data is visible to the field users, and the ability to add/display notes and the status availability.
5. Demonstrate the device and resource visibility for the following: viewing/responding to ITS devices or resources, differentiation of device states, vehicle/AVL/resource visibility, and the ability to quickly interpret system status.
6. Demonstrate Roadway/Geographic Filtering for the following:
a. Filtering by roadway/route/area,
b. Impact of filtering on the map and lists, and
c. Ease of switching views.
7. Discuss the following regarding the mobile app:
a. Expected latency characteristics,
b. Behavior under degraded connectivity,
c. Data refresh model, and
d. Known constraints or dependencies.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 8. |
| Reporting |
POSSIBLE POINTS: 15
Demonstrate the following via a scenario regarding Reporting:
1. Archive all events, DMS messages, travel time data, GPS, VDS data, list of exported videos, emails, user performance, including logins, breaks, event interactions, etc.
2. Show the ability to report on all archived data in a data visualization and dashboards.
3. Retrieve, archive, and generate and disseminate alarm alerts for device and/or main processes.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
| 9. |
| Technical Support: |
POSSIBLE POINTS: 20
1. Present the structure of onsite vs remote support.
2. Provide an overview of how to troubleshoot performance issues within the system. Review the tools, interfaces, and logs that are available for handling problems.
3. Provide the details on how system restoration and point-in-time recovery are applied to an environment in case of data recovery needs.
4. Provide an overview of the setup of log shipping options to systems, like Splunk.
5. Provide an overview of maintenance tasks expected to be handled by the IT staff or end users of the system, including, but not limited to, any database maintenance, backups, log purging, indexing, etc.
Tollway reserves the right to request clarification or additional details to describe further any demo items listed in this section.
File details come from the government source that posted it. Updated .