Inadvertent/MarkeTrak PR010_01 Critical Release Training - PowerPoint PPT Presentation

inadvertent marketrak pr010 01 critical release training n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Inadvertent/MarkeTrak PR010_01 Critical Release Training PowerPoint Presentation
Download Presentation
Inadvertent/MarkeTrak PR010_01 Critical Release Training

play fullscreen
1 / 127
Inadvertent/MarkeTrak PR010_01 Critical Release Training
118 Views
Download Presentation
zeal
Download Presentation

Inadvertent/MarkeTrak PR010_01 Critical Release Training

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Inadvertent/MarkeTrak PR010_01 Critical Release Training

  2. Antitrust 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.

  3. MarkeTrak Phase 3 Changes Requirement 1 – Market Rule Requirement 2 – AMS LSE Interval Dispute/Missing Requirement 3 – Switch Hold Removal Requirement 4 – Redirect Fees Requirement 5– Customer Rescission

  4. Requirement 1Market Rule

  5. Market Rule • ***There is no Market process currently approved for use within this subtype*** • Flexible catch-all subtype for accommodating any future PUC rulings that cannot be worked thru existing workflows in MarkeTrak. • Will include broader range of optional fields and will include functionality to enable an assignee to add a third party to the issue. • Any issue submitted under this subtype should include a reference to a specific approved rule or guideline, within processes outlined in Market documentation. In the absence of such processes, this subtype should not be used and may be rejected by the assignee.

  6. Market Rule • Day to Day Issues – Market Rule • Required Fields for Market Rule • Assignee • Market Rule • Comments • Examples of Market Rule Workflows • CR to TDSP • CR to TDSP – TDSP assign Second CR • TDSP to ERCOT • TDSP to ERCOT – ERCOT assign Second CR • CR to CR • TDSP to TDSP • A CR or TDSP can submit this subtype

  7. Market Rule

  8. Market Rule • The following fields must be populated for successful submission (required information). • CR enters required information: • ASSIGNEE • MARKET RULE • COMMENTS

  9. Market Rule

  10. Market Rule • “Happy Path” #1- CR submits issue to TDSP • CR enters required information and selects ‘OK’. • Issue transitions to state of ‘New’ with the TDSP as the Responsible MP. • TDSP selects ‘Begin Working’. • Issue transitions to state of ‘In Progress (Assignee)’ with the TDSP as the Responsible MP. • TDSP selects ‘Assign To Secondary’ and enters a second CR DUNS in the find/drop down field and selects ‘OK’.

  11. Market Rule Issue transitions to state of ‘New (Secondary Assignee)’ with the second CR as the Responsible MP.

  12. Market Rule • “Happy Path” #1- CR submits issue to TDSP (cont.) • Second CR selects ‘Begin Working’. • Issue transitions to state of ‘In Progress (Secondary Assignee)’. • Second CR selects ‘Complete’ and enters required comments to close the issue.

  13. Market Rule Issue transitions to State of ‘Pending Complete’ with the Submitting CR as the Responsible MP.

  14. Market Rule • Happy Path” #2- TDSP submits issue to TDSP, who assigns to CR. • TDSP selects Market Rule subtype from the Submit Tree. • TDSP enters required information: • Assignee - TDSP • Market Rule • Comments • TDSP selects ‘OK’. • Issue transitions to state of ‘New’ with second TDSP as the Responsible MP. • TDSP selects ‘Begin Working’.

  15. Market Rule • Happy Path” #2- TDSP assigns issue to TDSP, who assigns to CR (cont.) • Issue transitions to state of ‘In Progress (Assignee)’ with TDSP as the Responsible MP. • TDSP selects ‘Assign To Secondary’ and enters a CR Duns in the dropdown field and selects ‘OK’. • Issue transitions to state of ‘New (Secondary Assignee)’ with the CR as the Responsible MP. • CR selects ‘Begin Working’. • Issue transitions to state of ‘In Progress (Secondary Assignee)’.

  16. Market Rule • Happy Path” #2- TDSP assigns issue to TDSP, who assigns to CR (cont.) • CR selects ‘Assign To Submitter’ and enters required comments. • Issue transitions to state of ‘New - All’ with the Submitting TDSP as the Responsible MP. • Submitting MP selects ‘Begin Working’ and the issue transitions to state of ‘In Progress’. • Submitting MP selects ‘Complete’ and issue transitions to state of ‘Pending Complete’.

  17. Market Rule • Examples for Market Rule submitted by TDSP to ERCOT 1. TDSP selects the Submit tab 2. From the Submit Tree, select Market Rule • The following fields must be populated for successful submission (required information): • TDSP enters required information • Assignee – ERCOT • Market Rule • Comments • Optional TDSP Information

  18. Advanced Meter SystemAMS LSE Interval Dispute/Missing

  19. AMS LSE Interval Dispute/Missing The Usage/Billing AMS LSE Interval Missing and Dispute SubTypes were developed to address market discrepancies for Advanced Smart Meter Data. Smart Meters register data with 15-minute intervals. The Usage/Billing Missing and Dispute SubTypes differ in the fact that these issues are submitted for discrepancies for Monthly 867s and 810 invoices.

  20. AMS LSE Interval - Dispute • Dispute description: • A new subtype, Usage and Billing Dispute LSE Interval Data was added to the MarkeTrak tool under the Day to Day (D2D) submit tree using the existing D2D Usage and Billing workflow as a template. • A new field ‘UIDAMSINTERVAL’ was added for this subtype – this field is located in ERCOT’s AMSINTERVAL table. This field uniquely identifies the specific interval being disputed.

  21. AMS LSE Interval - Dispute • Dispute Overall High Level Process: • Define the following: • Who should submit this SubType • What is required to submit this SubType • How to submit this SubType

  22. AMS LSE Interval - Dispute Who should submit this SubType? • Competitive Retailers (CRs) submit this SubType when they discover a discrepancy with the AMS LSE interval data from the TDSP.

  23. AMS LSE Interval - Dispute What is required to submit this SubType? • The ESIID must have an AMS meter profile at ERCOT. • The usage data must be loaded in the ERCOT system and is identified by the unique identifier ‘UIDAMSINTERVAL’ from the Supplemental AMS Interval Data Extract. • This field uniquely identifies the specific interval being disputed for a one day service period. • For example: 01/01/2012 00:00:00 – 01/01/2012 23:59:59

  24. AMS LSE Interval - Dispute The Supplemental AMS Interval Data Extract is posted daily to the ERCOT Market Information System (MIS). Additional information about the extract can be found in the Supplemental AMS Interval Data Extract User Guide located on ERCOT.com.

  25. AMS LSE Interval - Dispute How to submit this SubType? From the MarkeTrak submit tree, under the D2D section: • Select the Usage/Billing AMS LSE Interval Dispute option. • Enter the data for the required fields.

  26. AMS LSE Interval - Dispute • “Happy Path” • Requesting CR selects Dispute under Usage/Billing AMS LSE Interval from the Submit Tree. • Requesting CR enters all required information and selects ‘OK’. • The issue is now in the state of ‘New’ with the TDSP as Responsible MP. • TDSP selects ‘Begin Working’. • The issue is now in a state of ‘In Progress (Assignee)’.

  27. AMS LSE Interval - Dispute • “Happy Path (cont.)” • TDSP selects ‘Complete’, enters Comments (optional) and selects ‘OK’. • The issue is now in a state of ‘Pending Complete’ with the Submitting MP as the Responsible MP. • Submitting MP selects ‘Complete’ and the issue transitions to ‘Complete’.

  28. AMS LSE Interval - Dispute CR selects ‘Dispute’ from the Submit Tree.

  29. AMS LSE Interval - Dispute CR enters required information and selects ‘OK’.

  30. AMS LSE Interval - Dispute TDSP selects ‘Begin Working’ and then selects ‘Complete’ and enters optional Comments. TDSP selects ‘OK’.

  31. AMS LSE Interval - Dispute Submitting CR selects ‘Complete’ and the issue is closed to a state of ‘Complete.

  32. 867_03 vs. LSE Discrepancy Inquiry about 867_03 Usage Discrepancy If there is an inquiry about the mismatch between an 867_03 service period and the sum of the AMS intervals for that service period, CRs should not use the AMS Dispute Subtype. Instead, the CR should email: - Designated TDSP inbox when applicable, or; - TDSP REP Relations contact

  33. AMS LSE Interval - Missing • Missing description • A new subtype, Usage and Billing MissingLSE Interval Data, was added to the MarkeTrak tool under the Day to Day (D2D) submit tree using the existing D2D Usage and Billing workflow as a template.

  34. AMS LSE Interval - Missing • Missing Overall High Level Process: • Define the following: • Who should submit this SubType • What is required to submit this SubType • How to submit this SubType

  35. AMS LSE Interval - Missing Who should submit this SubType? • Competitive Retailers (CRs) file this SubType when they discover an interval usage gapwith the AMS LSE interval data from the TDSP.

  36. AMS LSE Interval - Missing What is required to submit this SubType? • The ESIID must have an AMS meter profile at ERCOT. • The CR must be the current Rep of Record for ALL usage days specified by the StartTime and StopTime range. • The issue must reflect one or more consecutive day(s). • For example: 01/01/2012 00:00:00 – 01/04/2012 23:59:59

  37. AMS LSE Interval - Missing How to submit this SubType? From the MarkeTrak submit tree, under the D2D option: • Select the Usage/Billing AMS LSE Interval Missing option. • Enter the data for the required fields.

  38. AMS LSE Interval - Missing • “Happy Path” • Requesting CR selects Missing under Usage/Billing AMS LSE Interval from the Submit Tree. • Requesting CR enters all required information and selects ‘OK’. • The issue is now in the state of ‘New’ with the TDSP as Responsible MP. • TDSP selects ‘Begin Working’. • The issue is now in a state of ‘In Progress (Assignee)’.

  39. AMS LSE Interval - Missing • “Happy Path cont.” • TDSP selects ‘Complete’, enters Comments (optional) and selects ‘OK’. • The issue is now in a state of ‘Pending Complete’ with the Submitting MP as the Responsible MP. • Submitting MP selects ‘Complete’ and the issue closes to ‘Complete’.

  40. AMS LSE Interval - Missing CR selects ‘Missing’ from the Submit Tree.

  41. AMS LSE Interval - Missing CR enters required information and selects ‘OK’.

  42. AMS LSE Interval - Missing TDSP selects ‘Begin Working’ and then selects ‘Complete’ and enters optional Comments. TDSP selects ‘OK’.

  43. AMS LSE Interval - Missing Submitting CR selects ‘Complete’ and the issue is closed to a state of ‘Complete.

  44. Requirement 3Switch Hold Removal

  45. Switch Hold Removal • Addition and Removal of Switch Hold by REP of Record • MarkeTrakOther subtype used prior to Texas SET 4.0, no longer in use for this process. • ISA 71711 • ISA 71712 • ISA 71644 • TDSPs will unexecute any attempts to add or remove a Switch Hold using MarkeTrak subtype Other. • 650_01 transactions are now required for this process • SH001- Add payment plan hold • SH002- Remove payment plan hold • SH003- Remove tampering hold

  46. Switch Hold Removal • General overview of Four-Hour Switch Hold Removal Process • PUCT Subst. Rules 25.126 Adjustments due to Non-Compliant Meters and Meter Tampering in Areas where Customer Choice has been Introduced and 25.480 Bill Payments and Adjustments contain guidelines for the addition and removal of switch holds by CRs • If a CR would like to request a move-in for a new customer on an ESIID subject to switch hold, PUCT Rules allow for a process to be created within MarkeTrak to be resolved in four business hours. The TDSP, REP of Record and requesting CR will work together to determine if the new occupant is associated with the occupant subject to switch hold. • The requesting CR must provide one of several PUCT-approved forms of documentation for all MPs involved to review. • If it is determined that the new occupant is not associated with customer of record, the TDSP will remove all switch holds applied to the ESIID.

  47. Switch Hold Removal • General overview of Four-Hour Switch Hold Removal Process (cont.) • Only one MarkeTrak issue needs to be filed per ESIID (Type of switch hold applied to ESIID may not be visible to requesting CR). • Sections 7.16 (Tampering) and 7.17 (Payment Plan) in the Retail Market Guide (RMG) were created to accommodate removal of switch holds. The sections only differ based on type of switch hold; the end result is the same. • RMG 7.16-7.17 outlines the entire process using MarkeTrak terminology. All MPs should become familiar with this section of the RMG. • If an issue has been open four business hours without resolution, the TDSP will make a final decision as to whether or not the switch hold will remain.

  48. Switch Hold Removal • Switch Hold Removal Subtype • Background: Developed by MarkeTrak Task Force to facilitate the process from RMG Sections 7.16-7.17 • This subtype replaces the interim process which used the Other subtype (ISA 7164) • TDSPs will unexecute any attempt to use the Other subtype with this ISA • New features within Switch Hold Removal subtype • Agree and Disagree transitions to indicate clear response from CR • Time Limit Exceeded transition for use by the Requesting CR when the REP of Record has not replied within one and a half business hours, as stated in the RMG • Requesting CR no longer has to notify TDSP via email • TDSP will become Responsible MP • More efficient workflow • Submitter will not have to continuously monitor the issue • As a result of the new workflow, the TDSP and REP of Record each have an additional 30 minutes of review time within the overall four-hour period

  49. Switch Hold Removal • Business Hours • The timelines referred to within this workflow are in effect Monday-Friday, 8:00AM-5:00PM (Business Days) • Business rules which govern timelines are also found within RMG 7.16-7.17 • TDSP initial review: one business hour • REP of Record review: one and a half business hours • TDSP final review: one and a half business hours (or remaining time within four-hour period) • If issue remains unresolved at the end of a business day, the Responsible MP’s time will resume next business day at 8:00AM • Example: REP of Record is assigned the issue at 4:00PM Friday. Business hours cease at 5:00PM Friday. Business hours resume 8:00AM Monday. REP of Record has until 8:30 AM Monday to respond, for a total of one and a half business hours as Responsible MP.

  50. Switch Hold Removal • CR Transitions • Agree • REP of Record believes the customers are not associated, or does not have information to show otherwise • Disagree • Per RMG 7.16.4.3.2(3)(a)(ii)(B): “If the losing CR has information that indicates that the gaining CR’s Customer and the losing CR’s Customer are associated, the losing CR shall choose the ‘Disagree’ transition within MarkeTrak. Additionally, the losing CR must state reasons for disagreement and attach documents that support the losing CR’s position.” • Time Limit Exceeded • The Requesting CR should use this transition ONLY when the REP of Record has been Responsible MP, without transition, for one and a half business hours.