Entergy Actual Peak Load and Peak Load Forecast Postings

1. Entergy Actual Peak Load and Peak Load Forecast Postings

2. What are Load Postings? • Per FERC Order 890, all Transmission Providers must post Actual Peak Loads and Forecasted Peak Loads on OASIS • Entergy Started posting flat files of Actual Peak Load and Hourly Forecasted Loads for the Native Load and System Load in July 2007 • Subsequently FERC Order 676 E required posting these loads on OASIS so that these can be queried using NAESB developed templates. • Entergy started posting Actual Peak Loads and Load Forecasts using these templates.

3. Native vs. System Load • Native Loads are the values of Entergy’s metered load • System Loads are the values for the total load that includes non-Entergy loads within the Entergy BA Area

4. Actual vs. Forecasted Load • Actual Peak Load data is the peak hourly MW Load that occurred for the previous day • One entry per day • Forecasted Peak Load is the forecasted peak hourly MW Load that is expected to occur in the future • Currently Entergy posts 35 days into the future • Since the forecasted peaks for a given day can change, it sometimes results in more than one peak load forecast value for a day • Requirement is to post only a single forecasted peak value for the next day

5. Why are there multiple records for Forecasted Peak Load? • Since Forecasted Load is currently posted for future days, a change in peak load forecast value for a given day may create multiple values for that day based on postings made on different days. • An additional record is created if the hour in which the maximum MW value occurs shifts from previous days • If a different MW value for the daily peak load is forecasted but it is for the same hour, then that is reflected in the Audit log

6. Concern • Requirement is to post forecasted peak load as a single MW hourly value for next day • Current daily postings for 35 days into future is causing multiple peak load values for a given day

7. Solution • Entergy is going to post only a single MW peak load value for the next day in compliance with requirements so that only a single value is available for a given day • Posting will be done every day for the next day based on the latest available forecast. • These Peak Load Forecast values will not be overwritten by any subsequent forecasts

8. Conclusion • Entergy has changed its Load Posting methodology to using the OASIS templates • Actual Load Postings are for the previous day and only create one record a day • Forecasted Load Postings currently are for 35 days in the future and may create multiple records • Entergy is going to fix this problem in near future by posting a single forecasted peak load value only for next day to comply with the requirements

9. HOW TO ACCESSACTUAL PEAK LOAD &PEAK LOAD FORECAST POSTINGSON ENTERGY OASIS

10. Load Posting Data on webOASIS • The Load Posting data can be found under the “Sys Data” tab of webOASIS

11. Filters on System Data Screen • The System Data screen has a set of filters to assist in finding the Load Posting data

12. Filters on System Data • The TP should be set to EES • The Type should be set to LOAD_ZONE

13. Filters on System Data • The Attributes field allows the choice of four options: • NATIVE_ACTUAL_LOAD • NATIVE_FORECASTED_LOAD • SYSTEM_ACTUAL_LOAD • SYSTEM_FORECASTED_LOAD • Entergy does not use the ZONE attributes

14. Filters on System Data • The Time filters determine what records are retrieved in webOASIS • The Start, Stop, and Active options use the Start Time and Stop Time fields to retrieve records

15. Filters on System Data • The Update options use the Updated Time field to retrieve records

16. Viewing Actual Load Data • Since Actual Load postings are always in the past, the easiest way to view them is to set the Attribute for the load of interest with Time = Active and Before Today • Only one record exists per day

17. Viewing Forecasted Load Data • Forecasted Load Posting data is always for days in the future, so the time filters can alter what is displayed • Setting the Time filters to “Active Today forward” or “Start Today forward” results in showing all future records • Multiple records may exist for certain days

18. Viewing Forecasted Load Data • Setting the Time filters to “Update Today“ returns all records updated by today’s load posting

19. Example - Why are there multiple records? • Let’s look at an example of June 1 for Native Forecasted Load • Two records exist • On the System Data Summary page, look for the Posting Ref with the highest numerical value to find the active one • In this example, the 21832 value is active since it is the latest record

20. Example - Why are there multiple records? • We can track the history of the Forecasted Load postings for this day by looking at the Audit history, however the easiest way to determine the most recent record is by looking for the Posting Ref with the highest numerical value. • In order to view the historical postings, click on the Posting ref to open a Record

21. Example - Why are there multiple records? • The Individual Record opens • Click the Audit button from this screen to see the history of the record

22. Example - Why are there multiple records? • This record is for the 15:00-16:00 hour on May 1st • The Audit Log shows that this record initially was created on April 28th • This record has been updated once with a different MW value on May 27th

23. Example - Why are there multiple records? • The second record for May 1st is for the 16:00-17:00 hour • This record was initially created on May 23rd • The Record Type = I shows the initial record; the Record Types = U show the updates • This record has 5 updates with the last one being the current value