Nodal Reliability Performance Measures Workshop Project No. 37052 Public Utility Commission of Texas...

Nodal Reliability Performance Measures Workshop

Project No. 37052Public Utility Commission of Texas

June 12, 2009

1

Nodal Reliability and Regulatory Oversight• Goals for Go-live:– Adequate PUCT oversight of market on first day– Enforcement to consider new market limitations• Reasonableness• Metric adjustment and tuning process

– Reliability and Compliance Training Plan– Monitoring reports are tested and useable– Longer term plan for additional metrics, if needed– Clear communication of regulatory oversight and

risk

2

Approach• PUCT, Texas RE, IMM and ERCOT ISO have taken

a proactive approach– Define a minimum set of reliability metrics and

criteria (NPRRs and NOGRRs) necessary to enable go live

– Implement a gap analysis– Create NPRRs and NOGRRs to fill gaps– Work through Stakeholder process to enact in time

for market trials with urgent status– Ensure proper reports are ready for monitoring and

enforcement– Create regulatory training and roll out plan

3

Other Issues• Plan to submit resulting NPRRs and

NOGRRs to ERCOT process for approval using urgent status

• Leverage NOGRR-025 work and integrate results into stakeholder process

• Reliability metrics and criteria to be in place for market trials for testing

• Minimized impact to Nodal Project (no code changes to core systems)

4

Reliability Issues• 55 issues affecting reliability of the ERCOT grid

were identified• Of these, 24 are deemed to be critical for Nodal

go-live regulatory oversight• Of these 24, 12 will require protocol or operating

guide changes• The remaining 12 issues are already addressed in

existing protocols or operating guides• Many of the other 31 issues will be ready for go-

live or should be addressed within a short time frame after nodal go-live

5

Design Requirements

• Criteria must be defined that detail what he expect behavior is and how it will be measured

• Metrics must be defined that clearly identify what is passing and what is failing

• The mechanism for monitoring performance, reporting potential failure and communicating this to Texas RE must be included

6

Reporting

• Reports will need to be developed to generate exception reports on a periodic basis (e.g. monthly) to identify failures of calculated metrics

• Complaint process may be used to identify incident-oriented failures

• Trending metrics may be defined that are intended to monitor an issue but that are not intended to be used for violations

7

Organization

8

Not needed @

go-live

Critical for go-live, already covered

Critical for go-live work

needed

Binding Documents

• State Estimator• Telemetry Standards• Any other applicable binding documents

9

Real-time > ISO > FrequencyOG: NP: 8.2(2)(b)(vii)

10

Metric Criteria Report

CPS1 (not changing) The BA must maintain a minimum of 100% for 12 months per NERC BAL-001 standards

This is to be reported to TAC for their review per the protocol reference

Critical for Nodal go-live. Already covered.

Real-time > ISO > Event Recovery > DCSOG: NP: 8.2(b)(vii)

11

Metric Criteria ReportA Balancing Authority performance is based on the pre-disturbance ACE and it's ACE at then end of the Disturbance Recovery Period (15 minutes after the disturbance).

Percent Recovery is calculated in the following way:- ACE(pre) = pre-disturbance ACE- ACE(max) = max. algebraic value of ACE measured within the 15 minutes following the disturbance- MW(loss) = MW size of disturbance- R = Percent Recovery For loss of generation: If ACE(pre) < 0 R = 100*(MW(loss) - max(0, ACE(pre) - ACE(max)))/MW(loss) Else R = 100*(MW(loss) - max(0, - ACE(max)))/MW(loss) This must be calculated for all disturbances greater than or equal to 80% of the magnitude of the BA's most severe single contingency loss

An average percent recovery will be calculated for all reportable disturbances in a quarter. This value must be greater than 100% per NERC BAL-002 Standards

This is to be reported to TAC for their review as per the protocol reference


Real-time > ISO > Event Recovery > EEA-EILSOG: NP: 8.1.3.1, 8.1.3.4

12


Compliance during an EILS deployment is determined using EILS Interval Performance Factors (EIPFs).

For EILS deployment, the average of the EIPFs during the entire curtailment period must be greater than or equal to 0.95 for the event to meet the performance obligations for that event.

ERCOT shall post to the MIS Certified Area a summary of each QSE’s EILS Load availability and performance for each Contract Period.


Real-time > ISO > Constraints > IROLsOG: 9.12.1(1), 9.12.4 NP: 8.2.(2)(d)

13


(a) Exceedance of system operating limits or power transfer limitations set by ERCOT to guard against post-contingency stability exceedance;(b) N-1 post-contingency exceedance of equipment ratings provided by Transmission Service Providers (TSPs) and Qualified Scheduling Entities (QSEs);

(a) Violation has occurred if a exceedance is for 30 continuous minutes or more

(b) Violation has occurred if a exceedance is for 30 continuous minutes or more.

ERCOT is reporting these values monthly.


Real-time > ISO > Constraints > SOLsOG: 9.12.1(1), 9.12.4 NP: 8.2.(2)(d)

14

Metric Criteria Report(a) Base power exceedance detected during the month, the time duration of the loading above normal operating limit or, the average operating limit but below or at the emergency (2 hour) operating limit; (b) Base power exceedance detected during the month, the time duration of the loading above emergency (2 hour) operating limit or, the average emergency (2 hour) operating limit ;

