Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1

Similar documents
TOP-010-1(i) Real-time Reliability Monitoring and Analysis Capabilities

primary Control Center, for the exchange of Real-time data with its Balancing

November 9, Revisions to the Violation Risk Factors for Reliability Standards IRO and TOP

Standard INT Dynamic Transfers

Standard TOP Transmission Operations

Standard COM-002-2a Communications and Coordination

A. Introduction. B. Requirements and Measures

Standard INT Dynamic Transfers

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective.

Standards Authorization Request Form

Peak Reliability. Reliability Coordinator Data Request and Specifications for Data Provision

Internal Controls Evaluation (ICE) Tony Eddleman, P.E. NERC Compliance Manager Nebraska Public Power District

5. Effective Date: The first day of the first calendar quarter after applicable regulatory approval.

New Brunswick 2018 Annual Implementation Plan Version 1

Reliability Compliance Update. Reliability Standards and Compliance Subcommittee Preston Walker August 16, 2018

Standard COM Communication and Coordination

Reliability Coordinator Procedure

Project Consideration of Commission Directives in Order No. 693

COM Communications and Coordination

Southwest Power Pool Independent Coordinator of Transmission RELIABILITY PLAN for Entergy in the Southeastern Electric Reliability Council September

Québec Reliability Standards Compliance Monitoring and Enforcement Program Implementation Plan Annual Implementation Plan

Table of Contents. TOP TOP BA Data Request and Specification Guidelines. Operating Procedure

TOP/IRO Standards. RC Users Group January 21, Vic Howell Manager, Operations Engineering Support

Reliability Coordinator Procedure PURPOSE... 1

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective.

Standard CIP Cyber Security Critical Cyber As s et Identification

NERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum

WON Security Guideline

Development Authority of the North Country Governance Policies

British Columbia Utilities Commission Reliability Standards with Effective Dates adopted in British Columbia

Standard CIP 005 4a Cyber Security Electronic Security Perimeter(s)

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective.

Subject: Implementation of the WECC Merchant Alert Protocol Guideline.

Project Retirement of Reliability Standard Requirements

Bulk Electric System Definition Changes and Reporting

Standard CIP 007 4a Cyber Security Systems Security Management

Standard CIP Cyber Security Electronic Security Perimeter(s)

Overview. Section 1. Reviewer Home Page. Module 3: Reviewing a Manuscript for Ethnicity & Disease

Standard CIP-006-4c Cyber Security Physical Security

Standard Development Timeline

Reliability Standard Audit Worksheet 1

FRCC Disturbance Monitoring Equipment Outage Reporting

Standard EOP Disturbance Reporting

Standard Development Timeline

Standard CIP Cyber Security Critical Cyber Asset Identification

Standard CIP Cyber Security Critical Cyber Asset Identification

Modifications to TOP and IRO Standards

Concept White Paper. Concepts for Proposed Content of Eventual Standard(s) for Project : Real-Time Monitoring and Analysis Capabilities

Engaged Management ReView Author Guidelines V.1.0. Friday, March 11, 2015

St. Christopher (St. Kitts) & Nevis. FATCA Portal User Guide

Standard CIP Cyber Security Incident Reporting and Response Planning

Generation, Transmission, and End User Facilities

Requirements for Data for Power System Modeling and Analysis (MOD-032-1) Arizona Public Service Company

Reliability Standard Audit Worksheet 1

PRC Coordination of Protection Systems for Performance During Faults

Published: December 15, 2016 Revised: December 15, 2016

COM Interpersonal Communications Capabilities

Standard CIP 005 2a Cyber Security Electronic Security Perimeter(s)

Published: December 15, 2017 Revised: December 15, 2017

SOUTH TEXAS ELECTRIC COOPERATIVE, INC.

Implementation Plan for Version 5 CIP Cyber Security Standards

Reliability Standard Audit Worksheet 1

Southwest Power Pool Portal Market Participant General User s Guide

The Toyota Foundation Grant Programs Guide for Web-based Grant Applications (Project Proposals)

