RC Coordination Small Group Updates

Presented by Small Group Leads

Date: February 13, 2019

1/24/20192

Agenda

• ECC, WIT & USFM• ICCP/Data Sharing• Reliability Messaging Tools• Network Modeling• SOL Methodology• Synchrophasors, WECC & NERC Data Needs• Operations Planning• Shadow Operations• EOP & Restoration• IRO-010 RC Data Request

1/24/20193

ECC, WIT and USFM Group Scope & Objectives• Lead – Dede Subakti, CAISO• Scope statement▫ This team is to discuss the use of Western

Interconnection wide tools and functions and identify responsibilities of RCs, vendors, and other parties to ensure the use of these tools continue to provide value to the West. This team will also support the development of a governance document by providing input to respective team developing the governance framework.

1/24/20194

Key Activities and Action Items – WIT, ECC & USFM• Key Activities List▫ Document Peak’s administrative tasks related to ECC,

WIT and Time Error▫ Work with OATI ECC - multi-RC change order 10 (Peak leading) ECC - messaging system change order 11 (CAISO leading) WIT - multi-administrator change order (CAISO leading) ECC - integrate CAISO inputs (CAISO leading)

▫ EIR Transition Planning Each BA/PSE needs to update tags for the RC cutover date AESO has scheduled meeting with NAESB and OATI to

discuss EIR registration

1/24/20195

Decisions – ECC, WIT & USFM

• Decisions List▫ WIT and ECC are the only “shared tools” being

considered by this small-team.▫ Shared governance is being discussed by executive

team led by Nancy Traweek▫ CAISO to take WIT Delta Time Error (DTE)

responsibilities on November 1, 2019.▫ CAISO to provide Western Interconnection model

and State Estimator data to OATI for ECC post Peak wind-down period.

1/24/20196

WIT, ECC & USFM - Questions?

1/24/20197

ICCP/Data sharing - Group Scope & Objectives

• Lead – Kevin Colmer, CAISO• Scope statement▫ The ICCP/Data sharing team will document the

technical transitions that are occurring to accommodate real-time ICCP data sharing, PMU data sharing, and forecast data sharing. Coordination will occur with other sub teams (Ops Planning, Shadow Operations, etc.) to be sure issues are properly addressed.

1/24/20198

Key Activities and Action Items – ICCP/Data Sharing• Key Activities List▫ Define and validate connectivity necessary for

data sharing▫ Create plan for of EHV Data Pool▫ Define ICCP, PMU, Forecast and Outage data

exchanges between entities through the transition period

▫ Document coordinated transition plans covering network connect / disconnect and data exchanges between entities

▫ Coordinate with other sub teams to assure alignment of plans

1/24/20199

Decisions – ICCP/Data Sharing

• Decisions List▫ The ECN and WON will not change as part of the RC

transitions.▫ The next phase of the ECN/WON will support CIP-012▫ Each RC will establish their own network for real-time

data exchange between their RC customers (future configuration)

▫ SPP RC Customers will connect to SPPNet. They will also maintain their connection with the WON for the transition period

▫ All BA/TOPs in the West will continue to send ICCP data to Peak through the termination of Peak’s RC responsibilities

1/24/201910

ICCP/Data Sharing Questions?

1/24/201911

RC Messaging Group Scope & Objectives

• Lead: Tim Beach, CAISO• Scope statement▫ The RC messaging tools sub-group is working

to facilitate the change in real-time messaging tools from Peak's RMT to CAISO and SPP future messaging tools.

1/24/201912

RC Messaging - Key Activities and Action Items• Key Activities List▫ API is being built to “bridge” SPP and CAISO

messaging tools▫ 20 proposed message types that fit in 3

categories: Emergency, Operational Information Messages, and Control Center and Tool Functionality

▫ SPP finishing rollout of messaging tool to the Eastern entities

▫ Messaging guideline and distribution list to be created

1/24/201913

• Regional Messaging?

• BAS and TOPs can communicate

• Messaging Guideline to be written

RC Messaging – Dealing With RC Seams

SPP

WALCAZPS

CAISO (GMS)

1/24/201914

RC Messaging Decisions

• BC Hydro and AESO will use CAISO’s GMS messaging tool

• CAISO is the only RC implementing the Merchant Alert Protocol for its BAs/Merchants via messaging tool.

1/24/201915

RC Messaging Questions?

1/24/201916

Network Modeling Group Scope & Objectives

