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).
Availability of Performance Order If, and to the extent that, a breach of this contract has been caused by a Relevant Force Majeure Event, the Non-affected Party shall not be entitled to a Performance Order except to secure performance by the Affected Party of its obligations under this Clause 17.
Employee Performance Evaluations Any employee performance evaluation shall be prepared by the employee's supervisor who has the responsibility and authority to prepare such reports. Employee performance evaluation reports shall be discussed with the employee prior to finalization of each category of the report. An employee will receive an appointment with his/her department's reviewing officer to discuss the evaluation by signing the evaluation form in the space provided. Each department shall make a reasonable effort to ensure that the reviewing officer for this purpose has not been a party to the preparation of the evaluation. In no case shall the reviewing officer sign the evaluation form until a review has occurred. Any regular or special evaluation with a rating of "unsatisfactory" shall include plans for employee development. Except in cases of termination, release from probation, or leave of absence, employees who receive an unsatisfactory performance evaluation must receive a follow-up evaluation. The follow-up evaluation shall cover a period of time no greater than ninety (90) calendar days from the date of the final review of the initial unsatisfactory evaluation. An employee shall have the right to submit written comments regarding any evaluation and to have such comments included in his/her personnel file along with the evaluation.
EMPLOYEE PERFORMANCE EVALUATION Purpose: To provide the policy and procedures for assessing employee performance and communicating the results of assessment to the employee and to others using assessment information in personnel decisions, and further to express the mutual commitment of the parties to the University’s values.
Evaluation of Performance School, in conjunction with Company personnel, is responsible for and shall make arrangements for evaluating Student’s performance during the clinical program.
Assessment of Performance The assignment of a teacher to a TLS position will be subject to review by the school district’s administration at least annually. The first review must be completed no later than five (5) work days before the beginning of the transfer process. The review shall include peer feedback on the effectiveness of the teacher’s performance of duty specific to the teacher’s TLS position. A teacher who completes an assignment in a TLS position may apply for assignment to a new TLS position.
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.
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).
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.
