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