Changes in Performance Sample Clauses

Changes in Performance. All changes in performance of this Agreement shall be described in detail on a change order request form, provided by the City, and which must be authorized in writing by an authorized representative of the City prior to commencing any proposed changes in performance. Contractor shall not be entitled to any additional consideration for changes in performance which were not authorized as contemplated by this section, nor for the correction of any mistakes attributable in any way to Contractor, or its employees, agents, subcontractors, independent contractors, and the like.
Sample 1Sample 2Sample 3See All (11)
AutoNDA by SimpleDocs
Changes in Performance. 2.1. GRANTEE agrees to notify CCCE immediately, in writing, of any change in local law, conditions (including its legal, financial, or technical capacity), or any other event that may adversely affect the GRANTEE’s ability to perform the Project in accordance with the terms of the Agreement. The GRANTEE also agrees to notify CCCE immediately, in writing, of any current or prospective dispute, breach, default, or litigation arising from GRANTEE’s performance under this Agreement that may adversely affect CCCE; and agrees to inform CCCE, also in writing, before naming CCCE as a party to litigation for any reason, in any forum.
Sample 1
Changes in Performance. Charges shall be reduced to the extent that the Exchange performs obligations which are described in the Agreement as being performed by Contractor, as mutually agreed upon by the parties in accordance with Section 11.
Sample 1
Changes in Performance. 2.1. XXXXXXX agrees to notify 3CE immediately, in writing, of any change in local law, conditions (including its legal, financial, or technical capacity), or any other event that may adversely affect the GRANTEE’s ability to perform the Project in accordance with the terms of the Agreement. The GRANTEE also agrees to notify 3CE immediately, in writing, of any current or prospective dispute, breach, default, or litigation arising from GRANTEE’s performance under this Agreement that may adversely affect 3CE; and agrees to inform 3CE, also in writing, before naming 3CE as a party to litigation for any reason, in any forum.
Sample 1

Related to Changes in Performance

  • Delays in Performance a. Neither City nor Consultant shall be considered in default of this Agreement for delays in performance caused by circumstances beyond the reasonable control of the non-performing party. For purposes of this Agreement, such circumstances include but are not limited to, abnormal weather conditions; floods; earthquakes; fire; epidemics; war; riots and other civil disturbances; strikes, lockouts, work slowdowns, and other labor disturbances; sabotage or judicial restraint.

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

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

  • EVALUATING PERFORMANCE 6.1 The Performance Plan (Annexure A) to this Agreement sets out -

  • Service Performance All Services provided by the Agency shall be performed in a diligent, safe, courteous, and timely manner in accordance with this Contract and the Associated federal requirements.

  • Excused Performance 6.1 Notwithstanding the occurrence of a Force Majeure Event, in which case Clause 17 will govern, BT will not be liable for any failure or delay to perform any of its obligations under this Agreement (including any of its obligations to meet any Service Levels) to the extent that BT’s failure or delay in performing arises as a result of:

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