eds 1 early delivery systems testing preparation webex meeting jonathan pulcini - eds 1 john webb -...
TRANSCRIPT
EDS 1Early Delivery Systems
Testing Preparation WebEx MeetingJonathan Pulcini - EDS 1John Webb - EDS 1Ken Kasparian - EDS 3Bill Blevins - EMSFrank Kendall - EMS May 16, 2007
2EDS 1 – Release 2May 2007
Page 2EDS 1 – Early Delivery Systems
Agenda9:30 -10:00 am• EDS 1 Point Verification Process – Jonathan Pulcini
– Pre-Verification Activities – Verification Activities – Post-Verification Activities – Q&A
10:00 – 10:30am• QSE Nodal Point Verification – John Webb and Ken Kasparian
– Inbound Testing Schedule (EDS 1 / EDS 3) – Outbound Testing Schedule (EDS 1 / EDS 3) – Q&A
10:30 – 12:00 noon• ICCP Handbook – Bill Blevins and Frank Kendall
– Overview of sections – Specific review of recent updates – Q & A
3EDS 1 – Release 2May 2007
Page 3EDS 1 – Early Delivery Systems
EDS 1 Point Verification ProcessJonathan Pulcini
4EDS 1 – Release 2May 2007
Page 4EDS 1 – Early Delivery Systems
Point to Point Verification Testing - Scheduling– Testing Timeline is June 1st – Sept 30th
– EDS1 is scheduling with MPs currently for all time slots– Contact Jonathan Pulcini at [email protected] to schedule testing
5EDS 1 – Release 2May 2007
Page 5EDS 1 Testing Timeline
June Initial TSP and QSE Testing: confirmed
ONCOR ELECTRIC DELIVERY COMPANY,
CENTERPOINT ENERGY HOUSTON ELECTRIC LLC AND NRG TEXAS LP
July QSE and TSP Testing:
1st two weeks are confirmed
ONCOR ELECTRIC DELIVERY COMPANY, EXELON, APX (need list of sub QSEs), RELIANT
Availability remains for weeks of 7/16-720, 7/23-727
August QSE and TSP Testing:
AUSTIN ENERGY (TSP), CPS (TSP)
Availability remains for most of month
September QSE and TSP Testing:
BRAZOS ELECTRIC COMPANY (QSE/TSP)
Availability remains for most of month
6EDS 1 – Release 2May 2007
Page 6Testing Preparation – Confirming Schedule
By May 30th
– Confirm testing schedule with ERCOT for each MP.– MP must confirm number of testing resources available during
scheduled time slot.– For any other questions or issues that need to be addressed,
ERCOT will schedule a call with the MP as needed.– POC for EDS 1 Testing - Contact Jonathan Pulcini at
[email protected] to schedule testing.
7EDS 1 – Release 2May 2007
Page 7Testing Preparation – Pre-Testing Activities
Four Weeks Prior to Testing– ERCOT sends the Market Participant (MP) the AIEF form to
complete.– The MP emails the ICCP team a completed AIEF form to Steve
White at [email protected].– ERCOT sends the MP an ICCP Change Request Form pre-
populated with existing Zonal ICCP points.– ERCOT completes all network requests and verifies network
connectivity with the MP.
Note: these steps have already been completed for CenterPoint Energy
8EDS 1 – Release 2May 2007
Page 8Testing Preparation – Pre-Testing Activities
Three Weeks Prior to Testing– MP submits the ICCP Service Request:
• link http://nodal.ercot.com/readiness/eds1/documents/index.html
• as a Service Request (SR) through the Texas Market Link (TML)
• with all new ICCP points using the pre-populated service request form sent by ERCOT the previous week.
Note: ERCOT requests that MPs submit SRs to TML early in the week to give ERCOT time to review the list and load changes into their Wednesday database batch load
– MP sends:• detailed schedule (list of stations/resources to test each day)
• number of resources available
• testing contacts (name, phone, email)
– ERCOT loads existing SCADA points into EMS database as part of the weekly Wednesday batch load.
9EDS 1 – Release 2May 2007
Page 9Testing Preparation – Pre-Testing Activities
Two Weeks Prior to Testing– ERCOT loads new ICCP data points for the MP into ICCP test
database.– EDS 1 testing team loads ICCP testing data points into EDS 1
testing database.– ERCOT generates and sends test checklists to the MP for
verification.– MP sends ERCOT one line diagrams (if available) for all
stations/resources that will be tested.
10EDS 1 – Release 2May 2007
Page 10Testing Preparation – Pre-Testing Activities
One Week Prior to Testing– ERCOT re-confirms testing schedule with the MP.– ERCOT updates testing checklists and resends to the MP.– ERCOT conducts a pre-test with one MP station/resource
scheduled for testing the first week.
Note: Testing will consist of verifying status changes on a unit, reviewing randomly selected analog points, and manually changes some points. The MP must have at least one resource available to conduct pre-testing.
11EDS 1 – Release 2May 2007
Page 11Testing Preparation – Testing Activities
P2P Testing– ERCOT records the MP operator name, contact information, and
start time of the test on each test checklist.– ERCOT cross-verifies with the MP all analog point values and
quality codes on both ends.– The MP changes values of selected analog points on their side
and ERCOT verifies changes in value, quality code, and update time at ERCOT.
– The MP toggles status of each status point. ERCOT verifies status change, change in quality code and time taken for update on tabular displays.
12EDS 1 – Release 2May 2007
Page 12Testing Preparation – Testing Activities
Immediately Following Test– ERCOT logs, categorizes, and prioritizes all the identified
problems. – ERCOT sends an electronically signed copy of the test
results to the MP through email.– MP emails confirmation and agreement of the ERCOT
electronically signed copy to [email protected]– ERCOT provides a weekly status on testing results to track
progress at:• http://nodal.ercot.com - Readiness Center tab, Key
Documents• EDS 1 Weekly Status Report mmddyyyy.doc
13EDS 1 – Release 2May 2007
Page 13Testing Preparation – Testing Activities
EDS 1 Weekly Status Report - example
14EDS 1 – Release 2May 2007
Page 14Testing Preparation – Post-Testing Activities
Week After Testing– ERCOT updates central EDS 1 testing database with test results. – ERCOT updates issue list database based on the issues
identified and assigns them either to ICCP analysts or network modeling teams.
– ERCOT ICCP/Modeling teams work with the MPs to resolve problems.
– EDS 1 team re-verifies the issues at appropriate time and updates the databases.
15EDS 1 – Release 2May 2007
Page 15Questions?
• Point to Point Scheduling
• Point to Point Testing Activities
16EDS 1 – Release 2May 2007
Page 16For more information . . .
• Visit Texas Nodal Website: http://nodal.ercot.com
• Subscribe to biweekly newsletter: http://lists.ercot.com/cgi-bin/majordomo. Select TexasNodalNews
• E-mail questions, comments or feedback to the Nodal Transition Readiness Center at [email protected] or call (512) 248-3900 to speak with a representative
• Contact your account manager
17EDS 1 – Release 2May 2007
Page 17EDS 1 – Early Delivery Systems
QSE Nodal Point VerificationJohn Webb and Ken Kasparian
18EDS 1 – Release 2May 2007
Page 18Nodal QSE SCED / LFC Point Verification Plan
Background– Each QSE will add approximately 30 new SCED / LFC ICCP
points per Resource (Unit and Load)– New points are defined in the ICCP Handbook in tables 20 and
26-31
EDS 1– Scope
• Load new and existing points into the Nodal ICCP database• Verify ICCP connectivity, point mapping, scan rates and
quality code values between QSEs and ERCOT– Inbound to ERCOT
• QSE Operator manually enters / toggles values for ERCOT Operator to verify
– Outbound to QSEs• ERCOT Operator manually enters / toggles values for QSE
Operator to verify
19EDS 1 – Release 2May 2007
Page 19Nodal QSE SCED / LFC Point Verification Plan
EDS 3– Scope
• Trial Operation of Security Constrained Economic Dispatch (SCED)
• Attain Reasonable LMPs & Begin Six Month LMP Posting• Trial Operation of Load Frequency Control (LFC)
– Inbound to ERCOT• Real-Time ICCP point data required for SCED / LFC
– Outbound to QSEs• EDS 3 SCED / LFC ICCP point data
20EDS 1 – Release 2May 2007
Page 20
Step 1(Jun – Sep 07)
Step 2(Aug – Oct 07)
Step 3(Oct – Dec 07)
ICCP Validation• Point to Point Checkout• Configure New ICCP Data
Registration Data Collection• Validate Existing Data• Collect New Registration Data
Web Services• WS Interface Specifications• Development Sandbox
SCED ICCP Input• Connect new ICCP data sources (EMS, Field Telemetry, …)• Validate new MP ICCP telemetry is available for SCED testing
Registration Data• Upload New Registration Data for Nodal testing• Complete Registration Data Integration
Web Services• WS Backend Integration• MMS Validation Rule Testing (Early EDS)
SCED Execution• Nodal Registration Data• Static ICCP data inputs to validate initial stability• Migrate to Real-Time ICCP data inputs for SCED testing• Reasonable LMP Attainment
SCED ICCP Output• Complete Integration with EMS system• Distribute SCED outputs via ICCP
Web Service Output• Distribute SCED output via Web Services
Step 4(Jan – Jun 08)
LMP Posting• Post LMPs for 6 months as required by the Nodal Transition Plan• Utilize Real-Time ICCP data• Distribute SCED outputs via Web Services & ICCP
EDS 3 - Data Preparation for SCED 6 Month LMP Posting
21EDS 1 – Release 2May 2007
Page 21Questions?
• QSE Nodal Point Verification
22EDS 1 – Release 2May 2007
Page 22EDS 1 – Early Delivery Systems
ICCP HandbookBill Blevins and Frank Kendall
23EDS 1 – Release 2May 2007
Page 23ICCP Handbook Changes Summary
• This ERCOT Nodal ICCP Communication Handbook Version 0.20 is a major revision from the previous Version 0.11. Changes have occurred in every section and nearly every paragraph.
• The document has also been organized so that material is easier to find, easier to use as a reference document, and to improve comprehension.
24EDS 1 – Release 2May 2007
Page 24ICCP Handbook Change Summary Details
• All comments from ERCOT internal review, TPTF, and other Market Participants have been processed.
• The AIEF has been modified and moved to Appendix A. • There is now only one version of the AIEF regardless of Market
Participant type.• An explanation of the ICCP Object Naming conventions and the
purpose of the naming convention tables versus the data exchange tables has been added (Section 1.4).
• The ICCP Object Naming convention tables have been moved so that they are adjacent to the data exchange tables they support.
• The ICCP Object Naming conventions have been changed to make constructing an object name easier.
• The glossary has been expanded (Section 1.6).
25EDS 1 – Release 2May 2007
Page 25ICCP Handbook Change Summary Details
• Section 2 has been improved and combined with the section on implementation procedures previously duplicated in the QSE and TSP sections.
• The description of the high data availability architecture has been given its own chapter level section (Section 3) and greatly expanded to discuss various Market Participant configurations, connections, and operation in the new architecture.
• Domain naming conventions have been changed to support the high data availability architecture, and the section has been reorganized for improved clarity (Section 4.3).
• Resource status codes have been defined and included in the Handbook (Section 4.5.2).
• Other improvements in clarity have been made throughout the document.
26EDS 1 – Release 2May 2007
Page 26ICCP Handbook Next steps
• Address TBD issues.• Post version 0.21 for TPTF approval.• May 22nd review comments and resolution with TPTF.• Obtain vote from TPTF for approval.• Place ICCP handbook under document control.• Deliver to IRT for EDS P-P checkouts.• Distribute to Market Participants.
27EDS 1 – Release 2May 2007
Page 27Questions?
• ICCP Handbook