Forecasting Requirements. 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.
Forecasting Requirements. 2.2.1 Within ninety (90) days of executing the Agreement, PBX shall provide Frontier a two (2)-year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Frontier pursuant to this Attachment, over the next eight (8) quarters.
2.2.2 Ongoing forecast requirements. Where the Parties are already exchanging traffic through a Third Party Tandem Switch in a LATA, PBX shall provide a new or revised traffic forecast when PBX develops plans or becomes aware of information that will materially affect the Parties’ exchange of traffic through such Third Party Tandem Switch in that LATA. Instances that require a new or revised forecast include, but are not limited to: (i) PBX plans to deploy a new switch; (ii) PBX plans to implement interconnection in accordance with the Interconnection Attachment or a new network architecture; (iii) PBX plans to rearrange its network; or (iv) PBX expects a significant change in traffic volume.
Forecasting Requirements. 2.2.1 Within ninety (90) days of executing the Agreement, Onvoy shall provide Frontier a two (2)-year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Frontier pursuant to this Attachment, over the next eight (8) quarters.
2.2.2 Ongoing forecast requirements. Where the Parties are already exchanging traffic through a Third Party Tandem Switch in a LATA, Onvoy shall provide a new or revised traffic forecast when Onvoy develops plans or becomes aware of information that will materially affect the Parties’ exchange of traffic through such Third Party Tandem Switch in that LATA. Instances that require a new or revised forecast include, but are not limited to: (i) Onvoy plans to deploy a new switch; (ii) Onvoy plans to implement interconnection in accordance with the Interconnection Attachment or a new network architecture; (iii) Onvoy plans to rearrange its network; or (iv) Onvoy expects a significant change in traffic volume.
Forecasting Requirements. 5.6.1 The Parties shall exchange technical descriptions and forecasts of their interconnection and traffic requirements in sufficient detail necessary to establish the interconnections required to assure traffic completion to and from all customers in their respective designated service areas.
5.6.2 Both parties shall meet every six months or at otherwise mutually agreeable intervals for the purpose of exchanging non-binding forecast of its traffic and volume requirements for the interconnection and network elements provided under this Agreement, in the form and in such detail as agreed by the Parties. Section 5.6.3 contains guidelines regarding trunk forecasts, the forecast meetings and meeting intervals, that the Parties can use to form the basis of their agreement. The Parties agree that each forecast provided under this Section 5.6.2 shall be deemed “Confidential Information” under Section 9 of the General Terms and Conditions – Part A of this Agreement.
5.6.3 The trunk forecast should include trunk requirements for all of the interconnecting trunk groups for the current year plus the next two future years. The forecast meeting between the two companies may be a face- to-face meeting, video conference or audio conference. It may be held regionally or geographically. Ideally, these forecast meetings should be held at least semi-annually, or more often if the forecast is no longer usable. Updates to a forecast or portions thereof should be made whenever the Party providing the forecast deems that the latest trunk requirements exceed the original quantities by 24 trunks or 10%, whichever is greater. Either Party should notify the other Party if they have measurements indicating that a trunk group is exceeding its designed call carrying capacity and is impacting other trunk groups in the network. Also, either Party should notify the other Party if they know of situations in which the traffic load is expected to increase significantly and thus affect the interconnecting trunk requirements as well as the trunk requirements within the other Party’s network. The Parties agree that the forecast information provided under this Section shall be deemed “Confidential Information” under Section 9 of the General Terms and Conditions of this Agreement.
5.6.4 In addition to, and not in lieu of, the non-binding forecasts required by Section 5.6.2, a Party that is required pursuant to this Agreement to provide a forecast (the “Forecast Provider”) or a Party that is entit...
Forecasting Requirements. XIX-2 19.6 Certain Network Facilities ..................................................................................... XIX-3 19.7 Network Harm........................................................................................................ XIX-3 19.8 Insurance ................................................................................................................ XIX-4 19.9 Labor Relations ...................................................................................................... XIX-6 19.10 Good Faith Performance ........................................................................................ XIX-6 19.11 Responsibility to Customers .................................................................................. XIX-6 19.12 Unnecessary Facilities............................................................................................ XIX-6 19.13 NXX Code Administration .................................................................................... XIX-6 19.14 LERG Listings ....................................................................................................... XIX-6 19.15 LERG Use .............................................................................................................. XIX-6 19.16 Switch Programming.............................................................................................. XIX-6 19.17 OCNs….................................................................................................................. XIX-6 19.18 Transport Facilities................................................................................................. XIX-7 19.19 Change of Name..................................................................................................... XIX-7 19.20 Deposits ................................................................................................................. XIX-7 19.21 Expenses............................................................................................................... XIX-10 ARTICLE XX PROPRIETARY INFORMATION 20.1 Definition of Proprietary Information ..................................................................... XX-1 20.2 Disclosure and Use.................................................................................................. XX-2 20.3 Government Disclosure........................................................................................... XX-4 20.4 Ownership .......................
Forecasting Requirements. 5.6.1 The Parties shall exchange technical descriptions and forecasts of their interconnection and traffic requirements in sufficient detail necessary to establish the interconnections required to assure traffic completion to and from all customers in their respective designated service areas.
5.6.2 Within thirty (30) days after the Effective Date and each month during the term of this Agreement, each Party shall provide the other Party with a rolling, six (6) calendar month, non-binding forecast of its traffic and volume requirements for the interconnection and network elements provided under this Agreement, in the form and in such detail as agreed by the Parties. The Parties agree that each forecast provided under this Section 5.6.2 shall be deemed “Confidential Information” under Section 10.1 of the General Terms and Conditions – Part A of this Agreement.
5.6.3 In addition to, and not in lieu of, the non-binding forecasts required by Section 5.6.2, a Party that is required pursuant to this Agreement to provide a forecast (the “Forecast Provider”) or a Party that is entitled pursuant to this Agreement to receive a forecast (the “Forecast Recipient”) with respect to traffic and volume requirements for the services and network elements provided under this Agreement may request that the other Party enter into negotiations to establish a forecast (a “Binding Forecast”) that commits such Forecast Provider to purchase, and such Forecast Recipient to provide, a specified volume to be utilized as set forth in such Binding Forecast. The Forecast Provider and Forecast Recipient shall negotiate the terms of such Binding Forecast in good faith and shall include in such Binding Forecast provisions regarding price, quantity, liability for failure to perform under a Binding Forecast and any other terms desired by such Forecast Provider and Forecast Recipient. The Parties agree that each forecast provided under this Section 5.6.3 shall be deemed “Confidential Information” under Section
Forecasting Requirements. 1. Seller shall abide with all established requirements and procedures described below:
(a) Generating Facilities 1000 kW and greater must comply with the CAISO Tariff and Protocols while generating facilities under 1000 kW must comply with all applicable interconnection, communication and metering rules; and
(b) Generating Facilities 100 kW and greater must provide a weekly forecast of their expected generation output.
2. Weekly Energy Forecasting Procedures. Seller must meet all of the following requirements specified below: Beginning the Wednesday prior to the planned Initial Energy Delivery Date of the Generating Facility, and every Wednesday thereafter, Seller will electronically provide PG&E with an Energy Forecast for the next calendar week, by no later than 5 PM Wednesday of the week preceding the week covered by the Energy Forecast. The Weekly Energy Forecast submitted to PG&E shall:
a) Not include any anticipated or expected electric energy losses;
b) Be submitted using PG&E’s website at xxxxx://xxx.xxx.xxx/qic, or as otherwise instructed by PG&E;
c) Include Seller’s contact information;
d) Limit Day Ahead forecast changes to no less than 100 kW.
Forecasting Requirements. 1. Seller shall abide with all established requirements and procedures described below:
(a) Generating Facilities 1000 kW and greater must comply with the CAISO Tariff and Protocols while generating facilities under 1000 kW must comply with all applicable interconnection, communication and metering rules; and
(b) Generating Facilities 100 kW and greater must provide a weekly forecast of their expected generation output.
2. Weekly Energy Forecasting Procedures. Seller must meet all of the following requirements specified below: Beginning the Wednesday prior to the planned Initial Operation of the Generating Facility, Seller will electronically provide PG&E with an Energy Forecast for the next calendar week, by no later than 5 PM Wednesday of the week preceding the week covered by the Energy Forecast. The Weekly Energy Forecast submitted to PG&E shall:
a) Not include any anticipated or expected electric energy losses;
b) Be submitted using PG&E’s website at xxxxx://xxx.xxx.xxx/qic, or as otherwise instructed by PG&E;
c) Include Seller’s contact information;
d) Limit Day Ahead forecast changes to no less than 100 kW.
Forecasting Requirements. 2.2.1 Within ninety (90) days of executing the Agreement, Ygnition 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 pursuant to this Attachment, over the next eight (8) quarters.
2.2.2 Ongoing forecast requirements. Where the Parties are already exchanging traffic through a Third Party Tandem Switch in a LATA, Ygnition shall provide a new or revised traffic forecast when Ygnition develops plans or becomes aware of information that will materially affect the Parties’ exchange of traffic through such Third Party Tandem Switch in that LATA. Instances that require a new or revised forecast include, but are not limited to: (i) Ygnition plans to deploy a new switch; (ii) Ygnition plans to implement interconnection in accordance with the Interconnection Attachment or a new network architecture; (iii) Ygnition plans to rearrange its network; or (iv) Ygnition expects a significant change in traffic volume.
Forecasting Requirements. 2.4.1 Within ninety (90) days of executing the Agreement, WCL shall provide Frontier a two (2)-year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Frontier pursuant to this Attachment, over the next eight (8) quarters.
2.4.2 Ongoing forecast requirements. Where the Parties are already exchanging traffic through a Third Party Tandem Switch in a LATA, WCL shall provide a new or revised traffic forecast when WCL develops plans or becomes aware of information that will materially Tandem Switch in that LATA. Instances that require a new or revised forecast include, but are not limited to: (i) WCL plans to deploy a new switch; (ii) WCL plans to implement interconnection in accordance with the Interconnection Attachment or a new network architecture; (iii) WCL plans to rearrange its network; or (iv) WCL expects a significant change in traffic volume.
