Market and Performance Market Simulation Teleconference Call

Transcription

1 Market and Performance Market Simulation Teleconference Call MAP Market Simulation Teleconference Call November 8, 2010 Dial-In: Domestic (800) Dial-In: International (612) Web-meeting: Web Meeting #: Access Code:

2 MAP Market Simulation Agenda Environment Planning Calendar Convergence Bidding Update Market Simulation Schedule Updates Next Steps MSG Update SCP II Update Slide 2

3 Environment Planning Calendar Slide 3

4 Convergence Bidding (CB) CB Update Slide 4

5 Market Simulation Schedule Updates CB Market Simulation No Structured Scenarios this week SIBR-Lite is available for continued SIBR rules testing The MAP Stage environment is being updated to support Convergence Bidding Market Simulation beginning 11/15/10. There may be unusual or unexpected information in the system while the ISO is testing in the environment. Slide 5

6 Market Simulation Schedule Updates CB Market Simulation Slide 6

7 ISO Support CB Market Simulation Support Convergence Bidding Market Simulation Support Hours: Monday to Friday, 8 AM to 6 PM (PST) Phone: (916) ISO Help Desk: (916) (connectivity or end points) Preferred interface for communicating issues or questions is CIDI Please select the Market Simulation environment dropdown and include the words CB Market Simulation in the subject line Slide 7

8 Multi-Stage Generation (MSG) MSG Update Slide 8

9 Multi-Stage Generation Participant Testing and Important Go-Live Dates Full MSG market simulation MAP Stage environment unavailable most of 11/5 and through weekend. MAP Stage environment will re-open today (11/8). STAGE Environment activities STAGE not currently available. STAGE will open for participant testing this week. November 15 th go-live MSG Resources are active in STAGE as of 11/8. Market participates can Opt Out their MSG resources (remain as Forbidden Operating Regions) through November 10 th at 10:00am. A final go / no-go decision will be made on November 10 Slide 9

10 MSG Resource Day Ahead Bidding on 11/15 for 11/16 Operating Date High-Level November 15 th MSG Resource Activation Plan: Monday, 11/15/2010 by 10:00am: Day Ahead Bids for MSG Resources for 11/16/2010 Operating Date SIBR does not have capability to look farther ahead than 24 hours for a new resource. Participants will submit their Day Ahead bids by 10:00am on Monday, 11/15/2010. Tuesday, 11/15/2010: Starting at Hour Beginning 00, MSG Resources are active in Real- Time. Slide 10

11 MSG Operational Contingencies 1. Ability to opt out as a MSG resource by November 10, 10:00 AM 2. Allow a temporary expedited process for reversion from MSG to FOR through Master File refresh process. OD 1 Request opt out back to FOR OD 2 Master File refresh at Midnight between OD 2 and OD 3 OD 3 FOR bid in DA for OD 4 OD 4 Full FOR treatment in DA and RT 3. Use other bidding and outages strategies to override modeling impacts Self-scheduling capability Outage management 4. Direct dialog with ISO Operations Pre go-live briefing meeting Ability to use exceptional dispatch if necessary Slide 11

12 MSG Resource Type Transition: General Comments Resources can only have one resource type during a trading day this requires specific measures for handling the transitions from FOR to MSG & MSG to FOR These measures are only necessary for the real-time market as its look-ahead period straddles over two trading days; these do not apply for the IFM given that the time horizon starts and ends for a given trading day The rules specified below apply for the transition of resources to their MSG status on November 15, 2010 and are also intended to apply for transitions afterwards. Slide 12

13 MSG Resource Type Transition: Planned Outages for the resource Resources transitioning from FOR to MSG For any planned outages/de-rates/re-rates across the midnight hour of the date on which the conversion is to take effect, Scheduling Coordinators should continue to use SLIC for reporting their outages within 72 hours prior to the midnight hour of conversion as follows: 1. Shorten or redefine the SLIC ticket ending at midnight based on the prior resource definition, i.e., the FOR definition; 2. Enter a new SLIC ticket starting the midnight hour to reflect the outages for the new resource definition, i.e., the configuration based definitions for the MSG resource. 3. For the planned outages/de-rates/re-rates into the future beyond the transitioning period, the SLIC tickets will need to be re-defined based on the new MSG configuration definitions. The ISO will retain the priority of previously submitted tickets in the approval process. Slide 13

14 Transitioning from FOR to MSG Status Slide 14

15 FOR-to-MSG Resource Type Transition: Day-Ahead Initial Condition IFM Applications Determining Initial Condition for Midnight of Nov16 The day-ahead market will determine the initial configuration that can completely contain the energy schedule of HE24 of Nov15 by 1pm Nov 14 (within Pmin and Pmax) 1. If only one configuration exists in this set, that configuration becomes the initial configuration 2. If more than one configuration fits the criteria, the configuration with the lowest Pmin will become the initial configuration If there is confusion, contact the ISO operators for information and to validate initial configurations of affected resources. Before Transition Nov 15 (Last) After Transition Nov 16 (New) Slide 15