Recommended:(a) Violation has occurred if a exceedance is for 30 continuous minutes or more

(b) Violation has occurred if a exceedance is for 15 continuous minutes or more

ERCOT is reporting these values monthly.

Not needed for oversight at go-live. NPRR/NOGRR required to adopt criteria.

Real-time > ISO > Constraints > Maintain proper bus voltage limitsOG: 9.12.9, 2.7 NP: 3.15.1, and 6.5.7.7

15


These are being reported but levels of exceedance recommended:(a) Real Time voltage exceedance greater than 1.05pu or below 0.95pu of nominal voltage detected during the month; (b) N-1 voltage exceedance greater than 1.10pu or below 0.90pu of nominal voltage detected during the month;

Recommended:(a) Violation has occurred if a exceedance is for 30 continuous minutes or more

(b) Violation has occurred if a exceedance is for 30 continuous minutes or more

ERCOT is reporting these values monthly by TSP.

Not needed for oversight at go-live. NPRR/NOGRR required to adopt criteria.

Real-time > ISO > State Estimator > State Estimator StandardsOG: 9.12.1(4)(a) NP: 8.2(2)(a)(iii)

16

Metric Criteria Report(1) State Estimator convergence.

(2) On transmission elements identified as causing 80% of congestion cost in the latest year for which data is available, the residual difference between State Estimator results and Power Flow results for critically monitored transmission element MW flows.

(3) On transmission elements identified as causing 80% of congestion cost in the latest year for which data is available, the difference between the MW telemetry value and the MW SE value.

(4) On 20 most voltage critical buses designated by ERCOT and approved by TAC each October; the telemetered bus voltage minus state estimator voltage.

(5) On all transmission elements greater than 100kV; the difference between state estimator MW solution and the SCADA measurement.

(1) Must converge 97% of runs during a monthly test period.

(2) The calculated residual differences shall be less than 3% of the associated element emergency rating on at least 95% of samples measured in a one month trial.

(3) The calculated differences shall be less than 3% of the associated element emergency rating on at least 95% of samples measured in a one month trial.

(4) The calculated differences shall be within the greater of 2% or the accuracy of the telemetered voltage measurement involved for at least 95% of samples measured during a 1 month trial.

(5) The calculated differences will be less than 10 MW or 10% of the associated emergency rating (whichever is greater) on 99.5% of all elements during a 30 day period. All equipment failing this test will be reported to the associated TSP for repair within 10 days of detection.



Real-time > ISO > Operating/Ancillary Reserves > RegulationOG: NP: 6.5.7.5(1)(h)

17


Ancillary Service Procurement Methodology

Ancillary Service Requirement defined in the methodology and is Board approved

None

Not needed for oversight at go-live. No action required.

Real-time > ISO > Operating/Ancillary Reserves > Non-spinOG: NP: 6.5.7.5(1)(d)-(g)

18




None


Real-time > ISO > Operating/Ancillary Reserves > Responsive ReservesOG: 9.12.2(2)(a) NP: 6.5.7.5(1)(a)-(c ),6.5.9.4.2

19




None


Real-time > ISO > Operating/Ancillary Reserves > LaaRsOG: NP: 6.5.7.5(1)(b),(c ),and(e)

20




None


Real-time > ISO > Ancillary Service Energy Deployment > System Regulation Deployment

OG: 9.12.2(1) NP: 8.2(2)(b)(ii) and 6.5.7.6.2.1

21


The metric is CPS1 The BA must maintain a minimum of 100% for 12 months per NERC BAL-001 Standards



Real-time > ISO > Ancillary Service Energy Deployment > Non-spin online measures

OG: NP: 6.5.7.6.2.3

22


None None None


Real-time > ISO > Ancillary Service Energy Deployment > Responsive requirements of units

OG: 9.13.4 NP: 6.5.7.6.2.2, 8.2(b)(vii)

23

Metric Criteria ReportA Balancing Authority performance is based on the pre-disturbance ACE and it's ACE at then end of the Disturbance Recovery Period (15 minutes after the disturbance).

Percent Recovery is calculated in the following way:- ACE(pre) = pre-disturbance ACE- ACE(max) = max. algebraic value of ACE measured within the 15 minutes following the disturbance- MW(loss) = MW size of disturbance- R = Percent Recovery For loss of generation: If ACE(pre) < 0 R = 100*(MW(loss) - max(0, ACE(pre) - ACE(max)))/MW(loss) Else R = 100*(MW(loss) - max(0, - ACE(max)))/MW(loss) This must be calculated for all disturbances greater than or equal to 80% of the magnitude of the BA's most severe single contingency loss

An average percent recovery will be calculated for all reportable disturbances in a quarter. This value must be greater than 100% per NERC BAL-002 Standards



Real-time > QSE > Operating/Ancillary Reserves > RegulationOG: NP: 8.1.1.3.1

24

Metric Criteria Report(a) Sum of each QSE'S Resources telemetered Reg-Up Responsibility minus QSE's total Reg-Up Responsibility

(b) Sum of each QSE'S Resources telemetered Reg-Down Responsibility minus QSE's total Reg-Down Responsibility