• Lead(s): Dede Subakti, CAISO (WECC variance) and Ankit Mishra, CAISO (CIM)

• Scope statement▫ This group is asked to help determine details of

network model exchange given the decisions on the western interconnection model (WIM) being supported by CAISO.

1/24/201917

Network Model - Key Activities and Action Items• Key Activities List (CIM model focus)▫ Document the model exchange/data collection

(CIM15XML) and build process. Topics include: Identify content and level of detail for

CIM15XML SCADA mapping file that maps the ICCP object

ID to the RDFID in the CIM15XML Data needed for VSA and TSAT RAS data exchange Facility Rating data exchange Contingency list exchange

1/24/201918

Network Model - Key Activities and Action Items (cont.)• Key Activities List (WECC variance focus)▫ Create a common methodology doc for

implementation of IRO-002-5 WECC regional standard variance. Methodology to contain: Method for development, maintenance, and

periodic review of West-wide model Modeling/Monitoring methods to understand

impacts of Inter-area oscillations Determining contingencies for analyses Determining RAS for analyses Determining forecast data for analyses Method for validation and periodic review of the

model

1/24/201919

Network Model Decisions

• Decisions List▫ CAISO will take responsibility for building and

maintaining the Western Interconnection Model as of November 1, 2019.

▫ Each RC will work with TOPs to obtain the detailed RAS information used for RAS modeling. However, RCs can share with other Western RCs the high level RAS information that is found in EMS RAS models.

1/24/201920

Network Model Questions?

1/24/201921

SOL Methodology Group Scope & Objectives

• Lead: Eric Desjardins, BC Hydro• Scope statement▫ The SOL Methodology sub-team will review RC

SOL Methodology documents and identify methodology differences, coordination issues and gaps that need to be resolved.

1/24/201922

SOL Methodology - Key Activities and Action Items

• Key Activities List▫ BC Hydro and SPP to complete their respective

methodology documents by mid-February▫ CAISO methodology complete; differences with

Peak’s methodology documented▫ AESO – no plans for significant methodology

changes▫ Small group will assess SOL methodology

differences and recommend course of action if needed

1/24/201923

SOL Methodology Decisions

• None recorded

1/24/201924

SOL Methodology Questions?

1/24/201925

Group Scope & Objectives - Synchrophasor Data, WECC/NERC Data Needs

• Lead: Dede Subakti, CAISO• Scope statement▫ This group is asked to help determine the future for RC

involvement in providing for PMU data, what to do with the archives at Peak, what critical PMU values need to be shared and how, what reports are necessary to others and others.

1/24/201926

Key Activities and Action Items -Synchrophasor Data, WECC/NERC Data Needs• Key Activities List▫ Determine a plan and coordinate for replacement of the WISP

WAN. ▫ Determine how PMU data that Peak is currently archiving, will

be maintained for future use beyond 12/3/2019 final cutover date.

▫ Document what critical PMU data need to be shared between them and how this data will be shared and archived.

▫ WECC/NERC to document requirements of what reports, notifications, access, visuals, SAFNR data they need. Determine how each RC will submit inertia data for WECC and

NERC ▫ RCs to each design and develop the WECC/NERC requested

reports, notifications, access, and visuals. Non-US entities to address jurisdictional matters as may be needed.

1/24/201927

Decisions - Synchrophasor Data, WECC/NERC Data Needs

• Decisions List▫ None to date

1/24/201928

Synchrophasor Data, WECC/NERC Data Questions?

1/24/201929

Ops Planning Group Scope & Objectives

• Lead: Will Tootle, SPP• Scope statement▫ This team is to take up issues of data exchange

that focuses on Current Day and Next Day studies, Outage Coordination, SOL and IROL exchange, load and dispatch forecast exchange. This team will also identify processes for sharing of study results.

1/24/201930

Key Activities and Action Items – Ops Planning

• Key Activities List▫ Determined data exchange methods CD/ND

studies between RC<>RC and RC<>TOP in different RC footprint

▫ Document Seasonal Coordination process▫ Determine mutually agreeable forecast data

sharing deadline▫ Exchange of outages (Still need to discuss

clearance points)

1/24/201931

Decisions – Ops Planning

• Decisions List▫ SOLs will be communicated via four methods

(Outage Coordination call, NDS reports, outage card submissions and real-time ICCP)

▫ Four possible outage states are submitted, approved, cancelled, and completed.

