HAN Update AMIT/RMS April

HAN Core Support Team HAN Coordinator Jay Foliano Oncor Robert Smith CNP Steve Mulroe AEP Jerry Young TNMP Bobby Roberts PUCT Rebecca Reed -RMS/AMIT – 03/12/12 Coordinators Vendors/ MFG REPS/3rd Party 2

HAN Support Design HAN Initiatives HAN Initiatives Documentation Joselito Documentation Joselito HAN Task Force Jay HAN Task Force Jay Market Awareness Jay Market Awareness Jay National Standards EnerNex - TBD National Standards EnerNex - TBD Call Center Scripts Steve Ard Call Center Scripts Steve Ard -RMS/AMIT – 02/22/11 TDSP’s ROR/REP/3rd Party/Mfg 3

HAN Project - Milestones – Completed the HAN Support Model Workshop with the TDSP’s and Market: – Defined the detailed operational requirements and processes, issue resolution scenarios and required customer information to capture – Developing the HAN SMT Call Center Scripts : – Collaborative Effort with the SMT Call Center to Define the Template and Content Requirements, Q2 Phased Implementation – HAN Task Force Initiative: – HAN Score Card Report, Next Steps meeting with the TDSP’s, 4/19: – Finalize the report title – Define the frequency of updating/maintaining report content – Ownership/Gate-keeper of the Report – Where it will reside and access method – Review with the market participants for input and buy-in – HAN Documentation milestones, status and next steps presented by: – Joselito Samoy – Defined the Process and Procedures to support the on-going maintenance of the HAN Documentation : – Joselito Samoy, IBM, will assume the HAN Documentation ownership 4

HAN Project – Next Steps - AMIT, 4/24, present the initial version of the HAN documentation Define the Process & Procedures for the On-Going Maintenance/Updating of the Documentation – Define the future objectives of the HAN Roles & Permissions – Present the HAN Support Model Operational Details to the Market: Requirements & Processes Call Center Objectives and Escalation Procedures Issue Handling Scenarios Issue Resolution & Notification Expectations of SLO’s Phased Implementation Time-line, Q2 – HAN SMT Call Center Scripts Phased Implementation, Q2 5

HAN Guide Presentation April

HAN Guide HAN Guide is available to registered REPs and TDSPs in private SMT website

HAN Guide Sections

List of All HAN Functions UI / APIHAN Functionalities UIHAN UI (User Interface) UIAccount Management UIGrant HAN Access UIRevoke HAN Access UIProvisioning/Deprovisioning UIView Provisioning Status UIProvisioning UIDeprovisioning UIMessaging UIView Messaging History APIHAN API (Application Programming Interface) APIProvisioning/Deprovisioning/UEG APIProvisioning APIDeprovisioning APIUpdate Utility Enrollment Group APIMessaging APISend Price Signal APISend Simple Text/Display APICancel Simple Text/Display APISend Load Control Event APICancel Load Control Event APICancel All Load Control Events

HAN Account Management Functional Specifications The HAN Account Management processes describe how HAN Permissions are granted/revoked to users in the Portal. The HAN Account Management business rules describe how HAN Permissions are granted/revoked at the entity level.

HAN Account Management

HAN Device Provisioning and Deprovisioning Functional Specifications The HAN Provisioning processes describe how authorized users provision and deprovision HAN Devices through the Portal and how the Portal handles the different statuses of a provisioned Device. The processes also describe how authorized users are able to view provisioning information through the portal.

HAN Device Status Descriptions

HAN Device Messaging History This HAN Device Messaging History describes what the authorized user will be able to do through the UI, which is simply the ability to retrieve message acknowledgments (message log) for a particular message type, DUNS and message creation date.

HAN Device Messaging User Experience Message Log – Request Report

Messaging Report File Format

HAN Application Programming Interface (API) Provisioning and Deprovisioning APIs Update Utility Enrollment Group API Messaging APIs

HAN Messaging API Addressing of Messages with ESIID

Load Control Message API Request Information

