DELIVERY PERFORMANCE FAILURES Sample Clauses

DELIVERY PERFORMANCE FAILURES. Kos shall use Commercially Reasonable Efforts to fulfill orders within the confirmed quantity and within the confirmed date with a deviation of **** days. In the case that Kos does not reach the OTIF targets in paragraph (a) above, Kos shall use all Commercially Reasonable Efforts to fulfill such orders and Merck shall, in addition to any other remedy, be entitled to reduce the Provisional Price of Product for such delivery by ****, which reduction shall not be paid in the process described in Section 5.4(c) (i.e., the deduction will remain reflected in a deduction in the final Transfer Price for such Product).
AutoNDA by SimpleDocs

Related to DELIVERY PERFORMANCE FAILURES

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

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. 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 MFMP or on the Department's website).

  • REGISTRY PERFORMANCE SPECIFICATIONS

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

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

  • Equipment Failures In the event of equipment failures beyond the Administrator's control, the Administrator shall take reasonable and prompt steps to minimize service interruptions but shall have no liability with respect thereto. The Administrator shall develop and maintain a plan for recovery from equipment failures which may include contractual arrangements with appropriate parties making reasonable provision for emergency use of electronic data processing equipment to the extent appropriate equipment is available.

  • Delivery Period The “Delivery Period” shall commence on the Commercial Operation Date and shall continue until midnight on the date that is [number to be inserted] years after the Commercial Operation Date.

  • Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.

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

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