Recommended:

(a) Violation if < 0 for 10 or more minutes

(b) Violation if < 0 for 10 or more minutes

Qualifying exemptions may need to be further defined

QSE is notified by ERCOT through MIS when criteria is not met.

Critical for Nodal go-live. NOGRR/NPRR required to define compliance report/possible exemptions.

Real-time > QSE > Operating/Ancillary Reserves > Non-SpinOG: NP: 8.1.1.3.3

25

Metric Criteria ReportSum of each QSE'S Resources telemetered Non-Spin Responsibility minus QSE's total Non-Spin Responsibility

Recommended:

Violation if < 0 for 10 or more minutes




Real-time > QSE > Operating/Ancillary Reserves > Responsive ReservesOG: NP: 8.1.1.3.2

26

Metric Criteria ReportSum of each QSE'S Resources telemetered Responsive Responsibility minus QSE's total Responsive Responsibility

Recommended:





Real-time > QSE > Operating/Ancillary Reserves > LaaRsOG: NP: 8.1.1.3.2(2) and 8.1.1.3.3(2)

27

Metric Criteria ReportSum of each QSE'S Resources telemetered Non-Spin Responsibility minus QSE's total Non-Spin Responsibility

Sum of each QSE'S Resources telemetered Responsive Responsibility minus QSE's total Responsive Responsibility

Recommended:





Real-time > QSE > Ancillary Services Energy Deployment > Non-spin online measures (1/3)OG: 9.13.6 NP: 8.1.1.4.3 and 8.1(3)(m)

28

Metric1) Generation Resources with Output Schedules: Net Generation divided by Resource Base Point (adjusted based on deployment instruction)

2) Load Resources, including Controllable Load Resources: (a) Real-time power consumption minus Baseline capacity (5 minute average of real power consumption prior to deployment) all divided by the dispatch instruction. This is used for deployment performance.

(b) Real-time power consumption/Resource Non-spin obligation. Used for recall performance.

Recommend the following to replace the measures above:

1) For all Generation Resources and Controllable Load Resources providing NSRS, the GREDP calculation (described in row 28) would be used. Also, the NSRS Resource Schedules will compare to the NSRS Resource Responsibilities.

2) For Load Resources, excluding Controllable Load Resource: (a) Real-time power consumption minus Baseline capacity (5 minute average of real power consumption prior to deployment) all divided by the dispatch instruction. This is used for deployment performance.

(b) Real-time power consumption/Resource Non-spin obligation. Used for recall performance.

Critical for Nodal go-live. NOGRR/NPRR required.


29

Criteria1) Generation Resources with Output Schedules: Value calculated 30 minutes after the deployment instruction must be >=0.95 and <=1.50 and this must be maintained until recalled or Non-Spin obligation expires

2) Load Resources, including Controllable Load Resources: (a) Value calculated 30 minutes after the deployment instruction must be >=0.95 and <=1.50 and this must be maintained until recalled or Non-Spin obligation expires

(b) No more than 3 hours following a recall instruction, the calculated values must be >=0.95

Recommend the following to replace the measures above:1) For all Generation Resources providing NSRS:During 85% of all intervals which are after NSRS is deployed and before either NSRS is recalled or the NSRS obligation expires, one of following criteria must be met: (a) GREDP(%) <= 5% (b) GREDP(MW) <= 5 MW

NSRS capacity release must occur within 20 minutes of receiving a deployment and the difference between the sum of the QSE's Resource NSRS Responsibilities and the sum of the QSE's Resource NSRS Schedules must be equal to the QSE NSRS deployment. Off-line Generation Resources must also be online at their LSL within this 20 minute period.

2) For Controllable Load Resources providing NSRS:During 85% of all intervals which are 30 minutes after NSRS is deployed and before either NSRS is recalled or the NSRS obligation expires, one of following criteria must be met: (a) GREDP(%) <= 5% (b) GREDP(MW) <= 5 MW

NSRS capacity release must occur within 20 minutes of receiving a deployment and the difference between the sum of the QSE's Resource NSRS Responsibilities and the sum of the QSE's Resource NSRS Schedules must be equal to the QSE NSRS deployment.

2) For Load Resources, excluding Controllable Load Resource: (a) Value calculated 30 minutes after the deployment instruction must be >=0.95 and <=1.50 and this must be maintained until recalled or Non-Spin obligation expires

(b) No more than 3 hours following a recall instruction, the calculated values must be >=0.95



30

Report

ERCOT will post reports monthly describing Resource-specific performance for all Non-spin deployments which occurred during the previous month.


Real-time > QSE > Ancillary Services Energy Deployment > Responsive requirements of units (1/3)

OG: 9.13.4 NP: 8.1.1.4.2 and 8.1(3)(k)

31

Metric

1) Generation Resources with Output Schedules: Net Generation divided by Resource Base Point (adjusted based on deployment instruction)

2) Controllable Load Resources: (a) Real-time power consumption divided by desired load level. The desired load level is calculated as the Scheduled Power Consumption minus deployment. This is used for deployment performance.

(b) Real-time power consumption divided by Scheduled power consumption. Used for recall performance.

