Purchase Terms Subject to the satisfaction of the conditions set forth in Article VII, the parties agree as follows:
Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.
(b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program.
(c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only.
(d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use.
(e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient.
(f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor.
(g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient.
(h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes.
(i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5.
(j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.
Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
The Purchase Agreement This Agreement has been duly authorized, executed and delivered by the Company and the Guarantors.
Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.
MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.
Asset Purchase Agreement (a) Within fifteen (15) business days following PCC's receipt of the Put Notice or FBC's receipt of the Call Notice, as the case may be, FBC and PCC shall enter into the Asset Purchase Agreement in the form of Exhibit A hereto (the "Asset Purchase Agreement"), it being understood that the only change to such form shall be changes, if any, in the information contained in the Schedules thereto and the addition, if any, of Schedules thereto that are reasonably required to reflect events occurring after the date hereof; provided, however, that PCC shall not be required to accept any such change or addition that could reasonably be expected to cause a material adverse change in, or have a material adverse effect on, (i) the Assets to be conveyed to PCC pursuant to the Asset Purchase Agreement, (ii) the conduct of the business or operations of the Station or (iii) the ability of FBC to consummate the transactions contemplated by the Asset Purchase Agreement in accordance with its terms; provided further, however, that PCC shall be required to accept any change or addition of the type described in the preceding proviso if such change or addition results from any action taken (or, if required, not taken) by PCC under the Time Brokerage Agreement. Upon the execution and delivery of the Asset Purchase Agreement, FBC and PCC shall perform their respective obligations thereunder, including, without limitation, filing and prosecuting an appropriate application for FCC consent to the assignment of the FCC Licenses from FBC to PCC (the "FCC Consent"). Except as expressly set forth in the Time Brokerage Agreement or the Asset Purchase Agreement, PCC shall not assume any obligations or liabilities of FBC under any contract, agreement, license, permit or other instrument or arrangement.
(b) Notwithstanding Section 3(a) of this Option Agreement, in the event that, at the time of the exercise of the Put Option or the Call Option, as the case may be, the only assets held by FBC are (i) the assets to be conveyed to PCC pursuant to the Asset Purchase Agreement and (ii) the certain similar assets to be sold to Buyer pursuant to a certain Option Agreement bearing even date herewith with respect to Seller's New Orleans Station (as identified in such Option Agreement, the "New Orleans Option"), FBC may, at its election, notify PCC in writing that the transactions contemplated by the Asset Purchase Agreement and the New Orleans Option shall each be reconstituted as a sale to PCC of all of the capital stock of FBC (the "Stock Purchase Election"); provided, however, that FBC shall have no right to exercise the Stock Purchase Election if (i) PCC is unable to treat such purchase of stock as a purchase of assets pursuant to Internal Revenue Code ss. 338(h)(10), or its successor, as the same may be amended from time to time, and (ii) PCC and FBC are unable to agree upon the terms and conditions of, and execute and deliver, a Stock Purchase Agreement within thirty (30) days following PCC's receipt from FBC of written notice of its election to exercise the Stock Purchase Election. If FBC exercises the Stock Purchase Election in accordance with the terms of this Section 3(b), FBC and PCC shall negotiate in good faith the terms of the Stock Purchase Agreement, it being understood that such Stock Purchase Agreement shall be substantially equivalent to the Asset Purchase Agreement except for such modifications and additions thereto that are required to conform the Asset Purchase Agreement to the form of agreement customarily used in connection with a sale of capital stock rather than assets, and it being further understood that neither FBC nor PCC shall be required to accept any term or provision in the Stock Purchase Agreement that would, or could reasonably be expected to, result in any increase or decrease in the consideration payable by PCC under the Asset Purchase Agreement or in the liabilities to be assumed by PCC under the Asset Purchase Agreement.
DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.
Terms of the Purchase Agreement The terms of the Purchase Agreement, including, but not limited to, the representations, warranties, covenants, agreements and indemnities relating to the Assigned Contracts are incorporated herein by this reference. The parties hereto acknowledge and agree that the representations, warranties, covenants, agreements and indemnities contained in the Purchase Agreement shall not be superseded hereby but shall remain in full force and effect to the full extent provided therein. In the event of any conflict or inconsistency between the terms of the Purchase Agreement and the terms hereof, the terms of the Purchase Agreement shall govern.
Authorization Purchase and Sale Terms of the Private Placement Warrants A. Authorization of the Private Placement Warrants. The Company has duly authorized the issuance and sale of the Private Placement Warrants to the Purchaser.
