Exchange of Transmission and Generation Scheduled Outage Data Sample Clauses

Exchange of Transmission and Generation Scheduled Outage Data. Upon a Party’s request, the projected status of generation and transmission availability will be communicated among the Parties, subject to data confidentiality agreements. All requested and available information regardless of scheduled date will be shared. The Parties shall exchange the most current information on proposed Scheduled Outage information and provide a timely response on potential impacts of proposed Scheduled Outages. The Parties agree that this information will be shared promptly upon its availability, but no less than daily and more often as required by system conditions. The Parties shall utilize the NERC SDX (or other jointly developed, common format as determined by the OC) for the exchange of this information. The information shall include the data required for the SDX per NERC and Regional Reliability Standards. Each Party will also provide information independently on approved and anticipated Scheduled Outages formatted as required for the NERC SDX System. OUTAG --> PROGRESS-JOA 7.1 Operating Protocols for Coordinating Schedu --> PROGRESS-JOA 7.1.2 Evaluation and Coordination of Transmiss
AutoNDA by SimpleDocs
Exchange of Transmission and Generation Scheduled Outage Data. Upon a Party’s request, the projected status of generation and transmission availability shall be communicated among the Parties. The Parties shall exchange the most current information on proposed Scheduled Outage information and provide a timely response on potential impacts of proposed Scheduled Outages.
Exchange of Transmission and Generation Scheduled Outage Data. Upon a Party’s request, the projected status of generation and transmission availability shall be communicated among the Parties. The Parties shall exchange the most current information on proposed Scheduled Outage information and provide a timely response on potential impacts of proposed Scheduled Outages. The Parties shall share this information promptly upon its availability, but no less than daily and more often as required by system conditions. The Parties shall utilize a mutually agreed upon format for the exchange of this information, which includes the owning Party’s facility name; proposed Scheduled Outage start date and time; proposed facility return date and time; date and time when a response is needed from the impacted Party to modify the proposed schedule; and any other information that may be relevant to the reliability assessment. Each Party shall also provide information independently on approved and anticipated Scheduled Outages formatted as required for the SDX System.
Exchange of Transmission and Generation Scheduled Outage Data. Upon a Party’s request, the projected status of generation and transmission availability will be communicated among the Parties, subject to data confidentiality agreements. All requested and available information regardless of scheduled date will be shared. The Parties shall exchange the most current information on proposed Scheduled Outage information and provide a timely response on potential impacts of proposed Scheduled Outages. The Parties agree that this information will be shared promptly upon its availability, but no less than daily and more often as required by system conditions. The Parties shall utilize the NERC SDX (or other jointly developed, common format as determined by the OC) for the exchange of this information. The information shall include the data required for the SDX per NERC and Regional Reliability Standards. Each Party will also provide information independently on approved and anticipated Scheduled Outages formatted as required for the NERC SDX System. Effective Date: 9/17/2010 - Docket #: ER10-2746-000

Related to Exchange of Transmission and Generation Scheduled Outage Data

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 ARTICLE VII BLV/BLVI TRAFFIC 16 7.1 Busy Line Verification 16 7.2 Busy Line Verification Interrupt 16 7.3 BLV/BLVI Traffic 16 7.4 BLV/BLVI Compensation 16

  • Information Submission by Connecting Transmission Owner The initial information submission by Connecting Transmission Owner shall occur no later than one hundred eighty (180) Calendar Days prior to Trial Operation and shall include New York State Transmission System information necessary to allow the Developer to select equipment and meet any system protection and stability requirements, unless otherwise mutually agreed to by the Developer and Connecting Transmission Owner. On a monthly basis Connecting Transmission Owner shall provide Developer and NYISO a status report on the construction and installation of Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades, including, but not limited to, the following information: (1) progress to date; (2) a description of the activities since the last report; (3) a description of the action items for the next period; and (4) the delivery status of equipment ordered.

  • Transmission Delivery Service Implications Under ER Interconnection Service, Interconnection Customer will be eligible to inject power from the Generating Facility into and deliver power across the Transmission System on an “as available” basis up to the amount of MW identified in the applicable stability and steady state studies to the extent the upgrades initially required to qualify for ER Interconnection Service have been constructed. After that date FERC makes effective MISO’s Energy Market Tariff filed in Docket No. ER04-691-000, Interconnection Customer may place a bid to sell into the market up to the maximum identified Generating Facility output, subject to any conditions specified in the Interconnection Service approval, and the Generating Facility will be dispatched to the extent the Interconnection Customer’s bid clears. In all other instances, no transmission or other delivery service from the Generating Facility is assured, but Interconnection Customer may obtain Point-To-Point Transmission Service, Network Integration Transmission Service or be used for secondary network transmission service, pursuant to the Tariff, up to the maximum output identified in the stability and steady state studies. In those instances, in order for Interconnection Customer to obtain the right to deliver or inject energy beyond the Point of Interconnection or to improve its ability to do so, transmission delivery service must be obtained pursuant to the provisions of the Tariff. The Interconnection Customer’s ability to inject its Generating Facility output beyond the Point of Interconnection, therefore, will depend on the existing capacity of the Transmission or Distribution System as applicable, at such time as a Transmission Service request is made that would accommodate such delivery. The provision of Firm Point-To-Point Transmission Service or Network Integration Transmission Service may require the construction of additional Network or Distribution Upgrades.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.

  • Transmission and Routing of Telephone Exchange Service Traffic 50.4.1 The Appendix Reciprocal Compensation, which is/are attached hereto and incorporated herein by reference, prescribe traffic routing parameters for Local Interconnection Trunk Group(s) the Parties shall establish over the Interconnections specified in the Appendix ITR, which is/are attached hereto and incorporated herein by reference.

  • Connecting Transmission Owner’s Scope of Work and Responsibilities The Connecting Transmission Owner will design, construct, own, operate and maintain all Connecting Transmission Owner’s Interconnection Facilities, except as otherwise stated above and in the Project Specific Specifications. The Connecting Transmission Owner will complete all engineering reviews, field verifications and witness testing, etc. in accordance with the ESBs and the Project Specific Specifications. Connecting Transmission Owner shall provide the revenue metering CT/PT units and meter socket enclosure. The Connecting Transmission Owner shall: • provide, run, and wire both ends of the color-coded cable for the revenue metering instrument transformer secondary wiring; • perform all terminations; and • supply and install the meter. The revenue meter may require a communications link to the RTU. The Connecting Transmission Owner will specify and run those communications cables. The Connecting Transmission Owner shall complete all wiring, testing and commissioning of the RTU.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Ymax shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Ymax and Verizon. Ymax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx- Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and Xxxx shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’s performance in connection with these Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Ymax will route its traffic to Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the Verizon End Office.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!