RATMS Operational Scenarios Sample Clauses

RATMS Operational Scenarios. 3.4.1 RATMS and associated devices will be operated and maintained by the RATMS operators. They will be responsible for maintaining the communications system down to the edge of the Ethernet switch that serves as a point of connection for traffic controllers and other roadside equipment. 3.4.2 RATMS operators will maintain bluetooth readers, dynamic message sign (DMS), Microwave Vehicle Detection System (MVDS) units, CCTV Cameras, Road Weather Information Systems (RWIS), network devices, surge protective devices, and other equipment associated with the RATMS. Day-to-day operations and maintenance of RATMS will include several common RATMS operational scenarios. While the RATMS will be capable of operating and managing the region’s traffic signal system on 24-hours a day, 7-days a week, initial core hours of operation are expected to be Monday through Friday from 8:00 a.m. to 5:00 p.m. Hours and shifts for RATMS operators can fall outside of these core hours so that there is coverage during morning and evening traffic peaks and special events. As the scope and responsibility of the RATMS and RTMC increases, additional staff can be added into overlapping shifts that provides coverage from 6:00 a.m. to 7:00 p.m. and beyond. In all cases, on- call staffing will be required to respond to emergencies and special events outside of normal business hours, such as major airshows held at area beaches and military installations and other significant tourist events.
View SourceView Similar (3)

Related to RATMS Operational Scenarios

  • Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including RTU for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG shall immediately after each synchronization/tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Operational Support Systems 14.1 BellSouth has developed and made available electronic interfaces by which Unity Acquisition may submit LSRs electronically. 14.2 LSRs submitted by means of one of these electronic interfaces will incur an OSS electronic ordering charge. An individual LSR will be identified for billing purposes by its Purchase Order Number (PON). LSRs submitted by means other than one of these interactive interfaces (mail, fax, courier, etc.) will incur a manual order charge. All OSS charges are specified in Exhibit A of this Attachment.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.