Outage Management Process Redesign
The IESO is conducting a stakeholder engagement initiative to redesign its outage management process and tools. This redesign will focus on enhancements to outage-related services to market participants, as well as better align the IESO's process with its interconnected neighbours. The intent of the consultation is to ensure that those market participants who submit outage information to the IESO have an opportunity to provide feedback and input in the process redesign.
This redesign is in response to a preliminary review of outage processes along with discussions among stakeholders who identified objectives that will improve efficiencies in maintenance planning efforts, improve coordination among all customers and provide longer-term certainty on outage requests.
Outage Management Redesign Web Client User Guide (Final, October 26, 2016)
Outage Management Redesign Web Client Training Videos
This video demonstrates how to create an outage request and save it into draft status. The draft status is typically used for outage requests that are being planned but are not yet ready for submission to the IESO. Searching for draft outage requests is also shown.
2. Submitting a Planned Outage
This video demonstrates creating and submitting the most common type of outage request – a generic planned outage with an Out-of-service (OOS) constraint code and a continuous recurrence.
3. Submitting a Planned (Continuous) De-rating
Demonstrates creating and submitting a planned de-rating with a continuous recurrence – most commonly used to reflect the limited capability of a generating unit for a continuous period of time.
4. Submitting a Planned (Non-Continuous) De-rating
Demonstrates creating and submitting a planned de-rating with a non-continuous recurrence – typically used to reflect the capability of a generating unit during testing or as it ramps up or down from an outage.
5. Submitting a Planned Protection Outage
Demonstrates creating and submitting a planned outage to equipment protections using the new Protection Out-of-service (PROT OOS) constraint code. Also demonstrated is the automatic transition to Advance Approved status once a mandatory low-impact question is answered.
Demonstrates creating and submitting a planned outage to a generator AVR or PSS using the new AVR/PSS OOS constraint code. Also demonstrated is the automatic transition to Advance Approved status once a mandatory low-impact question is answered.
Demonstrates the conflict checking feature of the application when an outage is submitted in conflict with another outage (in accordance with IESO outage planning guidelines). The system displays a warning message describing the conflict and requires that rationale be provided to proceed with submission in the event the conflict cannot be avoided.
Demonstrates how to submit a non-critical outage into the new Weekly AA process. Indication that the request for Weekly AA was successful is also shown.
Demonstrates the Auto Advance Approval feature of the system using the new Breaker Fail Protection Out-of-service (BF PROT OOS) constraint code. Auto advance approval can only be granted after a series of low-impact questions are answered favourably.
Demonstrates both the Auto Advance Approval and Final Approval in Advance features of the system using the new HOLDOFF constraint code. Only a subset of Auto Advance Approved outages are also eligible to receive Final Approval in Advance. See Market Manual 7.3 for additional information about the FAA process.
Demonstrates retrieving an outage already in the Advance Approved status and saving it into a draft status. This feature can be used in situations where the outage applicant is no longer able to proceed with the outage request as originally planned but would like to retain the outage request for future use.
Demonstrates submitting an opportunity outage following an unsuccessful attempt to submit a planned outage once a submission deadline has passed. Opportunity outages should only be submitted if they present an unexpected opportunity to perform work and present a low risk to the power system (e.g. during surplus conditions for generator outages or improved weather conditions for transmitter outages).
Demonstrates creating and implementing a forced outage after providing an actual time of occurrence. Note that forced outages are unable to be submitted in advance. For advance notification of non-discretionary outages, the Urgent priority code is used. This video also demonstrates viewing a forced outage amongst other outages in the outage index view summary.
Demonstrates searching and selecting an outage in Final Approved status and then implementing (i.e. starting) the outage by applying an actual start time. Note that planned outages can only be implemented once the outage applicant has requested final approval from the IESO and the IESO has manually transitioned the outage request to Final Approved status.
Demonstrates how to force-extend an outage that is already implemented and is unable to be completed on time. For planned extensions, a new planned outage must be submitted to the IESO in accordance with the submission deadlines for planned outages.
Demonstrates searching and selecting an outage in the Implemented status and then completing (i.e. ending) the outage by applying an actual end time.
Demonstrates searching and selecting an outage in the Submitted status and then cancelling the outage after providing a reason for doing so.