Common use of Forecasting Requirements for Trunk Provisioning Clause in Contracts

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. 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, 20012002, 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. 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 FebruaryAugust, 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 Telecommunications 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. 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 2002,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.