3) Load Resources, excluding Controllable Load Resources: (a) Real-time power consumption minus Baseline capacity (5 minute average of real power consumption prior to deployment) all divided by the dispatch instruction. This is used for deployment performance.

(b) Real-time power consumption/Resource RRS obligation. Used for recall performance.

ERCOT recommends the following to replace the measures above:

1) For all Generation Resources and Controllable Load Resources providing RRS, the GREDP calculation (described in row 28) would be used. Also, the RRS Resource Schedules will compare to the RRS Resource Responsibilities.

2) For Load Resources, excluding Controllable Load Resource: (a) Real-time power consumption minus Baseline capacity (5 minute average of real power consumption prior to deployment) all divided by the dispatch instruction. This is used for deployment performance.

(b) Real-time power consumption/Resource RRS obligation. Used for recall performance.



OG: 9.13.4 NP: 8.1.1.4.2 and 8.1(3)(k)

32

Criteria

1) Generation Resources with Output Schedules: (a) 10 minutes following a deployment instruction, the calculated value must be >=0.95 and <= 1.5 and this must be maintained until recalled or RRS obligation expires. (b) Within 10 minutes following a recall, the calculated value must be >=0.95 and <= 1.05 2) Controllable Load Resources:The following is currently written the protocols (a) 10 minutes following a deployment instruction, the calculated value must be >=0.95 and <= 1.5 and this must be maintained until recalled or RRS obligation expires. (b) Within 10 minutes following a recall, the calculated value must be >=0.95 and <= 1.05

The deployment performance should be changed to the following: (a) 10 minutes following a deployment instruction, the calculated value must be >=0.95 and <= 1.50 and this must be maintained until recalled or RRS obligation expires.

3) Load Resources, excluding Controllable Load Resources: (a) Value calculated 10 minutes after the deployment instruction must be >=0.95 and <=1.50 and this must be maintained until recalled or RRS obligation expires (b) No more than 3 hours following a recall instruction, the calculated values must be >=0.95

Recommend the following to replace the measures above:1) For all Generation Resources providing RRS:During 85% of all intervals which are after RRS is deployed and before either RRS is recalled or the RRS obligation expires, one of following criteria must be met: (a) GREDP(%) <= 5% (b) GREDP(MW) <= 5 MW

RRS capacity release must occur within 1 minute of receiving a deployment and the difference between the sum of the QSE's Resource RRS Responsibilities and the sum of the QSE's Resource RRS Schedules must be equal to the QSE RRS deployment.

2) For Controllable Load Resources providing RRS:During 85% of all intervals which are 10 minutes after RRS is deployed and before either RRS is recalled or the RRS obligation expires, one of following criteria must be met: (a) GREDP(%) <= 5% (b) GREDP(MW) <= 5 MW

RRS capacity release must occur within 1 minute of receiving a deployment and the difference between the sum of the QSE's Resource RRS Responsibilities and the sum of the QSE's Resource RRS Schedules must be equal to the QSE RRS deployment.

3) For Load Resources, excluding Controllable Load Resource: (a) Value calculated 10 minutes after the deployment instruction must be >=0.95 and <=1.50 and this must be maintained until recalled or RRS obligation expires (b) No more than 3 hours following a recall instruction, the calculated values must be >=0.95



OG: 9.13.4 NP: 8.1.1.4.2 and 8.1(3)(k)

33

Report

ERCOT will post reports monthly describing Resource-specific performance for all RRS deployments which occurred during the previous month.


Real-time > QSE > Telemetry StandardsOG: 9.3(c)(ii) NP: 8.1(3)(c)(i)

34


1) General Telemetry: Availability, which is measured based on end-to-end connectivity of the communications path and the passing of Real-Time data with good quality codes at the scheduled periodicity.

2) Critically Important Telemetry (Define in the Telemetry Standards): Availability, which is measured based on end-to-end connectivity of the communications path and the passing of Real-Time data with good quality codes at the scheduled periodicity.

3) ICCP Links: Availability. A link will be considered as available when at least eighty-five (85%) percent of the data defined on that link is successfully transferred to ERCOT with a valid or manual quality code.

1) General Telemetry: 98% of all telemetry provided by the QSE must be available at least 80% of the time during a quarter. 2) Critically Important Telemetry (Define in the Telemetry Standards): 95% of all telemetry provided by the QSE must be available at least 90% of the time during a quarter.

3) ICCP Links: Each QSE must achieve a monthly availability of 98%, excluding planned outages

Performance is broken up into three categories: General Telemetry, Critically Important Telemetry and ICCP links. These metrics and criteria must be found in the Telemetry Standards.


Real-time > QSE > Event Recovery > Governor Response (1/3)OG: 2.2.7, 2.2.8 NP: 8.5.2, 8.5.1.1 and 8.5.1.2

35

Metric

Governor droop as measured during system frequency events.

