Planned Non-Performance Events Sample Clauses

Planned Non-Performance Events. (1) The Participant will be permitted to use Planned Non-Performance Events in accordance with the applicable criteria set out in Sections 7.2(2) and (3), provided that the Participant notifies the OPA in writing of such Planned Non-Performance Event in a form and manner acceptable to the OPA and including the MW reduction from the Baseline in accordance with Exhibit B-1 and the Adjusted Baseline in accordance with Exhibit B-2, if applicable, no later than: (a) a time to be specified by the OPA on the Website with respect to a Single Day Planned Non-Performance Event; and (b) 12:01 a.m. (E.S.T.) on the fifth Business Day prior to the first day of an Extended Period Planned Non-Performance Event. Such notice shall be irrevocable and may not be withdrawn by the Participant once given to the OPA. For greater certainty, a Planned Non-Performance Event must relate to an entire Settlement Account, even though that Settlement Account may in fact be composed of one or more Contributors, some of whom in fact would otherwise have been able to Curtail. (2) The Participant, whether an Aggregator or a Direct Participant, may take one Extended Period Planned Non-Performance Event per Settlement Account per calendar year, for a period up to and including the Extended Period, if the M&V Plan includes a request for such Extended Period together with reasonable evidence in writing satisfactory to the OPA that the Extended Period Planned Non- Performance Event is for the purpose of regularly scheduled maintenance activities and at least 75% of the Participant’s Monthly Contracted MW for that Settlement Account has taken such Extended Period for a Planned Outage in each of the previous two calendar years. If a Planned Non-Performance Event for an Extended Period is used by the Participant and has ended earlier than expected, the Participant shall deliver a notice in writing to the OPA confirming when such Planned Non-Performance Event has ended, but in such circumstance, the Participant shall not be entitled to use as a performance exemption at any subsequent time in the calendar year any days that had not been used in that Extended Period Planned Non-Performance Event. (3) The Participant may take Single Day Planned Non-Performance Events per Settlement Account in a calendar year, on the following basis: (a) a Participant who is an Aggregator may take one Single Day Planned Non-Performance Event per calendar year. In addition, Aggregators may request Single Day Planned Non- ...

Related to Planned Non-Performance Events

  • Non-Performance The obligation of ECOLOGY to the RECIPIENT is contingent upon satisfactory performance by the RECIPIENT of all of its obligations under this Agreement. In the event the RECIPIENT unjustifiably fails, in the opinion of ECOLOGY, to perform any obligation required of it by this Agreement, ECOLOGY may refuse to pay any further funds, terminate in whole or in part this Agreement, and exercise any other rights under this Agreement. Despite the above, the RECIPIENT shall not be relieved of any liability to ECOLOGY for damages sustained by ECOLOGY and the State of Washington because of any breach of this Agreement by the RECIPIENT. ECOLOGY may withhold payments for the purpose of setoff until such time as the exact amount of damages due ECOLOGY from the RECIPIENT is determined.

  • Annual Performance Evaluation On either a fiscal year or calendar year basis, (consistently applied from year to year), the Bank shall conduct an annual evaluation of Executive’s performance. The annual performance evaluation proceedings shall be included in the minutes of the Board meeting that next follows such annual performance review.

  • Performance Adjustment One-twelfth of the annual Performance Adjustment Rate will be applied to the average of the net assets of the Portfolio (computed in the manner set forth in the Fund's Declaration of Trust or other organizational document) determined as of the close of business on each business day throughout the month and the performance period.

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Historical Performance Information To the extent agreed upon by the parties, the Sub-Advisor will provide the Trust with historical performance information on similarly managed investment companies or for other accounts to be included in the Prospectus or for any other uses permitted by applicable law.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit G), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • Performance Evaluations Employee performance shall be evaluated and communicated on a yearly basis as required under County policy. Performance evaluations are used to demonstrate to employees that they are valued; record how an employee’s performance meet the requirements of the job; create a job history record; identify employee strengths and areas for enhancement; assist the employee and supervisor in an effort to attain the highest level of performance; and reinforce performance standards. Every effort will be made to include substantiated information within an employee’s performance evaluation. Non-recurring discipline history which is more than two (2) years old will not be referenced in performance evaluations. The County shall ensure employee performance evaluations are conducted in accordance with County and departmental policy. Performance evaluations and disciplinary matters shall only be conducted by County employees. When an employee who does not agree with the overall rating he/she receives on his/her written performance evaluation, he/she shall discuss and attempt to resolve the differences with his/her immediate supervisor. If discussion with his/her immediate supervisor does not result in resolution of the differences, the employee may file a written request to meet with the next level of management. Said request shall state the unresolved issues and the specific changes in the written performance evaluation the employee is seeking. The appropriate manager shall meet with the employee to discuss the unresolved issues. If the issues are not resolved to the employee’s satisfaction following discussion with the appropriate manager, the employee may within thirty (30) working days file a written request for a meeting with the department head. Within fourteen (14) working days of receipt of a written request stating the unresolved issues and the desired changes in the written performance evaluation, the department head shall meet with the employee to discuss the issues. Within ten (10) working days of said meeting, the department head shall respond in writing to the employee. The decision of the Department Head shall be final and not subject to the grievance procedure. An employee may submit a written response to his/her evaluation that shall be placed in his/her personnel file.

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

  • Performance Excused The Affected Party, to the extent rendered unable to perform its obligations or part thereof under this Agreement as a consequence of the Force Majeure Event shall be excused from performance of the obligations. Provided that, the excuse from performance shall be of no greater scope and of no longer duration than is reasonably warranted by the Force Majeure Event. Provided further, nothing contained herein shall absolve the Affected Party from any payment obligations accrued prior to the occurrence of the underlying Force Majeure Event.

  • Quarterly Contractor Performance Reporting Customers shall complete a Contractor Performance Survey (Exhibit I) for each Contractor on a Quarterly basis. Customers will electronically submit the completed Contractor Performance Survey(s) to the Department Contract Manager no later than the due date indicated in Contract Exhibit D, Section 17, Additional Special Contract Conditions. The completed Contractor Performance Survey(s) will be used by the Department as a performance-reporting tool to measure the performance of Contractors. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MyFloridaMarketPlace or on the Department's website).