Reliability Run Sample Clauses

Reliability Run. Contractor guarantees that, in no event later than the occurrence of Final Acceptance of the Facility hereunder, the Facility shall have successfully completed the Reliability Run (the "Reliability Guarantee"). Contractor recognizes and acknowledges that in operating the Facility during the Reliability Run Owner will operate the Facility in accordance with the Power Purchase Agreement.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Reliability Run. Contractor shall carry out a Reliability Run to demonstrate the reliable operation of the Power Plant and its Component Units under normal working conditions and under the dispatch control of the power purchaser and grid operator. The test will be recorded per the attached Test Record of the Reliability Run. The Power Plant will be operated during the Reliability Run Period (defined below) and the Reliability Run will be considered successful if during such period there are: o Not more than 5 (five) Outages (as defined below) o Not more than 16 (sixteen) aggregate Outage Hours (as defined below) o No single Outage with a duration greater than 6 (six) Outage Hours o Not more than 2 (two) Plant Shutdowns (as defined below) o Not more than 8 (eight) aggregate Outage Hours due to Plant Shutdowns o No Plant Shutdowns in the last 48 (forty-eight) hours of the Reliability Run Test Period o No second Outage which was caused by the repetition, after rectification, of a failed item of equipment which had caused a prior Outage (D-6) August 14, 2002 EPC Contract - Mokai II, New Zealand Where: -------------------------------------------------------------------------------- Outage = One or more of the Component Units is not operating under the dispatch control of the power purchaser and grid operator as a result of Equipment failure, Work design or construction defects or an occurrence or circumstance within the reasonable control of Contractor ----------------------------- -------------------------------------------------- Outage Hours = The period of time with respect to a particular Outage commencing upon the time that any or all Component Units are not under the dispatch control of the power purchaser and grid operator as a result of Equipment failure, Work design or construction defects or an occurrence or circumstance within the reasonable control of Contractor and ending upon the resumption of normal dispatch control ----------------------------- -------------------------------------------------- Plant Shutdowns = An Outage in which none of the Component Units are under the dispatch control of the power purchaser and grid operator under normal operating conditions ----------------------------- -------------------------------------------------- Reliability Run Period = 14 (fourteen) days plus the aggregate Outage Hours during the Reliability Run (if any) plus any additional hours necessary (if any) so as to not have a Plant Shutdown during the last 48 (forty-eight...
Sample 1
Reliability Run. As a minimum requirement to demonstrate the reliability of the Facility (, the Company shall carry out a reliability run for a period of one hundred and sixty eight (168) hours during which time the Facility shall operate continuously (without interruption) for seventy-two (72) continuous hours at then demonstrated Dependable Capacity. The output during the remaining ninety six (96) hours of the test will be as requested by BPDB in accordance with the Dispatch provisions outlined in Section 9.2 (excluding Section 9.2(a)(iii)) as if such provisions were applicable during the period prior to the Commercial Operations Date. This test shall have been satisfactorily completed if the reliability run continues without interruption (arising out of factors internal to the Facility) for not less than one hundred and sixty eight (168) hours. In the event that the reliability run is interrupted for reasons external to the Facility, the accumulated testing time prior to such interruption shall be deemed acceptable for testing purposes. The Company shall be required to carry out the reliability run only for such remaining period after such interruption ceases and the reliability runs carried out during the period prior to the interruption and the period after the interruption shall be deemed as one continuous period as if such interruption had not occurred.
Sample 1
Reliability Run. As soon as is practicable after the achievement of Provisional Acceptance and for purposes of determining whether the Turnkey Contractor has satisfied the Reliability Guaranty, the Turnkey Contractor, with the assistance and cooperation of the MEP Participants’ operations personnel, shall operate the Facilities in accordance with the requirements of Section 7.3.1 (the “Reliability Run”) to support the operating demands for the Facilities, while simultaneously operating the Facilities in accordance with the Operating Manuals. The Reliability Run shall be conducted with all systems being operated in the automatic mode in accordance with Appendix A. Without limiting the practices which may void the test, the use of nonpermanent systems and equipment, jumpering out of safety interlocks and use of excess operating personnel shall be prohibited during the Reliability Run.
Sample 1
Reliability Run. As a minimum requirement to demonstrate the reliability of the Facility, the Company shall carry out a reliability run for a period of one hundred (100) hours during which time the Facility shall operate continuously for seventy-two (72) continuous hours at the then demonstrated Dependable Capacity. The output during the remaining twenty eight (28) hours of the test will be as requested by BPDB. This test shall have been satisfactorily completed if the reliability run continues without interruption (arising out of factors internal to the Facility) for not less than one hundred (100) hours. In the event that the reliability run is interrupted for reasons external to the Facility, the accumulated testing time prior to such interruption shall be deemed acceptable for testing purposes. The Company shall be required to carry out the reliability run only for such remaining period after such interruption ceases and the reliability runs carried out during the period prior to the interruption and the period after the interruption shall be deemed as one continuous period as if such interruption had not occurred.
Sample 1
Reliability Run. A reliability run for the Early Generation Facility or the Plant as the case may be will be carried out as part of the Commissioning tests. The run will be for a period of thirty (30) days and will include seventy-two (72) continuous hours at one hundred percent (100%) base load (i.
Sample 1

Related to Reliability Run

  • Reliability Reliability targets (Mean Time Between Failures (MTBF)) are defined in the technical specifications as set out in the Contract. Notwithstanding any possible application of penalties relating to reliability defined in the Contract, Goods shall remain covered by the warranty defined in this Article 16 as long as the reliability commitments have not been reached.

  • Quality Service Standards Price Services and the Fund may from time to time agree to certain quality service standards, as well as incentives and penalties with respect to Price Services’ Services hereunder.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (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 Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer 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. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11164 et seq. and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.

  • Infertility Services This plan covers the following services, in accordance with R.I. General Law §27-20-20. • Services for the diagnosis and treatment of infertility if you are:

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!