1. 1 HAN Device Status Report Storyboard Smart Meter Texas Release 4.0 Requirements February 21, 2012 DRAFT

2. This scope is a combination of 3 CRs and 1 BR CR029 – REP Recurring HAN status report and API Ad Hoc Query for Exception Checking HAN Provisioned Devices –Title: Request to send SMT HAN Device Status report via FTPS –Change the delivery method of the Daily SMT HAN Device Status report from direct email to availability via FTPS. CR026 - HAN APIs to Include Status Information in a Timely Manner –Title: HAN API provisioning and deprovisioning status return –Issue: Current functionality of the SMT HAN provisioning/De-provisioning API doesn’t return the resulting status of the API call through a synchronous or asynchronous means, but only updates the SMT database with the status where it can be viewed via the Web GUI. –Consequence: If a HAN fails to provision and a customer attempts to install, the HAN device join will fail and best case will result in a customer call to the help desk. Worst case the customer will be dissatisfied and return the device to the provider. –Request: Our request is to provide the device status data back at the device level from the associate API request in a way that it can be consumed in an automated manner by the requesting party in a timely fashion. –As a workaround in the interim, we request to have available a daily status report of all that day’s API provisioning requests available via FTP. 2

3. This scope is a combination of 3 CRs and 1 BR BR400 - De-provisioning Reason and Source Reporting –Ability for an authorized user to extract and report on reasons and source for why a device(s) was de-provisioned based on defined roles CR031 - TDSP HAN Device Status Report –Daily Report, run automatically same time every day, by SMT –All HAN devices within SMT associated with TDSP – MAC Address and Installation Code –Associated ESI Id and Meter Id –All HAN device status transactions (including historical) with event type, status, and data and time stamp (the current Reliant Report can be used as an example) –Identification of originator of provision/deprovision request – Id and Name Description –Creation of an TDSP FTP folder within SMT for direct deposit – 10 day limit on file storage 3

4. HAN Status Report Storyboard REP, 3rd Party or TDSP initiates a HAN Status Report request via a call to the SMT Call Center SMT Call Center receives a request for HAN Status Report and logs a ticket SMT Production Support Team receive the ticket from the SMT Call Center SMT Production Support team adds to the list of HAN Status Reports REP, 3 rd Party or TDSP initiates a HAN Status Report via an API call SMT receives the request via API SMT creates adds to the list of requested HAN Status Reports SMT runs a job in after hours to generate the HAN Status Reports Comprehensive HAN Status reports are dropped in the FTP site on a daily basis. REP, 3 rd Party or TDSP retrieve the Status report from the FTP site Incremental Intraday HAN Status reports are delivered via synchronous API in XML REP or 3 rd Party receive the report via API 4 123456789101112

5. 5 REP, 3rd Party or TDSP initiates a HAN status Report request Request via Call Center HAN Status Report Story Board 1 SMT Call Center receives request for HAN Status Report 2 SMT Production Support receives a ticket from the call center 3 REP, 3rd Party or TDSP initiate an API call for HAN status report Request via API 5 SMT receives the API call 6 SMT adds to the list of HAN Status Report requests 7 SMT Production Support adds to the list of HAN status Report requests 4 SMT runs a job against the request list 8 9 REP, 3 rd Party or TDSP retrieve the report from FTP 10 SMT Processes Request Incremental Intraday HAN Status reports are delivered via synchronous API in XML 11 REP or 3 rd Party receive the report via API 12 Comprehensive HAN Status reports are dropped in the FTP site on a daily basis.

6. HAN Device Status Report - Overview 6 RequesterRequest ChannelRequest TypeReport Generation ProcessDelivery Channel 1 REP/ 3rd PartyCall comes into SMT Call Center Recurring Comprehensive HAN Status Device report requested Report is for 60 days SMT Production Support receives a ticket from the call center SMT Production Support adds to the list of HAN status Report requests SMT runs a job against the request list The Comprehensive HAN Status reports are dropped in the SMT FTP site on a daily basis 2 REP/ 3rd PartyInitiate an API callComprehensive HAN Device Status report requested Report is for 1 day The request is added to the list of HAN status Report requests SMT runs a job against the request list The Comprehensive HAN Status reports are dropped in the FTP site on a daily basis 3 REP/ 3rd PartyInitiate an API callIncremental Intraday HAN Status report requested REP/ 3 rd Party may invoke the request 3 times during the day The request is added to queue and processed as soon as processing is available The Incremental Intraday HAN Status report is delivered by API in synchronous fashion in XML format 4 TDSPCall comes into SMT Call Center Comprehensive HAN Device Status report requested Report is for 1 day SMT Production Support receives a ticket from the call center SMT Production Support adds to the list of HAN status Report requests SMT runs a job against the request list The Comprehensive HAN Status reports are dropped in the SMT FTP site on a daily basis

