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.
Manufacturing Technology Transfer Upon AbbVie’s written request with respect to a given Collaboration CAR-T Product and Licensed Product, Caribou shall effect a full transfer to AbbVie or its designee (which designee may be an Affiliate or a Third Party Provider) of all Materials and Know-How Controlled by Caribou relating to the then-current process for the Manufacture of such Collaboration CAR-T Product and any corresponding Licensed Products (each, a “Manufacturing Process”). Caribou shall provide, shall cause its Affiliates to provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to provide, all reasonable assistance requested by AbbVie to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to implement each Manufacturing Process at the facilities designated by AbbVie. If requested by AbbVie, such assistance shall include facilitating the entering into of agreements with applicable Third Party suppliers relating to such Collaboration CAR-T Product and any corresponding Licensed Products. Without limitation of the foregoing, in connection with the Manufacturing Process and related transfer: (a) Caribou shall, and shall cause its Affiliates to, make available to AbbVie (or its Affiliate or designated Third Party Provider, as applicable), and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to make available to AbbVie, from time to time as AbbVie may request, all Materials and Manufacturing-related Know-How Controlled by Caribou relating to each Manufacturing Process, including methods, reagents and processes and testing/characterization Know-How, and all documentation constituting material support, performance advice, shop practice, standard operating procedures, specifications as to Materials to be used, and control methods, that are necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party manufacturer, as applicable) to use and practice such Manufacturing Process; (b) Caribou shall cause all appropriate employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility at mutually convenient times to assist with the working up and use of each Manufacturing Process and with the training of the personnel of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to the extent necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice such Manufacturing Process; (c) Without limiting the generality of this Section 4.4.2, Caribou shall cause all appropriate analytical and quality control laboratory employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate analytical and quality control laboratory employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility and make available all necessary equipment, at mutually convenient times, to support and execute the provision of all applicable analytical methods and the validation thereof (including all applicable Know-How, Information and Materials Controlled by Caribou, and sufficient supplies of all primary and other reference standards); (d) Caribou shall, and shall cause its Affiliates to, take such steps, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers take such steps, as are necessary or reasonably useful to assist AbbVie (or its Affiliate or designated Third Party Provider, as applicable) in obtaining any necessary licenses, permits or approvals from Regulatory Authorities with respect to the Manufacture of the applicable Collaboration CAR-T Products and corresponding Licensed Products at the applicable facilities; and (e) Caribou shall, and shall cause its Affiliates to, provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers to provide, such other assistance as AbbVie (or its Affiliate or designated Third Party Provider, as applicable) may reasonably request to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice each Manufacturing Process and otherwise to Manufacture the applicable Collaboration CAR-T Products and corresponding Licensed Products.
Development Services During the term of this Agreement, the Provider agrees to provide to or on behalf of the Port the professional services and related items described in Exhibit A (collectively, the “Development Services”) in accordance with the terms and conditions of this Agreement. The Provider specifically agrees to include at least one Port representative in any economic development negotiations or discussions in which the Provider is involved concerning (i) a port-related business prospect or (ii) a business transaction which will ultimately require Port involvement, financial or otherwise.
License; Use Upon delivery to an Authorized Person or a person reasonably believed by Custodian to be an Authorized Person of the Fund of software enabling the Fund to obtain access to the System (the “Software”), Custodian grants to the Fund a personal, nontransferable and nonexclusive license to use the Software solely for the purpose of transmitting Written Instructions, receiving reports, making inquiries or otherwise communicating with Custodian in connection with the Account(s). The Fund shall use the Software solely for its own internal and proper business purposes and not in the operation of a service bureau. Except as set forth herein, no license or right of any kind is granted to the Fund with respect to the Software. The Fund acknowledges that Custodian and its suppliers retain and have title and exclusive proprietary rights to the Software, including any trade secrets or other ideas, concepts, know-how, methodologies, or information incorporated therein and the exclusive rights to any copyrights, trademarks and patents (including registrations and applications for registration of either), or other statutory or legal protections available in respect thereof. The Fund further acknowledges that all or a part of the Software may be copyrighted or trademarked (or a registration or claim made therefor) by Custodian or its suppliers. The Fund shall not take any action with respect tot the Software inconsistent with the foregoing acknowledgement, nor shall the Fund attempt to decompile, reverse engineer or modify the Software. The Fund may not xxx, sell, lease or provide, directly or indirectly, any of the Software of any portion thereof to any other person or entity without Custodian’s prior written consent. The Fund may not remove any statutory copyright notice or other notice included in the Software or on any media containing the Software. The Fund shall reproduce any such notice on any reproduction of the Software and shall add any statutory copyright notice or other notice to the Software or media upon Custodian’s request.
Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.
Developer License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license for the number of Developer(s) indicated in the Order Form to install the Software on any number of Machines in order to internally use the Software to create, develop and test Applications. For clarity, a single Software license may be re-allocated to another Developer in the event that the original Developer is no longer employed by you or has been assigned to a new role where access to the Software will no longer be required on a permanent basis.
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.
Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.
DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK
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. 4.2 The Parties shall negotiate with each other to enter into specific technology license contracts to expressly specify the detail matters such as the technology to be licensed, the method to license the technology, license fees and payment.