Performance Measures and Financial Consequences Sample Clauses

Performance Measures and Financial Consequences. See Attachment A, Section B, for the specific performance measures and financial consequences that apply to this contract.
AutoNDA by SimpleDocs
Performance Measures and Financial Consequences. All deliverables and related tasks must be completed 100% as specified. Failure to satisfactorily complete or submit a deliverable in the time and manner specified will result in a financial consequence as indicated below:

Related to Performance Measures and Financial Consequences

  • Financial Consequences The Department reserves the right to impose financial consequences when the Contractor fails to comply with the requirements of the Contract. The following financial consequences will apply for the Contractor’s non-performance under the Contract. The Customer and the Contractor may agree to add additional Financial Consequences on an as-needed basis beyond those stated herein to apply to that Customer’s resultant contract or purchase order. The State of Florida reserves the right to withhold payment or implement other appropriate remedies, such as Contract termination or nonrenewal, when the Contractor has failed to comply with the provisions of the Contract. The Contractor and the Department agree that financial consequences for non-performance are an estimate of damages which are difficult to ascertain and are not penalties. The financial consequences below will be paid and received by the Department of Management Services within 30 calendar days from the due date specified by the Department. These financial consequences below are individually assessed for failures over each target period beginning with the first full month or quarter of the Contract performance and every month or quarter, respectively, thereafter. Deliverable Performance Metric Performance Due Date Financial Consequence for Non-Performance Contractor will timely submit completed Quarterly Sales Reports All Quarterly Sales Reports will be submitted timely with the required information Reports are due on or before the 30th calendar day after the close of each State fiscal quarter $250 per Calendar Day late/not received by the Contract Manager Contractor will timely submit completed MFMP Transaction Fee Reports All MFMP Transaction Fee Reports will be submitted timely with the required information Reports are due on or before the 15th calendar day after the close of each month $100 per Calendar Day late/not received by the Contract Manager Failure to timely provide Quarterly Sales Reports, transaction fee reports, or other reports as required will result in the imposition of financial consequences and repeated failures or non- payment of financial consequences owed under this Contract may result in the Contractor being found in default and the termination of the Contract. No favorable action will be considered when Contractor has outstanding Contract Quarterly Sales Reports, MFMP Transaction Fee Reports, or any other documentation owed to the Department or Customer, to include fees / monies, that is required under this Contract.

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

  • Financial Consequences for Nonperformance The State reserves the right to withhold payment or implement other appropriate remedies, such as contract termination or nonrenewal, when the Contractor has failed to perform under or comply with the provisions of this contract. When or if the Contractor fails to perform or comply with provisions of this contract, the Contractor has ten (10) calendar days from receipt of Complaint to Vendor Form (PUR 7017) to comply as instructed within the notice. An amount of $500.00 may be assessed for each day the Contractor is delinquent after the ten (10) day notice period ends, and that amount may be withheld from a Contractor’s invoice. The rights and remedies of the State in this paragraph are not considered penalties and are in addition to any other rights and remedies provided by law.

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

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