Forced Outage Slip Submissions Rule Interpretation (Action Item - - PowerPoint PPT Presentation

forced outage slip submissions rule interpretation action
SMART_READER_LITE
LIVE PREVIEW

Forced Outage Slip Submissions Rule Interpretation (Action Item - - PowerPoint PPT Presentation

Forced Outage Slip Submissions Rule Interpretation (Action Item 170-1) Carmela Phillips - Supervisor Compliance and Dispute Resolution Market Assessment and Compliance Division IESO Market Rules Requirements Chapter 5, section 1.2.5


slide-1
SLIDE 1

Forced Outage Slip Submissions Rule Interpretation (Action Item 170-1)

Carmela Phillips - Supervisor Compliance and Dispute Resolution Market Assessment and Compliance Division IESO

slide-2
SLIDE 2

Market Rules Requirements

Chapter 5, section 1.2.5

  • “…wherever this Chapter specifies that an

action is to be taken "promptly" or "immediately”, such action shall be taken…within five minutes, subject only to delay necessitated by concerns for the safety of equipment, employees, the public or the environment.”

slide-3
SLIDE 3

Market Rules Requirements

Chapter 5, section 3.6.1.3 and 6.3.4

  • promptly informing the IMO of any change or

anticipated change in the status of any generation facility or related equipment that …could have a material effect on the IMO-controlled grid or the

  • peration of the IMO-administered markets. Such

change shall include, but not be limited to, any change in status that could affect the maximum

  • utput of a generation unit, ..”
slide-4
SLIDE 4

Market Rules Requirements

Chapter 7, section 3.3.8

  • “…participant shall as soon as practical submit to

the IMO revised dispatch data for any registered facility in respect of which it is the registered market participant if, for any dispatch hour in the current pre-dispatch schedule, the quantity of any physical service scheduled for that registered facility differs from the quantity the registered market participant reasonably expects to be delivered or withdrawn…”

slide-5
SLIDE 5

Market Manual Requirements

Market Manual 7.3, “Outage Management”, section 1.3.8 - Forced Outages

  • “Market participants are required, as far in advance as

possible, to notify the IESO of any forced outage, using the

  • utage submission tools, and where necessary, by

telephoning the IESO. Where the forced outage has already occurred, the market participant is required to promptly telephone the IESO to notify them of the

  • ccurrence of the outage and to provide a brief

description of the nature and causes of the forced

  • utage…and then make the outage submission”
slide-6
SLIDE 6

Market Manual Requirements

Market Manual 7.3, “Outage Management”, section 1.3.9 - Forced Outages “A Generator whose outage or derating results in a change of the greater of 2% of rated output or 10 MW, is not required to revise their offers if the derating/

  • utage is expected to last less than 2
  • hours. “
slide-7
SLIDE 7

Interpretation

Generators

Chapter 5, section 6.3.4 and 3.6.1.3, the application of “promptly” refers to the notification of the forced outage and cause of forced outage There is no requirement on a generator to submit outage slips by a specific time for real time forced outages. There is a requirement to update dispatch data upon becoming aware of the outage for outage durations longer than 2 hour (outside of the restricted window). Revisions to dispatch data submissions within the restricted window are managed through outage slips (MM7.3, section 1.3.8)

slide-8
SLIDE 8

Compliance Cases

The following examination of past compliance cases are sector wide

  • No MP has been found in breach of an outage

submission requirement related to the timely submission

  • f an outage slip for forced outages.
  • No MP has not been given a specific time by which it

needs to submit real time forced outage slips in relation to a compliance investigation

  • Informal discussion: A reasonable period of time for

submission has been given to MPs of 15 minutes

slide-9
SLIDE 9

Compliance Cases – cont’d

  • MPs have been found in breach of Chapter 3.3.8 related

to dispatch data revisions outside of the restricted window due to lack of due diligence

  • MPs have been found in breach of prolonged (beyond

the restricted window) deviations from dispatch not resolved through changes to dispatch data

slide-10
SLIDE 10

Compliance Cases – cont’d

Outage related investigations and breaches

  • failure to notify of equipment return to service or

removal for outage, failure to promptly notify of reason for forced outages, failure to notify and submit outage for auxiliary system work, failure to notify of forced extension to planned outage.

  • Operating Reserve Activations failures where an outage

slip submission for a forced outage was not submitted in a timely matter related to a breach of Appendix 5.1, section 1.2.1 or 1.2.4, “an ancillary service provider

  • ffering …operating reserve…shall ensure that the

register facility …is available for dispatch as scheduled.”