peak reliability – ecc webinar for marketing entities entities... · o mitigation to occur only...
TRANSCRIPT
• Welcome – the webinar will begin shortly• All participants will be muted during the
webinaro Please use the chat feature to submit questions
or comments to Anne Eisenach while muted• Please note that this meeting and any
discussions are being recorded. By continuing to participate, you are consenting to that recording.
Peak Reliability –ECC Webinar for Marketing Entities
ECC Webinar Series for Marketing Entities #1 –UFMP Migration Phase
1. Educate users about upcoming ECC –webSAS parallel operations and migration
2. Discuss ECC tool access and functionality
3. Provide forum for marketing entities to ask questions concerning ECC
Objective of the ECC Webinars
• What is the ECC?• What is UFMP?• ECC / webSAS Parallel Operations• Getting Access to the ECC• Marketing Entity Materials• Open Q&A
Please send chat questions to Anne Eisenach
Agenda for Today
What is the ECC?
• 2011 – WECC Efficient Dispatch Toolkit Paper outlined the ECC’s role in future operations of the Western Interconnection and described its key functions.o Enhancements to webSAS – Provide ability to
calculate curtailments on many more paths and allow for real-time updates of transmission data
o Manage Seams Issues – Play a significant role in managing seams issues between markets and entities.
ECC Background
• 2011 – ECC Task Force formed to develop ECC proposal. This task force worked with Peak to develop an initial set of functional requirements and continues to work with Peak to influence future phases.
• 2013 – Post-Sept. 8th WECC Board presentation points:o ECC should address SOL exceedances for all BES
Facilities, not just Qualified Paths. o ECC should use Real-time inputs to improve
accuracy of calculations
ECC Background (Cont.)
• WECC Path Operator Task ForceCreated a new paradigm
• NERC SOL Whitepaper Further defining SOLs
• NERC IRO/TOP Standard Changes (4/1/2017) Real-time Assessments, retirement of TOP-007-WECC-1
• Peak RC SOL Methodology changes (4/1/2017)
Industry Changes that Involve ECC
• Reliability Benefitso Increased situational awareness, common view for allo Ability to see tagged and untagged contributionso One mechanism to implement POTF recommendationso Future hour – Identify problems in advance
• Efficiency Benefitso Mitigation to occur only when exceeding SOLso Identifies “fair and equitable” mitigating actions based on
defined methodologyo Real-time model accuracy improves factor quality
ECC Business Case
• Forecast transmission flows that may cause System Operating Limit (SOL) exceedances;
• Determine the impact of generation, load and Interchange schedules contributing to such exceedances, and
• Provide users with the ability to take appropriate actions, such as curtailing schedules or adjusting generation, in a fair and equitable manner to mitigate SOL exceedances.
Purpose of ECC
ECC Data Inputs & Outputs
ECC Monitored Equipment(Interfaces, Single transmission lines, Contingency groupings)
WSM State Estimator (including contingency)
Telemetry (ACE, PT & DS) E-Tags
5 m
in
5 m
in
4-6
wee
ks
Factors / Impacts(5 min)
e-Tags Load ACE DT
1 m
in
Visualization
DC Lines
Phase Shifters
There are two types of Element definitions:• Power Transfer Distribution Factor (PTDF) -
Monitored Facilities Pre-contingent flows Monitor against thermal limits Single lines, WECC Path
• Outage Transfer Distribution Factor (OTDF) -Contingencies Monitor pre- and post-Contingent flows Similar to RTCA run
Defining Elements in ECC
ECC Timeline
1. Provide visualization of impact “layers” on Elements.2. Increase knowledge of e-Tag impacts.3. Provide ACE/Gen. re-dispatch analysis capability.4. Inform mitigation plans with BAs and TOPs.
June 2016: Current Hour Situational Awareness
Q2 2017: WebSAS Integration
1. Move UFMP support from webSAS to ECC.2. Base curtailment factors on Real-time conditions.3. Implement more granular mappings.
Q4 2017: Future Hour Situational Awareness
1. Apply forecast and outage data to provide look-ahead visualization of potential SOL exceedances.
2. Provide time to adjust system prior to actual events.
Q4 2018: Expanded Mitigation
1. Expand SOL management functionality to all defined Elements.
2. Monitor and mitigate seams issues between BAs and Markets by determining relief obligations.
3. Work with stakeholders on final design.
June 2016
1. ECC is primarily a reliability entity tool
2. Current design is for marketing entities to have access to UFMP functionality
3. End state of ECC project could lead to changes outside of UFMP paradigm
Key Takeaways for Marketing Entities on ECC
What is the UFMP?
• UFMP details the current congestion management practices for Qualified Paths in the Western Interconnection
• There are currently four Qualified Paths:o Paths 30, 31, 36, 66
• Path Operators responsible for issuing events:o CAISO, WACM
Unscheduled Flow Mitigation Plan (UFMP)
• Four steps for mitigation:o Step 1 = TOP informs RC of intended actions o Step 2 = TOP takes local actions to reduce USFo Step 3 = TOP requests COPS (active for 4 hours)o Step 4 = TOP requests e-Tag Curtailments (each
hour)
Qualified Path flows must reach or be anticipated to reach 95% of the path limit before calling on Step 3 or 4. Requests for Step 4 must be made by 25 minutes after the hour, or sooner as determined by the Administrator, for actions related to the next hour.
Unscheduled Flow Mitigation Plan (Cont.)
Step Timing: • Steps 1-3 – Effective immediately• Step 4 o Path Operator must issue by 25 after the hour for e-
Tag curtailments to occur at top of the next hour (otherwise will be 2 hrs. out)
o RC has 5 mins. to approve or deny (passive approval)o BAs have 10 mins. to approve curtailment profile or
provide equivalent relief via an alternate method (passive approval)
Unscheduled Flow Mitigation Plan (Cont.)
• Curtailment Priority – 16 bucketso Uses NERC transmission priority (0-7) but layers in
On-Path Vs. Off-Path concepto On-Path – Transmission rights across Qualified Patho Off-Path – No transmission rights across Qualified Path
• On/Off Path status dictates curtailment actionso For a given transmission priority, Off-Path e-Tags
curtailed completely before moving to On-Path e-Tagso Off-Path e-Tags use lowest priority across all legso On-Path e-Tags use QP leg priority
Unscheduled Flow Mitigation Plan (Cont.)
• TDF Squared o Prior buckets curtailed completelyo Marginal bucket of curtailment uses
TDF Squared (teal blue row)
o Curtails higher TDF tags moreo All e-Tags in the marginal bucket
are curtailed if > 0.5 MW impact
Unscheduled Flow Mitigation Plan (Cont.)
©2017 OATI, Inc.
• Competing Pathso Two Qualified Paths
both need reliefo Calculations based on
impact to both QPs Both + = Highest TDF Both - = Do not curtail One + / One - =
Perform 2x Check
Unscheduled Flow Mitigation Plan (Cont.)
REMINDER: ENSURE BOTH SIDES OF COMPETING PATHS ARE ISSUED
ECC / webSAS Parallel Operations
• No modifications to the UFMP required o No changes to curtailment methodology
• Minimal modifications to ECC user interfaceo Minimize USF-related user trainingo Maintain current process for issuing USF events
and conform with curtailment process currently in webSAS
WebSAS Integration into ECC
• Improved accuracy in TDF calculationso WebSAS TDF factors are static, calculated twice
per year from planning models.o ECC factors are calculated every 5 mins. from
State Estimator and Power Flow solutions• More accurate curtailment calculations
during USF eventso More accurate TDF yields more equitable and
tag curtailment lists that better respond to reliability problems
WebSAS Integration into ECC (Cont.)
• Workflow for issuance of USF procedureso Timing for TOP issuanceo Timing for RC to Approveo Timing for BA Curtailment acknowledgements
• USF calculations do not change (except for using more accurate TDFs)
• Competing Path methodology remains the same as that currently implemented in webSAS
• GUI for USF procedures and related reports have very minimal changes
What Doesn’t Change from webSAS?
Benefits:• Allows validation of actual USF events• Stakeholders to gain familiarity with ECC
prior to being active system
ECC / webSAS Parallel Operations
webSAS USF Event ECC Study USF Event
Scheduled for 3 months
• Review the new ECC version for familiarity
• Look at how e-Tag curtailments differ due to webSAS and ECC calculation changes
Marketing Entity Role during UFMP Parallel Operations
Key Dates:• Three biweekly webinars for marketing
entities February 28th – March 28th
• Parallel Operations begin Wed. March 1st
• Target for cutover Thurs. June 1st
o Subject to results during parallel operations
ECC / webSAS Parallel Operations
Getting Access to the ECC
• Fill out PSE Production Request formo Completed by first company admin
• Peak will confirm request and configure company in ECCo May require OATI Security Officer at marketing entity to
make a change in webCARES (https://www.oaticerts.com)
ECC Production Access
Options User Settings
• Peak will reply with user name• OATI will send temporary password• Requests are sent to [email protected]• Process detailed in PSE Getting Started Guide• After first admin is configured, that person can
follow directions in ECC Admin Guide_PSE to configure additional users
ECC Production Access
• Guides and additional reference material posted to peakrc.como Registration form and guideso User guide tailored to marketing entitieso Training presentationo Webinar slide decks and recordings
ECC Production Access
Marketing Entity Materials
Marketing Entity Materials on PeakRC.com
Open Q&A
