Applicant Evaluation and Performance Measurement Plan Sample Clauses

Applicant Evaluation and Performance Measurement Plan. Applicants must provide an evaluation and performance measurement plan that demonstrates how the recipient will fulfill the requirements described in the CDC Evaluation and Performance Measurement and Project Description sections of this NOFO. At a minimum, the plan must describe: • How applicant will collect the performance measures, respond to the evaluation questions, and use evaluation findings for continuous program quality improvement. • How key program partners will participate in the evaluation and performance measurement planning processes. • Available data sources, feasibility of collecting appropriate evaluation and performance data, and other relevant data information (e.g., performance measures proposed by the applicant) • Plans for updating the Data Management Plan (DMP), if applicable, for accuracy throughout the lifecycle of the project. The DMP should provide a description of the data that will be produced using these NOFO funds; access to data; data standards ensuring released data have documentation describing methods of collection, what the data represent, and data limitations; and archival and long-term data preservation plans. For more information about CDC’s policy on the DMP, see xxxxx://xxx.xxx.xxx/grants/additionalrequirements/ar-25.html. Where the applicant chooses to, or is expected to, take on specific evaluation studies, they should be directed to: • Describe the type of evaluations (i.e., process, outcome, or both). • Describe key evaluation questions to be addressed by these evaluations. • Describe other information (e.g., measures, data sources). Recipients will be required to submit a more detailed Evaluation and Performance Measurement plan, including a DMP, if applicable, within the first 6 months of award, as described in the Reporting Section of this NOFO. Applicant Evaluation and Performance Measurement Plan will be developed in concert with CDC based on the nature of the event. Companion guidance will be released by CDC with event-specific guidance.
Sample 1Sample 2See All (8)
AutoNDA by SimpleDocs
Applicant Evaluation and Performance Measurement Plan. ‌‌ At the time of application, awardees must include in their project narrative a brief description of how they plan to fulfill the requirements described in the ASPR-CDC Evaluation and Performance Measurement and Project Description sections of this FOA. Awardees also must briefly outline the scope of work, planned activities, and intended outcomes of work performed via subawardee contracts, per domain. This document should be approved by the local jurisdictions whose work it represents. Awardees are required to submit, within the first six months of award, a brief evaluation and performance measurement plan, including a DMP, as described in the Reporting section of this FOA. ASPR and CDC do not require awardees to follow a specific evaluation template and will provide more specific guidance prior to the deadline. ASPR and CDC recommend that awardees develop a five-year evaluation plan that will evaluate interim progress including subawardee and local monitoring annually.‌
Sample 1Sample 2Sample 3See All (5)

Related to Applicant Evaluation and Performance Measurement Plan

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

  • Criteria for Performance Assessment A. A teacher’s performance shall be assessed based on the standards for the teaching profession and the criteria set forth in the evaluation instrument, Appendix E 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).

  • Contractor Performance Evaluations The Contract Administrator will evaluate Contractor’s performance as often as the Contract Administrator deems necessary throughout the term of the contract. This evaluation will be based on criteria including the quality of goods or services, the timeliness of performance, and adherence to applicable laws, including prevailing wage and living wage. City will provide Contractors who receive an unsatisfactory rating with a copy of the evaluation and an opportunity to respond. City may consider final evaluations, including Contractor’s response, in evaluating future proposals and bids for contract award.

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

Time is Money Join Law Insider Premium to draft better contracts faster.