Monitoring and Adjusting Forecasts. Verizon will, for ninety (90) days, monitor traffic on each trunk group that it establishes at PNG’s suggestion or request pursuant to the procedures identified in Section 14.2 of this Attachment. At the end of such ninety-(90) day period, Verizon may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. If, after such initial ninety (90) day period for a trunk group, Verizon determines that any trunks in the trunk group in excess of two (2) DS-1s are not warranted by actual traffic volumes (considering engineering criteria for busy Centium Call Second (Hundred Call Second) and blocking percentages), then Verizon may hold PNG financially responsible for the excess facilities and disconnect such excess facilities.
Monitoring and Adjusting Forecasts. BA will, for ninety (90) days, monitor traffic on each trunk group that it establishes at Covad's suggestion or request pursuant to the procedures identified in subsection 10.3.1 above. At the end of such ninety (90) day period, BA may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. If, after such initial ninety (90) day period for a trunk group, BA determines that any trunks in the trunk group in excess of four (4) DS-1s are not warranted by actual traffic volumes (considering engineering criteria for busy hour CCIS and blocking percentages), then BA may hold Covad financially responsible for the excess facilities. In subsequent periods, BA may also monitor traffic for ninety (90) days on additional trunk groups that Covad suggests or requests BA to establish. If, after any such (90) day period, BA determines that any trunks in the trunk group are not warranted by actual traffic volumes (considering engineering criteria for busy hour CCIS and blocking percentages), then BA may hold Covad financially responsible for the excess facilities. At any time during the relevant ninety (90) day period, Covad may request that BA disconnect trunks to meet a revised forecast. In such instances, BA may hold Covad financially responsible for the disconnected trunks retroactive to the start of the ninety (90) day period through the date such trunks are disconnected.
Monitoring and Adjusting Forecasts. Verizon will, for ninety (90) days, monitor traffic on each trunk group that it establishes at GNAPs’ suggestion or request pursuant to the procedures identified in Section 14.3. At the end of such ninety-(90) day period, Verizon may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. If, after such initial ninety (90) day period for a trunk group, Verizon determines that any trunks in the trunk group in excess of two (2) DS-1s are not warranted by actual traffic volumes (considering engineering criteria for busy Centium Call Second (Hundred Call Second) and blocking percentages), then Verizon may hold GNAPs financially responsible for the excess facilities.
Monitoring and Adjusting Forecasts. Verizon will, for ninety (90) days, monitor traffic on each trunk group that it establishes at Reconex’s suggestion or request pursuant to the procedures identified in Section 13.3.1. At the end of such ninety-(90) day period, Verizon may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. If, after such initial ninety (90) day period for a trunk group, Verizon determines that any trunks in the trunk group in excess of two (2) DS-1s are not warranted by actual traffic volumes (considering engineering criteria for busy hour CCS and blocking percentages), then Verizon may hold Reconex financially responsible for the excess facilities.
Monitoring and Adjusting Forecasts. Verizon may monitor traffic on each trunk group that it establishes at pursuant to BTLLC’s forecast. For each trunk group with a utilization level of less than sixty percent (60%) (an “Underutilized Trunk Group”), unless the Parties agree otherwise, Verizon may notify BTLLC of its intent to disconnect a sufficient number of trunks to attain a utilization level of approximately sixty percent (60%) for each respective trunk group; provided that Verizon shall retain at least one (1) DS-1 (i.e., 24 DS0 trunks) in service for the trunk group),
Monitoring and Adjusting Forecasts. 10.3.3.1 For those LATAs where the Parties have previously provisioned Traffic Exchange Trunks, if the volume of traffic exchanged (i.e., the actual number of minutes exchanged in a particular month) between the Parties is out of balance (which, for the purposes of this Section 10.3.3 shall be defined as the volume of such traffic originating on one Party’s network being greater than three times the volume of such traffic originated on the other Party’s network), then the Party originating the lesser volume of traffic (“Party A”) shall provide the other Party (“Party B”) a non-binding trunk forecast in accordance with Section 10.3.1 for traffic in the inbound direction (i.e., terminating to Party A’s network).
Monitoring and Adjusting Forecasts. BA will, for ninety (90) days, monitor traffic on each trunk group that it establishes at Global’s suggestion or request pursuant to the procedures identified in Section 10.3.1. At the end of such ninety (90) day period, BA may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. If, after such initial ninety (90) day period for a trunk group, BA determines that any trunks in the trunk group in excess of four (4) DS-1s are not warranted by actual traffic volumes (considering engineering criteria for busy hour CCS and blocking percentages), then BA may hold Global financially responsible for the excess facilities. In subsequent periods, BA may also monitor traffic for ninety (90) days on additional trunk groups that Global suggests or requests BA to establish. If, after any such (90) day period, BA determines that any trunks in the trunk group are not warranted by actual traffic volumes (considering engineering criteria for busy hour CCS and blocking percentages), then BA may hold Global financially responsible for the excess facilities. At any time during the relevant ninety (90) day period, Global may request that BA disconnect trunks to meet a revised forecast. In such instances, BA may hold Global financially responsible for the disconnected trunks retroactive to the start of the ninety (90) day period through the date such trunks are disconnected.
Monitoring and Adjusting Forecasts. As soon as AT&T reasonably expects the volume of Local and intraLATA Toll traffic exchanged between the Parties to become out of balance (which, for the purposes of this Subsection 10.3.3 shall be defined as the volume of such traffic originating on Verizon's network being greater than three times the volume of such traffic originated on AT&T's network), then AT&T shall, as the Party originating the lesser volume of Local and intraLATA Toll traffic, provide to Verizon a trunk forecast in accordance with this Section 10.3 for Local and intraLATA Toll traffic in both directions (i.e., ingress and egressinbound and outbound). For the avoidance of any doubt, the preceding obligation to provide forecasts of another carrier's outbound traffic is imposed only on AT&T and not Verizon. If the volume of Local and intraLATA Toll traffic exchanged between the Parties is in balance (i.e., the volume of such traffic originating on one Party's network is no greater than three times the volume of such traffic originated on the other Party's network), then each Party shall provide the other Party a trunk forecast in accordance with this Section 10.3 for Local and intraLATA Toll traffic originating on its network (i.e., egress outbound only).
Monitoring and Adjusting Forecasts. HTC may, for ninety (90) days, monitor traffic on each trunk group that it establishes at LEVEL 3’s suggestion or request pursuant to the procedures identified in Section 9.4. At the end of such ninety-(90) day period, with thirty (30) days written notice to LEVEL 3, HTC may disconnect trunks that based on reasonable engineering criteria and capacity constraints are not warranted by the actual traffic volume experienced. If, after such initial ninety
Monitoring and Adjusting Forecasts. Verizon will, for ninety
