Item 17 - Agreement for McFadden Ave. Transit Signal Priority Pilot Project

Home Browse Search

CITY OF SANTA ANA 10 The TSP system shall be cloud-based and hosted online by the system vendor platform. The consultant is responsible for the TSP system on the cloud-hosted platform and is responsible for interfacing with Swiftly or OCTA’s CAD/AVL and traffic signal system. Other than the items noted in the general work overview that is the responsibility of by City of Santa Ana or OCTA, all items needed to support the TSP system will be the responsibility of the consultant. The TSP system shall include functionality to monitor the system and associated equipment, system management and configuration functions, data storage and management, and troubleshooting capabilities from a central location. The system shall provide the functionality to interface with the system from a central location or from the field for maintenance and testing purposes. The TSP system shall interface with Swiftly or OCTA’s CAD/AVL over a secure network connection if the interface is with the central CAD/AVL system. The TSP system shall interface with the traffic signal controllers over a secure network connection at City’s TMC. The TSP system shall provide end-to-end network security and security monitoring functionality. The TSP system shall comply with all network security requirements by City of Santa Ana and OCTA. Subtask 4.2: TSP Cloud Functionality The core functionality of the TSP system is expected to reside in the cloud-hosted application platform. This section outlines the key functions that are expected to be part of the cloud-hosted application. At a minimum, TSP system shall be able to: 1. Monitor TSP Transit Vehicles and Traffic Signals – The TSP system is expected to maintain a continuously updated status of all active TSP-enabled transit vehicles and signals. It is envisioned that a map-based user interface showing real-time system activity could serve this function. 2. Priority Request Generation (PRG) – The TSP system is expected to function as the PRG. As part of the PRG function, the system needs to be able to: 3. Priority Request Server (PRS) – The TSP system is expected to function as the PRS. 4. Manage and Archive Data – The TSP system is expected to collect, store, and disseminate system data for analysis and evaluation. 5. Maintain Reporting and Performance Monitoring System – The TSP system is expected to provide system reporting and performance monitoring information, preferably in a dashboard format as part of the user interface. Performance measures would include items such as: transit vehicle travel time, transit travel time variability, overall TSP requests, TSP requests granted/rejected, TSP request status, traffic signal controller status, TSP action taken by the signal controller, and communications status (latency, uptime, response from controller, response from transit vehicle, etc.). Subtask 4.3: Traffic Signal System The TSP system is expected to send transit signal priority request messages to, and retrieve priority request status messages from, the traffic signal controller at the project signals in the City of Santa Ana using NTCIP communications protocols. The controller functionality in response to the priority request messages will be the responsibility of City. The TSP system shall utilize City’s Econolite 2070 ASC3 or Econolite Cobalt EOS controllers for this purpose.