Effect on Performance Sample Clauses

Effect on Performance. Neither Party shall be liable in any manner for any delays or failures in its performance under this Agreement as and to the extent (i) such failures or delays are substantially caused by conditions or events of Force Majeure, and (ii) the conditions of Section 11.1(D)(1) (Satisfaction of Certain Conditions) are satisfied. Except as otherwise expressly provided for in this Agreement, the existence of an event of Force Majeure shall not relieve the Parties of their obligations under this Agreement to the extent that performance of such obligations is not precluded by the event of Force Majeure.
Sample 1
AutoNDA by SimpleDocs
Effect on Performance. This agreement is a basic agreement with no legally binding force, concluded in order for the Company to give consideration to inheriting the relevant business. At this point, there has been no decision to inherit the relevant business.
Sample 1
Effect on Performance. The Arbitrator shall have authority to extend Delivery Dates or Acceptance Dates only to the extent that matters are in dispute that adversely impact any party's ability to deliver or accept the relevant Release. Both parties shall be obligated to continue to perform unless and until the Arbitrator rules that they are not obligated to do so. Failure to perform without such a ruling by the Arbitrator shall be at the risk of the non-performing party. If the Arbitrator recognizes or permits a delay caused by escalation or arbitration which affects the development process, the Release Delivery Dates shall be extended for the period of such delay. If the Arbitrator recognizes or permits such a delay which affects Acceptance Testing, the Partnership shall segregate the disputed issue and continue with all other Acceptance Testing, including Regression Testing, to the extent practicable. If such segregation is not practicable, the Arbitrator shall determine the amount of necessary delay in the Acceptance Dates set forth in Paragraph 13(a). The parties mutually agree that any such delay should be kept to a minimum.
Sample 1
Effect on Performance. In the event Tenant shall be delayed, hindered, or prevented from the performance of any act required under this Lease, by reason of war, civil commotion, acts of God, governmental restrictions, or any other causes beyond its reasonable control, the performance of such act shall be excused for the period of delay, and the period for the performance of any such act shall be extended for the period necessary to complete performance after the end of the period of such delay. The party claiming such delay shall advise the other party in writing as soon as the cause for the delay is reasonably known to it, and such notice shall estimate the period of the delay.
Sample 1
Effect on Performance. In the event Vendor believes that such change in terms required due to a changed funding source will have a material effect on Vendor’s performance of its obligations under the Agreement and will cause Vendor substantial economic hardship, the Vendor may notify the PBC, if at all, within thirty (30) days of the date of the PBC’s notice of such change, and request the PBC to review the Agreement. Upon such request, if the Director of Procurement in his or her sole discretion agrees that Vendor will suffer substantial economic hardship, the PBC may elect to (i) change the funding source or otherwise modify or exempt Vendor from the application of the requirement at issue (if possible), (ii) provide equitable adjustment in the Agreement for only the effect of the changes due to the changed funding source, or (iii) terminate the Agreement.
Sample 1
Effect on Performance. Unless directed otherwise in writing, Contractor shall not cease or delay performance of its obligations under this Agreement during the existence of any dispute or the pendency of any proceeding to resolve it, and Owner shall pay to Contractor all amounts owing and not subject to dispute or offset.
Sample 1
Effect on Performance. Neither Party will be liable for any failure to fulfill any term or condition of this Agreement, nor will such failure constitute a breach of or default under this Agreement, if fulfillment has been delayed, hindered or prevented by an event of force majeure, including, without limitation, any war, riot, strike, lock-out or other industrial dispute, acts of the elements, acts of any government or agency hereof (including the enactment of any new laws, rules or regulations), sabotage or industrial accident, plant breakdown or failure of equipment, inability to obtain equipment, fuel, power, materials or transportation, or by any similar circumstances beyond its reasonable control.
Sample 1
AutoNDA by SimpleDocs

Related to Effect on Performance

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

  • Prompt Performance All actions required to be taken (including payments) by any party under this Agreement shall be performed within the time prescribed for performance in this Agreement, or if no period is prescribed, such actions shall be performed promptly.

  • Substantial Performance This Contract shall be deemed to be substantially performed only when fully performed according to its terms and conditions and any written amendments or supplements.

  • Continuing Performance (a) The obligations under this Agreement continue until satisfied in full and do not merge with any action performed or document executed by any Party for the purposes of performance of this Agreement. (b) Any representation in this Agreement survives the execution of any document for the purposes of, and continues after, performance of this Agreement. (c) Any indemnity given by any Party under this Agreement: (i) constitutes a liability of that Party separate and independent from any other liability of that Party under this Agreement or any other agreement; and (ii) survives and continues after performance of this Agreement.

  • EVALUATING PERFORMANCE 7.1 The Performance Plan (Annexure A) to this Agreement sets out: 7.1.1 the standards and procedures for evaluating the Employee’s perfor- xxxxx; and 7.1.2 the intervals for the evaluation of the Employee’s performance. 7.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force. 7.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames. 7.4 The Employee’s performance will measured in terms of contributions to the goals and strategies set out in the Employer’s IDP. 7.5 The annual performance appraisal will involve: 7.5.1. Assessment of the achievement of results as outlined in the perfor- xxxxx plan: (a) Each KPA should be assessed according to the extent to which the specified standards or performance indicators have been met and with due regard to ad hoc tasks that had to be performed under the KPA. (b) An indicative rating on the five-point scale should be provided for each KPA. (c) The applicable assessment rating calculator (refer to paragraph 7.5.3. below) must then be used to add the scores and calculate a final KPA score.

  • 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: 6.1.1 any failure or delay by the Customer to perform any of the Customer’s obligations under this Agreement; 6.1.2 any act or omission other than on the part of a BT Affiliate or a subcontractor or supplier appointed by it unless that BT Affiliate, subcontractor or supplier has invoked their force majeure rights under their contract with BT; or 6.1.3 Applicable Law, a court order, an application for interlocutory relief or injunction restricting or preventing BT from supplying a Service.

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

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

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

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