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).
Non-Performance The obligation of ECOLOGY to the RECIPIENT is contingent upon satisfactory performance by the RECIPIENT of all of its obligations under this Agreement. In the event the RECIPIENT unjustifiably fails, in the opinion of ECOLOGY, to perform any obligation required of it by this Agreement, ECOLOGY may refuse to pay any further funds, terminate in whole or in part this Agreement, and exercise any other rights under this Agreement. Despite the above, the RECIPIENT shall not be relieved of any liability to ECOLOGY for damages sustained by ECOLOGY and the State of Washington because of any breach of this Agreement by the RECIPIENT. ECOLOGY may withhold payments for the purpose of setoff until such time as the exact amount of damages due ECOLOGY from the RECIPIENT is determined.
Excuse from performance of obligations If the Affected Party is rendered wholly or partially unable to perform its obligations under this Agreement because of a Force Majeure Event, it shall be excused from performance of such of its obligations to the extent it is unable to perform on account of such Force Majeure Event; provided that:
(a) the suspension of performance shall be of no greater scope and of no longer duration than is reasonably required by the Force Majeure Event;
(b) the Affected Party shall make all reasonable efforts to mitigate or limit damage to the other Party arising out of or as a result of the existence or occurrence of such Force Majeure Event and to cure the same with due diligence; and
(c) when the Affected Party is able to resume performance of its obligations under this Agreement, it shall give to the other Party notice to that effect and shall promptly resume performance of its obligations hereunder.
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.
Consequences for Non-Compliance If the Department has reason to believe that the District is not in substantial compliance with one or more of the statutory or regulatory requirements applicable to the District, the Department shall notify the District that it has ninety (90) days after the date of notice to come into compliance. If, at the end of the ninety-day period, the Department finds the District is not substantially in compliance with the applicable statutory or regulatory requirements, meaning that the District has not yet taken the necessary measures to ensure that it meets the applicable legal requirements as soon as practicable, the District may be subject to the interventions specified in sections 00-00-000 through 00-00-000, C.R.S. If the District has failed to comply with the provisions of article 44 of title 22 or article 45 of title 22, the District does not remedy the noncompliance within ninety (90) days and loss of accreditation is required to protect the interests of the students and parents of students enrolled in the District public schools, the Department may recommend to the State Board that the State Board remove the District’s accreditation. If the Department determines that the District has substantially failed to meet requirements specified in this accreditation contract and that immediate action is required to protect the interests of the students and parents of students enrolled in the District’s public schools, the Department may lower the District’s accreditation category.
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.
Certification Regarding Termination of Contract for Non-Compliance (Tex Gov. Code 552.374)
Significant Non-Compliance Under Article 5
Non-Compliance 11.1 The provisions of 31 CFR Part 205.29 and 31 CFR Part 205.30 shall apply in cases of non-compliance with the terms of this Agreement.
Payment of Non-compliance Penalties Subject to Clause (i) above, the Service Provider shall pay the Non-compliance Penalty indicated in the Non-compliance Penalty Certificate within 10 (ten) Business Days of Transnet issuing a valid Tax Invoice to the Service Provider for the amount set out in that certificate. If Transnet does not issue a valid Tax Invoice to the Service Provider for Non-compliance Penalties accrued during any relevant period, those Non-compliance Penalties shall be carried forward to the next period.