▫ RCs will all host a document sharing system for sharing studies with their BAs/TOPs and external RCs.

▫ Decisions made regarding which VSAT/TSAT calculated limits would be exchanged and how.

1/24/201932

Ops Planning Questions?

1/24/201933

Group Scope & Objectives – Shadow Operations

• Lead: Tim Beach, CAISO• Scope statement▫ The Shadow Operations team is addressing activities

that are needed to plan and execute successful shadow operations periods.

1/24/201934

Key Activities and Action Items – Shadow Operations• Two webinars – 1/25 and 2/8• Reviewed and approved USF/PST coordination

Op guide▫ Effective July 1▫ Will need to be revised for November 1st

▫ Plan on table top drill and possible simulation• Reviewed and approved Daily Conference call

guide▫ Effective July 1▫ Structured call so West-wide information is

discussed first, allowing regional information exchange breakouts at the end.

1/24/201935

Key Activities and Action Items – Shadow Operations (cont.)• Discussed table top drills▫ To be coordinated by CAISO Operational Readiness

Dept (SIM Group)▫ USF/PST coordination▫ IROL mitigation▫ WECC 1 RAS coordination and communication▫ AESO and BCH interface

• Developed procedure coordination matrix▫ Link RC procedures to each other▫ Review for further coordination and drill opportunities

• Developed RC transition communication process (under review)

1/24/201936

Key Activities and Action Items – Shadow Operations (cont.)

• External Situational Awareness▫ Assembling Alarm Schema narratives from all RCs▫ Plan to develop comprehensive narrative of RC alarm

schemas and situational awareness▫ Developed guideline for expected communications

when RC observes issue from external footprint monitoring

• Developed action item list and tracking• Next meeting – 2/22/2019

1/24/201937

Decisions – Shadow Operations

• Decisions List▫ NERC will not participate in RC daily calls (per

Carter Edge, 2/8)

1/24/201938

Shadow Operations Questions?

1/24/201939

EOP Group Scope & Objectives

• Lead: Tricia Johnstone, CAISO• Scope statement▫ Identify and coordinate RC Area restoration

plans, TOP/BA emergency operation plans, and plan for the development and delivery of joint emergency training.

1/24/201940

EOP - Key Activities and Action Items

• Key Activities List▫ Each RC to determine plan/schedule/scope for 2019

system restoration training. ▫ Each RC to share their RC Area restoration plan with

the other RCs.▫ Each RC shall complete the review of their neighboring

RC's restoration plan(s) prior to certification. Peak and CAISO reviews complete

▫ RCs to coordinate the reviews of overlapping TOP EOP-005, EOP-010 and EOP-011 Emergency Operations plans (AEPCO and Tristate)

▫ Determine method (technology) for RC-RC plan exchanges in 2019 and in the future

1/24/201941

EOP - Decisions

• Decisions List▫ Peak will provide restoration training in spring

2019. Has invited all RCs to week 6.▫ CAISO will provide restoration training in

spring and fall 2019. Will invite all RCs to fall training.

1/24/201942

EOP Questions?

1/24/201943

Group Scope & Objectives - IRO-010 Data Spec• Lead: Asher Steed, BC Hydro• Scope statement▫ This team is to meet and discuss the needs of each

RC’s IRO-010 data submittal as it pertains to the transition of RC functions and the specific RC to RC IRO-010 components.

▫ Scope is to include topics such as: RC to RC requests (data, formats, timeframes, etc.);

and RC to BA/TOP requests: keep things as consistent

with Peak's current request, but evaluate the need for any immediate changes.

1/24/201944

Key Activities and Action Items – IRO-010• Key Activities List▫ Initial meeting Feb 6; to meet bi-weekly▫ RC to RC data spec review and coordination CAISO finalized for July 1 cutover CAISO requesting finalizing by June for Nov 1 cutover to

support certification timeline▫ PEAK’s data spec changes for July 1 are drafted Intent is to clarify need to continue providing data to Peak Ready for sub-group review end of February

▫ CAISO requesting SPP/AESO/BCH RCs to confirm method to provide outage and forecast data. All RCs to review CAISO API and advise.

▫ Tracking of related items in other sub-teams Operations Planning - Sharing of study results, operating

plans Modeling teams - network modelling to align with IRO-

002-5 variance

1/24/201945

Decisions – IRO-010

• Decisions List▫ None to report▫ Expect decisions on first action items at Feb 20

meeting.

1/24/201946

IRO-010 Questions?