Current Telemetry Dashboards

Lead from the frontTexas Nodalhttp://nodal.ercot.com 1

Current Telemetry Dashboards

NDSWG

August 18, 2009


QSE Telemetry (as of 08/10/09)


TDSP Telemetry (as of 08/10/09)


Load Observability (as of 08/10/09)

Lead from the frontTexas Nodal

State Estimator Daily Convergence Rates: July 2009

http://nodal.ercot.com 5

2009 Monthly Convergence %

Jan: 80% Feb: 70% Mar: 90% Apr: 86% May: 77% Jun: 88% Jul: 87%


State Estimator Monthly Convergence Rates: May 2009 – July 2009

2009 Monthly Convergence %

Jan: 80% Feb: 70% Mar: 90% Apr: 86% May: 77% Jun: 88% Jul: 87%


July 2, 2009

0102030405060708090

100

1 2 3 4 5 6 7 8 9

Test Hour

Co

nv

erg

en

ce

%

0900

1000

1100

1200

1300

1400

1500

1600

1700

Hour Ending

July 1, 2009

0102030405060708090

100

1 2 3 4 5 6 7 8 9

Test Hour

Co

nv

erg

en

ce

%

0900

1000

1100

1200

1300

1400

1500

1600

1700

Hour Ending

June 30, 2009

0102030405060708090

100

1 2 3 4 5 6 7 8 9

Test Hour

Co

nv

erg

en

ce

%

0900

1000

1100

1200

1300

1400

1500

1600

1700

Hour Ending

Key Numbers: 91% Test Average Convergence; 100% for 11 of 27 Test Hours. The majority of

issues were attributable to zonal-nodal mismatches. On June 30, eight of nine test hours achieved convergence rates of 92% or

higher. All issues were attributable to Manual Replacements (MRs) necessary to address zonal-nodal mismatches.

• On July 1, five of nine hours achieved convergence rates of 92% or higher. Convergence rates were affected intermittently throughout the day owing to MRs necessary to accommodate a group of wind farms moving Inter-Control Center Communication Protocol (ICCP) service to a different provider. A nodal database load was conducted in the afternoon, but it did not significantly affect State Estimator convergence.

On July 2, additional MRs were needed throughout the day to accommodate intermittent wind telemetry (carry-over issue from Day Two). MRs were also necessary throughout the day to address a known reactive capability curve issue that was limiting the ERCOT State Estimator’s ability to recognize MVAR values beyond a pre-defined limit (this curve issue was later addressed through code enhancements that were deployed on July 15).


FIT III, Week 10 – State Estimator


July 14, 2009

0102030405060708090

100

1 2 3 4 5 6 7 8 9

Test Hour

Co

nve

rgen

ce %

0900

1000

1100

1200

1300

1400

1500

1600

1700

Hour Ending

Key Numbers:

91% Test Average Convergence; 100% for 14 of 27 Test Hours. The majority of issues were attributable to zonal-nodal mismatches.

Day One:

On July 14, the average convergence for the test day finished at 91%. Rates of 92% or higher were achieved during 6 of 9 test hours. Notable issues occurred during the following test hours:

Hour Ending (HE) 0900- the hourly convergence rate dipped to 75% as Manual Replacements (MRs) were made to address telemetry issues that accumulated during the non-Business Hours immediately prior to testing.

HE 1300- the hourly convergence dipped to 86% as MRs were made to adjust telemetry values for a failed Inter-Control Center Communication Protocol (ICCP) link.

HE 1600- the hourly convergence dipped to 75% as MRs were made to adjust telemetry values for a failed ICCP link.




Day Two:

On July 15, the average convergence for the test day finished at 85%. Rates of 92% or higher were achieved during 5 of 9 test hours. Notable issues occurred during the following test hours:

HE 0900- the hourly convergence dipped to 42% as MRs were made to address telemetry issues that accumulated during the non-Business Hours immediately prior to testing (i.e., same issue as on Day One).

HE 1000- the hourly convergence dipped to 79% as MRs were made to address zonal-nodal mismatches.

