License Diligence Sample Clauses

License Diligence. The License Agreement will include diligence criteria similar to the form of Appendix A. [Diligence will include .]
AutoNDA by SimpleDocs

Related to License Diligence

  • License Key 2.5. The Application Software may include an embedded security system which if provided must be used together with a license key. The license key may limit the use of the Application Software to the applicable Use Level and prevent a single User from using more than one workstation at the same time and is valid for a certain period of time following which the license key must be renewed. Customer is solely responsible for any cost or loss arising out of Customer’s failure or delay to renew the license key.

  • License Keys The Software, when used in production, requires a License Key to install or access it. You are responsible for the use of any License Key(s) assigned to you and must not share the License Key(s) with any third party. If your License Key is stolen, or if you suspect any improper or illegal usage of your License Key, you should promptly notify Acumatica of such occurrence. A replacement License Key will be issued to you and the compromised License Key will be disabled.

  • License Term The license term shall commence upon the License Effective Date, provided, however, that where an acceptance or trial period applies to the Product, the License Term shall be extended by the time period for testing, acceptance or trial.

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

  • SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:

  • Licensee Licensee represents and warrants that:

  • License of Intellectual Property Each Party (a “Licensor”) grants the other Party (a “Licensee”) the non-exclusive, royalty-free, paid-up, worldwide, irrevocable, right, during the term of this Agreement, to use the Licensor’s Intellectual Property solely for the purposes of this Agreement and to carry out the Party’s functions consistent with its responsibilities and authority as set forth in the enable legislation and regulations. Such licenses shall not give the Licensee any ownership interest in or rights to the Intellectual Property of the Licensor. Each Licensee agrees to abide by all third-party license and confidentiality restrictions or obligations applicable to the Licensor’s Intellectual Property of which the Licensor has notified the Licensee in writing.

  • Third Party Materials The Application may display, include, or make available third-party content (including data, information, applications, and other products, services, and/or materials) or provide links to third-party websites or services, including through third- party advertising ("Third-Party Materials"). You acknowledge and agree that Company is not responsible for Third-Party Materials, including their accuracy, completeness, timeliness, validity, copyright compliance, legality, decency, quality, or any other aspect thereof. Company does not assume and will not have any liability or responsibility to you or any other person or entity for any Third-Party Materials. Third-Party Materials and links thereto are provided solely as a convenience to you, and you access and use them entirely at your own risk and subject to such third parties' terms and conditions.

  • Licensed Products Lessee will obtain no title to Licensed Products which will at all times remain the property of the owner of the Licensed Products. A license from the owner may be required and it is Lessee's responsibility to obtain any required license before the use of the Licensed Products. Lessee agrees to treat the Licensed Products as confidential information of the owner, to observe all copyright restrictions, and not to reproduce or sell the Licensed Products.

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

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