1 ERCOT Nodal Protocols Telemetry Requirements. 2 Protocol References Telemetry 3.10.7.4 TAC will establish TASK force and approve a telemetry criteria.

Slides:



Advertisements
Similar presentations
ERCOT Nodal Protocols Telemetry Requirements Proposal
Advertisements

California Independent System Operator Soumen Ghosh CAISO CONFIDENTIAL Created: 06/15/2008 State Estimator for CA ISO Market - Relevance and Readiness.
Real-Time Transmission Congestion Management & Market Effects
1 New Resource Qualification Testing Sandip Sharma Supervisor, Operations Analysis New Generation Information Forum ERCOT Public November 4, 2014.
A Partial Interim Report To WMS Guidance on Implementing Protocol Implementation Plan (PIP) 102 Reactive Power Task Force.
NERC Lessons Learned Summary March NERC lessons learned published in March 2015 Two NERC lessons learned (LL) were published in March2015 LL
October 22, 2007 TPTF Meeting Early Delivery Systems Status Update and Forecast Daryl Cote/John Webb/John Hall.
03/22/07 TPTF meeting ICCP Quality Codes Bill Blevins/Frank Kendall.
Peak RCCo Performance Metrics Draft –November 2013.
April 23 rd OWG UFLS Survey & Power Factor Review.
Demand Side Working Group Load Resource Performance Subgroup April 9, 2010 Mary Anne Brelinsky EDF Trading North America.
ROS Feb 2006 The Model Curtis Crews Network Model Engineering Supervisor
SPS policy – Information Presentation Presentation to ROS June 16, 2004.
1Texas Nodal Texas Nodal Market Trials and Data Verification ROS Meeting By Steve Grendel, ERCOT Thursday, 01/11/2007.
Lead from the front Texas Nodal 1 Texas Nodal Energy Management System Requirement Documents December 5, 2006 Jay Dondeti EMS Project.
Protocol Revision Subcommittee Presentation to the ERCOT Technical Advisory Committee March 4, 2010.
EDS 2 Early Delivery Systems Review and Request for Approval May 2007 John Webb.
NPRR514, Seasonal Generation Resource Wholesale Market Subcommittee April 12, 2013 Amanda Frazier.
SIMPLE TRANSMISSION OUTAGE. Nodal Protocol Definition 2.26 Simple Transmission Outage A Planned Outage or Maintenance Outage of any Transmission Element.
Texas Nodal 1 Nodal Operations Model Posting Confirmation TAC May 7, 2009 Matt Mereness, ERCOT.
NPRR XXX: PRR 307 Inclusion in Nodal…Part II. Questions Raised 06/26/06 Section 3 –COP (resource parameters) –CLR participation limits –Telemetry Requirements.
Protocol Revision Subcommittee Sandy Morris November 3, 2011.
Transmission Outage Process April Purpose In compliance with the Protocols and the Electric Reliability Council of Texas (ERCOT) Operating Guides,
Nodal ATF 1 Nodal Advisory Task Force Update for TAC September 2 nd, 2010.
EDS 2 Early Delivery Systems Release 3 – WebEx Conference July 10, 2007.
Nodal MIS Portal Project MIS Functions to Support EDS 3, Release 5 September 11, 2007.
1 Energy Storage Settlements Consistent with PUCT Project & NPRR461 ERCOT Commercial Market Operations May 8, 2012 – COPS Meeting May 9, 2012 – WMS.
© Property of ERCOT /17/20041 RTCA, CAM, and SFT Presented by: John Adams November 17, 2004.
2013 Wind Conference. Congestion Management & Communication Processes CJ Brown.
January 21, 2008 TPTF 168 Hour Test Initial Approach Discussion.
7 August, 2006 TPTF MMS Issues Review Brandon Whittle Lead, Real-Time Market Operations.
– 1Texas Nodal Texas Nodal Electrical Buses – 2Texas Nodal Electrical Bus Definition as Proposed in NPRR 63 Electrical Bus A physical transmission element.
DREAM November Meeting. Agenda Introduction and Expectations Path to becoming a Resource Node – ERCOT Registration process for non-modeled resources –
Appeal of PRS Action NPRR 351, Calculate and Post Projected Non-Binding LMPs for the Next 15 Minutes Floyd Trefny Texas Steel Companies.
Managing of Limits during Loss of Analysis Tools/ EMS April 23, 2014.
Floyd Trefny, P.E. Director of Wholesale Market Design Nodal Market Tools to Manage Wind Generation January 29, 2009 Presentation to the Renewables Technology.
Distributed Generation Registration June 30, 2008.
Operating Guide and Planning Guide Revision Requests Blake Williams, ROS Chair September 13, 2012.
1 State Estimator performance. 2 State of Technology Many metrics have been proposed for measuring State Estimator performance.. PI = min Σ( Z – h i (x))^
NDSWG Report June 16, NDSWG Report Regular meeting held May 16 in Taylor Telemetry / State Estimator Update Naming Convention Electrical Bus Designation.
ERCOT Guideline for Interim Updates to the Network Operations Model Excerpted from the “Modeling Expectations” whitepaper D.W. Rickerson.
October 29, 2012 RARF Workshop 2 Introduction to ERCOT Modeling Process Jay Teixeira Manager, Model Administration.
TEXAS NODAL Market Design Structure and Process August 19, 2003.
Scheduling and Operating Transmission Devices in the Nodal Environment.
Protocol Revision Subcommittee Rob Bevill January 5, 2012.
Role of Account Management at ERCOT 2006 TAC Subcommittee Review ERCOT Board February 21, 2006.
1 Nodal Stabilization Market Call December 27, 2010.
Telemetry and State Estimator Standards Network Data Support Working Group June 16, 2006.
Demand Side Working Group March 5, 2010 Mary Anne Brelinsky EDF Trading North America.
Transition Plan Network Operations Model Change Requests 5/26/2010.
Current Nodal OS Design 1.The NMMS database will have an OWNER and an OPERATOR designation for each piece of equipment in the model. The OWNER and OPERATOR.
ERCOT Wholesale Market SubcommitteeJanuary 12, ERCOT Wholesale Market SubcommitteeJanuary 12, ERCOT/IMM/PUCT Proposal for Redaction of State.
Text reason for Deviation from Defined High Sustained Limit/Low Sustained Limit John Adams January 5, 2010 Nodal Advisory Task Force.
Day-Ahead Market Discussion/Clarification TPTF April 24, 2006.
Approval of Important Station Voltages for State Estimator Reporting Review of SE and Telemetry Standards Alex Sills Advanced Network Applications 10/13/11.
Lead from the front Texas Nodal 1 Texas Nodal Energy & Market Management System EMS/MMS Projects Requirement Documents November.
PRS Workshop- NPRR755/NOGRR154 WAN communications of Critical Market Data and Agency-Only QSE Feb 29, 2016.
February 26, 2015 Technical Advisory Committee (TAC) Update to RMS Kathy Scott March 3, 2015 TAC Update to RMS 1.
EDS 2 Early Delivery Systems Approach March 2007.
Nodal Planning Go Live Austin, TX February 3, 2011
Current Nodal OS Design 1.The NMMS database will have an OWNER and an OPERATOR designation for each piece of equipment in the model. The OWNER and OPERATOR.
Information Needed By All Market Participants To Facilitate Transmission Congestion Studies In ERCOT Presented to the ERCOT ROS by Shannon Caraway, P.E.
Reliability Must Run Workshop RMR Study Process May 24, 2016.
Market Trials Update NATF March 2,
NMT – Network Operations Modeling & Telemetry - Project
Current FRRS Language & Explanation of Posted Data
Phase Angle Limitations
TAC Report to the ERCOT Board
Reactive Power Task Force
“TOP-010-1: Data Quality, Analysis Quality, and Alarm Process Monitor”
Presentation transcript:

