Extension of the Licence for Production Sample Clauses

Extension of the Licence for Production. In the event of a Discovery and unless otherwise decided by the Operating Committee, and with due regard for the need to obtain the approval of the Parties in sufficient time before the expiry of the ex­ploration period (or any extension thereof), the Operator shall submit to the Opera­ting Committee a proposed application for the extension of the Licence for the purpose of production. The proposal shall be accom­panied by a report on the deposit concerned, which in accordance with the requirements of the Danish Energy Agency describes the geological, technical and economic characteristics upon which the appraisal of the deposit is based. As soon as possible after the approval by the Operating Committee of the application and the report, the Operator shall submit them to the Danish Energy Agency. If the Operating Committee decides that an application for exten­sion shall not be submitted, the Operator shall submit to the Danish Energy Agency a report on the deposit which has been approved by the Operating Committee. If the necessary majority required by Section 4.7.2 for the submission of an application for extension covering one or more deposits is not achieved, and the failure to submit an application at the time in question will result in the expiry of the Licence, the Parties wishing to do so may submit an application for an extension of the Licence covering the deposit, to be effective as of the expiry of the exploration period. The Parties not participating in such an application shall cease to be Parties to said extension of the Licence. The Parties not wishing to join in such an application shall take no action which would unreasonably prejudice such an application.
Sample 1
AutoNDA by SimpleDocs

Related to Extension of the Licence for Production

  • License; Use Upon delivery to an Authorized Person or a person reasonably believed by Custodian to be an Authorized Person of the Fund of software enabling the Fund to obtain access to the System (the “Software”), Custodian grants to the Fund a personal, nontransferable and nonexclusive license to use the Software solely for the purpose of transmitting Written Instructions, receiving reports, making inquiries or otherwise communicating with Custodian in connection with the Account(s). The Fund shall use the Software solely for its own internal and proper business purposes and not in the operation of a service bureau. Except as set forth herein, no license or right of any kind is granted to the Fund with respect to the Software. The Fund acknowledges that Custodian and its suppliers retain and have title and exclusive proprietary rights to the Software, including any trade secrets or other ideas, concepts, know-how, methodologies, or information incorporated therein and the exclusive rights to any copyrights, trademarks and patents (including registrations and applications for registration of either), or other statutory or legal protections available in respect thereof. The Fund further acknowledges that all or a part of the Software may be copyrighted or trademarked (or a registration or claim made therefor) by Custodian or its suppliers. The Fund shall not take any action with respect tot the Software inconsistent with the foregoing acknowledgement, nor shall the Fund attempt to decompile, reverse engineer or modify the Software. The Fund may not xxx, sell, lease or provide, directly or indirectly, any of the Software of any portion thereof to any other person or entity without Custodian’s prior written consent. The Fund may not remove any statutory copyright notice or other notice included in the Software or on any media containing the Software. The Fund shall reproduce any such notice on any reproduction of the Software and shall add any statutory copyright notice or other notice to the Software or media upon Custodian’s request.

  • Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.

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

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.

  • Research License Each Collaborator shall allow the other Collaborator to practice any of its Non- Subject Inventions for the purpose of performing the Cooperative Work. No license, express or implied, for commercial application(s) is granted to either Collaborator in Non-Subject Inventions by performing the Cooperative Work. For commercial application(s) of Non-Subject Inventions, a license must be obtained from the owner.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • 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 OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

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