Jason Ausmus, Jason Smith and Akshay Shivaram Peak Operations Planning Outage Coordination, Data Quality Improvement and OPWG Efforts October 24, 2017 Jason Ausmus, Jason Smith and Akshay Shivaram Peak Operations Planning

Overview Outage Coordination Process Data Quality Improvements COS Data Dictionary Operations Planning Working Group (OPWG) Outage Coordination Phase II Outage Coordination Process Metrics

Outage Coordination Process Observations Process currently in the 5th month of existence (Apr 1st implementation) Have had more than 43,119 outages submitted to COS (Apr – Sept) 21,462 considered in-scope for OC 7,767 generator outages 13,695 transmission outages

Outage Coordination Process Observations Most of the issues from study process being observed/addressed in Short-Range About 75% of all issues being identified in OC are being caught in the SR process vs the day-ahead OPA One of the anticipated benefits of the OC Process Multiple study iterations of the study are allowing for more potential issue to be identified Reduces surprises for RT Ops

Outage Coordination Process Observations All in-scope outages must be RC Confirmed prior to Implementation Planned generator outages must be “BA & TOP Confirmed” not just “BA Confirmed” Submitted vs Confirmed outage state usage Enhancement being pursued to address this Outage records looking ahead T+3 hours, need to be within +/- 1 hour accuracy

Outage Coordination Process Observations Currently have a daily manual check for new outages Late to start, missing outages, etc. New EMS module Forced Outage Detection (FOD) will help automate these checks COS enhancement already designed to allow for updating of record with actual start/end date/times, Phase 3a

Forced Outage Detection (FOD) Compares COS data export, mapped to WSM Delayed, early – Planned Outages, Missing – Forced A/E

Outage Coordination Process Reports Two weekly reports being sent out Short-Range “Outages at Risk” of missing window Preliminary, proposed and planned gen outages with only BA Confirmation (need both BA and TOP) Week ahead report for outage that have missed the window E.g. outages in the submitted state, expired outages

Example Weekly Report – Approaching SR submission timeline

Example Weekly Report – Outages that missed SR

Outage Coordination Process Reports Two COS Report variation also available at: PeakRC.org->Library->Entity Studies->COS Outages

Example COS Outage Report

COS Patches / Minor Enhancements Apr 1st -> mid-Oct Several small patches to COS have been applied since Apr 1st Addressing miscellaneous software and OC Process issues Examples include: remote id search revert auto-transitioned outages due to time updates allow outage extensions with sufficient notice prevent “Station” outages, enforce specific equip Peak RCSO/ROE view improvements

COS Phase 3 Summary Implemented in production on 10/12/17 Please refer to recorded 12/7/16 webinar for details Changes mostly centered around increased usage of COS Data Dictionary related to outage history Some additional minor enhancements currently underway to expand on Phase 3 COS Data Dictionary build out, i.e. Phase 3a

Additional Enhancement Phase 3a Another enhancement planned that will indicate key outage attribute data by record OC In-Scope flag to be utilized in the future to eliminate the confusion with “Submit” Additional usability improvements, e.g. filtering, dictionary update improvements

COS Status – Dictionary Standardization Objective was ensure a one-to-on mapping of WSM to COS equipment Other non-WSM also allowed in COS (e.g. RTU, SCADA, iccp, relay) Initial effort focused on duplicates and including missing WSM equipment Effort began last Oct 2016 Good response, but more work needed in this area

COS Status – Dictionary Standardization Recently started 2nd and 3rd rounds of duplicate elimination and missing WSM elements Peak Modeling is leading this effort and have been contacting each company as spreadsheets are developed Spreadsheets were simplified for clarity Sent out in “pieces”, duplicates and unmapped CROW are first

COS Dictionary Standardization Roadmap Finish 2/3rd Cleanup rounds Equipment Grouping Jointly Operated Equipment BES/non-BES Identification Switching Point Association

Future COS Outage Record - w/COS Data Dictionary Populated

COS Outage Record w/Dictionary Populated

Operations Planning Working Group (OPWG) WECC NDSTF NDSWG Peak OPWG Group focused on Operations Planning study input data and study process Group will have subgroup efforts (aka “small teams”)

OPWG and Subgroup Efforts ? Operations Planning Working Group Outage Coordination Phase II Outage Metrics ? ?

Outage Coordination Phase II Initial focus will be on “cleaning up” process issues One area of focus is in regards to change requests, e.g. delayed starts, outage extensions Discussion around outage state, outage type changes, requiring actual start/end date/time entries, etc.

Outage Coordination Phase II Future COS changes may result of process changes OC Phase II will be involved in the design Collaborate with other Peak efforts small team efforts Seasonal Planning process Data Request

Outage Coordination Metrics Identify insightful outage metrics Feedback necessary for Peak’s process improvement Develop industry metrics to ensure OC Process consistency Design metrics reporting, identify recipients and distribution

Example In-Scope Outages by Type

Example In-Scope Outages by Type - Generation outages

Example In-Scope Outages by Type - Transmission outages

Group Membership Email will be forthcoming regarding volunteers for all 3 efforts OPWG OC Phase II OC Metrics Group formation in Nov Kickoff meetings in Dec/Jan