A measureable event is defined using the following method:(1) For the purposes of this Section, the “A Point” is the last stable frequency value before a frequency disturbance. ERCOT shall determine the A Point frequency for each event using the following standards. (a) For a decreasing frequency event with the last stable frequency value of 60.000 Hz or below, the actual frequency is used as the A Point. (b) For a decreasing frequency event with the last stable frequency value between 60.000 and 60.036 Hz, 60.000 Hz is used as the A Point. (c) For a decreasing frequency event with the last stable frequency value above 60.036 Hz, actual frequency is used as the A Point. (d) For an increasing frequency event with the last stable frequency value of 60.000 or above, the actual frequency is used as the A Point. (e) For an increasing frequency event with the last stable frequency between 59.964 and 60.000 Hz, 60.000 Hz will be used as the A Point. (f) For an increasing frequency event with the last stable frequency value of 59.964 or below, the actual frequency is used as the A Point. (2) For the purposes of this Section, the “C Point” is the lowest frequency value during the first five seconds of the event. ERCOT shall determine the C Point for each event.(3) For the purposes of this Section, the “B Point” is the “recovery” frequency value after the C Point. The B Point should occur after full governor response of the turbines has occurred, usually between ten and 30 seconds after the A Point, but not greater than 60 seconds after the A Point. ERCOT shall determine the B Point for each event.(4) For the purposes of this Section, a “Measurable Event” that will be evaluated for performance compliance is a sudden change in frequency that has both: (a) A frequency B Point between 59.700 Hz and 59.900 Hz or between 60.100 Hz and 60.300 Hz; and (b) A difference between the B Point and the A Point greater than or equal to +/- 0.100 Hz.



36

Criteria

All generators except wind and nuclear powered must respond to frequency disturbances with a governor droop of 5% or less unless limited by a High Sustained Limit (HSL) or other limits filed with ERCOT including duct burning on Combined-Cycle units.



37

Report

ERCOT shall make a regular report on selected system disturbances, documenting the response of individual QSEs, together with a summary. This report is reviewed by the PDCWG. The TRE shall communicate with the Market Participants that are not meeting the current performance requirements.


Real-time > QSE > Resource OutagesOG: 9.6 NP: 8.1(3)(q)

38


None None Yes


Real-time > QSE > COP > Day-AheadOG: 9.10(2),(3),(4),(6) NP: 8.1(3)(r ), 3.9.2, 3.16, 8.1.2

39


1) For each QSE for each month the number of Operating Hours in which the COP used for DRUC and HRUC did not meet any one of the following criteria: (a) The amount of RRS that a QSE can self arrange using Load Resources, excluding Controllable Load Resources, is limited to 50% of its RRS obligation or a reduced percentage if one is established by ERCOT (b) The total amount of RRS using Load Resources, excluding Controllable Load Resources procured by ERCOT is also limited to this percentage. The total amount includes what QSEs have sold to other Market Participants. (c) The sum of the Ancillary Service capacity designated in the COP for each hour, by service type is at least equal to the QSEs Responsibility for that service.

2) For each QSE for each month the number of Operating Hours in which RUC committed Resources failed to be online and released to SCED for deployment in the RUC-commitment hour. Hours during which the Resource is offline as a result of a forced outage are removed.

Recommended:3) For each QSE for each day the number of Operating Hours in which the Outage Scheduler information did not match the COP.

1) QSEs shall have no more than 3 hours during an Operating Day or 74 hours during a month during which the metric (a)-(c ) are not met.

2) QSEs shall have no more than 3 hours during an Operating Day or 74 hours during a month during which the metric is not met.

Recommended:1) QSEs shall have no more than 3 hours during an Operating Day or no more than 3 Operating Days a month in which at least 1 hour in which the (a)-(c) are not met

2) QSEs shall have no more than 3 hours during an Operating Day or no more than 3 Operating Days a month in which at least 1 hour in which the metric is not met

3) QSEs shall have no more than 2 hours during an Operating Day in which the metric is not met.

1) and 2) are reported monthly by ERCOT.

Recommended that 3) be reported daily.

Critical for Nodal go-live. Changes recommended can wait until after go-live.

Real-time > QSE > COP > Adjustment PeriodsOG: 9.10(1),(5),(6) NP: 8.1(3)(r ), 3.9.2, 3.16, 8.1.2

40


1) For each QSE for each month the number of Operating Hours in which the COP used for DRUC and HRUC did not meet any one of the following criteria: (a) The amount of RRS that a QSE can self arrange using Load Resources, excluding Controllable Load Resources, is limited to 50% of its RRS obligation or a reduced percentage if one is established by ERCOT (b) The total amount of RRS using Load Resources, excluding Controllable Load Resources procured by ERCOT is also limited to this percentage. The total amount includes what QSEs have sold to other Market Participants. (c) The sum of the Ancillary Service capacity designated in the COP for each hour, by service type is at least equal to the QSEs Responsibility for that service.

2) For each QSE for each month the number of Operating Hours in which RUC committed Resources failed to be online and released to SCED for deployment in the RUC-commitment hour. Hours during which the Resource is offline as a result of a forced outage are removed.

Recommended:3) For each QSE for each day the number of Operating Hours in which the Outage Scheduler information did not match the COP

1) QSEs shall have no more than 3 hours during an Operating Day or 74 hours during a month during which the metric (a)-(c ) are not met.

2) QSEs shall have no more than 3 hours during an Operating Day or 74 hours during a month during which the metric is not met.

Recommended:1) QSEs shall have no more than 3 hours during an Operating Day or no more than 3 Operating Days a month in which at least 1 hour in which the (a)-(c) are not met