7. REP, 3rd Party or TDSP initiates a HAN status Report request via Call Center 7 REP, 3rd Party or TDSP initiates a HAN status Report request 1 SMT Call Center receives request for HAN Status Report 2 SMT Production Support receives a ticket from the call center 3 3 rd Parties will have to provide the e- mail address that the active consumer accounts are linked to  Have a relationship in SMT with the e-mail address provided by the 3 rd Party  Have granted the 3 rd Party authorization to provision/ de-provision HAN devices  Have a relationship in SMT with the e-mail address provided by the 3 rd Party  Have granted the 3 rd Party authorization to provision/ de-provision HAN devices For REPs the list is generated for accounts which are currently in ROR A Request Lifecycle rule applies – recurring requests are kept on the list for a period of 60 days after which they are deleted from the list For 3rd Parties, the list is generated for accounts which: There are 2 types of requests that can be made: 1.REPs or 3 rd Parties will ask to be enrolled in recurring auto reports. This will allow them to receive a recurring daily report for a specific period of time (60 days) 2.TDSPs will ask for an auto report for HAN statuses for a single day There are 2 types of requests that can be made: 1.REPs or 3 rd Parties will ask to be enrolled in recurring auto reports. This will allow them to receive a recurring daily report for a specific period of time (60 days) 2.TDSPs will ask for an auto report for HAN statuses for a single day SMT Production Support adds to the list of HAN status Report requests 4

8. REP, 3rd Party or TDSP initiates a HAN status Report request via API 8 REPs or 3 rd Parties initiate an API call for HAN status report 5 SMT receives the API call 6 SMT adds to the list of HAN Status Report requests 7 3rd Parties will have to provide the e-mail address that the active consumer accounts are linked to  Have a relationship in SMT with the e-mail address provided by the 3 rd Party  Have granted the 3 rd Party authorization to provision/ de- provision HAN devices For REPs the list is generated for accounts which are currently in ROR A Request Lifecycle rule applies – recurring requests are kept on the list for a period of 60 days after which they are deleted from the list For 3rd Parties, the list is generated for accounts which : 2 types of reports can be transmitted via API: 1.REPs or 3 rd Parties can request HAN Device Status Auto-Report for a single day. 2.REPs or 3 rd Parties can request Incremental Reports. These reports may be requested 3 times a day – this interval will be reviewed once the exact load generated by the requests is estimated. First request generates report from the midnight to the time the request for received. Following request generate report for interval between last and the new request.

9. 9 Comprehensive HAN Status reports are dropped in the FTP site on a daily basis SMT runs a job against the request list 8 The HAN Status reports are dropped in the FTP site 9 REP, 3 rd Party or TDSP retrieve the report from FTP 10 The jobs are run daily at a pre-set time at night The current FTP Lifecycle Rule applies – reports are kept on the FTP site for a period of 10 days after which they are deleted A standardized report format is applied which includes parameters like – ESI ID, Meter no, MAC Address, Event Type, Status Description, Provision Response Date Requester retrieves the Report from the FTP site A functionality will be added to SMT UI which will allow a consumer to select a HAN device Provisioning/ De Provisioning reason. Reasons include but are not limited to: Customer Requested Malfunctioning Device Unsupported Device Request Provision By Mistake Other De-provisioning reason code Example Report:

10. 10 Incremental Intraday HAN Status reports are delivered via synchronous API in XML SMT runs a job against the request list 8 The HAN Status reports are returned via API 11 REPs or 3 rd Parties retrieve the reports via API 12 The jobs are run daily at a pre-set time at night The current FTP Lifecycle Rule applies – reports are kept on the FTP site for a period of 10 days after which they are deleted A standardized report format is applied which includes parameters like – ESI ID, Meter no, MAC Address, Event Type, Status Description, Provision Response Date Requester retrieves the Report from the FTP site A functionality will be added to SMT UI which will allow a consumer to select a HAN device Provisioning/ De Provisioning reason. Reasons include but are not limited to: Customer Requested Malfunctioning Device Unsupported Device Request Provision By Mistake Other De-provisioning reason code Final Reason code will be finalized through AMIT input. Example Report:

11. 11 RES or Business users who de-provision a device will navigate to the Remove HAN Device page The consumer navigates to My Account /HAN Devices/HAN Devices. There are no changes to these 2 pages

12. 12 Once at the Remove HAN Device page, the RES or Business optionally chooses the Reason Code and writes Reason Comments prior to clicking the Remove HAN Device button Current Reason Codes: RepRequested CustomerRequested MalfunctioningDevice UnsupportedDevice RequestProvByMistake NetworkInterference Other The Reason Code pull down is added to the My Account / HAN Devices / HAN Devices / Remove HAN Device page. The current Reason Codes are shown below. AMIT needs to determine which of these reasons or any new reasons to be added to this choice list.