1 ERCOT Nodal Protocols Telemetry Requirements

2 Protocol References Telemetry TAC will establish TASK force and approve a telemetry criteria – update each October. Telemetry req. will define performance & observablity of voltage and power flow measurements including redundancy and telemetry measurement data required to support State Estimator in meeting the approved performance standard and to support TAC approved accuracy standards for the calculation of LMP. Telemetry from TSP updated 10 second or less scan rate and provided to ERCOT at the same rate. Each TSP & QSE install appropriate detection capability to inform ERCOT of potentially incorrect data…Condition codes accompany data to indicate its quality and if measured within scan requirement. ERCOT to analyze data for possible loss of updates. ERCOT provide condition detection capability on loss of telemetry links. ERCOT represent condition codes in a consistent manner all applications.

Each TSP/QSE use fully redundant communication links (ICCP or RTU) such that any single element can fail & 1.For server failures complete information re-established within 5 minutes 2. For other failures complete information continues at 30 second or less scan rate 5.When ERCOT identifies a reliability concern… ERCOT may request that a TSP or QSE provide additional telemetry measurements beyond those required by the Telemetry Criteria, in a reasonable timeframe. Such requests include written justification …including documentation of deficiency in system observabity…ERCOT should consider economic implications of inaccurate representation of Load models in LMP results vs the cost to remedy Protocol References Telemetry

