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).
Forecasting Requirements for Trunk Provisioning. Within ninety (90) days of executing this Agreement, Connectel 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 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 (Reciprocal Compensation Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for applicable Verizon Tandem and End Office switches to which Connectel wishes to send traffic and the technically feasible Points of Interconnection on Verizon’s network in a LATA at which the Parties will interconnect), interface type (e.g., DS1), and trunks in service each year (cumulative).
Forecasting Requirements for Trunk Provisioning. Within ninety (90) days of executing this Agreement, NorthPoint shall provide BA a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to BA over each of the Traffic Exchange Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to BA on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the BA 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 NorthPoint-IPs and BA-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).
Forecasting Requirements for Trunk Provisioning. Within ninety (90) days of executing this Agreement, Covad shall provide BA a one (1) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to BA over each of the Traffic Exchange Trunk groups over the next four (4) quarters. The forecast shall be updated and provided to BA on an as-needed but no less frequently than quarterly basis. All forecasts shall include Access Carrier Terminal Location (ACTL), traffic type (local/toll, operator services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Covad-IPs and BA-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).
Forecasting Requirements for Trunk Provisioning. Within ninety (90) days of executing this Agreement, ICG 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 Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon semiannually, and, to the extent commercially practicable, at such other times as may be reasonably requested by Verizon. 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 (Reciprocal Compensation Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for ICG-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).
Forecasting Requirements for Trunk Provisioning. Within ninety (90) days of executing this Agreement, MFN shall provide BA a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to BA over each of the Traffic Exchange Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to BA on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the BA 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 MFN-IPs and BA-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).
Forecasting Requirements for Trunk Provisioning. Within sixty (60) days of executing this Agreement, MFS shall provide BA a one (1) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to each of BA's End Offices affected by the exchange of traffic. The forecast shall be updated and provided to BA on a quarterly basis, and include Access Carrier Terminal Location (ACTL), traffic type (local/toll, operator services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes), interface type (e.g., DS1), and trunks in service each year (cumulative).
Forecasting Requirements for Trunk Provisioning. Within ninety (90) days of executing this Agreement, Covad shall provide BA a one (1) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to BA over each of the Traffic Exchange Trunk groups over the next four (4)
Forecasting Requirements for Trunk Provisioning. SPRINT shall provide a two (2) year traffic forecast (“Initial Forecast”) to VERIZON. SPRINT’s Initial Forecast shall provide the number of trunks for delivery of traffic to and from VERIZON over each Traffic Exchange Trunk group over the next eight (8) quarters. If SPRINT has not provided such Initial Forecast to VERIZON in February, 2001, SPRINT agrees to provide such Initial Forecast to VERIZON within forty-five (45) days of executing this Agreement. Thereafter, the Initial Forecast shall be updated, and forecasts shall be provided to VERIZON on an as-needed basis but no less frequently than semiannually in accordance with VERIZON’s forecasting cycle. 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 (Reciprocal Compensation Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for SPRINT-IPs and VERIZON-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative). In addition, the Parties will hold joint planning sessions, as needed, to address trunk engineering, utilization, and forecasting issues. At these meetings, subject to Section 19 of the General Terms and Conditions, the Parties will each share their historical trunk group usage data (and other applicable trunk group utilization data) for trunk groups dedicated to the other carrier. The Parties agree to work together cooperatively in: the establishment of new trunk groups; assessing utilization of, and sizing additions to, existing trunk groups; and, reducing trunk quantities for underutilized trunk groups.
Forecasting Requirements for Trunk Provisioning. Within ninety (90) days of executing this Agreement, each Party shall provide the other Party a one (1) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to BA over each of the Traffic Exchange Trunk groups over the next four (4)
