DELIVERY OR PERFORMANCE SCHEDULE Clause Samples

DELIVERY OR PERFORMANCE SCHEDULE. The Subcontractor shall furnish, deliver, and perform the Project, commencing as of the date of this Agreement and continuing through, _ for which period funds will be available under the Federal Aid Agreement. This Agreement may be extended with the consent of both parties made in writing, subject to extension of the Federal Aid Agreement if necessary.
View SourceView Similar (7)
DELIVERY OR PERFORMANCE SCHEDULE. (a) Time is of the essence with respect to completion and/or fulfillment of the Purchase Order. (b) Supplier shall deliver the Goods to and/or perform the Services at the designated delivery point no later than the Delivery Date, unless the Delivery Date or Delivery address is altered by the Company and is agreed upon in writing with the Supplier. (c) The Company shall not be obliged to accept any Goods and/or Services in excess of the quantity specified in the Purchase Order. (d) The Company may terminate the Purchase Order for any nonconformity in any Goods supplied and/or Services performed hereunder, including, without limitation, failure of Supplier to supply Goods and/or to perform Services when due or deficient, defective or incomplete performance of Goods and/or Services. (e) Supplier shall promptly advise the Company of any delay or anticipated delay in delivery or performance and shall pay the Company for any losses sustained or costs incurred by the Company as a result of a late delivery or performance. (f) Supplier shall not, without the Company’s prior written consent, manufacture or procure materials in advance of Supplier’s normal flow time or supply Goods and/or to perform Services in advance of schedule. In the event of termination of the Purchase Order, no claim by Supplier will be allowed for any such manufacture or procurement or delivery of Goods and/or performance of Services in advance of such normal flow time without the prior written consent of the Company. (g) The Supplier shall, at the Supplier’s cost, replace any Goods lost or damaged in transit, howsoever caused. (h) The Supplier shall ensure that the Goods are packaged as per the instructions in the Purchase Order. In the event that there are no instructions in the Purchase Order, the Supplier shall meet the packaging standards as is customary in the industry so as to ensure adequate protection for Goods and eliminate damage. (i) If applicable, Delivery shall not be deemed completed until instruction and assembly manuals, drawings, signed off samples or prototypes required to be supplied in terms of the Purchase Order have been delivered to and accepted by the Company in writing. (j) The Supplier warrants and represents that whilst at any Company site or premises, the Supplier shall and shall ensure that its employees, agents, sub-contractors and/or representatives shall comply with the Occupational Health and Safety Act No. 85 of 1993 and any Company health and safety policie...
View SourceView Similar (2)
DELIVERY OR PERFORMANCE SCHEDULE. (a) Time is of the essence with respect to completion and/or fulfillment of the Purchase Order. (b) Supplier shall deliver the Goods to and/or perform the Services at the designated delivery point no later than the
View Source
DELIVERY OR PERFORMANCE SCHEDULE. 3.1 The Subcontractor shall furnish and deliver the material and/or perform the services required by Exhibit A, Statement of Work. 3.2 The period of performance under this Agreement is specified as May 15, 1998 through February 28, 1999, for which period funds are available and allotted.
View Source

Related to DELIVERY OR PERFORMANCE SCHEDULE

  • Performance Schedule The Parties will perform their respective responsibilities in accordance with the Performance Schedule. By executing this Agreement, Customer authorizes Motorola to proceed with contract performance.

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

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

  • 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 ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/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.