16 FOR-to-MSG Resource Type Transition: Market Participants Actions In the Day-Ahead Submit bids (IFM) For the prior day, no particular bidding is required. (IFM) For HE1 for the New day, self schedule only the initial configuration using the MSG definition with the same energy schedule MW as the HE24 on prior day (IFM) For HE2 for the New day, self schedule only the initial configuration using the MSG definition. MW at HE2 can be different from MW at HE1 Schedule Outages For resource adequacy (RA) resources (using SLIC Normal Card to avoid transition across midnight) Since SIBR will create energy bids and ancillary service bids for those RA resources even if only self schedules are provided, a SLIC normal card should be used to control the transition across midnight. For HE1 and HE2 of New day, submit SLIC normal card to disable all other configurations except the initial configuration. This can be done any time between 1pm of Nov14 and 10am of Nov15. Before Transition Nov 15 (Last) After Transition Nov 16 (New) Slide 16

17 FOR-to-MSG Resource Type Transition: Real-Time Important Actions for Participants Self-schedule in the real-time at the day-ahead schedule MW For HE23 & HE24 of Last Day For HE01 & HE02 of New Day -- Although not required, it is recommended to have HE24 and HE1 self scheduled at the same energy MW in case that day-ahead schedules are not equal for those two hours. All Day-Ahead AS awards should be self provided Before Transition Nov 15 (Last) After Transition Nov 16 (New) Slide 17

18 FOR-to-MSG Resource Type Transition: CAISO IFM/RTM IFM/RTM Applications Internal Actions RTPD will internally shutdown the FOR resource at midnight and startup the MSG resource at midnight. No startup or shutdown instructions will be issued. Energy schedules will be protected. RTD solution will not be affected as the plant level DOP/DOTs that will be issued are continuous due to the combination of self-schedules and SLIC normal card outages ISO will temporarily disable startup notification time & startup ramp time for midnight to allow resources being committed immediately (RTPD will startup/shutdown the unit internally) ISO will block the incorrect RTPD startup/shutdown instructions that would otherwise be sent through ADS ISO will block zero DOP/DOTs that would otherwise be sent through ADS Before Transition Nov 15 (Last) After Transition Nov 16 (New) Slide 18

19 Transitioning from MSG to FOR Status Slide 19

20 Day-Ahead Initial Condition IFM Applications Determining Initial Condition HE24 schedule MW from the Last day determines initial condition. The configuration ID in CMRI for HE24 already tells the initial configuration that market application is assumed on at midnight. Before Transition (Last) After Transition (New) Slide 20

21 Day-Ahead Important Actions for Participants Submit bids (IFM) For the prior day, no particular bidding needs to be different. For the DA market run for the New day, submit bids for the new resource type (IFM) For HE1 for the New day, self schedule with the same energy schedule MW as the HE24 on prior day (IFM) For HE2 for the New day, self schedule. MW can be different from HE1 as long as it is ramp capable. Before Transition (Last) After Transition (New) Slide 21

22 Real-Time Important Actions for Participants Self-schedule in the Real-Time at the Day-Ahead schedule MW For HE23 & HE24 of Last Day For HE01 & HE02 of New Day -- Although not required, it is recommended to have HE24 and HE1 self scheduled at the same energy MW in case that day-ahead schedules are not equal for those two hours. All Day-Ahead AS awards should be self provided Before Transition (Last) After Transition (New) Slide 22

23 Standard Capacity II (SCPII) SCPII Update Slide 23

24 SCP II Market Simulation Update Connectivity Testing Connectivity Testing has been extended to allow for incremental testing of the new RAAM APIs, pending MAP Stage availability Market Simulation Plan Updated for Connectivity Details Contains API end point details and URL (Section 3.4) Ensure appropriate portals are used: MAP Stage = Stage = CB structured and unstructured testing this week please do not submit any data to SIBR, SLIC or OMAR in support of SCP II testing. Slide 24

25 SCP II Market Simulation Update Structured Scenario Testing: Results Scenario Group Scenario Description Pass/ Fail USUB Unit Substitutions USUB 009* : Test the ability to request Unit Substitution without a reported outage (this will occur for units less than 10MW who only submit outages at month s end) USUB 010* : Test Real Time Unit Substitution for Prequalified Local Resource. USUB 011* : Test Day Ahead Unit Substitution for a local unit wanting to substitute two units to meet the obligation of one unit USUB 017* : Test scenario where 3rd party Day Ahead Unit Substitution exists USUB 019* : Test scenario where 3rd party rejects Day Ahead unit substitution USUB 022 : Test scenario where RAAM shall process unit substitutions for existing SCP RA resources with no change resulting from the addition of HQC resources (non- HQC resource substituted for non-hqc resource) USUB 023a : Test the application of existing unit substitution rules when substituting an HQC unit for a non-grandfathered, non-hqc resource USUB 023b : Test the application of existing unit substitution rules when substituting a non-hqc resource for a non-grandfathered HQC resource USUB 023c : Test the application of existing unit substitution rules when substituting a non-grandfathered HQC resource for a non-grandfathered HQC resource USUB 024 : Test the ability to enter the total MW amount of RA capacity needed to cover a resource on outage 11/17* 11/17* 11/17* 11/17* 11/17* Slide 25

