Outage Management System Revised Straw Proposal Overview. October 31, 2013

Transcription

1 Outage Management System Revised Straw Proposal Overview October 31, 2013

2 Agenda Time Topic Speaker 1:00 1:10 Introduction, Stakeholder Process Kristina Osborne 1:10 3:45 OMS Revised Straw Proposal Review Heather Tegerdine, Rod Wheeler, Dave Douglass, Dede Subakti 3:45 4:00 Wrap-up and Next Steps Kristina Osborne

3 CAISO Stakeholder Initiative Process POLICY AND PLAN DEVELOPMENT TARIFF DEVELOPMENT This diagram represents the typical process, often stages will run in parallel. IMPLEMENTATION Paper Proposal Final Proposal Board Draft Tariff Final Tariff FERC Planning BPM Market Documents Revisions Simulation Go Live Stakeholder Input We are here AND We are here

4 Nature of Work Resource NoW changes Pmin Rerate Ramp Rate adjustment Short Notice Opportunity The intention is for these templates to be available with related Nature of Work types Example: Resource A has a NoW type of Plant Maintenance. A template will be available to report a Pmin rerate and a ramp rate adjustment for the work, as well as request an opportunity outage.

5 GADS Codes The Generator Availability Data System (GADS) Codes are used by the participants they will remain in OMS. They will, however, become an optional field on the outage.

6 De-Aggregation Resource Adequacy (RA) replacement and substitution will remain at the Plant level The following will also remain at the Plant level Stated Availability Pmin rerate Ramp rate rerate Multi-Stage Generation (MSG) will remain at the configuration level

7 Structured PTO Data CAISO will perform a mapping/association of transmission equipment between each PTO and the ISO. Where possible, normal isolation points will be premodeled by the CAISO and validated by the PTO for use during outage creation For equipment not pre-modeled, the PTO will identify isolation points

8 Transmission Mapping

9 Pre-Modeled/Mapping Example Line A-B The Transmission Registry name of the line is Line A-B Station A CB-1 CB-2 CB-3 Station B CB-7 CB-8 CB-9 CB-10 CB-11 CB-12 The following would be premodeled as associated with isolating Line A-B: CB-1 at Station A CB-2 at Station A CB-7 at Station B CB-8 at Station B

10 PTO Outage Processing Efficiencies Final Approval Not Required (FAN) A majority of the outages that are processed by real time operators have been through the standard outage lifecycle If work will begin and end as planned, low risk, low impact outages will not be required to request an additional real time approval prior to commencing work If not commencing as planned, PTO will keep times up to date per BPM for Outage Management and CAISO Operating Procedure This is no different than today.

11 PTO Outage Processing Efficiencies Final Approval Required (FAR) For outages with additional responsibilities or with higher risk or system impact, final approval by CAISO real time will be required prior to commencing work The current proposed Transmission FAR outages are: 500kV work Equipment out of service that impacts a path rating Outages with generation requirements Outages with flow limits associated Work that impacts relays The CAISO operator can also move an outage into this category

12 Planned Resource Outage Submittal Timeline To be considered Planned, an outage request must be submitted to the CAISO no later than Seven Days prior to the start date of the proposed Outage. The determination of seven day prior notice excludes the date of submission and the date of the outage.

13 Proposed RA Unit Substitution Changes After considering Stakeholder comments, the CAISO proposes the following changes that will reduce the impact of the seven day outage timeline to the Standard Capacity Product (SCP) Substitution Process: An approved outage request submitted 7 calendar days through 4 calendar days prior to the start of the outage will require local, likefor-like substitution capacity if available. If local, like-for-like substitution capacity is not available, system capacity will be accepted. An approved outage request submitted 3 calendar days or less prior to the outage start date will require local like-for-like substitution capacity.

14 Proposed RA Unit Substitution Changes In addition to the above noted changes, Many-to-Many SCP Substitution functionality will give Market Participants the capability to use one substitute unit to cover multiple forced RA outages.

15 Partial Forced Resource Outages An outage is considered Partial Forced if the scope of a Planned outage is increased in the Forced timeframe. Outage is extended past its scheduled end time Outage is rescheduled to start prior to scheduled start time Derate amount is increased above the value approved as planned outage. The outage change will be evaluated based on the time of the request and the start time of the change to be implemented

16 Example 1 Outage Extension request, Planned The above outage example shows an Approved Planned 16 day outage that is currently in progress. On Day 4 of the outage, the Scheduling Coordinator submits a request to extend the outage through Day 21.

17 Example 1 Outage Extension request, Planned Update Request Because this request does not go into effect until greater than seven days from the time of the request, the original outage card will be updated and remain Planned.

18 Example 2 Outage Extension request, Planned The above outage example shows an Approved Planned 16 day outage that is currently in progress. On Day 15 of the outage, the Scheduling Coordinator submits a request to extend the outage through Day 21.

19 Example 2 Outage Extension request, Forced Update Request Because this request goes into effect less than seven days from the time of the request, if approved the additional portion will require a new Forced outage card. The Planned outage will remain and may be linked to the associated Forced outage for tracking purposes.

20 Example 3 Additional curtailment request, Planned The above outage example shows an Approved Planned outage, scheduled to start on Day 12 with a 100MW curtailment on the resource. On Day 2, the Scheduling Coordinator requests an additional curtailment of 25MW for the duration of the outage

21 Example 3 Additional curtailment request, Planned Update Request Because this request does not go into effect until greater than seven days from the time of the request, the original outage card will be updated and remain Planned.

22 Example 4 Additional curtailment request, Forced The above outage example shows an Approved Planned outage, scheduled to start on Day 12 with a 100MW curtailment on the resource. On Day 10, the Scheduling Coordinator requests an additional curtailment of 25MW for the duration of the outage

23 Example 4 Additional curtailment request, Forced Update Request Because this request goes into effect less than seven days from the time of the request, if approved the additional portion will require a new Forced outage card. The Planned outage will remain Planned with a 100MW curtailment. The Forced outage will have a 25MW curtailment. The outages may be linked for tracking purposes.

24 Next Steps Stakeholder comments due on Revised Straw Proposal by November 7 th to: OMSCustomerInquiry@caiso.com The OMS Straw Proposal can be found at: OutageManagementSystemReplacement.pdf 12/3/13 Post Draft Final Proposal 12/10/13 Stakeholder web conference call 12/17/13 Stakeholder comments on Draft Final Proposal due February 2014 Board of Governors 24