1 / 19

RMS Update - High Level Timeline for Project PR010_03

This draft timeline outlines the planning, execution, testing, and implementation phases of Project PR010_03. The project aims to improve workflows and reporting capabilities in the market, increasing efficiency and reducing resolution time for market participants.

lulad
Download Presentation

RMS Update - High Level Timeline for Project PR010_03

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. Update to RMS January 10, 2014

  2. Project(PR) 010_03 SCR756 Part B – High Level Timeline DRAFT: Planning Phase: ~ (End of 2013) Business requirements for the market will be finalized from ERCOT ~ end of Jan 2014 Execution/Development: ~ 3 Months (Start Jan 2014 –March 2014) Testing: ~ 3 Months (Start April 2014) Includes UAT Testing/ITesting/Training documentation Begin developing training materials and identify dates for training sessions

  3. Project(PR) 010_03 SCR756 Part B – High Level Timeline DRAFT: Start identifying sections in the User’s Guide (UG) to update (Start August 2013 – End of 2013) Define what’s not working well in the current UG Clarification Market Training: ~ 1 Month (May 2014) Coordinate training sessions close to implementation weekend at least 5 weeks before migration weekend TF provide ERCOT with final draft for PartB training materials. (February 2014)

  4. Project(PR) 010_03 SCR756 Part B – High Level Timeline DRAFT: Implementation: ~ Weekend (End of June 2014) Usually implemented during an ERCOT I.T. Retail release (Included in SLA) Stabilization: ~ 4 -6 Weeks Lessons Learned

  5. Market benefits associated with Project(PR) 010_03: Inadvertent Gain (IAG) Abbreviated workflow and increased validations will facilitate quicker reinstatement of the Customer with their CR of choice by: Ensuring issue is always assigned to appropriate Market Participant. Automating system alert to notify losing CR of regaining IAG transaction status.

  6. Market benefits associated with Project(PR) 010_03: Inadvertent Gain (IAG)- cont. Eliminating confusion and delays in resolving IAG issues by clarifying reinstatement date of the Electric Service Identifier (ESI ID) by the losing CR. Displaying critical information for regaining transaction based on user input.

  7. Market benefits associated with Project(PR) 010_03: Specific Customized Reporting Allow companies to have view into their specific issues in progress to ensure completion within ERCOT and Public Utility Commission of Texas (PUCT) mandatory timelines. Allow MPs to create reports specific to their organizational needs.

  8. Market benefits associated with Project(PR) 010_03: Data Extract Variance (DEV) Adds reporting and process efficiencies to the DEV process and will decrease resolution time by: Implementing an additional data field “First Touched by TDSP” and Service History information to DEV LSE subtypes. This allows CRs and TDSPs to have visibility to determine their “workflow” responsibility and how much time available to resolve the issue

  9. Market benefits associated with Project(PR) 010_03: Usage and Billing The following improvements to workflows will facilitate positive customer impact: Creates distinct subtypes (Missing vs. Dispute) for Market Participants to submit the correct issue type and minimize delays due to issues submitted with incorrect data. Users will be able to more accurately differentiate the type of issues submitted.

  10. Market benefits associated with Project(PR) 010_03: Usage and Billing – cont. CRs and TDSPs will be able to streamline internal processes, expediting resolution. If corrective action is necessary, adds transparency to settlement data quality. Market Participants can efficiently route issues to the appropriate users upon “transition.” Automatic validation that submitting CR is Retail Electric Provider (REP) of record for affected service period will reduce the need for manual intervention.

  11. Market benefits associated with Project(PR) 010_03: MarkeTrak Notifications Reduces resolution time by increasing transparency of MarkeTrak activity via the following: Sending emails specific to the impacted Data Universal Numbering System (DUNS Number). Increasing frequency of email reminders for issues untouched by assigned party. Expanding the list of escalation categories, allowing efficient routing of newly created specific subtypes.

  12. Market benefits associated with Project(PR) 010_03: System Validations Will minimize delays due to issues submitted with incorrect data by: Implementing validations to prevent users from entering invalid information into pre-defined fields. Changing specific warning messages to error messages (disallowing users to proceed with the submission of invalid information)

  13. Market benefits associated with Project(PR) 010_03: API functionality The ability to retrieve and download attachments via the API will allow: Easier dissemination that allows faster processing of critical, time sensitive information/reports to increase operational efficiencies Improved API functionality will remove manual steps during Market Participant evaluation of new move-in customer’s documentation

  14. Market benefits associated with Project(PR) 010_03: API functionality – cont. Impacted subtypes include Switch Hold Removal for new move-ins to support P.U.C. Subst. R. 25.126 - Adjustments Due to Non-Compliant Meters and meter Tampering in areas Where Customer Choice Has Been Introduced – P.U.C. Subst.R. 25.480 – Bill Payments and Adjustments Retail Market Guide Sections 7.16, Business Processes and Communications Related to Meter Tampering and 7.17, Business Processes and Communications for Switch Holds Related to Deferred Payment Plans, of new move-in customer’s documentation.

  15. 2014 Goals Successfully implement Project(PR) 010_03 MarkeTrak Phase III Enhancements via System Change Request (SCR756) Part B Update the MarkeTrak User’s Guide to include PR010_03 changes Coordinate with ERCOT to develop market training for PR010_03 Coordinate with RMS to sunset Task Force, if all Phase III Enhancements are concluded in 2014

  16. 2013 Accomplishments The Task Force was able to accomplish all objectives set at the beginning of 2013. Successfully finalized project plan for Phase III of SCR756 Part B, Enhancements to the MarkeTrak Tool At the request of PRS for the consideration of TAC, developed a white paper – ‘Summary of Market Benefits Associated with SCR756 Part B’ Developed training material for ERCOT Serena upgrade Facilitated training with ERCOT for Serena upgrade to MarkeTrak users

  17. 2013 Accomplishments • Assisted ERCOT during stabilization period for Post Serena Upgrade project • Implemented suggestions contributed by Market participants for improvements to the MarkeTrak Users Guide • Worked with other Retail Market Groups to streamline and update Retail processes in the ERCOT market • Retail Market SLA(TDTWG) • Non- Standard Metering Service, Switch Hold process (TX SET WG) • Data Extract Variance (COPS and CSWG) • Encouraged and increased Task Force participation for Retail market participants

  18. MarkeTrak Documentation • http://www.ercot.com/services/client_svcs/mktrk_info/ • User Guide • Bulk Insert Templates • MarkeTrak Workflows • MarkeTrak Tips and Tricks • MarkeTrak API WSDL/XSD Also direct link from MarkeTrak tool

  19. Questions

More Related