License Requests Sample Clauses

License Requests. In order for Gas Party or Coal Party to exercise its License Use Rights, it shall request from the other Party specific licenses (each such license, a “License”). Each such request (a “License Request”) made pursuant to this Section 5.8 shall be made in writing and shall include (i) a description of the License being requested, including its specific purpose, and (ii) a description of the Surface Rights or other assets, as applicable, that would be affected by such License. Following the receipt of a License Request pursuant to this Section 5.8, the Party receiving such License Request shall use reasonable discretion (exercised in good faith) to determine if such License Request (x) is sufficiently specific in nature and (y) would not materially impair the value of the Surface Right or other asset which is subject to such License Request. Should the Party receiving such License Request be satisfied that both clause (x) and clause (y) of this Section 5.8 are satisfied by such requested License, and subject to any restrictions under applicable Existing Permits/Agreements and the other terms of this Agreement, such receiving Party shall prepare and deliver, without cost or fees to the other Party, such License; provided, however, such License shall contain language that it is non-exclusive and subject to (A) any applicable restrictions under any Existing Permits/Agreements, (B) the other terms of this Agreement, and (C) any applicable Laws.
AutoNDA by SimpleDocs
License Requests. All requests for a License shall be in writing to the APS Communications Systems Department and shall include a description of the route over which MTI desires to run Cable. When a request is submitted by MTI, APS may require that a field survey be conducted, at MTI’s expense, for the entire Cable route.

Related to License Requests

  • Sublicense Requirements Any Sublicense: (A) is subject to this Agreement; (B) will reflect that any sublicensee will not further sublicense; (C) will prohibit sublicensee from paying royalties to an escrow or other similar account; (D) will expressly include the provisions of Sections 8, 9, and 10 for the benefit of Stanford; and (E) will include the provisions of Section 4.4 and require the transfer of all the sublicensee’s obligations to *****, including the payment of royalties specified in the Sublicense, to Stanford or its designee, if this Agreement is terminated. If the sublicensee is a spin-out from *****, ***** must guarantee the sublicensee’s performance with respect to the payment of Stanford’s share of Sublicense royalties.

  • License Requirements The Hotel’s alcoholic beverage license requires that the Hotel shall: (i) request proper identification (photo ID) of any person of questionable age and refuse alcoholic beverage service if the person is either under age or proper identification cannot be produced, and (ii) refuse alcoholic beverage service to any person who, in the Hotel’s judgment, appears to be intoxicated; and (iii) instruct its personnel to avoid encouraging patrons to consume alcoholic beverages (commonly referred to as “over-pouring”).

  • Notice of a License Action Grantee shall notify their contract manager of any action impacting its license to provide services under this Contract within five days of becoming aware of the action and include the following: a. Reason for such action; b. Name and contact information of the local, state or federal department or agency or entity; x. Xxxx of the license action; and d. License or case reference number.

  • License Compliance HP may audit Customer compliance with the software license terms. Upon reasonable notice, HP may conduct an audit during normal business hours (with the auditor’s costs being at HP’s expense). If an audit reveals underpayments then Customer will pay to HP such underpayments. If underpayments discovered exceed five (5) percent of the contract price, Customer will reimburse HP for the auditor costs.

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

  • Minimum Vendor License Requirements Vendor shall maintain, in current status, all federal, state, and local licenses, bonds and permits required for the operation of the business conducted by Vendor. Vendor shall remain fully informed of and in compliance with all ordinances and regulations pertaining to the lawful provision of goods or services under the TIPS Agreement. TIPS and TIPS Members reserve the right to stop work and/or cancel a TIPS Sale or terminate this or any TIPS Sale Supplemental Agreement involving Vendor if Vendor’s license(s) required to perform under this Agreement or under the specific TIPS Sale have expired, lapsed, are suspended or terminated subject to a 30‐day cure period unless prohibited by applicable statue or regulation.

  • Sublicense Fees Licensee will pay Sublicense Fees indicated in Section 3.1(e) of the Patent & Technology License Agreement on or before the Quarterly Payment Deadline for the Contract Quarter.

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

  • License Scope Licensee is granted a non-exclusive, perpetual license to use, execute, reproduce, display, perform, or merge the Product within its business enterprise in the United States up to the maximum licensed capacity stated on the Purchase Order. Product may be accessed, used, executed, reproduced, displayed or performed up to the capacity measured by the applicable licensing unit stated on the Purchase Order (i.e., payroll size, number of employees, CPU, MIPS, MSU, concurrent user, workstation). Licensee shall have the right to use and distribute modifications or customizations of the Product to and for use by any Authorized Users otherwise licensed to use the Product, provided that any modifications, however extensive, shall not diminish Licensor’s proprietary title or interest. No license, right or interest in any trademark, trade name, or service xxxx is granted hereunder.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

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