1 / 76

Texas Retail Market Testing Flight 0312– V4.0

Texas Retail Market Testing Flight 0312– V4.0. Agenda. I. Acronyms II. Points of Contact III. Supporting Documents IV. TX SET V4.0 High Level Changes V. Business Requirements for Entering Flight 0312 VI. Flight 0312 Schedule and Overview VII. Retail Testing Website Overview.

stu
Download Presentation

Texas Retail Market Testing Flight 0312– V4.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. Texas Retail Market TestingFlight 0312– V4.0

  2. Agenda I. Acronyms II. Points of Contact III. Supporting Documents IV. TX SET V4.0 High Level Changes V. Business Requirements for Entering Flight 0312 VI. Flight 0312 Schedule and Overview VII. Retail Testing Website Overview

  3. Agenda VIII. Flight 0312 Test Scripts Overview IX. Production Implementation X. Certification Letters XI. Testing to Production

  4. Acronyms • CERT – Certification Environment (used by ERCOT for flight testing) • FASD – First Available Switch Date • MCT – Market Coordination Team • PROD – Production Environment • RCS – Retail Client Services • RMG – Retail Market Guide • RMRD – Requested Meter Read Date • ROR – Rep of Record • RTW – Retail Testing Website • SMRD – Scheduled Meter Read Date • Texas SET – Texas Standard Electronic Transaction • TMTP – Texas Market Test Plan • TW – Testing Worksheet

  5. Points of Contact • Gene Cervenka: gcervenka@ercot.com; (512) 248-3903 • Kathryn Thurman: kthurman@ercot.com; (512) 248-6747 • James Allen: jallen@ercot.com; (512) 248-6466 • Sarah Heselmeyer: sheselmeyer@ercot.com; (512) 248-3952 • flighttesting@ercot.com – Used for day to day flight testing questions and issues during the test flight • retailmarkettesting@ercot.com – Used for flight testing signup questions and issues • mct@ercot.com – Used for TX SET version release questions and issues

  6. Supporting Documents and Useful Links • RTW – http://etod.ercot.com/default.asp; Related Content section provides additional links • Texas SET – http://www.ercot.com/committees/board/tac/rms/txset/ • MCT - http://www.ercot.com/committees/board/tac/rms/mct/

  7. Texas SET V4.0 High Level Changes • Acquisition Transfer A process that can be used to transfer ESI IDs from the current CR to another CR(s). Refer to Section 7.11.2 of the RMG for additional details. • Switch Hold 2 types: Tampering and Payment Plan. • Critical Care CCC, CCCT, CLI, CLP, CRC, and CRCT added as options in the REF03 of the REF~SU segment. Added expiration date and emergency contact information.

  8. Texas SET V4.0 High Level Changes • AMS Meter Indicator AMSM, AMSR, or NULL displayed on MIS Find ESIID and TDSP ESI ID Extract. • Same Day Move Outs ERCOT will send the 814_24 FWD, 814_03, or 814_25 reject within 1 Retail Business hour for move outs when the DTM~376 = current day. • Same Day Switches ERCOT will send the 814_03 or 814_02 reject within 1 Retail Business hour. FASD is the day received by ERCOT unless received on a Sunday or ERCOT holiday (in that instance FASD will be the next day that is not a Sunday or ERCOT holiday).

  9. Texas SET V4.0 High Level Changes • Same Day Move In ERCOT will send the 814_03 or 814_17 reject within 1 Retail Business hour for move ins when the DTM~375 = current day. • Date Change Window CR can send a date change request until 1 Retail Business day prior to the SMRD of the move in or move out. • Cancellation Window CR can send a cancel request until 1 Retail Business day prior to the SMRD of the move in, move out, or switch.

  10. Texas SET V4.0 High Level Changes • Stacking ERCOT Rejection Rule 3 will be removed. This rule evaluated the 2nd initiating transaction (or date change request) that was received within 2 days of the SMRD of the original transaction. Also, if a move in is received by ERCOT with a requested date prior to or equal to the SMRD of a move out, the move out will not be cancelled upon receipt of the move in. ERCOT will wait for the 814_04 on the move in before cancelling (or cancel pending) the move out. ERCOT Rejection Rule 4 will now include validation that if a switch is received with a requested date (or FASD for a Standard Switch) that is equal to the SMRD of a move in, ERCOT will reject the switch.

  11. Texas SET V4.0 High Level Changes • Stacking – cont. ERCOT Cancellation Rule 8 – If a move out or move out to CSA is scheduled for current day, and a move in is then scheduled for current day, ERCOT will not cancel the move out or move out to CSA and the TDSP has the option to work it or not. ERCOT Cancellation Rule 8 – T023 will be added as an unexecutable code in the REF~G7 segment in the 814_28 for use when the TDSP does not work the move out. ERCOT Cancellation Rule 8 – In the event the current day move out or move out to CSA is not completed or unexecuted by the TDSP within 4 Retail Business days, ERCOT will send an 814_08 (hard cancel) with a new cancel code of CMO (Cancel Move Out) to cancel the move out or move out to CSA.

  12. Texas SET V4.0 High Level Changes • Stacking – cont. ERCOT Cancellation Rule 8 – ERCOT will continue to evaluate a move in and move out or move out to CSA that are scheduled for the same day as long as neither is scheduled for the current day. At the beginning of the evaluation period prior to the move in and move out SMRD, if both still exist, ERCOT will cancel the move out or move out to CSA, and send a cancel to the TDSP and requesting CR. Pending Transactions Rule 16 – Upon receipt of an 814_04 to schedule either a Mass Transition or an Acquisition Transfer, ERCOT will generate the 814_14. All 814_20 Maintain transactions will be forwarded to the current ROR and any CRs that have a scheduled order for the ESI ID when the transaction is processed.

  13. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls Remove the EM (Electronic Mail) from the PER~IC segment in the 814_24. Add the A78 “Item or Service Already Established (Requested action has already completed)” reject code to the REF~7G segment in the 814_29 (ERCOT use only). Update the 650_04 to add an additional required field (REF~5H = RC001) upon submission of reconnect after disconnect for non-payment requiring the Originating Tran ID and the Estimated Restoration Date.

  14. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Discontinue use of the following transactions submitted to ERCOT by a CR: 814_07, 814_09, 814_10, 814_13, 814_15, 814_19, 814_21, 814_23 & 814_29. Three new codes will be added to the REF~8X segment of the 650_01 and 650_02. DC005 – Disconnect due to tampering; Authorizes the TDSP to disconnect service at any location accessible to them, including premium disconnect location. RC005 – Reconnect after tampering disconnect. MM007 – Investigate or verify premise type.

  15. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. ERCOT will close the Business Process Instance (BPI) if the 814_27 contains ASI~WQ~029 (Accept). Clarify language in the gray box for the REF~1P of the 814_04, 814_05, and 814_27 in the REF02. HUU is when no Historical Usage Available. HIU is when Summarized Historical Usage will be provided in the 867_02.

  16. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Clarify language in the gray box for the ASI~WQ of the 814_27 in the ASI01 to state: Note: WQ response does not mean that the TDSP will provide an 867_02 Historical Usage transaction to the CR or ERCOT. Note: Receipt of the TX SET 814_27 Accept Transaction will close the Business Process Instance (BPI) for ERCOT. Add the ACR “Acquisition Cancel Rejected” reject code to the REF~7G segment in the 814_09 (ERCOT use only). Add the 101 maintenance type code to the ASI~U segment in the 814_29 and SW to the LIN07 to allow ERCOT to reject the complete un-executable for a switch.

  17. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Sync transaction names in the Implementation Guides with those in the Protocols and Retail Market Guide. 824, 650_02, 650_04, 650_05, 810_02, 810_03, 814_01, 814_02, 814_03, 814_04, 814_05, 814_06, 814_08, 814_09, 814_18, 814_19, 814_20, 814_21, 814_22, 814_23, 814_26, 814_27, 814_28, 814_29, 820_02, 820_03, 867_03, 867_04, T0, T1, T2, T3, & T4. Remove the REF~IK segment (Invoice Number) from the 810_03 Muni/Co-op invoice. Add the FME “Force Majeure Event” reject code to the REF~7G segment in the 650_02.

  18. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Add the WTM “Weather Moratorium” reject code to the REF~7G segment in the 650_02. Add the T022 “Force Majeure Event” complete unexecutable code to the REF~G7 segment in the 650_02. Add the T022 “Force Majeure Event” complete unexecutable code to the REF~G7 segment in the 814_28. Add the FME “Force Majeure Event” reject code to the REF~7G segment in the 814_04, 814_05, 814_11, 814_13, and 814_25. Remove the incorrect link for locating the ISO Country Codes from the TX SET Implementation Guides for the 814_01, 814_14, 814_16, 814_24, and 814_PC.

  19. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Add the FI012 “Customer inquiry or installation of some type of Generation device or equipment at the Premise” code to the REF~8X segment in the 650_01 and 650_02. REF~1P segment is required in the 650_02 when REF~8X = FI012. Add the FI013 “Electric Vehicle” code to the REF~8X segment in the 650_01 and 650_02. REF~1P segment is required in the 650_02 when REF~8X = FI013. Add the A5 “Notice of Charge” code to the BIG segment in the 810_02 to communicate meter tampering charge. If BIG07 = A5, the BIG05, DTM~150, and DTM~151 segments are not used for Meter Tampering Discretionary Invoice as this will be sent on separate 810_02 and not included on Monthly Invoice.

  20. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Update the Implementation Guides for the 814_03, 814_04, 814_05, and 814_11 to reflect off-cycle as self-selected. An optional REF~RAA segment will be added to 814_03, 814_16, and 814_24 to allow the ability to communicate additional information to the TDSP. Only 1 segment allowed per transaction. Add the LE “Light Emitting Diode” code to the REF~PRT segment in the 814_04, 814_05, 814_14, 814_20, 814_22, 867_02, and 867_03. Add the WF “Wi-Fi (Wireless Fidelity)” code to the REF~PRT segment in the 814_04, 814_05, 814_14, 814_20, 814_22, 867_02, and 867_03.

  21. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Discontinue use of the 650_05. Add the T024 “Switch or Move-In cannot be completed due to Switch Hold recently applied to this ESI ID” code to the REF~G7 segment in the 814_28. REF~PV segment required when Complete (BGN08 = 51) and Purpose Code in the REF~8X = MM007 in the 650_01. Add the CMO “Cancel Move Out” code to the REF~1P segment in the 814_08 and 814_09 (ERCOT use only).

  22. TexasSET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Add the DUP “Duplicate” code to the REF~7G in the 650_02. Add clarifying language for the DC005 “Disconnect for Non-Pay for Charges associated to Tampering” to the REF~8X segment in the 650_01. Add clarifying language for the DC004 “Disconnect Due to Denial of Access to the Meter” to the REF~8X segment in the 650_02. Add the TCC “Competing Transaction Scheduled for the Same Date” code to the REF~7G segment in the 814_04, 814_05, 814_11, 814_13, 814_25, and 650_02.

  23. Texas SET V4.0 High Level Changes • TEXAS SET Change Controls – cont. Add the T025 “Competing Transaction Scheduled for the Same Date” code to the REF~G7 segment in the 814_28 and 650_02. Add the TDR “Two Business Days Notification Required” to the REF~7G segment in the 814_13. Update the gray box of the 814_04 to remove the statement that the REF~IX segment is optional when REF~MT = COMBO. Add clarifying language to the gray box to correct to PTD~PL.

  24. Business Requirements for Entering Test Flight FlightTesting

  25. EnteringTest Flight • How do I sign up to participate in Flight 0312, TX SET V4.0? • New LSE • Existing MPs • Additional DUNS for Certified REP • What are the business requirements I must fulfill before entering the test flight?

  26. Signing up for Flight 0312: New LSEs New LSEs that wish to sign up for Flight 0312 must complete ALL of the following by Flight Deadline: Wednesday, February 22 - 5:00 p.m. CPT • Submit LSE Application • Application can be found online: http://www.ercot.com/services/rq/lse • QSE Designation must be made prior to production Note – QSE must be Qualified/Certified by ERCOT • Application requires a DUNS number (www.dnb.com) • Please note that proper registration of your company must be on file at the Texas Secretary of State office in order for your ERCOT LSE application to be accepted (http://www.sos.state.tx.us/) .

  27. Signing up for Flight 0312: New LSEs • Submit $500 LSE Application Fee • File for REP Certification with PUCT (not required for MOU/EC) • Send the PUCT docket number to: RetailMarketTesting@ercot.com • Complete and submit a Testing Worksheet (TW) • TW located on the Texas Retail Testing Website (http://etod.ercot.com) • Notify ERCOT of intent to test via email • Notification must include company legal name and DUNS • E-mail must be sent directly from the Authorized Representative as designated on the LSE application • Send notification e-mail to: RetailMarketTesting@ercot.com

  28. Signing up for Flight 0312: New LSEs Additional DUNS for Certified REP please note: If a decision is made to add a DUNS for a Certified REP (DUNS or DUNS plus 4), this new entity is considered a new LSE from a business perspective • The new LSE must follow the “New LSE” steps for signing up for Flight 0312 From a testing perspective, there are ad-hoc truncated testing tracks available under certain circumstances.

  29. Existing LSEs will be required to test for the version upgrade to TX SET V4.0 and also if they are entering new service territories, testing additional business functionality, changing banking information, changing their service provider, or adding another entity to their business umbrella. Signing up for Flight 0312: Existing LSEs

  30. Signing up for Flight 0312: Existing LSEs To sign up for Flight 0312, an existing LSE must complete the following by Flight Deadline: Wednesday, February 22 - 5:00 p.m. CPT • Submit UPDATED Testing Worksheet (TW) • TW located on the Texas Retail Testing Website (http://etod.ercot.com) • Notify ERCOT of intent to test via email • Notification must include company legal name, DUNS, and what the entity plans to test for • E-mail must be sent directly from the Authorized Representative ERCOT currently has on file • Send notification e-mail to: RetailMarketTesting@ercot.com • If the only testing you are doing is for TX SET V4.0 changes, you do not need to send an intent to test email

  31. ERCOT Registration Requirements are defined in Protocol Section 16: Registration and Qualification of MPs http://www.ercot.com/mktrules/nprotocols/current ERCOT Registration Requirements must be fulfilled prior to a Market Participant receiving their certification letter and migrating to production. Registration Requirements

  32. New Load Serving Entity (LSE) Registration Requirements: LSE Application Completed Executed Standard Form Agreement QSE Designation Note – QSE must be qualified/certified by ERCOT LSE Application Fee Received PUCT Certification Issued (not required for MOU/EC) LSE Registration Requirements

  33. Flight 0312 Schedule Signup begins Feb. 15th. All existing MPs will be designated as testing due to the version upgrade. Please send an email to retailmarkettesting@ercot.com if you do not wish to test which will result in de-certification. Also, send notice if you intend to opt out of testing SCR51 and/or SCR61 due to not using this functionality. Signup deadline is Feb. 22nd. Connectivity testing begins Feb. 28th. Conference calls begin. TDSPs send test beds to CRs and ERCOT Mar. 19th. Flight 0312 kickoff conference call is Mar. 23rd.

  34. Flight 0312 Schedule Day 1 testing begins Mar. 26th. MarkeTrak testing begins May 1st and will end by May 25th. Testing will be on a volunteer basis (API users are required to test). MPs should provide testing contact info. to ERCOT. Additional information regarding testing will be communicated to the Texas SET listserv. Flight scheduled to end May 8th. Contingency testing available until May 25th if needed. PROD implementation for TX SET V4.0 version upgrade scheduled to take place Jun. 1st– 3rd. The following weekend would be used as a contingency.

  35. Flight Overview

  36. Flight 0312 Test Participants • ALL Existing CRs currently in the Market; Additional DUNS that utilize the same functionality as the Umbrella DUNS do not have to test • ALL Existing TDSPs • ERCOT • CRs new to the Market • Testing full Flight using ‘ALL’ Track

  37. How Do We Move Forward? • Check Points – Check Points will exist throughout the market test. These check points exist to allow: • The Flight Administrator to gauge where the market test is in relation to the flight timeline. • Take necessary action to get the flight back on schedule. • Weekends – The Flight Administrator may elect to use weekends for testing in the event testing has fallen behind schedule.

  38. Testing Testing Tracks and Testing Relationships

  39. Track Names TX SET 4.0 Connectivity Testing Scripts All New IOU CRs All New MOU/EC CRs Testing Tracks for V4.0 End-to-End Scripts

  40. Testing Tracks for V4.0 End-to-End Scripts • Track Names (cont) • CSA CRs • PUCT REP Certification Option 2 LSEs • Existing CR – Changing Service Provider

  41. Testing Tracks for V4.0 End-to-End Scripts • New IOU CR • All New LSEs will execute all scripts in this track with at least one TDSP territory that the LSE is entering • New MOU/EC CR • Any LSE who signed up to test with a MOU/EC TDSP will execute all scripts in this track with the MOU/EC TDSP

  42. Testing Tracks for V4.0 End-to-End Scripts • CSA CR • CSA LSEs and existing LSEs wanting to add CSA functionality will test IOU and MOU separately • PUCT REP Certification Option 2 LSEs • LSEs who are PUCT REP Option 2 LSEs are only required to test this track • Changing Service Provider • LSEs who are changing Service Providers will execute all scripts in the track with all TDSP territories in which the LSE is certified

  43. NAESB Connectivity Testing • All testing participants must test connectivity using NAESB EDM v1.6 • After connectivity is tested, any changes will require retesting before the start of the flight • Connectivity testing needs to be complete prior to Day 1

  44. Testing Relationships • ERCOT has committed to providing the following information to the market: • ERCOT will provide the testing relationship to MPs by Friday, February 24. • These lists will be sent to the Primary Testing, Secondary Testing, and Primary Business contact for each LSE and each TDSP that is listed on the Testing Worksheet (TW)

  45. Testing Relationships • If a Market Participant has issues with the testing relationships, issues must be communicated back to ERCOT by 5:00 p.m. on Monday, February 27. • Checklists will be created after the final testing relationships lists are delivered to the Market Participants.

  46. What Happens If I Don’t Meet Flight Checkpoints/Tasks? • Additional conference calls with the Flight Administrator as needed • Escalation procedures to executive management at the MP, ERCOT, and possibly the PUCT • MP may be requested to work overtime and/or weekends to catch up • MP may be asked to start the script over at a later time

  47. Random Testing • Market Participants testing the New track will participate in Random Testing • The purpose of Random Testing is to assist Market Participants with uncovering any potential validation problems • This allows the Market Participant to make changes to their system during the flight test • The goal is to reduce problem transactions in production

  48. Random Testing • Validations • Business validation • ANSI validation • Note: Each MP must successfully complete two Business validation tests and two ANSI validation tests • Further information regarding Random Testing may be found at the following: www.ercot.com Select Committees and Groups Select RMS Select Texas SET WG Under Key Documents, Select the Texas Market Test Plan (TMTP)

  49. Pre-Testing Preparation • Review ERCOT Protocols, Retail Market Guide, Texas Market Test Plan, TDSP Tariffs, and the Terms and Conditions • Review the V4.0 TX SET Implementation Guides • These often contain additional information on the business processes • Market Participants must establish banking relationships prior to the Connectivity Kick-Off call

  50. Pre-Testing Preparation • Review all test scripts within your test tracks • Contact ERCOT and/or Texas SET working group when you have questions • If you have a service provider, coordinate your testing activities in advance • When utilizing a service provider for flight testing, the testing process between the MP and the service provider must be representative of their production environments

More Related