HE 1400- the hourly convergence dipped to 82% as MRs were made to address zonal-nodal mismatches.

HE 1700- the hourly convergence dipped to 77% as MRs were made to adjust telemetry values for a failed ICCP link.

A nodal database load was performed in the afternoon, but it did not significantly affect State Estimator convergence rates for the test day.


FIT III, Week 11 – State Estimator (continued)

July 15, 2009

0102030405060708090

100

1 2 3 4 5 6 7 8 9

Test Hour

Co

nve

rgen

ce %

0900

1000

1100

1200

1300

1400

1500

1600

1700

Hour Ending

Note:

Code enhancements for the State Estimator exited FAT and were deployed on July 15. The enhancements were implemented to address a reactive capability curve issue that had previously limited the ERCOT State Estimator’s ability to recognize MVAR values beyond a pre-defined limit. At present, the enhancements appear to be supporting State Estimator convergence as intended.


July 16, 2009

0102030405060708090

100

1 2 3 4 5 6 7 8 9

Test Hour

Co

nve

rgen

ce %

0900

1000

1100

1200

1300

1400

1500

1600

1700

Hour Ending

Day Three:

On July 16, The average convergence for the test day finished at 98%. Rates of 92% or higher were achieved during 8 of 9 test hours. Notable issues occurred during the following test hours:

HE 1000- the hourly convergence dipped to 86% as MRs were made to adjust for telemetry not yet mapped in nodal.


FIT III, Week 11 – State Estimator (continued)


Key Numbers and Issues: 95% Test Average Convergence 92% or higher for 21 of 27 Test Hours 100% for 18 of 27 Test Hours The majority of issues that arose during the test were

attributable to zonal-nodal mismatches as well as missing nodal telemetry. Shift Engineers logged over 30 manual replacements throughout the test to address unit telemetry not yet mapped in nodal systems. This issue resulted in two noticeable drops in convergence during the test:

The first drop occurred on July 28, when Hour Ending (HE) 1100 converged at 79%.

The second drop occurred on July 29, when HE 1100 converged at 69%.



Lead from the frontTexas NodalLFC04/20/23

FIT Series

Week Date Day 1 Day 2 Day 3 Average Convergence % for all Test

Hours

100% Convergence Achieved

FIT II Week 1 Oct 21 – 23, 2008 90.18 74.16 91.83 85.39 12 of 27 hrs

Week 2 Nov 04 – 06, 2008 88.17 96.58 97.11 93.95 18 of 27 hrs

Week 3 Nov 18 – 20, 2008 87.17 84.19 82.91 84.76 12 of 27 hrs

Week 4 Dec 02 – 04, 2008 96.04 93.33 93.44 94.27 14 of 27 hrs

Week 5 Dec 16 – 18, 2008 94.74 97.49 96.30 96.18 19 of 27 hrs

Week 6 Jan 13 – 15, 2009 96.00 94.12 95.78 95.30 15 of 27 hrs

Week 7 Jan 27 – 29, 2009 94.07 90.13 93.29 92.49 14 of 27 hrs

FIT III

Week 1 Feb 24 – 26, 2009 75.45 78.86 92.85 82.39 09 of 27 hrs

Week 2 Mar 10 – 12, 2009 96.82 92.97 98.41 96.07 20 of 27 hrs

Week 3 Mar 24 - 26, 2009 85.45 94.98 94.70 91.71 14 of 27 hrs

Week 4 Apr 07 - 09, 2009 97.13 92.60 97.44 95.72 21 of 27 hrs

Week 5 Apr 21 – 23, 2009 87.47 89.87 95.65 91.00 08 of 27 hrs

Week 6 May 05 – 07, 2009 94.34 94.47 91.87 93.56 13 of 27 hrs

Week 7 May 19 – 21, 2009 96.81 97.36 97.04 97.07 18 of 26 hrs*

Week 8 Jun 02 – 04, 2009 88.47 84.09 93.29 88.62 10 of 27 hrs

Week 9 Jun 16 – 18, 2009 97.45 86.14 95.59 93.06 13 of 27 hrs

