Research and Development Agreements Sample Clauses

Research and Development Agreements. Schedule 4.17(c) identifies each sponsoring, research and development or other agreement entered into since January 1, 2004 (whether expired or currently in effect) pursuant to which any Seller Party or the Affiniti Companies has sponsored or otherwise collaborated in the research and development of Proprietary Rights.
Sample 1
AutoNDA by SimpleDocs
Research and Development Agreements. The Support and Development Agreement will also specify mechanisms (whether through the JSC or otherwise) to maintain coordination of all development activities of the Parties for Products in the Field and to address concerns that either Party may have that development activities within or outside the Territory could adversely affect the Product in the other Party’s territory.
Sample 1
Research and Development Agreements. (a) This sub-clause (a) applies to agreements for research into and/or development of Gas Turbine or Steam Turbine technology:
Sample 1
Research and Development Agreements. In December 1999, the Company extended its development contract with Pirelli Cables and Systems, a stockholder of the Company, to jointly develop high temperature superconducting cable wires. Pirelli agreed to provide the Company with up to $13,800,000 in additional funding over the five-year period between October 1, 1999 and September 30, 2004. $3,500,000 of that funding was recognized as revenue in fiscal 2000, of which $2,500,000 was for R&D work performed by the Company prior to the effective date (October 1, 1999) of the latest Pirelli agreement. The Pirelli alliance was originally established in February 1990; in the 11-year period between 1990 and March 31, 2001, the Company received development funding of approximately $21,600,000 from Pirelli. In fiscal 1998, the Company entered into research and development contracts with Asea Xxxxx Boveri (ABB) and EDF, an affiliate of which is a stockholder of the Company, to develop HTS wire for power transformers. The ABB and EDF agreements, each of which called for the payment of $5,000,000 in development fees to the Company over four years, were terminated in April 2000, with ABB having paid a cumulative total of $4,350,000 and EDF $4,450,000. The Company recorded revenues under these contracts as follows: 2001 2000 1999 ---------- ---------- ---------- Pirelli................................... $2,000,000 $4,250,000 $2,000,000 ABB....................................... -- 1,050,000 1,025,000 EDF....................................... -- 1,050,000 1,600,000 ---------- ---------- ---------- $2,000,000 $6,350,000 $4,625,000 ========== ========== ========== Future funding commitments under the Pirelli contract are $8,300,000 through September 2004. At March 31, 2001, $1,750,000 due under the development contract with Pirelli was included in accounts receivable, of which $1,250,000 was classified as long-term. In March 1996, the Company entered into a strategic alliance with the Electric Power Research Institute (EPRI) to develop and commercialize a possible next-generation HTS wire. This agreement ended on March 31, 2000. In March 1996, under the first phase of the agreement, the Company granted a warrant for 100,000 shares of common stock to EPRI at $14.00 per share which became exercisable over a five-year period following the date of grant. In March 1998, under the second phase of the agreement, the Company granted to EPRI another AMERICAN SUPERCONDUCTOR CORPORATION NOTES TO CONSOLIDATED STATEMENTS--(Conti...
Sample 1

Related to Research and Development Agreements

  • Research and Development (i) Advice and assistance in relation to research and development of Party B;

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

  • Clinical Development Licensee will have sole responsibility for and sole decision making over the clinical development of any Product arising from the Research Program in the Field. Notwithstanding the foregoing, if Licensee wishes to conduct clinical development of a Development Candidate at Penn and Penn has the clinical expertise, interest and ability to run such a trial as assessed at Penn’s sole discretion, such a study will be conducted under a separate Clinical Trial Agreement to be negotiated by the Parties prior to initiation of such study. Such separate clinical trial agreement will include a detailed clinical development plan, including costs and time lines for conducting the Clinical Trial.

  • Initial Development Plan Not later than the Effective Date, Licensee shall have provided Merck with an initial Development plan for the Licensed Product in the Field in the Territory, which shall be incorporated as part of this Agreement as Attachment 3.02(a) (as may be amended in accordance with this Agreement, the “Development Plan”). **CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND WILL BE FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO A CONFIDENTIAL TREATMENT REQUEST.

  • Joint Development If joint development is involved, the Recipient agrees to follow the latest edition of FTA Circular 7050.1, “Federal Transit Administration Guidance on Joint Development.”

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

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

  • Collaboration Management Promptly after the Effective Date, each Party will appoint a person who will oversee day-to-day contact between the Parties for all matters related to the management of the Collaboration Activities in between meetings of the JSC and will have such other responsibilities as the Parties may agree in writing after the Effective Date. One person will be designated by Merck (the “Merck Program Director”) and one person will be designated by Moderna (the “Moderna Program Director,”) together will be the “Program Directors”. Each Party may replace its Program Director at any time by notice in writing to the other Party. Any Program Director may designate a substitute to temporarily perform the functions of that Program Director by written notice to the other Party. The initial Program Directors will be: For Moderna: [***] For Merck: [***]

  • Marketing Agreement The Company shall have entered into, ------------------- executed and delivered the Marketing Agreement.

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