Impacts and Implementation: NERC Reliability Standards, Compliance Initiatives, and Regulatory Activities

Standard CIP 007 3a Cyber Security Systems Security Management

Standard CIP Cyber Security Electronic Security Perimeter(s)

Drinking Water Quality (DWQ) Web Form Reporting A User Manual

Standard Development Timeline

Implementation Plan for COM-001-2

Standard CIP-006-3c Cyber Security Physical Security

Standard CIP Cyber Security Systems Security Management

Physical Security Reliability Standard Implementation

Gateway User Guide Annual Report Submission

CIP Cyber Security Personnel & Training

Unofficial Comment Form Project Operating Personnel Communications Protocols COM Operating Personnel Communications Protocols

CIP Cyber Security Systems Security Management

IssueTrak End User Training

Standard CIP Cyber Security Critical Cyber As s et Identification

Procedure For NPCC Bulk Electric System Asset Database

Designation and Termination of Network Resources

P3 USER GUIDE FOR MARKET ACTORS COMMERCIAL STANDARD OFFER PROGRAM

STCP Amendment Proposal Form

NERC Relay Loadability Standard Reliability Standards Webinar November 23, 2010

Standards Authorization Request Justification

Standard Development Timeline

CYBER SECURITY POLICY REVISION: 12

Peak Reliability IRO Project Overview Oct 25, 2016

Misoperations Information Data Analysis System (MIDAS)

Date adopted/approved 02/08/2013 Custodian (entity responsible for maintenance and upkeep) Data Exchange Work Group. Web URL: Previous name/number

Standard Development Timeline

CIP Cyber Security Security Management Controls. Standard Development Timeline

Reliability Standard Audit Worksheet 1

Standard CIP-006-1a Cyber Security Physical Security

Disclaimer Executive Summary Introduction Overall Application of Attachment Generation Transmission...

Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities

Outage Coordination External Workshop. Jason Ausmus Manager, Operations Planning

Modifications to TOP and IRO Standards

Standard Development Timeline

Project Posting 8 Frequently Asked Questions Guide

Transcription:

Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1 Revision History Version Effective Date Summary of Revisions 1 March 8, 2017 Initial Creation Introduction The purpose of this document is to provide Transmission Operators (TOP) and Balancing Authorities (BA) in the Southwest Power Pool Reliability Coordinator Area guidelines to follow when submitting NERC Reliability Standards required documents to the SPP Reliability Coordinator (SPP RC) and Balancing Authority (SPP BA). SPP staff will be responsible for maintaining the contents of this document. The SPP Operating Reliability Working Group (ORWG) and the SPP Reliability Compliance Working Group (RCWG) will provide input on the contents of this document. This document is intended to provide guidelines on submitting information required by certain NERC Reliability Standards to the SPP RC and BA. If any responsible entity identifies a perceived conflict between NERC Reliability Standards and this document, NERC Reliability Standards shall always supersede this document. NERC Reliability Standards Requiring Document Submissions to SPP RC or SPP BA EOP-005-2 System Restoration from Blackstart Resources EOP-010-1 Geomagnetic Disturbance Operations EOP-011-1 Emergency Operations IRO-017-1 Outage Coordination TOP-002-4 Operations Planning TOP-003-3 Operational Reliability Data

Process for Submitting Required Documents Step 1: Submit via email a description of your submission and any subject document(s) as an attachment(s) to the SPP RC/BA using the appropriate email address identified below for each subject NERC Reliability Standard. Emails with included attachments will be considered the official submission of information to the SPP RC/BA. The FTP site use will not be considered the official exchange mechanism for the subject documents at this time. Step 2: Upload desired document(s) to the appropriate FTP site subfolder to facilitate convenient use of the documents. Details on Email Address Use In addition to official submissions of documents and information on each subject NERC Reliability Standard, email addresses can also be used for general correspondence on the subject document submission. Correspondence from SPP to the submitting entity, such as, confirmations of receipt, results of document reviews, document approvals, and other such correspondence will be emailed to the original submitter of the notification along with other previously identified contacts for the subject topic. Details on Use of the FTP Site FTP Site URL: https://xfer.spp.org Each entity (TOP and/or BA) will be granted a single user account for the FTP site to be used by all entity staff. The user authentication scheme is username and password. Entities are responsible for the distributing the username/password for the entity wide user account to the appropriate TOP/BA staff at their respective entities. Access should be limited to TOP/BA staff only. All TOPs/BAs in the SPP RC area will have access to all the information contained on the FTP site to facilitate document sharing between all entities. Submitting entities will be responsible for notifying other entities that documents they wish to share are available on the FTP site. SPP will retain entity uploaded documents for a period of at least five (5) years. Upon initial login, users will see a number of folders including NERC Reliability Standards Required Documents. In this folder, a subfolder for each subject NERC Reliability Standard 2

