Alignment of Performance Measures to Capability Sample Clauses

Alignment of Performance Measures to Capability e-Incide Measure Function 1 Function 2 Function 3 Function 4 PHEP 15.1 • • HPP-PHEP J.2 • •
AutoNDA by SimpleDocs
Alignment of Performance Measures to Capability. Measure Function 1 Function 2 Function 3 Function 4 Function 5 PHEP 12.2 ● ● PHEP 12.5 ● PHEP 12.6 ● PHEP 12.7 PHEP 12.11 ● PHEP 12.14 ● PHEP 12.15 ● *Note: The performance measures for capability 12 use data collected primarily from other CDC sources. Once the data is provided to DSLR, awardees are asked to confirm the data. No templates are provided for capability 12 performance measures because direct self-reporting (i.e., manual entry) of data to DSLR is not required.
Alignment of Performance Measures to Capability. Measure Function 1 Function 2 Function 3 Function 4 PHEP 15.1 • • HPP-PHEP J.2 • •

Related to Alignment of Performance Measures to Capability

  • 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.

  • 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.

  • 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.

  • 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.

  • Performance Measurement Satisfactory performance of this Contract will be measured by:

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