Technology and Program Transfer Plan. The Parties shall have mutually agreed upon a final Technology and Program Transfer Plan, which plan shall be appended to Schedule 1.69 hereof.
Technology and Program Transfer Plan Sample Clauses
Related to Technology and Program Transfer Plan
Manufacturing Technology Transfer Upon AbbVie’s written request with respect to a given Collaboration CAR-T Product and Licensed Product, Caribou shall effect a full transfer to AbbVie or its designee (which designee may be an Affiliate or a Third Party Provider) of all Materials and Know-How Controlled by Caribou relating to the then-current process for the Manufacture of such Collaboration CAR-T Product and any corresponding Licensed Products (each, a “Manufacturing Process”). Caribou shall provide, shall cause its Affiliates to provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to provide, all reasonable assistance requested by AbbVie to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to implement each Manufacturing Process at the facilities designated by AbbVie. If requested by AbbVie, such assistance shall include facilitating the entering into of agreements with applicable Third Party suppliers relating to such Collaboration CAR-T Product and any corresponding Licensed Products. Without limitation of the foregoing, in connection with the Manufacturing Process and related transfer: (a) Caribou shall, and shall cause its Affiliates to, make available to AbbVie (or its Affiliate or designated Third Party Provider, as applicable), and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to make available to AbbVie, from time to time as AbbVie may request, all Materials and Manufacturing-related Know-How Controlled by Caribou relating to each Manufacturing Process, including methods, reagents and processes and testing/characterization Know-How, and all documentation constituting material support, performance advice, shop practice, standard operating procedures, specifications as to Materials to be used, and control methods, that are necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party manufacturer, as applicable) to use and practice such Manufacturing Process; (b) Caribou shall cause all appropriate employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility at mutually convenient times to assist with the working up and use of each Manufacturing Process and with the training of the personnel of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to the extent necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice such Manufacturing Process; (c) Without limiting the generality of this Section 4.4.2, Caribou shall cause all appropriate analytical and quality control laboratory employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate analytical and quality control laboratory employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility and make available all necessary equipment, at mutually convenient times, to support and execute the provision of all applicable analytical methods and the validation thereof (including all applicable Know-How, Information and Materials Controlled by Caribou, and sufficient supplies of all primary and other reference standards); (d) Caribou shall, and shall cause its Affiliates to, take such steps, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers take such steps, as are necessary or reasonably useful to assist AbbVie (or its Affiliate or designated Third Party Provider, as applicable) in obtaining any necessary licenses, permits or approvals from Regulatory Authorities with respect to the Manufacture of the applicable Collaboration CAR-T Products and corresponding Licensed Products at the applicable facilities; and (e) Caribou shall, and shall cause its Affiliates to, provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers to provide, such other assistance as AbbVie (or its Affiliate or designated Third Party Provider, as applicable) may reasonably request to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice each Manufacturing Process and otherwise to Manufacture the applicable Collaboration CAR-T Products and corresponding Licensed Products.
Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.
Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.
End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).
Development Plans Shipper has provided Gatherer with a report attached hereto as Exhibit D (the “Current Development Plan”) describing in detail, as of January 1, 2017, the planned development, drilling, and production activities to take place with respect to Dedicated Production for the applicable Development Period. The information contained in the TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Current Development Plan is broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by the Current Development Plan, on a Quarter-by-Quarter basis, and with respect to the remaining Years covered by the Current Development Plan, on a Year-by-Year basis. The Current Development Plan attached hereto has been approved by the Parties. (a) From time to time during each Year of the Term, the Parties shall meet to discuss the planned development, drilling, and production activities that Shipper expects to take place with respect to Dedicated Production for the then-applicable Development Period. Shipper and Gatherer shall each make their respective representatives available to participate in such meetings and discussions. No later than August 1 of each such Year, Shipper shall provide (or cause to be provided) to Gatherer a proposed update of the then-currently agreed Development Plan, prepared on the same basis as the Current Development Plan and describing in detail the planned development, drilling, and production activities to take place with respect to Dedicated Production for the then-applicable Development Period (any such update, an “Updated Development Plan” and, together with the Current Development Plan, each, a “Development Plan”). Notwithstanding anything herein to the contrary, in no event shall Gatherer be required to agree to any Updated Development Plan and corresponding updated Gathering System Plan that contains a Committed Build-Out that (i) has a corresponding Target Completion Date that occurs after the end of the Initial Term, and (ii) Gatherer, in its sole discretion, does not wish to approve. (b) Each proposed Development Plan shall include information as to the following, in each case, broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by such Development Plan, on a Quarter-by-Quarter basis, and, with respect to the remaining Years covered by such Development Plan, on a Year-by-Year basis: (i) all Xxxxx that, as of the date such Development Plan was delivered, are currently in existence and (A) the production therefrom is being delivered into the Gathering System, or (B) are awaiting connection to the Gathering System; (ii) the Xxxxx that are expected to be drilled during the time period covered by such Development Plan (each such Well reflected in such Development Plan, a “Planned Well”), and the estimated timing of the drilling of such Planned Xxxxx; (iii) forward-looking production estimates for the applicable time period covered by such Development Plan for all Shipper Gas (A) that Shipper reasonably and in good faith believes will become owned or Controlled by Shipper during the time period covered by such Development Plan, and/or (B) that will be produced from (I) in the aggregate, all Xxxxx then-existing and (II) in the aggregate, any Planned Xxxxx included in such Development Plan (such collective estimates described in subsections (A) and (B), both with respect to a particular Quarter and an entire Year, the “Dedicated Production Estimates”); TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). (iv) forward-looking estimates for the applicable time period covered by such Development Plan of the aggregate volumes of those Shipper Injected Liquids that Shipper intends to Tender to the Injection Points hereunder to receive the System Services (such estimates, both with respect to a particular Quarter and an entire Year, the “System Liquids Estimates” and, together with the Dedicated Production Estimates, the “System Production Estimates”); (v) (A) each new receipt point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such receipt point, including those located at the site of a Planned Well, a “Planned Receipt Point”), (B) each Receipt Point at which Shipper expects to Tender Shipper Gas and/or Shipper Injected Liquids reflected in such Development Plan into the Gathering System, and (C) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to Tender at each such Receipt Point and Planned Receipt Point; (vi) the earliest date on which each Planned Well included in the Development Plan is estimated to be completed and producing, which date shall not be earlier than three Months after the January 1st that is immediately subsequent to the date that the Development Plan that initially reflected such Planned Well was delivered to Gatherer hereunder; (vii) the anticipated characteristics of the production from the Xxxxx and Planned Xxxxx reflected in such Development Plan (including liquids content and gas and liquids composition) and the projected production volumes and production pressures applicable thereto; provided that Shipper may utilize the existing and historical production information from similarly situated Xxxxx; (viii) (A) each new delivery point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such delivery point, a “Planned Delivery Point”), (B) each Delivery Point at which Shipper expects Shipper Gas produced from the Xxxxx and Planned Xxxxx reflected in such Development Plan to be redelivered to Shipper, (C) each Delivery Point at which Shipper expects any Drip Liquids allocated to Shipper in accordance with this Agreement and/or Shipper Injected Liquids to be redelivered to Shipper, and (D) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to be redelivered to Shipper at each such Delivery Point and Planned Delivery Point; (ix) any (A) proposed revision to the then-existing Dedicated Area and/or any then-existing Dedicated Contract and/or (B) any new contract that Shipper proposes to be a Dedicated Contract; and (x) other information reasonably requested by Gatherer that is relevant to the design, construction, and operation of the Gathering System, including (A) any Subsystem Extension proposed by Shipper, (B) the relevant Receipt Point, Planned Receipt Point, Delivery Point and Planned Delivery Point facilities applicable to such TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Development Plan, and (C) any treating, processing, or liquids handling facilities proposed by Shipper that may be required for any Shipper Gas and/or Shipper Injected Liquids to meet applicable Downstream Facility specifications at the Delivery Points.
Technology Research Analyst Job# 1810 General Characteristics
Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.
Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.
SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:
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.
