Antitrust Admonition

1. 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, an electronic version is available at http://www.ercot.com/about/governance/index.html. Please remember your ongoing obligation to comply with all applicable laws, including the antitrust laws. 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.

2. PR010-03 Requirements • MTTF3 - Using the current Usage/Billing workflow, create two distinct Usage and Billing subtypes 1) Usage and Billing – Missing and 2) Usage and Billing – Dispute. This will minimize the optional fields resulting in fewer issues submitted with incorrect data. • MTTF4 - Create new MarkeTrak Administrator workflows. • MTTF5 - Change the name of the subtype ‘Missing TXNs’ to ‘Missing Enrollment TXNs’. • MTTF8 - Increase validations on Original Tran ID and Tran ID fields to prevent users from entering invalid data. • MTTF9 – Improve the process flow for Inadvertent Losing subtype.

3. PR010-03 Requirements – cont. • MTTF10 - Update Bulk Insert Templates by removing columns and rows that are no longer deemed necessary and check formatting of templates. • MTTF15 - Add the ability to return comments for specific date ranges on Background reports. • MTTF17 - Add “First Touched by TDSP” field to all DEV LSE subtypes. • MTTF21 - Add Service History as a required field for DEV LSE for the TDSP when a CR is the submitting MP and the modify/reassign transition is executed by the TDSP. • MTTF22 - For the Missing TXN subtype, add the 867_02, 814_PC, and 814_PD transactions to the list in the Tran Type drop-down field.

4. PR010-03 Requirements – cont. • MTTF23 - Add the ability to retrieve and download attachments via the API. • MTTF24 - Add Additional Subtypes to the Contact Type field in the MarkeTrak Contact List (Rolodex) table. • MTTF25 – Add the ability to validate ROR is the Submitting market participant to prevent users from creating invalid issues. This will apply to Usage Billing – Missing and Usage Billing-Dispute workflows. • MTTF26 - Background Reports: • Standardize the backend report criteria to use Issue Available Date • Count of Issues by Submitting MP Duns (Summary) • Count of Issues by Submitting MP Duns (By Subtype) • MTTF27 - ESIID duplicate warning message expanded to include hyperlinks to other MarkeTrak issues with that ESIID.

5. PR010-03 Requirements – cont. • MTTF28 - Auto close escalation and notification messages for issues remaining in Pending (not yet submitted) state for greater than three calendar days. • MTTF30 - Add the ability to execute and retrieve Background Reports via the API. • MTTF31 - Require Tran ID on the ‘814_20 Sent/Complete’ transition for Premise Type and Service Address subtypes. • MTTF33 - Create automatic transition for no regaining Siebel status (IAG and IAL). • MTTF34 - Change the TDSP matches validation from a warning to an error message. • MTTF35 - Add Recipient DUNs number and subject ESIID to MarkeTrak generated emails. • MTTF36 - Add Requested Date and MVI priority for Regaining Transaction.

6. PR010-03 Requirements – cont. • MTTF37 - Add an escalation email if an issue has been in states of ‘New’ for more than 3 calendar days. • MTTF40 - Add optional fields such as ESIID to the ‘997 Issues’ subtype to provide additional information about the transaction for which the 997 functional acknowledgement is missing. • MTTF44 - Add the ability to differentiate between Submitting MP Type in Background Reports. • MTTF46 - Add help function to field labels on Inadvertent Subtypes.

7. Requirement MTTF3Create Two Distinct Usage & Billing Subtypes

8. MTTF3a – Create Dispute Subtype • Description: Using the current Usage/Billing workflow, create a distinct subtype for Dispute. New Field titled ‘Dispute Category’ added to the workflow. Values for this field are as follows: • Priority Issue • Defined as a subsequent MarkeTrak issue submitted/resubmitted due to initial MarkeTrak issue being auto closed without resolution or a follow-up MarkeTrak issue exceeding Market accepted SLA. A MarkeTrak issue submitted as ‘Priority Issue’ that does not meet these guidelines may be rejected. • Consumption/Usage Issue • Billing Calculations kWh • Billing Calculations kW • Billing Calculations Power Factor • TDSP Charge Issues • Rate Issues • Crossed Meter Issues • Non-Metered Issues • Other • Comments required

9. MTTF3a – Create Dispute Subtype

