FF&E Package. All Residential Condominium Units that are eligible to be a Participating Unit must be sold or furnished with a standard package of FF&E approved by Licensor for the Hotel.
FF&E Package Sample Clauses
Related to FF&E Package
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.
ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
Voice Grade Unbundled Copper Sub-Loop Unbundled Sub-Loop Distribution – Intrabuilding Network Cable (aka riser cable)
SPECIAL PACKAGING Items shall be packaged and cartoned so as to protect the contents from damage during shipment, handling and storage. Shipping container shall have a label with the following information: Name of Receiving Agency Agency Purchase Order Number Name of Supplier Item Description of Contents Manufacturer Name Model Name and Number
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.
Certain Characteristics of the Receivables (A) Each Receivable had a remaining maturity, as of the Cutoff Date, of not less than three (3) months and not more than eighty-four (84) months. (B) Each Receivable had an original maturity, as of the Cutoff Date, of not less than three (3) months and not more than eighty-four (84) months. (C) Each Receivable had a remaining Principal Balance, as of the Cutoff Date, of at least $250 and not more than $150,000. (D) Each Receivable had an Annual Percentage Rate, as of the Cutoff Date, of not more than 20%. (E) No Receivable was more than thirty (30) days past due as of the Cutoff Date. (F) Each Receivable arose under a Contract that is governed by the laws of the United States or any State thereof. (G) Each Obligor had a billing address in the United States or a United States territory as of the date of origination of the related Receivable. (H) Each Receivable is denominated in, and each Contract provides for payment in, United States dollars. (I) Each Receivable arose under a Contract that is assignable without the consent of, or notice to, the Obligor thereunder, and does not contain a confidentiality provision that purports to restrict the ability of the Servicer to exercise its rights under the Sale and Servicing Agreement, including, without limitation, its right to review the Contract. Each Receivable prohibits the sale or transfer of the Financed Vehicle without the consent of the Servicer. (J) Each Receivable arose under a Contract with respect to which GM Financial has performed all obligations required to be performed by it thereunder. (K) No automobile related to a Receivable was held in repossession inventory as of the Cutoff Date. (L) The Servicer’s records do not indicate that any Obligor was in bankruptcy as of the Cutoff Date. (M) No Obligor is the United States of America or any State or any agency, department, subdivision or instrumentality thereof.
Status of Seller The Seller is not an “investment company” within the meaning of the Investment Company Act of 1940, as amended. The Seller is not subject to regulation as a “holding company”, an “affiliate” of a “holding company”, or a “subsidiary company” of a “holding company”, within the meaning of the Public Utility Holding Company Act of 1935, as amended.
Purchases of Portfolio Shares for Sale to Customers (a) In offering and selling Portfolio shares to your customers, you agree to act as dealer for your own account; you are not authorized to act as agent for us or for any Portfolio.
WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-‐times or more the corresponding SLR, the RTT will be considered undefined.
