MARS 867_03F ROR vs. Settlement vs. 810 Scenarios ERCOT September 2008

2 Purpose: Facilitate discussion of how the REP of Record (ROR) history is maintained for ESI IDs with AMI meters, how/what usage is used in settlement and what is affiliated with the 810 –Currently - NIDR 867_03F - ERCOT stops the REP history with the day prior to the date received in the 867_03F at 23:59:59. –With AMI - NIDR 867_03F will continue to be used to complete service orders and maintain the REP history. Therefore, ERCOT will continue to stop the REP history with the day prior to the date received in the 867_03F at 23:59:59. AMI IDR data provided via LSE file could be available through the stop date provided in the NIDR 867_03F at 23:59:59. This would be an extra day of usage where there is no ROR. –Currently - IDR 867_03F - ERCOT stops the REP history with the date received in the 867_03F at 23:59:59.

3 7/22 23:59:59 7/21 23:59:59 REP A Relationship 867_03F NIDR Data MVO requested for 7/22/2008 TDSP reads meter for MVO 7/22/ :03:00 Non IDR 867_03F is sent in with date of 7/22/2008 Current ERCOT System: Move Out Non-IDR

4 REP of Record history: Rep A Relationship exists from 1/1/2007 to current. Rep A submits a MVO for 7/22/2008. MVO for Rep A is Scheduled for 7/22/2008. MVO occurred 7/22/ :03:00 – TDSP reads meter at this time. TDSP sends Non IDR 867_03F with a stop date of 7/22/2008, which includes the usage that occurred on 7/22/2008 in the total kWh. Non IDR 867_03F completes MVO with a stop date of 7/21/ :59:59. This ESIID is available for settlement of operating days 1/1/2007 through 7/21/2008 (inclusive). Non IDR Usage/810: ERCOT loads the Non IDR 867_03F from the TDSP for 6/22/2008 – 7/22/2008, which includes the usage that occurred on 7/22/2008 in the total kWh. The usage stop time is interpreted as 7/21/ :59:59 for ERCOT settlement. The 810 from the TDSP to LSE is for 6/22/2008 – 7/22/2008, which includes the changes that occurred on 7/22/2008. Settlement using NIDR data: For all operating days between 6/22/2008 and 7/21/2008 (inclusive), the NIDR usage read loaded for this example will be used to scale the NIDR profile for settlement for each operating day. The scalar ratio is the meter read total kWh divided by profile total kWh. ERCOT applies the backcasted profile to the ESIID Non-IDR monthly cumulative read data to convert data to 15 minute intervals.

5 Example Non-IDR Load Profile for settlement

6 Move Out Non-IDR using AMI for settlement MVO requested for 7/22/2008 TDSP reads meter for MVO 7/22/ :03:00 Non IDR 867_03F is sent in with date of 7/22/2008 to complete MVO AMI Interval data sent in through 7/22/ :59:59 7/22 23:59:59 7/21 23:59:59 REP A Relationship 867_03F NIDR Data AMI IDR Data UFE

7 Move Out Non-IDR using AMI for settlement REP of Record history: Rep A Relationship exists from 1/1/2007 to current. Rep A submits a MVO for 7/22/2008. MVO for Rep A is Scheduled for 7/22/2008. MVO occurred 7/22/ :03:00 – TDSP reads meter at this time. TDSP sends Non IDR 867_03F with a stop date of 7/22/2008, which includes the usage that occurred on 7/22/2008 in the total kWh. Non IDR 867_03F completes MVO with a stop date of 7/21/ :59:59. This ESIID is available for settlement of operating days 1/1/2007 through 7/21/2008 (inclusive). Non IDR Usage/810: ERCOT loads the Non IDR 867_03F from the TDSP for 6/22/2008 – 7/22/2008, which includes the usage that occurred on 7/22/2008 in the total kWh. This is not used for settlement. The 810 from the TDSP to LSE is for 6/22/2008 – 7/22/2008, which includes the activity that occurred on 7/22/2008. AMI IDR data: Since the MVO occurred 7/22/ :03:00, the TDSP will provide data to ERCOT for the complete operating day of 7/22/2008. Settlement using AMI IDR data: Settlement is based on the ‘ACTIVE’ status of the ESIID, the characteristics assigned and the usage. In this example, last operating day for this ESIID for settlement is 7/21/2008. The ESIID is de-energized starting 7/22/2008, therefore, the AMI IDR data for 7/22/2008 would not be used in settlement.

