Use Cases Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Supported Use Cases Subscription Services are provided for Red Hat Satellite Server, Red Hat Satellite Capsule and Red Hat Satellite Proxy Management Subscriptions only when used for their supported purposes (“Use Case”) in accordance with the terms of this Exhibit and Table 2 below.
Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.
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.
Early Construction of Base Case Facilities Developer may request Connecting Transmission Owner to construct, and Connecting Transmission Owner shall construct, subject to a binding cost allocation agreement reached in accordance with Attachment S to the ISO OATT, including Section 25.8.7 thereof, using Reasonable Efforts to accommodate Developer’s In-Service Date, all or any portion of any System Upgrade Facilities or System Deliverability Upgrades required for Developer to be interconnected to the New York State Transmission System which are included in the Base Case of the Class Year Study for the Developer, and which also are required to be constructed for another Developer, but where such construction is not scheduled to be completed in time to achieve Developer’s In-Service Date.
Participating TO’s Interconnection Facilities The Participating TO shall design, procure, construct, install, own and/or control the Participating TO’s Interconnection Facilities described in Appendix A at the sole expense of the Interconnection Customer. Unless the Participating TO elects to fund the capital for the Participating TO’s Interconnection Facilities, they shall be solely funded by the Interconnection Customer.
CONSTRUCTION/PUBLIC WORKS CONTRACTS In compliance with Article 8, Section 220 of the New York State Labor Law:
Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
