Monitoring of Performance and Quality
Monitoring of Performance and Quality Sample Clauses
Related to Monitoring of Performance and Quality
Monitoring of Performance Vendor shall continuously monitor and record its performance to ensure that all of Vendor's responsibilities and obligations hereunder are being met and fulfilled. Citizens may conduct programmatic and other administrative contract monitoring during the term of this Agreement. The purpose of this monitoring is to ensure that all of Vendor's responsibilities and obligations are being met and fulfilled. Such monitoring may include on-site visits, report reviews, invoice reviews, compliance reviews, and a review of any other areas reasonably necessary. Vendor acknowledges and agrees that Citizens may also monitor and record Vendor Staff communications to the extent they occur within or are connected to any Citizens’ resource, such as electronic or telecommunications systems.
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.
PERFORMANCE MONITORING AND REPORTING Performance indicators
Monitoring of Contract Performance The Contractor shall comply with the monitoring arrangements set out in the Monitoring Requirements Schedule including, but not limited to, providing such data and information as the Contractor may be required to produce under the Contract.
Assurance of Performance If at any time the COUNTY has good objective cause to believe CONTRACTOR may not be adequately performing its obligations under this Agreement or that CONTRACTOR may fail to complete the Services as required by this Agreement, COUNTY may request from CONTRACTOR prompt written assurances of performance and a written plan acceptable to COUNTY, to correct the observed deficiencies in CONTRACTOR’s performance. CONTRACTOR shall provide such written assurances and written plan within thirty (30) calendar days of its receipt of COUNTY’s request and shall thereafter diligently commence and fully perform such written plan. CONTRACTOR acknowledges and agrees that any failure to provide such written assurances and written plan within the required time is a material breach under this Agreement.
Timing of Payment of Performance When the payment of any obligation or the performance of any covenant, duty or obligation is stated to be due or performance required on a day which is not a Business Day, the date of such payment (other than as described in the definition of Interest Period) or performance shall extend to the immediately succeeding Business Day.
Prohibition of Performance Requirements 1. The provisions of the Agreement on Trade-Related Investment Measures in Annex 1A to the WTO Agreement (TRIMs), which are not specifically mentioned in or modified by this Agreement, shall apply, mutatis mutandis, to this Agreement. 2. Member States shall undertake joint assessment on performance requirements no later than 2 years from the date of entry into force of this Agreement. The aim of such assessment shall include reviewing existing performance requirements and considering the need for additional commitments under this Article.
Limitations of Performance The Custodian shall not be responsible under this Agreement for any failure to perform its duties, and shall not be liable hereunder for any loss or damage in association with such failure to perform, for or in consequence of the following causes:
Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.
Excuse from performance of obligations If the Affected Party is rendered wholly or partially unable to perform its obligations under this Agreement because of a Force Majeure Event, it shall be excused from performance of such of its obligations to the extent it is unable to perform on account of such Force Majeure Event; provided that: (a) the suspension of performance shall be of no greater scope and of no longer duration than is reasonably required by the Force Majeure Event; (b) the Affected Party shall make all reasonable efforts to mitigate or limit damage to the other Party arising out of or as a result of the existence or occurrence of such Force Majeure Event and to cure the same with due diligence; and (c) when the Affected Party is able to resume performance of its obligations under this Agreement, it shall give to the other Party notice to that effect and shall promptly resume performance of its obligations hereunder.
