Sharing of Project Data with the Research Community Sample Clauses

Sharing of Project Data with the Research Community. Awardee will share with the research community Project Data relevant to topics of interest to the research community, such as disease-specific assays, animal models, correlates of protection or diagnostics and epidemic preparedness mechanisms, as described in the IPDP and agreed in the JMAG, subject to the Awardee’s right, prior to such Project Data entering the public domain, (i) to remove Trade Secret Information and Confidential Information within Awardee Background IP, if any, included in such Project Data and (ii) in case there is any patentable subject matter included in such Project Data, to delay such Project Data entering the public domain for a reasonable period of time, not to exceed [***].
Sample 1Sample 2
AutoNDA by SimpleDocs
Sharing of Project Data with the Research Community. Awardee will share Project Data as described in the IPDP relevant to topics of interest to the research community, such as disease-specific assays, animal models, correlates of protection or diagnostics and epidemic preparedness mechanisms, subject to reasonable protection for Awardee’s rights under this Agreement.
Sample 1

Related to Sharing of Project Data with the Research Community

  • Outside Activities of Limited Partners Subject to any agreements entered into by a Limited Partner or its Affiliates with the General Partner, Partnership or a Subsidiary, any Limited Partner and any officer, director, employee, agent, trustee, Affiliate or stockholder of any Limited Partner shall be entitled to and may have business interests and engage in business activities in addition to those relating to the Partnership, including business interests and activities in direct competition with the Partnership or that are enhanced by the activities of the Partnership. Neither the Partnership nor any Partners shall have any rights by virtue of this Agreement in any business ventures of any Limited Partner or Assignee. Subject to such agreements, none of the Limited Partners nor any other Person shall have any rights by virtue of this Agreement or the partnership relationship established hereby in any business ventures of any other Person, other than the Limited Partners benefiting from the business conducted by the General Partner, and such Person shall have no obligation pursuant to this Agreement to offer any interest in any such business ventures to the Partnership, any Limited Partner or any such other Person, even if such opportunity is of a character which, if presented to the Partnership, any Limited Partner or such other Person, could be taken by such Person.

  • 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: [***]

  • Research Collaboration Upon FibroGen’s request, the Parties will discuss conducting a research program funded by AstraZeneca and directed toward franchise enhancement and lifecycle management for HIF Compounds or other topics that the Parties determine relevant to the Products and the Field. Upon agreement on the terms of such research program, the Parties will enter into a separate agreement or amend this Agreement accordingly.

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

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Collaboration We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.

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

  • Omnibus Transparency Services Upon request of the Fund, the Transfer Agent shall carry out certain information requests, analyses and reporting services in support of the Fund’s obligations under Rule 22c-2(a)(2). The parties will agree to such services and terms as stated in the attached schedule (“Schedule 1.1(y)” entitled “Omnibus Transparency Services”) that may be changed from time to time subject to mutual written agreement between the parties.

  • REMOTE ACCESS SERVICES ADDENDUM The Custodian and each Fund agree to be bound by the terms of the Remote Access Services Addendum hereto.

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

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