Strengthening Technology Transfer and Extension. Strengthening the transfer of technology and extension services to enterprises with special attention to SMEs through, inter alia:
Strengthening Technology Transfer and Extension Sample Clauses
Related to Strengthening Technology Transfer and Extension
Research, Science and Technology Cooperation 1. The aims of cooperation in research, science and technology, carried out in the mutual interest of the Parties and in compliance with their policies, will be: (a) to build on existing agreements already in place for cooperation on research, science and technology; (b) to encourage, where appropriate, government agencies, research institutions, universities, private companies and other research organizations in the Parties to conclude direct arrangements in support of cooperative activities, programs or projects within the framework of this Agreement, specially related to trade and commerce; and (c) to focus cooperative activities towards sectors where mutual and complementary interests exist, with special emphasis on information and communication technologies and software development to facilitate trade between the Parties. 2. The Parties will encourage and facilitate, as appropriate, the following activities including, but not limited to:
Technology Transfer Subject to the terms of the Development Supply Agreement, as soon as reasonably practicable, but in no event later than the fifth (5th) anniversary of the Effective Date, Alnylam shall initiate a technology transfer to MedCo, or to its Third Party manufacturer(s) of Licensed Product, selected by MedCo and reasonably acceptable to Alnylam, of Alnylam Know-How that is reasonably necessary or useful for the Manufacture of the Licensed Product, and shall make available its personnel on a reasonable basis to consult with MedCo or such Third Party manufacturer(s) with respect thereto, all at MedCo’s expense, including the Costs reasonably incurred by Alnylam in connection with such technology transfer activities. MedCo shall reimburse Alnylam such Costs incurred with respect to such Manufacturing technology transfer within [***] days after receipt of an invoice therefor. Alnylam and its Affiliates shall keep complete and accurate records in sufficient detail to enable the payments payable hereunder to be determined. Alnylam shall not be required to perform technology transfer to more than one Third Party manufacturer for each stage of the Licensed Product supply chain (i.e., Bulk Drug Substance, Bulk Drug Product and Finished Product). Promptly after MedCo’s written request, Alnylam shall use Commercially Reasonable Efforts to assign to MedCo any manufacturing agreement between Alnylam and a Third Party that is solely related to the manufacture of Licensed Products. Such assignment shall be subject to the terms and conditions of such agreement, including any required consents of such Third Party and MedCo’s written agreement to assume all the obligations of Alnylam under such agreement to be undertaken after such assignment, but Alnylam shall remain solely responsible for its obligations under such agreement arising prior to such assignment. Except as provided in the immediately preceding sentence, MedCo shall be solely responsible for contracting with such Third Party manufacturer (and any other Third Party manufacture to whom Alnylam has initiated technology transfer as set forth in this Section 5.3) for the supply of such Licensed Product and Alnylam shall have no obligations under such agreement between MedCo and such Third Party manufacturer. Alnylam shall use Commercially Reasonable Efforts to obtain any such consent in a form reasonably acceptable to MedCo.
TECHNOLOGY/KNOWLEDGE TRANSFER ACTIVITIES The goal of this task is to develop a plan to make the knowledge gained, experimental results, and lessons learned available to the public and key decision makers. The Recipient shall: • Prepare an Initial Fact Sheet at start of the project that describes the project. Use the format provided by the CAM. • Prepare a Final Project Fact Sheet at the project’s conclusion that discusses results. Use the format provided by the CAM. • Prepare a Technology/Knowledge Transfer Plan that includes: o An explanation of how the knowledge gained from the project will be made available to the public, including the targeted market sector and potential outreach to end users, utilities, regulatory agencies, and others.
Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.
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.
Development of Common Reporting and Exchange Model The Parties are committed to working with Partner Jurisdictions and the Organisation for Economic Co- operation and Development on adapting the terms of this Agreement and other agreements between the United States and Partner Jurisdictions to a common model for automatic exchange of information, including the development of reporting and due diligence standards for financial institutions.
Notice for Technological Change This subclause sets out the notice provisions to be applied to terminations by the employer for reasons arising from "technology" in accordance subparagraph (1) of paragraph (a) of subclause (i)
Dissemination of Research Findings and Acknowledgement of Controlled-Access Datasets Subject to the NIH GDS Policy It is NIH’s intent to promote the dissemination of research findings from use of controlled-access dataset(s) subject to the NIH GDS Policy as widely as possible through scientific publication or other appropriate public dissemination mechanisms. Approved Users are strongly encouraged to publish their results in peer-reviewed journals and to present research findings at scientific meetings.
Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.
VISIBILITY OF FUNDING FROM THE OFFICIAL DEVELOPMENT ASSISTANCE Unless the SAIDC requests or agrees otherwise, any communication or publication made by the Final Beneficiary that relates to the action, including at conferences, seminars or in any information or promotional materials (such as brochures, leaflets, posters, presentations in electronic form, etc.), including tangible assets acquired from the project must: (a) indicate that the action has received funding from the Official Development Assistance, SlovakAid and (b) display the SlovakAid logo. When displayed in association with another logo, the SlovakAid logo must have appropriate prominence. The obligation to display the SlovakAid logo does not confer on the Final Beneficiary a right of exclusive use. The Final Beneficiary may not appropriate the SlovakAid logo or any similar trademark or logo, either by registration or by any other means. For the purposes of the first, second and third subparagraphs and under the conditions specified therein, the Final Beneficiary may use the SlovakAid logo without first obtaining permission from the SAIDC.