will be available. Submitting entities will place documents in the entity specific subfolder by subject. Below is an example of the subfolder structure. - NERC Reliability Standards Required Documents - GMD Plans (EOP-010) - AEP - KCPL -. - TOP Restoration Plans (EOP-005) - AEP - KCPL -. Description of Guidelines Format Standard: Name/Number of the NERC Reliability Standard Submission From: NERC registered entity responsible to submit the information Submission To: NERC registered entity to switch document(s) are being submitted Document(s) Submitted: Description of document(s) to be submitted Frequency of Submission: Description of the frequency of document(s) submissions Annual Resubmission Deadline: Date of annual submission resubmission deadline if applicable Notification Email Address: Email address to which notifications of FTP site postings and other correspondence on subject document submissions should be sent FTP Document Folder Name: Specific name of the FTP site subfolder for the subject document submissions or No indication if an indication of initial receipt of the document(s) will provided by the receiving entity to the submitting entity. Receipts will be provided to email address providing the notification of document submission. Description of the submitting entity s responsibilities. Description of the receiving entity s responsibilities. 3

Standard: EOP-005-2 System Restoration from Blackstart Resources Submission From: Transmission Operator Document(s) Submitted: TOP Restoration Plans Frequency of Submission: Annually and Upon Revision Annual Resubmission Deadline: June 1 Annually Notification Email Address: RestorationPlans@spp.org FTP Document Folder Name: TOP Restoration Plans (EOP-005) EOP-005-2 R3. Each Transmission Operator shall review its restoration plan and submit it to its Reliability Coordinator annually on a mutually agreed predetermined schedule. EOP-005-2 R4. Each Transmission Operator shall update its restoration plan within 90 calendar days after identifying any unplanned permanent System modifications, or prior to implementing a planned BES modification, that would change the implementation of its restoration plan. R4.1. Each Transmission Operator shall submit its revised restoration plan to its Reliability Coordinator for approval within the same 90 calendar day period. EOP-006-2 R5. Each Reliability Coordinator shall review the restoration plans required by EOP-005 of the Transmission Operators within its Reliability Coordinator Area. R5.1. The Reliability Coordinator shall determine whether the Transmission Operator s restoration plan is coordinated and compatible with the Reliability Coordinator s restoration plan and other Transmission Operators restoration plans within its Reliability Coordinator Area. The Reliability Coordinator shall approve or disapprove, with stated reasons, the Transmission Operator s submitted restoration plan within 30 calendar days following the receipt of the restoration plan from the Transmission Operator. 4

Standard: EOP-010-1 Geomagnetic Disturbance Operations Submission From: Transmission Operator Document(s) Submitted: TOP GMD Operating Procedure or Operating Process Frequency of Submission: Annually and Upon Revision Annual Resubmission Deadline: October 1 Annually Notification Email Address: GMDPlans@spp.org FTP Document Folder Name: GMD Plans (EOP-010) EOP-010-1 R3. Each Transmission Operator shall develop, maintain, and implement a GMD Operating Procedure or Operating Process to mitigate the effects of GMD events on the reliable operation of its respective system. At a minimum, the Operating Procedure or Operating Process shall include: 3.1. Steps or tasks to receive space weather information. 3.2. System Operator actions to be initiated based on predetermined conditions. 3.3. The conditions for terminating the Operating Procedure or Operating Process. EOP-010-1 R1.2 A process for the Reliability Coordinator to review the GMD Operating Procedures or Operating Processes of Transmission Operators within its Reliability Coordinator Area. 5