10. MTTF3a – Create Dispute Subtype The following fields must be populated for successful submission (required information). • ASSIGNEE • ESI ID • Tran Type • TXN Date • STARTTIME • DISPUTE CATEGORY • IDR/NON-IDR • TRAN Id

11. MTTF3b – Create Missing Subtype • Description: Using the current Usage/Billing workflow, create a distinct Usage and Billing subtype - Missing.

12. MTTF3b – Create Missing Subtype The following fields must be populated for successful submission (required information). • ASSIGNEE • ESI ID • Tran Type • TXN Date • STARTTIME • IDR/NON-IDR

13. MTT4 – New MarkeTrak Admin Workflows

14. MTTF4 – New Admin Workflows – Add User ‘Add User’ function will be added to the Submit Tree under a ‘MarkeTrak Admin’ tab for Administrator use only.

15. MTTF4 – New Admin Workflows – Add User • Submit Transition Fields: • Employee ID – Required • First Name – Required • Middle Name/Initial – Optional • Last Name – Required • Email Address – Required • Phone Number – Required • Validations Performed on Submit Transition: • Email Address is formatted correctly • Phone number has 10 digits • Employee ID is alpha-numeric • Employee ID is not a duplicate

16. MTTF4 – New Admin Workflows – Add User • Employee ID: Enter the Employee ID from the digital certificate. There is no need to precede the Employee ID with duns$. MarkeTrak automatically adds duns$ to the Employee ID. • Enter remaining information making sure telephone number is 10 digits and Email address is formatted correctly. • Your Company duns will be defaulted in the Company field. • User Type: User type will typically be either Regular or MP Admin User. • Select OK to continue.

17. MTTF4 – New Admin Workflows – Add User • Add User issue is created • The Contact Record and Company Association have been created. • Review the information and if edits are needed, select the ‘Re-Select Parameters’ button. Or the user can select Withdraw to cancel the Add User process. • Edit the information and select ‘OK’.

18. MTTF4 – New Admin Workflows – Add User • Select the ‘Commit’ transition to complete the Add User request.

19. MTTF4 – New Admin Workflows – Add User • Add User request is complete and the issue auto closes.

20. MTTF4 – New Admin Workflows – Update User ‘Update User’ link will be added to the Submit Tree under a ‘MarkeTrak Admin’ tab for Administrator use only. Update User through a MarkeTrak workflow will allow for a more efficient means to update user information.

21. MTTF4 – New Admin Workflows – Update User • Company – Your Duns number will be defaulted in this field. • Contact – Enter the user name to be updated or select Find and review the list of users in your company. • Select OK

22. MTTF4 – New Admin Workflows – Update User • Edit User issue is created • From this screen, the MP Admin would either select ‘Edit’ to make changes to the selected user or choose ‘Select Different User’ if the current user selected is incorrect

23. MTTF4 – New Admin Workflows – Update User • The fields appearing in green can be edited. For this example, the email address was modified. • Select OK “Now I’m jdoe@marketraktraining.com!”

24. MTTF4 – New Admin Workflows – Update User • To complete the Update User request, select ‘Commit’. The MP Admin can also ‘Re-Edit User’ or ‘Withdraw’ the issue.

25. MTTF4 – New Admin Workflows – Update User • Update User is complete and the issue auto closes.

26. MTTF4 – New Admin Workflows – Delete User ‘Delete User’ link will be added to the Submit Tree under a ‘MarkeTrak Admin’ tab for Administrator use only. Delete User through a MarkeTrak workflow will allow for a more efficient delete user process.

27. MTTF4 – New Admin Workflows – Delete User • Company – Your Duns number will be defaulted in this field. • Contact – Enter the user name to be deleted or select Find and review the list of users in your company. • Select OK

28. MTTF4 – New Admin Workflows – Delete User • Delete User issue is created • This workflow allows the MP Admin to select a replacement for the user being deleted. If there is no replacement, the value should remain (None). • Enter either a replacement user or leave (None) and select ‘OK’.

29. MTTF4 – New Admin Workflows – Delete User • This workflow allows the MP Admin to view all items owned by the user being deleted. It also provides a means to identify all rolodex entries corresponding to the deleted user. To view issues and rolodex contacts, select the links under Description.

30. MTTF4 – New Admin Workflows – Delete User Owner Report

