1 / 167

MarkeTrak Issue Resolution Tool Retail Market Participant Workshop

MarkeTrak Issue Resolution Tool Retail Market Participant Workshop. MarkeTrak Overview. Bulk Insert Requirement 4. Bulk Insert. A method via the GUI application to submit multiple issues at once Must use a csv (comma separated value) file to submit issues

yovela
Download Presentation

MarkeTrak Issue Resolution Tool Retail Market Participant Workshop

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. MarkeTrakIssue Resolution ToolRetail Market Participant Workshop

  2. MarkeTrak Overview

  3. Bulk InsertRequirement 4

  4. Bulk Insert A method via the GUI application to submit multiple issues at once Must use a csv (comma separated value) file to submit issues All issues within a single csv file must be of the same issue sub-type

  5. Bulk Insert – Creating csv file Guidelines for creating csv input file Bulk Insert Templates can be found on the MarkeTrak Information page. (http://www.ercot.com/services/client_svcs/mktrk_info/index) Use the MarkeTrak data field tables as a guide. Must use all fields even if left blank Follow csv file format rules: Pay attention to special characters because it may alter columns Exclude header row Requirement 4

  6. Bulk Insert DATE FORMAT: YYYY-MM-DDTHH:MM:SS

  7. Bulk Insert – Creating csv file Cancel With Approval Template found on MarkeTrak Information page.

  8. Bulk Insert – Creating csv file **NOTE: 1 in the Optional Columns N and O means run those validations. Otherwise Validations are defaulted to 0 (do not run) Requirement 4

  9. Bulk Insert – Creating csv file Delete both of the Header Rows before saving as a csv file

  10. Bulk Insert – Creating csv. file

  11. **You will have to open your csv file in notepad and verify that all fields are represented by commas.**

  12. **Add any missing commas (place holders) to the issues**

  13. Background Report Requirement 17

  14. Background Report Overview • Market Participants have requested the ability to run reports that would involve more than 1000 rows of data. • In an effort to accommodate this request, ERCOT has enabled Market Participants to request reports that are run in the background and are delivered either as attachments or posted to TML. • Report will be posted as a .csv file • This ability allows Market Participants to increase their efficiency by allowing the Market Participant to request large reports and continue working in MarkeTrak while the report is being run. • Multiple background reports can be requested, so Market Participants do not have to wait for an individual report to complete before moving on to other MarkeTrak tasks.

  15. From Submit Tree, CR selects Background Report

  16. CR then selects the appropriate report from the drop-down menu and types any comments (optional) and clicks “OK” button

  17. Background Reports Available and Descriptions

  18. CR is then given a screen showing what report they are requesting. CR will then click the “Provide Parameters” button.

  19. CR Selects Destination for report (either Issue Attachment or TML) from the Report Destination drop-down menu

  20. CR Selects applicable project(s) from the MarkeTrak Projects drop-down menu. *Note: All background reports have the option, but some background reports do not require the MarkeTrak Projects field to be populated. All required parameters for the report type selected will be shown above the Report Destination drop-down menu

  21. CR Inputs Parameters required for the type of background report that is being requested. Different reports have different parameters. Any parameters that are not necessary will either not be visible or will show the “Not Used” header. Once all Parameters are filled out, CR clicks the “OK” button

  22. If CR would like to be notified upon completion of the report, the CR Clicks the “Actions” drop-down menu, selects “Add Item Notification” and selects “MT – Background Report has been prepared”. This must be done prior to submission of the report request.

  23. CR then reviews the details of the background report submission and has the option to either ‘Update Parameters’, ‘Withdraw’, ‘Add Comment’ or “Submit Report” using the buttons at the top of the page.

  24. At this point the report has been submitted and will be posted either as an attachment or to TML, whichever was requested. Reports will be available on TML for 30 days

  25. Once the report has completed and is either attached to the issue or posted to TML, the MarkeTrak issue will Auto-Close.

  26. Screenshot of an example report

  27. If the report encounters an error, the report will post with all data present up to the point in which the error occurred and will include a description of the source of the error in the last populated column. Possible errors may include (but not limited to): • SQL errors • Data requested in wrong format (date that does not exist, etc) • Start and Stop time transposed If a report encounters an error, you cannot modify the report once submitted. You will have to submit another background report request with the needed modifications.

  28. Requirement 31

  29. LSE in ERCOT System but not in MP System

  30. LSE relationship record present in ERCOT system but not in MP system Submitted TDSP to ERCOT CR to ERCOT • TDSPs and CRs should file this variance when: • LSE relationship should be removed at ERCOT • When a de-energized period would be created in ERCOT’s systems to complete a Variance, the TDSP will be asked to confirm rep of record for the affected time period • Submitting MP and Assignee must be in agreement prior to process the change request ERCOT Resolution Remove LSE relationship from ERCOT systems

  31. LSE relationship record present in ERCOT system but not in MP system Requested Resolution equals Remove LSE relationship from ERCOT systems Information should reflect relationship as is present in ERCOT systems and is communicated to the MP through their ESI ID Data Extract (SCR727) If a de-energized period is being created in ERCOT systems where TDSP reflects a rep of record, TDSP is required to inform ERCOT of rep of record as is reflected in their systems per RMS decision on 8/14/2003 Most required fields are found in your ESI ID Extract (SCR727) Quick Notes

  32. LSE in ERCOT system not MP 1. The TDSP selects the Submit tab 2. From the Submit Tree, select LSE in ERCOT system not MP 1 2

  33. 3. The following fields must be populated for successful submission of a DEV- LSE sub type LSE in ERCOT System not MP: Assignee ESI ID UIDESIID STARTTIME STOPTIME- optional PROFILECODE REP CODE ADDTIME STATUS ROR 1 (if Submitter is TDSP) 4. Select OK LSE in ERCOT system not MP

  34. TDSP 4 3 Requirement 31

  35. LSE in ERCOT system not MP Three Validations Occur: ESI ID Validation- Is the ESI ID valid? ESI ID Duplicate Check- Are there any other MarkeTrak issues submitted with the same ESI ID for the same company? TDSP associated with ESI ID?

  36. LSE in ERCOT system not MP The issue enters ERCOT’s queue in the state of “New” and is visible only by the Submitter, Assignee and ERCOT The Submitter can ‘Withdraw’ only. ERCOT can acknowledge it only TDSP

  37. LSE in ERCOT system not MP 5. ERCOT selects ‘Begin Working’ ERCOT 5 Only ERCOT and TDSP can view the TDSP Information within the issue. (Requirement 31)

  38. LSE in ERCOT system not MP 6. The Submitter can no longer ‘Withdraw’ the issue. ERCOT has the options: ‘Passed Analysis’ or ‘Unable to Complete’, which transitions the issue to an “Unable to Complete (PC)” status or ERCOT selects primary path: ‘Passed Analysis’ ERCOT 6

  39. LSE in ERCOT system not MP 7. The following fields must be populated by ERCOT to complete the transition based on this sub type: Usage Matches Date Requested, Usage Loaded for Date Requested and Usage for Time Period 8. Once these fields are populated, ERCOT selects ‘OK’

  40. ERCOT 8 7

  41. LSE in ERCOT system not MP The issue is transitioned to a state of “New (Pending Approval)”. The visibility of the issue remains unchanged. Only the Responsible MP (CR) can transition and the only option is ‘Begin Working’ CR

  42. LSE in ERCOT system not MP From the state of “In Progress-Pending Approval” the Responsible MP has three options: ‘Update Approved’, ‘No Agreement Reached’ or ‘Modify/Reassign’ for Approval transitioning to a “New-Pending Approval State” CR

  43. LSE in ERCOT system not MP 9. Selection of ‘Update Approved’, the Responsible MP is agreeing to the current requested resolution CR 9

  44. LSE in ERCOT system not MP 10. The Responsible party (CR) can provide Comments at this time and Select ‘OK’. The issue will transition to state “New (ERCOT Resolve) CR 10

  45. LSE in ERCOT system not MP 11. ERCOT selects ‘Begin Working’ ERCOT 11

  46. LSE in ERCOT system not MP 12. ERCOT has the option to select ‘Additional Info Required’, ‘Unexecutable’or ‘Complete’. In this example, ERCOT selects ‘Complete’ ERCOT 12

  47. LSE in ERCOT system not MP The change would be made in Siebel/Lodestar and notifications would be sent to affected MPs. The issue is transitioned to a “Pending Complete” state The Submitter has the option to close the issue by selecting ‘Complete’ or the issue will be auto closed in 14 calendar days TDSP

  48. LSE in ERCOT system not MP The issue will transition to a “Complete” (Closed) state. TDSP

  49. Questions

More Related