Common use of Future Upgrades Clause in Contracts

Future Upgrades. (1) If not currently available, The TXShare Participating Entity will allow functional requirements presented in the following sections of the PRL to be delivered as a future software upgrade, provided the upgrade is provided within two years of the initial software delivery. 2.5.4.1.1 Manage RSU Interface 2.5.4.1.2 Manage RSU Interface Watchdog 2.5.4.2.1 Manage Roadway Geometrics Information 2.5.4.2.2 Manage Movement Configuration for Connected Devices 2.5.4.2.3 Manage Collection of Connected Devices Data 2.5.4.2.4 Monitor Broadcasted MAP Messages 11.16 NTCIP 1211 v02 TXShare Participating Entities are implementing a pilot project to provide Transit Signal Priority (TSP) for buses along specific routes in their respective locales. The Centralized TSP System will collect data from buses and, if certain criteria are met, generate a TSP request that is transmitted to the TXShare Participating Entity’s traffic management system for action. The Centralized TSP system is based on NTCIP 1211 v02. NTCIP 1211 defines the management information base for signal control and prioritization (SCP) systems. It defines individual parameters that represent the configuration, status, and control information that is unique to SCP. Within the standard, NCTIP 1211 defines the following three critical SCP components: • Priority Request Generator (PRG) • Priority Request Server (PRS) • Coordinator (CO) NTCIP 1211 defines the primary functions of these components as follows: Priority Request Generator (PRG) • To produce an estimate of the arrival time at the intersection • To produce an estimate of the time for departure from the intersection. • To send a request for signal priority to the Priority Request Server. • To send and receive the status of a priority request from the PRS. Priority Request Server (PRS) • To receive priority requests from the PRG • To send the status of priority requests back to the PRG. • To prioritize multiple priority requests • To exchange service requests with the coordinator. • To exchange status information with the coordinator. Coordinator • To receive service requests from the PRS • To transmit status information back to the PRS • To implement the requested priority strategy Based on the architecture of the Centralized TSP System, the PRS and CO will be located in the local controller.