Limited Internal License for Development Purposes Sample Clauses

Limited Internal License for Development Purposes. Subject to this Agreement and Customer’s payment of all applicable fees, during the License Term, BlackBerry grants to Customer, under BlackBerry’s Intellectual Property Rights, a non-exclusive, non-transferable license to internally install, access, and/or use: 1) the Software Center (and any content BlackBerry makes accessible through the Software Center) strictly in support of the licenses granted to Customer herein and for no other purpose; and 2) the Software solely for Development Purposes and subject to the terms and conditions in this Agreement, including the specific rights, requirements, restrictions and limitations outlined in Exhibit A which apply to the particular licensing “model” relevant to the purchase (See Exhibit A for the rights, requirements, restrictions and limitations applicable to each relevant licensing model - e.g., Developer License, Build Server License, Floating License, Cloud Computing License, Project License, Evaluation License, or Early Access License) and the License Parameters identified in the relevant Order. The License Certificate that Customer obtains will specify the licensing “model” relevant to the purchase of any development license. The underlying software delivered as part of the Software Center shall be deemed “Software” for purposes of the general restrictions outlined in section 4.1.2, warranty disclaimers, and liability limitations identified in this Agreement. All such Software is provided “as is” without any warranties, representations or conditions of any kind.
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
Limited Internal License for Development Purposes. Subject to this Agreement and Customer’s payment of all applicable fees, during the License Term, BlackBerry grants to Customer, under BlackBerry’s Intellectual Property Rights, a non-exclusive, non-transferable license to internally install, access and/or use the Software solely for Development Purposes and subject to the terms and conditions in this Agreement, including the specific rights, requirements, restrictions and limitations outlined for the particular licensing “model” (See Exhibit A - e.g. Developer License, Build Server License, Floating License, Project License, Evaluation License, or Early Access License) and the License Parameters identified in the relevant Order. The License Certificate that Customer obtains will identify the license model relevant to the purchase. For clarity, and without limiting any other restrictions, none of the specific license models outlined herein include any rights of commercialization of the Customer Applications and/or Target Systems developed using the Software (beyond demonstration of the Customer Application(s) and/or Target System(s) to potential customers). Runtime Subsystem licenses for any such commercialization of Customer Applications and/or Target Systems must be obtained separately from BlackBerry.
Sample 1
Limited Internal License for Development Purposes. Subject to this Agreement and Customer’s payment of all applicable fees, during the License Term, BlackBerry grants to Customer, under BlackBerry’s Intellectual Property Rights, a non-exclusive, non-transferable license to internally install, access and/or use the Software solely for Development Purposes and subject to the terms and conditions in this Agreement, including the specific rights, requirements, restrictions and limitations outlined in Exhibit A which apply to the particular licensing “model” relevant to the purchase (See Exhibit A for the rights, requirements, restrictions and limitations applicable to each relevant licensing model - e.g., Developer License, Build Server License, Floating License, Project License, Evaluation License, or Early Access License) and the License Parameters identified in the relevant Order. The License Certificate that Customer obtains will specify the licensing “model” relevant to the purchase of any development license.
Sample 1

Related to Limited Internal License for Development Purposes

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

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Updated Information Submission by Developer The updated information submission by the Developer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. Developer shall submit a completed copy of the Large Generating Facility data requirements contained in Appendix 1 to the Large Facility Interconnection Procedures. It shall also include any additional information provided to Connecting Transmission Owner for the Interconnection Feasibility Study and Interconnection Facilities Study. Information in this submission shall be the most current Large Generating Facility design or expected performance data. Information submitted for stability models shall be compatible with NYISO standard models. If there is no compatible model, the Developer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Developer’s data is different from what was originally provided to Connecting Transmission Owner and NYISO pursuant to an Interconnection Study Agreement among Connecting Transmission Owner, NYISO and Developer and this difference may be reasonably expected to affect the other Parties’ facilities or the New York State Transmission System, but does not require the submission of a new Interconnection Request, then NYISO will conduct appropriate studies to determine the impact on the New York State Transmission System based on the actual data submitted pursuant to this Article 24.3. Such studies will provide an estimate of any additional modifications to the New York State Transmission System, Connecting Transmission Owner’s Attachment Facilities, or System Upgrade Facilities or System Deliverability Upgrades based on the actual data and a good faith estimate of the costs thereof. The Developer shall not begin Trial Operation until such studies are completed. The Developer shall be responsible for the cost of any modifications required by the actual data, including the cost of any required studies.

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

  • Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.

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

  • Certification Regarding Prohibition of Boycotting Israel (Tex Gov. Code 2271)

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.

  • Research Independence The Company acknowledges that each Underwriter’s research analysts and research departments, if any, are required to be independent from their respective investment banking divisions and are subject to certain regulations and internal policies, and that such Underwriter’s research analysts may hold and make statements or investment recommendations and/or publish research reports with respect to the Company and/or the offering that differ from the views of its investment bankers. The Company hereby waives and releases, to the fullest extent permitted by law, any claims that the Company may have against such Underwriter with respect to any conflict of interest that may arise from the fact that the views expressed by their independent research analysts and research departments may be different from or inconsistent with the views or advice communicated to the Company by such Underwriter’s investment banking divisions. The Company acknowledges that the Representative is a full service securities firm and as such from time to time, subject to applicable securities laws, may effect transactions for its own account or the account of its customers and hold long or short position in debt or equity securities of the Company.

  • Recognition of the U.S. Special Resolution Regimes (i) In the event that any Underwriter that is a Covered Entity becomes subject to a proceeding under a U.S. Special Resolution Regime, the transfer from such Underwriter of this Agreement, and any interest and obligation in or under this Agreement, will be effective to the same extent as the transfer would be effective under the U.S. Special Resolution Regime if this Agreement, and any such interest and obligation, were governed by the laws of the United States or a state of the United States. (ii) In the event that any Underwriter that is a Covered Entity or a BHC Act Affiliate of such Underwriter becomes subject to a proceeding under a U.S. Special Resolution Regime, Default Rights under this Agreement that may be exercised against such Underwriter are permitted to be exercised to no greater extent than such Default Rights could be exercised under the U.S. Special Resolution Regime if this Agreement were governed by the laws of the United States or a state of the United States. As used in this Section 16(e):

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