OpenShift Enterprise Broker Infrastructure Sample Clauses

OpenShift Enterprise Broker Infrastructure. Each OpenShift Enterprise deployment consisting of one or more Software Subscription(s) requires at least one OpenShift Enterprise Broker Infrastructure Software Subscription.
AutoNDA by SimpleDocs
OpenShift Enterprise Broker Infrastructure. Cada implantação de OpenShift Enteprise consiste de uma ou mais Subscrições de Software exige, pelo menos, uma Subscrição de Software OpenShift Enterprise Broker Infrastructure.
OpenShift Enterprise Broker Infrastructure. Chaque déploiement OpenShift Enterprise constitué d’une ou plusieurs Souscriptions de Logiciel nécessite au moins une Souscription de Logiciel OpenShift Enterprise Broker Infrastructure Software.
OpenShift Enterprise Broker Infrastructure. Jeder Einsatz von OpenShift Enteprise, der aus einer oder mehreren SOFTWARE SUBSCRIPTIONS besteht, erfordert mindestens eine OpenShift Enterprise Broker Infrastructure SOFTWARE SUBSCRIPTION.

Related to OpenShift Enterprise Broker Infrastructure

  • Red Hat Enterprise Linux Developer Suite Red Hat Enterprise Linux Developer Suite provides an open source development environment that consists of Red Hat Enterprise Linux with built-in development tools, certain Red Hat Enterprise Linux Add-Ons, Red Hat Enterprise Linux for Real Time, Smart Management and access to Software Maintenance, but no Development or Production Support. If you use any of the Subscription Services or Software associated with Red Hat Enterprise Linux Developer Suite for Production Purposes, or use the Red Hat Enterprise Linux Software Subscription entitlement independently, you agree to purchase the applicable number of Units of the applicable Software Subscription. Red Hat does not provide Production Support or Development Support for Red Hat Enterprise Developer Suite.

  • Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.

  • Partnership Working 7.1 Partnerships will be supported by local authorities on four levels between:

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Associated Enterprises (a) an enterprise of a Contracting State participates directly or indirectly in the management, control or capital of an enterprise of the other Contracting State, or

  • Indiana Veteran Owned Small Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran Owned Small Business Enterprise (“IVOSB”) participation plan, as detailed in the IVOSB Subcontractor Commitment Form, commonly referred to as “Attachment A-1” in the procurement documentation and incorporated by reference herein. Therefore, any changes to this information during the Contract term must be approved by IDOA’s IVOSB Division (“IVOSB Division”) and may require an amendment. It is the State’s expectation that the Contractor will meet the subcontractor commitments during the Contract term. The following certified IVOSB subcontractor(s) will be participating in this Contract: [Add additional IVOSBs using the same format.] IVOSB COMPANY NAME PHONE EMAIL OF CONTACT PERSON PERCENT Briefly describe the IVOSB service(s)/product(s) to be provided under this Contract and include the estimated date(s) for utilization during the Contract term: A copy of each subcontractor agreement must be submitted to the IVOSB Division within thirty (30) days of the effective date of this Contract. The subcontractor agreements may be uploaded into Pay Audit (Indiana’s subcontractor payment auditing system), emailed to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx, or mailed to IDOA, 000 X. Xxxxxxxxxx Street, Room W-478, Indianapolis, IN 46204. Failure to provide a copy of any subcontractor agreement may be deemed a violation of the rules governing IVOSB procurement and may result in sanctions allowable under 25 IAC 9-5-2. Requests for changes must be submitted to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx for review and approval before changing the participation plan submitted in connection with this Contract. The Contractor shall report payments made to certified IVOSB subcontractors under this Contract on a monthly basis using Pay Audit. The Contractor shall notify subcontractors that they must confirm payments received from the Contractor in Pay Audit. The Pay Audit system can be accessed on the IDOA webpage at: xxx.xx.xxx/xxxx/xxxx/xxxxxxxx.xxx. The Contractor may also be required to report IVOSB certified subcontractor payments directly to the IVOSB Division, as reasonably requested and in the format required by the IVOSB Division. The Contractor’s failure to comply with the provisions in this clause may be considered a material breach of the Contract.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Indiana Veteran’s Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran’s Business Enterprise (“IVBE”) participation plan. The following IVBE subcontractors will be participating in this Contract: VBE PHONE COMPANY NAME SCOPE OF PRODUCTS and/or SERVICES UTILIZATION DATE PERCENT _____________________________________________________________________________________ _____________________________________________________________________________________ A copy of each subcontractor agreement shall be submitted to IDOA within thirty (30) days of the request. Failure to provide any subcontractor agreement may also be considered a material breach of this Contract. The Contractor must obtain approval from IDOA before changing the IVBE participation plan submitted in connection with this Contract. The Contractor shall report payments made to IVBE subcontractors under this Contract on a monthly basis. Monthly reports shall be made using the online audit tool, commonly referred to as “Pay Audit.” IVBE subcontractor payments shall also be reported to IDOA as reasonably requested and in a format to be determined by IDOA.

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

Time is Money Join Law Insider Premium to draft better contracts faster.