2) QSEs shall have no more than 3 hours during an Operating Day or no more than 3 Operating Days a month in which at least 1 hour in which the metric is not met

3) QSEs shall have no more than 2 hours during an Operating Day in which the metric is not met.

1) and 2) are reported monthly by ERCOT.

Recommended that 3) be reported daily.

Critical for Nodal go-live. Changes recommended can wait until after go-live.

Real-time > QSE > Energy > Adherence to dispatch ordersOG: 9.4 NP: 8.1(3)(f)

41


For Verbal Dispatch Instruction, QSEs must adhere to all dispatch orders, unless deemed to be unsafe.

Did the QSE comply with the instruction: Yes or No

ERCOT will report any suspected non-compliance to the TRE.


Real-time > QSE > Energy > GREDP (1/3)OG: 9.4 NP: 8.1.1.4.1(2)-(5)

42

Metric

For Resources which are not DSRs, the following equation is used:GREDP (%) = ABS[((ATG – AEGR)/(ABP + ARI)) – 1.0]*100GREDP(MW) = ABS(ATG – AEGR – ABP - ARI) Where: -ATG = Average Telemetered Generation = the average telemetered generation of the Generation Resource for the SCED interval -ARI = Average Regulation Instruction = the amount of regulation that the Generation Resource should have produced based on the LFC deployment signals, calculated by LFC, during each SCED interval -AEGR = Average Estimated Governor Response = 10 * GRF * HSL * (average frequency deviation in Hz) for the SCED interval -Governor Response Factor (GRF) is a value that shall be provided to ERCOT by the Resource Entity usually between the values of: 0.014 and 0.033 (where the units for GRF * HSL are MW/0.10 Hz) -ABP = Average Base Point = (Base Point in the immediately previous SCED interval + Base Point from the current SCED interval)/2

This is calculated for each 5 minute interval.

A similar equation for calculating GREDP is also used for a QSEs Resources which are part of the it's DSR portfolio. The equation could not be written here can be found in 8.1.1.4.1(3)

GREDP will not be calculated if any of the following events has occurred: (a) The 20-minute period in which ERCOT has experienced a Forced Outage causing an ERCOT frequency deviation of greater than 0.05 Hz; (b) Settlement Intervals in which ERCOT has issued Emergency Base Points to the QSE; (c) The two hour period following the Forced Outage of any Resource within the QSE’s DSR Portfolio that has a Resource Status of ONDSR or ONDSRREG; and (d) Certain other periods of abnormal operations as determined by ERCOT in its sole discretion.

Critical for Nodal go-live. NOGRR/NPRR required to adopt criteria.


43

Criteria

Recommend the following 2 criteria:These criteria take into account analysis done using data from last summer's 2-hour LFC test. This criteria should apply to all Generation Resources and Controllable Load Resources. The GREDP calculations would need to be updated to include Controllable Load Resources.

85% of all intervals in a month during which GREDP is calculated and the Resource or DSR portfolio is released to SCED, one of following criteria must be met: (a) GREDP(%) <= 5% (b) GREDP(MW) <= 5 MW



44

Report

The reporting requirements will need to be adjusted slightly to capture performance based on the suggested criteria.


Real-time > QSE > Energy > Voltage Control > Maintain voltage set pointOG: 9.9, 2.7.4.1, 9.2 NP: 3.15.3, 8.1(3)(o), 6.5.5.1, 8.1(3)(b)

45

Metric Criteria Report1) Has the QSE submitted an AVR test report within the last 60 months

2) The percentage is calculated as: Time (AVR is on while providing Service) / (Total Time Providing Services) (100%).

3) Request made by TO or ERCOT

4) Reactive Testing - QSEs must provide the following information:(a) Unit name;(b) QSE;(c) Date; (d) Time; (e) Tested generation capability;(f) Reported time; and (g) Corrected Unit Reactive Limit (CURL) and Unit Reactive Limit (URL).

5) For Generation Resource required to provide VSS which is operating at less than the maximum reactive capability of the unit: Abs(Voltage at point of interconnection - voltage profile)/voltage profile

1) New test results must be submitted every 60 months.

2) AVR must be on and operating automatically at least 98% of the time in which the QSE is providing the Reactive Power supply from Generation Resources required to provide Voltage Support Service (VSS).

3) Failed to provide VSS up to the required capability of the unit upon request.

4) Reactive Testing - The information must be provided when reactive testing indicates a changed in unit capability and at a minimum of once every 2 years.

5) Must always <=2%

1) ERCOT is required to produce a report stating who has is not meeting the requirement, but it is not stated how often the report is produced (Part of NOGRR25).

ERCOT recommends this be reported monthly.

2) No report, just being monitored by ERCOT

3) Non-compliance can be reported by ERCOT to the TRE

4) Reactive Testing - ERCOT shall produce reports annually which describe when the last reactive capability test took place, what the MW and MVAR outputs were during the test period, how long the output was held, and a minimum of four MW/MVAR pairs describing the CURL of the unit.

5) Non-compliance can be reported by ERCOT to the TRE

Critical for Nodal go-live. NOGRR/NPRR required to define report.

Real-time > TSP > Transmission OutagesOG: 9.11.3 NP: 8.3(1)(c )

46


None None Yes


