Monitoring and Adjusting Forecasts Sample Clauses

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 ATI’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) DS1s 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 ATI financially responsible for the excess facilities and disconnect such excess facilities.

Monitoring and Adjusting Forecasts. Verizon will, for ninety (90) days, monitor traffic on each trunk group that it establishes at FRCI’s suggestion or request pursuant to the procedures identified in Section 14.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 FRCI financially responsible for the excess facilities.

Monitoring and Adjusting Forecasts. Verizon will, for one hundred eighty (180) days, monitor traffic on each trunk group that it establishes at AT&T Broadband’s suggestion or request pursuant to the procedures identified in Section 10.4.1. At the end of such one hundred eighty (180) day period, after reasonable notice and an opportunity for discussion between the Parties, Verizon may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced, unless AT&T Broadband has substantiated the need for maintaining the underutilized trunk groups. If, after such initial one hundred eighty (180) day period for a trunk group, Verizon 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 Verizon may hold AT&T Broadband financially responsible for the excess facilities. In subsequent periods, Verizon may also monitor traffic for one hundred eighty (180) days on additional trunk groups that AT&T Broadband suggests or requests Verizon to establish. If, after any such one hundred eighty (180) days period, Verizon 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 Verizon may hold AT&T Broadband financially responsible for the excess facilities. At any time during the relevant one hundred eighty (180) day period, AT&T Broadband may request that Verizon disconnect trunks to meet a revised forecast. In such instances, Verizon may hold AT&T Broadband financially responsible for the disconnected trunks retroactive to the start of the one hundred eighty (180) days period through the date such trunks are disconnected.

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. Verizon will, for ninety

Monitoring and Adjusting Forecasts. STC may, for ninety (90) days, monitor traffic on each trunk group that it establishes at TCA’s suggestion or request pursuant to the procedures identified in Section 8.4. At the end of such ninety-(90) day period, with thirty (30) days written notice to TCA, STC 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, STC 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 STC may hold TCA financially responsible for the excess facilities at the STC intrastate access tariff rate for the services ordered by TCA.

Monitoring and Adjusting Forecasts. Verizon will, for ninety (90) days, monitor traffic on each trunk group that it establishes in response to EMW’s forecast pursuant to the procedures identified in Section 14.2 of this Attachment. If Verizon identifies a trunk group with a utilization level of less than 60 percent (60%), and determines that any trunks in the trunk group are not warranted by actual traffic volumes (considering engineering criteria for busy Centium Call Second (Hundred Call Second), reasonable engineering criteria and blocking percentages), then Verizon may bill EMW (and EMW shall pay Verizon) for the excess facilities carrying such trunks at the rates set forth in the Pricing Attachment and may disconnect such excess facilities.