HAN Messaging Examples Load Control Messaging Temperature Set Point The following example illustrates how to send a load control message to set the cooling temperature setpoint to 30 deg C (3000 in the example below) and the heating temperature setpoint to 15 deg C (1500 in the example below). Since the start time has been set to T00:00:00Z, this load control event will be started immediately for a duration of 30 minutes. All HAN Devices, regardless of the utility enrollment group they are assigned to, will receive the event as the Utility Enrollment Group in the load control event has been set to 0. Duty Cycle is 255 or NULL which means that the load control switches will not react to this load control event T00:00:00Z

HAN Device Messaging API

HAN API Starter Kit The HAN API Starter Kit is a soapUI-based tool that SMT has developed that Retail Electric Providers (REPs) can use for invoking the Smart Meter Texas (SMT) Home Area Networking (HAN) Web Service interface.

HAN API Starter Kit Overview of Steps for using the Starter Kit Set up the Starter Kit Configure SSL Configure WS-Security Invoke Web Services

HAN API Starter Kit HAN Provisioning and Messaging WSDL Files After the REPs have integrated with SMT HAN API’s using the API Starter Kit, the WSDL (Webservice description language) files for HAN related services will be provided by SMT upon request. These files can be utilized to build client applications to consume the SMT services for HAN. SMT will provide the WSDL files for the HAN services listed below. HAN Device Provisioning / Deprovisioning HAN Device Utility Enrollment Group HAN Device Messaging which includes: Sending simple text message Cancel simple text message Sending price signal Sending Load control event Cancel a Load control event Cancel all Load control events The REPs are expected to raise a request with the SMT help desk (Call ) to request these WSDL files. SMT technical team would provide the WSDL files in a compressed (.zip) file. The WSDL files can also be imported to SOAP UI tool to create and setup the project to access the service.

HAN Interface Security Prerequisites for Interfaces · All communication to SMT from REPs and TDSPs will be over 2-Way Secure Sockets Layer (SSL). For each TDSP, a VPN channel has to be established between SMT and TDSP systems. In the case of TDSPs, SSL will be employed over a virtual private network (VPN). · For API requests from TDSPs, SMT requires that a user credential be passed in a SAML token that is part of SOAP header. The specific of SAML token is described in a later section. · For API requests from REPs, SMT requires that a user credential be passed in a UserName Token that is part of SOAP header. SMT does not require password to be passed as part of UsernameToken.

HAN API Authentication and Authorization

HAN Device Testing Criteria Note: Verify that TDSPs have processes in place to support HAN Device Testing with REPs and HAN Device vendors. The TDSPs provide a standardized method of testing and verifying HAN Device functionality to ensure that HAN Devices function as designed within the specifications detailed in the Smart Energy Profile 1.0 when operated on TDSPs advanced metering system (AMS) network. The REPs and HAN Device vendors should contact the TDSPs to initiate request to perform HAN Device testing. The HAN Device test cases that are executed during the ZigFest Interoperability events are the basis of the test cases executed by the TDSPs in their HAN Device validation program. Some TDSPs have more test cases, and some have less, but all are based on the ZigFest test cases. These include provisioning, deprovisioning, and messaging (simple text, load control and pricing). The TDSPs record the testing results and provide feedbacks to the REPs and HAN Device vendors that requested the tests.

HAN Interoperability Report The HAN Device Interoperability Report contains information regarding HAN Devices that have passed testing at a particular TDSP. The reports are updated monthly and filed with each TDSP's Commission report. Each report contains the device name, version, meter firmware version, device configuration and date tested. Devices that are in testing or have failed testing are not on this list.

HAN Device Reprovisioning During Meter Exchange

Next Steps Working with Handbook and Education taskforces to review and fine- tune the HAN Guide – Method to incorporate the HAN documentation into the HandBook – Going forward Process & Procedures to interface HAN documentation, future versions, with both Task Forces group efforts – Education Process to advise the market of the HAN documentation availability, location and access method – AMIT steering committee to determine who in the market can have access to the HAN documentation – Will we provide a soft copy, hard copy or both available to the market Gather feedbacks and comments from the Market Participants, and include these in the next version of the HAN Guide Please send your feedbacks and comments to: (Joselito Samoy)