1 / 50

SMART METER TEXAS

SMART METER TEXAS. Proposed Scope for the Summer Release. April 19-20, 2010. 1. AMIT has asked the SMT Team to present the following on 4/19-20. SMT OBJECTIVES from March 30

fanchon
Download Presentation

SMART METER TEXAS

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. SMART METERTEXAS Proposed Scope for the Summer Release April 19-20, 2010 1

  2. AMIT has asked the SMT Team to present the following on 4/19-20 SMT OBJECTIVES from March 30 OBJ-024 - Implement a shorter time period (sooner than the day after the meter read) for VEE or potentially raw customer 15 minute interval usage data to show up on the portal OBJ-025 - Implement automated reporting of statistics, performance measures and monitoring capabilities of portal usage. OBJ-026 - Provide automated reporting to the market of statistics, performance measures and monitoring capabilities of portal usage. OBJ-027 – Implement self-registration on the SMT for the REPs and Non-residential Customers OBJ-029 – Implement the capability for power outage information to be available to the customer through the portal at the customer’s option. OBJ-030 – Automate provisioning and de-provisioning of HAN devices for customers and Non-Residential customers through the portal UI. OBJ-031 – Provide the capability to access meter attribute and meter capability information on the portal 2

  3. Recap Example on the Functionality Matrix Green = Delivered Blue = In Process for Delivery * = SMT Has Functionality but not supported by current technology Yellow = Proposed for Summer Release (AMIT Requested) Orange = Proposed for Summer Release (SMT Suggested) Purple = Requested but not available Summer Release 3

  4. Propose scope for a “summer” release • Meter attributes • Customer HAN device provisioning and de-provisioning • SMT automated reporting of statistics • SMT is proposing additions to the summer release • Premise attributes • Monthly billed usage • On-demand meter read/power status • Customer HAN device details and device history • Event subscription and notifications will be included in a future release 4

  5. Meter/Premise Attributes 5

  6. Meter/Premise Attributes Overview • Meter and premise attributes will be available through SMT to the ROR, TDSPs, SMT Host, and Customers • Can view, print and download Meter/Premise attributes for 1 ESIID at a time in Portal • Can download Meter/Premise attributes for multiple ESIIDs via Portal or API • Attributes read from SMT database • SMT presents what is online • Same attributes are presented to all user types • Not in Scope • Support for 3rd parties, Supplemental, Regulatory • Sorting/editing attributes 6

  7. Meter/Premise Attributes – UI Design (REPs and TDSPs) Meter and Premise attributes would be available from My Account / Search A button will be added that links to a new Meter/Premise attributes page Export would be available from that page My Account Search View PremiseAttributes View Premise Attributes View Meter Attributes Export Attributes View MeterAttributes View Premise Attributes View Meter Attributes Export Attributes Export Attributes 7

  8. View Premise Attributes View Meter Attributes Export Attributes Meter/Premise Attributes – UI Design (Customers) 8

  9. Premise Attributes Meter Attributes Meter/Premise Attributes – Export Request 9

  10. Meter/Premise Attributes Functionality Matrix OBJ-031 – Provide the capability to access meter attribute and meter capability information on the portal Green = Delivered Blue = In Process for Delivery * = SMT Has Functionality but not supported by current technology Yellow = Proposed for Summer Release (AMIT Requested) Orange = Proposed for Summer Release (SMT Suggested) Purple = Requested but not available Summer Release 10

  11. Meter Attributes 11

  12. Premise Attributes 12

  13. Meter/Premise Attributes Functional Flow 13

  14. Meter/Premise Attributes Portal UI Technical Flow 14

  15. Meter/Premise Attributes Portal API Technical Flow 15

  16. Monthly Billed Usage 16

  17. Monthly Billed Usage Overview • Customers, ROR, TDSP, SMT Host will have access to Monthly Billed Usage • Usage data read from SMT database • SMT presents what is online • Monthly billed usage is accessed via the API or UI • API access to billed usage (BR- 004.004) • Access via UI (BR-004 and BR-008) • Default: previous 12 months displayed • Maximum accessible: previous 24 months • UI capabilities • UI allows viewing monthly billed usage for 1 ESIID at a time • Display, print and export all monthly billed usage data elements (BR-004.004) • Graph kWh only (BR-004.006/8) • Standard bar graph • View updates/multiple versions – ROR and TDSP (BR-008) • Change time period to be displayed (BR-004.003) • Not in Scope • Support for 3rd parties, Supplemental, Regulatory 17

  18. Monthly Billed Usage – UI Design (REPs and TDSPs) Billed usage would be offered as another report type Exported like other reports 18

  19. Monthly Billed Usage – UI Design (Customers) 19

  20. Monthly Billed Usage Monthly Billed Usage – Export Request 20

  21. Monthly Billed Usage Functionality Matrix Green = Delivered Blue = In Process for Delivery * = SMT Has Functionality but not supported by current technology Yellow = Proposed for Summer Release (AMIT Requested) Orange = Proposed for Summer Release (SMT Suggested) Purple = Requested but not available Summer Release 21

  22. Monthly Billed Usage Functional Flow 22

  23. Monthly Billed Usage Portal UI Technical Flow 23

  24. Monthly Billed Usage Portal API Technical Flow 24

  25. On-demand meter Read/ Power Status 25

  26. On-Demand Meter Read/Power Status Overview • Provided to the ROR and TDSPs • Meter Read returns the current meter read • Power status returns on/off (line side) • One ESIID/MeterID per request (BR-006.006) • The lifecycle of a request is until midnight the day of the request • Invoked via UI • Always executed asynchronously • Invoked via Usage tab as option within customer meters • Response shown on UI • RORs are limited to: • 1 successful power status request per day per ESIID , and • 1 successful meter read per day per ESIID • Not in Scope • Other meter data • Asset information, for example firmware release • Other units of measure, for example, KVAR or generation register • Load side power status • Support for Customers, 3rd parties, Supplemental, Regulatory 26

  27. On-Demand Meter Read / Power Status – Search Screen Usage Search On-Demand Page Power Status/History Meter Read/History Meter Read and Power Status Meter Read and Power Status Button is only available if 1 ESIID is selected Meter Read and Power Status 27

  28. On-Demand Meter Read and Power Status –Request and History Screen • Page has 3 sections • Last read & power status • Request identifier • Request history • The last read for the ESIID is presented in the top section on the meter image • Last LSE value or on-demand read – whichever is most recent • Power status and meter read buttons will be enabled if that operation is allow for the ESIID • See on-demand invocation rules (next page) • Request identifier section is blank initially • Blank until a request is submitted and while in process • A request id appears if a request is invoked • If the page is re-loaded while the request is in process, in-process status appears in this section • Bottom section includes an invocation history • Displays status for requests submitted since midnight • Portal status information • Loaded when the page is entered • If a power status or read request is invoked, the page must be reloaded to see it in the history Usage / Search / On-Demand On-Demand Read / Power Status MM/DD/YYYY ESI ID: XXXXXXXXXXXXXXXX Meter ID: YYYYYYYYYYYYYYYY Last Read Date: mm/dd/yyyy hh:mm:ss Check Power Status Read Meter Power Status Request 123 has been submitted ID Date Time Status xxx xx/xx/xx hh:mm:ss Power status request failed xxy xx/xx/xx hh:mm:sT Power status is ON xyy xx/xx/xx hh:mN:ss Meter read request failed xyz xx/xx/xx hh:mN:sZ Meter read request returned 527.81 28

  29. On-Demand Meter Read / Power Status Invocation Rules • On-Demand functions • Power status • Meter read • A time out period will be associated with on-demand functions • Time out period is the expected time to complete an on-demand function • Estimated at 15 minutes • After a function is invoked, SMT will not accept another request (same function, same ESIID) until • Time out ends or function completes • Handling success and failure • If the power status returns successfully, no further power status requests are allowed for the day for that ESIID • If the meter read returns successfully, no further meter read requests are allowed for the day for that ESIID • If the function fails, that function for the ESIID is re-enabled • If the function completes successfully after the time out period, that function for that ESIID is disabled through the end of the day 29

  30. On-Demand Meter Read/Power Status Functionality Matrix Green = Delivered Blue = In Process for Delivery * = SMT Has Functionality but not supported by current technology Yellow = Proposed for Summer Release (AMIT Requested) Orange = Proposed for Summer Release (SMT Suggested) Purple = Requested but not available Summer Release 30

  31. On-Demand Meter Read/Power Status Functional Flow *REP =ROR 31

  32. On-Demand Meter Read Technical Flow 32

  33. On-Demand Power Status Technical Flow 33

  34. Customer HAN device provisioning & de-provisioning 34

  35. Customer HAN Device Provisioning and De-provisioning Overview * REP= ROR. Additional content will be added to the user guide and FAQs to explain to the user that provisioning and de-provisioning is not instantaneous. • Residential Customers and Non-Residential Administrators are automatically granted HAN rights • HAN rights will be granted on an all-or-nothing basis per Release 1.0 • Non-Residential Administrators can grant HAN access rights to Non-Residential users • Customers screen functionality • Provisioning, De-provisioning • HAN Details and View History • Will reuse REP/TDSP screens • Provisioner role will be added to device history • A maximum of 5 (Customer and REP) devices slots can be allocated (HAN Device Check) • Design does not include restrictions on messaging based on “provisioner” • ROR can send Smart Energy Profile 1.0 messages to any devices • No special restrictions need to be designed for de-provisioning devices – For example: • REPs can de-provision customer-provisioned devices • Customers can de-provision REP-provisioned devices • Not in Scope • Smart Energy Profile 1.0 messaging for customers • Customer provisioning & de-provisioning via API • Customers access to Message Log functionality 35

  36. Customer HAN Device – Device List Screen 36

  37. HAN Devices > Customer HAN Device – ESIID List View 37

  38. HAN Devices > View HAN Devices Customer HAN Device – Provisioning Screen*Add tool tip to MAC address and installation code what they may look like ( an example) and what characters are acceptable. Add to page help a description of where the MAC address and installation code may be found. A message will be displayed after clicking “Add HAN Device” letting the user know that the request has been submitted. Please check back in a few minutes. 38

  39. HAN Devices > View HAN Devices Customer HAN Device – De-provisioning Screen*Remove requirement for “Reason for Removing”.A message will be displayed after clicking “Remove HAN Device” letting the user know that the request has been submitted. Please check back in a few minutes 39

  40. HAN Devices > View HAN Devices Customer HAN Device – Device Details 40

  41. HAN Devices > View HAN Devices Customer HAN Device – Provisioning History 41

  42. Customer HAN Device Functionality Matrix Green = Delivered Blue = In Process for Delivery * = SMT Has Functionality but not supported by current technology Yellow = Proposed for Summer Release (AMIT Requested) Orange = Proposed for Summer Release (SMT Suggested) Purple = Requested but not available Summer Release OBJ-030 – Automate provisioning and de-provisioning of HAN devices for customers and Non-Residential customers through the portal UI. 42

  43. Customer HAN Device Provisioning and De-provisioning Functional Flow 43

  44. Customer HAN Device Provisioning Technical Flow 44

  45. Customer HAN Device De-provisioning Technical Flow 45

  46. SMT Automated Reporting of Statistics 46

  47. SMT Automated Reporting of Statistics Overview • REPs, Regulatory and TDSPs • Report items are at right • Report will be created weekly and filed by a TDSP in project 34610. The TDSPs will include in their monthly compliance reports that they have filed the SMT status weekly in 34610. 47

  48. SMT Automated Reporting of Statistics Functionality Matrix Green = Delivered Blue = In Process for Delivery * = SMT Has Functionality but not supported by current technology Yellow = Proposed for Summer Release (AMIT Requested) Orange = Proposed for Summer Release (SMT Suggested) Purple = Requested but not available Summer Release OBJ-025 - Implement automated reporting of statistics, performance measures and monitoring capabilities of portal usage OBJ-026 – Provide automated reporting to the market of statistics, performance measures and monitoring capabilities of portal usage. 48

  49. Next steps SMT to provide an implementation schedule 49

  50. Thank You For The Opportunity To Discuss SMART METER TEXAS 50

More Related