Unit of Measure and Purchasing Requirements for Red Sample Clauses

Unit of Measure and Purchasing Requirements for Red. Hat Enterprise Linux Server
AutoNDA by SimpleDocs
Unit of Measure and Purchasing Requirements for Red. Hat Enterprise Linux Server You must purchase the appropriate number and type of Software Subscription(s) for each System that deploys, installs, uses or executes Red Hat Enterprise Linux Server including variants such as Red Hat Enterprise Linux Server for HPC Compute Nodes, for Power and for SAP, based on (1) the number of Socket-pairs and Virtual Guests when the Unit is a System; or (2) the number of vCPUs when the Unit is a vCPU. A “Socket-pair” is up to two sockets each occupied by a CPU on a System. A “Virtual Guest” is an instance of the Software that is executed or installed on a System that is a virtual machine. When you deploy a guest operating system in a virtualized environment, you are responsible for securing the required license rights for any third party operating systems or other software that you use.
Unit of Measure and Purchasing Requirements for Red. Hat Enterprise Linux Server You must purchase the appropriate number and type of Software Subscription(s) for each System that deploys, installs, uses or executes Red Hat Enterprise Linux Server (including Red Hat Enterprise Linux Server for HPC Compute Nodes, for Power and for SAP) based on (1) the number of Socket-pairs and Virtual Guests; or (2) with respect to System that Red Hat sells based on the number of vCPUs, the number of vCPUs.
Unit of Measure and Purchasing Requirements for Red. Hat Quay. Table 3 sets forth the Units of measure and Supported Use Cases for the Red Hat Quay Subscriptions. Red Hat Quay is an Add-On Subscription.
Unit of Measure and Purchasing Requirements for Red. Hat Storage Services. Table 3 sets forth the support level, Unit of measure and Supported Use Case for various Red Hat Data Services and Storage Subscriptions. You must purchase the appropriate number and type of these Software Subscriptions based on the Unit and other parameters described in Table 3 below. In addition, the following terms apply:
Unit of Measure and Purchasing Requirements for Red. Hat Advanced Cluster Security for Kubernetes. Table 4 sets forth the Units of Measure, Capacity limitations and Supported Use Cases for Red Hat Advanced Cluster Security for Kubernetes. You must purchase the appropriate number and type of Software Subscription(s) for each Unit, based on the Unit and other parameters described in Table 4. Table 4

Related to Unit of Measure and Purchasing Requirements for Red

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • COMPLETION OF MEET AND NEGOTIATE During the term of this Agreement, the parties waive and relinquish the right to meet and negotiate except as provided below and elsewhere in this Agreement, and agree that they shall not be obligated to meet and negotiate with respect to any subject or matter referred to or covered in this Agreement, nor on those subjects or matters which were proposed by either party and later withdrawn. Negotiations may be reopened at any time on any section of this contract on petition of either party and with the concurrence of the second party.

  • F1 Transfer and Sub-Contracting F1.1 Except where F1.4 and F1.5 applies, the Contractor shall not assign, sub- contract or in any other way dispose of the Contract or any part of it without prior Approval. Sub-contracting any part of the Contract shall not relieve the Contractor of any of its obligations or duties under the Contract.

  • ECR Number Environmental Commitment Record Requirements Description of ADOT Responsibilities TMP-3 The following measures will be implemented for the Selected Alternative: • All equipment exhaust systems will be in good working order. Properly designed engine enclosures and intake silencers will be used. • Equipment will be maintained on a regular basis. New equipment will be subject to new product emission standards. • Stationary equipment will be located as far away from sensitive receivers as possible. • Construction-related noise generators will be shielded from noise receivers (e.g., use temporary enclosures to shield generators or crushers, take advantage of site conditions to provide topographic separation). • Construction alerts will be distributed to keep the public informed of construction activities, and a toll-free number for construction-related complaints will be provided. • During the design phase, hours of operation will be evaluated to minimize disruptions during construction. ADOT to oversee for compliance TMP-4 Congestion from construction-related traffic will create temporary impacts in the project vicinity. The magnitude of these impacts will vary depending on the location of the sources of the fill material and of the disposition sites for surplus material, the land uses along the routes, the duration of hauling operations, staging locations, and the construction phasing. To identify acceptable routes and times of operation, ADOT, or its representative, will prepare an agreement with local agencies regarding hauling of construction materials on public streets. ADOT to oversee for compliance TP Attachment 000-0 Xxxxx Xxxxxxxx Xxxxxxx Project Record of Decision (ROD) Developer’s Environmental Commitment Requirements The following table includes the Project-specific environmental commitments as written in the ROD, with minor modifications for clarification purposes. As it relates to these Technical Provisions, references to freeway, project, South Mountain Freeway, proposed action, proposed freeway, and Selected Alternative mean the Project, and references to contractor mean Developer. Developer shall comply with and perform all of the contractor and ADOT requirements, including the ADOT obligations, commitments, and responsibilities, identified in the following table, except to the extent of those requirements that are specifically identified in the third column, entitled “Description of ADOT Responsibilities,” which are not delegated to Developer.

  • F4 Transfer and Sub-Contracting F4.1 Except where clauses F4.5 and F4.6 both apply, the Contractor shall not transfer, charge, assign, sub-contract or in any other way dispose of the Contract or any part of it without prior Approval. All such documents shall be evidenced in writing and shown to the Authority on request. Sub-contracting any part of the Contract shall not relieve the Contractor of any of its obligations or duties under the Contract.

  • Audit Requirements for Recipients of State Financial Assistance For purposes of this paragraph, the word "Contractor" shall be deemed to mean "nonstate entity," as that term is defined in section 4-230 of the Connecticut General Statutes. The Contractor shall provide for an annual financial audit acceptable to the Client Agency for any expenditure of State awarded funds made by the Contractor. Such audit shall include management letters and audit recommendations. The State Auditors of Public Accounts shall have access to all records and accounts for the fiscal year(s) in which the award was made. The Contractor shall comply with federal and State single audit standards as applicable.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Certain State Law Requirements for Contracts The contents of this Section are required by Texas Law and are included by County regardless of content.

  • Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.

  • Certification Regarding Termination of Contract for Non-Compliance (Tex Gov. Code 552.374)

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!