Real-time > TSP > Telemetry StandardsOG: 9.11.2 NP: 8.3(1)(b)

47


1) General Telemetry: Availability, which is measured based on end-to-end connectivity of the communications path and the passing of Real-Time data with good quality codes at the scheduled periodicity.

2) Critically Important Telemetry (Define in the Telemetry Standards): Availability, which is measured based on end-to-end connectivity of the communications path and the passing of Real-Time data with good quality codes at the scheduled periodicity.

3) ICCP Links: Availability. A link will be considered as available when at least eighty-five (85%) percent of the data defined on that link is successfully transferred to ERCOT with a valid or manual quality code.

1) General Telemetry: 98% of all telemetry provided by the TSP must be available at least 80% of the time during a quarter. 2) Critically Important Telemetry (Define in the Telemetry Standards): 95% of all telemetry provided by the TSP must be available at least 90% of the time during a quarter.

3) ICCP Links: Each TSP must achieve a monthly availability of 98%, excluding planned outages

ERCOT shall produce monthly reports. For 1) and 2), this report will shows the results for the previous quarter. For 3), the report will show the results for the previous month.

Critical for Nodal go-live. No action required.

Real-time > TSP > Voltage and Switching of Transmission Elements > Following TOP directives

OG: 9.11.5, 2.7.4.1 NP: 3.15.2

48


ERCOT shall produce monthly reports describing TSP valid Dispatch Instruction performance.

Not needed for oversight at go-live. NOGRR25 may need more detail to explain the monthly report.

Planning > ISO > Day-Ahead Market > DRUCOG: 9.12.1(3)(a)(i),9.12.2(3)(a),9.12.4(c) NP: 8.2(2)(l), 8.2(2)(d)(iii), 8.2(2)(b)(iv), 5.3

49


None None Yes


Planning > ISO > Day-Ahead Market > HRUCOG: 9.12.1(3)(a)(i),9.12.2(3)(a),9.12.4(c) NP: 8.2(2)(l ),8.2(2)(d)(ii), 5.3, 8.2(2)(b)(iv)

50


None None Yes


Planning > ISO > Forecast > Wind/RenewablesOG: NP: 3.13, 4.2.2

51


None None None


Planning > ISO > Forecast > LoadOG: 9.12.3 NP: 8.2(2)(c)

52


None None None


Planning > ISO > Outage CoordinationOG: 9.12.1(2) NP: 8.2(2)(a)(ii), 8.2(2)(b)(i), 3.1.6.6, 3.1.7.1

53


(b) ERCOT shall post on the Market Information System (MIS) Secure Area its performance in processing TSP Outage requests.(c) ERCOT shall post on the MIS Secure Area its performance in sending TSPs rejection Notices. The report will include specific concerns that caused the rejection.

Further analysis for clearly defining pass/fail criteria and the inclusion of Resource Outage metrics.

For b and c), ERCOT must adhere to the following deadlines:- If time between request and outage is 3 days, ERCOT must approve or reject by 1800, 2 days before the outage- If time between request and outage is between 3 and 8 days, ERCOT must approve or reject by 1800, 3 days before the outage- If time between request and outage is between 9 and 45 days, ERCOT must approve or reject by 1800, 4 days before the outage- If time between request and outage is between 46 and 90 days, ERCOT must approve or reject by 1800, 40 days before the outage- If time between request and outage is more than 90 days, ERCOT must approve or reject by 1800, 75 days before the outage

Similar deadlines for Resource outages can be found in Nodal Protocol 3.1.6.6 and 3.1.7.1

For a) it states the metrics are produced for each month. It would make sense that all of these are produced monthly, however it is not currently stated in the Nodal Protocols or Operating Guides

Not needed for oversight at go-live. Consider requiring monthly reporting.

Planning > ISO > Network Operations Model Change Request (NOMCR)OG: 9.12.5 NP: 3.10.1

54


The following will be reported:(a) total number of NOMCRs submitted(b) total number of NOMCRs approved(c ) total number of NOMCRs rejected(d) total number of NOMCRs withdrawn(e) number of interim updated and reasons provided by Market Participants

ERCOT performance will be based and their required action as compared to when the information was submitted to them.

Performance criteria is given in a table in Nodal Protocol 3.10.1(3). The table would not fit here.

Shall be reported monthly


