Redispatch Cost Posting to allow for posting of third party offers of planning redispatch services

Redispatch Cost Posting Excerpt from Order 890, paragraph 1139: …We therefore are adopting, as explained above, a requirement that transmission providers modify their OASIS to allow for the posting of third party offers to supply planning redispatch. This OASIS posting requirement does not obligate transmission providers to incorporate bids from third parties into their redispatch; rather, posting of third party offers to provide redispatch may be used by transmission customers to secure planning redispatch provided the appropriate agreements are reached between the customer, third party redispatch provider, transmission provider and reliability coordinator.

Redispatch Cost Posting BPS ASSIGNMENT:   NAESB Business Practices Subcommittee (BPS) has been assigned to work on determining what information related to the planning redispatch should be posted on OASIS. Based on the explanation above, BPS is proposing that the following information should be posted on OASIS for third party planning redispatch offers as applicable (see exemption per WEQ-001-C.3): Generating Unit(s) Identification Incremental and Decremental pair if applicable Amount of Capacity over time Flowgate(s) where congestion can be relieved (if available) Cost (optional) Host Control Area

Redispatch Cost Posting From the October 2017 OASIS meeting: OASIS Scope: The OASIS subcommittee will develop templates for posting the information identified by the BPS. No Business Practice Standards will be developed to require posting of offers for third party planning redispatch. The OASIS subcommittee recommends the development of two templates for posting third party planning redispatch offers. One template will be used to capture generator information that may be used in a redispatch offer (Items 1 and 6 from the BPS list). The other template will show the actual offer parameters (items 2-5 from the BPS list). The third party will register one or more generators and then reference those generators when posting offers for planning redispatch. This approach means that the third party won’t be required to include generator information every time an offer is made.

Redispatch Cost Posting Recommendation summary: WEQ-001 Establishes requirement for TPs to support postings in WEQ-001-13 OASIS GENERAL POSTING BUSINESS PRACTICE STANDARDS Recognizes that the posting constitutes a non-binding offer Relieves the TP from any responsibility to review or validate the offer

Redispatch Cost Posting Recommendation summary (continued): WEQ-002 Updated 002-4.3.1 Template Summary to show the new templates are in 4.3.10 Informal Messages New Templates 4.3.10.7 Third Party Offering of Planning Redispatch query/response (redispatchoffering) 4.3.10.8 Third Party Planning Redispatch Offer Posting (redispatchpost) 4.3.10.9 Third Party Planning Redispatch Generation query/response (redispatchgen) 4.3.10.10 Third Party Planning Redispatch Generation Posting (redispatchgenpost)

Redispatch Cost Posting Recommendation summary (continued): WEQ-002 Updated 002-4.3.11 OASIS Audit Log redispatchofferingaudit redispatchgenaudit Updated 002-6 Implementation Plan Updated 002-6.1 Data Element Conversion and Cross Reference

Redispatch Cost Posting Recommendation summary (continued): WEQ-003 (Data Dictionary) CAPACITY – modified definition CONGESTION_RELIEF – new definition GEN_AREA – modified definition GEN_DESCRIPTION – modified definition GEN_INTERCONNECTION – new definition GEN_NAME – modified definition GEN_REF – new definition GEN_REF_DEC – new definition GEN_REF_INC – new definition GEN_STATUS – new definition OFFER_START_TIME – modified definition OFFER_STOP_TIME – modified definition REDISPATCH_DESCRIPTION – new definition REDISPATCH_PRICE – new definition REDISPATCH_REF – new definition

Redispatch Cost Posting Recommendation summary (continued): WEQ-013 x013-3.9 redispatchoffering/redispatchpost x013-3.10 redispatchgen/redispatchgenpost

Discussion Topics REDISPATCH_PRICE is free form to allow flexibility in how one described the costs for redispatch – not just a numeric dollar figure. Pros/cons? Should CAPACITY be replaced with new free form REDISPATCH_CAPACITY to allow more flexibility in describing the amount of redispatch available? Should Generator information (GEN_NAME, etc.) be returned in redispatchoffering rather than just referencing registered generation posting? GEN_INTERCONNECTION is included; this has been discussed and various opinions on whether it should be included or not. Final disposition - in or out? Others?