Proposed Scope for the Summer Release 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 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

Recap Example on the Functionality Matrix   Residential Customer Non-Residential User Non-Residential Admin REP User REP Admin TDSP User TDSP Admin Portal Host / SMT Supplemental User 3rd Party User 3rd Party Admin Regulatory User Regulatory Admin Alert/Event Management Set Broadcast Messages M1 View Broadcast Messages Authenticated Users View Broadcast Messages Unauthenticated Users Subscribe to Alerts for Meter Events -- My ESIIDs M3 / OBJ 29 Subscribe to Alerts for Meter Events -- ROR ESIIDs M3 Subscribe to Alerts for Meter Events -- TDSP ESIIDs Subscribe to Alerts for Meter Events -- ALL ESIIDs Subscribe to Portal Events M3 TBD Distribute Alert Messages to Subscribers HAN Functions Grant and Revoke HAN Granular Permissions H3 View, Print or Extract HAN Granular Permissions Grant the Admin HAN Access Automatically H2 Grant / Revoke HAN Access to REP Portal User Grant / Revoke HAN Access to TDSP Portal User Provision HAN Device via GUI H3 / OBJ 30 Provision HAN Device via API H3 TBD De-Provision HAN Device via GUI De-Provision HAN Device via API Display reason for deprovision of a HAN device H2 TBD Delete pending provision request View HAN Devices by ESIID (Current Status) View HAN Device Details View HAN Device History Send Text Message via API Cancel Text Message via API Send Load Control Message via API Cancel Load Control Message via API Cancel All Load Control Events via API Send Price Signal via API Send a single message to a single HAN device H3* Send a single message to multiple HAN devices Assign Message Priority Ping ESI Ping HAN Device Notify authorized user of normal operations status of ESI Notify authorized user of status of HAN device View HAN Message Log Report View message sent from HAN device View status of message Create ESIID groups 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

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

Meter/Premise Attributes 5

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

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 View Premise Attributes View Meter Attributes Export Attributes My Account Search View Premise Attributes View Meter Attributes Export Attributes 7

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

Meter/Premise Attributes – Export Request Meter Attributes 9

Meter/Premise Attributes Functionality Matrix   Residential Customer Non-Residential User Non-Residential Admin REP User REP Admin TDSP User TDSP Admin Portal Host / SMT Supplemental User 3rd Party User 3rd Party Admin Regulatory User Regulatory Admin Customer Data Management View Meter Lists -- my ESIIDs M1 View Meter Lists -- granted ESIIDs M2 View Meter Lists -- ROR ESIIDs View Meter Lists -- TDSP ESIIDs View Meter Lists -- ALL ESIIDs M3 View Meter Attributes -- my ESIIDs M2 / OBJ 31 View Meter Attributes -- ROR ESIIDs View Meter Attributes -- TDSP ESIIDs View Meter Attributes -- ALL ESIIDs View Premise Attribute -- my ESIIDs View Premise Attributes -- ROR ESIIDs View Premise Attributes -- TDSP ESIIDs View Premise Attributes -- ALL ESIIDs View Meter Capabilities -- my ESIIDs View Meter Capabilities -- ROR ESIIDs View Meter Capabilities -- TDSP ESIIDs View Meter Capabilities -- ALL ESIIDs 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

Meter Attributes Attribute Name Description Utility Company Id TDSP DUNS number Extract Timestamp Time the TDSPs extracted data from their internal systems to be delivered to SMTxP Transaction Type A code identifying the type of customer transacion triggering a change. ESIID Meter serial number The serial number of the meter from the manufacturer KWH Meter multiplier A multiplying factor that regulates the KWH reading on certain meters. This is an external multiplier, not internal to the meter TDSP number of used channels on the meter number of channels the meter is configured for Meter manufacturer name Last meter test date Last date the meter was manually tested, in the field or in the meter shop Meter class (ampacity) The ampere maximum rating of the meter Date Meter was Installed Initial Provision Date Initial Provision Date (this date will correspond to the date that the TDSP starts sending usage data to the SMT) Technology/Communication indicator Technology/Communication indicator code identifying the type of communication method being used to transport data from that meter Instrument Rated Yes or No (e.g. Current Transformer / Potential Transformer) Ratio of Current Transformers The transformer ratio for the amperage transformer, if present" Ratio of Potential Transformers Tthe transformer ration for the voltage transformer, if present" ESI Firmware version Energy Services Interface: The main firmware version of the Gridstream communication module. This allows the AMI network and Communicaiton module to communicate to the HAN. HAN Protocol (ZigBee or HomePlug) Type of HAN Protocol enabled Smart Energy Profile The HAN compliance specification that this meter supports. This is the “protocol” used at the application layer (ex: ZigBee SEP 1.0) Interval setting How often the meter is recording usage (the length in minutes of the interval) In flow / Out flow (DG) Capable A true false value indicating whether or not the meter is able to handle both consumption and generation metering DG channel The channel number on the meter of the Distributed Generation channel Remote disconnect / connect Capable A true false value indicating whether or not the meter is enabled for remote disconnects Meter Status Is electricy flowing through the meter, as of the time of the latest i-sync extraction at the TDSP. Either energized or de-energized, as indicated by a single character code Meter Phases The number of phases that the meter handles, either 1, 2 or 3 Utility Meter Number The identifier for this meter that is used in the TDSP database (a.k.a. MeterID) Meter Model Meter Model identifier 11