(6)Within 30 days of submittal by ERCOT to the designated contact of a TSP or QSE with a written request justifying additional telemetry measurements, the TSP or QSE shall acknowledge the request and either: (a)Agree with the request and make reasonable effort to install new equipment providing measurements to ERCOT within the timeframe specified; (b)provide ERCOT an analysis of the cost to comply with the request, so that, ERCOT can perform a cost justification with respect to the LMP market; or (c)if the TSP or QSE disagrees with the request, appeal that request to TAC or present an alternate solution to ERCOT for consideration. Protocol References Telemetry

)If ERCOT rejects the alternate solution, the TSP or QSE may appeal the original request to TAC within 30 days. If, after receiving an appeal, TAC does not resolve the appeal within 65 days, the TSP or QSE may present its appeal to the ERCOT Board. Notwithstanding the foregoing, a TSP or QSE is not required to provide telemetry measurements from a location not owned by that TSP or QSE, if the location owner does not grant access to the TSP or QSE for the purpose of obtaining such measurements. ERCOT shall report such cases to the Wholesale Electric Market Monitor. Protocol References Telemetry

(1)Each TSP and QSE shall provide telemetry, as described in this subsection, to ERCOT on the status of all breakers and switches used to switch any Transmission Element or load modeled by ERCOT. Each TSP and QSE is not required to install telemetry on individual breakers and switches, where the telemetered status shown to ERCOT is current and free from ambiguous changes in state caused by the TSP or QSE switching operations and TSP or QSE personnel. Each TSP or QSE shall update the status of any breaker or switch through manual entries, if necessary, to communicate the actual current state of the device to ERCOT, except if the change in state is expected to return to the prior state within one minute. If in the sole opinion of ERCOT, the manual updates of the TSP or QSE have been unsuccessful in maintaining the accuracy required to support State Estimator performance to a TAC-approved predefined standard as described in Section , State Estimator Performance Standard, ERCOT may request that the TSP or QSE install complete telemetry from the breaker or switch to the TSP or QSE, and then to ERCOT. In making the determination to request installation of additional telemetry from a breaker or switch, ERCOT shall consider the economic implications of inaccurate representation of Model Loads in LMP results versus the cost to remedy. Protocol References Telemetry

(2)ERCOT shall measure TSP or QSE performance in providing accurate data that do not include ambiguous changes in state and shall report the performance metrics on the MIS Secure Area on a monthly basis. (3)Unless there is an emergency condition, a TSP or QSE must obtain approval from ERCOT to purposely open a breaker or switch unless that breaker or switch is shown in a Planned Outage in the Outage Scheduler, or the device will return to its previous state within one minute. Also, a TSP or QSE must obtain approval from ERCOT before closing any breaker or switch, except in response to a Forced Outage, or an emergency, or the device will return to its previous state within one minute. Protocol References Telemetry

