Phil O’Donnell, Manager Operations and Planning Audits

Slides:



Advertisements
Similar presentations
Interchange Authority Recommendations Board of Directors Meeting December 7, 2007.
Advertisements

Western Electricity Coordinating Council Status of NERC Standards Activity WECC PCC Meeting March 6-7, 2008.
POTF Status update.
Phase II – Analyze the Identified Issues from Perspectives of Alternative Approaches Determine which of the identified issues remain under alternate approaches.
Marv Landauer Report to TSS on Annual Study Program Report Review Task Force April 2012 TSS Meeting Salt Lake City.
CUG Meeting June 3 – 5 Salt Lake City, UT
NERC New Approved Standards
Presented to PGDTF February 11, 2015
PER
PER Update & Compliance Lessons Learned
1 PER-005 Update Impact on Operators System Operator Conference April and May 1-3, 2012 Columbia, SC Margaret Stambach Manager, Training Services.
1. 11/26/2012: NERC Board of Trustees adopted CIP v5 CIP thru CIP CIP and CIP Version 5 Filing FERC requested filing by 3/31/2013.
Branden Sudduth Director, Reliability Assessment and Performance Analysis Rocky Mountain Region PA/PC Meeting March 18-19, 2014 Denver, Colorado.
System Operator Conference NERC Standards Review for: Simulator Drill Orientation 2014 System Operator Conferences Charlotte NC & Franklin TN SERC/SOS.
Notice of Compliance Audit
Reliability Standards Update
June 6, 2007 TAC Meeting NERC Registration Issues Andrew Gallo, Assistant General Counsel, Litigation and Business Operations ERCOT Legal Dept.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
GOP and QSE Relationship Jeff Whitmer Manager, Compliance Assessments Talk with Texas RE June 25, 2012.
B O N N E V I L L E P O W E R A D M I N I S T R A T I O N 1 Network Operating Committee (NOC) June 12 th, 2014.
Determine Facility Ratings, SOLs and Transfer Capabilities Paul Johnson Chair of the Determine Facility Ratings Standard Drafting Team An Overview of the.
ERCOT SOL Methodology for the Planning and Operations Horizons Stephen Solis 2014 OTS 1.
Entity Registration Under EPAct 2005 Public Power Council April 6, 2006 Louise McCarren Chief Executive Officer WECC.
1 Arizona Corporation Commission BTA Workshop Presenter: Steven Cobb May 23, 2008.
Steve Rueckert Director of Standards TPL Discussion – PCC Steering Committee March 25, 2014.
Standards Subject to Enforcement Currently Or Standards Subject to Future Enforcement TSS Meeting #169 May 6-8, 2015 By: Lesley Kayser-Sprouse.
Project System Protection Coordination Requirement revisions to PRC (ii) Texas Reliability Entity NERC Standards Reliability Subcommittee.
Bill Lewis, Compliance Team Lead NERC Reliability Working Group May 16, 2013 Texas RE Update Talk with Texas RE April 25, 2013.
COMPLIANCE ROLLOUT Vann Weldon Compliance Training Administrator March 23, 2005 NERC FUNCTIONAL MODEL REVIEW.
CIP Version 4 The Basics. CIP Version 4- Background Centers around expanded criteria for Critical Assets – FERC thought Risk Based Methodologies used.
PMUs for NERC Reliability Standards Ryan D. Quint, Ph.D., P.E. Staff Coordinator, NERC SMS, SAMS WECC JSIS Meeting September 22, 2015.
RiversidePublicUtilities.com Arts & Innovation RiversidePublicUtilities.com MOD GENERATOR TESTING REQUIREMENTS RESOURCE PLANNERS LeeAnne Uhler, Regulatory.
1 Power System Restoration. 2 Not Active 3 4 Compliance Audit Process APPA E&O Technical Conference – Atlanta April 16, 2007.
October 29, 2012 RARF Workshop 2 Introduction to ERCOT Modeling Process Jay Teixeira Manager, Model Administration.
TEPPC Review Task Force January 11, Purpose Advise and make recommendations on Future potential future generation and load balance Adequacy of the.
Path Operator Implementation Task Force Vic Howell, Vice Chair Report to OC March 22, 2016.
Project WECC-0100 Standards Briefing WECC-0100 SDT April 7, 2016 W ESTERN E LECTRICITY C OORDINATING C OUNCIL.
CMTF Tariff Language Clarification 1. Parking Lot Question Is the Planning Reserve Margin requirement meant to be maintained throughout the whole calendar.
Reliability Standard TPL Transmission System Planned Performance for Geomagnetic Disturbance Events September 28, 2016 TPL Standard Status.
MOPC Meeting Oct , 2016 Little Rock, AR
NERC Lessons Learned Summary
PLWG Review 6.9 and the Interconnection process
Phase Angle Limitations
GMD Research FERC Order No. 830 Research Work Plan Mark Olson, NERC
NERC Entity Registration and Certification in the ERCOT Region
COM Operating Personnel Communications Protocols
Planning Geomagnetic Disturbance Task Force (PGDTF) Update to the ROS
NERC Readiness Spotlight
WECC Regional Standards Update
Path Operator Implementation Task Force
ERCOT Technical Advisory Committee June 2, 2005
Long-term Planning and TPL TP Workshop November 2, 2017
Phil O’Donnell, Manager Operations and Planning Audits
Terry Baker Peak Reliability
Transmission Planner Seminar
Pseudo-tie business procedure
Project WECC-0100 Update Load Modeling Task Force
Determine Facility Ratings, SOLs and Transfer Capabilities
CEO/Co-founder, SOS Intl
Review of After-the-Fact (ATF) Tagging Criteria Scheduler’s Meeting May 24, 2016 Raymond will ask the audience what their expectations are in regard to.
“TOP-010-1: Data Quality, Analysis Quality, and Alarm Process Monitor”
Workshop Session 1: Overview
Coordinate Operations Standard
Workshop Session 1: Overview
Review of After-the-Fact (ATF) Tagging Criteria Scheduler’s Meeting May 24, 2016 Raymond will ask the audience what their expectations are in regard to.
GMD Research FERC Order No. 830 Research Work Plan Mark Olson, NERC
Donald Davies Chief Senior Engineer
Project WECC-0100 Update Load Modeling Task Force
Peak Reliability IRO Webinar
Pseudo-tie business procedure
Presentation transcript:

