1Initial Forecasts/Trunking Requirements Sample Clauses

1Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom NTL decides to market its services, Verizon will be largely dependent on NTL to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter provide the same number of trunks to terminate Local Traffic to NTL as NTL provides to terminate Local Traffic to Verizon. At Verizon’s discretion, when NTL expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks NTL suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to NTL is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and NTL’s previous forecasts have proven to be reliable and accurate.
AutoNDA by SimpleDocs
1Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom SBCT decides to market its services, Verizon will be largely dependent on SBCT to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter provide the same number of trunks to terminate Reciprocal Compensation Traffic to SBCT as SBCT provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when SBCT expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon may provide the number of trunks SBCT suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to SBCT is conditioned on the following: that such forecast is based on reasonable engineering criteria, applicable blocking objectives, 'standard trunk traffic engineering methods' as described in Bell Communications Research, Inc. – Telcordia Technologies document SR TAP 000191 – Trunk Traffic Engineering Concepts and Applications, there are no capacity constraints, and SBCT’s previous forecasts have proven to be reliable and accurate.
1Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom XXX.xxx decides to market its services, Verizon will be largely dependent on XXX.xxx to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter provide the same number of trunks to terminate Local Traffic to XXX.xxx as XXX.xxx provides to terminate Local Traffic to Verizon. At Verizon’s discretion, when XXX.xxx expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks XXX.xxx suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to XXX.xxx is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and XXX.xxx’s previous forecasts have proven to be reliable and accurate.
1Initial Forecasts/Trunking Requirements. To the extent BTI does not have interconnection trunking established with Verizon, Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom BTI decides to market its services. Verizon will, as an initial matter, provide the same number of trunks to terminate Local Traffic to BTI as BTI provides to terminate Local Traffic to Verizon. Verizon will be largely dependent on BTI to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. At Verizon’s discretion, when BTI expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks BTI requests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to BTI is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and BTI’s previous forecasts have proven to be reasonably reliable and accurate.
1Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom TCCF decides to market its services, Verizon will be largely dependent on TCCF to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter provide the same number of trunks to terminate Local Traffic to TCCF as TCCF provides to terminate Local Traffic to Verizon. At Verizon’s discretion, when TCCF expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks TCCF suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to TCCF is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and TCCF’s previous forecasts have proven to be reliable and accurate.
1Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom LifeLine decides to market its services, Verizon will be largely dependent on LifeLine to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to LifeLine as LifeLine provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when LifeLine expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks LifeLine suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to LifeLine is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and LifeLine’s previous forecasts have proven to be reliable and accurate.
1Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom Excel decides to market its services, Verizon will be largely dependent on Excel to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to Excel as Excel provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when Excel expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks Excel suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to Excel is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and Excel’s previous forecasts have proven to be reliable and accurate.
AutoNDA by SimpleDocs

Related to 1Initial Forecasts/Trunking Requirements

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • 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.

  • Trunking Requirements 7.2.2.9.1 The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • 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).

  • Initial Trunk Forecast Requirements At least ninety (90) days before initiating interconnection in a LATA, Emergency shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Ongoing Trunk Forecast Requirements Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.

  • Metering Requirements Seller shall comply with all applicable rules in installing a meter appropriate for deliveries pursuant to the Full Buy/Sell or Excess Sale arrangement selected in paragraph 2.2, above, which can be electronically read daily by:

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