1 / 27

EDS 4 Release 9.2 Outage Scheduler

EDS 4 Release 9.2 Outage Scheduler. Kickoff Meeting. March 27, 2008. Agenda. Outage Scheduler EDS 4.9.2 Overview: Presentation Legend Objectives Audience Outage Scheduler EDS 4.9.2 Timeline Nodal Summary Release Schedule Sandbox Testing Test Cases Sample Activity Timeline

stellah
Télécharger la présentation

EDS 4 Release 9.2 Outage Scheduler

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EDS 4 Release 9.2Outage Scheduler Kickoff Meeting March 27, 2008 http://nodal.ercot.com 1

  2. Agenda • Outage Scheduler EDS 4.9.2 Overview: • Presentation Legend • Objectives • Audience • Outage Scheduler EDS 4.9.2 Timeline • Nodal Summary Release Schedule • Sandbox Testing • Test Cases • Sample Activity Timeline • Testing Windows • Outage Scheduler EDS 4.9.2 Testing • Testing Window • Basic Communications Test • Digital Certificates • Support Calls • Issue Management • Tracking • Master Schedule • Preparation Checklist / Schedule • Dashboard • Reference • QSE Activity Summary • Relevant Documents • Q&A http://nodal.ercot.com 2

  3. Presentation Legend • Note: Throughout this presentation, there are several references to activities required by QSEs with Resources and TSPs on the Web Services and MIS (RUI) • For convenience and clarity, the following will apply: • All activities that apply only to users of the MIS (RUI) will appear in BLUE • All activities that apply only to users of the Web Services will appear in MAROON • Activities that apply to both the RUI and the Web Services will remain in BLACK http://nodal.ercot.com 3

  4. Outage Scheduler EDS 4.9.2: Audience • Contact eds4@ercot.com if: • You should not be on this list <or> You should be on this list but are not QSEs http://nodal.ercot.com 4

  5. Outage Scheduler EDS 4.9.2: Audience • Contact eds4@ercot.com if: • You should not be on this list <or> You should be on this list but are not TSPs http://nodal.ercot.com 5

  6. EDS 4.9.2 Sandbox testing timeline Feb Mar Apr May Jun Application Components 4/1 - V1.11 (unapproved) 3/21 - V1.10 Nodal Sandbox - Loopback EWS 4/21 – V1.11 (approved) • Outage Creation • Outage Cancellation • Outage Query EWS RUI 4/15 6/13 OS Connectivity and Submission Testing EWS & RUI Application Components • Outage Creation • Outage Cancellation • Outage Query • Nodal Sandbox contains External Web Services pertinent to Outage Scheduler. If you will be using the Web Services to connect to Outage Scheduler, please use the Sandbox to verify connectivity and XML structures • All Outage Scheduler web services currently conform to External Interface Specification V1.10 • Changes to the following services will be deployed to Sandbox on 4/1 • Outage Creation • Outage Cancellation • Outage Query • If you have any questions, please contact EDS 4 team – EDS4@ERCOT.com http://nodal.ercot.com 6

  7. EDS 4.9.2 RUI timeline Feb Mar Apr May Jun 4/15 6/26 RUI RUI • Print • Help • Warnings • Copy Outage • Outage Creation (all outage types) • Grouped outages • Recurring Outages • View Summary • Edit Outage (Simple / Group) • Remove items from Group • Forced & Unavoidable extensions • Advanced filtering • Pagination • Export Application Components EWS RUI 4/15 6/13 OS Connectivity and Submission Testing EWS & RUI Application Components • Outage Creation • Outage Cancellation • Outage Query • MPs will be able to perform all EDS test scenarios using the RUI starting 4/15/2008 • If you have any questions, please contact EDS 4 team – EDS4@ERCOT.com http://nodal.ercot.com 7

  8. Outage Scheduler 4.9.2 Timeline • EDS 4 9.2 will now start on 4/15 • The focus of this presentation will be primarily on EDS 4 9.2.2 – OS Connectivity and Submission Testing http://nodal.ercot.com 8

  9. Outage Scheduler EDS 4.9.2: Objectives http://nodal.ercot.com 9

  10. Outage Scheduler EDS 4.9.2: MP Involvement http://nodal.ercot.com 10

  11. Outage Scheduler 4.9.2 Testing: Support Call Test Cases for Connectivity and Submission testing TSPs QSEs with Resources • Each of the outage types may require multiple outage entries to ensure we can test the entire workflow • OS Submissions Test Scripts document to be posted on Readiness Center on 4/2/08 will provide further details http://nodal.ercot.com 11

  12. Outage Scheduler 4.9.2 Timeline: Example Activity Timeline EDS TIMELINE Example Activity Timeline http://nodal.ercot.com 12

  13. Outage Scheduler 4.9.2 Testing: Testing Window • QSEs and TSPs are required to sign up via email for a testing window • This will initiate a number of events that will occur before the Testing Window (detailed in a later slide) • Testing Window includes: • 2 hour support and scripted testing call • Resolution of issues during the 2 hour support call • 7 calendar days testing window for prioritized support and self guided testing • Optional self guided testing are test scenarios that the QSEs and TSPs have defined and execute independently in the EDS environment • Scheduling your testing window early allows more time for self guided testing, make-up windows and issue resolution http://nodal.ercot.com 13

  14. Outage Scheduler 4.9.2 Testing: Testing Window Sign-up Email Content The sign-up Email from QSEs and TSPs should include: • Support Window Date and AM or PM preference • Provide primary contact details • Provide top three preferred dates with AM / PM preference • ERCOT may still need to coordinate a date outside of these 3, but will make every effort to be on one of these dates • DUNS number of QSE or TSP • If using Web Services, confirm that you the QSE/TSP will be engaged in testing and not your 3rd Party Service Provider: Yes/No • If using Web Services the URL where notifications will be sentNote: If this is unavailable at the time of sign up, this must be received 2 weeks prior to your scheduled testing window Send sign-up email to eds4@ercot.com by April 4th, 2008 http://nodal.ercot.com 14

  15. Outage Scheduler 4.9.2 Testing: Basic Communications Test (“Ping” Test) • MPs testing on the Web Services for the first time will be Scheduled for a 1 Hour Basic Communications test • This test typically takes 20-30 minutes if no issues are found • 1 hour is allocated to address any issues • Tests performed on the call will be as follows: • ERCOT performs a telnet to QSEs and TSPs Listener • QSEs and TSPs performs telnet to ERCOT External Web Services Listener • QSEs and TSPs send a sample transaction to ERCOT External Web Services Listener • Prior to this test MPs using External Web Services will need to have their network and security teams make the following changes: • QSE and TSP Listener must be on port 443 using one of the following Certificate Authorities • Verisign • Thawte • Entrust • Equifax http://nodal.ercot.com 15

  16. Outage Scheduler 4.9.2 Testing: Basic Communications Test (“Ping” Test) (continued….) • Prior to this test QSEs and TSPs using External Web Services will need to have their network and security teams make the following changes: • QSE’s / TSP’s Outage Scheduler system must be able to access:https://nodaleds.ercot.com:80/2007-08/Nodal/eEDS/EWS/NOTE: this SSL URL is on port 80 • Market Participants must be able to receive / send transactions to/from the following IP ranges: • 66.128.16.0/24 • 66.128.17.0/24 • 66.128.18.0/24 http://nodal.ercot.com 16

  17. Outage Scheduler 4.9.2 Testing: Basic Communications Test (“Ping” Test) (continued….) • QSEs and TSPs using MIS (RUI) will need to have their network and security teams make the following changes: • Market Participants must be able to receive / send transactions to/from the following IP ranges: • 66.128.16.0/24 • 66.128.17.0/24 • 66.128.18.0/24 http://nodal.ercot.com 17

  18. Outage Scheduler 4.9.2 Testing: Digital Certificates • 1 digital certificate w/ a Generic Userid (NODALTEST) will be Generated for Each QSE and TSP • 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 MP 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) • All valid ERCOT issued digital certificates will continue to work in the Nodal Sandbox http://nodal.ercot.com 18

  19. Outage Scheduler 4.9.2 Testing: Support Calls • Support Calls will be held Monday – Thursday Every Week • Support Calls Have 2 Time Slots available 9am – 11am and 1pm – 3pm • Fridays are reserved for: • Issue Resolution • Follow-up calls • Market wide status calls • Each Testing Date has up to 2 slots Available • MPs must have their Outage coordinator / Operator participating in the support call. MP IT personnel should be available for support • Calendar will be Posted Weekly on the Readiness Center / EDS 4 / Documents: http://nodal.ercot.com/readiness/eds4/documents/index.html http://nodal.ercot.com 19

  20. Outage Scheduler 4.9.2 Testing: Support Calls (continued…) • QSEs and TSPs using Web Services • Will perform all test scenarios on the web services during support call • Will perform a subset of scenarios on the RUI during the support call • Remainder of the scenarios can be tested independently by the MP through the RUI after the support call is complete • MPs must communicate to ERCOT once all test scenarios are complete • ERCOT will validate RUI submitted transactions • QSEs and TSPs using the RUI • Will perform all test scenarios on RUI during the support call • Validation will take place on the support call http://nodal.ercot.com 20

  21. Outage Scheduler 4.9.2 Testing: Issue Management • 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 eds4@ERCOT.com • 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 http://nodal.ercot.com 21

  22. Outage Scheduler 4.9.2 Tracking: Master Schedule (example) http://nodal.ercot.com 22

  23. Outage Scheduler 4.9.2 Tracking: Preparation Checklist / Schedule This Checklist will be completed by the ERCOT PM and consolidated to the Readiness Scorecard http://nodal.ercot.com 23

  24. Outage Scheduler 4.9.2 Tracking: Dashboard http://nodal.ercot.com 24

  25. Outage Scheduler 4.9.2 Reference: MP Activity Summary • Email eds4@ercot.com with the information on slide 12 “Sign-up email” by April 4th • Use the Nodal Sandbox functionality • Download and review the Outage Scheduler Test Package • Send sample XML to ERCOT no less than 2 weeks prior to Testing Window • Make Modifications (if any) to XML’s that ERCOT provides • Prepare final XML files for Support Call • Read and be Familiar with Documents on Next Slide • First Friday call will take place on Apr 18th. Refer to the ERCOT Calendar for log-in info and times. • Send all questions to eds4@ercot.com http://nodal.ercot.com 25

  26. Outage Scheduler 4.9.2 Reference: Relevant Documents http://nodal.ercot.com 26

  27. Q&A / Open Forum http://nodal.ercot.com 27

More Related