Presentation is loading. Please wait.

Presentation is loading. Please wait.

Stacen Tyskiewicz CIIMS Chair October 18, 2016

Similar presentations


Presentation on theme: "Stacen Tyskiewicz CIIMS Chair October 18, 2016"— Presentation transcript:

1 Stacen Tyskiewicz CIIMS Chair October 18, 2016
CIIMS Update Stacen Tyskiewicz CIIMS Chair October 18, 2016

2 Critical Infrastructure & Information Management Subcommittee (CIIMS)
EMS Event Analysis Standards Work Group Reports Energy Management Systems Work Group (EMSWG) Data Exchange Work Group (DEWG) Physical Security Work Group (PSWG) Western Electricity Coordinating Council

3 EMS Event Analysis

4 WECC EMS Event Analysis
So far in 2016, 12 EMS events (category 1h) have been reported: Date Duration (mins) Category Root Cause 10-Feb 104 Network Infrastructure A1 – Design/Engineering 29-Feb 125 A3 – Individual Human Performance 18-Mar 97 EMS Software  AX – Other 116  A2 – Equipment/Material 26-Mar 220 Facilities  A1 – Design/Engineering 6-Apr 161 2-Jun 57 A5 – Communication 9-Jun 180 EMS Hardware 28-Jun 43 AX – Other 6-Jul 135  A3 – Individual Human Performance 26-Aug 366 14-Sep 37 Western Electricity Coordinating Council

5 Western Electricity Coordinating Council
EMS Event Analysis WECC EMS EA: Added new members, defining new objectives Identifying interesting 1h reports for in-depth discussions during EMSWG closed-door sessions Collecting questions for vendors NERC EMS EA: Investigating impacts of loss of ICCP data on SE/CA (visited WECC) Digging deeper into extended outage times (across NERC, not just WECC) Annual conference now includes vendor panel Western Electricity Coordinating Council

6 Standards TOP-001-3 TOP-003-3

7 Standards TOP-003-3 (becomes effective 1/1/2017)
Requires each TOP and BA to document and distribute data requests for all data required to perform its monitoring, analyses and assessments; and for each data-owner to satisfy the data request. WECC TOP-003 Task Force The TOP-003 Task Force is proposing a common approach for all WECC entities to take in achieving and maintaining compliance with this new standard.  Essentially, Peak RC will provide a secure location through which all TOPs and BAs can share model and forecast data, complete lists of all available ICCP points and any other documents that need to be shared.

8 Standards: TOP-003 Task Force
TOP Requirements 1 and 2 Language of Requirements Compliance Approach Status “…maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real‐time monitoring, and Real‐time Assessments.” A TOP-003 Data Specification template is being developed, based on Peak RC’s IRO-010 Data Specification Peak RC is currently updating its IRO-010 Data Specification and expects to have it completed by late October.  The TOP-003 Data Specification template will be available very soon after. Some entities represented on the Task Force have tested the template and found it easily adaptable to their own needs. 

9 Standards: TOP-003 Task Force
TOP Requirements 3 and 4 Language of Requirements Compliance Approach Status “…distribute its data specification to entities that have data required by the Transmission Operator’s Operational Planning Analyses, Real-time monitoring, and Real‐time Assessment.” Peak RC is providing a secure repository where all TOPs and BAs can post their Data Specification.  Note that although there is a mechanism for creating alerts inherent with the SharePoint technology on PeakRC.org, the alerting functionality should not be relied upon for compliance tracking. The Peak RC secure repository will be available to all interested TOPs and BAs in November.  Entities will use the same login they currently use for the peakrc.org site. Peak RC will manage access permissions to the folders.  Entities can manage access on each document it posts to those folders. Data-sharing partners will be able to “subscribe” to get alerts when you make changes to the Data Specification.

10 Standards: TOP-003 Task Force
TOP Requirement 5 (effective 4/1/17) Language of Requirements Compliance Approach Status “…satisfy the obligations of the documented specifications…” Satisfying requests for real-time and near real-time data will not be done through the peakrc.org site, but lists of available data points will be posted to simplify the request process. Satisfying requests for data contained in documents, spreadsheets and similar files can be done through the pearkrc.org site. Same as noted above for Requirements 3 and 4.

11 Standards: TOP-003 Task Force
Deliverables Status Survey Completed Data Specification Template Final expected mid November Secure Repository Available mid November Guidelines Document ASAP List of POCs per entity With data specification

12 Standards TOP (R9) Requirement 9: Each BA and TOP shall notify its RC and known impacted interconnected entities of all planned outages, and unplanned outages of 30 minutes or more, for telemetering and control equipment, monitoring and assessment capabilities, and associated communication channels between the affected entities. In their response to the WECC EMSWG question involving interpretation of TOP R9, WECC seems to indicate that entities are required to notify data-sharing partners prior to a momentary outage related to a regularly scheduled EMS failover.   The WECC EMSWG strongly disagrees with this guidance and would like to have the following interpretation approved:  For Energy Management Systems (EMS), momentary outages caused by purposeful failovers between redundant systems are considered out-of-scope as “planned outages”.  If a purposeful failover is unsuccessful, resulting in an extended outage, then interconnected entities should be notified if that unplanned outage goes beyond the 30-minute time limit.

13 Work Group Reports

14 Energy Management Systems Work Group (EMSWG)
Chair: Jonathan Aust (WAPA) Workgroup Focus Currently focused on TOP-003-3 New CIM Task Force EMS Questions for the next Operational Practices Survey Next focus will be on newly approved standard TOP with a goal of ensuring a consistent understanding and collaborating on possible solutions and best practice. Summary: Requires each TOP and BA to have criteria for evaluating, provisions to indicate and actions to address issues with quality in the real-time data used for monitoring and analysis.

15 Data-Exchange Work Group (DEWG)
Chair: Devin Miroy (WAPA-SNR) Vice Chair: Eric Mscichowski (SMUD) Workgroup Focus Currently focused on TOP-003-3 WON Connection Agreements re-signing (~33% done) WECCNet Retirement (last server powered down last week) Next focus will be on the future of the WON

16 Physical Security Work Group (PSWG)
New Chair and Vice Chair Chair - Rich Hyatt from Chelan County PUD Vice Chair - Brady Phelps from Grant County PUD  Workgroup Focus CIP-014 Working with CIIMS chair to set goals Working with WECC on identifying a secure location for sharing information with the broader WECC membership.


Download ppt "Stacen Tyskiewicz CIIMS Chair October 18, 2016"

Similar presentations


Ads by Google