26 SCP II Market Simulation Update Structured Scenario Testing: Results Scenario Group Scenario Description Pass/ Fail AC Availability Calculations AC 001: Test an overlap of forced and planned outages 11/17 AC 002: Test an overlap of a forced outage and two planned outages (removes both of the curtailments) AC 003: Test the overlap of a forced outage and an ambient not due to temperature outage AC 004: Test the overlap of forced, planned, and ambient not due to temperature outages (removes both of the curtailments) AC 005: Test the overlap of an ambient due to temperature outage and a planned outage AC 006: Test how a forced outage for full Pmax on a HQC resource impacts the availability calculation AC 007: Test how a forced outage for 10% Pmax on a HQC resource impacts the availability calculation AC 008: Test how a forced outage for 50% Pmax on a HQC resource impacts the availability calculation AC 009: Test the impact on availability of a forced outage on a non-hqc resource AC 010: Test the impact on availability of a planned outage on a non-hqc resource 11/17 11/17 11/17 11/17 11/17 AC 011: Test the ability to submit an outage correction and its impact on availability 11/17 11/17 Slide 26

27 SCP II Market Simulation Update Structured Scenario Testing: Results Scenario Group Scenario Description Pass/ Fail SCPO Outage Correction Process SCPO 002* : Test an overlap of Forced Outages 11/17 SCC Settlements Calculations SCC 101* : Test the scenario where there are more Availability Charges than Credits for the qualifying RA Units to confirm that the charge code 8824 shall no longer enforce the existing DLAP-only distribution 11/17 SCC 102* : Test scenario where Grandfathered units exist 11/17 SCC 104 : Test to verify that HQC resources are included in the monthly availability calculation (ensure attribute is populated) SCC 105 : Test to confirm the use of Meter Quantity in the availability calculation for HQC resources SCC 106 : Test to confirm that HQC resources SCP charges and credits can be flagged as advisory-only SCC 107 : Test to confirm the existence of the Substitution Request ID attribute in the Settlement Record 11/17 11/17 11/17 11/17 11/17 Slide 27

28 SCP II Market Simulation Update Variances logged to date ID Description Status 1 "Overlap" flag is set when no overlap exists Under investigation 2 Availability Average not calculating correctly (do not agree with manually-calculated values) Under investigation 3 Outage correction cannot be entered for Ambient Due to Temperature to Ambient Not Due to Temperature outages Under investigation Slide 28

29 SCP II Market Simulation Update Structured Scenario Testing Settlement Statements Daily (T+8) November Initial mini-monthly (T+8) November 17 Recalculated mini-monthly (T+13) November 29 ISO will communicate the results of scenarios during the MAP Market Simulation calls Calls will continue during off weeks Some results may time to publish Look for updates to the reference slides for more detail Slide 29

30 SCP II Market Simulation Update SCP II Enhancements Training Next session planned for mid-november November 17, :00pm 3:00pm Details on CAISO calendar Will cover Enhancements included in the SCP II project Product rules applicable to historical qualifying capacity (HQC) resources Forced vs planned outage overlap detection Long-term process for outage cause code corrections Procedures within SCP II Enhancements for HQC resources Slide 30

31 MAP Reference Slides Slide 31

32 Multi-Stage Generation Bidding Scenario Overview October 25, 2010 Li Zhou, Senior Advisor Power Systems Technology Development

33 Multi-Stage Generation Bidding Scenario Overview Objective of This Overview Review various bidding patterns and expected outcomes from the market applications (MAP Stage) Identify the critical patterns that impact the commitment and dispatch decisions of the MSG resources Allow MSG resource owners to make the best use of the features while not getting surprised by certain outcomes Allow CAISO to make the best use of the features when MSG go-live Slide 33

34 Multi-Stage Generation Bidding Scenario Overview (Sample MSG resource definition) Sample MSG resource: 1. Configuration 1: Pmin = 20MW, Pmax = 100MW; 2. Configuration 2: Pmin = 130MW, Pmax = 200MW; 3. Configuration 3: Pmin = 220MW, Pmax = 300MW. Transition Matrix: Config 1 -> Config 2: Config 2 -> Config 3; Config 3 -> Config 2 Config 2 -> Config 1 Config 1 is startup-able and shutdown-able Slide 34

35 Multi-Stage Generation Bidding Scenario Overview (Self Schedule across Configurations Pattern 1) Problematic Bidding Pattern 1, HE 7: Self Schedule at Configuration 1 with 80MW; HE8: Self Schedule at Configuration 3 with 250MW. Market Outcome: It will likely put the MSG resource on Configuration 1 at 80MW for HE7 and shuts it down at the end of HE7. Explanation: When it is purely self schedule (without energy bids), market application interprets this as a self scheduled transition and the self scheduled transition has to be DIRECTLY transit-able across consecutive hours. Slide 35

36 Multi-Stage Generation Bidding Scenario Overview (Self Schedule across Configurations Pattern 1) How to transit from configuration 1 to 3 using self schedules, HE 7:Self Schedule at Configuration 1 with 80MW; HE8: Self Schedule at Configuration 2 with 150MW; HE9: Self Schedule at Configuration 3 with 250MW; Assure self schedules across hours are ramp feasible to finish within an hour as follows: Total ramp time (HE7 to HE8) <= 1 Hour With total ramp time = (Ramp from 80 to 100 based on config 1 s ramp-rate + transition ramp time from config 1 to config 2 + Ramp from 130 to 150 based on configuration 2 s ramp-rate) Slide 36

37 Multi-Stage Generation Bidding Scenario Overview (Self Schedule with Bid Pattern 2) Problematic Bidding Pattern 2: HE 7: Self Schedule at Configuration 3 with 250MW and a bid for ((250, 300), $50) HE8: Self Schedule at Configuration 2 with 150MW. Market Outcome: It will likely put the MSG resource on Configuration 3 for HE7 if it is economically feasible BUT however will not transit to HE8 on configuration 2 even it is ramp feasible. Slide 37

