eds 1 early delivery systems eds 1 update jonathan pulcini - project manager august 13, 2007
DESCRIPTION
Page 3 3 EDS 1 – Release 2 August 2007 EDS 1 – PtP Testing Update Points Tested46,802 of 68, % Complete Points Remaining21,66532 % Remaining MPs Tested20 of 3951 % Complete QSEs Tested13 of 2356 % Complete TSPs Tested7 of 1643 % Complete Remaining Points for Aug12,90818 % Remaining Remaining Points for Sept8,75512 % Remaining Projected Completion for Aug 59,710 pts (29 of 39 MPs) 87 % Complete (74 % MPs Tested) Projected Completion for Sept 67,873 pts (38 of 39 MPs) 99 % Complete (remaining 1 % will be tested in early Oct)TRANSCRIPT
EDS 1Early Delivery Systems
EDS 1 Update Jonathan Pulcini - Project ManagerAugust 13, 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 46,802 of 68,476
68 % Complete
Points Remaining 21,665 32 % Remaining
MPs Tested 20 of 39 51 % Complete
QSEs Tested 13 of 23 56 % Complete
TSPs Tested 7 of 16 43 % Complete
Remaining Points for Aug 12,908 18 % Remaining
Remaining Points for Sept 8,755 12 % Remaining
Projected Completion for Aug
59,710 pts(29 of 39 MPs)
87 % Complete(74 % 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)
• 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 12,877 10,133 are E-NFT QC issues.2,744 are all other types of issues.
Modeling 267 2 % of total issues
Telemetry 12,610 98 % of total issues
ERCOT 10,532 81 % of total issues
MP 2,345 18 % of total issues
Open 12,359 95 % of total issues
Closed 518 4 % of total issues complete.18 % of all other types of issues complete (not including E-NFT).
9EDS 1 – Release 2August 2007
Page 9EDS 1 – Testing Issues Report
Status Type Issue Count Description
Pending 377 Issues have been entered into the tracking DB; waiting to be assigned
Assigned 11,95010,133 (E-NFT)
Issues have been assigned to ERCOT or the MP to resolve.
In Progress 9 Issues are being worked on by the modeling or telemetry teams.
To Test 20 Issues are awaiting testing.To Implement 3 Issues have been addressed and are
awaiting migration to Production.Closed 518 Issues have been resolved and
tested in Production.TOTAL 12,877
10EDS 1 – Release 2August 2007
Page 10EDS 1 – Testing Deliverables
# Artifact Initiator Distribution1 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 OverviewER
CO
T O
pera
tions
Mar
ket
Part
icip
ants
ERC
OT
ICC
P Su
ppor
tED
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
noda
l.erc
ot.
com
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.• Complete disaster recovery test – physical failover.
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 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.
14EDS 1 – Release 2August 2007
Page 14EDS 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.
15EDS 1 – Release 2August 2007
Page 15Questions?
• Testing
• Issue Resolution Process
• Deliverables
• Metrics
• Schedule