Phil O’Donnell, Manager Operations and Planning Audits Other TP Obligations Phil O’Donnell, Manager Operations and Planning Audits

Introduction This presentation does not include TPL-001! Each Registered TP is responsible for demonstrating compliance with Requirements applicable to that function. That TP or another entity may perform the tasks.

Introduction Compliance Responsibility can only be transferred to another entity registered as a TP. There must be a formal agreement by both parties to transfer/accept compliance responsibility

The Most Important Concept! Good Coordination between TPs and the PC such that there are no reliability gaps in the implementation of the standards!

The Purpose and Requirement's in this presentation are paraphrased to emphasize responsibilities and tasks. Do not consider them complete

FAC-002-2 Facility Interconnection Studies Purpose: To study the impact of interconnecting new or materially modified Facilities on the BES. R1. Each TP and each PC shall study the reliability impact of: (i) interconnecting new generation, transmission, or electricity end-user Facilities and (ii) materially modifying existing interconnections of generation, transmission, or electricity end-user Facilities. Conditional: Based on planned interconnections or modifications Trigger: When TO or GO wishes to interconnect or modify facilities (FAC-001-2 R3 & R4) One party can perform a single study as long as the results satisfy the needs of the PC study and the TP studies.

FAC-014-2 Establish and Communicate System Operating Limits Purpose: To ensure that System Operating Limits (SOLs) used in the reliable planning and operation of the Bulk Electric System (BES) are determined based on an established methodology or methodologies. R4. The TP shall establish SOLs, including IROLs, for its Transmission Planning Area that are consistent with its PA’s SOL Methodology. R5.4. The TP shall provide its SOLs (including the subset of SOLs that are IROLs) to its PA, RC, TOPs, and TSPs that work within its Transmission Planning Area and to adjacent TPs. Note that R3 requires the PA to determine SOLs for its area. TP and PA must coordinate to ensure no gaps exist.

IRO-017-1 Outage Coordination Purpose: To ensure that outages are properly coordinated in the Operations Planning time horizon and Near-Term Transmission Planning Horizon. R3. Each PC and TP shall provide its Planning Assessment to impacted RC’s. R4. Each PC and TP shall jointly develop solutions with its respective RC for identified issues or conflicts with planned outages in its Planning Assessment for the Near-Term Transmission Planning Horizon.

MOD-004-1 Capacity Benefit Margin Purpose: To promote the consistent and reliable calculation, verification, preservation, and use of Capacity Benefit Margin (CBM) to support analysis and system operations. Not Applicable if your TSP does not use CBM in its tariff. (we rarely see use of CBM) CBM can be requested by a Resource Planner of Load Serving Entity.

MOD-020-0 Providing Interruptible Demands and DCLM Data Purpose: Collection of data To ensure that assessments and validation of past events and databases can be performed and future system assessments can be performed to assist in proper real-time operations. R1. The TP, and RP shall each make known its amount of interruptible demands and Direct Control Load Management (DCLM) to TOPs, BAs, and RCs on request within 30 calendar days. Conditional: depends on a request from TOP, BA or RC

