Liquidated Damages For Failure to meet Performance Outcome and Standard Sample Clauses

Liquidated Damages For Failure to meet Performance Outcome and Standard. The Contractor’s performance under this Contract must meet the Performance Outcome and Standard set forth in Section II., J., 1. If the Contractor fails to meet the Performance Outcome and Standard, the Department will impose Liquidated Damages in the following amounts: Fifteen hundred dollars ($1,500.00) for the Performance and Outcome Standard failed during the quarterly monitoring period. Repeated failure to meet an established Performance Outcome and Standard for a consecutive monitoring period will result in liquidated damages being doubled. The Department may also choose to terminate this Contract in the absence of any extenuating or mitigating circumstances. The determination of the existence of extenuating or mitigating circumstances is within the exclusive discretion of the Department.
AutoNDA by SimpleDocs

Related to Liquidated Damages For Failure to meet Performance Outcome and Standard

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

  • Breach of Contract and Liquidated Damages A. Where OGS determines that the Contractor is not in compliance with the requirements of this Contract, and the Contractor refuses to comply with such requirements, or if it is found to have willfully and intentionally failed to comply with the MWBE participation goals set forth in the Contract, the Contractor shall be obligated to pay liquidated damages to OGS.

  • Excuse for Nonperformance or Delayed Performance Except with respect to defaults of subcontractors, Contractor/Vendor shall not be in default by reason of any failure in performance of this contract in accordance with its terms (including any failure by Contractor/Vendor to make progress in the prosecution of the work hereunder which endangers such performance) if Contractor/Vendor has notified the Commission or designee within 15 days after the cause of the delay and the failure arises out of causes such as: acts of God; acts of the public enemy; acts of the State and any other governmental entity in its sovereign or contractual capacity; fires; floods; epidemics; quarantine restrictions; strikes or other labor disputes; freight embargoes; or unusually severe weather. If the failure to perform is caused by the failure of a subcontractor to perform or to make progress, and if such failure arises out of causes similar to those set forth above, Contractor/Vendor shall not be deemed to be in default, unless the services to be furnished by the subcontractor were reasonably obtainable from other sources in sufficient time to permit Contractor to meet the contract requirements. Upon request of Contractor, the Commission or designee shall ascertain the facts and extent of such failure, and, if such officer determines that any failure to perform was occasioned by any one or more of the excusable causes, and that, but for the excusable cause, Contractor’s progress and performance would have met the terms of the contract, the delivery schedule shall be revised accordingly, subject to the rights of the State under the clause entitled (in fixed-price contracts, “Termination for Convenience,” in cost-reimbursement contracts, “Termination”). (As used in this Paragraph of this clause, the term “subcontractor” means subcontractor at any tier).

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Excuse from Performance The Parties shall be excused from performing their respective obligations hereunder if they are prevented from so performing by reason of floods, earthquakes, other acts of nature, war, civil insurrection, riots, acts of any government (including judicial action), and other similar catastrophic events which are beyond the control of and not the fault of the Party claiming excuse from performance hereunder. Labor unrest, including but not limited to strike, work stoppage or slowdown, sick-out, picketing, or other concerted job action conducted by Contractor's employees or directed at Contractor is not an excuse from performance and Contractor shall be obligated to continue to provide service notwithstanding the occurrence of any or all of such events. The Party claiming excuse from performance shall, within two (2) Business Days after such Party has notice of such cause, give the other Party notice of the facts constituting such cause and asserting its claim to excuse under this Section. If either Party validly exercises its rights under this Section, the Parties hereby waive any claim against each other for any damages sustained thereby. The partial or complete interruption or discontinuance of Contractor's services caused by one or more of the events described in this Section shall not constitute a default by Contractor under this Agreement. Notwithstanding the foregoing, however, if Contractor is excused from performing its obligations hereunder for any of the causes listed in this Section for a period of thirty (30) calendar days or more, the SCWMA shall nevertheless have the right, in its sole discretion, to terminate this Agreement by giving ten (10) calendar days notice to Contractor unless Contractor has demonstrated, by the thirtieth (30th) calendar day, to the satisfaction of the SCWMA that the Contractor will resume services no later than the sixtieth (60th) day following the date service was interrupted or discontinued by Contractor.

  • Contractor’s Performance Warranties Contractor represents and warrants to the State that:

  • Performance Warranty Contractor shall warrant all work under this Contract, taking necessary steps and precautions to perform the work to County’s satisfaction. Contractor shall be responsible for the professional quality, technical assurance, timely completion and coordination of all documentation and other goods/services furnished by the Contractor under this Contract. Contractor shall perform all work diligently, carefully, and in a good and workmanlike manner; shall furnish all necessary labor, supervision, machinery, equipment, materials, and supplies, shall at its sole expense obtain and maintain all permits and licenses required by public authorities, including those of County required in its governmental capacity, in connection with performance of the work. If permitted to subcontract, Contractor shall be fully responsible for all work performed by subcontractors.

  • Performance Delay Time is of the essence in the Vendor’s performance of this Agreement. If at any time it appears to Vendor that it may not meet any of the performance schedules or the scheduled completion date of the services to be performed for any reason, including labor disputes, Vendor shall immediately by verbal means (to be confirmed in writing) notify Customer of the reasons for and the estimated duration of such delay. If requested by Customer, Vendor shall make every effort to avoid or minimize the delay to the maximum extent possible including the expenditure of premium time. Any additional cost caused by these requirements of Customer shall be borne by Vendor, unless the delay in performance arises out of causes beyond the control and without the fault or negligence of Vendor or its subcontractors within the meaning of the Cancellation- Default clause herein. The foregoing requirements are in addition to any of Customer’s other rights and remedies as may be provided by law or this Agreement.

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

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