SCR 740 Business & Technical Training

1. ERCOT presents: Market Data Transparency SCR 740 Business & Technical Training SCR 727 Phase II: Web Services Market Data Transparency

2. Training ground rules • Be courteous to those around you. • Please turn Cell Phones, Pagers, and Notebooks to vibrate/mute. • If you have to take a call, please leave the room so as not to disturb those around you. • Questions are welcome during the discussion. Please raise your hand to ensure everyone has the opportunity to participate. • Have fun. Market Data Transparency

3. Agenda • Joint Business & Technical Meeting: • Introductions & Expectations • Agenda Overview & Course Goals • SCR 740 Background • Services Available • General Information • Future of Web Services Market Data Transparency

4. Agenda – Breakout Sessions • Business Breakout: • Accessing Data Requests • Using Data Requests • Error Codes • Technical Breakout: • Using the GUI for Scheduled Data Requests • Web Services • Request Processing & Delivery Market Data Transparency

5. Course goals • Business users should walk away with a basic understanding of the specific services offered including: • Where and how to access these services • Inputs/Outputs of each service • Understanding of Point in Time Selectivity • Technical users should be able to: • Understand SOAP & XML • Submit SOAP Requests and receive SOAP Responses • Handle fault and error codes • Basic understanding of EIS Operations Market Data Transparency

6. SCR740 background • SCR 740 was a System Change Request initiated by the Market in early 2005. The requirements as identified by ERCOT and the Market were: • Provide Market Participants capability to query ESIID level data (from the SCR727 ESIID Service History & Usage Extract) directly from ERCOT Systems • Capability for Market Participants to request baseline databases to recreate their entire 727 database • Provide audit capabilities Market Data Transparency

7. Background cont. • ERCOT met with the Market several times in 2005 to both identify the requirements and ensure Market understanding of the path ERCOT was taking to implement Web Services. • In addition to these Market Trainings, ERCOT has continued to work with the Data Extract Working Group (DEWG) to keep the Market apprised of the progress and timeline of PR_50024. • In November of 2005 ERCOT introduced the initial framework for Web Services and an overview of the Graphical User Interface(GUI) Prototypes in development. Market Data Transparency

8. Background cont. • In December of 2005 ERCOT met with the Market and held follow up conference calls to discuss the security and conversation strategies for the Web Services. Based on these discussions, ERCOT determined the following. • ERCOT chose to use the existing Digital Certificate process for security strategy • ERCOT opted to utilize a WSDL/SOAP Service over a REST Service Market Data Transparency

9. SCR 740 & PR_50024 • To implement SCR740, a project was created. This project is PR_50024. All information including presentations and documentation pertaining to SCR740/PR_50024 can be found on the ERCOT website project page at the following link: • http://www.ercot.com/services/comm/projects/current/50024/index.html • PR_50024 is currently in execution and scheduled to be implemented December 2, 2006. Market Data Transparency

10. Accessing Web Services • The Web Services/Data Requests for SCR 740 will be available via the Texas Market Link. • Once logged into the TML, access the “Archive” tab in the top/middle of the page. https://tml.ercot.com/tibco/archive Market Data Transparency

11. Data requests • High level overview of the fifteen Data Requests that are available via the GUI and Application Program Interface (API). • The details of the requests will be covered in the business training session this afternoon. Market Data Transparency

12. Data request index Market Data Transparency

13. Transaction information • Along with the GUI, you can also view the completed SOAP request and response messages under Transaction Information. Market Data Transparency

14. Additional information • Market Participants will only receive data results for ESIIDs that belong to them at the point in time of their request. • Market Participants may upload a parameter file that includes ESIIDs/UIDESIIDs with no more than 1000 records. • Data Requests are queried against ERCOTs Lodestar (Data Aggregation & Settlement system) ODS environment. • The turnaround for these Data Requests will be less than 3 business days. Market Data Transparency

