EDS 1 Early Delivery Systems

1. EDS 1Early Delivery Systems EDS 1 TPTF Update Jonathan Pulcini - Project Manager August 28, 2007

2. EDS 1 – Early Delivery Systems Point to Point Verification Testing • PtP Testing Update • PtP Issue Resolution Process • Short Term (for EDS 1) • Long Term (beyond EDS 1) • PtP Issues Report • EDS 1 Testing Deliverables • EDS 1 Testing Metrics • Ongoing Process • Remaining Schedule • Questions EDS 1 – Release 2

3. EDS 1 – PtP Testing Update EDS 1 – Release 2

4. EDS 1 – PtP Testing Update • Currently, the error rate is at 4 % for PtP testing. • All issues represent an mix of both ERCOT and MP issues. • Errors consist of both modeling and telemetry type errors encountered during PtP testing. • Errors are prioritized, categorized, and assigned to either the modeling team or telemetry teams to address as issues in a issues database. • For Non-Field Telemetered point Quality Code errors (category E-NFT) , ERCOT will re-verify selected points of various device types with each MP (up to 10 %) once the ERCOT EMS upgrade is available in Sept. • ERCOT is working with the vendor to deliver a fix for the E-NFT category errors by mid Sept. • ERCOT is targeting to resolve all issues for a rate of 3 % or less for each MP by the end of Release 2 (Sept. 30th). EDS 1 – Release 2

5. EDS 1 – PtP Issue Resolution Process (Short Term) • Each issue is entered into an issue database in a Pending status. • MPs are provided with an issue list after their PtP testing is completed. • Each issue is Assigned to ERCOT and/or the MP and categorized as a Modeling or Telemetry issue type. • Each issue is investigated and resolved accordingly; some issues can require a Service Request be submitted by the MP to complete. • Each issue is re-tested to ensure correction was made before it is migrated to Production. • Once an issue has been resolved, tested, and migrated to Production, it is Closed. • The MP is provided an updated Issue List on a periodic basis to continue to address remaining issues. EDS 1 – Release 2

6. EDS 1 – Issue Resolution Process (Long Term) SCADA / NOM Data Issues Management • Definition • Nodal EMS will provide tools to measure SCADA and SE performance • Performance measurements are based on Telemetry and SE Standards • SCADA not performing to standards will be: • reported using ERCOT Enterprise Data Warehouse functionality • available to ERCOT and to the responsible MP via the MIS portal • resolved jointly between ERCOT Operations Support and the MPs • Conclusion • Operations Support will need a Data Issues Management Tool • Short term to resolve p2p issues • Long term to resolve on-going performance issues ERCOT I C C P p2p Issue Mgmt MPs EMS EDW EDS 1 – Release 2

7. EDS 1 – Issue Resolution Process (Long Term) SCADA / NOM Data Issues Management Basic Tool Requirements • SCADA / NOM issues creation • import issues from EDW or other sources (current PtP issue DB) • Manage a list of ERCOT and MP contacts with contact information • Notify ERCOT and MPs when issues are Assigned, Updated, Closed • Manage and track issues • Pending (new issue) • Assigned (to MP and/or ERCOT) • To Implement (Service Request created and linked) • Closed (issue resolved, verified and closed in Production for both Zonal and Nodal) • Include a Web-based thin client • Include Reporting and Trend Analysis • Provide Secure access • ERCOT has access to all issues • MPs can access only their assigned issues EDS 1 – Release 2

8. EDS 1 – Testing Issues Report EDS 1 – Release 2

9. EDS 1 – Testing Issues Report EDS 1 – Release 2

10. EDS 1 – Testing Deliverables EDS 1 – Release 2

11. EDS 1 – Early Delivery Systems EDS 1 – Release 2

12. EDS 1 – Readiness Metrics For a MP to be considered ready and marked as such in the Readiness Metrics for EDS 1, they must have the following completed by the end of Release 2: • PtP Testing has been completed. • Complete Telemetry check and topology review. • Failover testing has been completed. • Complete association failover test – ICCP link failover to alternate server. • Resolve all issues down to 3% or less for modeling and telemetry for each MP. • Address all priority modeling and telemetry issues. • Includes re-test of selected points categorized as E-NFT quality code issues (up to 10%). EDS 1 – Release 2

13. EDS 2 – Early Delivery Systems EDS 1 Release 2 – Entry Criteria Status EDS 1 – Release 2

14. EDS 2 – Early Delivery Systems EDS 1 Release 2 – Exit Criteria Status EDS 1 – Release 2

15. EDS 1 – Ongoing Process • What will the new process be for telemetry checking beyond EDS 1? • The PtP process established and used for telemetry checking in EDS 1 will be used for all new construction or changes being submitted by a MP in the future. • Each new substation or generation resource will not only include a modeling check but also a PtP telemetry checkout to ensure accuracy and reliability. • Telemetry check will be scheduled as part of a checklist to energize a new station/resource. • Any issues encountered will be logged in current issues DB and resolved by following the existing processes. EDS 1 – Release 2

16. EDS 1 – Remaining Schedule • Complete testing of 99% all remaining points by Sept 30th; 100% by early Oct. • Log all issues and address them accordingly with each MP through the current issue assignment and resolution process. • Complete internal alarm processing and testing. • Complete site failover testing by Sept. 30th for each MP; includes both ICCP association failover (primary to secondary link) and server disaster recovery testing. • Verify with each MP that issues have been resolved to 3 % or less by Sept. 30th. EDS 1 – Release 2

17. Questions? • Testing • Issue Resolution Process • Deliverables • Metrics • Schedule EDS 1 – Release 2