MOD-026-1 Verification of Models and Data for Generator Excitation Control System or Plant Volt/Var Control Functions Purpose: To verify that the generator excitation control system or plant volt/var control function model and the model parameters used in dynamic simulations accurately represent the generator excitation control system or plant volt/var control function behavior. R1. Each TP shall provide requested information to the GO within 90 calendar days of receiving a written request R6. Each TP shall provide a written response to the GO within 90 calendar days of receiving the model information that the model is usable or is not usable. Who is doing the modeling? No PC here! R2 compels the GO to provide data but must provide data compatable with TP Model (also PC and WECC models) so they “should” request what is needed.

MOD-027-1 Verification of Models and Data for Turbine/Governor and Load Control or Active Power/Frequency Control Functions Purpose: To verify that the turbine/governor and load control or active power/frequency control model and the model parameters, used in dynamic simulations accurately represent generator unit real power response to system frequency variations. R1. Each TP shall provide information to the GO within 90 calendar days of receiving a written request: R5. Each TP shall provide a written response to the GO within 90 calendar days of receiving verified R2 model information that the model is usable or is not usable. Similar to MOD-026 but for real power

MOD-031-2 Demand and Energy Data Purpose: To provide authority for applicable entities to collect Demand, energy and related data to support reliability studies and assessments and to enumerate the responsibilities and obligations of requestors and respondents of that data. R2. Each TP identified in a data request shall provide the data requested by its PC or BA in accordance with the data request. R4. Any TP shall, in response to a written request for the data from a PC, BA, TP or RP with a demonstrated need for such data, provide or otherwise make available that data to the requesting entity. If you get a request you must comply for your PC and BA and “should” comply for others but some leeway allowed if external entities request data.

MOD-032-1 Data for Power System Modeling and Analysis Purpose: To establish consistent modeling data requirements and reporting procedures for development of planning horizon cases necessary to support analysis of the reliability of the interconnected transmission system. R1. Each PC and each of its TPs shall jointly develop steady-state, dynamics, and short circuit modeling data requirements and reporting procedures for the PC’s planning area... Need to coordinate with WECC for model needs

NUC-001-3 Nuclear Plant Interface Coordination Purpose: Ensure coordination between Nuclear Plant Generator Operators and Transmission Entities for the purpose of ensuring nuclear plant safe operation and shutdown.

NUC-001-3 Nuclear Plant Interface Coordination

PRC-010-2 Under Voltage Load Shedding Purpose: To establish an integrated and coordinated approach to the design, evaluation, and reliable operation of Undervoltage Load Shedding (UVLS)Programs. R1. Each PC or TP that is developing a UVLS Program shall evaluate its effectiveness and subsequently provide the UVLS Program’s specifications and implementation schedule to the UVLS entities responsible for implementing the UVLS Program.

PRC-010-2 Under Voltage Load Shedding R3. Each PC or TP shall perform an effectiveness assessment of its UVLS Programs each 60 months. R4. Each PC or TP shall, perform an assessment within 12 months of a UVLS Event R5. Each PC or TP that identifies deficiencies during R3 or R4 shall develop and distribute a Corrective Action Plan and Implementation schedule. Conditional: If only if you as a TP have a UVLS Program in your area.

TPL-007-1 Transmission System Planned Performance for Geomagnetic Disturbance Events Purpose: Establish requirements for Transmission system planned performance during geomagnetic disturbance (GMD) events. R1. Each PC, in conjunction with its TP(s), shall identify the individual and joint responsibilities of the PC and TP in the PC’s planning area for maintaining models and performing the study or studies needed to complete GMD Vulnerability Assessment(s). R2. Each TP if identified in R1, shall maintain System models and GIC System models of the responsible entity’s planning area for performing the study or studies needed to complete GMD Vulnerability Assessment(s). Only R1 Effective now but R2 becomes effective 7/1/18

TPL-007-1 Transmission System Planned Performance for Geomagnetic Disturbance Events R3 Each TP if identified in R1, shall have criteria for acceptable System steady state voltage performance for its System during the benchmark GMD event described in Attachment 1. R4 Each TP if identified in R1, shall complete a GMD Vulnerability Assessment of the Near-Term Transmission Planning Horizon once every 60 calendar months. R7. Each TP if identified in R1, that concludes, that their System does not meet the performance requirements of Table 1 shall develop a Corrective Action Plan addressing how the performance requirements will be met. These requirements are not effective until 1/1/22 Additional Requirements coming for version 2

Questions and Contacts Phil O’Donnell Manager, Operations and Planning Audits podonnell@wecc.biz Ruben Arredondo Senior Legal Counsel rarrendondo@wecc.biz