Developer’s and Vendors’ Obligations & Covenants Sample Clauses

Developer’s and Vendors’ Obligations & Covenants. Subject to the Purchasers making payment of the Total Amount Payable in the manner stipulated in this Agreement, the Developer and the owner hereby agrees:
AutoNDA by SimpleDocs

Related to Developer’s and Vendors’ Obligations & Covenants

  • Licensors Obligations 4.5.1. Xxxxx the Licensee the right to use the intellectual property (the Service) as in the Agreement. Ensure 24/7 availability of the Service, apart from preventive maintenance time. 4.5.2. Keep confidential any information, materials, documents which become available to the Licensee in the course of performance of this Agreement. 4.5.3. Duly publish the official messages (documents) related to the right to use the Service.

  • Vendor’s Obligations Vendor shall incur no further obligations in connection with the terminated work and on the date set in the notice of termination Vendor will stop work to the extent specified. Vendor shall also terminate outstanding orders and subcontracts as they relate to the terminated work. Vendor shall settle the liabilities and claims arising out of the termination of subcontracts and orders connected with the terminated work. The MTC or designee may direct Vendor to assign Vendor’s right, title, and interest under terminated orders or subcontracts to the MTC. Vendor must still complete the work not terminated by the notice of termination and may incur obligations as are necessary to do so.

  • Contractor’s Obligations Pursuant to this contract, the Contractor agrees to provide the specific services detailed herein and shall be responsible for the following:

  • Developer’s Obligations 7.1.1 In consideration of the Rights hereby granted, the Developer shall pay to the Authority an annual fee of Rs. /- (Rupees only) (“Fee”) commencing from the 1st (first) anniversary of Appointed Date. The Fee is exclusive of GST and all other applicable taxes and shall be payable by the Developer at actual over and above the Fee. The Fee is payable to the Authority on or before 30 (thirty) days prior to the start of every year in advance as set out in Schedule 1 throughout the Agreement Period. During the Agreement Period the Fee shall be increased by 5% (five percent) every year over the previous year’s Fee on compounded basis. 7.1.2 The Developer should pay the Fee to the Authority notwithstanding the fact that, the development of Project Facilities is not completed within the specified period or Developer does not start the commercial operation of the Project. In other words, the Developer shall not be entitled to seek any reduction of Fee, claim, damages, compensation or any other consideration from the Authority on account of any reason. 7.1.3 Any delay in payment of the Fee shall attract an interest for the delayed period at the rate of SBI PLR plus 5% per annum on the outstanding amount, which shall be due from the date of such payment till the amount is realized by the Authority. In addition to the foregoing, any delay in payment of Fee beyond a period of 60 (sixty) days from the due date of such payment will be construed to be Material Breach under this Agreement.

  • Processor’s Obligations Except where expressly permitted by Article 28 (3)(a) GDPR, Processor shall process data subjects’ Data only within the scope of the Agreement and the instructions issued by Controller. Where Processor believes that an instruction would be in breach of applicable law, Processor shall notify Controller of such belief without undue delay. Processor shall be entitled to suspend performance on such instruction until Controller confirms or modifies such instruction. Processor shall, within Processor’s scope of responsibility, organize Processor’s internal organization so it satisfies the specific requirements of data protection. Processor shall implement technical and organizational measures to ensure the adequate protection of Controller’s Data, which measures shall fulfil the requirements of the GDPR and specifically its Article 32. Processor shall implement technical and organizational measures and safeguards that ensure ongoing confidentiality, integrity, availability and resilience of processing systems and services and shall implement a process for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for ensuring the security of the processing. Controller is familiar with these technical and organizational measures, and it shall be Controller’s responsibility that such measures ensure a level of security appropriate to the risk. The parties agree to refer to the existing certification of Processor by Kiwa International Cert GmbH in accordance with DIN ISO/IEC 27001:2015 which is considered sufficient evidence for these purposes by Controller and which is available on the website of Processor (xxx.xxxxxxx.xxx). Processor reserves the right to modify the measures and safeguards implemented, provided, however, that that the level of security shall not be less protective than initially agreed upon. Processor shall support Controller, insofar as is agreed upon by the parties, and where possible for Processor, in fulfilling data subjects’ requests and claims, as detailed in chapter III of the GDPR and in fulfilling the obligations enumerated in Articles 33 to 36 GDPR. Processor shall ensure that all employees involved in Contract Processing of Controller’s Data and other such persons as may be involved in Contract Processing within Processor’s scope of responsibility shall only do so within the scope of the instructions. Furthermore, Processor shall ensure that any person entitled to process Data on behalf of Controller has undertaken a commitment to confidentiality under terms similar to the confidentiality terms of the Agreement. All such confidentiality obligations shall survive the termination or expiration of such Contract Processing. Processor shall notify Controller without undue delay if Processor becomes aware of any Data breaches within Processor’s scope of responsibility. Processor shall implement the measures necessary for securing Data and for mitigating potential negative consequences for the data subject; the Processor shall coordinate such efforts with Controller without undue delay. Processor shall notify to Controller the point of contact for any issues related to data protection arising out of or in connection with the Agreement. The Exhibit provides for a list of the initially designated persons. Processor shall correct or erase Data if so instructed by Controller and where covered by the scope of the instructions permissible. Where an erasure, consistent with data protection requirements, or a corresponding restriction of processing is impossible, Processor shall, based on Controller’s instructions, and unless agreed upon differently in the Agreement, destroy, in compliance with data protection requirements, all carrier media and other material or return the same to Controller. In specific cases designated by Controller, such Data shall be stored or handed over. The associated cost for doing so and protective measures to put in place shall be agreed upon separately, unless already agreed upon in the Agreement. Processor shall, upon termination of Contract Processing and upon Controller’s instruction, return all Data, carrier media and other materials to Controller or delete the same. Where a data subject asserts any claims against Controller in accordance with Article 82 of the GDPR, Processor shall support Controller in defending against such claims, where possible at Controller’s cost as set out in Section 6 para. 3. Controller shall notify Processor without undue delay, and comprehensively, of any defect or irregularity with regard to provisions on data protection detected by Controller in the results of Processor’s work.

  • The Supplier's Obligations The Supplier will in writing, by the time and date specified by the Contracting Body in accordance with paragraph 3.1.3(b) provide the Contracting Body with either: 3.2.1 a statement to the effect that it does not wish to tender in relation to the relevant Service Requirements; or 3.2.2 the Statement of Work and full details of its tender made in respect of the relevant Statement of Requirements. In the event that the Supplier submits a Statement of Work, it should include, as a minimum: a) an email response subject line to comprise unique reference number and Supplier name, so as to clearly identify the Supplier; b) a brief summary, in the email (followed by a confirmation letter), stating whether or not the Supplier is bidding for the Statement of Requirements; c) a proposal covering the Services Requirements; and d) confirmation of discounts applicable to the work, as referenced in Framework Agreement Schedule 3 (Charging Structure). 3.2.3 The Supplier shall ensure that any prices submitted in relation to a further competition held pursuant to this paragraph 3 shall be based on the Charging Structure and take into account any discount to which the Contracting Body may be entitled as set out in Framework Agreement Schedule 3 (Charging Structure). 3.2.4 The Supplier agrees that: a) all tenders submitted by the Supplier in relation to a further competition held pursuant to this paragraph 3 shall remain open for acceptance by the Contracting Body for ninety (90) Working Days (or such other period specified in the invitation to tender issued by the relevant Contracting Body in accordance with the Ordering Procedure); and b) all tenders submitted by the Supplier are made and will be made in good faith and that the Supplier has not and will not fix(ed) or adjust(ed) the amount of the offer by or in accordance with any agreement or arrangement with any other person. The Supplier certifies that it has not and undertakes that it will not: (a) communicate to any person other than the person inviting these offers the amount or approximate amount of the offer, except where the disclosure, in confidence, of the approximate amount of the offer was necessary to obtain quotations required for the preparation of the offer; and (b) enter into any arrangement or agreement with any other person that he or the other person(s) shall refrain from making an offer or as to the amount of any offer to be submitted.

  • THE CUSTOMER’S OBLIGATIONS (1) The Customer must maintain procedures relating to a withdrawal of the goods, recall and tampering and records necessary to support a recall of the goods, and allow the Supplier to inspect such procedures and records at any time on reasonable notice. (2) The Customer must provide any services, resources or facilities to the Supplier as may be reasonably required in respect of a recall of the goods. (3) The Supplier agrees to refund or provide credit to the Customer for any units of the goods that are recalled under this clause unless the conduct of the Customer or its employees, contractors or other persons it has engaged has given rise to the recall of the goods.

  • Customer’s Obligations The Customer shall: (a) provide the Supplier with: (i) all necessary co-operation in relation to this agreement; and (ii) all necessary access to such information as may be required by the Supplier; in order to render the Services, including but not limited to Customer Data, security access information and configuration services; (b) comply with all applicable laws and regulations with respect to its activities under this agreement; (c) carry out all other Customer responsibilities set out in this agreement in a timely and efficient manner. In the event of any delays in the Customer's provision of such assistance as agreed by the parties, the Supplier may adjust any agreed timetable or delivery schedule as reasonably necessary; (d) ensure that the Authorised Users use the Services and the Documentation in accordance with the terms and conditions of this agreement and shall be responsible for any Authorised User’s breach of this agreement; (e) obtain and shall maintain all necessary licences, consents, and permissions necessary for the Supplier, its contractors and agents to perform their obligations under this agreement, including without limitation the Services; (f) ensure that its network and systems comply with the relevant specifications provided by the Supplier from time to time; and (g) be solely responsible for procuring and maintaining its network connections and telecommunications links from its systems to the Supplier’s data centres, and all problems, conditions, delays, delivery failures and all other loss or damage arising from or relating to the Customer's network connections or telecommunications links or caused by the internet.

  • Lessor's Obligations Subject to the provisions of Paragraphs 2.2 (Condition), 2.3 (Compliance), 9 (Damage or Destruction) and 14 (Condemnation), it is intended by the Parties hereto that Lessor have no obligation, in any manner whatsoever, to repair and maintain the Premises, or the equipment therein, all of which obligations are intended to be that of the Lessee. It is the intention of the Parties that the terms of this Lease govern the respective obligations of the Parties as to maintenance and repair of the Premises, and they expressly waive the benefit of any statute now or hereafter in effect to the extent it is inconsistent with the terms of this Lease.

  • Conditions of Investor’s Obligations at Closing The obligations of the Investor under subsection 1.1(c) of this Agreement are subject to the fulfillment on or before the Closing of each of the following conditions, the waiver of which shall not be effective against the Investor if it does not consent thereto:

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