EDS 1Early Delivery Systems

EDS 1 TPTF UpdateJonathan Pulcini - Project ManagerAugust 28, 2007

2EDS 1 – Release 2August 2007

Page 2EDS 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

3EDS 1 – Release 2August 2007

Page 3EDS 1 – PtP Testing Update

Points Tested 50,150 of 67,908

74 % Complete

Points Remaining 17,758 26 % Remaining

MPs Tested 23 of 39 58 % Complete

QSEs Tested 14 of 23 60 % Complete

TSPs Tested 9 of 16 56 % Complete

Remaining Points for Aug 8,000 11 % Remaining

Remaining Points for Sept 9,758 14 % Remaining

Projected Completion for Aug

58,150 pts(27 of 39 MPs)

85 % Complete

(69 % MPs Tested)

Projected Completion for Sept

67,873 pts(38 of 39 MPs)

99 % Complete(remaining 1 % will be tested in early Oct)

4EDS 1 – Release 2August 2007

Page 4EDS 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).

5EDS 1 – Release 2August 2007

Page 5EDS 1 – PtP Issue Resolution Process (Short Term)

1. Each issue is entered into an issue database in a Pending status.

2. MPs are provided with an issue list after their PtP testing is completed.

3. Each issue is Assigned to ERCOT and/or the MP and categorized as a Modeling or Telemetry issue type.

4. Each issue is investigated and resolved accordingly; some issues can require a Service Request be submitted by the MP to complete.

5. Each issue is re-tested to ensure correction was made before it is migrated to Production.

6. Once an issue has been resolved, tested, and migrated to Production, it is Closed.

7. The MP is provided an updated Issue List on a periodic basis to continue to address remaining issues.

6EDS 1 – Release 2August 2007

Page 6EDS 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

p2pICCP

MPsIssue Mgmt

EMS

ERCOT

EDW

7EDS 1 – Release 2August 2007

Page 7EDS 1 – Issue Resolution Process (Long Term)

SCADA / NOM Data Issues ManagementBasic 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

8EDS 1 – Release 2August 2007

Page 8EDS 1 – Testing Issues Report

Total PtP Issues 3,658 E-NFT QC issues will be addressed as part of vendor fix implemented in Sept.

Closed 1,533 41 % of issues (not including E-NFT)

Open 2,125 58 % of issues

Modeling 478 13 % of open issues

MP 0 0 % of modeling issues

ERCOT 478 100 % of modeling issues

Telemetry 1,647 45 % of open issues

ERCOT 1,398 81 % of telemetry issues

MP 249 18 % of telemetry issues

9EDS 1 – Release 2August 2007

Page 9EDS 1 – Testing Issues Report

Status Type Issue Count Description

Pending 615 Issues have been entered into the tracking DB; waiting to be assigned

Assigned 1,496 Issues have been assigned to ERCOT or a MP to resolve.

To Test 13 Issues are awaiting testing.

To Implement 1 Issues have been resolved and are awaiting migration to Production.

Future 0 Issues are awaiting future implementation.

Closed 1,533 Issues have been resolved and tested in Production.

TOTAL 3,658

10EDS 1 – Release 2August 2007

Page 10EDS 1 – Testing Deliverables

# Artifact Initiator Distribution

1 EDS 1 Alarm Processing Requirements ERCOT Public

2 Service Request Process and Procedure ERCOT Public

3 ICCP Service Request – Initial Request MP ERCOT Internal

4 ICCP Service Request - Initial Approval ERCOT MP Specific

5 ICCP Database ERCOT ERCOT Internal

6 EDS 1 PtP Testing Results Database ERCOT ERCOT Internal

7 Completed PtP Station Checklists ERCOT MP Specific

8 EDS 1 Results Dashboard (provided weekly)

ERCOT Public

9 PtP Issue List (Summary and Detail) ERCOT MP Specific

10 ICCP Service Request – Updates MP ERCOT Internal

11 ICCP Service Request - Update Approval ERCOT MP Specific

12 EDS 1 SharePoint Site for Documentation ERCOT ERCOT Internal

11EDS 1 – Release 2August 2007

Page 11EDS 1 – Early Delivery Systems

Early Delivery Systems 1 – Process and Artifact OverviewE

RC

OT

O

per

atio

ns

Mar

ket

Par

tici

pan

tsE

RC

OT

ICC

P

Su

pp

ort

ED

S 1

Summary Results

Dashboard

* Beta Results* Alarm Results* ICCP Results* PtP Schedule* PtP Metrics* PtP Results

* Request # * Description

Service Request

ICCP Points

ICCP Database

Initial Load

SharePoint

PtP Checklist

PtP Checklist

PtP Completed

x

PtP Completed

x

no

dal

.erc

ot.

co

m

Service Request Approval

Managed

Failed Point Procedure

Managed

* Request # * Description

Service Request

ICCP Points

PtP Issues

Resolve PtP Issues

Analysis

ICCP Database

Update

Service Request Approval

Managed

3

4 6

7

8

9

10

11

Service Request

Procedure

2

5

Requirements and Process

Alarm Process

Alarm Configuration

and Test

Verification

1

12EDS 1 – Release 2August 2007

Page 12EDS 1 – Readiness Metrics

For a MP to be considered ready and marked as such inthe Readiness Metrics for EDS 1, they must have thefollowing completed by the end of Release 2:

1. PtP Testing has been completed.• Complete Telemetry check and topology review.

2. Failover testing has been completed.• Complete association failover test – ICCP link failover to

alternate server.3. 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%).

13EDS 1 – Release 2August 2007

Page 13EDS 2 – Early Delivery Systems

Entry Criteria Status Comment

• MPs have submitted all ICCP points for NODAL.

75% Some MPs are in the process of PtP testing.

• MPs have all scheduled for PtP testing.99% One MP must complete testing in early

Oct. (ETA – by Oct 15)

• MPs have all set up ICCP associations/links with ERCOT.

50% Some MPs do not have secondary associations set up yet for failover testing.

MP Readiness Status Comment

• MPs have completed PtP testing for all points submitted.

58% There are 16 of 39 MPs left to test by Sept 30th.

• MPs have completed failover testing.0% EDS 1 team is currently working to

schedule MPs for testing starting this week.

• ERCOT/MPs have addressed all logged issues from PtP testing down to an rate of 3% or less by Sept. 30th.

20% ERCOT is working with the MPs to resolve all telemetry and modeling issues.

EDS 1 Release 2 – Entry Criteria Status

14EDS 1 – Release 2August 2007

Page 14EDS 2 – Early Delivery Systems

Exit Criteria Status

• MPs have completed PtP checkout and topology review for all submitted Nodal points.

74%

• Each MP who has completed PtP checkout has been provided with summary of results and a detailed issues list with assigned issues to resolve.

71%

• ERCOT has completed failover testing with each MP. 0%

• ERCOT has completed Alarm Processing configuration and testing. 50%

• ERCOT has completed all PtP process documentation to support ongoing telemetry checkout process for new construction and future changes to telemetry.

75%

EDS 1 Release 2 – Exit Criteria Status

15EDS 1 – Release 2August 2007

Page 15EDS 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.

16EDS 1 – Release 2August 2007

Page 16EDS 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.

17EDS 1 – Release 2August 2007

Page 17Questions?

• Testing

• Issue Resolution Process

• Deliverables

• Metrics

• Schedule