Premise Attributes Attribute Name Description Utility Company Id Current SMT value is a TDSP DUNs number Extract Timestamp Time the TDSPs extracted data from their internal systems to be delivered to SMT ESIID Meter ESIID Premise ID Unique Premise Identifier Service Voltage Voltage rating of the premise Premise Status The current status of this premise, either active or inactive Time-zone The time zone where the premise is located Fractional House Address The fractional house number of the service address, or the designator that can be used to distinguish premises with the same address Leading Directional The directional indicator (typically N, S, E, W) that precedes the street name of a service address Street name The street name for the service address Street type The street type (e.g. St, Ave, Ln) for the premise address Trailing Directional The directional indicator that occurs after the street type, not commonly used Locality The city or locality of the service address State The state of the service address. This should always be TX Five digit Zip Code The primary, five digit ZIP code of the address Zip Code + 4 The secondary, four digit ZIP Code of the service address Meter Read Cycle The cycle number indicating the meter ready cycle date Load Profile ERCOT Load Profile: A text field that describes the load profile at the service location Rate Class/Code This is code that identifies the tariff used by the TDSP in billing this location House Number The house number of the service address Unit Designation This is used to denote individual premises in multi-unit addresses, for example in apartment or office buildings. Original Transaction ID Transaction ID generated by the TDSP to tie any exceptions created during delivery to SMT back to an original record or market transaction AMS profile effective date ERCOT AMS Profile effective date: Effective start date for SMT to start sending usage data to ERCOT. It is not necessary to push the usage data if this attribute value is null 12

Meter/Premise Attributes Functional Flow 13

Meter/Premise Attributes Portal UI Technical Flow 14

Meter/Premise Attributes Portal API Technical Flow 15

Monthly Billed Usage 16

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

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

Monthly Billed Usage – UI Design (Customers) 19

Monthly Billed Usage – Export Request 20

Monthly Billed Usage Functionality Matrix   Residential Customer Non-Residential User Non-Residential Admin REP User REP Admin TDSP User TDSP Admin Portal Host / SMT Supplemental User 3rd Party User 3rd Party Admin Regulatory User Regulatory Admin Customer Data Management Retrieve Billed Usage Reports -- my ESIIDs M2 Retrieve Billed Usage Reports -- granted ESIIDs Retrieve Billed Usage Reports -- ROR ESIIDs Retrieve Billed Usage Reports -- TDSP ESIIDs Retrieve Billed Usage Reports -- ALL ESIIDs M3 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

Monthly Billed Usage Functional Flow 22

Monthly Billed Usage Portal UI Technical Flow 23

Monthly Billed Usage Portal API Technical Flow 24

On-demand meter Read/ Power Status 25

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

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

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 Read Meter Check Power Status 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 Power Status Request 123 has been submitted 28

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

On-Demand Meter Read/Power Status Functionality Matrix   Residential Customer Non-Residential User Non-Residential Admin REP User REP Admin TDSP User TDSP Admin Portal Host / SMT Supplemental User 3rd Party User 3rd Party Admin Regulatory User Regulatory Admin Customer Data Management Poll Meter for Power Status -- ROR ESIIDs M2 Poll Meter for Power Status -- TDSP ESIIDs Poll Meter for Power Status -- ALL ESIIDs Request On-Demand Read -- ROR ESIIDs Request On-Demand Read -- TDSP ESIIDs Request On-Demand Read -- ALL ESIIDs 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

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

On-Demand Meter Read Technical Flow 32

On-Demand Power Status Technical Flow 33

