WECC Board Technical Session March 5, 2019 Steve Ashbaker Reliability Initiative Director
RC Footprints 2
Board RC Technical Session • Reliability Coordination Tools • Wide-Area Model • Seams Issues • RC Shadow Operations • Outage Coordination • RC Certification 3
RC Tools • WECC Interchange Tool (WIT) • Enhanced Curtailment Calculator (ECC) • Reliability Messaging Tools 4
WECC Interchange Tool (WIT) • WIT Governance • Multi-RC Access • WIT Administrator Duties (SPP & CAISO) • Month-end Interchange Reconciliation • Inadvertent Dispute tracking (NERC and PII) • Perform NERC CERT monthly lockdown • WIT Delta Time Error (CAISO) 5
WIT Architecture BAs OATI Peak Variable Bias DTE (3 entities via EIDE) Schedules NAI/NSI (primary) (via e-Tags) (via EIDE) WAPA DTE (BU1) EIDE NERC CERTS WIT (EPG tool – manual) AVA DTE (BU2) EIDE WREGIS Primary = BU1/BU2 OR requires (WECC–specific manual action PSE/MISC info combo) 6
Enhanced Curtailment Calculator • ECC manages congestion on USF Qualified Paths and provides situation awareness • CAISO provide WI model and State Estimation data to OATI • USFMP Step 4 implementation • CAISO manages Path 66 (COI) • SPP manages Paths 30, 31, 36 • ECC Governance (Funding, Change Orders) • CAISO holds OATI Contract • Multi-RC Access 7
ECC Inputs / Outputs WSM State Model SCADA Estimator E-Tags Contingencies Base Data ECC Elements Engine USF Situational Curtailments Awareness
ECC Congestion Management 9
RC Messaging Tools • RC to RC communication via RCIS (NERC hosted RC messaging tool) • SPP has developed their own messaging tool for BA/TOPs • Peak is staying with RMT for their BA/TOPs • CAISO has developed their own messaging tool for their BA/TOPs (GMS) 10
RC Messaging Tools SPP MAP/ AESO USF TOP/ Peak BCH BA RMT RC West SPP API GMS TOP/ MAP/ TOP/ USF BA USF BA 11
Current ICCP Data Sharing 12
Future ICCP Data Sharing 13
WECC Board Technical Session March 5, 2019 Brett Wangen Vice President GridSME
Western Interconnection Model Model must support Key objectives • Interconnection- • Preserve the value wide situational of the West-wide awareness/analysis System Model • Static (Power • Enable efficient Flow) studies model sharing • Dynamic • Common model (Transient) studies used by all RCs 15
IRO-002-5 WECC Variance Common modeling and monitoring methodology for all RCs in the West, including methods for: • Development, maintenance, and periodic review of Western Interconnection model • Assessment of inter-area oscillation impacts • Determining Contingencies to include in analyses and assessments • Determining Remedial Action Schemes to include in analyses and assessments • Determining forecast data to include in analyses and assessments • Validation and periodic review of the model 16
Model Maintenance AESO AESO BAs/TOPs RC BC Hydro BC Hydro CAISO Western BAs/TOPs RC CIM Interconnection BAs, TOPs, Model Export RCs Process SPP SPP RC BAs/TOPs CAISO CAISO RC BAs/TOPs Note: this is illustrative; all RCs share among themselves 17
Model Update Coordination Each RC has authority to collect necessary model data through NERC standard IRO-010-2 •How often are updates available? •How much advanced notice? •What is modeled during construction? •Exchangeable formats? •What does IRO-002-5 variance methodology say? 18
Remedial Action Schemes Monitoring RAS RAS Modeling Impacts •RAS data sharing •SCADA (ICCP (TOP->RC, points, visualization) RC->RC) •Alarming •Identifying BES •Real-time impactful RAS Contingency •Understanding Analysis RAS interactions 19
Seams Issues 20
Restoration • Each BA and/or TOP must still have emergency operations plan (EOP-011-1) • Identify blackstart generators • Identify cranking paths • Each RC will have an RC Area restoration plan (EOP- 006-2) • Restoration training • Coordination • Simulation • Operating Instructions • RC-to-RC coordination and communication will be critical during restoration or other emergencies 21
Outage Coordination • IRO-017-1 BC Hydro requires each RC Outages to have an outage coordination SPP AESO process CAISO Outages Outages OMS • Outage data, approvals, study expectations, and coordination GridForce CAISO Outages Outages 22
System Balancing • Each RC will monitor ACE and frequency for Frequency all BAs • Reserve Sharing Groups span multiple RCs in some cases • Coordinated operating Reserves ACE procedures will be critical 23
Unscheduled Flow • Western Interconnection Unscheduled Flow Mitigation Plan (WIUFMP) • Coordinated Operations of Phase Shifters (COPS) • Curtailments • Enhanced Curtailment Calculator • Each RC participating in unscheduled flow management must analyze the system to assess potential impact to its own system. 24
SOL/IROL Methodology • Each RC required to have SOL methodology for operations horizon (FAC-011-3) • Defines SOL and IROL • Defines acceptable system operations within SOLs and IROLs • Mitigation expectations • RCs are coordinating on future SOL methodology documents—consistency is goal • Identify differences compared to Peak’s SOL methodology and present to the group 25
Shadow Operations • Each RC taking two months (or more) for Shadow Operations • Tools, data, models • Procedures, studies, real-time coordination • Each RC developing training prior to entering Shadow Operations • RC of record for an area always will have authority 26
RC Certification March 5, 2019 Tim Reynolds Sr. Reliability Engineer
Certification Process Overview Pre- Planning On-Site Visit Reporting Data Retention Certification •Application •Establish •Opening •Create action •Documents Certification Presentations list of Bucket retained for •WECC Team Item six years reviews •Review application •Certification documents •Draft Final •Final Report for Scope Report posted on •Interview completeness NERC’s •Establish management •Approval and website online portal and operators from Regional applicability to share and NERC •Tour the •WECC documents Management facilities notifies NERC •Develop and •Bucket Items of application Send •Exit Certification Presentation Packet 28
Planning • RC Certification Team • An existing RC, a BA and a TOP in the proposed RC area, each affected RE, and NERC • Team Member Must Complete Training • Certification Packet • Logistical Information • Master Matrix • Requests for additional information 29
On-Site Visit • At a minimum, the team will: • Review documents and data with the entity • Interview the operations and management personnel • Inspect the facilities and equipment • Request demonstration of tools • Review any additional documentation resulting from inquiries arising during the site-visit • Bucket Items 30
Reporting: The Final Steps • Bucket 1 & 2 items will be on Final Report • Final Report approved by WECC/NERC management • Registration process can be completed 31
RC Certification Timelines 32
Dashboard • Track RC Certification https://www.wecc.org/EventAnalysisSituationalAwar eness/Pages/Certification.aspx 33
Contact: Steve Ashbaker - sashbaker@wecc.org Tim Reynolds - treynolds@wecc.org Brett Wangen - bwangen@gridsme.com 34
Recommend
More recommend
