eds 4 release 9.1 dam/ruc/sasm

23
http://nodal.ercot.com 1 Lead from the front Texas Nodal EDS 4 Release 9.1 DAM/RUC/SASM 4.9.1 Market Call February 15, 2008

Upload: ova

Post on 07-Jan-2016

24 views

Category:

Documents


0 download

DESCRIPTION

EDS 4 Release 9.1 DAM/RUC/SASM. 4.9.1 Market Call. February 15, 2008. ERCOT Anti-Trust Admonition. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 1Lead from the front

Texas Nodal

EDS 4 Release 9.1DAM/RUC/SASM

4.9.1 Market Call

February 15, 2008

Page 2: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 2Lead from the front

Texas Nodal

ERCOT Anti-Trust Admonition

ERCOT strictly prohibits Market Participants and their employees who are participating in ERCOT activities from using their participation in ERCOT activities as a forum for engaging in practices or communications that violate the antitrust laws. The ERCOT Board has approved guidelines for members of ERCOT Committees, Subcommittees and Working Groups to be reviewed and followed by each Market Participant attending ERCOT meetings. If you have not received a copy of these Guidelines, copies are available at the Client Relations desk. Please remember your ongoing obligation to comply with all applicable laws, including the antitrust laws.

Page 3: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 3Lead from the front

Texas Nodal

Agenda

• DAM/RUC EDS 4.9.1 – QSEs not signed up for testing – Network Changes– Current Issues– DAM Awards Notifications– Master Schedule Update– Dashboard Update– Q&A and Roll Call

• Appendix– Connectivity and Digital Certificate information– Links to Key Documentation – Metrics– Test Case Summary– Summary of QSE activity needed– Data Preparation

Page 4: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 4Lead from the front

Texas Nodal

EDS 4 Release 9

Alcoa Power MarketingAmbridge Energy AquilaBear EnergyBrilliant EnergyCargill Power MarketsCitadel Energy ProductsClearview Electric ECONnergyElectric Now Glacial Energy J AronKansas City Power and LightKeystone Energy Partners Lehman Brothers Commodity

Services

Merrill Lynch CommoditiesMxEnergy Electric Inc QSENational Power Company Sitara Energy Spark Energy Texas Retail Energy Texas Star Energy Texpo Power Urban Energy Source Viasyn WCW International

QSEs that have not signed up for a testing window for EDS4 (as of COB 2/14/08)

Page 5: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 5Lead from the front

Texas Nodal

Forthcoming Network Changes

Update: Network Changes / site to site fail-over testing

(please communicate to your network / firewall teams)

• Test to be conducted mid / late March

• All QSEs need to have network changes in place no later than 3/14

• The changes should enable receiving / sending data to / from::

» 66.128.16.0/24

» 66.128.17.0/24

» 66.128.18.0/24

• Reminder: required ports do not change (443/80)

• Reminder: required protocols do not change (http/https)

Page 6: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 6Lead from the front

Texas Nodal

Update on EDS 4 Environment- Current Issues

• NOTE: Patch will migrate Tuesday afternoon

– The EDS environment will be undergoing an outage for this at 3:00 PM on 2/19 returning to service at 12:00 PM (noon) on 2/20

– This will contain a patch for MMS and Web Services; however, there will not be a patch for Market Manager (MMS UI) in this migration

• Will communicate the target date for migration of the Market Manager patch through a market notice

Page 7: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 7Lead from the front

Texas Nodal

Web Services Issues

Update: Defect clarification regarding short mRID– After the patch migrates 2/19, short mRID will work for all

transactions except:• CRR Offer query• PTP Obligation Bid query• Energy Bid query• Energy Only Offer query

Update: Payload size limitation• The expansion in max size has uncovered performance issues (timeouts on

response) in test• ERCOT is working with vendor to resolve• We do not believe this will be resolved by the migration date • QSEs should continue to split their submissions until further notice

Page 8: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 8Lead from the front

Texas Nodal

Web Services Issues

Error notifications• The Reply Code ERCOT sends can be OK, ERROR or FATAL. The

External Interfaces Specification document only mentioned a Reply Code of either OK or ERROR.

• The EIP team will make the corresponding change in the next version of the document.

• Current list of issues to be posted by end-of-day today (2/15/08)

Page 9: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 9Lead from the front

Texas Nodal

DAM Awards

DAM awards notification availability in the nodal Sandbox• There is a scheduled job running in Sandbox that sends out

notifications once a day (around 11:53 AM CST)• To receive them, you must have your listener configured in the

Sandbox environment – if you need it configured, send us an email with your URL (send to [email protected])

• NOTE: These notifications are generated from static files (pre-formed xmls)