Customer HAN device provisioning & de-provisioning 34

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

Customer HAN Device – Device List Screen 36

Customer HAN Device – ESIID List View HAN Devices > 37

Customer HAN Device – Provisioning Screen 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. HAN Devices > View HAN Devices 38

Customer HAN Device – De-provisioning Screen 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 HAN Devices > View HAN Devices 39

Customer HAN Device – Device Details HAN Devices > View HAN Devices Condition Status Displayed When the Portal accepts the add/provisioning request Add Acknowledged When the TDSP acknowledges the receipt of the add request When the TDSP sends a Pending Provisioning Status (only CNP could potentially send this status) Add Pending When the TDSP sends a Meter Ready Status Meter Ready When the Device is provisioned Device Added When the Portal accepts the remove/de-provisioning request Remove Acknowledged When the TDSP acknowledges the receipt of the remove request When the TDSP sends a Pending De-provisioning Remove Pending When a de-provisioning request fails before the de-provisioning is complete by the TDSP Remove Failed 40

Customer HAN Device – Provisioning History HAN Devices > View HAN Devices Condition – statuses that take a slot Status Displayed When the Portal accepts the add/provisioning request Add Acknowledged When the TDSP acknowledges the receipt of the add request When the TDSP sends a Pending Provisioning Status (only CNP could potentially send this status) Add Pending When the TDSP sends a Meter Ready Status Meter Ready When the Device is provisioned Device Added When the Portal accepts the remove/de-provisioning request Remove Acknowledged When the TDSP acknowledges the receipt of the remove request When the TDSP sends a Pending De-provisioning Remove Pending When a de-provisioning request fails before the de-provisioning is complete by the TDSP Remove Failed Condition – statuses that do not take a slot Provisioning Request Rejected by TDSP Add Rejected When a the TDSP sends a provisioning failure Add Failed De-provisioning Request Rejected by TDSP Remove Rejected When the Device is de-provisioned Device Removed 41

Customer HAN Device Functionality Matrix   Residential Customer Non-Residential User Non-Residential Admin REP User REP Admin TDSP User TDSP Admin Portal Host / SMT Supplemental User 3rd Party User 3rd Party Admin Regulatory User Regulatory Admin HAN Functions Grant and Revoke HAN Granular Permissions H3 View, Print or Extract HAN Granular Permissions Grant the Admin HAN Access Automatically H2 Grant / Revoke HAN Access to REP Portal User Grant / Revoke HAN Access to TDSP Portal User Provision HAN Device via GUI H3 / OBJ 30 Provision HAN Device via API H3 TBD De-Provision HAN Device via GUI De-Provision HAN Device via API Display reason for deprovision of a HAN device H2 TBD Delete pending provision request View HAN Devices by ESIID (Current Status) View HAN Device Details View HAN Device History Send Text Message via API Cancel Text Message via API Send Load Control Message via API Cancel Load Control Message via API Cancel All Load Control Events via API Send Price Signal via API Send a single message to a single HAN device H3* Send a single message to multiple HAN devices Assign Message Priority Ping ESI Ping HAN Device Notify authorized user of normal operations status of ESI Notify authorized user of status of HAN device View HAN Message Log Report View message sent from HAN device View status of message Create ESIID groups 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

Customer HAN Device Provisioning and De-provisioning Functional Flow 43

Customer HAN Device Provisioning Technical Flow 44

Customer HAN Device De-provisioning Technical Flow 45

SMT Automated Reporting of Statistics 46

SMT Automated Reporting of Statistics Overview Criteria Total as of 4/18/2010 @ midnight   User Counts Residential Users 1563 Spanish Residential Users 16 NRC Users 23 REP Users 294 TDSP Users 64 Total users 1772 Entity Counts in DB NRC Entities REP Entities 28 ESIID Counts Total ESIIDs in DB 897,903 Residential ESIIDs registered 1625 Non-residential ESIIDs registered 36 HAN Devices HAN devices provisioned 127 HAN devices deprovisioned 53 HAN messages processed 12 HAN message log requests 4 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

SMT Automated Reporting of Statistics Functionality Matrix   Residential Customer Non-Residential User Non-Residential Admin REP User REP Admin TDSP User TDSP Admin Portal Host / SMT Supplemental User 3rd Party User 3rd Party Admin Regulatory User Regulatory Admin Reporting Provide Data Access History OBJ 26 M3 / OBJ 25 Provide History of Third Party Access M3 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

Next steps SMT to provide an implementation schedule 49

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