8 Example AMI IDR Load for settlement 7/21/08 - Used in Settlement 7/22/08 - Not used in Settlement

9 7/22 23:59:59 REP A Relationship 867_03F IDR Data MVO requested for 7/22/2008 TDSP reads meter for MVO 7/22/ :03:00 IDR 867_03F is sent in with date of 7/22/ :59:59 Current ERCOT System: Move Out IDR

10 Current ERCOT System: Move Out IDR REP of Record history: Rep A Relationship exists from 1/1/2007 to current. Rep A submits a MVO for 7/22/2008. MVO for Rep A is Scheduled for 7/22/2008. MVO occurred 7/22/ :03:00 – TDSP reads the meter at this time. TDSP sends IDR 867_03F with a stop date of 7/22/ :59:59. IDR 867_03F completes MVO with a stop date of 7/22/ :59:59. This ESIID is available for settlement of operating days 1/1/2007 through 7/22/2008 (inclusive). IDR Usage/810: ERCOT loads the IDR 867_03F from the TDSP for 6/22/ :00:00 – 7/22/ :59:59. The 810 from the TDSP to LSE is for 6/22/ :00:00 – 7/22/ :59:59. Settlement using IDR data: For all operating days between 6/22/2008 and 7/22/2008 (inclusive), the associated 96 intervals for each operating day in the IDR usage read loaded for this example will be used for each settlement.

11 Example IDR Load for settlement 7/21/08 - Used in Settlement7/22/08 - Used in Settlement

12 Summary of all 3 examples Scenario - MVO schedule for 7/22/2008 and TDSP reads meter 7/22/ :03:00 ESIID Characteristics for Settlement Rep of Record History Profile Code Meter Type 867_03F Non-Interval Usage 867_03F Interval Data AMI Interval Data (LSE File)810Comments #1 Current – Using 867_03F NIDR to complete Service Order and NIDR usage for Settlements start - 01/01/ :00:00 stop - 07/21/ :59:59 NIDR start - 06/22/2008 stop - 07/22/2008 (interpreted as 07/21/08 23:59:59) -- start - 06/22/2008 stop - 07/22/2008 (interpreted as 07/21/08 23:59:59) #2 Using 867_03F NIDR to complete Service Order and AMIT LSE usage for Settlements start - 01/01/ :00:00 stop - 07/21/ :59:59 IDR start - 06/22/2008 stop - 07/22/2008 (interpreted as 07/21/08 23:59:59) -- daily reads through 7/22/ :59:59 start - 06/22/2008 stop - 07/22/2008 (interpreted as 07/21/08 23:59:59) ESIID not included in the 07/22 settlement due to stop time on service instance although usage is available. #3 Current – Using 867_03F IDR to complete Service Order and IDR usage for Settlement start - 01/01/ :00:00 stop - 07/22/ :59:59 IDR-- start - 06/22/ :00:00 stop - 07/22/ :59:59 -- start - 06/22/ :00:00 stop - 07/22/ :59:59

13 Number of orders completed by 867_03F Orders Completed by 867_03 Final Note: The number of MVOs where a MVI completed within one day was around 1,000 for a 3 month period. count Move InMove Out Move Out to CSA Switch Mass Transition Drops Jun-08 12,16878,4581,6542,38745 May-08 11,81170,0521,8473, Apr-08 10,77571,1311,5724,274n/a Percentage Of Total Completed Orders Move InMove Out Move Out to CSA Switch Mass Transition Drops Jun %100.00%4.42%3.63%0.14% May %100.00%5.64%7.33%6.82% Apr %100.00%4.96%7.19%n/a

14 Food for thought This presentation shows the example of a MVO completing with an 867_03F, as well as what happens in settlements and the 810. You could take this same example and apply it to MVI, MVO to CSA, Switch, etc. Options: –Do nothing Consider impacts to: –UFE for settlement for MVO –Who is settled in the instance of a MVI, MVO to CSA, SWITCH, etc. –Change the ROR date logic Consider impacts to: –MVO only solution – consider impact to ‘leap frogging’. –Stacking logic –What happens if we apply this across SWITCH, MVI, etc. as well? (a much larger impact) –Increase the volume of Siebel exceptions that ERCOT manages, if there is no change to TDSPs sending data What’s next? For the interim AMI solution (PR 80027), are there any changes to the order completion process to account for AMI interval data available for settlement that need to be included in the project requirements?