– AwardedCRR– AwardedAS– AwardedEnergyBid– AwardedEnergyOffer– AwardedEnergyOnlyOffer– AwardedPTPObligation– ConfirmedTrades– UnConfirmedTrades– OutageSet– ASObligations– StartupShutdownInstructions

Page 10: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 10Lead from the front

Texas Nodal

DAM/RUC 4.9.1 Tracking: Master Schedule for Next Week

Page 11: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 11Lead from the front

Texas Nodal

DAM/RUC 4.9.1 Tracking: Dashboard

• To view the most updated copy refer to the readiness center at:http://nodal.ercot.com/readiness/eds4/documents/index.html Under Weekly Status – new posting every Friday night

Page 12: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 12Lead from the front

Texas Nodal

Q&A / Open Forum

Roll-Call

Page 13: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 13Lead from the front

Texas Nodal

-Current Issues (Web Services)-Connectivity and Digital Certificate information-Links to Key Documentation -Metrics-Test Case Summary-How to log issues-Data preparation

APPENDICES

Page 14: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 14Lead from the front

Texas Nodal

Update on EDS 4 Environment - Current Issues

• WebServices Known Issues/Limitations– Issue with Credit Validation

• DAM Bids/Offers being rejected, workaround by submitting 2-days out– Query using short mRID is not available for:

• “PTP Obligation” / “DAM Energy Only Offer” / “Energy Bid” / “CRR Offer” / “AS Offer”

– Negative test for Energy Bid not working (submission of curve <1MW)• Will pass QSE without this test

– DC Tie Schedule• NERC tag data not yet set up to be used for testing

– PtP Obligation Bids• <crrAccountHolderId/> is REQUIRED (different from M2M/API spec)• Set crrAccountHolderId = TSTQSE

Page 15: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 15Lead from the front

Texas Nodal

APPENDIX- DAM/RUC 4.9.1 Testing: Basic Communications Test (“Ping” Test)

• BASIC COMMUICATION TEST

• Prior to this test QSE’s using External Web Services will need to have their network and security teams make the following changes:

– QSE’s Market System must be able to access:https://nodaleds.ercot.com:80/2007-08/Nodal/eEDS/EWS/ NOTE: this SSL URL is on port 80NOTE: this is changed from Release 3.5

– QSE’s must be able to receive messages from 66.128.17.136

– QSE’s must be able to send messages to EDS Environment: 66.128.17.32Sandbox Environment: 66.128.16.84

• QSE’s using MIS User Interface will need to have their network and security teams make the following changes:

– Must be able to access: MIS URL: https://nodaleds.ercot.com/misportal/ NOTE: MMS User Interface will have link from MISNOTE: MIS/MMS UI are on port 443

Page 16: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 16Lead from the front

Texas Nodal

APPENDIX- DAM/RUC 4.9.1 Testing: Digital Certificates

• DIGITAL CERTIFICATES

• 1 digital certificate w/ a Generic Userid (NODALTEST) will be Generated for Each QSE and Sub-QSE

– The MP’s USA does not need to take any action– This is the only certificate that will work in the EDS environment– This certificate will also work in the Nodal Sandbox environment– It will not work in production, MOTE, or any other ERCOT environment– The Digital Certificate will be sent to the MP USA

• Distribution will occur after the QSE signs up for a Testing Window and Just Prior to the Support Call

– (for those requiring the basic communications test, it will be sent prior to that session)

Page 17: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 17Lead from the front

Texas Nodal

APPENDIX- DAM/RUC 4.9.1 Reference: Relevant Documents

EDS 4.9.1 – DAM/RUC/SASM Test Package

http://nodal.ercot.com/readiness/eds4/documents/index.html

Settlement Point Listing http://nodal.ercot.com/readiness/eds4/documents/index.html

QSE Short Name Listing

To post by end-of-day

http://nodal.ercot.com/readiness/eds4/documents/index.html

Dashboard of Metrics and Schedule

http://nodal.ercot.com/readiness/eds4/documents/index.html

EDS Issue Submission Form

http://nodal.ercot.com/readiness/eds4/documents/r9/ercot_eds_issue_submission_form.xls

EIP External Interface Specification

http://nodal.ercot.com/docs/pd/eip/od/misp/eip_external_interfaces_specification_v1_06.zip

Explanation of Market Submissions v0.25

http://nodal.ercot.com/readiness/eds4/documents/index.html

Page 18: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 18Lead from the front

Texas Nodal

APPENDIX- DAM/RUC 4.9.1 Reference: Relevant Documents

ERCOT Nodal Transition Plan

http://nodal.ercot.com/docs/po/pd/ntp/ERCOT_Nodal_Transition_Plan_110305.doc