38 Multi-Stage Generation Bidding Scenario Overview (Self Schedule with Bid Pattern 2) Explanation: Whenever there are energy bids for either of the two consecutive hours, market application treats this as an economic dispatch and the self schedule cross hour rule does not apply. Furthermore, since there is no bid segment between 150MW and 200MW, it will not move to configuration 2. Cases that the transition will happen if economic: HE8: Besides the Self Schedule at Configuration 2 with 150MW, a bid segment exists between 150 and 200MW OR HE8: Self Schedule at Configuration 2 with 200MW. Slide 38

39 Multi-Stage Generation Bidding Scenario Overview (Challenge of Minimum Up Time Pattern 3) Problematic Bidding Pattern 3: Assuming minimum up time of configuration 2 is one hour, HE7: Configuration 1 has economic bid from 20 to 100; HE8: Configuration 2 has economic bid from 130 to 200; HE9: Configuration 3 has economic bid from 220 to 300; Possible Market Outcome: Assuming economic, HASP run for horizon (6:15 to 8:00) can commit this resource at Configuration 1 for intervals from 6:15 to 7:30 and transition and commits this resource at configuration 2 for intervals from 7:30 to 8:00. Slide 39

40 Multi-Stage Generation Bidding Scenario Overview (Challenge of Minimum Up Time Pattern 3) Possible Market Outcome: Now the next HASP run for horizon (7:15, 9:00) sees the resource does not have a bid on configuration 2 at HE9 but however it has a MUT time of one hour And it has only been on-line for 30 minutes. It shuts down the resource. This is the similar treatment today for non MSG resource in real-time. Explanation: As a general rule, whenever the market application finds infeasible inter-temporal constraint due to bid-in patterns so it can not move, it will shut the unit down. In this case, HASP only sees the bids for two hours. Slide 40

41 Multi-Stage Generation Bidding Scenario Overview (Challenge of Minimum Up Time Pattern 3) Cases that this will not be a problem HE9: Configuration 2 is bid in. The fact that configuration 2 is bid in will allow optimization to keep the unit on configuration 2 for two 15-minute intervals and then transit to other configurations if economic feasible. Critical Area to avoid infeasibility: If a configuration s minimum up time is N hours and it is only bid in real-time for exactly N hours, the scenario described above can possibly happen due to the different horizon of RTPD. Slide 41

42 Communications CB -Bi-Weekly Teleconference Calls & Market Simulation Plan Twice weekly Market and Performance (MAP) market simulation calls Market Simulation Communications Event Date / Day Time Dial-in Number / Code Market Participant Call Monday Market Participant Call Thursday Web Meeting Web Address Domestic (800) International (612) Web Meeting # Access Code Domestic (800) International (612) Web Meeting # Access Code If there are multiple initiatives in market simulation concurrently the teleconference calls will be combined Convergence Bidding Market Simulation Plan is located at: Slide 42

43 Technical Variances CB - Known variances The Known Technical Variances for Convergence Bidding Market Simulation document is posted at: Slide 43

44 ISO Support and Communications Convergence Bidding Documents Links Relevant Market Notices: Current Initiatives Documentation: Convergence Bidding Technical Specifications Convergence Bidding Registration Application Access Request Forms (AARF) and Application Installation Instructions Systems Access Information For Market Participants Access document Slide 44

45 Reference CB - New Convergence Bidding Endpoints for SIBR-Lite The following new SIBR-Lite endpoints are available to Market Participants on Monday, September 20 for use in the Convergence Bidding Market Simulation. RetrieveCBCleanBidSet_SIBRLITEv _DocAttach_AP RetrieveCBCurrentBidResults_SIBRLITEv _DocAttach_AP A complete listing of endpoints for SIBR-Lite can be found in the Systems Access Information For Market Participants Access document Systems Access Information For Market Participants Access document Slide 45

46 Convergence Bidding Market Simulation Existing SIBR-Lite Endpoints Slide 46

