Requesting Price Increase/Required Documentation Contractor must submit a written notification at least thirty (30) calendar days prior to the requested effective date of the change, setting the amount of the increase, along with an itemized list of any increased prices, showing the Contractor’s current price, revised price, the actual dollar difference and the percentage of the price increase by line item. Price change requests must include H-GAC Forms D Offered Item Pricing and E Options Pricing, or the documentation used to submit pricing in the original Response and be supported with substantive documentation (e.g. manufacturer's price increase notices, copies of invoices from suppliers, etc.) clearly showing that Contractor's actual costs have increased per the applicable line item bid. The Producer Price Index (PPI) may be used as partial justification, subject to approval by H-GAC, but no price increase based solely on an increase in the PPI will be allowed. This documentation should be submitted in Excel format to facilitate analysis and updating of the website. The letter and documentation must be sent to the Bids and Specifications manager, Xxxxxxx Xxxxxx, at Xxxxxxx.Xxxxxx@x-xxx.xxx Review/Approval of Requests If H-GAC approves the price increase, Contractor will be notified in writing; no price increase will be effective until Contractor receives this notice. If H-GAC does not approve Contractor’s price increase, Contractor may terminate its performance upon sixty (60) days advance written notice to H-GAC, however Contractor must fulfill any outstanding Purchase Orders. Termination of performance is Contractor’s only remedy if H-GAC does not approve the price increase. H-GAC reserves the right to accept or reject any price change request.
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.
Billing Increments Unless otherwise stated in a Service Order, usage-based charges will be billed on either a per-minute or per- message basis. Service calls invoiced on a per-minute basis will have an initial minimum call duration of one (1) minute, subsequent intervals of one (1) minute each, and will be billed by rounding to the next whole minute.
Optional Extended Local Calling Scope Arrangement Traffic (5) special access, private line, Frame Relay, ATM, or any other traffic that is not switched by the terminating Party; (6) Tandem Transit Traffic; (7) Voice Information Service Traffic (as defined in Section 5 of the Additional Services Attachment); or, (8) Virtual Foreign Exchange Traffic (or V/FX Traffic) (as defined in the Interconnection Attachment). For the purposes of this definition, a Verizon local calling area includes a Verizon non-optional Extended Local Calling Scope Arrangement, but does not include a Verizon optional Extended Local Calling Scope Arrangement.
Pricing Increase Requests Subsequent to the first twelve (12) months of the Contract term and in accordance with the schedule for price adjustments established by OGS, Contractor may request an increase in the pricing contained in the Centralized Contract by submitting an update request based on change in pricing level as contained in Appendix C, Contract Modification Procedure to the OGS Contract Administrator. With any price increase request, in addition to the requirements contained in Appendix C, the Contractor must certify in writing that the price change for the Services is the same as its pricing in its GSA Supply Schedule, and that Contractor documents the request to the satisfaction of the State.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the XxxxXxxxx XX 00000.
Longevity Increment All unit members who have completed the required years of District service, as defined below, shall be eligible to receive a longevity increment.
Longevity Increments 11.6.1 Each regular classified employee shall receive a two-range increase (5%) upon completion of five (5) years of satisfactory and continuous service. This increase will become effective at the beginning of the sixth year.
Anniversary Increments Employees shall advance on the wage grid on their anniversary date in the classification.
Data Transmission Control Except as necessary for the provision of the Cloud Services in accordance with the Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed-upon service levels (for example, encryption and lead-lined containers). Measures: • Personal Data in transfer over SAP internal networks is protected according to SAP Security Policy. • When data is transferred between SAP and its customers, the protection measures for the transferred Personal Data are mutually agreed upon and made part of the relevant agreement. This applies to both physical and network based data transfer. In any case, the Customer assumes responsibility for any data transfer once it is outside of SAP-controlled systems (e.g. data being transmitted outside the firewall of the SAP Data Center).
