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. 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 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), CLEC shall have the option to lease the Underutilized Trunk Group(s) and provided, further that in no case shall such disconnection by Verizon result in complete removal of all trunks between CLEC and a particular Verizon end point. If Verizon at BTLLC’s request does not disconnect trunks on an Underutilized Trunk Group and the trunk group does not have a utilization of at least sixty percent (60%), Verizon may xxxx BTLLC for the excess trunks and facilities at the applicable rates provided for in the Pricing Attachment; provided that Verizon shall not charge BTLLC for excess trunks and facilities pursuant to this sentence if the number of trunks in the Underutilized Trunk Group does not exceed the number of trunks in one DS-1 (i.e., 24 DS0 trunks).
Monitoring and Adjusting Forecasts. BA will, for ninety (90) days, monitor traffic on each trunk group that it establishes at NorthPoint’s suggestion or request pursuant to the procedures identified in Section‌‌
Monitoring and Adjusting Forecasts. Each Party will monitor traffic on each trunk group that it establishes at the other Party’s request. After establishing the TCBH, busy season, the parties shall review their forecasts and make any necessary adjustments to individual trunk groups to meet the established service criteria using industry accepted trunk servicing and forecasting techniques. Each Party will provide the other with peg count usage and overflow on trunk groups originating on its network. If one party believes particular trunk groups are underutilized, the parties will in good faith seek to make adjustments in order to optimize network utilization. If the Parties cannot reach agreement on such adjustments, either party may submit the dispute for resolution pursuant to Section 14.4 of the General Terms and Conditions.
Monitoring and Adjusting Forecasts. Verizon may, for ninety (90) days, monitor traffic on each trunk group that it establishes based on SBCT’s forecast. At the end of such ninety (90) day period, Verizon may disconnect trunks in trunk groups according to the provisions in Section 2.3.1.3.1 of the Interconnection Attachment for One-Way Interconnection Trunk groups and Section 2.4.12 of the Interconnection Attachment for Two-Way Interconnection Trunk groups. To the extent that Verizon has purchased any of these transport facilities from SBCT, SBCT shall waive any associated non- recurring and recurring charges (in the form of credits, refunds, or waiver of charges not billed).
Monitoring and Adjusting Forecasts. NPTC will, for ninety (90) days, monitor traffic on each trunk group that it establishes at MCIm’s suggestion or request pursuant to the procedures identified in this Section. At the end of such ninety-(90) day period, NPTC may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced subject to the limitations in Section 2.3 and Section 2.4 of this Interconnection Attachment.
Monitoring and Adjusting Forecasts. Verizon will, for ninety

Related to Monitoring and Adjusting Forecasts

  • Forecasting Manager and Sprint PCS will work cooperatively to generate mutually acceptable forecasts of important business metrics that they agree upon. The forecasts are for planning purposes only and do not constitute either party's obligation to meet the quantities forecast.

  • TRUNK FORECASTING 58.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Embarq shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Embarq twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include:

  • Quality Assurance The parties endorse the underlying principles of the Company’s Quality Management System, which seeks to ensure that its services are provided in a manner which best conforms to the requirements of the contract with its customer. This requires the Company to establish and maintain, implement, train and continuously improve its procedures and processes, and the employees to follow the procedures, document their compliance and participate in the improvement process. In particular, this will require employees to regularly and reliably fill out documentation and checklists to signify that work has been carried out in accordance with the customer’s specific requirements. Where necessary, training will be provided in these activities.