EDS 4 Approach v1.0 http://nodal.ercot.com/readiness/eds4/documents/index.html

EDS 4 - DAM/RUC/SASM Market Participant Handbook v1.0

http://nodal.ercot.com/readiness/eds4/documents/index.html

Market Management System User Guide

http://nodal.ercot.com/docs/pd/eds/eds4/eds4mmsuidum/eds_4_mms_ui_draft_user_manual_20080128.doc

Page 19: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 19Lead from the front

Texas Nodal

APPENDIX- DAM/RUC 4.9.1 Tracking: Readiness Metrics

• READINESS METRICS:• Sign-Up Testing Window Scheduled

– QSE signs up by 1/4/2008 – Status is GREEN– QSE’s that have not signed up by

• 01/04/08 – Will turn Amber until signed up• 03/15/08 – Will turn red

• MP8 - QSE Ability to Submit Transactions Via MIS– Expected completion date March 15

• MP9 – QSE Ability to Submit Web Service Transactions– Expected completion date March 15

• Execution – MP’s that have met readiness metric M8 or M9 by 3/15/08 are GREEN– MP’s that have attempted readiness metric M8 or M9 by 3/15/08 are AMBER– MP’s that have not yet attempted readiness metric M8 or M9 by 3/15/08 are RED

• MP16 - MP EDS-4 Trials Participation (phase 2)

• ERCOT is calling all QSEs that have not signed up for EDS4

Page 20: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 20Lead from the front

Texas Nodal

Appendix- DAM/RUC 4.9.1 Testing: Support Call Test Cases

Primary QSE Sub-QSE

Create / Query / Update / Cancel (if applicable)

CRR OFFER All Scenarios

NOIE / PCRR Holders Only

Create Only

PTP Obligation All Scenarios Create Only

Three Part Supply Offer All Scenarios

QSE w/ Resources Only

Create Only

Capacity Trade All Scenarios Create Only

Energy Trade All Scenarios Create Only

AS Trade All Scenarios Create Only

DAM Energy-Only Offer All Scenarios Create Only

DAM Energy Bid All Scenarios Create Only

AS Self Arrangement All Scenarios

QSE w/ Load Only

Create Only

AS Offer All Scenarios

QSE w/ Resources Only

Create Only

Self Schedule All Scenarios Create Only

DC Tie Schedule All Scenarios Create Only

Page 21: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 21Lead from the front

Texas Nodal

Appendix- Reminder of support window and issues process

• Issues encountered on the Support Call will have a high priority• Issues encountered during the remainder of the 7 day Test Window

should be reported via the ERCOT EDS Issue Submission Form – Form is located at:

http://nodal.ercot.com/readiness/eds4/documents/index.html – Submit form to [email protected]  – Internal testing will occur in parallel with all EDS activities – MP issues will be logged when submitted

• MP submitted issues will be compared to internal defects and addressed in parallel– When completing the Issue form, provide:

• Web Services: the XML files used • MIS User Interface: Screen Shots and/or error message• Both: The detailed scenario to reproduce the issue

Page 22: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 22Lead from the front

Texas Nodal

Appendix- DAM/RUC 4.9.1 Reference: QSE Activity Summary

• Download and review the EDS 4 Test Package– For API WebServices users only-

• Send sample XML to ERCOT no less than 2 weeks prior to Testing Window• Make Corrections/Modifications (if any) to XMLs that ERCOT provides• Prepare final XML files for Support Call

– For MMS-UI/Market Manager, download the user guide– Support calls are for troubleshooting submissions in real-time

• Read and be familiar with key Documents (references in Appendix)

• Known issues will be posted to the Nodal Readiness Center under EDS 4: – File will be updated by COB 2/1– http://nodal.ercot.com/readiness/eds4/documents/index.html

• When environments upgraded (issues resolved), a Market Notice will be sent

• Send all questions to [email protected]

Page 23: EDS 4 Release 9.1 DAM/RUC/SASM

http://nodal.ercot.com 23Lead from the front

Texas Nodal

Appendix- DAM/RUC 4.9.1 Reference: QSE Data Preparation

Reminder to Download Settlement Points and QSE Short Name List(both files posted on Readiness- http://nodal.ercot.com/readiness/eds4/documents/index.html)

• Both data sets are subject to change

• QSE Short Names used in transactions– Your QSE short name is needed as <source> in XML Header– All QSE short names listed, but may change

• Can use ERCOT test QSE of “TSTQSE” to avoid populating and changing QSE list in your systems

• Settlement Point used as points of business in submission testing– Market Participants revisiting Resource Node SPs– Considering change from Low side to High side– Change would result in many SP name changes