Development Phase for the Purposes of Local Content Sample Clauses

Development Phase for the Purposes of Local Content. For the purposes of benchmarking of the Local Content, the development phase will begin on the date of submission of the Declaration of Commerciality and will close, for each module of the development phase, with the first among the following occurrences:
AutoNDA by SimpleDocs
Development Phase for the Purposes of Local Content. For the purposes of benchmarking of the Local Content, the development phase will begin on the date of submission of the Declaration of Commerciality and will close, for each module of the development phase, with the first among the following occurrences: The course of five years after the extraction of the first oil; The abandonment of the development of the module of the development phase; or The achievement of the investments foreseen in the Development Plan. ANP may, in exceptional character and upon request of the Contracted Party, exempt it from the compliance with the Local Content percentage with which it is committed in relation to the recruitment of a specific good or service when: There is no Brazilian supplier for the purchased product or contracted service; All proposals received from Brazilian suppliers present an excessive delivery limit in relation to non-Brazilian counterparts; All proposals received from Brazilian suppliers present an excessive delivery price in relation to non-Brazilian counterparts; or There is no replacement of a given technology for which there is no offer with Local Content. In this case the exemption from the compliance with the Local Content only applies to goods and services replaced by the new technology. The exemption from the requirement of compliance with the Local Content does not extend to the overall percentage of Local Content, not distracting, therefore, any deduction of amount. The request must be made in a reasoned way and presented to ANP during the duration of the phase or step in which the exemption is intended. If ANP has granted the exemption mentioned in the caput of this paragraph due to the conditions provided in lines “a”, “b”, “c” or “d”, the Contracted Party is obliged to prove the accomplishment of the alleged conditions for the granting of the exemption. The exemption from the obligation of compliance with the Local Content does not apply to items of basic and detailed engineering The Contracted Party may request from ANP the adjustment of the Local Content with which it has committed itself to. The request for reduction of the Local Content should be made in relation to the supply lines of the Table of Local Content, whereas the Local Content for the other items. The adjustments in the committed Local Content do not extend to the overall Local Content. The request must be made in such a way as detailed, formal, written and presented to ANP during the duration of the phase or stage for whic...
Development Phase for the Purposes of Local Content. 49 Exemption from the Obligation of Compliance with the Local Content 49 Adjustments in the Committed Local Content Percentage 50 Surplus of Local Content Erro! Indicador não definido. Fine for Noncompliance with the Local Content 51 Environmental Control 52 Social Responsibility 52 Liability for Damage and Losses 53 Insurances 53 Governmental and Third Parties Contributions 55 Taxation Proceedings 56 Certificates and Proof of Regularity 56 Currency 57 Foreign Currency 57 Accounting 57 Audit 57 Undivided Share in the Rights and Obligations 59
Development Phase for the Purposes of Local Content. 50 Exemption from the Obligation of Compliance with the Local Content 50 Adjustments in the Committed Local Content Percentage 51

Related to Development Phase for the Purposes of Local Content

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • 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 Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • Tests and Preclinical and Clinical Trials The preclinical studies and clinical trials conducted by or, to the Company’s knowledge, on behalf of the Company, that are described in the Registration Statement, the Pricing Disclosure Package and the Prospectus, as applicable, and are intended to be submitted to the U.S. Food and Drug Administration (the “FDA”) or other comparable government entities, were and, if still ongoing, are being conducted in all material respects in accordance with experimental protocols, procedures and controls pursuant to accepted professional scientific standards and all Authorizations and Applicable Laws, including, without limitation, current Good Clinical Practices and Good Laboratory Practices and any applicable rules and regulations of the jurisdiction in which such trials and studies are being conducted; the descriptions of the results of such studies and trials contained in the Registration Statement, the Pricing Disclosure Package and the Prospectus are, to the Company’s knowledge, accurate and complete in all material respects and fairly present the data derived from such studies and trials; except to the extent disclosed in the Registration Statement, the Pricing Disclosure Package and the Prospectus, the Company is not aware of any studies or trials, the results of which the Company believes reasonably call into question the study or trial results described or referred to in the Registration Statement, the Pricing Disclosure Package and the Prospectus when viewed in the context in which such results are described and the clinical stage of development; and, except to the extent disclosed in the Registration Statement, the Pricing Disclosure Package or the Prospectus, the Company has not received any written notices or written correspondence from the FDA or any governmental entity requiring the termination or suspension of any preclinical studies or clinical trials conducted by or on behalf of the Company, other than ordinary course communications with respect to modifications in connection with the design and implementation of such trials, copies of which communications have been made available to you.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

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

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

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

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