1 / 10

TX SET v3.0

TX SET v3.0. Implementation Plan - Brainstorming. Table of Contents. Example Shutdown Procedure Historical Shut Down Timeline Details Draft Conference Calls. Shut Down Procedure. The shutdown times listed will be strictly adhered to

daquan-vaughan
Download Presentation

TX SET v3.0

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. TX SET v3.0 Implementation Plan - Brainstorming DRAFT - for Discussion

  2. Table of Contents • Example Shutdown Procedure • Historical Shut Down Timeline Details • Draft Conference Calls DRAFT - for Discussion

  3. Shut Down Procedure • The shutdown times listed will be strictly adhered to • All MPs should submit transactions well in advance of the shutdown time so that large transaction volumes are not experienced just prior to shutdown • (i.e. if you run batch jobs, schedule them throughout the day)!!! • All MPs shall call-in to each conference call, on-time, during the implementation. • All times listed are Central Prevailing Time DRAFT - for Discussion

  4. Use of Safety Net-Draft • Begins Thursday, June 21st at 8:00am, the CR will utilize the approved Safety Net process during implementation with a default BGN 02 value to request Move-Ins with requested dates during migration period. If the REP cannot include the actual BGN02, the BGN02 must use the following format (cannot exceed 30 characters): • First 4 spaces= V301 • Next 3 spaces= Abbreviated CR name • Then followed by a unique number for each transaction. • CRs will be required to follow up with the corrected BGN02 on a Safety Net correction to the TDSP once their actual BGN02 is available. • The TDSPs will no longer accept default BGN values on Monday, June 25th at 8:00am or as soon as Version 3.0 transactions begin to flow. DRAFT - for Discussion

  5. High-Level TransactionShut-down timeline **Dates above based on MIMO and TX SET 2.1 Plans presented at MCT for those releases. • TX SET 3.0 will follow the same procedures as performed for previous implementations of MIMO and TX SET 2.1. • At this time, 3.0 looks larger than a 2.1 but smaller than MIMO, so the estimate would be a Thursday – Monday (or Go-Live) suspension of transactions. • The timing details will be finalized as Designs are complete. ERCOT will return to MCT to review and finalize all dates and times in the coming meetings. DRAFT - for Discussion

  6. Conference Call Times - DRAFT • Conference Call Information • TBD password: TBD • Press ‘6’ to mute/un-mute phone • Thursday June 21st 4:00pm • ERCOT transaction processing update • “in queue” • “in process” • Overall system health • CRs and TDSPs to provide status (state of systems and processing) DRAFT - for Discussion

  7. Conference Call Times-Draft • Friday June 22nd 9:00am • ERCOT transaction processing update • “in queue” • “in process” • Overall system health • Friday June 22nd 5:00pm • CRs & TDSPs to confirm 650s, 810s, 820s, 867s, and 814 P-2-Ps have stopped flowing (excluding responses); Confirm all initiating transactions processed. • ERCOT transaction processing update • “in queue” • “in process” • Overall system health DRAFT - for Discussion

  8. Conference Call Times-Draft • Saturday June 23rd 6:00 pm – DRAFT (This may be moved to Sunday based on the code migration duration times) • ERCOT declares Go/No-Go, % complete of production verification • CRs and TDSPs provide migration status DRAFT - for Discussion

  9. Conference Call Times-Draft • Sunday June 24th 10:00 am • CRs and TDSPs provide migration status • Sunday June 24th TBD • ERCOT provides time at which ERCOT will begin accepting v3.0 transactions • CRs and TDSPs provide migration status • If a Market Participant is not ready will use this time to establish the next conference call DRAFT - for Discussion

  10. Additional Contingencies • Weather delay – (May not be necessary) • First discussion of weather delay will take place on the Friday 9:00 am conference call. • If delay is not called on Friday 9:00 am, last opportunity for discussion of weather delay will take place on Friday 5:00 pm conference call • If delay is called, there are 2 possible results: • Weather does not cause a significant impact on any active MPs. Delay is one week. • Weather causes a significant negative impact on one or more active MPs. Delay may be more than one week. • Market Participant or ERCOT Delay • Contingency Plans required due to a Market Participant or ERCOT delay will be developed by affected participants and ERCOT if necessary DRAFT - for Discussion

More Related