1. Nodal EDW Project Reporting Requirements & Conceptual Design Update EDW Project Team July 23, 2007

2. 2 EIS Training 05/17/2007 Contents Section 8 Performance Monitoring & Compliance and Requirements EDW Data Archival and Reporting Requirements EDW Conceptual System Design concerns

3. 3 EIS Training 05/17/2007 Section 8 Requirements Definition and delivery of Section 8 requirements to TPTF to be conducted by ERCOT business. Protocol Section 8 report definitions are a part of compliance modeling which must be completely addressed by the TAC approved monitoring program. ERCOT has formed a new team to address the requirements for section 8 and compliance in general. This team will report their process and timelines to TPTF. The Nodal EDW project will change the context of its requirements to focus on the data archival and reporting requirements. The EDW project will provide the reporting services for compliance items in the same manner with other reporting requirements from Nodal Project teams.

4. 4 EIS Training 05/17/2007 Data Archival and Reporting Requirements During the course of trying to get approval of our EDW Compliance Requirements (Section 8) the EDW Project has heard the following comments/ questions from TPTF: 1.We need to understand what data sets are going to be replicated in the EIS systems. 2.We would like to see a list of all the reports and extracts expected. 3.We would like to see that the EDW team has a contracted obligation from the other nodal teams to supply the data needed for archival and reporting. 4.We need to see more specifics for each report not just a report name. To address these questions and provide data archival and reporting requirements to TPTF in a more timely fashion, the EDW Project will deliver the EDW “Data Archival and Reporting Requirements” to TPTF for approval.

5. 5 EIS Training 05/17/2007 Data Archival and Reporting Requirements The “Data Archival and Reporting Requirements” document will describe data archival to the following level of detail: Source System Replication Requirements (reflects business/Nodal Project agreement for the delivery of replication requirements) –Data replication process –Data set descriptions –Replication SLAs –Replication timelines

6. 6 EIS Training 05/17/2007 Data Archival and Reporting Requirements New Market Reports –Report Name –Report Data Set –Data Source –Generating System –Generating Frequency (timeliness SLAs) –Archival System –Format(s) –Display or Delivery System –ERCOT Report owner –Intended Recipients –Report Definition New Market Extracts –Extract Name –Extract Data Set –Data Source –Generating System –Generating Frequency (timeliness SLAs) –Archival System –Format(s) –Display or Delivery System –ERCOT Extract owner –Intended Recipients –Extract Definition New Market Web Services –Web Service name –Web Service possible data set –Data Source –Generating System –Archival System –Format –Display or Delivery System –ERCOT Web Service owner –Intended Recipient –Web Service Definition Market Extracts and Reports transitioning from Zonal –Extract/Report Name –Extract/Report Data Set –Data Source –Generating System –Generating Frequency (timeliness SLAs) –Archival System –Format(s) –Display or Delivery System –ERCOT Extract/Report owner –Intended Recipients –Extract/Report cut over schedule –Extract/Report Definition The “Data Archival and Reporting Requirements” document will describe data reporting to the following level of detail: Market Data Products (reflects business/Nodal Project agreement for the deilvery of reporting requirements)

7. 7 EIS Training 05/17/2007 Data Archival and Reporting Requirements To produce these requirements the EDW Project has contracted with each other Nodal Delivery team and their Business SMEs for the content of each report expected for nodal operations. The Nodal EDW Business Agreement matrix was created to advise each nodal project and SME of the operational area they have responsibility for to the EDW Project. This matrix contains the following data elements for each operational area: EDW Project Functional Area EDW Sub Project Area Early Delivery System Inclusion Signed Requirements Due Date EDW Resource Responsible for Delivery Business Owner/ Responsible Person For Content Definition/Req. Input Responsible Business Mgr/Dir Nodal Project PM Responsible for Business Input

8. 8 EIS Training 05/17/2007 Conceptual System Design for EDW Project Some concerns have been raised surrounding the EDW Project CSD with reference to the use of EIS systems for delivery of EDW Products. The Nodal EDW Project has written a Conceptual System Design based upon the following conditions: 1.The EIS Data systems for archival of source data, market extracts, and reporting will be leveraged to deliver EDW Products for the Nodal Market. 2.Zonal and Nodal Data will be archived in separate schemas within the same Operation Data Store data base. 3.Some Zonal and Nodal systems will run in a parallel mode for a period of time after the Go-Live of the nodal market. 4.The total volume of nodal data processed into the EIS systems will be at least 2 ½ times that of the zonal data. 5.Addressing performance issues and optimization of EIS data operations will be a required on-going task of the EDW Project.

9. 9 EIS Training 05/17/2007 Conceptual System Design for EDW Project Some concerns have been raised surrounding the EDW Project CSD with reference to the use of EIS systems for delivery of EDW Products. The Nodal EDW Project will incorporate an initial section in the Conceptual System Design to address the following concerns: –The causes of recent zonal incidents with data deliver out of the EIS systems. –The remedy plan that EIS is currently executing to address these issues. –The expected changes to the EIS systems to address specific areas of change for nodal: Data replication volume increase Reporting volume increase Parallel operations (Zonal/Nodal) Performance Contingency Measures

10. 10 EIS Training 05/17/2007 Summary Performance & Compliance concerns from the TPTF would be addressed by the new Compliance Definition Team. The Nodal project teams with their associated business SMEs would be required to provide the EDW team with their data retention and reporting requirements. The EDW project would then deliver a consolidated “EDW Data Archival and Reporting Requirements” to the TPTF. The EDW CSD will be expanded to address existing conditions and the changes to be made to EIS systems to address each one. Questions?