Presentation is loading. Please wait.

Presentation is loading. Please wait.

Dynamic Schedule e-tagging Requirements Criterion WECC-087 (formerly INT-008) ISAS Report January 2012.

Similar presentations


Presentation on theme: "Dynamic Schedule e-tagging Requirements Criterion WECC-087 (formerly INT-008) ISAS Report January 2012."— Presentation transcript:

1 Dynamic Schedule e-tagging Requirements Criterion WECC-087 (formerly INT-008)
ISAS Report January 2012

2 Progress to date 2nd draft developed and posted
Comments received and discussed in Nov and Dec of 2011 Responses to comments posted Additional Web conferences planned on 2/9, 3/1, 3/15, 3/29 Details are located within the WECC-087 Team Site

3 WR1. Each Purchasing-Selling Entity (tag author) that submits a Request For Interchange (RFI) for a Dynamic Transfer shall specify the transaction type as either “dynamic” or “pseudo-tie”. WM1. Each Purchasing-Selling Entity that authors a Request For Interchange (RFI) for a Dynamic Transfer shall have and provide upon request, evidence that it specified the transaction type as either “dynamic” or “pseudo-tie” in accordance with WR1 above. Since Pseudo-ties by their very nature cross BA boundaries they must be tagged according to WR1. This ensures all impacted BAs have forecast information they need for reliability analysis and that energy transfer impacts to unscheduled flow are known.

4 WR2. Each Source Balancing Authority and each Sink Balancing Authority that are parties to an e-Tag for a Dynamic Transfer shall agree upon a single data source from which hourly energy values are obtained. WM2. Each Source Balancing Authority and each Sink Balancing Authority that are parties to an e-Tag for a Dynamic Transfer shall have and provide upon request, evidence that it agreed upon a single data source from which hourly energy values are obtained, in accordance with WR2. Evidence may include, but is not limited to, records, logs or multi-party agreements designating a specified metering point.

5 WR3. Each Purchasing-Selling Entity shall inform the Transmission Service Provider, via the Request For Interchange, of the transmission capacity required to serve the maximum flow of the Purchasing-Selling Entity’s Dynamic Transfer. WM3. Each Purchasing-Selling Entity shall have and provide upon request, evidence that it informed the Transmission Service Provider, via the Request-for-Interchange, of the transmission capacity required to serve the maximum flow of the Purchasing-Selling Entity’s Dynamic Transfer, in accordance with WR3. Evidence may include, but is not limited to, production of e-Tags reflecting the Dynamic Transfer, or other forms of communication if the e-Tagging system is not available.

6 WR4. Each Source Balancing Authority and each Sink Balancing Authority shall implement the Confirmed Interchange without exceeding either the transmission allocation profile or the reliability limit profile stated in the Confirmed Interchange. WM4. Each Source Balancing Authority and each Sink Balancing Authority shall have and produce upon request, evidence that during the operating hour the Implemented Interchange did not exceed either the transmission allocation profile or the reliability limit profile stated in the Confirmed Interchange, as required in WR4. Entities are free to use other systems (like CISO market system or flow based system) to manage transmission allocations while also meeting the requirement of WR4. The most limiting transmission allocation on the tag should be respected by the Source and Sink BAs

7 WR5. Each Balancing Authority shall exclude each Implemented Interchange of type “dynamic” from the Net Scheduled Interchange between Adjacent Balancing Authorities, until the completion of the current operating hour. WM5. Each Balancing Authority shall have and provide upon request, evidence showing that it excluded Implemented Interchange of type “dynamic” from the Net Scheduled Interchange between Adjacent Balancing Authorities and that the exclusion remained in place until the completion of the current operating hour, as required in WR5. Evidence may include, but is not limited to, review of control number records identifying the value used as the static component of Net Scheduled Interchange in the Area Control Error equation during the period examined.

8 WR6. Each Balancing Authority shall include each adjusted Implemented Interchange of type “dynamic” in the Net Scheduled Interchange between Adjacent Balancing Authorities. WM6. Each Balancing Authority shall have and provide upon request, evidence that it included in the Net Scheduled Interchange between Adjacent Balancing Authorities for the previous hour, each adjusted Implemented Interchange of type “dynamic”, pursuant WR6 above. Evidence may include, but is not limited to, production of Western Interchange Tool Net Scheduled Interchange values for the examined period or records from other internal systems.

9 WR7. Each Purchasing-Selling Entity that is a tag author, each Source Balancing Authority, and each Sink Balancing Authority, shall use the values obtained from WR2 above, to submit updates to the Dynamic Transfer energy profile with the final integrated energy value (MWh), within sixty minutes after the completion of the operating hour, to allow for correct Net Scheduled Interchange (NSI) between Balancing Authorities.

10 Guideline and Technical Basis
Please review this section It is very helpful in understanding the basic concepts and rationale for the requirements

11 Questions?


Download ppt "Dynamic Schedule e-tagging Requirements Criterion WECC-087 (formerly INT-008) ISAS Report January 2012."

Similar presentations


Ads by Google