MASTER TECHNOLOGY DEVELOPMENT AGREEMENT Sample Clauses

MASTER TECHNOLOGY DEVELOPMENT AGREEMENT or MTDA shall mean the agree- ment executed by the PARTIES on or about March 31, 1997, containing the terms governing research and development and the funding thereof.
AutoNDA by SimpleDocs

Related to MASTER TECHNOLOGY DEVELOPMENT AGREEMENT

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

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

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

  • Manufacturing Technology Transfer With respect to each Technology Transfer Product, upon AbbVie’s written request after the Inclusion Date for the Included Target to which such Technology Transfer Product is Directed, Morphic shall effect a full transfer to AbbVie or its designee (which designee may be an Affiliate or a Third Party manufacturer) of all Morphic Know-How and Joint Know-How relating to the then-current process for the Manufacture of such Technology Transfer Product (the “Manufacturing Process”) and to implement the Manufacturing Process at facilities designated by AbbVie (such transfer and implementation, as more fully described in this Section 5.3, the “Manufacturing Technology Transfer”). To assist with the Manufacturing Technology Transfer, Morphic will make its personnel reasonably available to AbbVie during normal business hours for up to [***] FTE hours with respect to each Included Target (in each case, free of charge to AbbVie) to transfer and implement the Manufacturing Process under this Section 5.3. Thereafter, if requested by AbbVie, Morphic shall continue to perform such obligations; provided, that AbbVie will reimburse Morphic for its full-time equivalent (FTE) costs (for clarity, in excess of [***] FTE hours) and any reasonable and verifiable out-of-pocket costs incurred in providing such assistance. CERTAIN CONFIDENTIAL INFORMATION CONTAINED IN THIS DOCUMENT, MARKED BY [***], HAS BEEN OMITTED BECAUSE IT IS NOT MATERIAL AND WOULD LIKELY CAUSE COMPETITIVE HARM TO THE COMPANY IF PUBLICLY DISCLOSED.

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

  • Technology License 4.1 Unless any event described in Article 2.2 or 2.3 of this Agreement occurs, all of the technology required to be licensed for any of Party B’s business shall be provided by Party A on an exclusive basis. Party A will try its best to license Party B to use the technology owned by Party A, or re-license Party B to use the technology as approved by the owner.

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

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

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

  • New Technology When new or updated technology is introduced into a workplace, it will be the responsibility of the employer to provide appropriate and, if necessary, ongoing training to the employees directly affected. Such training will include any health and safety implications or information that will enable employees to operate the equipment without discomfort and will help maintain their general well-being.

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