Call meeting to order

 

• 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, they are available in person at the ERCOT Client Relations desk or you may request an electronic version by emailing Susan Clifton at Susan.Clifton@ercot.com.

 

• Disclaimer

All presentations and materials submitted by Market Participants or any other Entity to ERCOT staff for this meeting are received and posted with the acknowledgement that the information will be considered public in accordance with the ERCOT Websites Content Management Operating Procedure.

                                                                     

Introductions

ERCOT- SLA Updates

Review  comments if any and finalize Use Cases:

 

• Use Case MP9- IAG/IAL- impacts Use Case MP1 IAG/IAL as well with description below.  MP9 - On Inadvertent Issues, improve the workflow and validations to ensure that the Responsible MP is reflected as the party that is expected to provide the next update to move the issue towards resolution.

·         Use Case MP1 - Add functionality to the Inadvertent Gain and Inadvertent Loss process to allow for the efficient and verifiable approval for Transmission and/or Distribution Service Providers (TDSPs) to reverse priority Move-In Request charges from the losing Market Participant to the gaining Market Participant

·         Use Case MP20- GUI enhancement- Create a new user and individual item notification specifically related to the Meter Tampering issues.  (Reference MP19)

·         Use Case MP24- GUI Rolodex enhancement Add specific rolodex contacts for each sub-type (i.e. Billing/Usage, Meter Tampering, Cancel w/Approval, etc.)

·         Use Case MP21- DEV LSE- Add Service History as a required field for the TDSP when CR is the submitting MP and the modify/reassign transition is executed by TDSP

·         Use Case MP22- Missing Transaction enhancement - Add 867_02 to the tran type drop down feature

 Review and complete the following Use Cases:

 

• Use Case MP25- Validation- Usage/Billing: validate ROR = submitting MP
• Use Case MP27- Validation msg: ESI ID dupe return message link to existing issues
• Use Case MP28- Review Pending issue usage and necessity( Pending issues ill auto-closed  after 14 dayes) Send escalation notice of auto-close to submitter after 48 hours 

                                                            Lunch

• Use Case MP29- Proactively create a new, flexible catch all subtpe for market processes created prior to MTP4

 

• Use Case MP33- IAG/IAL: If there is no Regaining Siebel Status after 14 days of transition send it back to the Losing CR

 

• Use Case MP34-Validation: TDSP matches validation change request to change message from a warning to an error message

Assign Next Set Use Cases

Other Business

Gather Action Items

Adjourn