Openonline S Obligations
Openonline S Obligations Sample Clauses
Related to Openonline S Obligations
FIRM’S OBLIGATIONS 3.1 Firm shall comply with the Rules and this Agreement at all times and shall timely pay all fees established in accordance with the Rules.
Developer’s Obligations (a) Upon the expiry of the Agreement Period by efflux of time and in the normal course, the Developer shall on the Expiry Date, hand back vacant and peaceful possession of Project Site and the Project Facilities to the Authority free of cost and in good operable condition.
COUNCIL’S OBLIGATIONS Save as otherwise expressly provided, the obligations of the Council under the Contract are obligations of the Council in its capacity as a contracting counterparty and nothing in the Contract shall operate as an obligation upon, or in any other way xxxxxx or constrain the Council in any other capacity, nor shall the exercise by the Council of its duties and powers in any other capacity lead to any liability under the Contract (howsoever arising) on the part of the Council to the Provider.
Customer’s Obligations 8.1 The Customer shall:
TRANSNET’S OBLIGATIONS 8.1 Transnet undertakes to promptly comply with any reasonable request by the Supplier/Service Provider for information, including information concerning Transnet's operations and activities, that relates to the Goods/Services as may be necessary for the Supplier/Service Provider to provide the Goods/Services, but for no other purpose. However, Transnet's compliance with any request for information is subject to any internal security rules and requirements and subject to the observance by the Supplier/Service Provider of its confidentiality obligations under this Agreement.
Developer's Obligation The Developer shall bear the total cost and expense of all the obligations and duties created by this Contract unless otherwise explicitly stated in this Contract. Those obligations and duties are, generally, to create all Improvements as may be required by the City in accordance with this Contract and with City Requirements. Such Improvements include but are not limited to: i) all Improvements within the Project; ii) all Improvements connecting to water, sewer, or stormwater infrastructure outside the Project, whether existing or planned; iii) modifications to any existing water, sewer, or stormwater infrastructure outside the Project that facilitate provision of utility service to the Project, or compliance with City Requirements, or integration of the Improvements with the surrounding existing or planned water, sewer, or stormwater system; and iv) new streets or alterations to existing streets or rights of way within which the Improvements are located. The Developer's obligations also include all costs, including but not limited to legal costs, of acquiring all fees or easements within which the Improvements will be located.
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. § 4Controller’s Obligations 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.
RESIDENT’S OBLIGATIONS Resident agrees as follows:
City’s Obligations 1. The City will disclose those parts of records the Contractor has marked as “proprietary” information only to authorized persons unless:
SUPPLIER’S OBLIGATIONS 6.1 The Supplier undertakes that the Services will be performed substantially in accordance with the Documentation and with reasonable skill and care.