Planning > ISO > 24/7 Operations and Backup PlanOG: 9.12.6(1)(b), 3.9(4)(d), 3.2.1(30(d) NP: 8.2(2)(h), 8.1(3)(l)

55


The status of ERCOT's backup plan and status of backup training for QSEs and TSPs

Is there a backup procedure on file and has backup training for QSEs/TSPs been performed: Yes or No

Reported by the end of the first quarter of each year

Not needed for oversight at go-live. Clarify in OG that training is responsibility of QSEs/TSPs.

Planning > ISO > Black Start > PlansOG: 9.12.7 NP: 8.2(2)(i)

56


Was a plan developed and when was it posted

No deadline date is currently given (MPs are required to submit by the end of the first quarter so it can not be required any earlier than that)

Reported to annually to the MIS Secure Area

Not needed for oversight at go-live. Consider establishing deadline.

Planning > ISO > Black Start > TestingOG: NP: 8.1.1.2.1.5

57


None None None


Planning > ISO > Black Start > TrainingOG: 4.6.4(1)(c) NP: 3.14.2(6)

58


If the training was done and when it was done.

No deadline date for the training is currently given .

No reporting to be done.

Not needed for oversight at go-live. Consider establishing deadline.

Planning > QSE > Generator Equipment RatingOG: NP: 3.10.6, 3.10.7.2

59


None None None


Planning > QSE > Unit Capability and Reactive Testing (Seasonal, etc.)OG: 9.1-9.2 NP: 8.1(3)(a)-(b)

60


Unit Capability - For any Generation Resource (> 10 MW) that intends to be operating during a season, the QSE must provide ERCOT the seasonal HSL

Reactive Testing - QSEs must provide the following information:(a) Unit name;(b) QSE;(c) Date; (d) Time; (e) Tested generation capability;(f) Reported time; and (g) Corrected Unit Reactive Limit (CURL) and Unit Reactive Limit (URL).

Unit Capability - The seasonal HSL must be provided within the first 15 days of the season

Reactive Testing - The information must be provided when reactive testing indicates a changed in unit capability and at a minimum of once every 2 years.

Unit Capability - ERCOT shall produce annual reports summarizing the submittals by QSEs

Reactive Testing - ERCOT shall produce reports annually which describe when the last reactive capability test took place, what the MW and MVAR outputs were during the test period, how long the output was held, and a minimum of four MW/MVAR pairs describing the CURL of the unit.


Planning > QSE > Network Operations Model Change Request (NOMCR) submitted by ERCOT

OG: 9.5 NP: 3.10.1

61


Unit Capability - For any Generation Resource (> 10 MW) that intends to be operating during a season, the QSE must provide ERCOT the seasonal HSL

Reactive Testing - QSEs must provide the following information:(a) Unit name;(b) QSE;(c) Date; (d) Time; (e) Tested generation capability;(f) Reported time; and (g) Corrected Unit Reactive Limit (CURL) and Unit Reactive Limit (URL).

Unit Capability - The seasonal HSL must be provided within the first 15 days of the season

Reactive Testing - The information must be provided when reactive testing indicates a changed in unit capability and at a minimum of once every 2 years.

Unit Capability - ERCOT shall produce annual reports summarizing the submittals by QSEs

Reactive Testing - ERCOT shall produce reports annually which describe when the last reactive capability test took place, what the MW and MVAR outputs were during the test period, how long the output was held, and a minimum of four MW/MVAR pairs describing the CURL of the unit.


Planning > QSE > Generation Resource SchedulingOG: 9.6 NP: 8.1(3)(q)

62


None None Yes


Planning > QSE > 24/7 Operations and Backup PlanOG: 9.12.6, 9.8, 9.7 NP: 8.1(3)(l),(n)

63


24/7 Operations - QSEs shall maintain a 24x7 scheduling center with qualified personnel with the authority to commit and bind the QSE

Backup Plan - Results from backup control testing must be provided to ERCOT. QSEs must also submit backup plan procedures to ERCOT. These plans should include a staffing plan.

24/7 Operations - Was this maintained: Yes or No

Backup Plan - The backup control testing must be conducted at least annually. Does ERCOT have a backup plan on file: Yes or No

24/7 Operations - ERCOT shall report to the TRE instances of non-performance following ERCOT's investigation

Backup Plan - ERCOT shall produce a report identifying the date of backup control testing and the success or failure of that test. This report is ad hoc. ERCOT will also report by the end of the first quarter of each year all QSEs which have met the criteria and the date on which the back-up plan was last updated


Planning > QSE > Black Start > PlansOG: 9.13.3 NP: 8.1(3)(h)

64


QSEs participating in Black Start Service shall provide an updated black start procedure to ERCOT.

This procedure must be submitted by the end of the first quarter of the year and any time the procedure is changed

ERCOT shall produce annual reports with if and when a black start procedure was received by ERCOT.


Planning > QSE > Black Start > TestingOG: NP: 8.1.1.2.1.5

65


None None None


Planning > TSP > Transmission Equipment RatingsOG: 9.11.1 NP: 8.3(1)(a)

66


TSPs shall submit their equipment rating methodology to ERCOT or provide notice that the rating methodology has not changed.

Must be done by the end of the first quarter of each year.

ERCOT shall prepare an annual report summarizing these methodologies and submit it to the TRE.


Planning > TSP > Network Operations Model Change Request (NOMCR)OG: 9.11.4 NP: 8.3(1)(d), 3.10.1

67


None None Yes


Planning > TSP > Transmission Outage SchedulingOG: 9.11.3 NP: 8.3(1)(c )

68


None None Yes


Planning > TSP > 24/7 Operations and Backup PlanOG: 9.12.6 NP: 8.2(2)(h)

69


TSPs must have an approved back-up procedure on file with ERCOT. The procedure should also include the date on which it was last updated. These plans should include a staffing plan.

Is there a back-up procedure on file: Yes or No.

ERCOT shall report by the end of the first quarter of each year all TSPs which have met the criteria and the date on which the back-up plan was last updated


Date post:	13-Jan-2016
Category:	Documents
Upload:	oswin-cunningham
View:	216 times
Download:	0 times