© 2012 IBM Corporation 3 rd Party Registration & Account Management 1 1 SMT Post R 4.3 Potential Enhancements

© 2012 IBM Corporation

3rd Party Registration &Account Management3rd Party Registration &Account Management

1 1

SMT Post R 4.3 Potential Enhancements



2

Potential Enhancements Inventory

# Description

1 Improve error messages displayed in SMT Portal

2 Add Customer Type and Customer Address in the Customer Information section

3 Improve REP-of-Record ROR search criteria

4 Keep ROR during customer registration process

5 Allow multiple ESIIDs during customer registration for SMT account

6 Provide another mechanism to send and accept Customer Agreements

7 Ability to renew an Energy Data Agreement after one year

8 Ability to hold Third Party account for 60 days

9 Add identifying data fields in Report Request Status page

10 Display portal message when report cannot be displayed in the portal page

11 Add customized usage data buttons

12 Allow User to Enter Start Date and End Date on Export Report page

13 Allow user to copy and paste in the ESIID box in the Usage page

14 Improve TDSP Data / User functionality



Item # 1 – Improve Error Messages displayed in SMT Portal

Improve Error Messages

During Agreement Invitation process, the error messages displayed in the Portal invitation page are generic. They do not display the reason why the agreement invitation failed. REPs and Third Parties do not know if the cause of the error was invalid entry (user error) or invalid data provided by their customers.

Add Customer Type in the Customer Information section of the View / Edit Customer Agreement page.

Examples:

• REPs and Third Parties are unaware if email address provided by the customer is already registered with SMT

• REPs and Third Parties are unaware if Account Authorization Code provided by the customers is invalid

• They do not know if customer does not have Smart Meter yet

REP and Third Party User Experience will be enhanced if they understand why Agreement Invitations failed, instead of deciphering from a list of generic error messages.



Item # 2 – Add Customer Type and Customer Address

Customer Type

Add Customer Type in the Customer Information section of the View / Edit Customer Agreement page.

Customer Address

The Service Address of the Customer Information section of the View / Edit Customer Agreement page always displays N/A. It unnecessarily gives the impression that something may be wrong.

Options:

• Remove the Service Address in the Customer Information section

• Change Service Address to the physical Customer Address



Item # 3 – Improve REP-of-Record ROR search criteria

REP-of-Record ROR Search

Allow keywords with and without asterisk in Search criteria.

Example:

Typing AMIGO did not yield results, but typing AMIGO* (with asterisk) did. Allow AMIGO and AMIGO* in search text box.

Allowing both criteria enhances Customer experience when choosing REP-of-Record during customer registration process



Item # 4 – Keep ROR during Customer Registration

ROR field during Customer Registration

Customer Registration User Experience

During customer registration process, if “Previous” button was clicked, the previously entered ROR was removed. The Customer is required to re-enter ROR information.

Customer Registration User Experience – The Customer does not need to re-enter previously entered information.



Item # 5 – Allow Multiple ESIIDs during Customer Registration

Multiple ESIIDs during Customer Registration

Provide the customer an option to enter single or multiple ESIIDs during customer registration for SMT account.



Item # 6 – Provide Another Mechanism to Send and Accept Customer Agreements

Another Mechanism to Send and Accept Customer Agreements

The Texas Low Income program was created to provide users without internet access the ability to view their energy usage and take advantage of smart meter benefits.

Third Parties are required to establish In-Home Device Agreement with a Customer in order to provision an In-Home Device to a Customer’s meter. The Customer will provide the authorization to Third Parties by accepting the agreement via email or by accessing SMT Portal.

Provide another mechanism other than email / SMT website to send and accept customer agreements. Allow in-person or phone authorization and acceptance by the Customers in order to establish Third Party Agreements – Energy Data Agreement, In-Home Device Agreement and In-Home Device Services Agreement to ensure that all low income customers in Texas are allowed to participate in this program.



Item # 7 – Ability to Renew an Energy Data Agreement after One Year

Renew Energy Data Agreement after one year

The current maximum agreement duration for Energy Data Agreement is one year only. Provide the ability to renew Energy Data Agreement after one year.



Item # 8 – Ability to hold a Third Party account for 60 days

Hold Third Party Account for 60 Days

When Third Party SMT Account registration is approved, it gives them the ability to utilize SMT Portal to initiate customer usage requests and schedule report requests even though they have not completed FTP and API integration with SMT.

The ability to hold Third Party Accounts for 60 days provide the assurance that Third Party will complete the required integration and connectivity processes with SMT.



Item # 9 – Add Identifying Data Fields in Report Request Status page

New Data Fields in Report Request Status page

REP / Third Party User Experience – Report Type, Start Date, End Date, Customer Name, ESIID etc would provide distinguishable features on the screen which will aid the REPs and Third Parties in locating customer’s data which had previously been requested / exported.



Item # 10 – Display Portal Message when report cannot be displayed in the SMT page

Portal Message

The “Update Report” button gives the impression that the report will be displayed in the SMT page. However if the dates are set further apart, i.e. outside of the allowed date range, an Order ID was generated instead of displaying the report in the current page.

If the requested date range will not fit on the page when “Update Report” button is clicked, display a Portal Message to inform the user and give the user an option if they would like to receive the report via email.

• Yes – will process the request as a report (existing logic)

• No / Cancel – cancels the user’s request and send them back to the Usage Report page where the user can enter a different date range



Item # 11 – Add Customized Usage Data Buttons

Customized Usage Buttons

Add customized Usage Data buttons to provide REPs, Third Parties and Customers the ability to export the latest 12 months of 15-Min, Daily and Monthly usage data without the need to enter the start date and end date.

Furthermore, if the start date and end date do not provide the full 365 days of usage data, expand the usage date range to have 7 days of cushion in order for the REP, Third Party and Customer to have a full set of 365 days of usage data.



Item # 12 – Allow User to Enter Start Date and End Date on Export Report page

Start and End Dates on Export Report page

Allow the user to enter dates on the Export Report screen, in addition to selecting dates from the Calendar drop down.



Item # 13 – Allow Copy and Paste in the ESIID Box in the Usage page

ESIID Box

Allow the user to copy and paste data in the ESIID box in the Usage page.

-Allow pasting of 7 digit ESIID, and then pasting of 10 digit prefix in front-Allow copy pasting a list of ESIIDs, then add commas using keyboard instead of using the mouse to set the cursor at the end of each ESIID



Item # 14 – Improve TDSP Data / User Functionality

TDSP Data / User functionality

• Ability to view all the versions of a Day’s Reads with the date loaded.

• Ability to see all Version of Daily Read data in the extracts reports.

• Ability to pull in the Register Read quality code in header row 3 of the LSE data and present that in SMT.•Note: Oncor is the only TDSP that puts a quality code in the LSE files.

Documents

© 2012 IBM Corporation 3 rd Party Registration & Account Management 1 1 SMT Post R 4.3 Potential Enhancements