OWG Report

NOGRR Number / 162 / NOGRR Title / Process for Resolving Real-Time Data Discrepancies
Date of Decision / August 18, 2016
Action / Tabled
Timeline / Normal
Proposed Effective Date / To be determined
Priority and Rank Assigned / To be determined
Guide Sections Requiring Revision / 7.3.3, Data from QSEs and TSPs to ERCOT
7.3.4, Data Quality and Resolving Real-Time Data Conflicts (New)
7.3.4, TSP and QSE Telemetry Restoration (Delete)
7.3.5, General Telemetry Performance Criterion (Delete)
Related Documents Requiring Revision/Revision Requests / None
Revision Description / This Nodal Operating Guide Revision Request (NOGRR) establishes a process for resolving Real-Time data discrepancies that affect ERCOT’s Network Security Analysis (NSA).
Reason for Revision / Addresses current operational issues.
Meets Strategic goals (tied to the ERCOT Strategic Plan or directed by the ERCOT Board).
Market efficiencies or enhancements
Administrative
Regulatory requirements
Other: (explain)
(please select all that apply)
Business Case / North American Electric Reliability Corporation (NERC) Reliability Standard IRO-010-2, Reliability Coordinator Data Specification and Collection, requires ERCOT and applicable Entities to have a mutually agreeable process for resolving Real-Time data conflicts.
OWG Decision / On 7/21/16, the Operations Working Group (OWG) was in consensus to table NOGRR162.
On 8/18/16, OWG was in consensus to continue to table NOGRR162.
Summary of OWG Discussion / On 7/21/16, participants discussed NERC Reliability Standard IRO-010-2; whether the discrepancy resolution window might be expanded to 48 Business Hours; and whether language could be developed to address third-party response timelines.
On 8/18/16, participants reviewed the 8/11/16 ERCOT comments; discussed different timeframes for manually updating data; and requested a WebEx be scheduled to further discuss the language before the next OWG meeting.
Sponsor
Name / Stephen Solis
E-mail Address /
Company / ERCOT
Phone Number / 512-248-6772
Cell Number
Market Segment / Not applicable
Market Rules Staff Contact
Name / Brittney Albracht
E-Mail Address /
Phone Number / 512-225-7027
Comments Received
Comment Author / Comment Summary
Luminant 072916 / Proposed data replacement or a specific resolution plan within ten minutes and suggested revising original language to allow 30 minutes for data replacement
ERCOT 081116 / Restored paragraphs (4) and (5) in Section 7.3.3 to delineate expectations relative to common telemetry data issues not affecting ERCOT NSA and suggested edits to clarify Entities involved and to structure similar to the proposed Section 7.3.4 without the ten minute requirements
CenterPoint Energy 081516 / Recommended ERCOT either meet with the Network Data Support Working Group (NDSWG) or host a workshop to first review the State Estimator Standards and Telemetry Standards
Market Rules Notes

Please note that the following NOGRR(s) also propose revision(s) to the following section(s):

·  NOGRR154, Alignment with NPRR755 and Requirements for ERCOT WAN Installation and Exchange of Resource-Specific XML Data

o  Section 7.3.3

Proposed Guide Language Revision

7.3.3 Data from QSEs and TSPs to ERCOT

(1) Each TSP and QSE shall provide telemetered measurements on modeled Transmission Elements as required by the Protocols and the ERCOT Nodal ICCP Communications Handbook.

(2) QSEs and TSPs shall provide Real-Time monitoring of power system quantities to ERCOT as defined in the Protocols and the ERCOT Nodal ICCP Communications Handbook. ERCOT shall work with TSPs and QSEs to determine the required data using the methodology presented in the Protocols. Transmission Element status and analog measurements that the TSPs and QSEs define in the Network Operations Model shall, at a minimum, be provided to ERCOT. Ultimately, it is the responsibility of the TSPs and QSEs to provide all data requested by ERCOT.

(3) Real-Time telemetry data from QSEs used to supply power or Ancillary Services shall be integrated by ERCOT and checked against settlement meter values on a monthly basis.

(4) Each QSE and TSP shall notify ERCOT as soon as practicable when telemetry will not be available or is unreliable for operational purposes. The report, as outlined in Section 9.2.2, Real-Time Data Monitor, will contain unavailability data associated with Planned Outages of RTUs.

(5) Each QSE and TSP shall notify ERCOT as soon as practicable when telemetry is returned to normal state.

7.3.4 Data Quality and Resolving Real-Time Data Conflicts

(1) ERCOT will notify the QSE or TO responsible for the data when a Real-Time data discrepancy affects ERCOT’s Network Security Analysis (NSA). The QSE or TO shall resolve the Real-Time data discrepancy or manually replace the data within 10 minutes of notification. Manually replaced data shall be updated at least every 10 minutes until the Real-Time data discrepancy is resolved.

(2) The QSE or TO shall resolve the discrepancy as soon as practicable. If the QSE or TO cannot resolve the discrepancy within 48 hours, it shall provide an estimated time of resolution. The QSE or TO shall notify ERCOT when the Real-Time data discrepancy is resolved.

7.3.4 TSP and QSE Telemetry Restoration

Real-Time telemetry data shall be restored using criteria and procedures as established by the Telemetry Standards.

7.3.5 General Telemetry Performance Criterion

All Real-Time telemetry as required by the Protocols shall meet the State Estimator Standards and the Telemetry Standards.

162NOGRR-07 OWG Report 081816 Page 3 of 4

PUBLIC