Units of Measure and Purchasing Requirements Sample Clauses

The "Units of Measure and Purchasing Requirements" clause defines the standard units in which goods or services are quantified and the specific purchasing obligations of the parties. It typically outlines how products must be ordered (such as by weight, volume, or count) and may set minimum or maximum order quantities or frequency. This clause ensures both parties have a clear understanding of how transactions will be measured and fulfilled, reducing the risk of disputes over order sizes or delivery expectations.
Units of Measure and Purchasing Requirements. You must purchase the appropriate number and type of Red Hat Smart Management Subscriptions based on the Unit and Supported Use Cases described in Table 1 below.
View SourceView Similar (4)
Units of Measure and Purchasing Requirements. Table 2 sets forth the Unit of measure and Supported Use Cases for Red Hat Ansible Automation Platform Subscriptions. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 2 below.
View SourceView Similar (2)
Units of Measure and Purchasing Requirements. Table 2 sets forth the Unit of measure, stacking capabilities and Supported Use Cases for various Red Hat Management Subscriptions. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 2. For Virtual Nodes managed by CloudForms in a CloudForms enabled public cloud, you need to purchase Units equal to either (at your option), (a) the Table 2 Software Subscription Unit of Measure Capacity Stackable Use Case
View Source
Units of Measure and Purchasing Requirements. Table 2 sets forth the Unit of measure, stacking capabilities and Supported Use Cases for various Red Hat Management Subscriptions. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 2. For Virtual Nodes managed by CloudForms in a CloudForms enabled public cloud, you need to purchase Units equal to either (at your option), (a) the actual number of Units or (b) the average daily maximum Virtual Nodes managed by CloudForms in the previous 365 days. If 365 days of usage history is not available, you may use the average usage history period that is available. If managing Virtual Nodes on a public cloud, you must confirm that a specific public cloud is Red Hat CloudForms enabled.
View Source
Units of Measure and Purchasing Requirements. Table 3 sets forth the Unit of measure and Supported Use Cases for Red Hat Ansible Engine and Red Hat Ansible Tower Software. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 3 below.
View Source
Units of Measure and Purchasing Requirements. Table 3 sets forth the Unit of measure and Supported Use Cases for Red Hat Ansible Engine and Red
View Source

Related to Units of Measure and Purchasing Requirements

  • Entitlements and Purchasing Requirements You must purchase the appropriate number of Software Subscription(s), based on the number of Socket-pairs for all Managed Nodes being managed by the Red Hat CloudForms Software. A “Socket-pair” is up to two sockets each occupied by a CPU on a Managed Node. Red Hat CloudForms Software is configured to manage virtual machines on certain public clouds (a “Red Hat CloudForms Enabled Cloud”). You must purchase the appropriate number of Red Hat CloudForms for Public Cloud Software Subscriptions based on the number of Managed VMs instantiated on a Red Hat CloudForms Enabled Cloud. Please confirm that a specific public cloud is a Red Hat CloudForms Enabled Cloud prior to purchasing. A Red Hat Enterprise Linux Software Subscription is bundled with the Red Hat CloudForms Software Subscription and the fees for the Red Hat CloudForms Subscription are based on such bundled use. Any use of the Red Hat Enterprise Linux other than to run the Red Hat CloudForms Software is subject to Red Hat’s standard Software Subscription fees for such use.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Surviving Requirements The termination of this contract and payment of an amount in settlement as prescribed above shall extinguish the rights, duties, and obligations of the State and the Engineer under this contract, except for those provisions that establish responsibilities that extend beyond the contract period.

  • Vesting Requirements The vesting of this Award (other than pursuant to accelerated vesting in certain circumstances as provided in Section 3 below or vesting pursuant to Section 6 below) shall be subject to the satisfaction of the conditions set forth in each of subsections A and B, as applicable, and, in each case, subsection C of this Section 2:

  • Requirements Pertaining Only to Federal Grants and Subrecipient Agreements If this Agreement is a grant that is funded in whole or in part by Federal funds: