SMT Model for Third Party Access Revision Date June 1, 2011

2 Third Party Access Model Market (ie. REPs, Aggregators, Brokers, Consultants, Google, MicroSoft, etc.) 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 SMTConsumer New Consumer ID API New Consumer ID FTPS 3.1. Invite Market Participant 3.2 Accept Consumer Invitation 4.1. Consumer Unique Identifier 4.2. Consumer ID, Duration 4.3. Consumer ID, Duration New Consumer ID Notification and Approval 4.1. Notification of Data Pull Request 4.1. Approval of Data Pull Request

Third Party Access Model 3 Use Case 1 – Consumer provides account information via existing report or screen print functionality directly to the Third-Party Use Case 2.1 – Consumer provides their user ID and password directly to the Third-Party for account access Use Case 2.2 – Third-Party accesses consumer data using ID and password via the existing Smart Meter Texas residential online user interface Use Case 2.3 – Third-Party accesses consumer energy data using ID and password via existing screen scraping capabilities (this option will be retired after development of new consumer ID API and FTPS) Use Case 3.1 – Consumer provides account information to a Third-Party by invitation via the existing “Friends and Family” Smart Meter Texas residential online functionality Use Case 3.2 – Third-Party accesses consumer energy data using the existing “Friends and Family Smart Meter Texas residential online functionality

Third Party Access Model 4 Use Case 4.1 – Consumer provides their Consumer Unique Identifier directly to the Third-Party for account access Use Case 4.2 – Third-Party accesses the consumer energy data using Consumer Unique Identifier via a new Smart Meter Texas API Use Case 4.3 – Third-Party accesses the consumer energy data using Consumer Unique Identifier via a new Smart Meter Texas FTPS

Third Party Access Considerations 5 Establish a connection fee which will be charged for any Third-Party who wishes to establish an API connection with the SMT environment. Establish a monthly management fee which will be charged for any Third- Party who wishes to maintain an API connection with the SMT environment. The fee would probably need to be based on a tiered approach. Consider whether the REPs who are not a ROR should be charged a connection fee or monthly management fee.