Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 1 of 12

Table of Contents

PURPOSE ....................................................................................................................... 1

1. RESPONSIBILITIES ............................................................................................................ 1 2. SCOPE/APPLICABILITY ...................................................................................................... 2

2.1. Background ............................................................................................................ 2 2.2. Scope/ Applicability ................................................................................................. 2

3. PROCEDURE DETAIL ......................................................................................................... 2 3.1. Running the Real-Time Market ............................................................................... 2 3.1.1. Real-Time Load Forecast .................................................................................... 2 3.1.2. Real-Time Ancillary Service Requirement ........................................................... 3 3.1.3. Real-Time Pre-Dispatch (RTPD) ......................................................................... 5 3.1.4. Real-Time Dispatch ............................................................................................ 6 3.1.5. Real-Time Contingency Dispatch ........................................................................ 6 3.1.6. Real-Time Manual Dispatch ................................................................................ 7 3.2. Real-Time Timelines ............................................................................................... 8

4. SUPPORTING INFORMATION .............................................................................................10 Operationally Affected Parties ...........................................................................................10 References ........................................................................................................................10 Definitions .........................................................................................................................10 Version History ..................................................................................................................11

5. PERIODIC REVIEW PROCEDURE .......................................................................................11 Review Criteria & Incorporation of Changes ......................................................................11 Frequency .........................................................................................................................11

APPENDIX .................................................................................................................... 12

Purpose

Provides guidelines for running the Real-Time Market (RTM) process and for procuring Ancillary Services (AS) in the RTM.

1. Responsibilities

ISO Generation Desk

Reviews and allows instructions from RTM to be sent to Market Participants via ADS

Logs all compliance issues

Ensures RTM runs at the designated intervals

Dispatches resources with Exceptional Dispatch as requested by the ISO Shift Manager Desk

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 2 of 12

Conform transmission constraints as required for reliability purposes

Sends market messages as required

Utilizes RTM/Exceptional Dispatch to modify resources in RTM

Adjusts RTM (as needed) for proper Dispatching

Scheduling Coordinator (SC)

Submits Energy and Ancillary Service Schedules and Bids for the Real-Time Markets.

2. Scope/Applicability 2.1. Background

Describes Real-Time Market activities.

2.2. Scope/ Applicability

This procedure applies to Real-Time Market activities.

3. Procedure Detail

3.1. Running the Real-Time Market 3.1.1. Real-Time Load Forecast

Take the following actions to forecast Load:

ISO Generation Desk

1. Access the Real-Time Load Forecasting Tool from System Operations Launch Pad.

2. Update, adjust, and publish the RT Load Forecast to RTN.

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 3 of 12

3.1.2. Real-Time Ancillary Service Requirement

RTPD Description

The AS requirements for the HASP and RTUC processes are based on NERC/WECC requirements.

RT AS is procured on a 15-minute basis, as needed, from resources certified to provide AS. All AS procured in RT is Contingency only.

In the event sufficient AS cannot be procured through the ISO Real-time markets, RT Dispatchers may procure additional AS, including from Reliability Must-Run (RMR) Units, to meet NERC/WECC requirements. The ISO will replace such AS with market procured AS as soon as practicable.

Note: The first consideration in determining which resource to assign AS should be based upon the resource’s ability to deliver the assigned AS. There is no requirement to select an RMR resource prior to a market resource. See ISO Desktop Procedure GEN-029 Manual AS Assignment

Take the following actions to review/adjust AS requirements in RTPD:

Note: If an RMR resource is selected, a written confirmation of the RMR AS dispatch must

be sent to the SC within 24 hours of the dispatch.

ISO Generation Desk

1. If the ISO makes a change after DAM but prior to the close of HASP of a min or max,

Issue a Market Notice as soon as reasonably practicable.

Note: After the close of HASP, the AS limits used in HASP are published in OASIS.

2. Open the ASRS screen in RTN.

Review calculated requirements.

Adjust market provided reserves as required for reliability.

Update new requirements to RTN (see ISO Desktop Procedure GEN-007 Ancillary Service Requirements Setter).

3. Determine whether any forecasted transmission and/or generation constraints exist:

If no transmission and/or generation constraints exist, o Go to Section 3.1.3.

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 4 of 12

ISO Generation Desk

If there are transmission and/or generation constraints, o Identify the applicable unit(s) associated with the constraint(s) (i.e.

units not addressed by the use of min’s and max’s of existing AS sub-regions).

o Block AS Bids as necessary. o Log the event.

Note: This historical record of AS blocking/buy back is used to assist in determining whether new AS sub-regions need to be created.

Note: Other reasons for blocking AS include Resource Testing and communications outages.

