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.
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 H), 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 Measure Grantee will adhere to the performance measures requirements documented in
Performance Measures The System Agency will monitor the Grantee’s performance of the requirements in Attachment A and compliance with the Contract’s terms and conditions.
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.
Performance Measurement The Uniform Guidance requires completion of OMB-approved standard information collection forms (the PPR). The form focuses on outcomes, as related to the Federal Award Performance Goals that awarding Federal agencies are required to detail in the Awards.
Review of Performance The Board of Directors shall periodically review and evaluate the performance of Employee under this Employment Agreement with Employee.
Standard of Performance Consultant represents and warrants that it has the qualifications, experience and facilities necessary to properly perform the services required under this Agreement in a thorough, competent and professional manner. Consultant shall at all times faithfully, competently and to the best of its ability, experience and talent, perform all services described herein. In meeting its obligations under this Agreement, Consultant shall employ, at a minimum, generally accepted standards and practices utilized by persons engaged in providing services similar to those required of Consultant under this Agreement.
Appropriation of Performance Security (i) Upon occurrence of a Contractor’s Default, the Authority shall, without prejudice to its other rights and remedies hereunder or in law, be entitled to encash and appropriate the relevant amounts from the Performance Security as Damages for such Contractor’s Default. (ii) Upon such encashment and appropriation from the Performance Security, the Contractor shall, within 30 (thirty) days thereof, replenish, in case of partial appropriation, to its original level the Performance Security, and in case of appropriation of the entire Performance Security provide a fresh Performance Security, as the case may be, and the Contractor shall, within the time so granted, replenish or furnish fresh Performance Security as aforesaid failing which the Authority shall be entitled to terminate the Agreement in accordance with Article 23. Upon replenishment or furnishing of a fresh Performance Security, as the case may be, as aforesaid, the Contractor shall be entitled to an additional Cure Period of 30 (thirty) days for remedying the Contractor’s Default, and in the event of the Contractor not curing its default within such Cure Period, the Authority shall be entitled to encash and appropriate such Performance Security as Damages, and to terminate this Agreement in accordance with Article 23.
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.