Failure to Meet Performance Requirements Sample Clauses

Failure to Meet Performance Requirements. (a) In the event any of the Operations Tests, the Systems Acceptance Test or the Monthly Operations and Maintenance Reports of ongoing operating performance do not yield results which meet or are better than a Guaranteed Performance Requirement, TSP shall become obligated hereunder to pay Performance Liquidated Damages in the amounts set forth in Exhibit N for any shortfall in performance below the Performance Requirements based upon such test results. (b) TSP’s obligation to pay Performance Liquidated Damages for failure to meet Guaranteed Performance Requirements shall apply from and after the first Revenue Service Date. If TSP becomes obligated to pay Performance Liquidated Damages, such Performance Liquidated Damages shall be due and payable directly to the Joint Board or to such other person as directed by the Joint Board in writing, without notice or demand, on the tenth day of the following month and if not paid when due shall thereafter accrue interest as provided in Section 12.7. The Joint Board may, in its sole discretion, offset such Performance Liquidated Damages against amounts otherwise payable by the Joint Board to the TSP.
AutoNDA by SimpleDocs
Failure to Meet Performance Requirements. (a) In the event any of the Operations Tests, the Systems Acceptance Test or the Monthly Operations and Maintenance Reports of ongoing operating performance do not yield results which meet or are better than a Guaranteed Performance Requirement, TSP shall become obligated hereunder to pay Performance Liquidated Damages in the amounts set forth in Exhibit N for any shortfall in performance below the Performance Requirements based upon such test results. (b) TSP’s obligation to pay Performance Liquidated Damages for failure to meet Guaranteed Performance Requirements shall apply from and after the first Revenue Service Date. If TSP becomes obligated to pay Performance Liquidated Indiana Finance Authority/Joint Board 51. Toll Services Agreement LSIORB Toll Services Project Execution Version Damages, such Performance Liquidated Damages shall be due and payable directly to the Joint Board or to such other person as directed by the Joint Board in writing, without notice or demand, on the tenth day of the following month and if not paid when due shall thereafter accrue interest as provided in Section 12.7. The Joint Board may, in its sole discretion, offset such Performance Liquidated Damages against amounts otherwise payable by the Joint Board to the TSP.
Failure to Meet Performance Requirements. In the event the Licensee fails to meet any of the milestones or performance criteria set forth in Schedule D, or observe and perform the obligations set forth under any of Sections 4.1 or 4.3, such shall constitute a default under this Agreement pursuant to Section 13.2 hereof.
Failure to Meet Performance Requirements. In the event the Licensee fails to meet any of the milestones or performance criteria, or observe and perform the obligations set forth under any of Sections 4.1, including Schedule “D”, 4.2, 4.3 such shall constitute a default under this Agreement and shall entitle the University to terminate this Agreement pursuant to Section 13.2 hereof.

Related to Failure to Meet Performance Requirements

  • Performance Requirements A. There is no guaranteed minimum amount of work which will be ordered under this Contract. B. The total Contract amount will not exceed $4,900,000. C. This is a Contract for work specified in individual Job Orders. Work ordered prior to but not completed by the expiration of the Contract period, and any additional work required as a result of unforeseen conditions encountered during construction up to six (6) months after the contract expiration date, will be completed with all provisions of this Contract still in force. Performance time for each Job Order issued under this Contract will be determined in accordance with the Contract. This performance time will be determined and agreed upon by both Parties for each individual Job Order. Contractor must self-perform 20% of the Work under this Contract for ‘A’ and ‘B’ licenses. Contractor must self-perform 75% of the Work under this Contract, unless otherwise approved by the County, for ‘C’ licenses. D. This is an indefinite-quantity Contract for the supplies or services specified and effective for the period stated. Work or performance shall be made only as authorized by Job Orders issued in accordance with the ordering procedures clause. The Contractor agrees to furnish to the County when and if ordered, the supplies or services specified in the Contract up to and including the quantity designated in the Job Orders issued as the maximum designated in the Contract.

  • 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. 2. Member States shall undertake joint assessment on performance requirements no later than 2 years from the date of entry into force of this Agreement. The aim of such assessment shall include reviewing existing performance requirements and considering the need for additional commitments under this Article.

  • Service Requirements Grantee shall:

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

  • Service Requirement Except as otherwise provided in Section 6(e) of the Plan or Section 2 of this Agreement, this Option may be exercised only while you continue to provide Service to the Company or any Affiliate, and only if you have continuously provided such Service since the Grant Date of this Option.

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

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

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Contractor’s Performance Warranties Contractor represents and warrants to the State that: (i) Each and all of the services shall be performed in a timely, diligent, professional and skillful manner, in accordance with the highest professional or technical standards applicable to such services, by qualified persons with the technical skills, training and experience to perform such services in the planned environment. (ii) Any time software is delivered to the State, whether delivered via electronic media or the internet, no portion of such software or the media upon which it is stored or delivered will have any type of software routine or other element which is designed to facilitate unauthorized access to or intrusion upon; or unrequested disabling or erasure of; or unauthorized interference with the operation of any hardware, software, data or peripheral equipment of or utilized by the State. Without limiting the generality of the foregoing, if the State believes that harmful code may be present in any software delivered hereunder, Contractor will, upon State’s request, provide a new or clean install of the software. Notwithstanding the foregoing, Contractor assumes no responsibility for the State’s negligence or failure to protect data from viruses, or any unintended modification, destruction or disclosure. (iii) To the extent Contractor resells commercial hardware or software it purchased from a third party, Contractor will, to the extent it is legally able to do so, pass through any such third party warranties to the State and will reasonably cooperate in enforcing them. Such warranty pass-through will not relieve the Contractor from Contractor’s warranty obligations set forth herein.

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