Post on 01-Mar-2021
NODAL MARKET EDUCATIONNODAL MARKET EDUCATION
Outage Scheduler
Legal Disclaimer
Protocol DisclaimerThi t ti id l i f th TThis presentation provides a general overview of the Texas Nodal Market Implementation and is not intended to be a substitute for the ERCOT Nodal Protocols as amendedsubstitute for the ERCOT Nodal Protocols, as amended from time to time. If any conflict exists between this presentation and the ERCOT Nodal Protocols, the ERCOTpresentation and the ERCOT Nodal Protocols, the ERCOT Nodal Protocols shall control in all respects.
For more information, please visit:
http://nodal.ercot.com/protocols/index.html
Slide 2
http://nodal.ercot.com/protocols/index.html
Legal Admonition
Antitrust AdmonitionERCOT t i tl hibit k t ti i t d th iERCOT strictly prohibits market participants and their employees, who are participating in ERCOT activities, from using their participation in ERCOT activities as a forum forusing their participation in ERCOT activities as a forum for engaging in practices or communications that violate antitrust laws. The ERCOT Board has approved guidelines forlaws. The ERCOT Board has approved guidelines for Members of ERCOT Committees, subcommittees, and working groups to be reviewed and followed by each market participant attending ERCOT meetings.
Slide 3
Housekeeping
• Restrooms• Refreshmentse es e s• Attendance sheet• Breaks • Questions• Evaluation
Pl ff ll hPlease turn off cell phones & other electronics
Slide 4
Course Outline
• Market Participant Outage Scheduler User Interface
O t E t R l d E l• Outage Entry Rules and Examples• ERCOT Outage Scheduler Interface• Outage Reports• Outage Reports• Outage information on the MIS
Slide 5
Objectives
• Review ERCOT market rules for outage coordination
• Describe roles and responsibilities of ERCOT and Market Participants
• Demonstrate and discuss how TSP & QSE outages are• Demonstrate and discuss how TSP & QSE outages are entered into the Outage Scheduler.
• Briefly demonstrate the OS User Guides for QSEs and TSPsBriefly demonstrate the OS User Guides for QSEs and TSPs
• Briefly demonstrate the OS WBTs for QSEs and TSPs
• Discuss Outage Reports• Discuss Outage Reports.
• Discuss accessing Outage information on the MIS
Slide 6
External Web Services
Notable Feature• External Web Services (EWS) allow TSPs and QSEs with
Resources to exchange outage data in XML format• File upload with return feature in Requestor User InterfaceAll Outage Coordination and Scheduling rules apply to EWSAll Outage Coordination and Scheduling rules apply to EWS
Users!
XML
Slide 7
Outage Scheduler User Interface
Outage Scheduler
What is the Outage Scheduler?• Critical application used by• Critical application used by
QSEs and TSPs to submit notifications or requests for outages to ERCOT
Requirement• Energization or removal of equipment in the Network
Operations Model requires submission in Outage SchedulerScheduler
Slide 9
Outage Coordination
What Do Congestion
Revenue RightsCongestion
Revenue RightsCRR AwardsPTP Awards
Outages Affect?
Day-Ahead Day-Ahead
Energy AwardsAncillary Service AwardsSecurity AnalysisReliability Unit Commitment
Adjustment Period Adjustment Period
Outage Evaluation
OUTAGESOUTAGESSecurity AnalysisAS DeploymentReliability Unit CommitmentReliability Unit CommitmentOutage Evaluation
Real-TimeReal-TimeRT Security AnalysisSCEDReal-Time Real-Time SCED Forced Outage Detection
SettlementsP t R l TiP t R l Ti
Slide 10
Outage ReportsPost Real TimePost Real Time
Outage Types
There are two outage categories: Transmission and ResourceResource
Transmission Resource
Planned
Maintenance
Planned
Maintenance
1
212
Forced
Remedial Sw.
Forced
Opportunity
34
34
Opportunity
Simple
5
6
Slide 11
p6
Transmission Outage Rules
TSPs can view all transmission and resource outagesresource outages.•A TSP may create a transmission outage for any operating company, station or y p g p y,equipment.
•A TSP can not create a resource outage.
•A TSP can not change the name of the requesting company. That is tied to the digital certificatedigital certificate.
•A TSP can not edit an outage created by another requesting company
Slide 12
another requesting company.
Resource Outage Rules
• QSEs may only schedule and view outages submitted by their company for the Resources in their portfolioin their portfolio
• Must log in separately for sub-QSEs.
QSE t i t i i t• QSEs cannot view transmission outages inside the Outage Scheduler.
• QSEs can access Approved Accepted• QSEs can access Approved, Accepted, Proposed and Rejected outages in the MIS.
• Scheduled outages on Resource Entity-g yowned Transmission Assets must be scheduled by a TSP on behalf of the QSE (per TSP submittal rules)
Slide 13
(per TSP submittal rules).
Logging On
• Access OS from Market Information System (MIS)Digital Certificate required• Digital Certificate required
• For multiple Digital Certificates, must select one
Slide 14
Logging On
• Multiple Outage Scheduler windows which are totally independent of one another may be opened in separateindependent of one another may be opened in separate browser sessions.
• MIS automatically logs out after 30 minutes of inactivity –click the OS Refresh often - in each open session! Any non-submitted requests in any open sessions will be lost!non submitted requests in any open sessions will be lost!
• For QSEs: All of the Resources in their portfolio will be available Must log in separately for Sub-QSEs
Slide 15
Summary Screen
Slide 16
Summary Screen
• 25 outages are displayed per page.• Summary Screen will display up to 7000 outages.• Use Custom Filter to find particular outages.• Use Page Arrows at bottom to page up and down the requests
Slide 17
Summary Screen
Default sort order is determined by:
• Current Date falls within the Planned start to Planned End periodp• Request Date – based on the time of submission
Slide 18
Summary Screen – Sorting Column Data
• Columns may be sorted in ascending and descending order.• To reverse the sort, click the column heading area• All data will be re sorted based on the selected column• All data will be re-sorted based on the selected column• For multiple levels of sorting, export the data to a .csv spreadsheet.
Click on the Column Heading area to re-sortre sort
Slide 19
Summary Screen
Click OS Refresh often due to 30 Minute Timeout Rule
Slide 20
Summary Screen
Printing Summary Information
Slide 21
Print Information Summary
Insert Printed Summary example here.
Slide 22
Summary Screen
Exporting Data fieldsExporting Data fields
Slide 23
Summary Screen – Export .xml format
Information shown represents One (1) OutageOne (1) Outage
Slide 24
Summary Screen – Export.csv format
Slide 25
Summary Screen – Export.csv format
Slide 26
TSP Outage Selection Screen
Slide 27
QSE Outage Selection Screen
Slide 28
TSP Create Outage Screen
General Information is pre-populated from digital certificate.
Acme Electric Use pull down to select other TSP Operating Companies.
Slide 29
QSE Create Outage Screen
General InformationGeneral Information is pre-populated from digital certificate.
512-222-1234
For QSEs – Operating Company cannot be changed. Must Log in separately for sub-QSEs
Slide 30
QSE Create Outage Screen
Remembers the last phone number entered from previous session.
This should be the number you wouldRequired Field
This should be the number you would want an ERCOT Outage Coordinator or System Operator to contact you at!
Slide 31
Create Outage Screen
TSP Required Data
Slide 32
Create Outage Screen
QSE Required Data
Slide 33
Create Outage Screen
Using the Calendar Widget:• enter PS first – automatically populates ES, PE and LEy p p ,• Entering PE automatically populates LE• Revising PS or PE automatically populates ES or LE
Manually entering data into any field revises that field only!
Slide 34
Outage Entry Screen
Detailed instruction on using the Calendar Widget may be found in:
• Section 7 of the QSE or TSE Outage Scheduler Users Guides• Section 7 of the QSE or TSE Outage Scheduler Users Guides• The New Outages > Enter New Outages section of the Outage Scheduler Web-Based Training module.
Slide 35
Create Outage Screen
Nature of Work Pull-down• Required Field• Pre-populated with generic e popu ated t ge e c
TSP or QSE types of work.
Slide 36
Nature of Work Pulldowns
Transmission Outages Resource OutagesAssociated Equipment OutageBreaker Maintenance
Black Start TestBoroscopeCLine Maintenance
Line Rebuild/UpgradeRelay Work Repair Hot Spot
Combustion Inspection and RepairCooling Water Problems/RepairsExhaust Problems/RepairsFeedwater Problems/Repairs
Repair/Replace Damaged EquipmentReplace EquipmentSwitch MaintenanceSwitch Repair/Replace
Fuel Limitation/Lack of Fuel AvailabilityFuel Problems/RepairsGas Company Pipeline WorkInlet Air Problems/Repairs
Transformer MaintenanceTransformer Repair/ReplaceTransformer TestingNew Equipment Energization
Lack of Steam Load AvailabilityMothballedOverhaulSteam Turbine Limited/Unavailableq p g
Retirement of Old EquipmentOther*Unknown*
Tube LeakTurbine/Generator Vibration/RepairNew Equipment EnergizationRetirement of Old Equipment
Slide 37
Retirement of Old EquipmentOther*Unknown** Enter reason in Requestor Notes
Emergency Restoration
TSP Required Data Only• Whole numbers only – no decimals.y• Cannot be longer than the outage duration• Rounds up for fractional hours (i.e. 8.5 hour outage
equals a 9 hour maximum restoration valueequals a 9 hour maximum restoration value
Slide 38
Project Name Field
• TSP Outage Types only.g yp y• Not a required field• Use to relate outages to a project• Up to 16 Characters
Slide 39
Selecting Equipment Fields
• Top down Hierarchyp y• Select Station first to pre-populate lower fields• Select additional equipment to create Group Outages• Higher selections clear lower fields
Slide 40
Selecting Equipment Fields
TSP Equipment Type Code Definition
CB Circuit Breaker
LN LineLN Line
DSC Disconnect
XF Transformer
SC Series Compensator
LD Load
SVC Static Var Compensator
QSE Equipment Type Code Definition
UN Unit
LR Load Resource
Slide 41
Recurring Outages
Note: For TSP & QSE Planned Outages –cannot use Recurring and Group feature at the same time.
Recurring Outages• Defaults to No
Slide 42
Recurring Outages
Maximum of50 Occurrences
2010
Repeats Field – decide first if outage is Weekly or
Maximum duration is 24 hours
first if outage is Weekly or Periodic
Slide 43
Recurring Outages
4 3
x x x
2010 08
x x
4
Slide 44
Recurring Outages
4 3
x
2010 08
x
Slide 45
Recurring Outages
IMPORTANT NOTE:• Validate dates before submittal!
O S b itt d h t b
Slide 46
• Once Submitted – each outage becomes a separate, stand-alone outage request!
Recurring Outages
2010
Repeats Periodically field
Slide 47
Recurring Outages
Planned Start Date is always the first outage plus…
8 14 1
2010 08
Slide 48
Recurring Outages
Planned Start date counts as one outage plus
8 4 3
2010 08
Slide 49
Recurring Outages
Planned Start date counts as one outage plus
Again - IMPORTANT NOTE:• Validate dates before submittal!• Once Submitted – each outage becomes a
Slide 50
gseparate, stand-alone outage request!
TSP Grouped Outage Example
Station B
BS 1Station U
Station A O
AS-1 AB-1 AS-2
BS-1
BS-2
BB-1
-A Line ABStation G
Station C
O
OAS-3 AB-2 AS-4
AB 3
Bus
-A
S-5
Line AB
Line AD Station F
C
Station DC
AS-6 AB-3 AS-7
AS-8 AB-4 AS-9
Bus
-B C
Segment AC
SegmentCF
SegmentFGC
C O O
C C C
C
Station E
OEB-1 ES-1EG-1 Line AG Outage
Slide 51
C C CStation E
QSE Grouped Outage Example
TSP Owned Resource Owned
L04
S040
CD03
C CT03
MT03QSE
B1 B2 B3 CD02
S040
C200 CT02
XT02MT02
C300 CT03
B4 B5 B6 SD01
200
S100 ST01
MT01
L01 L02 L03
S010 S020 S030XT01
MT01
Slide 52
Grouped Outages
• Submitted as a Group• Evaluated and Approved/Rejected as a Group• May be Cancelled as a Group• Actual Start and Actual End times apply to all outages in the group
• Group Name required if multiple Equipment selected
• Defines grouped outage• Up to 8 Characters
N t lid t d i t b• Not validated against – may be duplicated
30 Max
Slide 53
Associated Equipment
Associated Equipment table expandsp
Slide 54
Outage State
Selected Equipment always defaults to the state opposite theSelected Equipment always defaults to the state opposite the Normal State defined in the Network Operations Model
Slide 55
Entering & Viewing Notes
If no Notes section is collapsedIf no Notes, section is collapsed
Click on the Blue Arrow to Expand or Collapse the Notes section
Slide 56
Enter/View Notes
Requestor Notes• Enter reason when using “Other” or
“Unknown” for Nature of Work• For Supplemental Information• Up to 1000 characters
Slide 57
Enter/View Notes
• Previously submitted Notes appear with date/time stamp.• Cannot be edited or removed.• Original Notes only will be included if Copied
Slide 58
Enter/View Notes
RAP or SPS Notes• Required if disabling or impacting a
Remedial Action Plan or SpecialRemedial Action Plan or Special Protection System
• TSPs only• Up to 1000 charactersUp to 1000 characters
Slide 59
Special Protection Systems & Remedial Action Plans
Important: the following TSP actions are required if outages impact a Remedial Action Plan or Special Protection Systemimpact a Remedial Action Plan or Special Protection System.
•Enter information in the Notes area shown below.
•Email notes to OPSOutageCoordination@ercot com•Email notes to OPSOutageCoordination@ercot.com.
Call ERCOT Outage Coordination at 512-248-6841 if additional explanation is necessary.additional explanation is necessary.
Slide 60
Enter/View Notes
Supporting Information• Explanation of how an outage qualifies as a forced outage• Up to 1000 characters
R i d b f t i A t l E d f ll f d t t• Required before entering Actual End for all forced outage types:– Forced outages– Forced Extensions
Unavoidable Extensions– Unavoidable Extensions– Remedial Switching Actions
Slide 61
Enter/View Notes
ERCOT Reviewer NotesR d O l• Read Only
Slide 62
May 5, 2009 Sys. Coordinator. Rejected due to conflicting outages.
System Validation
When submitting Outage requests, validation checks for:• Conflicting existing outages• Conflicting existing outages• Required fields are complete
Error Messages are unique!
Slide 63
Cancellation & Withdrawal of Outage Rules
ERCOT can review & withdraw approval to ensure reliabilityB f A l f Aft A l freliabilityBefore Approval of
OutageAfter Approval of
Outage
ERCOT can reject outage ERCOT can withdraw outage
TSP or QSE can cancel TSP or QSE can cancel outageoutage TSP or QSE can cancel outage
Slide 64
Withdrawal of Approved Outages
Withdrawal of Inactive Outage • No Actual Start entered• No Actual Start entered• Status changes to Withdrawn• All fields become read-onlyAll fields become read only
Withdrawal of Active Outage• Actual Start entered• Actual Start entered• Status changes to Withdrawn • All fields are read-only, except for Actual End, which must y, p ,
be entered by the Requesting Entity
Slide 65
Canceling Outages
• Coordinating with ERCOT• Reschedule date unknown• Reschedule within next
season• Will not reschedule
Slide 66
Canceling Outages
• Outage must be inactive (No Actual Start entered)
• Only Outage statuses:– Received at ERCOT
Approved– Approved– Accepted
• Only ERCOT can cancel Forced Outages entered in error• Only ERCOT can cancel Forced Outages entered in error
Slide 67
Entry Rules Example
Actual Start and Actual
Actual Start field will notaccept entries until two hours prior to the Planned Start time.
Actual Start and Actual End Dates/Times may also be entered on the Summary Screen
Actual Start can be edited for two hours.
Date/Time Entry Rules Example:Example:
AS Must be ≥ Planned Start minus 2 hours, ≤ current time, and <
Slide 68
QSEPlanned End
Entry Rules Example
Actual End field not available for entries until after the Actual Start has been Submitted.
Actual End can be edited For two hours.
REMINDER:
New Planned End field will not appear until <3 days before Planned End
When entering Actual end, Supporting Information isRequired for:• Forced• Forced Extensions
Slide 69
QSEForced Extensions
• Unavoidable Extensions• Remedial Switching
Date/Time Entry Rules - Entering Actual Start
• Actual Start field will not be enterable until two hours before Planned Start.
• Actual Start may be changed for up to two hours after submittal.Actual Start may be changed for up to two hours after submittal.New Actual Start must be earlier than the old Actual Start.New Actual Start must also be later than the Planned Start minus two
hours.
• Entering the Actual End changes the Actual Start to read-only.
•You may ask ERCOT to delete the Actual Start. Once deleted, it can be entered again – restarting the two-hour editing window.
Note When the t o ho r entr period e pires the Act al Start field ill stillNote: When the two-hour entry period expires, the Actual Start field will still appear to be enterable. Attempts to update will generate an error message.
Slide 70
QSE
Date/Time Entry Rules - Entering Actual End
• Actual End field will not appear until after the Actual Start has been submitted.
• Actual End may be changed for two hours after submittal New Actual End must be earlier than the old Actual End.
• You may ask ERCOT to delete the Actual End. Once deleted, it can be entered again – restarting the two-hour editing window.
Note: When the two-hour entry period expires, the Actual End field will still appear to be enterable. Attempts to update will generate an error message. The Actual End never displays as read-only
Slide 71
QSE
Entry Rules Example – Summary Page
Slide 72
Warning Messages
Warnings Summary TabWarnings Summary Tab
Individual Warning
Slide 73
Warnings Tab Example
Click on Column Headings to Sort by Column
Slide 74
Warnings Tab Example
Slide 75
Warning Messages – Actual Start & End Summary
Condition Warning Message
Current time is 30 minutes after Planned Start and no Outage XXXNNNNNNN is late with Actual StartActual Start has been entered
Current time is 30 minutes before Planned End and no Actual End has been entered
Outage XXXNNNNNNN will end in 30 minutes. Please take appropriate action.
Note: If no Actual End is entered, this Warning Message will stay active until 30 minutes afterthe Planned End. At exactly 30 minutes after Planned End, this message disappears and thePlanned End, this message disappears and the following warning condition becomes effective.
Current time is 30 minutes after Planned End and no Actual End has been entered
Outage XXXNNNNNNNN is late with Actual End
Actual End for an Unavoidable Extension, Forced Outage or Forced Extension is submitted with no Supporting Information
Outage XXXNNNNNNNN is pending completion. Supporting Information is missing.
Slide 76
XXXNNNNNNNN = Outage Identifier
QSE Summary Screen – Show/Hide Columns
Slide 77
TSP Summary Screen – Show/Hide Columns
Slide 78
Custom Filter Screen - TSPs
If no Dates or Entry Fields are selected, clicking y , gApply will return all records for the RequestingCompany (up to 7000).
When specifying a date range, may enter Request and/or Effective datesRequest and/or Effective dates.
When Filtering for a specific Outage ID or GroupName, a Date range is not required.
Slide 79
Custom Filter Screen - QSEs
If no Dates or Entry Fields are selected, clicking Apply will return all records for the RequestingCompany (up to 7000).
When specifying a date range, may enter Request and/or Effective dates.
When Filtering for a specific Outage ID or Group Name, a Date range is not required.
Slide 80
Custom Filter Screen - QSEs
Slide 81
Custom Filter Screen
TSP & QSE Filtering Maximums
Field Name Maximum ValuesOutage Type Multiple
Outage Status MultipleOutage Status u t p e
Requesting Company – TSPs Only Up to 5
Operating Company – TSPs Only Up to 5
Station Up to 15
Equipment Type Up to 15
Equipment Name Up to 15
Slide 82
Custom Filter Screen - TSP
MultipleMultiple
5
5 15 15 15
Slide 83
Copying Outages
• All outages may be copied, regardless of type/statusExact copy (requestor must modify prior to re submittal)• Exact copy (requestor must modify prior to re-submittal)
• Copies original Requestor Notes only
Slide 84
Outage Entry ExamplesOutage Entry Examples
Nodal Outage Types
Planned
Transmission
Planned
Resource
1 1Planned
Maintenance
Forced
Planned
Maintenance
Forced
1
23
1
23Forced
Remedial Sw.
O t it
Forced
Opportunity
3
45
34
Opportunity
Simple
5
6
Slide 86
Outage Summary Screen
C t N O t t fi ldCreate New Outage entry fields
Slide 87
TSP Outage Selection Screen
Slide 88
QSE Outage Selection Screen
Slide 89
Planned OutagesPlanned Outages
Planned Outages
QSEs/TSPs:•Must provide Rolling 12-month Outage Plan
•Continuous updates required
Outage Plans affect: • Network models• Planning & operations functions• CRR Auctions
Slide 91
Planned Outages
ERCOT: •In-depth reviews of 12-month plans with TSPs
•At least twice each year•At least twice each year
Slide 92
QSE Planned Outages
Planned Outages for ResourcesTimelines for Response for Resource Planned Outages
1Timelines for Response for Resource Planned Outages
If QSE submits t t ERCOT will approve or reject…outage request… pp j
1-2 days prior Within 8 business hours of receipt*1 2 days prior Within 8 business hours of receipt
3-8 days prior Before 1800 hours, two days prior to start of proposed Outagey p prior to start of proposed Outage
8+ days prior Must accept, but may discuss reliability and scheduling impacts to minimize hazards/costs
Slide 93
scheduling impacts to minimize hazards/costs
* Eight Hour Business Rule Applies
QSE Planned Outages
Planned Outages for Reliability Must Run resourcesTi li f R f R li bili R Pl d
1
Timelines for Response for Reliability Resource Planned Outages (Reliability Must Runs & Black Starts)
Request for Approval
ERCOT will Approve or Reject
Not less than 30 days
15 days before start of proposed Outage
More than 45 days 30 days before the start of proposed OutageMore than 45 days 30 days before the start of proposed Outage
Slide 94
QSE Resource Planned Request Screen
Slide 95
Resource Deratings
• Change in Resource’s High Sustained Limit (HSL) from a temporary change in the power plant capabilityfrom a temporary change in the power plant capability
• Occurs when Resource capability reduced by 10% or 10 MW from loss of auxiliary equipment or other conditionsy q p
Slide 96
Derated HSL < Maximum HSL
Resource Derating Coordination
If Derating to last 48+ hours, QSE must:C i t ith ERCOT• Communicate with ERCOT
• Update Current Operating Plan• Submit Planned Maintenance or Forced Derating• Submit Planned, Maintenance, or Forced Derating
Derated Resource
Slide 97
Resource Deratings
Enter new HSL & LSL Values& LSL Values
XXX YYY
Slide 98
QSE Resource Deratings
TIP – use the Group feature to submit an outage request and a derating request at the same time.
i I bi d l t i if h tti d b ti t bi d thi.e. In a combined cycle train - if shutting down combustion turbines reduces the output from associated steam turbines - enter the outage request and the derating request in the same submittal!
Enter Zero’s (0’s) for off line Resourcesoff-line Resources and derated values for limited Resources.
0 0
0
######
0
Slide 99
0 0
QSE Resource Entity-Owned Asset Outages
Resource Entity-Owned Transmission Assets ((breakers switches transformers (main((breakers, switches, transformers (main power, auxilliary & stand-by) and other related equipment)) outages:
•QSEs may only schedule outages on Resources
•QSEs must request that a TSP schedule Resource Entity-Owned Transmission Asset outages on their behalfoutages on their behalf
•Outages must meet TSP submittal requirements
Slide 100
Resource Entity-Owned Assets
TSP Owned Resource Entity - OwnedS O ed esou ce t ty O ed
L04
S040
CD03
C CT03
MT03QSETSP
B1 B2 B3 CD02
S040
C200 CT02
XT02MT02
C300 CT03
B4 B5 B6 SD01
200
S100 ST01
MT01
L01 L02 L03
S010 S020 S030XT01
MT01
Also applies to transmission assets owned and operated by Wind Generation
Slide 101
Resources
QSE & TSP Grouped Outages
TSP Owned Assets Resource Entity-Owned AssestsS O ed ssets esou ce t ty O ed ssests
L04
S040
CD03
C CT03
MT03
QSE OnlyTSP Only
B1 B2 B3 CD02
S040
C200 CT02
XT02MT02
C300 CT03TSP
B4 B5 B6 SD01
200
S100 ST01
MT01
L01 L02 L03
S010 S020 S030XT01
MT01
Slide 102
TSP Planned Outages
Timelines for Response for TSP Planned Outages
If TSP submits outage request… ERCOT will approve or reject…
91 d * 75 d *91+ days* 75 days*
46–90 days* 30 days*
9–45 days* 4 days*
4 8 days* No later than 1800 hours 3 days*4–8 days No later than 1800 hours 3 days
3 days* No later than 1800 hours 2 days*
Slide 103
*Prior to Planned Start Date/Time
TSP Planned Outage
Slide 104
Maintenance OutagesMaintenance Outages
QSE & TSP Maintenance Outages
• Initiated manually to remove equipment from service to perform work on componentsperform work on components
• Required to prevent a potential forced outage • Could be postponed brieflyp p y• Cannot be postponed until next planned outage
Outage Equipment must beOutageLevels
Equipment must beremoved from service…
1 Within 24 hours
2 Within 2 – 7 days
Slide 106
3 Within 8 – 30 days.
QSE Communication
If Maintenance Outage occurs:QSE t d t C t O ti Pl• QSE must update Current Operating Plans
• Verbal communication with ERCOT may be necessary
Slide 107
Maintenance Outage
QSE Maintenance Outage Example
Planned Start Date & Time will determine Maintenancewill determine Maintenance 1, 2 or 3.
Slide 108
Maintenance Level 1 Example
Slide 109
Unavoidable Extensions
• Apply to Planned, Maintenance & Simple Outages
O l O U id bl E t i ll d• Only One Unavoidable Extension allowed
• Must be entered before Planned End
• New Forced Outage required after Planned End
Scheduled Return Time Unavoidable ExtensionWork exceeds
scheduled return time
Slide 110
Unavoidable Extensions
New Planned End field will not appear until <3will not appear until <3
days before Planned End.
Slide 111
Forced OutagesForced Outages
QSE & TSP Forced Outages
• Initiated by protective relay (or manually)
I i h ld l d i l• In response to equipment that could lead to a potential event, or poses threat to people, equipment, or public safety
Notification Requirements ERCOT Action
• Verbally communicate outage immediately.
• Submit into Outage Scheduler as soon as
• Default Accept status automatically assigned when submitted.
practicable.
• QSEs must update COP.
Slide 113
QSE Forced Outage
Slide 114
TSP Forced Outage
Slide 115
Forced Outages & Forced Extensions
Forced OutagesTrip Time Forced Outage
Submit as soonas practicable
Forced Extensions apply to Forced OutagesScheduled Return Time Forced Extension
Work exceeds
• Only one Forced Extension Allowed
Work exceeds scheduled return time
Slide 116
• Only one Forced Extension Allowed
• Must be entered prior to the Planned End or…
Forced Extensions
New Planned End field willNew Planned End field will not appear until <3 days
before Planned End.
Slide 117
Opportunity OutagesOpportunity Outages
Opportunity Outage
TSP Resource
• May be approved by
TSP Opportunity Outage
• May be accepted by
Resource Opportunity Outage
May be approved by ERCOT when a specified Resource will be outaged
• May be accepted by ERCOT when a specific Resource has been
• TSP has an outage “Received at ERCOT” for Transmission Elements
forced off-line
• Resource had been previously accepted for aTransmission Elements
associated with the Resource
previously accepted for a planned outage to begin during the next eight days
Slide 119
QSE Opportunity Outage Sequence of Events
1. The QSE has a previously Accepted or Approved Planned Outage on a Resource with a Planned Start date of eight (8)Outage on a Resource with a Planned Start date of eight (8) calendar days or less.
2 The QSE submits a Forced Outage on the Resource with the2. The QSE submits a Forced Outage on the Resource with the approved Planned Outage. The Forced Outage Planned End date cannot overlap with the Approved Planned Outages Planned Start date.a ed Sta t date
3. Warning Message “Conditions for a Resource Opportunity Outage (XXXNNNNNNNN) are met due to an incoming Forced Outage (XXXNNNNNNNN) with Planned End Date (MM-DD-YY)” is generated.
Slide 120
QSE Opportunity Outage Sequence of Events
1. The QSE has a previously Accepted or Approved Planned Outage on a Resource with a Planned Start date of eight (8)Outage on a Resource with a Planned Start date of eight (8) calendar days or less.
2 The QSE submits a Forced Outage on the Resource with the2. The QSE submits a Forced Outage on the Resource with the approved Planned Outage. The Forced Outage Planned End date cannot overlap with the Approved Planned Outages Planned Start date.a ed Sta t date
3. Warning Message “Conditions for a Resource Opportunity Outage (XXXNNNNNNNN) are met due to an incoming Forced Outage (XXXNNNNNNNN) with Planned End Date (MM-DD-YY)” is generated.
Slide 121
QSE Opportunity Outage Sequence of Events
1. The QSE has a previously Accepted or Approved Planned Outage on a Resource with a Planned Start date of eight (8)Outage on a Resource with a Planned Start date of eight (8) calendar days or less.
2 The QSE submits a Forced Outage on the Resource with the2. The QSE submits a Forced Outage on the Resource with the approved Planned Outage. The Forced Outage Planned End date cannot overlap with the Approved Planned Outages Planned Start date.a ed Sta t date
3. Warning Message “Conditions for a Resource Opportunity Outage (XXXNNNNNNNN) are met due to an incoming Forced Outage (XXXNNNNNNNN) with Planned End Date (MM-DD-YY)” is generated.
Slide 122
QSE Opportunity Outage
Slide 123
QSE - Opportunity Outage
4. QSE accesses the appropriate Update Outage Request screen and decides to “Yes” take the Resource Opportunity Outage.
• When “Yes” is checked and Update Submitted – the Outage Scheduler takes the Planned End of the Forced Outage and automatically uses it as the Planned Start of the Opportunity Outage.automatically uses it as the Planned Start of the Opportunity Outage.
• The Opportunity Outage basically fills in the time period between the Forced Outage and the Planned Outage.
• When the Resource Opportunity Outage is approved, the Outage Scheduler uses the approval date/time as the Actual end of the Forced
d h A l S f h O i Ooutage and the Actual Start of the Opportunity Outage.
Slide 124
QSE - Opportunity Outage
5. QSE accesses the appropriate Update Outage Request screen and decides to “No” not take the Opportunity Outage.
• When “No” is checked, a Warning Message is generated and the Planned Outage reverts back to its original state.
• In summary, the Resource experiences a Forced Outage and then comes back on-line until the start of the original Planned Outage.
Slide 125
QSE Opportunity Outage
Slide 126
QSE Opportunity Outage Warning Messages
Condition Warning Message
A Forced Outage has been submitted for a Resource /
Conditions for a Resource Opportunity Outage which has an accepted/approved outage scheduled to begin in less than 8 calendar days.
(XXXNNNNNNNN) are met due to an incoming Forced Outage (XXXNNNNNNNN) with Planned End Date
Th Pl d E d f F d O hi h i d h R O i O (XXXNNNNNNNN) hThe Planned End of Forced Outage which triggered the Resource Opportunity Outage has passed. The Resource Opportunity Outage automatically reverts back to the original accepted/approved Planned Outage.
Resource Opportunity Outage (XXXNNNNNNNN) has been reverted. The Planned End for the Designated Outage (XXXNNNNNNNN) has passed.
The QSE elects to not take the Opportunity Outage by checking the “No” radio button on the Update Outage
The Potential Opportunity has been cancelled by the Participant, so the Outage has been reset to its original
Request screen state.
The QSE has requested that ERCOT Cancel the Forced Outage
Conditions for a Resource Opportunity Outage (XXXNNNNNNNN) no longer exist due to the Forced Outage (XXXNNNNNNNN) being cancelled
Slide 127
Outage (XXXNNNNNNNN) being cancelled.
QSE Opportunity Outage Warning Messages
Condition Warning Message
A Forced Outage has been submitted for a Resource /
Conditions for a Resource Opportunity Outage which has an accepted/approved outage scheduled to begin in less than 8 calendar days.
(XXXNNNNNNNN) are met due to an incoming Forced Outage (XXXNNNNNNNN) with Planned End Date
Th Pl d E d f F d O hi h i d h R O i O (XXXNNNNNNNN) hThe Planned End of Forced Outage which triggered the Resource Opportunity Outage has passed. The Resource Opportunity Outage automatically reverts back to the original accepted/approved Planned Outage.
Resource Opportunity Outage (XXXNNNNNNNN) has been reverted. The Planned End for the Designated Outage (XXXNNNNNNNN) has passed.
The QSE elects to not take the Opportunity Outage by checking the “No” radio button on the Update Outage
The Potential Opportunity has been cancelled by the Participant, so the Outage has been reset to its original
Request screen state.
The QSE has requested that ERCOT Cancel the Forced Outage
Conditions for a Resource Opportunity Outage (XXXNNNNNNNN) no longer exist due to the Forced Outage (XXXNNNNNNNN) being cancelled
Slide 128
Outage (XXXNNNNNNNN) being cancelled.
QSE Opportunity Outage Warning Messages
Condition Warning Message
A Forced Outage has been submitted for a Resource /
Conditions for a Resource Opportunity Outage which has an accepted/approved outage scheduled to begin in less than 8 calendar days.
(XXXNNNNNNNN) are met due to an incoming Forced Outage (XXXNNNNNNNN) with Planned End Date
Th Pl d E d f F d O hi h i d h R O i O (XXXNNNNNNNN) hThe Planned End of Forced Outage which triggered the Resource Opportunity Outage has passed. The Resource Opportunity Outage automatically reverts back to the original accepted/approved Planned Outage.
Resource Opportunity Outage (XXXNNNNNNNN) has been reverted. The Planned End for the Designated Outage (XXXNNNNNNNN) has passed.
The QSE elects to not take the Opportunity Outage by checking the “No” radio button on the Update Outage
The Potential Opportunity has been cancelled by the Participant, so the Outage has been reset to its original
Request screen state.
The QSE has requested that ERCOT Cancel the Forced Outage
Conditions for a Resource Opportunity Outage (XXXNNNNNNNN) no longer exist due to the Forced Outage (XXXNNNNNNNN) being cancelled
Slide 129
Outage (XXXNNNNNNNN) being cancelled.
QSE Opportunity Outage Warning Messages
Condition Warning Message
A Forced Outage has been submitted for a Resource /
Conditions for a Resource Opportunity Outage which has an accepted/approved outage scheduled to begin in less than 8 calendar days.
(XXXNNNNNNNN) are met due to an incoming Forced Outage (XXXNNNNNNNN) with Planned End Date
Th Pl d E d f F d O hi h i d h R O i O (XXXNNNNNNNN) hThe Planned End of Forced Outage which triggered the Resource Opportunity Outage has passed. The Resource Opportunity Outage automatically reverts back to the original accepted/approved Planned Outage.
Resource Opportunity Outage (XXXNNNNNNNN) has been reverted. The Planned End for the Designated Outage (XXXNNNNNNNN) has passed.
The QSE elects to not take the Opportunity Outage by checking the “No” radio button on the Update Outage
The Potential Opportunity has been cancelled by the Participant, so the Outage has been reset to its original
Request screen state.
The QSE has requested that ERCOT Cancel the Forced Outage
Conditions for a Resource Opportunity Outage (XXXNNNNNNNN) no longer exist due to the Forced Outage (XXXNNNNNNNN) being cancelled
Slide 130
Outage (XXXNNNNNNNN) being cancelled.
TSP Opportunity Outage
Request for Approval Approval / Acceptance Rejection
• TSP should attempt to perform work during a scheduled Resource outage.
• Flags ERCOT & TSP
R t t b l tg g
• If no Resource outage is planned, TSP may submit an Opportunity outage
• Resource outage must be equal to or greater than TSP outage duration
TSP t b bl t li hg
• Specific Resource must be identified in request.
• TSP must be able to accomplish the work within specified time period
Th it i l ti• There are no security violations
• If all above true, ERCOT may Approve
Slide 131
TSP Opportunity Outage
TSP Owned Resource Owned
B1 B2 B3
TSP Owned
GD02
Resource OwnedL04
S040
XT01MT01B1 B2 B3 GD02
G200
G100
GT02
GT01
MT01
B4 B5 B6 GD01
L01 L02 L03
S010 S020 S030XT02MT01
To perform maintenance on TSP-owned switches,
Slide 132
GT01 needs to be off-line.
TSP Opportunity Outage
Stage 1TSP owned switches between Breakers B5 and B6• TSP-owned switches between Breakers B5 and B6 require annual maintenance
• TSP contacts the appropriate QSE or Resource and makes them aware f th tof the request
• TSP and Resource attempt to schedule maintenance during a planned Resource outage
• If no Resource outage is planned or scheduled, TSP submits an opportunity outage request
TSP Owned
Resource Owned
B1 B2 B3
L04S040
G200
G100
GT02
GT01
Slide 133
B4 B5 B6
L01 L02 L03
S010 S020 S030
100 GT01
TSP Opportunity Outage
Stage 1 (cont’d)• The Opportunity outage request must include
the desired outage duration and a specified Resource
• Enter an HSL of Zero (0) if the Resource must be off-line or a maximum ( )HSL value if the Resource can be on-line, but limited.
• Once submitted, outage request stays in status: “Received at ERCOT” waiting for specified Resource outage to occurwaiting for specified Resource outage to occur
• Opportunity outage requests will only stay in “Received at ERCOT” status pending approval for 90 days
Slide 134
TSP Opportunity Outage
Stage 2• If a QSE submits a Planned, Forced or Maintenance outage request on
a designated resource identified in the opportunity outage request, the Outage Scheduler will generate a Warning Message for ERCOT and the TSP.
• The Designated Resource outage duration must be equal to or greater than the duration specified by the TSP.p y
Slide 135
TSP Opportunity Outage
Stage 2 (cont’d)• When the TSP receives the Warning Message:• When the TSP receives the Warning Message:
– TSP must verify and confirm that they can perform their work during the outage durations
– TSP must enter desired planned start and planned end dates and times in the opportunity outage request
– ERCOT will evaluate the request and if no security violations occur, issue approval
Slide 136
TSP Opportunity Outage
Stage 2 (cont’d)If th R t i f ffi i t• If the Resource outage is of sufficient duration, but the TSP cannot perform their work for any reason, the TSP must Cancel the opportunity outage (the TSP may then submit a new request)
Logistics, site arrangements, or work schedules may prevent the TSP from being able to take advantage of thebeing able to take advantage of the opportunity outage.
Slide 137
TSP Warning Messages Summary
Condition Warning Message
A Designated Resource in a pending TSP Opportunity Outage has submitted a Planned Outage which meets the scheduling criteria
Conditions for a Transmission Opportunity Outage (XXXNNNNNNNN) are met due to an incoming Designated Resource Outage (XXXNNNNNNNN)scheduling criteria. Resource Outage (XXXNNNNNNNN).
The QSE has cancelled the outage on the Designated Resource identified in
The Designated Resource Outage has been cancelled The Opportunitythe Designated Resource identified in
the TSPs Opportunity Outage request.been cancelled. The Opportunity Outage is no longer available.
Slide 138
TSP Warning Messages Summary
Condition Warning Message
A Designated Resource in a pending TSP Opportunity Outage has submitted a Planned Outage which meets the scheduling criteria
Conditions for a Transmission Opportunity Outage (XXXNNNNNNNN) are met due to an incoming Designated Resource Outage (XXXNNNNNNNN)scheduling criteria. Resource Outage (XXXNNNNNNNN).
The QSE has cancelled the outage on the Designated Resource identified in
The Designated Resource Outage has been cancelled The Opportunitythe Designated Resource identified in
the TSPs Opportunity Outage request.been cancelled. The Opportunity Outage is no longer available.
Slide 139
TSP Opportunity Outage
Stage 1
DesignatedResources
Desiredd ti d
0
duration and equipment
Slide 140
TSP Opportunity Outage
Stage 2
Enter Zero (0) during submittal if the Resource must be off-line
0
Remains in OS
must be off-line or revised HSL if the Resource can be on-line, but limited
for 90 days, thenautomatically expires on this date
Slide 141
TSP Opportunity Outage – Entered Not Yet Submitted Status
A Designated Resourcehas submitted a Planned, Forced or Maintenance Outage request.
0
Note: the duration between the
Enter Planned Start &Planned End dates/times
between the Planned Start and the Planned End cannot exceed the original Outage
Slide 142
Planned End dates/timesDuration requested.
TSP Opportunity Outage
0
Once Approved, follows the same lifecycle as a
Planned Outage
Slide 143
Opportunity Outage Warnings Tip
QSEs and TSPs will only receive Opportunity Outage notifications viaQSEs and TSPs will only receive Opportunity Outage notifications via the Outage Scheduler Warning Message system. Warning Messages are not “pushed” out to any Market Participants!
To be notified of Opportunity Outages, Entities must either:• Closely monitor their Warning Messages, or• Use Custom Filters to monitor possible Opportunity Outage situations.p pp y g
Tip: Watch for the ENYS (Entered Not yet Submitted) status show below!
Slide 144
TSP Opportunity Outage
0
Pending
Slide 145
Remedial Switching Actions
What is a Remedial Switching Action?
• Some switches/breakers may need to be opened or closed to prevent security violations in Real-Timeto prevent security violations in Real-Time.
• TSPs and ERCOT identify and document any switching actions as part of the Network Operations Model definition of p pRemedial Action Plans (RAPs).
Slide 147
Remedial Switching Action (RSA)
Usage
•Mitigate security violations
•During outage evaluation or l ti ditiunusual operating conditions
Example• High imports
138C
• Unusual generation patterns
Slide 148
Remedial Switching Action (RSA)
Usage
•Entered in Outage Scheduler
•A type of Forced Outage
•Lists switches and breakers affected
•Transparent to all Market Participants138C
Slide 149
Timeline Requirements for RSAs
• If active longer than 3 days, must submit Planned OutageIf common occurrence must be entered into Network Model• If common occurrence, must be entered into Network Model as a Remedial Action Plan
Outage SchedulerDay 1 Day 2 Day 3
Remedial Switching
SubmitPlanned g
Action Outage
Slide 150
Remedial Switching Action (continued)
ERCOT mustA ll R di l S it hi A ti i t• Approve all Remedial Switching Actions prior to implementation by TSPs
• Post such outages to the MIS Secure Area os suc ou ages o e S Secu e ea• Produce statistics reporting use of RSAs
Remember: Outage Scheduler treats RSA as a forced outageRSA as a forced outage
Slide 151
Remedial Switching Action
1. Closing a Normally Open or Opening a Normally Closed Bus Section Breaker
Line 1
G
1138C
G
Auto 1Bus
Section Breaker
138G
EPS
Auto 3138A138E
Slide 152
Line 2Line 3Line 4Line 5Line 6 CB 1
CB 10
Remedial Switching Action
1. Closing a Normally Open or Opening a Normally Closed Bus Section Breaker
2. Opening Low Side Breaker(s) on Autotransformers Line 1
G
12 138C
G
Auto 1Bus
Section Breaker
138G
EPS
Auto 3138A138E
Slide 153
Line 2Line 3Line 4Line 5Line 6 CB 1
CB 10
Remedial Switching Action
1. Closing a Normally Open or Opening a Normally Closed Bus Section Breaker
2. Opening Low Side Breaker(s) on Autotransformers3. Single ending a Transmission Line to reduce line flow
Line 1
G
12 138C
G
Auto 1Bus
Section Breaker
138G
EPS
Auto 3138A138E
3
Slide 154
Line 2Line 3Line 4Line 5Line 6 CB 1
CB 10
Remedial Switching Action
1. Closing a Normally Open or Opening a Normally Closed Bus Section Breaker
2. Opening Low Side Breaker(s) on Autotransformers3. Single ending a Transmission Line to reduce line flow4. Single Ending or de-energizing an Underground
Transmission Line
Line 1
GTransmission Line
12 138C
G
Auto 1Bus
Section Breaker
138G
EPS
Auto 3138A138E
3
Slide 155
4Line 2Line 3Line 4Line 5Line 6 CB 1
CB 10
RSA Create Outage Screen
NOTE
Slide 156156
Simple Outage
Simple Transmission Outage
Request forAppro al
Approval / Acceptance RejectionApproval Rejection
• Submitted between 1 and 2 days in advance
• Within 8 business hours after receipt at ERCOTadvance
• Outage must have a restoration time of 1 hour or less
• Duration of the outage must be 12
ERCOT• Eight-Hour Business Rule Applies
Duration of the outage must be 12 hours or less
• Must not change load flow or direction
• Must not cause a topology change• Must not cause LMPs to change
Slide 158
Simple Transmission Outage (continued)
• TSP must control all involved equipment
• Line(s) must have a single switch or breaker to isolate it from the remaining energized system
• Ongoing bus outage may be expanded to include single• Ongoing bus outage may be expanded to include single-ended lines
• Opposite end of the line/equipment to be included in theOpposite end of the line/equipment to be included in the existing outage must be isolated from the next bus through opening a single switch or breaker
Slide 159
Simple Transmission Outage
Station B
BS 1
• Scheduled Outage on Breakers AB-1 and AB-2.
• Breakers isolated through
Station A C
AS-1 AB-1 AS-2
BS-1
BS-2
BB-1
-A Line ABStation G
Breakers isolated through Switches AS-1 to AS-5
Station C
O
OAS-3 AB-2 AS-4
AB 3
Bus
-A
S-5
Line AB
Line AD Station F
C
Station DC
AS-6 AB-3 AS-7
AS-8 AB-4 AS-9
Bus
-B C
Line AC LineCF
LineFGC
C C C
C C CLegend
C
Station E
OEB-1 ES-1EG-1
Slide 160
C C C- Closed Breaker - Open Breaker
- Open Switch - Closed Switch
C OStation E
Simple Transmission Outage
Station B
BS 1
Can Line AB be taken as a Simple
Transmission
Station A O
AS-1 AB-1 AS-2
BS-1
BS-2
BB-1
-A Line ABStation G
Transmission Outage?
Can Line AD be taken as a Simple
Transmission Outage?
Station C
O
OAS-3 AB-2 AS-4
AB 3
Bus
-A
S-5
Line AB
Line AD Station F
C
Station DC
AS-6 AB-3 AS-7
AS-8 AB-4 AS-9
Bus
-B C
Line AC LineCF
LineFGC
C O O
C C C
C
Station E
OEB-1 ES-1EG-1
Slide 161
C C CStation E
Simple Transmission Outage
Station B
BS 1
Station A O
AS-1 AB-1 AS-2
BS-1
BS-2
BB-1
-A Line ABStation G
Station C
O
OAS-3 AB-2 AS-4
AB 3
Bus
-A
S-5
Line AB
Line AD Station F
C
Station DC
AS-6 AB-3 AS-7
AS-8 AB-4 AS-9
Bus
-B C
Line AC LineCF
LineFGC
C O O
C C C
CCould the TSP have set up the Line AB Outage in a different way without using a SimpleStation E
OEB-1 ES-1EG-1
Slide 162
C C C way without using a Simple Transmission Outage?
Station E
Simple Outage Screen
Slide 163
“Be Aware” Tip
In an open Browser session – if you leave a Detailed Outage entry page without submitting the outage, access the Summary Page page t out sub tt g t e outage, access t e Su a y ageand open a new outage request – the original outage disappears –with no Warning!!
Slide 164
Summary Detailed
ERCOT Outage Scheduler CapabilitiesFor Outage Coordinators and
System Operators
ERCOT’s Outage Scheduler Capabilities
With respect to the Market Participants Nodal Market Outage Scheduler interface ERCOT Outage Coordinators andScheduler interface, ERCOT Outage Coordinators and System Operators may only edit or perform the following functions:
• Change Outage Status (Study, Accept, Approve, Reject or Withdraw)
• Delete Actual Start or Actual End times.
• Enter Reviewer Notes
• Cancel Forced Outages entered in error
Slide 166
ERCOT Market Information System
Market Information System – Accessing Outage Information
Slide 170
Market Information System – Accessing Outages
Slide 171
Market Information System – Accessing Outages
Slide 172
Market Information System – Accessing Outages
MIS Approved & Accepted Outages summary .csv formatFormat useful for multiple filtering and data sorts, etc.Contains all Active and future OutagesContains all Active and future Outages
Slide 173
Outage ReportsOutage Reports
Outage Reporting
• ERCOT posts individual QSE/RE and TSP outage scheduling data on MIS Secure areaoutage scheduling data on MIS Secure area monthly for informational purposes.
• Detailed Reporting and Performance p gMonitoring information is found in Nodal Protocol 8 and Nodal Operating Guide 9.
Slide 175
QSE & TSP Outage Reports
Posted on MIS SecureN b f O R b i d i• Number of Outage Requests submitted in advance
• Number of Outages by Outage Type• Number of Outages by Outage Type
• Total number of Outages that were requested, accepted, approved, cancelled and withdrawnapproved, cancelled and withdrawn
• Planned versus Actual Monthly and Annual Statistics
Slide 176
Supplemental References
The following Outage Scheduler documents and training material will be available at ERCOT commaterial will be available at ERCOT.com
•Outage Scheduler User Guide for TSPsOutage Scheduler User Guide for TSPs
•Outage Scheduler User Guide for QSEs
•Outage Scheduler Web Based Training•Outage Scheduler Web-Based Training
Slide 177