4. If additional reserves are necessary and all market mechanisms have been utilized,

Ask the ISO Shift Manager Desk whether to issue Dispatch instructions to the Scheduling Coordinators (SCs) for any AS certified Units.

5. If AS bids are skipped to maintain the WECC reserve requirement,

Notify Market Participants. 6. If insufficient AS have been procured,

Refer to ISO Operating Procedure 4420 System Emergency.

Log any deficiencies. 7. Inform the ISO Shift Manager Desk of any deviations from this procedure and

prepare a written report that provides the following information:

The procedure from which the deviation occurred.

A description of the deviation.

The duration of the deviation.

A detailed explanation of the reason for the deviation.

Any system reliability concern that led to the deviation. 8. Determine if minimum and/or maximum AS procurement limits are necessary for

each or any AS Region.

Consider the following: o Path Contingency de-ratings. o Path OTCs. o Most Severe Single Contingency (on-line Generating Unit or in-

service transmission). See Section 3.2, ISO Operating Procedure 2230 Most Severe Single Contingency (MSSC) Designation for a list of current MSSCs)

o Forecasted path flows o Other anticipated local operating conditions for Load and/or

Generation pocket AS Regions

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 5 of 12

ISO Generation Desk

9. If an Outage to a major transmission line results in Supply being curtailed into the Balancing Authority area and the Outage on the transmission line is a credible single Contingency,

Consider the transmission event a single largest Contingency for the purposes of determining Operating Reserves.

3.1.3. Real-Time Pre-Dispatch (RTPD)

Take the following actions for RTPD:

Scheduling Coordinator (SC)

1. Submit HASP and RTM Bids 75 minutes before the Operating Hour through SIBR.

ISO Generation Desk

1. Ensure adequate resources are available to meet all system reliability requirements.

2. If additional area resources are required:

Consider conforming impacted element per ISO Operating Procedure 2220 Transmission Conforming.

Consider adjusting and publishing to RTN a revised RT Load Forecast.

Consider committing additional units in RTN using Exceptional Dispatch per ISO Operating Procedure 2330 Real-Time Exceptional Dispatch.

3. Review HASP results, including Intertie Dispatches.

Modify or block results as necessary to meet reliability requirements. 4. If HASP robustness has occurred,

Adjust the Interties as needed, and

Request RTMO to manually publish the Interties and commitment.

Note: The HASP Market results are published automatically to the Customer Market Results Interface (CMRI) and ADS to notify Market Participants of their commitments and advisory status.

Note: Short Term Unit Commitment (STUC) will run automatically at T-52.5 minutes.

5. Determine if STUC has run properly and output is feasible.

If results are acceptable, take no action.

If results are not acceptable, determine whether results need to be modified.

o Adjust as necessary to meet reliability requirements.

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 6 of 12

ISO Generation Desk

6. Determine if additional Dispatch Instructions are needed based on the CFCD and the STUC Dispatches.

Communicate any additional Dispatch Instructions through Exceptional Dispatch instructions.

Refer to ISO Operating Procedure 2330 Real-Time Exceptional Dispatch. 7. Repeat Steps 7 and 8 for the remaining RTPD runs.

3.1.4. Real-Time Dispatch

Take the following actions for Real-Time Dispatch (RTD):

ISO Generation Desk

1. Adjust the 5 minute Real-Time Load Forecast as necessary to ensure reliability requirements are met.

2. Review the RTD results.

Adjust results as necessary to meet reliability requirements.

3. After issuing a 5 minute Dispatch,

Verify the Dispatch transferred to ADS, and

Monitor the Market Participants’ response to ADS instructions to ensure reliability requirements are met.

o If ADS is not functioning properly, refer to ISO Operating Procedure 5410 Communication/Applications Loss/Failure

o If the State Estimator (SE) is not functioning properly, Evaluate the need to request RTMO to switch Dispatch

Initialization Source to EMS. o If RTM is not functioning properly,

Dispatch resources as required via ADS or manually through an Exceptional Dispatch.

Refer to ISO Operating Procedure 2330 Real-Time Exceptional Dispatch.

3.1.5. Real-Time Contingency Dispatch

Take the following actions to address Contingencies in RT:

ISO Generation Desk

Note: The Disturbance Recovery Period is 15 minutes after the start of a Reportable Disturbance.

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 7 of 12

ISO Generation Desk

Note: The Contingency Reserve Restoration Period is 60 minutes.

Note: The Real-Time Contingency Dispatch (RTCD) can be activated at any time to address Contingencies by Dispatching contingent Operating Reserves.

1. Manually execute RTCD.

Refer to ISO Desktop procedure GEN-015 Real-Time Contingency Dispatch.