(4)ERCOT shall monitor the data condition codes of all breakers and switches showing loss of communication or scan function in the Network Operations Model. When the telemetry of breakers and switches is lost, ERCOT shall use the last known state of the device for Security Analysis as updated by the Outage Scheduler and through verbal communication with the TSP or QSE. ERCOT’s systems must identify probable errors in switch or breaker status and ERCOT shall act to resolve or correct such errors in a timely manner as described in Section 6, Adjustment Period and Real-Time Operations. (5)ERCOT shall establish a system that provides alarms to ERCOT operators when there is a change in status of any monitored transmission breaker or switch, and an indication of whether the device change of status was planned in the Outage Scheduler. ERCOT operators shall monitor any changes in status not only for reliability of operations, but also for accuracy and impact on the operation of the Security Constrained Economic Dispatch functions and subsequent potential for calculation of inaccurate LMPs…. Protocol References Telemetry

Continuous Telemetry of the Real-Time Measurements of Bus Load, Voltages, Tap Position, and Flows (1)Each TSP or QSE shall provide telemetry of voltages, flows, and Loads on any modeled Transmission Element to the extent such may be required to estimate all transmission Load withdrawals and generation injections to and from the ERCOT Transmission Grid using the State Estimator and as needed to achieve the TAC-approved SE performance standard with consideration given to the economic implications of inaccurate LMP results versus the cost … (3)Each TSP shall provide telemetered measurements on modeled Transmission Elements to ensure State Estimator observability, per TAC-approved Telemetry Criteria, of any monitored voltage and power flow between their associated transmission breakers to the extent such can be shown to be needed in achieving the TAC-approved SE performance standard. On monitored non- Load Electrical Buses, each TSP shall install, at the direction of ERCOT, sufficient telemetry such that there is an “N-1 Redundancy.” An N-1 Redundancy exists if the Electrical Bus remains observable on the loss of any single measurement pair (kW, kVar) excluding station RTU communication path failures. In making the determination to request additional telemetry, ERCOT shall consider the economic implications of inaccurate representation of Load Models in LMP results versus the cost to remedy. Protocol References Telemetry

Continuous Telemetry of the Real-Time Measurements of Bus Load, Voltages, Tap Position, and Flows (4)The accuracy of the State Estimator is critical to successful market operations. For this reason it is a critical objective for ERCOT to maintain reasonable and accurate results of the State Estimator. ERCOT shall use all reasonable efforts to achieve that objective, including the provision of legitimate constraints used in calculating LMPs. (5)Each TSP, QSE and ERCOT shall develop a continuously operated program to maintain telemetry of all Transmission Element measurements to provide accurate results using TAC-approved accuracy standards from the State Estimator. For any location where there is a connection of multiple, measured, Transmission Elements, ERCOT shall have an automated process to detect and notify ERCOT system operators if the residual sum of all telemetered measurements is more than (a) five percent of the largest line rating at the Electrical Bus or (b) five MW, whichever is greater. If a location chronically fails this test, ERCOT shall notify the applicable TSP or QSE and suggest actions that the TSP or QSE could take to correct the failure. Within 30 days, the TSP or QSE shall take the actions necessary to correct the failure or provide ERCOT with a detailed plan with a projected timeframe to correct the failure. ERCOT shall post a notice on the MIS Secure Area of any Electrical Buses not meeting TAC-approved accuracy requirements, including a list of all measurements and the residual errors on a monthly basis. Protocol References Telemetry

Continuous Telemetry of the Real-Time Measurements of Bus Load, Voltages, Tap Position, and Flows (6)ERCOT shall implement a study mode version of the State Estimator with special tools designed for troubleshooting and tuning purposes that can be used independently of any other ERCOT process that is dependant on the real time State Estimator. ERCOT shall implement a process to recognize inaccurate State Estimator results and shall create and implement alternative Real-Time LMP calculation processes for use when inaccurate results are detected. ERCOT must be guided in this by TAC-approved accuracy standards. (7)ERCOT shall establish a system to provide overload and over/under limit alarming on all Transmission Elements monitored as constraints in the LMP models. Protocol References Telemetry

