1 / 57

SMART METER TEXAS

SMART METER TEXAS. Smart Meter Texas Scope “Summer Release and Fall Approach”. May 25, 2010. Overview of Scope for Summer. Summer Scope Meter Attributes / Capabilities Premise Attributes Monthly Billed Usage Report Customer HAN Device Provisioning and De-Provisioning

daryl
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 Smart Meter Texas Scope “Summer Release and Fall Approach” May 25, 2010

  2. Overview of Scope for Summer • Summer Scope • Meter Attributes / Capabilities • Premise Attributes • Monthly Billed Usage Report • Customer HAN Device Provisioning and De-Provisioning • SMT Automated Reporting of Statistics • REP Web Rebranding (Moved Up from Fall) • Support for Regulatory (Moved Up from Fall) • Support for Supplementals (friends) (Moved Up from Fall)

  3. Overview of Scope for Fall • Fall Scope • On Demand Read (Moved out of Summer) • Event Subscriptions and Notifications • Support for Third Parties • Change Requests

  4. Approach for Fall Design Process • Late July upon request one on one requirements design workshops with REPs to understand individual requirements to ensure that Fall baseline framework for HAN and third parties as well as other functionality will support future needs. • August – September AMIT Fall functionality requirements and design sessions. • August – September parallel AMIT HAN functionality design discussions as appropriate to support Fall third party and other functions. • Late July – September AMIT change request review, design, approval

  5. Meter/Premise Attributes

  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

  7. View Premise Information View Meter Information Export Information View Premise Information View Meter Information Export Information 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 MeterAttributes Export Attributes

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

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

  10. Meter Attributes

  11. Premise Attributes

  12. Meter/Premise Attributes Functional Flow

  13. Monthly Billed Usage

  14. 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,

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

  16. Monthly Billed Usage – UI Design (Customers)

  17. Monthly Billed Usage Monthly Billed Usage – Export Request

  18. Monthly Billed Usage Functional Flow

  19. Customer HAN device provisioning & de-provisioning

  20. Customer HAN Device Provisioning and De-provisioning Overview • 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

  21. Customer HAN Device – Device List Screen

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

  23. HAN Devices > View HAN Devices Customer HAN Device – Provisioning Screen • Page help contains information about where MAC Address and Installation Code may be found. • The tool tip for the MAC Address and the Installation Code fields will display allowed characters and an example of what these fields look like. • Confirmation Page displayed after Add a HAN Device informs the user that the Add request has been received and that he should check back the status of the request in a few minutes.

  24. HAN Devices > View HAN Devices Customer HAN Device – De-provisioning Screen • Reason for Removing is not a required field for Customers. • Confirmation Page displayed after Remove a HAN Device informs the user that the Remove request has been received and that he should check back the status of the request in a few minutes.

  25. HAN Devices > View HAN Devices Customer HAN Device – Device Details New column to be added to this table will display who added the request. -Residential Customer’s Name -NRC Company Name -Name of the ROR -Name of the TDSP

  26. HAN Devices > View HAN Devices Customer HAN Device – Provisioning History New column to be added to this table will display who added the request. -Residential Customer’s Name -NRC Company Name -Name of the ROR -Name of the TDSP

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

  28. SMT Automated Reporting of Statistics

  29. 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.

  30. Rep Web Rebranding

  31. REP Web Re-branding Requirements and Options • Two methods for interpreting the stated requirements • (Synchronous Web Services) API for small amounts of data • Java Portlet Specification 2.0 (JSR 286) • Both are machine-to-machine APIs • Both offer different strengths/weaknesses

  32. REP Web Re-branding API REP uses SMT data to present varied views of customer usage REP Portal API Smart Meter Texas IntegrationEnvironment End-Customer Varieddataviews SMT Portal

  33. SMT is Recommending the API Option • (Synchronous Web Services) API for small amounts of data • Pros • Leverages the existing ad-hoc usage query and HAN web services security infrastructure • REPs do not need to build a portal to use this API • REPs have unrestricted ability to innovate around the services they offer to customers • For example. A unified view of interval, daily register and monthly billed usage data or advanced analytics • Cons • REPs with existing Portals have to build their own portlets • Java Portlet Specification 2.0 (JSR 286) • Pros • REPs do not need to build portlets but still must have or implement a portal • Cons • REP portals are limited to reporting functionality implemented by SMT • REPs customer account information must be in SMT • Requires federated identity management • JSR implementation is more complex than web service implementation (SMT assessment)

  34. REP Web Re-branding Proposal • Re-branding is available to ROR only • SMT will provide synchronous versions of existing APIs • Interval Data, Daily Usage, Billed Usage • Invocations secured using existing system account & credential exchange • Leverages the R1 HAN and ad-hoc query infrastructure • Synchronous limits are strictly enforced • 1 ESI ID/40 days for Intervals • 1 ESI ID/40 days for Daily Registers • 1 ESI ID/24 months for Monthly Billed Usage • REP responsibilities • Development of their own portlets • Assuring the user has proper access to the data • ROR authorizes user access to the ESIID • SMT validates the ROR system account and ROR access to the ESIID • Not in scope • Assistance in developing REP software

  35. Support for Regulatory

  36. Registration Host will setup the initial Regulatory administrative (first admin) accounts Regulatory Admins & Users will have access to ALL ESI IDs Reporting Have access to existing portal UI usage reporting Interval usage, daily meter read usage, and billed usage No access to premise and meter detailed data Batch reporting upon request for PUCT History of SMT Access by person (who, frequency, duration) (BR-028.008) History of 3rd Party Access (who, duration) (BR-028.009) Report output will be delivered encrypted to the PUCT Entity email address, regardless of who requests the report (CSV format) Data Extracts by Request No automatic files for Regulatory Users Not in scope Ad-hoc undefined reports HAN functionality Regulatory Overview

  37. Regulatory Entity Regulatory Entity View meter usage data for all Texas Smart meters. View meter usage data for all Texas Smart meters. • • Request Access to an Existing Regulatory Account Request Access to an Existing Regulatory Account or see if your Regulatory entity is already registered. or see if your Regulatory entity is already registered. Regulatory Registration Access will be via Private URL

  38. Reporting: History of SMT Access by Person

  39. Reporting: History of 3rd Party Access This report is contingent upon development for the 3rd Party role. It is being removed from the Summer release and will be bundled with the 3rd Party functionality in the Fall release.

  40. Support for Supplementals (Friends and family)

  41. Master Agreement One Master Agreement defines that there is a relationship between the Customer & the Friend Master Agreement ties to Friends by UserID, once active Pending Friend agreement contains Key + Email Either party may end the agreement at will ESI ID Agreement Customer may add or remove ESI IDs to the Master Agreement Tied to Master by prefix on Agreement-ID Customer may change permissions at will Friend has view-only to ESI ID Agreement Supplemental (Friends) Concepts

  42. RES Customer as Supplemental Only Residential accounts are eligible to be Supplemental Users Non-existent SMT User Registration Only Residential Customers can invite people to register as a Supplemental Registration as a Supplemental User (not an existing RES Customer) is by Residential Customer invitation (Agreement Key) SMT matches on email address and Agreement Key Supplemental (Friends) Overview

  43. Access to data is authorized by Customers Only Residential Customers can create Friend Agreements Customer creates a Master Agreement with the Friend Customer may have a maximum of 5 Friends Customer grants access by creating ESI ID Agreements under the Master Agreement ESI ID Agreements have no expiration date but can be removed at any time Authorization for ‘data’ includes interval usage (13 months), daily meter reads (13 months), billed usage (24 months), Access is granted by email address and agreement key (email address is not unique in SMT); relationship is with Friend’s UserID once the Friend accepts the Master Agreement Supplemental (Friends) Overview

  44. Create a New Friend Master Agreement

  45. Friends My Friends Add A Friend Add Agreement Edit Agreement Edit Agreement Remove Agreement Remove Agreement Add a Friend Add Agreement Edit Agreement Edit Agreement Remove Agreement Remove Agreement Customer View: Existing Friend Agreements Remove will display pop-up asking for confirmation Edit will allow adding / removing meters & permissions

  46. Friends > Add a Friend Friends > Add a Friend Add a Friend Add a Friend Add Friend Add Friend Cancel Cancel Customer View: Add a Friend

  47. Friends > Edit Friend Agreement Friends > Edit Friend Agreement Edit My Friend Agreement • • 1234567-00001, Doe, John, johndoe@anonymous.com Add a Meter to Agreement Add a Meter to Agreement Update Update Remove Meter Remove Meter Add a Meter to Agreement Add a Meter to Agreement Update Update Remove Meter Remove Meter Back Back Customer View: Edit Friend Agreement X X These are existing meters that are already included in the Agreement • No Data checkbox – Friend automatically gets usage • All Friend Agreements are perpetual – do not expire Notifications has been removed from this release.

  48. Friends > Edit Friend Agreement > Add a Meter to Agreement Friends > Edit Friend Agreement > Add a Meter to Agreement My Friend Agreement • • 1234567-0000, Doe, John, johndoe@anonymous.com Select Smart Meters to add to your Friend Agreement: Select Smart Meters to add to your Friend Agreement: Add Meters to Agreement Add Meters to Agreement Notifications Notifications Notifications Add Meters to Agreement Add Meters to Agreement Cancel Cancel Customer View: Add a Meter to a Friend Agreement X These are meters attached to the customer account that can be added to the Agreement Notifications are in the Fall release.

  49. Friend Accepts Master Agreement

  50. Friend (invited by a Residential Customer) Friend (invited by a Residential Customer) Friend (invited by a Residential Customer) You have been invited by an existing Residential Customer. You have been invited by an existing Residential Customer. You have been invited by an existing Residential Customer. • • • View your friend View your friend View your friend ’ ’ ’ s electricity usage. s electricity usage. s electricity usage. • • • Create a Friend Account Create a Friend Account Create a Friend Account 3 3 3 Party Party Party rd rd rd Create an account to view Smart Meter Texas data for a customer. Create an account to view Smart Meter Texas data for a customer. Create an account to view Smart Meter Texas data for a customer. • • • The Customer must grant you permission to view usage. The Customer must grant you permission to view usage. The Customer must grant you permission to view usage. • • • Friend Registration Access will be via Public URL

More Related