Trunk Provisioning Pursuant to Forecasts Sample Clauses

Trunk Provisioning Pursuant to Forecasts. Because BA’s trunking requirements will be dependent on the Customer segments and service segments within Customer segments to whom GNAPS decides to market its services, BA will be dependent on GNAPS to provide accurate trunk forecasts for both inbound (from BA) and outbound (from GNAPS) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate local traffic to GNAPS as GNAPS provides to terminate local traffic to BA, unless GNAPS expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks GNAPS suggests; provided, however, that in all cases BA’s provision of the forecasted number of trunks to GNAPS is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and GNAPS’s previous forecasts have proven to be reliable and accurate.
AutoNDA by SimpleDocs
Trunk Provisioning Pursuant to Forecasts. Because BA’s trunking requirements will be dependent on the Customer segments and service segments within Customer segments to whom Covad decides to market its services, BA will be dependent on Covad to provide accurate trunk forecasts for both inbound (from BA) and outbound (from Covad) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate local traffic to Covad as Covad provides to terminate local traffic to BA, unless Covad expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks Covad suggests; provided, however, that in all cases BA’s provision of the forecasted number of trunks to Covad is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and Covad’s previous forecasts have proven to be reliable and accurate.
Trunk Provisioning Pursuant to Forecasts. Because BA's trunking requirements will be dependent on the Customer segments and service segments within Customer segments to whom MGC decides to market its services, BA will be dependent on MGC to provide accurate trunk forecasts for both inbound (from BA) and outbound (from MGC) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate local traffic to MGC as MGC provides to terminate local traffic to BA, unless MGC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks MGC suggests; provided, however, that in all cases BA's provision of the forecasted number of trunks to MGC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and MGC's previous forecasts have proven to be reliable and accurate.
Trunk Provisioning Pursuant to Forecasts. BA will, as an initial matter and upon request, provide the same number of trunks to terminate Local Traffic to Transwire as Transwire provides to terminate Local Traffic to BA, unless Transwire expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks Transwire suggests; provided, however, that in all cases BA’s provision of the forecasted number of trunks to Transwire is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and Transwire’s previous forecasts have proven to be reliable and accurate.
Trunk Provisioning Pursuant to Forecasts. Because BA's trunking requirements will be dependent on the Customer segments and service segments within Customer segments to whom NCI decides to market its services, BA will be dependent on NCI to provide accurate trunk forecasts for both inbound (from BA) and outbound (from NCI) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate local traffic to NCI as NCI provides to terminate local traffic to BA, unless NCI expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks NCI suggests; provided, however, that in all cases BA's provision of the forecasted number of trunks to NCI is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and NCI's previous forecasts have proven to be reliable and accurate.

Related to Trunk Provisioning Pursuant to Forecasts

  • TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Additional Wet Weather Procedure 14.15.1 Remaining On Site a) for more than an accumulated total of four hours of ordinary time in any one day; or b) after the meal break, as provided for in clause 17.1 of the Award, for more than an accumulated total of 50% of the normal afternoon work time; or c) during the final two hours of the normal work day for more than an accumulated total of one hour, the Enterprise will not be entitled to require the employees to remain on site beyond the expiration of any of the above circumstances.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Operating Schedule Purchaser shall, be- fore commencing operations, provide in writing an annual Operating Schedule of anticipated major activities and needs for logging Included Timber, such as logging, road maintenance, Scaling, and road construction, including construction staking under B5.212 and material delivery under B5.22. Upon reasonable notice to Forest Service, such schedule shall be subject to modifications necessi- xxxxx by weather, markets, or other unpredictable circum- stances.

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (‘SLA’): (a) we are liable for any remedy or rebate allowed to you under the SLA; and (b) subject to clauses 34 to 38, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

  • Procedure for Termination, Amendment, Extension or Waiver A termination of this Agreement pursuant to Section 7.01, an amendment of this Agreement pursuant to Section 7.03 or an extension or waiver of this Agreement pursuant to Section 7.04 shall, in order to be effective, require in the case of Parent, Sub or the Company, action by its Board of Directors.

  • Service Level Commitment IBM provides the following service level commitment (“SLA”) for the Cloud Service, after IBM makes the Cloud Service available to you.

  • Agent’s Review of Proposed Amendments and Supplements Prior to amending or supplementing the Registration Statement (including any registration statement filed under Rule 462(b) under the Securities Act) or the Prospectus (excluding any amendment or supplement through incorporation of any report filed under the Exchange Act), the Company shall furnish to the Agent for review, a reasonable amount of time prior to the proposed time of filing or use thereof, a copy of each such proposed amendment or supplement, and the Company shall not file or use any such proposed amendment or supplement without the Agent’s prior consent, and to file with the Commission within the applicable period specified in Rule 424(b) under the Securities Act any prospectus required to be filed pursuant to such Rule.

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