15. Inoperability testing • ERCOT is currently in the process of planning for a point-to-point market test. • ERCOT is working to provide Market Participants the opportunity to perform Web Services connectivity testing by scheduling to test in a CERT environment starting Q1 2007. • This test will only test for a success/fail acknowledgement response on service request. • This will ensure that Market Participants are able to connect to ERCOT point-to-point and ERCOT is able to read the automated Web Service request.  This test will not provide payload data to the request. • Once more details are available, ERCOT will communicate this information through the Data Extract Working Group and Market notices. Market Data Transparency

16. Digital certificates • All Market Participants will be required to have a Digital Certificate to access the Data Requests. • You will be prompted to select your Digital Certificate when you enter TML. • You can use the same Digital Certificate for all TML services (for example MarketTrak). • To request a Digital Certificate you must contact your User Security Administrator (USA). Market Data Transparency

17. Future of Web Services • Data Extraction will remain a vital part of information services between ERCOT and the Market for the foreseeable future. • ERCOT will continue to work with the Market to create and implement more dynamic data requests as needs are identified. Methods of generation, formats, and delivery capabilities will evolve over time. • ERCOT continues to strive to create an efficient and effective environment for • Transparency in generation • Flexibility in format and delivery Market Data Transparency

18. Future of Web Service cont. • ERCOT will continue to utilize the DEWG to identify Market needs in the instance that extracts are not utilized for their original intent. • i.e. The Siebel Service Order Extract (SSOE) from PR_50059. As the usage of this extract varies out of the original intent, ERCOT hope to create dynamic ad-hoc queries for the information needed. • ERCOT is also implementing a Web Service with the transition to a Nodal environment. • ERCOT continues to monitor future projects and internal efforts to streamline extract changes with Web Services. • i.e. Load Counts and Volumes Reports which have low usage metrics but the need for certain pieces of data. Market Data Transparency

19. Data formats and payload size • Working to create a highly flexible formatting capability through the use of XML • XSL may be applied to XML at any time or place • Internal to ERCOT (set delivery format) • External to ERCOT (based on the customer’s need) • Formats • Existing extracts will remain available in CSV • Future formats will be decided on, as needed, with a push to generate as much as possible in XML • Sizing • REST delivery • Small, individual transactions obtained and navigated, based on domain • Batch delivery • Still reviewing what size limitations we have • Current opinion is to handle 50GB • Based on generation demands and persistency Market Data Transparency

20. Where we are • Current Status • Integration Testing (ITEST) in progress • Market Business & Technical Training scheduled for Friday, 11/10/2006 • Extract Project Information Postings • Find draft versions of the following documents: User Guide, WSDL, Technical Specification, and Web Services 101 documentation at http://www.ercot.com/services/comm/projects/current/50024/index.html • Market comments received from 1 MP; changes to be incorporated in next version • Market notice will be sent when ERCOT posts any updates to the draft documentation • Market Testing Strategy • Planning for a point-to-point market test still a work in progress. ERCOT working through the details to ensure that the testing process is well-defined and environment hardware available/in place to support this type of testing • ERCOT is working to provide MPs opportunity to perform Web Services connectivity testing by scheduling to test in CERT environment starting Q1 2007 • This test will only test for a success/fail acknowledgement response on service request. This will ensure that MPs are able to connect to ERCOT point-to-point and ERCOT is able to read the automated Web Service request • This test will not provide payload data to the request Market Data Transparency

21. Project Timeline December January February October November September 12/10 Complete Production Stabilization Market Go Live PR 50024 11/10 PR 50024 Technical & Business Training Session by ERCOT 12/2 EIS Production Migration PR 50024 10/9 ITEST Begins for 12/2/06 release PR 50024 11/10 PR 50024 Post updated User Documentation 11/27 PR 50024 Post final User Documentation PR 50024 Production Stabilization begins Market Data Transparency

22. Questions? Market Data Transparency