47 CB Update CB - BPM schedule update BPM PRRs are posted on the ISO website ( on 9/22 for the following CB BPMs: Market Instruments Credit Management Scheduling Coordinator Certification and Termination Settlement and Billing Market Operations posted (9/24) Target posting dates for the remaining BPMs: Congestion Revenue Rights 10/8 Definitions and Acronyms 10/31 Settlement Configuration Files will be posted on 10/15 Slide 47

48 Updated Technical Specifications CB - Technical Specifications The ISO has posted technical specification documents to the Convergence Bidding Technical Specifications webpage: New SIBR Rules and are posted SIBR Business Rules for Bidding - Version (CB) Release Notes SIBR Rules (CB) ITC - OTC Mapping for CB Position Limits FNM Pricing Node Mapping (based on FNM Release DB49 V1) - 8/17/10 Convergence Bidding Eligible Locations and Limits - Version 3-8/19/10 Slide 48

49 Structured Scenarios Overview CB Scenarios 1 to 5 # Description SIBR Test Suspended nodes: The ISO will suspend predetermined nodes which will prevent bids from being accepted as valid transactions at those points. The suspended node locations will be provided to all market participants before the start of market scenario. SIBR Test Position Limits: Bids will be submitted in high enough volume that they will exceed position limits. To accomplish this objective the ISO will submit bids by 0600 at four intertie points which will be within the position limit. At 0700 the ISO will reduce the Operating Transfer Capacity (OTC) at those locations which will cause bids to be rejected because the position limits were exceeded. At 0900 the ISO will remove the OTC reduction where market participants can resubmit bids at the affected ties. SIBR Test Position Limits - Interties reduced within 1 hour of market close: This scenario will demonstrate the impacts to convergence bids when Operating Transfer Capacity (OTC) is reduced within one hour of market close. To accomplish this objective the ISO will submit bids by 0900 at four intertie points which will be within the position limit. The ISO will reduce the Operating Transfer Capacity (OTC) at 0915 which will impact bids submitted between 0915 and market close at SIBR & CTS: The ISO will perform a credit reduction test which serves the purpose of viewing results when bids are submitted when there is no available credit. The ISO will reduce the available credit amount of all market participants by 50%. Market participants are encouraged to submit bids that will exceed their available credit limit. Market participants will be able to see and validate the results of submitting transactions when there is insufficient credit available. SIBR Test Suspended SCID: The ISO will suspend a SCID at all nodes which will prevent market participant bids from being accepted as valid transactions at any nodes. The ISO will suspend a SCID at a predefined node whose location will be provided to the market participant prior to the running of the scenario. This ISO will select market participants who have more than one SCID for convergence bidding and have agreed to be a participant in the scenario. Slide 49

50 Convergence Bidding Market Simulation Meter Data Submission The ISO will not seed meter data in OMAR for the CB market simulation, we will use meter data estimation There are no meter data changes with the implementation of Convergence Bidding. Market Participants who would like to perform regression testing can submit meter data to OMAR. Market Participant and Vendors can retrieve meter data through the BD File. The billing determinants are BA_10M_RSRC_METER_QTY BA_10M_RSRC_METER_SOURCE_FLAG OMAR will be available in the MAP Stage environment and participants may download meter data from OMAR SCs must first submit meter data, including data for ISO-polled meters Either CSV of MDEF format may be uploaded to OMAR The upload file format is identical to the download format The ISO will use the production OMAR usernames but reset the passwords for use in the simulation by individuals not normally involved in meter data submission Slide 50

51 Convergence Bidding Market Simulation Meter Data Submission Training A document describing the step-by-step approach to submitting meter data for market simulation is posted on the ISO website Meter data submission training guide: Technical specifications for file format: Please contact MDAS at (916) or mdas@caiso.com for questions related to meter data submission in market simulation Note: The training materials reference Production URLs when submitting meter data for market simulation substitute MAP Stage URLs. The URLs can be viewed in the Systems Access Information For Market Participants Access document. Slide 51

52 Frequently Asked Questions CB - FAQ reference questions # Question ISO Response 1 How do I access the SIBR-Lite Environment? The URL for MAP Stage which points to SIBR-Lite is: The URL for the SIBR-Lite environment is Check your bids sets for the following: Proper Date Valid Locations 2 Why are my bids being rejected? Supply curves are monotonically increasing Demand curves are monotonically decreasing Validate the web services being used by your API 3 What time does the Market Close? The market closes at 11:00 PPT. When a bid is submitted for credit approval and SIBR shows a credit status 4 Why does a SIBR rule fire when my bid is pending? of pending the rules associated with the pending status can be viewed by selecting the little yellow triangle. Virtual bids must start at 0 MW and have an increment of at least 1 MW per segment. 5 What is the minimum bid segment for virtual bids? Example supply bid set: (0,$10), (1, $15), (2,$20), (3,$20). Example demand bid set: (0,$20), (1, $15), (2,$10), (3,$10). Bids can be submitted to SIBR and then downloaded through an API. The ISO has provided a sample raw bid on the CB technical specifications 6 How can I create a sample XML format raw bid set? webpage. Dates will need to be modified for the trade date and then bids need to meet the SIBR business rules. Slide 52

53 Frequently Asked Questions CB Week of October 4 New Questions # Question ISO Response If I have a bid with one bid segment rejected does the whole bid get rejected? In the market simulation calendar what is the difference between the operating date and trade date? How can I find the internal node position limits values in the market simulation? Day-ahead market virtual bids are processed as a 24 hour group. If one hourly segment violates a position limit or other SIBR rule the bid will be invalidated. Structured scenarios are listed by operating day and will execute on the following trade date. For example a scenario listed on 10/4 has a trade date of 10/5. Internal nodes have a 10% limit, These values can be found in the Convergence Bidding Eligible Locations and Limits - Version 3, spreadsheet posted at: Where can I find out how much OTC is available on an intertie? Interties have a 5% limit of the available OTC. In SIBR the limit viewer shows the import and export OTC available at the selected interchange. When the market moves to the MAP Stage environment the values can be found in OASIS running the Current Transmission report for the timeframe of interest. 11. What OTC data is being used in SIBR-Lite testing? OTC data from September 8, 2010 will be seeded. Information can be found on the Transmission tab of the OASIS website: OASIS>Transmission>Current Transmission Usage>Date From 9/8/2010>Date To 9/8/2010 Slide 53

54 New SIBR Functionality Limit Viewer Slide 54

55 New SIBR Functionality Convergence Bidding Tab Slide 55

56 CMRI CB Recently Updated CMRI Technical Specifications The ISO has posted technical specification documents to the Convergence Bidding Technical Specifications webpage: New CMRI Technical Specifications are posted Artifacts are updated CMRI Interface Specification for Market Results Version 3.7 Release Notes for New ISO Market Interface Specification for Market Results Services Version 3.7 Three new web services added retrievecrradjustmentprices retrievecrradjustmentconstraints retrievecrradjustmentflowimpact Slide 56

57 Week of October 25 Activity Recap CB Settlement Publication Calendar Slide 57

58 SCP II Market Simulation Update Structured Simulation Scenarios Slide 58

59 SCP II Market Simulation Update Structured Scenario USUB 009 Description Actions/ Instructions Test the ability to request Unit Substitution without a reported outage (this will occur for units less than 10MW who only submit outages at month s end) CAISO for Scheduling Coordinator: Use RAAM to select RA and substitute units for substitution to satisfy forced outage MW value CAISO: (Specific test will need to be performed in the event of no forced or ambient temperature derate) Evaluate and approve/reject based upon applicable criteria Notes Expected Outcome Scheduling coordinator may review the status of the submitted unit substitution on the Substitutions screen in RAAM Actual Outcome Substitution ID Request to substitute small resource (capacity < 10MW) where no outage has been reported with compliant resource ACCEPTED, required the input of a "dummy" outage Pass/ Fail Pass Slide 59

60 SCP II Market Simulation Update Structured Scenario USUB 010 Description Actions/ Instructions Test Real Time Unit Substitution for Prequalified Local Resource. CAISO for Scheduling Coordinator: Use RAAM to nominate substitute unit from prequalified list CAISO: Approval will be based upon unit meeting all of the following criteria: Both the original and substitute units are located at same bus The units have similar operating characteristics The substitute unit is dispatchable Substitute unit has the same start time as the original unit Notes Reference SCP Tariff Section: Expected Outcome Scheduling coordinator may review the status of the submitted unit substitution on the Substitutions screen in RAAM Actual Outcome Substitution ID Request to substitute resource in outage with compliant pre-qualified resource ACCEPTED as expected. Pass/ Fail Pass Slide 60

61 SCP II Market Simulation Update Structured Scenario USUB 011 Description Actions/ Instructions Test Day Ahead Unit Substitution for a local unit wanting to substitute two units to meet the obligation of one unit CAISO for Scheduling Coordinator: Use RAAM to nominate two units for substitution to satisfy forced outage MW value (ensure both units are located at same bus, have similar operating characteristics, is dispatchable, and have the same start time as the original unit) CAISO: Approval will be based upon unit meeting all of the following criteria: Both the original and substitute units are located at same bus The units have similar operating characteristics The substitute unit is dispatchable Substitute unit has the same start time as the original unit Note: Both units must meet this criteria or request will be rejected Notes Reference SCP Tariff Section: Expected Outcome Scheduling coordinator may review the status of the submitted unit substitution on the Substitutions screen in RAAM Actual Outcome Substitution ID Request to substitute resource in outage with multiple compliant, pre-qualified local resources ACCEPTED as expected Pass/ Fail Pass Slide 61

62 SCP II Market Simulation Update Structured Scenario USUB 017 Description Actions/ Instructions Test scenario where 3rd party Day Ahead Unit Substitution exists CAISO for Scheduling Coordinator: Use RAAM to nominate third party owned unit for substitution (unit can be local or system) CAISO for Third Party: Use RAAM to accept the nomination CAISO: Approval will be based on similar operational characteristics Notes Expected Outcome Scheduling coordinator may review the status of the submitted unit substitution on the Substitutions screen in RAAM Actual Outcome Substitution ID Request to replace resource in outage with compliant 3rd-party resource ACCEPTED as expected Pass/ Fail Pass Slide 62

63 SCP II Market Simulation Update Structured Scenario USUB 019 Description Actions/ Instructions Test scenario where 3rd party rejects Day Ahead unit substitution CAISO for Scheduling Coordinator: Use RAAM to nominate third party owned unit for substitution (unit should be prequalified and located on the same bus) CAISO for Third Party: Use RAAM to reject the nomination CAISO: Rejection will be based on both parties not approving the substitution Notes Expected Outcome Scheduling coordinator may review the status of the submitted unit substitution on the Substitutions screen in RAAM (uncheck Show Approved Third Party Requests Only box to see pending/rejected requests) Actual Outcome Substitution ID Request to substitute resource on outage with compliant 3rd party resource which is subsequently denied by the owner - DENIED as expected Pass/ Fail Pass Slide 63

64 SCP II Market Simulation Update Structured Scenario USUB 022 Description Actions/ Instructions Test scenario where RAAM shall process unit substitutions for existing SCP RA resources with no change resulting from the addition of HQC resources (non-hqc resource substituted for non-hqc resource) CAISO for Scheduling Coordinator: Submit a forced outage on a non-hqc resource, identify a substitute non-hqc resource (no outage on that resource), and request the substitution before 6AM on the day prior to the trade date CAISO: Approve the substitution for the resource on the forced outage before 11 AM on the day prior to the trade date CAISO for Scheduling Coordinator: Submit bids for the substitute amount into the day-ahead market before 11 AM on the day prior to the trade date Notes Expected Outcome Given timing of outcomes to be observed, this scenario should be run early in the week for a trade date later in the week Verify that the substitution is properly captured in the settlement calculation Actual Outcome Substitution ID Request to substitute non-hqc resource in outage with compliant non-hqc resource ACCEPTED as expected Pass/ Fail Initial Pass - availability calculations pending Slide 64

65 SCP II Market Simulation Update Structured Scenario USUB 023a Description Actions/ Instructions Test the application of existing unit substitution rules when substituting an HQC resource for a nongrandfathered, non-hqc resource CAISO for Scheduling Coordinator: Submit a forced outage on a non-hqc resource, identify a nongrandfathered HQC resource to substitute (no outage on that resource), and request the substitution before 6AM on the day prior to the trade date CAISO: Approve the substitution for the resource on the forced outage before 11 AM on the day prior to the trade date CAISO for Scheduling Coordinator: Submit bids for the substitute amount into the day-ahead market before 11 AM on the day prior to the trade date Notes Expected Outcome Given timing of outcomes to be observed, this scenario should be run early in the week for a trade date later in the week Verify that the substitution is properly captured in the settlement calculation Actual Outcome Substitution ID Request to substitute non-hqc resource in outage with compliant non-grandfathered HQC resource ACCEPTED as expected Pass/ Fail Initial Pass - availability calculations pending Slide 65

66 SCP II Market Simulation Update Structured Scenario USUB 023b Description Actions/ Instructions Test the application of existing unit substitution rules when substituting a non-hqc resource for a non-grandfathered HQC resource CAISO for Scheduling Coordinator: Submit a forced outage on the HQC resource, identify a substitute non-hqc resource (no outage on that resource), and request a substitution before 6AM on the day prior to the trade date CAISO: Approve the substitution for the resource on the forced outage before 11 AM on the day prior to the trade date CAISO for Scheduling Coordinator: Submit bids for the substitute amount into the day-ahead market before 11 AM on the day prior to the trade date Notes Expected Outcome Given timing of outcomes to be observed, this scenario should be run early in the week for a trade date later in the week Verify that the substitution is properly captured in the settlement calculation Actual Outcome Substitution ID Request to substitute HQC resource in outage with a compliant non-hqc resource ACCEPTED as expected Pass/ Fail Initial Pass - availability calculations pending Slide 66

67 SCP II Market Simulation Update Structured Scenario USUB 023c Description Actions/ Instructions Test the application of existing unit substitution rules when substituting a non-grandfathered HQC resource for a non-grandfathered HQC resource CAISO for Scheduling Coordinator: Submit a forced outage on the non-grandfathered HQC resource, identify a substitute non-grandfathered HQC resource (no outage on that resource), and request a substitution before 6AM on the day prior to the trade date CAISO: Approve the substitution for the resource on the forced outage before 11 AM on the day prior to the trade date CAISO for Scheduling Coordinator: Submit bids for the substitute amount into the day-ahead market before 11 AM on the day prior to the trade date Notes Expected Outcome Given timing of outcomes to be observed, this scenario should be run early in the week for a trade date later in the week Verify that the substitution is properly captured in the settlement calculation Actual Outcome Substitution ID Request to substitute non-grandfathered HQC resource in outage with a compliant nongrandfathered HQC resource ACCEPTED as expected Pass/ Fail Initial Pass - availability calculations pending Slide 67

68 SCP II Market Simulation Update Structured Scenario USUB 024 Description Actions/ Instructions Notes Expected Outcome Actual Outcome Pass/ Fail Test the ability to enter the total MW amount of RA capacity needed to cover a resource on outage CAISO for Scheduling Coordinator: Create a substitution and enter the MW amount of RA capacity needed in the Outage Resource RA Capacity MW field The relevant field is the Outage Resource RA Capacity MW field, which can be found on the New Unit Substitution Request page (resource level) SC can see and enter information in the new field on the New Unit Substitution Request page Pre-requisite for passing all other structured scenarios Pass Slide 68

69 SCP II Market Simulation Update Structured Scenario AC 001 Description Test an overlap of forced and planned outages Actions/ Instructions CAISO for Scheduling Coordinator: Submit a forced outage, and submit a planned outage (which should be less than full derate, and less than forced outage) CAISO: Review sum of both outages and resulting availability Notes Run this scenario for both HQC and non-hqc resources Expected Outcome Actual Outcome The planned outage is backed out, but the forced outage continues to impact the Availability Calculation as shown on the RAAM calculation screen "Overlap" flag is checked when there is no overlap. Affects outages and curtailments. Pass/ Fail Slide 69

70 SCP II Market Simulation Update Structured Scenario AC 002 Description Test an overlap of a forced outage and two planned outages (removes both of the curtailments) Actions/ Instructions CAISO for Scheduling Coordinator: Submit a forced outage, and submit two planned outages CAISO: Review sum of both outages and resulting availability Notes The sum of the planned outages must be less than the full derate, and less than forced outage Expected Outcome Actual Outcome The curtailments for both planned outages are backed out, but the forced outage continues to impact the Availability Calculation as shown on the RAAM calculation screen "Overlap" flag is checked when there is no overlap. Also appears to affect the Curtailed MW. Pass/ Fail Slide 70

71 SCP II Market Simulation Update Structured Scenario AC 003 Description Test the overlap of a forced outage and an ambient not due to temperature outage Actions/ Instructions CAISO for Scheduling Coordinator: Create a forced outage and create an ambient not due to temperature outage that is less than full derate and less than the forced outage CAISO: Review sum of both outages and resulting availability Notes Expected Outcome The ambient not due to temperature is backed out, but the forced outage continues to impact the Availability Calculation as shown on the RAAM calculation screen Actual Outcome Pass/ Fail Slide 71

72 SCP II Market Simulation Update Structured Scenario AC 004 Description Actions/ Instructions Test the overlap of forced, planned, and ambient not due to temperature outages (removes both of the curtailments) CAISO for Scheduling Coordinator: Create a forced outage, create a ambient not due to temperature outage, and create a planned outage CAISO: Review sum of both outages and resulting availability Notes The sum of the ambient and planned outages must be less than full derate, and less than forced outage Expected Outcome Actual Outcome The planned and ambient not due to temperature outages are backed out, but the forced outage continues to impact the Availability Calculation as shown on the RAAM calculation screen Overlap Flag is checked when there is no forced or ADT outage. There has to be both for there to be an overlap. Pass/ Fail Slide 72

73 SCP II Market Simulation Update Structured Scenario AC 005 Description Test the overlap of an ambient due to temperature outage and a planned outage Actions/ Instructions CAISO for Scheduling Coordinator: Create an ambient due to temperature outage and create a planned outage that is less than full derate and less than ambient due to temperature outage CAISO: Review sum of both outages and resulting availability Notes Expected Outcome The planned outage is backed out, but the ambient due to temperature outage continues to impact the Availability Calculation as shown on the RAAM calculation screen Actual Outcome Pass/ Fail Slide 73

74 SCP II Market Simulation Update Structured Scenario AC 006 Description Actions/ Instructions Test how a forced outage for full Pmax on a HQC resource impacts the availability calculation CAISO for Scheduling Coordinator: Create a forced outage that is equal to Pmax CAISO: Review the resulting impact on availability Notes Select SCP II resources specific to the major LSEs (PG&E, Edison, SDG&E) The resource used in this scenario should not be a grandfathered resource Expected Outcome Actual Outcome Availability should be zero Availability Average not calculating correctly (do not agree with manually-calculated values) Pass/ Fail Slide 74

75 SCP II Market Simulation Update Structured Scenario AC 007 Description Test how a forced outage for 10% Pmax on a HQC resource impacts the availability calculation Actions/ Instructions CAISO for Scheduling Coordinator: Create a forced outage that is 10% of Pmax CAISO: Review the resulting impact on availability Notes RA capacity of the selected resource must be 85% or less of Net Qualifying Capacity (NQC) Select SCP II resources specific to the major LSEs (PG&E, Edison, SDG&E) The resource used in this scenario should not be a grandfathered resource Expected Outcome Availability should be 100% Actual Outcome Pass/ Fail Pass Slide 75

76 SCP II Market Simulation Update Structured Scenario AC 008 Description Actions/ Instructions Test how a forced outage for 50% Pmax on a HQC resource impacts the availability calculation CAISO for Scheduling Coordinator: Create a forced outage that is 50% of Pmax CAISO: Review the resulting impact on availability Notes RA capacity of the selected resource is equal to NQC Select SCP II resources specific to the major LSEs (PG&E, Edison, SDG&E) The resource used in this scenario should not be a grandfathered resource Expected Outcome Availability should be 50% of NQC. This can be viewed on the RAAM calculation screen Actual Outcome Pass/ Fail Pass Slide 76

77 SCP II Market Simulation Update Structured Scenario AC 009 Description Test the impact on availability of a forced outage on a non-hqc resource Actions/ Instructions CAISO for Scheduling Coordinator: Enter a forced outage on a non-hqc resource CAISO: Review the resulting impact on availability Notes Expected Outcome Verify that there is no change in the impact on the Availability Calculation from this type of resource outage (should be consistent with SCP I) Actual Outcome Pass/ Fail Pass Slide 77

78 SCP II Market Simulation Update Structured Scenario AC 010 Description Test the impact on availability of a planned outage on a non-hqc resource Actions/ Instructions CAISO for Scheduling Coordinator: Enter a planned outage on a non-hqc resource CAISO: Review the resulting impact on availability Notes Expected Outcome Verify that there is no change in the impact on the Availability Calculation from this type of resource outage (should be consistent with SCP I) Actual Outcome Pass/ Fail Pass Slide 78

79 SCP II Market Simulation Update Structured Scenario AC 011 Description Test the ability to submit an outage correction and its impact on availability Actions/ Instructions CAISO for Scheduling Coordinator: Create a forced outage and submit an outage correction CAISO: Approve or reject the outage correction based on applicable criteria, and review the resulting impact on availability Notes Expected Outcome Approved corrections will not impact the Availability Calculation Actual Outcome Pass/ Fail Slide 79

80 SCP II Market Simulation Update Structured Scenario SCPO 002 Description Test an overlap of Forced Outages Actions/ Instructions CAISO for Scheduling Coordinator: Submit two forced outage with partially overlapping date ranges. CAISO: Review sum of both outages and resulting availability Notes Expected Outcome Ensure that the full range (start date of earlier outage to end date of later outage) is covered in the availability calculation The timeframe of both outages is included in the availability calculation on the RAAM calculation screen Actual Outcome Pass/ Fail Pass Slide 80