12 Protocol References State Estimator State Estimator Performance Standard (1)The appropriate TAC subcommittee shall establish a task force that is open to Market Participants, comprised of technical experts to develop a State Estimator Performance Standard consistent with the minimum requirements of the Protocols. TAC shall approve the State Estimator Performance Standards, and the appropriate TAC subcommittee shall update the State Estimator Performance Standards annually each October or more often on a periodic basis as deemed necessary.

13 Protocol References State Estimator State Estimator Performance Standard (2)The State Estimator Performance Standard must define the performance requirements necessary to provide State Estimator results within a TAC- defined level of confidence and results for LMP calculation that meet TAC-approved accuracy standards. The appropriate TAC subcommittee shall coordinate with Market Participants to ensure a common understanding of the level of State Estimator performance required to enable LMP calculation that meets TAC-approved accuracy standards. Further, the standard must address the State Estimator’s ability to detect, correct, or otherwise accommodate communications system failures, failed data points, stale data condition codes, and missing or inaccurate measurements to the extent these capabilities contribute to LMP accuracy and State Estimator performance or as needed to meet reliability requirements.

14 Protocol References State Estimator Considerations for Performance Standards In developing the State Estimator Performance Standard recommendations to TAC, the following may be considered: (a)Desired confidence levels of State Estimator results. (b)Measurement requirements to estimate power injections and withdrawals at transmission voltage Electrical Buses defined in the SCED transmission model, which may provide for variations in criteria based on: (i)The number of Transmission Elements connected to a given transmission voltage Electrical Bus; (ii)The peak demand of the Load connected to a transmission voltage Electrical Bus; (iii)The total of Resource capacity connected to a transmission voltage Electrical Bus; (iv)The nominal transmission voltage level of a Electrical Bus; (v)The number of Electrical Buses with injections or withdrawals along a circuit between currently monitored transmission voltage Electrical Bus; (vi)Connection of Loads along a continuous, non-branching circuit that may be combined for modeling purposes; (vii)The quantity of Load at a Electrical Bus that may have its connection to the transmission system automatically transferred to an Electrical Bus other than the one to which it is normally connected (rollover operation); (vii)Electrical proximity to more than one Resource Node;… OTHERS

15 Protocol References State Estimator Considerations for Performance Standards In developing the State Estimator Performance Standard recommendations to TAC, the following may be considered: (c)Sensitivity of State Estimator results with respect to variations in input parameters; (d)Reasonable safeguards to assure State Estimator results are calculated on a non-discriminatory basis; and (e)Other parameters as deemed appropriate.

16 Summary of requirements All switch and breaker status telemetered to ERCOT All telemetry 10 second update or less All telemetry with quality codes All communications redundant – server failure recover within 5 Min. Any other failure recover 30 second update ERCOT posts performance ERCOT analyzes for topology errors and resolves TSP or QSE shall provide telemetry of voltages, flows, and Loads on any modeled Transmission Element to the extent such may be required to estimate all transmission Load withdrawals and generation injections On monitored non-Load Electrical Buses, each TSP shall install, at the direction of ERCOT, sufficient telemetry such that there is an “N-1 Redundancy.” residual sum of all telemetered measurements is more than (a) five percent of the largest line rating at the Electrical Bus or (b) five MW, whichever is greater. If a location chronically fails this test, ERCOT shall notify the applicable TSP or QSE and suggest actions that the TSP or QSE could take to correct the failure standard must address the State Estimator’s ability to detect, correct, or otherwise accommodate communications system failures, failed data points, stale data condition codes, and missing or inaccurate measurements to the extent these capabilities contribute to LMP accuracy and State Estimator performance or as needed to meet reliability requirements.

17 BREAK