Costs of implementing amendments to a System Wide Requirement. (a) The Operator must use all reasonable endeavours to minimise the Net Financial Effect on the Operator of any proposed amendments to a System Wide Requirement.
Costs of implementing amendments to a System Wide Requirement Sample Clauses
Related to Costs of implementing amendments to a System Wide Requirement
AMENDMENTS TO SERVICE AGREEMENT With effect from the date of this Deed the Parties agree that the Service Agreement is varied so that:
Monitoring Compliance with Contract For purposes of monitoring the District’s compliance with this contract, the Department may require the District to provide information or may conduct site visits as needed.
Implementation of and Reporting on the Project A. The Grantee shall implement and complete the Project in accordance with Exhibit A and with the plans and specifications contained in its Grant Application, which is on file with the State and is incorporated by reference. Modification of the Project shall require prior written approval of the State.
Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .
Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.
Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).
Uncontrollable Forces Tariff Provisions Section 14.1 of the CAISO Tariff shall be incorporated by reference into this Agreement except that all references in Section 14.1 of the CAISO Tariff to Market Participants shall be read as a reference to the Participating Generator and references to the CAISO Tariff shall be read as references to this Agreement.
General Program Requirements Subrecipient shall adhere, but not be limited to, the following requirements for all programs:
Trunking Requirements 7.2.2.9.1 The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards.
Additional Requirements for Sleeping Rooms The Contractor shall provide departing Attendees a secured area for storing belongings.