Week 10 Jun 30 – Jul 2, 2009 94.91 89.89 86.66 90.49 11 of 27 hrs

Week 11 Jul 14 – 16, 2009 91.01 84.70 97.49 91.06 14 of 27 hrs

Week 12 Jul 28 – 30, 2009 95.91 94.73 93.66 94.77 18 of 27 hrs

Trends – FIT II & FIT III

12

* One hour was removed from the Week 7 test results to accommodate a nodal database load.


Appendix: Telemetry & State Estimator

Overview of Reports, Processes, and Data


ICCP

• Telemetry Support• Telemetry Reporting• State Estimator Tuning• New Telemetry Point Addition Process• Telemetry Issue Process• Current Telemetry Status• Telemetry Status Whereabouts


Telemetry Support

• ERCOT Full Time Staff ICCP Support– Advanced Network Applications Support 2 Engineers– Control Room 1 Operations Analyst & 1 Shift Engineer– IT 2 System Analysts– Additional Staff on a part time basis

• Market Participants– Contact for Nodal Issues– Timely Response on detected issues


Telemetry Dashboards

FIT II & FIT III Assessment reports are posted at: http://nodal.ercot.com/readiness/eds3/documents/index.html

• The following Telemetry Dashboards are being posted on the Readiness Center:– Observability– QSER & TDSP Telemetry

• The link for these dashboards is:

http://nodal.ercot.com/readiness/eds1/documents/index.html

• These dashboards are currently being posted monthly following each mid-month Nodal database update.

• Report questions can be sent to [email protected]


Telemetry Dashboards

TelemetryDashboards

}


Telemetry Reporting – QSER/TDSP Dashboard

QSER & TDSP Dashboard

Questions may be sent to: [email protected]


Telemetry Reporting – Observability Dashboard

The number of unobservable buses in the system with all pseudo measurement removed.

The number of current unobservable buses in the system that have a load at the station where

telemetry is required to make the bus observable.

Buses that are unobservable due to a PUN load at the station.

If a number other then 0 is in column B, then there is missing telemetry which requires Market Participant Corrective Action.

Questions may be sent to: [email protected]


Telemetry Reporting

State Estimator (SE) Convergence

• Advanced Network Applications provides analysis assistance and can be reached at the EDS2 email: [email protected]


State Estimator Tuning

• FIT– Monitors Telemetry– Compares Generation between Zonal & Nodal

• ICCP Support Team– Analysis Support of FIT Issues– ICCP Issue Resolution Support– Produce FIT Report


FIT Telemetry Reporting

FIT Report• Log of Events &

Observations– The daily logs published in

the bi-weekly FIT Reports provide a window into the types of issues that affect convergence during FIT testing hours.

• FIT Reports are posted at: http://nodal.ercot.com/readiness/eds3/documents/index.html

Questions can be sent to [email protected]


New Telemetry Point Addition Process

MP (QSER or TSP) has new ICCP point to

activate

MP Consults ICCP Handbook to

determine data point names

MP fills out ICCP Change Request Form

MP creates a Service Request via the Texas

Market Link on ERCOT.com

MP attaches completed ICCP

Change Request form to Service Request

ERCOT ICCP Team receives and

processes each Service Request

No

ERCOT ICCP Team contacts MP to confirm the changes

ERCOT ICCP Team notifies the MP

upon completion of the Service Request

Service Request Issues?

Yes

ERCOT ICCP Team makes changes to

ICCP

No

MP has submitted & completed

Model Change

ICCP Standards Questions?

Yes


Current Telemetry Issue Process

ERCOT or Market Participant detects Telemetry, ICCP or other System Issue

Market Participant investigates to

determine correct ability

Requires ERCOT assistance to

resolve?

Contact ERCOT ANA by email

[email protected] for assistance

Yes

No

ERCOT Analyzes Issue and determines

corrective action

ERCOT Contacts MP to Affect Correction

Issue Resolved?

Done

Yes

NoMP Corrects Issue

During FIT? No

Yes

Contact ERCOT Shift Engineer @

512-248-6345

Documents

Current Telemetry Dashboards