R&D Agreement Sample Clauses

R&D Agreement. For clarity, and notwithstanding anything to the contrary herein, in the event that a Company Licensee would like to create, design, or synthesize any Analogs exercising any rights that are not expressly licensed hereunder, the Company shall have the right to request such rights in accordance with, and subject to, the terms of the R&D Agreement.
AutoNDA by SimpleDocs
R&D Agreement. The R&D Agreement shall have been executed and delivered by the Purchaser.
R&D Agreement. The R&D Agreement shall be in full force and effect as of the Milestone Closing Date.
R&D Agreement. The R&D Agreement was terminated by the Original Agreement as of the Effective Date.
R&D Agreement. As of the date of establishment of the Company, the Company and ZBB Corp. shall enter into the R&D Agreement, as set forth on Exhibit E hereto.
R&D Agreement. The Research and Development Agreement dated January 11, 1998 among ERD, MSI, and Tamarack Storage Devices, Inc. ("Tamarack"). 2.4.
R&D Agreement. The Company shall have executed a Research and Development Agreement between the Company and EG&G Astrophysics, substantially in the form of the draft dated November 11, 1996.
AutoNDA by SimpleDocs
R&D Agreement. The R&D Agreement shall remain in full force and effect.

Related to R&D Agreement

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Valid Agreement This Agreement has been duly executed and delivered by the Purchaser and constitutes the legal, valid and binding obligation of the Purchaser, enforceable against the Purchaser in accordance with its terms, except (i) as limited by applicable bankruptcy, insolvency, reorganization, moratorium, and other laws of general application affecting enforcement of creditors’ rights generally, and (ii) as limited by laws relating to the availability of specific performance, injunctive relief, or other equitable remedies.

  • Manufacturing Agreement Each of the Sellers (as applicable) shall have executed and delivered to the Buyer the Manufacturing Agreement with respect to the portion of the Business conducted at the applicable Facility.

  • Supply Agreement The Supply Agreement shall have been executed on behalf of the Seller and delivered to the Purchaser.

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

  • Termination of License Agreement Without limiting the generality of the foregoing, in the event that the License Agreement is terminated in accordance with its terms, this Agreement, including without limitation any Purchase Order(s) or Project Work Orders then-in-effect, shall automatically terminate in its entirety as of the effective date of termination of the License Agreement.

  • Xxxxxx Agreement Xxxx Agreement contains the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior agreement, written or oral, with respect thereto.

  • Sublicense Agreements Sublicenses shall only be granted pursuant to written agreements, which shall be in compliance and not inconsistent with and shall be subject and subordinate to the terms and conditions of this Agreement (each, a "Sublicense Agreement"). Each such sublicense agreement shall contain, among other things, provisions to the following effect:

Time is Money Join Law Insider Premium to draft better contracts faster.