1. Advanced Metering Implementation Team (AMIT) Update to RMS Presented by Christine Wright August 17, 2011 http://www.puc.state.tx.us/industry/projects/electric/34610/34610.aspx

2. Overview 3 rd Party Access Meeting July 25 th 3rd Party Functional Overview 3rd Party Use Cases Assumptions - 3rd Party Pilot Objectives RACI Matrix - 3rd Party Pilot SMT Model - 3rd Party AMIT Stakeholder Steering Committee Meeting July 26 th Decision Matrix for 3rd Party Access HAN Interoperability Model Ember Presentations SWG Update The Current State of Smart Grid Interoperability Standards August 30-31 Demand Response – AMI’s Next Frontier

3. SMT API 3 rd PARTY API SMT UI 3 rd PARTY UI CONSUMER 3 rd PARTY 001 Initiate 3 rd Party Relationship 002 View 3 rd Party Relationship 003 Manage 3 rd Party Relationship 004 Set up SMT API access 005 Requests list of relationships 006 Requests consumer data

4. Pilot Assumptions Any required business relationships between the 3 rd Party and the Consumer are already in place and are managed outside of any Smart Meter Texas processes. The Consumer AMS meter must be installed and provisioned through the TDSP processes. The relationship exists between the consumer and the 3 rd Party, not between the 3 rd Party and the meter.

5. Pilot Assumptions cont. For the pilot, the participating Consumer must be registered with SMT to grant 3 rd Party access to their ESI ID(s). As part of the pilot, a customer education/disclaimer will be given to the customer before 3 rd Party access is granted. The 3 rd Party will only be able to access the participating Consumer’s energy data

6. Pilot Objectives Develop, test and refine (lessons learned) the initial processes used by third parties for access to non-customer specific (aggregated) usage data (e.g. could be used for research, etc) Develop, test and refine (lessons learned) the initial processes used by third parties in preparation for a full rollout Test the customer authorization using the proposed tool for third party access to the data

7. Pilot Objectives cont. Develop, test and refine (lessons learned) the initial processes used by third parties in for HAN services Understand third party access methodology Lay the groundwork and provide actual experience that can be used in the development of national standards Test the concept and processes that are proposed for third parties accessing customer data

8. PSWG Use Cases for 3 rd Party Pilot Use Case 1: Consumer initiates Pilot 3rd Party relationship via e-mail Use Case 2: Consumer receives information on existing 3rd Party relationships via e-mail Use Case 3: Consumer manages 3rd Party relationships via e-mail Use Case 4: 3rd Party sets up SMT API access Use Case 5: 3rd Party requests list of existing consumer relationships Use Case 6: 3rd Parties ability to access consumer data

9. SMT Model for 3 rd Party Access Screen Scraping TO BE RETIRED IN THE FUTURE Existing Residential Usage GUI 1. Usage Report or Screen Print 2.1. User ID and Password 2.2 User ID and PW 2.3 User ID, and PW Existing Friends and Family SMTSMTConsumerConsumer New Grant ID API New Grant ID FTPS 3.1. Invite Market Participant 3.2 Accept Consumer Invitation 4.1. Consumer Grant Identifier 4.2. Grant ID, Duration 4.3. Grant ID, Duration New Grant D Notification and Approval 4.1. Notification of Data Pull Request 4.1. Approval of Data Pull Request Market (ie. REPs, Aggregators, Brokers, Consultants, Google, MicroSoft, etc.) Market

10. RACI Matrix R – Responsible/ A – Accountable/ C – Consultant / I - Informed 30 Actions Identified Assigned to SWG, OMWG, RAAWG, PSWG, PUCT, 3 rd Parties, JDOA Legal, JDOA TDSPs

11. RACI Matrix Actions Identify what 3rd Parties may participate in the pilot and the mechanism for selecting 3rd Parties to participate Determine 3rd Party Terms and Conditions for the pilot Develop a mechanism to support all pilot participants Develop the feedback requests we’re looking for from consumers in the pilot Report consumer feedback to the market

12. RACI Matrix Actions cont. Administer 3rd Party registration for pilot and any applicable fees Determine the number/cap of consumers for the pilot Determine the customer acknowledgement (T’s and C’s) mechanism Develop a mechanism for SMT to terminate a consumer from the pilot Develop a mechanism for SMT to terminate a 3rd Party from the pilot Build and design the automated portions of the pilot

13. Ember Presentation to AMIT Ember Overview Demonstration SE 1.x status and timeline SE 2.0 status and timeline Our Perspective on Market View

14. Smart Energy Profile (SEP) SE 1.0 Primary focus on consumption data Demand Response Pricing Establish underlying security and device authentication SE 1.1 (spec approved and released) Over the air software updates Fast polling Pricing Updates Large number of test spec improvements and cleanup from field events

15. Smart Energy Profile (SEP) SE 1.1 additional features (in testing) Tunneling (for DLMS) Prepayment Trust Center replacement Multi-ESI behavior SE 1.2 (in marketing discussion) Compatibility with HA networks British Gas requirements Security Improvements from CSWG review Other features under discussion with Members

16. SEP 2.0 Profile Functionality Application functionality includes DRLC Messaging Pricing Prepayment Metering Plug-in electric vehicles Distributed energy resources Billing Registration Device configuration and capabilities Network management Firmware downloads (tftp) Diagnostics and monitoring

17. AMI’s Next Frontier: Demand Response ERCOT DR Overview & Status Report AMIT Background & TDSP Status Report Technology Product Providers Perspectives – Tune Energy – Rainforest Automation – Consert – EnergyHub – Lowfoot – GE Role of the REP – Champion, Reliant, TXU Discussion of Barriers to Entry & Adoption

18. Questions?