Source Code Escrow Pursuant to 62 O.S. § 34.31, if customized computer software is developed or modified exclusively for a State agency, the Supplier has a continuing obligation to comply with such law and place the source code for such software and any modifications thereto into escrow with an independent third party escrow agent. Supplier shall pay all fees charged by the escrow agent and enter into an escrow agreement, the terms of which are subject to the prior written approval of the State, including terms that provide the State receives ownership of all escrowed source code upon the occurrence of any of the following:
Minerals All minerals, crops, timber, trees, shrubs, flowers and landscaping features now or hereafter located on, under or above Land;
Commingling The Seller shall not, and shall not permit any of its Affiliates to, deposit or permit the deposit of any funds that do not constitute Collections of any Loan Asset into the Interest Collection Subaccount or the Principal Collection Subaccount.
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.
Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters).
Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.
MINES The Contractor represents and warrants that neither it, its parent entities (if any), nor any of the Contractor’s subsidiaries or affiliated entities (if any) is engaged in the sale or manufacture of anti-personnel mines or components utilized in the manufacture of anti-personnel mines.
Delivery at Closing At the Closing, the Company will deliver to the Purchaser a stock certificate registered in the Purchaser’s name, representing the number of Shares to be purchased by Purchaser hereunder, against payment of the purchase price therefore as indicated above.
Transit Traffic The following rates will apply:
Transit Service is the delivery of certain traffic between Carrier and a third party ILEC, CLEC or CMRS provider by Frontier over a separate trunk group between Carrier and Frontier where appropriate trunks exist between Carrier and third party through Frontier’s tandem. The following traffic types will be delivered: (I) Local Traffic originated from Carrier to such third-party and (ii) Local Traffic originated from such third-party to Frontier’s tandem and terminated to Carrier.
