Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.
Development of the Property Except as modified by this Agreement, the Development and the Property will be developed in accordance with all applicable local, state, and federal regulations, including but not limited to the City’s ordinances and the zoning regulations applicable to the Property, and such amendments to City ordinances and regulations that that may be applied to the Development and the Property under Chapter 245, Texas Local Government Code, and good engineering practices (the “Applicable Regulations”). If there is a conflict between the Applicable Regulations and the Development Standards, the Development Standards shall control.
Research Collaboration 3.7.1 Aarvik shall carry out the activities of each Work Item and deliver the required Data Package and/or deliverables in accordance with the applicable SOW. Without limiting the generality of the foregoing, Aarvik shall, in accordance with the applicable SOWs and the timeline approved by JRC, apply the Aarvik IP to (i) design and synthesize Collaboration Compounds, and (ii) by itself or through subcontractor(s), [***]. During the Research Term, if any Party identifies any Third Party Patent or Know-How that is necessary or reasonably useful for any activity under the SOWs but has not been included in the Aarvik IP, then such Party shall immediately inform the other Party and the Parties shall discuss in good faith the need of obtaining a license from such Third Party.
3.7.2 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver the Data Packages and all other deliverables required under the [***], as well as the results of the Patentability and FTO Analysis as described in Section 3.2.3, to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1.
3.7.3 If, upon completion of the [***] for the Collaboration Program, AxxxXxxx decides not to advance the Collaboration Program to [***], ArriVent may terminate the Collaboration Program. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1.
3.7.4 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing.
3.7.5 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent.
3.7.6 Within [***] ([***]) days after completion of the [***], Aarvik shall deliver to ArriVent a full report on all key results and findings of the Collaboration Program, and such other data, results and information as ArriVent may deem necessary for it to determine whether or not to exercise the Option (the “Full Report”).
Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.
a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract.
b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.
Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.
Development of the Project 4.1 TSP's obligations in development of the Project:
a. for procuring and maintaining in full force and effect all Consents, Clearances and Permits, required in accordance with Law for development of the Project;
b. for financing, constructing, owning and commissioning each of the Element of the Project for the scope of work set out in Schedule 1 of this Agreement in accordance with:
i. the Electricity Act and the Rules made thereof;
ii. the Grid Code;
iii. the CEA Regulations applicable, and as amended from time to time, for Transmission Lines and sub-stations: • the Central Electricity Authority (Technical Standards for Connectivity to the Grid) Regulations, 2007; • Central Electricity Authority (Technical Standards for construction of Electrical Plants and Electric Lines) Regulation, 2010; • Central Electricity Authority (Grid Standard) Regulations, 2010; • Central Electricity Authority (Safety requirements for construction, operation and maintenance of Electrical Plants and Electrical Lines) Regulation, 2011; • Central Electricity Authority (Measures relating to Safety and Electricity Supply) Regulation, 2010; • Central Electricity Authority (Technical Standards for Communication System in Power System Operation) Regulations, 2020.
iv. Safety/ security Guidelines laid down by the Government;
v. Prudent Utility Practices, relevant Indian Standards and the Law; not later than the Scheduled COD as per Schedule 2 of this Agreement;
c. for entering into a Connection Agreement with the concerned parties in accordance with the Grid Code.
d. for owning the Project throughout the term of this Agreement free and clear of any encumbrances except those expressly permitted under Article 15 of this Agreement;
e. to co-ordinate and liaise with concerned agencies and provide on a timely basis relevant information with regard to the specifications of the Project that may be required for interconnecting the Project with the Interconnection Facilities;
f. for providing all assistance to the Arbitrators as they may require for the performance of their duties and responsibilities;
g. to provide to the Nodal Agency and CEA, on a monthly basis, progress reports with regard to the Project and its execution (in accordance with prescribed form) to enable the CEA to monitor and co-ordinate the development of the Project matching with the Interconnection Facilities;
h. to comply with Ministry of Power order no. 25-11/6/2018 – PG dated 02.07.2020 as well as other Guidelines issued by Govt. of India pertaining to this;
i. to procure the products associated with the Transmission System as per provisions of Public Procurement (Preference to Make in India) orders issued by Ministry of Power vide orders No. 11/5/2018 - Coord. dated 28.07.2020 for transmission sector, as amended from time to time read with Department for Promotion of Industry and Internal Trade (DPIIT) orders in this regard (Procuring Entity as defined in above orders shall deemed to have included Selected Bidder and/ or TSP). Also, to comply with Department of Expenditure, Ministry of Finance vide Order (Public Procurement No 1) bearing File No. 6/18/2019- PPD dated 23.07.2020, Order (Public Procurement No 2) bearing File No. 6/18/2019-PPD dated 23.07.2020 and Order (Public Procurement No. 3) bearing File No. 6/18/2019-PPD, dated 24.07.2020, as amended from time to time, regarding public procurement from a bidder of a country, which shares land border with India;
j. to submit to Nodal Agency information in the prescribed format [To be devised by Nodal Agency] for ensuring compliance to Article 4.1 i) above.
k. to comply with all its obligations undertaken in this Agreement.
4.2 Roles of the Nodal Agency in implementation of the Project:
4.2.1 Subject to the terms and conditions of this Agreement, the Nodal Agency shall be the holder and administrator of this Agreement and shall inter alia:
a. appoint an Independent Engineer within 90 days of the Effective Date
b. provide letters of recommendation to the concerned Indian Governmental Instrumentality, as may be requested by the TSP from time to time, for obtaining the Consents, Clearances and Permits required for the Project;
c. coordinate among TSP and upstream/downstream entities in respect of Interconnection Facilities; and
d. monitor the implementation of the Agreement and take appropriate action for breach thereof including revocation of guarantees, cancellation of Agreement, blacklisting etc
e. provide all assistance to the Arbitrators as required for the performance of their duties and responsibilities; and
f. perform any other responsibility (ies) as specified in this Agreement.
APPLICABILITY TO SUBCONTRACTORS Respondent agrees that all contracts it awards pursuant to the contract awarded as a result of this Agreement will be bound by the foregoing terms and conditions.
DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK
Maintenance of Intellectual Property The Company will, and will cause each of its Subsidiaries to, take all reasonable action necessary or advisable to maintain all of the Intellectual Property Rights of the Company and/or any of its Subsidiaries that are necessary or material to the conduct of its business in full force and effect.
Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-‐level domain strings across the Internet, certain top-‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.