Standard: EOP-011-1 Emergency Operations Submission From: Transmission Operator and/or Balancing Authority Document(s) Submitted: Operating Plan(s) to mitigate operating Emergencies Frequency of Submission: Annually and Upon Revision Annual Resubmission Deadline: February 1 Annually Notification Email Address: EmerOpPlans@spp.org FTP Document Folder Name: Operating Plans for Emergencies (EOP-011) EOP-011-1 R1. Each Transmission Operator shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate operating Emergencies in its Transmission Operator Area. EOP-011-1 R3. The Reliability Coordinator shall review the Operating Plan(s) to mitigate operating Emergencies submitted by a Transmission Operator or a Balancing Authority regarding any reliability risks that are identified between Operating Plans. 3.1. Within 30 calendar days of receipt, the Reliability Coordinator shall: 3.1.1. Review each submitted Operating Plan(s) on the basis of compatibility and inter-dependency with other Balancing Authorities and Transmission Operators Operating Plans; 3.1.2. Review each submitted Operating Plan(s) for coordination to avoid risk to Wide Area reliability; and 3.1.3. Notify each Balancing Authority and Transmission Operator of the results of its review, specifying any time frame for resubmittal of its Operating Plan(s) if revisions are identified. 6

Standard: IRO-017-1 Outage Coordination Submission From: Transmission Planner Document(s) Submitted: Planning Assessment(s) for the Near-Term Transmission Planning Horizon Frequency of Submission: Annually Notification Email Address: PlanningAssessmentsSPPRC@spp.org FTP Document Folder Name: Planning Assessments SPP RC Area (IRO-017) IRO-017-1 R3. Each Planning Coordinator and Transmission Planner shall provide its Planning Assessment to impacted Reliability Coordinators. IRO-017-1 R4. Each Planning Coordinator and Transmission Planner shall jointly develop solutions with its respective Reliability Coordinator(s) for identified issues or conflicts with planned outages in its Planning Assessment for the Near-Term Transmission Planning Horizon. 7

Standard: TOP-002-4 Operations Planning Submission From: Transmission Operator and/or Balancing Authority Document(s) Submitted: Next-Day Operating Plans that include information the submitting entity deems necessary to share with the Reliability Coordinator. Frequency of Submission: Daily as needed Annual Resubmission Deadline: N/A Notification Email Address: NDOpPlans@spp.org FTP Document Folder Name: Next-Day Operating Plans (TOP-002) Initial Receipt Acknowledged by Receiving Entity: No TOP-002-4 R6. Each Transmission Operator shall provide its Operating Plan(s) for nextday operations identified in Requirement R2 to its Reliability Coordinator. TOP-002-4 R7. Each Balancing Authority shall provide its Operating Plan(s) for nextday operations identified in Requirement R4 to its Reliability Coordinator. None 8

Standard: TOP-003-3 Operational Reliability Data Submission From: Transmission Operator or Balancing Authority Submission To: SPP Balancing Authority Document(s) Submitted: TOP Data Specifications Frequency of Submission: Annually and Upon Revision Annual Resubmission Deadline: April 1 Annually Notification Email Address: DataSpecifications@spp.org FTP Document Folder Name: BA and TOP Data Specifications (TOP-003-3) TOP-003-3 R3. Each Transmission Operator shall distribute its data specification to entities that have data required by the Transmission Operator s Operational Planning Analyses, Realtime monitoring, and Real-time Assessment. TOP-003-3 R4. Each Balancing Authority shall distribute its data specification to entities that have data required by the Balancing Authority s analysis functions and Real-time monitoring. TOP-003-3 R5. Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Load-Serving Entity, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications using: 5.1. A mutually agreeable format 5.2. A mutually agreeable process for resolving data conflicts 5.3. A mutually agreeable security protocol 9