Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
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.
CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to: request additional information reject Contract modifications remove Products from Contract modification requests request additional discounts for new or existing Products
Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.
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).
CERTIFICATION REGARDING USE OF CONTRACT FUNDS FOR LOBBYING This provision is applicable to all Federal-aid construction contracts and to all related subcontracts which exceed $100,000 (49 CFR 20).
Software Subscription Lifecycle During the life cycle of Red Hat Software, the scope of Software Maintenance and Support evolves and, after a number of years, we discontinue Software Maintenance and Support for older versions of Software. The details of the Software Maintenance and Production Support life cycle are set forth at xxxxx://xxxxxx.xxxxxx.xxx/support/policy/update_policies.html. If available, you may purchase Extended Update Support and/or Extended Life Cycle Support, as described in Exhibit 1.G, to extend your Subscription Services for certain versions of Software.
Sole Source as Grounds for Rejection of a Change Order If a Change Order is submitted to Contractor for the purposes of adding a Bulletin to this Contract and said Bulletin designates a Sole Source from which Contractor is required to procure goods or services necessary to perform the Work, which Sole Source has not been designated previously, Contractor shall be entitled to reject the proposed Change Order if the designated Sole Source refuses to provide to Contractor the warranties, bonds, terms or schedule required under the Contract Documents, including any warranty or terms or schedule required by Bulletins referenced in the proposed Change Order. In such event, Contractor shall give written notice to the Owner rejecting the proposed Change Order and, if possible, shall accompany said written notice with a proposal from Contractor for changes or modifications to the Bulletin so as to eliminate the Sole Source designation but to achieve goods or services equal in quality or function. The Owner may then require the Design Professional to revise the subject Bulletin so as to eliminate the designation of the Sole Source by incorporation of Contractor's proposal or otherwise. Upon revision of the Bulletin by the Design Professional and approval thereof by the Owner, the Owner shall again submit to the Contractor a proposed Change Order for the purpose of adding the revised Bulletin to this Contract. If the Owner decides to retain the Sole Source in the Change Order and Contractor cannot acquire the full contractually required warranties from the Sole Source, Contractor shall be held only to the warranty terms and schedule obtainable from the Sole Source.
Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