31. MTTF4 – New Admin Workflows – Delete User Rolodex Report

32. MTTF4 – New Admin Workflows – Delete User • To choose a replacement user, select the Find button and choose a user from the list. • Select ‘OK’.

33. MTTF4 – New Admin Workflows – Delete User • Delete User issue is created • A Review the information and if edits are needed, select the ‘Re-Select Parameters’ button. Or the user can select Withdraw to cancel the Add User process. • Edit the information and select ‘OK’. • To complete the replacement selection, click the ‘Commit’ button. The MP Admin also has an option to select another replacement if necessary by selecting the ‘Re-Select Replacement’ button.

34. MTTF4 – New Admin Workflows – Delete User • Delete User request is complete and the issue auto closes.

35. MTTF4 – New Admin WorkflowsAdmin Reporting • Ability to report against the Add User, Delete User, and Update User workflows

36. MTTF4 – New Admin Workflows Admin Reporting • Report criteria: • Delete User Workflow • All users deleted on or after 1/1/2014

37. MTTF4 – New Admin WorkflowsAdmin Reporting • Delete User issue is created • A Review the information and if edits are needed, select the ‘Re-Select Parameters’ button. Or the user can select Withdraw to cancel the Add User process. • Edit the information and select ‘OK’.

38. MTT5 – Rename Missing TXNs Subtype

39. MTTF5 – Rename Missing TXNs Subtype • Description: Change the name of the subtype ‘Missing TXNs’ to ‘Missing Enrollment TXNs’ to help minimize confusion surrounding which transaction types are available in this subtype. By changing the subtype name, it should provide clarity that only missing enrollment transactions; i.e. 814 tran types and 867_02/867_04 tran types are available for selection. • Impacts: • GUI Submit Tree • API XSD/WSDL • GUI Reports • Background Reports

40. MTTF5 – Rename Missing TXNs Subtype • Subtype name has been updated on the Submit Tree.

41. MTTF5 – Rename Missing TXNs Subtype • Subtype name has been updated for GUI reporting.

42. MTTF5 – Rename Missing TXNs Subtype • Subtype name has been updated in the MarkeTrak Projects list on all Background Report options.

43. MTT8 – Increase Validations on Pre-Defined Field

44. MTTF8 – Increase Validations on Pre-Defined Fields • Increase validations on the Original Tran ID field and the Tran ID field to prevent users from entering invalid data such as dates in the BGN fields. • Error will generate if user attempts to enter invalid data in either of these fields.

45. MTTF8 – Increase Validations on Pre-Defined Fields • Tran ID field cannot contain special characters. For this example, a date is entered in Tran ID field. Error message displays indicating an invalid value for Tran ID. • User corrects the invalid values and selects OK.

46. MTTF8 – Increase Validations on Pre-Defined Fields • Original Tran ID field cannot contain special characters. For this example, a backslash is entered in Original Tran ID field. Error message displays indicating an invalid value for Original Tran ID.

47. MTTF8 – Increase Validations on Pre-Defined Fields • User corrects the information in the Original Tran ID field and selects OK.

48. MTTF8 – Increase Validations on Pre-Defined Fields • Issue successfully creates.

49. MTTF9 – Changes to Inadvertent Losing Workflow

50. MTTF9 – Changes to Inadvertent Losing Workflow • Description: Task Force Participants have requested that on Inadvertent Issues, the workflow and validations be improved 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. • New/Revised Transitions: • Agree – New Transition • Transitioned by Gaining CR to indicate clear agreement on the Inadvertent issue. • Send To Losing CR – Revised Transition • This transition will be used by the Gaining CR to send the issue back to the Losing CR for clarification or information exchange. It is not an indication of agreement to the Inadvertent Loss. • Using this transition could potentially delay resolution of the issue. Market Participants are strongly encouraged to add pertinent information such as customer name in the comments section when submitting the issue. Providing information upon Submit could prevent the need for the Gaining CR to transition the issue back to the Losing CR for additional information or clarification. • Send To TDSP – Revised Transition • This transition will only be available to the Losing CR once the Gaining CR has selected the ‘Agree’ transition. If the Gaining CR selects ‘Send To Losing CR’ instead of the ‘Agree’ transition, the ‘Send To TDSP’ transition will not be available.