Co-Development Agreements Sample Clauses

Co-Development Agreements. Any operating system products (“OS Products”) that, in whole or in part, will be the subject of co-development or collaboration will be mutually agreed in writing from time to time. All co-development and collaboration will be subject to a definitive written co-development agreement to be mutually agreed by the parties prior to the commencement of the respective Collaboration Project(s). Such co-development agreements will include, among other things, terms and conditions providing for the following unless otherwise mutually agreed: (i) good faith efforts by each party to allocate engineering resources on a priority basis; (ii) each party bearing all direct and related costs associated with its development activities and personnel; (iii) Licensee sharing responsibility for providing PalmSource with compatibility tests and documentation for features or functions newly added by Licensee and agreeing to meet PalmSource’s then current requirements for dependencies related to dates, quality, and other specifics that may influence the widespread distribution of compatibility guidelines, tests, and metrics for the benefit of PalmSource’s business; (iv) ownership and other provisions consistent with those set forth in Section 10 of the Software License Agreement, under which, among other things, Licensee retains ownership of Licensee Add-On Modules and Licensee Replacement Fragments and PalmSource owns Derivative Works and other OS Developments; (v) a perpetual, irrevocable, non-terminable, paid-up, royalty-free, worldwide right and license for PalmSource to use, make and have made, modify, prepare and have prepared derivative works based on, reproduce, have reproduced, demonstrate, distribute, license, offer for sale, sell and import all OS Products that, in whole or in part, are the subject of co-development or collaboration, with the exclusive right to license such OS Products to third parties; and (vi) upon confirmation that a co-developed OS Product is feasible in commercial production and meets all of PalmSource’s then current requirements for a Golden Master Release of the PS OS Software (including, without limitation, compatibility, interoperability, reliability, support requirements and the like), the right for Licensee to obtain license a license to such co-developed OS Product (“Developed OS”) under the Software License Agreement (“Developed OS License”) on the same terms and conditions set forth therein, including the obligation to pay royalties and ma...
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
Co-Development Agreements. The Company and the Purchaser anticipate working together on one or more co-development agreements, the terms of which will be determined and set forth in separate agreements. The Company and the Purchaser agree that the general principles of co-development set forth on Exhibit H reflect the intent of both parties with respect to such co-development work.
Sample 1

Related to Co-Development Agreements

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

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

  • Supply Agreements For a period of three years from the consummation of the IPO, Odetics shall not unilaterally terminate or assign its guarantee obligation with respect to any supply agreement pursuant to which it has guaranteed the performance by ATL of ATL's obligations, unless such suppliers have consented to the termination or assignment of such guarantee.

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

  • Acquisition Agreements If the Equipment is subject to any Acquisition Agreement, Lessee, as part of this lease, transfers and assigns to Lessor all of its rights, but none of its obligations (except for Lessee's obligation to pay for the Equipment conditioned upon Lessee's acceptance in accordance with Paragraph 6), in and to the Acquisition Agreement, including but not limited to the right to take title to the Equipment. Lessee shall indemnify and hold Lessor harmless in accordance with Paragraph 19 from any liability resulting from any Acquisition Agreement as well as liabilities resulting from any Acquisition Agreement Lessor is required to enter into on behalf of Lessee or with Lessee for purposes of this lease.

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

  • License Agreements (a) Each Borrower and Guarantor shall (i) promptly and faithfully observe and perform all of the material terms, covenants, conditions and provisions of the material License Agreements to which it is a party to be observed and performed by it, at the times set forth therein, if any, (ii) not do, permit, suffer or refrain from doing anything that could reasonably be expected to result in a default under or breach of any of the terms of any material License Agreement, (iii) not cancel, surrender, modify, amend, waive or release any material License Agreement in any material respect or any term, provision or right of the licensee thereunder in any material respect, or consent to or permit to occur any of the foregoing; except, that, subject to Section 9.19(b) below, such Borrower or Guarantor may cancel, surrender or release any material License Agreement in the ordinary course of the business of such Borrower or Guarantor; provided, that, such Borrower or Guarantor (as the case may be) shall give Agent not less than thirty (30) days prior written notice of its intention to so cancel, surrender and release any such material License Agreement, (iv) give Agent prompt written notice of any material License Agreement entered into by such Borrower or Guarantor after the date hereof, together with a true, correct and complete copy thereof and such other information with respect thereto as Agent may request, (v) give Agent prompt written notice of any material breach of any obligation, or any default, by any party under any material License Agreement, and deliver to Agent (promptly upon the receipt thereof by such Borrower or Guarantor in the case of a notice to such Borrower or Guarantor and concurrently with the sending thereof in the case of a notice from such Borrower or Guarantor) a copy of each notice of default and every other notice and other communication received or delivered by such Borrower or Guarantor in connection with any material License Agreement which relates to the right of such Borrower or Guarantor to continue to use the property subject to such License Agreement, and (vi) furnish to Agent, promptly upon the request of Agent, such information and evidence as Agent may reasonably require from time to time concerning the observance, performance and compliance by such Borrower or Guarantor or the other party or parties thereto with the material terms, covenants or provisions of any material License Agreement.

  • Property Management Agreement The Property Management Agreement is in full force and effect and, to Borrower's Knowledge, there are no defaults thereunder by any party thereto and no event has occurred that, with the passage of time and/or the giving of notice would constitute a default thereunder.

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

  • Parties to Lock-Up Agreements The Company has furnished to the Underwriters a letter agreement in the form attached hereto as Exhibit A (the “Lock-up Agreement”) from each of the persons listed on Exhibit B. Such Exhibit B lists under an appropriate caption the directors and executive officers of the Company. If any additional persons shall become directors or executive officers of the Company prior to the end of the Company Lock-up Period (as defined below), the Company shall cause each such person, prior to or contemporaneously with their appointment or election as a director or executive officer of the Company, to execute and deliver to the Representatives a Lock-up Agreement.

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