Research Support (a) Having regard to the resources reasonably available for such purposes, the Operator will cooperate with AHS to provide such participation by its Staff as may be reasonable in relation to the carrying out of research within the Province.
(b) The Operator agrees to promptly notify AHS in the event that it undertakes or agrees to participate in any form of clinical trial, research project, instrument use, or similar activity which in any way relates to the Services provided under this Agreement. The Operator shall, upon request, provide AHS with written evidence of Client disclosure and consent to research.
Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").
PRODUCT SUPPORT Partners may provide support for Products and other value-added services, and Partner is responsible for the performance of any services it provides. If Customer purchases Microsoft Support Services through a Partner, Microsoft will be responsible for the performance of those services subject to the terms of this Agreement.
Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:
Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date.
31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must:
31.2.1 work proactively and in good faith with each of the Buyer’s contractors
31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services
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.
Development Program RWJPRI shall be [**] and have [**] in consultation with the JDAC, to select LICENSED COMPOUNDS which shall then be designated PRODUCTS for further DEVELOPMENT by RWJPRI and marketing by ORTHO and its AFFILIATES. RWJPRI shall provide KOSAN with written notice of its decision to select a LICENSED COMPOUND for DEVELOPMENT. Once a PRODUCT has been selected for further DEVELOPMENT, RWJPRI, with the advice of the JDAC, shall have the [**] right to develop the PRODUCT through STAGES O, I, II and III and shall have the [**] right to prepare and file, and shall be the owner of, all applications for MARKETING AUTHORIZATION throughout the world. During such DEVELOPMENT efforts, KOSAN will assist RWJPRI as may be mutually agreed, at RWJPRI's expense, in chemical development, formulation development, production of labeled material and production of sufficient quantities of material for STAGE O and initial STAGE I studies. RWJPRI shall exercise diligent efforts, commensurate with the efforts it would normally exercise for products with similar potential sales volume and consistent with its overall business strategy, in developing such PRODUCT in accordance with the DEVELOPMENT PLAN established by RWJPRI. In the course of such efforts RWJPRI shall, either directly or through an AFFILIATE or SUBLICENSEE to which the license shall have been extended, take appropriate steps including the following:
(i) in consultation with the JDAC, select certain LICENSED COMPOUNDS for STAGE O DEVELOPMENT; and
(ii) establish and maintain a program reasonably designed, funded and resourced to obtain information adequate to enable the preparation and filing with an appropriate and properly empowered national regulatory authority all necessary documentation, data and [**] CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. other evidence required for IND non-rejection to commence and conduct human clinical trials of such PRODUCT.
(iii) proceed following IND non-rejection to commence PHASE I, II, and III clinical trials, associated studies and such other work which RWJPRI reasonably deems to be required for subsequent inclusion in filings for MARKETING AUTHORIZATION;
(iv) after such submissions are filed prosecute such submissions and file all reasonably necessary, reports and respond to all reasonable requests from the pertinent regulatory, authorities for information, data, samples, tests and the like.
Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.
(b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program.
(c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only.
(d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use.
(e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient.
(f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor.
(g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient.
(h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes.
(i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5.
(j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.
Technology Access Fee After the Effective Date, within [***] days after receipt of the corresponding invoice from Mersana, Merck will pay to Mersana, a one-time, non-refundable, non-creditable, upfront fee of Twelve Million Dollars ($12,000,000.00) (the “Technology Access Fee”). Payment of the Technology Access Fee shall be subject to any withholding Tax obligations set forth in Section 6.9.1.
Technical Support State Street will provide technical support to assist the Fund in using the System and the Data Access Services. The total amount of technical support provided by State Street shall not exceed 10 resource days per year. State Street shall provide such additional technical support as is expressly set forth in the fee schedule in effect from time to time between the parties (the “Fee Schedule”). Technical support, including during installation and testing, is subject to the fees and other terms set forth in the Fee Schedule.