2. Consider requesting RTMO to check “Run RTD Power Flow” option in market software prior to initiating the Contingency Dispatch.

3. Determine whether requirements are met.

4. Review the Dispatches and adjust as necessary.

If Emergency Operations conditions exist such as reserve shortages, Load Shedding, Black Start restoration, etc.,

o Refer to ISO Operating Procedure 4420 System Emergency. o Determine emergency requirements.

5. Issue the RTCD instructions to the Market Participants. 6. If the system is recovered from the Contingency situation,

Return the Dispatched Contingency reserves back to Contingency reserves in a manner that does not cause frequency or Area Control Error (ACE) excursions.

3.1.6. Real-Time Manual Dispatch

Take the following actions whenever the RTD fails to converge because of bad data, network model issues, or optimization engine failure:

ISO Generation Desk

1. Run Real-Time Manual Dispatch. 2. If RTD Requirements are not met,

Adjust the 5-minute forecast while in RTMD to get the desired quantity. 3. If RTMD Dispatch instructions do not produce the desired results,

Issue Exceptional Dispatch instructions.

Refer to ISO Operating Procedure 2330 Real-Time Exceptional Dispatch

If reasons for Exceptional Dispatch no longer exist, o Issue RTMD Dispatch instructions only, or

Refer to ISO Operating Procedure 4420 System Emergency

When a bid is removed to resolve Market Disruption, o Refer to ISO Operating Procedure 2710 Market Disruption - RTM

Failure and Suspension.

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 8 of 12

3.2. Real-Time Timelines

The following diagrams attached below in the image section describe the HASP/STUC/RTPD and RTED timelines:

RTPD Timeline Figure 1

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 9 of 12

RTED Timeline Figure 2

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 10 of 12

4. Supporting Information

Operationally Affected Parties

Shared with the Public.

References

Resources studied in the development of this procedure and that may have an effect upon some steps taken herein include but are not limited to:

CAISO Tariff

ISO Operating/Desktop Procedures

GEN-007 Ancillary Service Requirements Setter

GEN-015 Real-Time Contingency Dispatch

NERC Requirements BAL-002-1 R4.2

WECC Criterion

Other References

Definitions

Unless the context otherwise indicates, any word or expression defined in the Master Definitions Supplement to the CAISO Tariff shall have that meaning when capitalized in this Operating Procedure. The following additional terms are capitalized in this Operating Procedure when used as defined below:

AS Ancillary Services

Robustness HASP Robustness occurs when HASP is given more time to run than normal (it actually steals time from STUC if there is time available)

RTD Real-Time Dispatch

RTCD Real-Time Contingency Dispatch

RTMD Real-Time Manual Dispatch

RTPD Real-Time Pre-Dispatch

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 11 of 12

Version History

Version Change Date

10.3 Section 3.1.3: Updated CMRI reference. 12/17/2014

10.4 Removed references to MOSES and SLIC. Page 3: Updated RTPD Description table. Page 6: Added verbiage to request RTMO to manually publish HASP robustness results. Page 8: Changed role from Generation Dispatcher to RTMO when switching to SE, removed power flow in EMS reference (it no longer exists) and changed verbiage to request RTMO to run power flow. Page 10: Updated RTPD Timeline. Section 3.1.2: Replaced RTPD Description table per Legal.

10/01/2015

10.6 Converted procedure from SharePoint Word to Centric. 3/09/2016

10.7 Section 3.1.6, step 1. Changed Merit Order to Manual to align with the Tariff. Updated section 3.1.3 to include language about bid removal and proper notification of the affected scheduling coordinator; Section 3.1.6 RT Manual Dispatch. Changed the role names used in this procedure to their new role names.

1/27/2017

11.0 Periodic Review: Section 3.1: Updated RT to Real-Time for all sub-section headers. Section 3.1.2: Replaced A/S with AS, added Note and updated existing Note. Section 3.1.4, #3 & Reference Section: Removed reference to Desktop Procedure GEN-001, as it retired on 4/05/18. Minor formatting and grammar updates. Removed version history prior to 5-years.

2/29/2020

5. Periodic Review Procedure

Review Criteria & Incorporation of Changes

There are no specific criteria for reviewing or changing this document, follow instructions in ISO Operating Procedure 5510.

Frequency Every 3 Years

Operating Procedure

Procedure No. 2210

Version No. 11.0

Effective Date 2/29/2020

Real-Time Market Activities Distribution Restriction:

None

This document is controlled when viewed electronically. When downloaded or printed, this document becomes UNCONTROLLED.

Page 12 of 12

Appendix

2210Z Effectiveness Factors - All 2210D Ancillary Service Blocking and Disqualification