Testing of Metering Equipment Connecting Transmission Owner shall inspect and test all of its Metering Equipment upon installation and at least once every two (2) years thereafter. If requested to do so by NYISO or Developer, Connecting Transmission Owner shall, at Developer’s expense, inspect or test Metering Equipment more frequently than every two (2) years. Connecting Transmission Owner shall give reasonable notice of the time when any inspection or test shall take place, and Developer and NYISO may have representatives present at the test or inspection. If at any time Metering Equipment is found to be inaccurate or defective, it shall be adjusted, repaired or replaced at Developer’s expense, in order to provide accurate metering, unless the inaccuracy or defect is due to Connecting Transmission Owner’s failure to maintain, then Connecting Transmission Owner shall pay. If Metering Equipment fails to register, or if the measurement made by Metering Equipment during a test varies by more than two percent from the measurement made by the standard meter used in the test, Connecting Transmission Owner shall adjust the measurements by correcting all measurements for the period during which Metering Equipment was in error by using Developer’s check meters, if installed. If no such check meters are installed or if the period cannot be reasonably ascertained, the adjustment shall be for the period immediately preceding the test of the Metering Equipment equal to one-half the time from the date of the last previous test of the Metering Equipment. The NYISO shall reserve the right to review all associated metering equipment installation on the Developer’s or Connecting Transmission Owner’s property at any time.
TESTING OF THE BCDR PLAN The Service Provider shall test the BCDR Plan on a regular basis (and in any event not less than once in every Contract Year). Subject to paragraph 6.2, the Purchaser may require the Service Provider to conduct additional tests of some or all aspects of the BCDR Plan at any time where the Purchaser considers it necessary, including where there has been any change to the Services or any underlying business processes, or on the occurrence of any event which may increase the likelihood of the need to implement the BCDR Plan. If the Purchaser requires an additional test of the BCDR Plan, it shall give the Service Provider written notice and the Service Provider shall conduct the test in accordance with the Purchaser's requirements and the relevant provisions of the BCDR Plan. The Service Provider's costs of the additional test shall be borne by the Purchaser unless the BCDR Plan fails the additional test in which case the Service Provider's costs of that failed test shall be borne by the Service Provider. The Service Provider shall undertake and manage testing of the BCDR Plan in full consultation with the Purchaser and shall liaise with the Purchaser in respect of the planning, performance, and review, of each test, and shall comply with the reasonable requirements of the Purchaser in this regard. Each test shall be carried out under the supervision of the Purchaser or its nominee. The Service Provider shall ensure that any use by it or any Sub-contractor of “live” data in such testing is first approved with the Purchaser. Copies of live test data used in any such testing shall be (if so required by the Purchaser) destroyed or returned to the Purchaser on completion of the test. The Service Provider shall, within twenty (20) Working Days of the conclusion of each test, provide to the Purchaser a report setting out: the outcome of the test; any failures in the BCDR Plan (including the BCDR Plan's procedures) revealed by the test; and the Service Provider's proposals for remedying any such failures. Following each test, the Service Provider shall take all measures requested by the Purchaser, (including requests for the re-testing of the BCDR Plan) to remedy any failures in the BCDR Plan and such remedial activity and re-testing shall be completed by the Service Provider, at no additional cost to the Purchaser, by the date reasonably required by the Purchaser and set out in such notice. For the avoidance of doubt, the carrying out of a test of the BCDR Plan (including a test of the BCDR Plan’s procedures) shall not relieve the Service Provider of any of its obligations under this Contract. The Service Provider shall also perform a test of the BCDR Plan in the event of any major reconfiguration of the Services or as otherwise reasonably requested by the Purchaser.
Transmission and Routing of Telephone Exchange Service Traffic PURSUANT TO SECTION 251(c)(2) ............................... 14 4.1
Pre-Operations Meeting PURCHASER shall meet with STATE no later than 30 days from execution of the contract to discuss the Threatened and Endangered Species survey, protection, and planning requirements. Operations Plan. PURCHASER shall prepare an Operations Plan for all operations to be conducted under this contract and submit the plan to STATE at least 5 calendar days prior to commencement of any operation. This plan shall be prepared on a form provided by STATE, and shall be used for all types of operations, including road maintenance, project work, logging, and postharvest requirements. STATE may require an on-site meeting prior to approval of the plan, attended by PURCHASER, subcontractor, and STATE representatives. STATE's approval of the plan must be obtained prior to commencement of any operation, and PURCHASER must comply with this plan. If PURCHASER fails to comply with any of the terms of the plan, including completion dates, STATE may, after giving written notice, suspend PURCHASER's operations until such time as an acceptable alternate plan is submitted by PURCHASER and that alternate plan is accepted by STATE, as provided in Section 29, "Violations, Suspensions, and Cancellation." PURCHASER shall notify STATE whenever operations will be inactive for more than 3 days, and again when operations will be resumed. Upon approval by STATE, the Operations Plan shall automatically be incorporated into, and made part of, this contract. PURCHASER's strict compliance with the Operations Plan, as approved by STATE, is a material condition and covenant of this contract. STATE has prepared the required Forest Practices Act (FPA) "Written Plan" for operations within 100 feet of Type F or Type D streams. Any changes to the plan must have STATE approval. PURCHASER shall comply with all provisions of the Written Plan. Seasonal Restrictions. PURCHASER shall adhere to the following restrictions, unless otherwise approved in writing by STATE:
Reporting of Metered Data and Parameters 7.2.1 The grid connected Solar PV power plants will install necessary equipment for regular monitoring of solar irradiance (including GHI, DHI and solar radiation in the module plane), ambient air temperature, wind speed and other weather parameters and simultaneously for monitoring of the electric power (both DC and AC) generated from the Project.
Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 5.1 Scope of Traffic 13 5.2 Trunk Group Architecture and Traffic Routing 13 5.3 Logical Trunk Groups 13 5.4 End Office Access 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 6.1 Meet-Point Billing Services 14 6.2 Data Format and Data Transfer 14 6.3 Errors or Loss of Access Usage Data 15 6.4 Payment 15 6.5 Additional Limitation of Liability Applicable to Meet-Point Billing Arrangements 16 ARTICLE VII BLV/BLVI TRAFFIC 16
Local Switching Interfaces 4.2.13.1 Newcomm shall order ports and associated interfaces compatible with the services it wishes to provide as listed in Exhibit A. BellSouth shall provide the following local switching interfaces:
Processing of Grievances (a) Shop stewards shall suffer no loss in pay for the time spent processing grievances or attending meetings with the Employer's representative.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
Project Managers; Meetings 10.1 Promptly following the Effective Date, each Party shall designate a Project Manager responsible for coordinating the Party’s Work and shall provide the other Party with a written notice containing the name and contact information of such Project Manager (“Project Manager”). In no event shall any Project Manager be authorized to amend or modify the provisions of this Agreement. Each Party may change its Project Manager, from time to time, by written notice to the other Party.
