Licensing Record. A. The TLA will open a licensing record when an applicant submits an application or the TLA responds to a request for an application.
Licensing Record Sample Clauses
Related to Licensing Record
PRICE LISTS AND PRODUCT INFORMATION Contractors should provide an electronic version of the proposed price list in an Excel format or pdf on a jump drive. Also provide a dealer list, if applicable in an Excel format with "read and write" capabilities on the same jump drive. No costs or expenses associated with providing this information in the required format shall be charged to the State of Arkansas. At the time of contract renewal contractor will furnish OSP with an updated dealer list and published price list.
Developer License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license for the number of Developer(s) indicated in the Order Form to install the Software on any number of Machines in order to internally use the Software to create, develop and test Applications. For clarity, a single Software license may be re-allocated to another Developer in the event that the original Developer is no longer employed by you or has been assigned to a new role where access to the Software will no longer be required on a permanent basis.
SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.
Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.
Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet
End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).
Background Intellectual Property Notwithstanding and superseding anything to the contrary in this ARTICLE 14, each Party retains title to all Intellectual Property Rights owned or possessed by it or any of its affiliates prior to or independent of performance of this Agreement and used by it in fulfilling its obligations under this Agreement, as well as any modifications or improvements made thereto in the course of performing this Agreement (“Background IP”). To the extent that one Party acquires any right, title, or interest in and to any aspect of the modifications or improvements to the Background IP of the other Party, such first Party shall assign such right, title, and interest to the second Party, immediately following such acquisition. If any of the Supplier’s Background IP is included in or required to use the Documentation provided by the Supplier to the City, the Supplier hereby grants to the City an irrevocable, perpetual, fully paid-up, royalty-free, worldwide, transferable and non-exclusive licence (including the right to sub-licence only to members of the City’s Group) to, itself and through contractors and agents, use, copy, amend, reproduce, modify, create derivative works of, use, commercialize, and otherwise exploit the Supplier’s Background IP but only to the extent required to use such Documentation for the purpose (or any reasonably inferred purpose) for which it has been provided or for the provision of the Supply under this Agreement (excluding any software source code).
BACKGROUND AND INTRODUCTION The Federal-aid Highway Program (FAHP) is a federally-assisted program of State-selected projects. The Federal Highway Administration (FHWA) and the State Departments of Transportation have long worked as partners to deliver the FAHP in accordance with Federal requirements. In enacting 23 U.S.C. 106(c), as amended, Congress recognized the need to give the States more authority to carry out project responsibilities traditionally handled by FHWA. Congress also recognized the importance of a risk-based approach to FHWA oversight of the FAHP, establishing requirements in 23 U.S.C. 106(g). This Stewardship and Oversight (S&O) Agreement sets forth the agreement between the FHWA and the State of Florida Department of Transportation (FDOT) on the roles and responsibilities of the FHWA and the State DOT with respect to Title 23 project approvals and related responsibilities, and FAHP oversight activities. The scope of FHWA responsibilities, and the legal authority for State DOT assumption of FHWA responsibilities, developed over time. The U.S. Secretary of Transportation delegated responsibility to the Administrator of the FHWA for the FAHP under Title 23 of the United States Code, and associated laws. (49 CFR 1.84 and 1.85) The following legislation further outlines FHWA’s responsibilities: • Intermodal Surface Transportation Efficiency Act (ISTEA) of 1991; • Transportation Equity Act for the 21st Century (TEA-21) of 1998; • Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) of 2005; and • Moving Ahead for Progress in the 21st Century Act (MAP-21) of 2012 (P.L. 112-141). The FHWA may not assign or delegate its decision-making authority to a State Department of Transportation unless authorized by law. Xxxxxxx 000 xx Xxxxx 00, Xxxxxx Xxxxxx Code (Section 106), authorizes the State to assume specific project approvals. For projects that receive funding under Title 23, U.S.C., and are on the National Highway System (NHS) including projects on the Interstate System, the State may assume the responsibilities of the Secretary of the U.S. Department of Transportation under Title 23 for design, plans, specifications, estimates, contract awards, and inspections with respect to the projects unless the Secretary determines that the assumption is not appropriate. (23 U.S.C. 106(c)(1)) For projects under Title 23, U.S.C. that are not on the NHS, the State shall assume the responsibilities for design, plans, specifications, estimates, contract awards, and inspections unless the State determines that such assumption is not appropriate. (23 U.S.C. 106(c)(2)) For all other project activities which do not fall within the specific project approvals listed in Section 106 or are not otherwise authorized by law, the FHWA may authorize a State DOT to perform work needed to reach the FHWA decision point, or to implement FHWA’s decision. However such decisions themselves are reserved to FHWA. The authority given to the State DOT under Section 106(c)(1) and (2) is limited to specific project approvals listed herein. Nothing listed herein is intended to include assumption of FHWA’s decision-making authority regarding Title 23, U.S.C. eligibility or Federal-aid participation determinations. The FHWA always must make the final eligibility and participation decisions for the Federal-aid Highway Program. Section 106(c)(3) requires FHWA and the State DOT to enter into an agreement relating to the extent to which the State DOT assumes project responsibilities. This Stewardship and Oversight Agreement (S&O Agreement), includes information on specific project approvals and related responsibilities, and provides the requirements for FHWA oversight of the FAHP (Oversight Program), as required by 23 U.S.C. 106(g).
Licensed Materials The materials that are the subject of this Agreement are set forth in Appendix A ("Licensed Materials").
Intellectual Property Warranty CONTRACTOR represents and warrants that its performance of all obligations under this Contract does not infringe in any way, directly or contributorily, upon any third party’s intellectual property rights, including, without limitation, patent, copyright, trademark, trade secret, right of publicity and proprietary information.
