Research question I Sample Clauses

Research question I. Assessment of unawareness
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs

Related to Research question I

  • Virginia Tech question Does the vendor acknowledge, agree, and understand that the terms and conditions of the RFP # 952642206 shall govern the contract if a contract is awarded to your company?

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

  • Technology Research Analyst Job# 1810 General Characteristics

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

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

  • Licensed Materials The materials that are the subject of this Agreement are set forth in Appendix A ("Licensed Materials").

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

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

  • Security of All Software Components Supplier will inventory all software components (including open source software) used in Deliverables, and provide such inventory to Accenture upon request. Supplier will assess whether any such components have any security defects or vulnerabilities that could lead to a Security Incident. Supplier will perform such assessment prior to providing Accenture with access to such software components and on an on-going basis thereafter during the term of the Agreement. Supplier will promptly notify Accenture of any identified security defect or vulnerability and remediate same in a timely manner. Supplier will promptly notify Accenture of its remediation plan. If remediation is not feasible in a timely manner, Supplier will replace the subject software component with a component that is not affected by a security defect or vulnerability and that does not reduce the overall functionality of the Deliverable(s).

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!