HAN Coordination Update to Advanced Metering Implementation Team

HAN Coordination Update to Advanced Metering Implementation Team
Prepared and Presented by Jay Foliano April 24th 2012

Update Overview HAN Task Force Market Awareness & Outreach
National Standards Call Center Scripts HAN Documentation Effort Questions & Comments

HAN Support Design HAN Initiatives TDSP’s ROR/REP/3rd Party/Mfg
Documentation Joselito HAN Task Force Jay Market Awareness Jay National Standards EnerNex - TBD Scripts Don Smallwood RMS/AMIT – 04/19/12

HAN Task Force: HAN Support Model, Milestones:
Workshop, 4/12, TDSP’s and Market Participants Defined the detailed operational requirements: Support center responsibilities and scenarios Level one troubleshooting Support center triage and hand off processes Issue Handling Standards, i.e. triage punch list Customer information captured Escalation Process and Procedures Short and Long Term Objectives phased and scalable Expectations of SLO’s

HAN Task Force HAN Score Card Report to Define:
HAN Support Model, Next Steps: Validate and finalize the session requirements, documents and buy-in Present findings to OWG for input and buy-in Present to AMIT to outline the Implementation steps and recommended oversight/ownership Commence phased implementation Q2 HAN Score Card Report to Define: Report Title, Access Method and Market Awareness Owner/Gate-Keeper CRITICAL Frequency Process and Procedure for Device Testing and updating

Awareness & Standards Efforts
Market Awareness: On-going outreach to the PUCT, REP’s, Third Parties, TDSP’s and Vendors Continued information dissemination to the market National Standards: Securing a Consultant to Assume the Ownership

HAN Call Center Scripts
Donald Smallwood Project Lead Weekly Status Meetings Project execution Plan Defined the Script Template Developed Draft Scripts for each scenario Collaborating with the SMT Help Desk on the Script development and implementation Initial Completion Q2

HAN Documentation Objectives, Milestones, Review and Editing Process, Access and Detailed overview of the document Presenter: Joselito Samoy Process and Procedure for on-going support: Ownership Maintenance Communication effort to the market Who should have access to the HAN documentation Presenter: Robert Smith

HAN Guide Presentation
April 24, 2012

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

HAN Guide The Smart Meter Texas (SMT) Home Area Network (HAN) Guide is the primary HAN document for the Texas market participants with existing HAN programs and for other participants that are considering implementation of HAN products and services in the Texas territories covered by American Electric Power (AEP), CenterPoint Energy (CNP), Texas New Mexico Power (TNMP) and Oncor Electric.

HAN Guide The HAN Guide is a consolidation of all relevant HAN documents and artifacts developed for the Texas market participants, with the objective of being the main source of information regarding the processes involved with SMT HAN implementation. The HAN Guide is a “living” document, continually evolving based on national standards as they are developed, developments in HAN and Advanced Metering System (AMS) technology, and market input.

HAN Guide Sections

List of All HAN Functions
UI / API HAN Functionalities UI HAN UI (User Interface) Account Management Grant HAN Access Revoke HAN Access Provisioning/Deprovisioning View Provisioning Status Provisioning Deprovisioning Messaging View Messaging History API HAN API (Application Programming Interface) Provisioning/Deprovisioning/UEG Update Utility Enrollment Group Send Price Signal Send Simple Text/Display Cancel Simple Text/Display Send Load Control Event Cancel Load Control Event Cancel 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 User Experience
User Account Details (View) - REP

HAN Account Management User Experience
User Account Details (View) - TDSP

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 Provisioning User Experience
Meter Search and Search Results

View HAN Devices

Add HAN Devices

View HAN Device Details

Remove HAN Device

HAN Device History

HAN Device Provisioning SMT Procedures

HAN Device Status Descriptions

Removing HAN Device SMT Procedures

HAN Device Status Descriptions

HAN Device Provisioning

HAN Device Deprovisioning

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

Request Message – Log Confirmation

Report Request Status

Request Messaging Report SMT Procedures

Messaging Report File Format

HAN Device Messaging Report

HAN Application Programming Interface (API)
Assumptions on Central Time REPs have the ability to specify the current time and/or start times for display of messages, load control events and price signals. SMT assumes that all time values input through the API are in Central Standard or Central Daylight Time and converts it to UTC (Coordinated Universal Time). An example for how Central time values should be formatted appears below: <StartTime> T16:00:00</StartTime> UTC values should be formatted as follows: <StartTime> T16:00:00Z</StartTime>

Meter Numbers An example of a manufacturer’s serial number appears below: <MeterSerialNumber> </MeterSerialNumber> Some TDSPs add a manufacturer code to the manufacturer’s serial number to guarantee uniqueness. CenterPoint places the manufacturer code before the serial number. <MeterSerialNumber>I </MeterSerialNumber> Oncor appends the manufacturer code to the end of the serial number. <MeterSerialNumber> LG</MeterSerialNumber>

Schema Definitions All provisioning and deprovisioning requests use the following schema definition: <soapenv:Envelope xmlns:soapenv=" xmlns:smt=" All messaging requests use the following schema definition: <soapenv:Envelope xmlns:soapenv=" xmlns:smt="

Header Information

HAN Provisioning and Deprovisioning API
Slot Management A meter may have up to 5 devices provisioned to it. Each device takes a slot. Meter slot management rules are as follows: A slot is allocated when a valid provisioning request is accepted by SMT. A slot is de-allocated if the TDSP returns a failure status associated with a provisioning request. A slot is de-allocated when the TDSP returns a completion status for a deprovisioning request. If a deprovisioning request fails, slot allocation is unchanged.

HAN Device Provisioning Request Information

HAN Device Deprovisioning Request Information

HAN Device Provisioning and Deprovisioning Acknowledgment

HAN Update Utility Enrollment Group API
HAN Device Update Utility Enrollment Group Request Information Element Mandatory Type Description ESIID Y string(17,64) Energy Service Interface identifier MeterSerialNumber string(30) TDSP Meter manufacturer serial number DeviceMACAddr string(16) Device MAC Address UtilityEnrollmentGroup int Utility Enrollment Group

HAN Messaging API Addressing of Smart Energy Messages

HAN Messaging API Addressing of Messages with Group ID
When a Smart Energy message is addressed by the requester with a Group ID, SMT creates copies of the message for each TDSP. Then, the appropriate copy of the message is forwarded to each TDSP. The reason for this is that a group id cannot be identified with a particular TDSP: there is no way to distinguish which TDSP it needs to be sent to. Oncor and AEP will reject the message with no return error message if there is only the Group id and no list of ESIID and meter serial numbers. CNP will perform internal validation, and processes the message accordingly. For Multicast Messaging, CNP requires that the GroupID field be populated with the REP DUNS number, whether the ESIID/Meter Serial Number is populated or not. Whenever the GroupID field is populated, CNP will treat the HAN Message as Multicast Messaging. The value in the GroupID field should be the same as the RequesterAuthenticationID field. CNP will broadcast the message to the REP group.

HAN Messaging API Addressing of Messages with ESIID

Simple Text / Display Message API
Request Information

Cancel Simple Text / Display Message API
Request Information

Load Control Message API
Request Information

Cancel Load Control Message API
Request Information

Cancel ALL Load Control Message API
Request Information Element Mandatory Type Description CancelControl Y int Identifies additional control options for the event

Price Signal Message API
Request Information

HAN Messaging Examples
Simple Text / Display The following example illustrates how to send a simple message that starts immediately for a duration of 30 minutes. No confirmation (0) is required for this simple message. <SimpleMessageBlock> <MessageID>58158</MessageID> <StartTime> T00:00:00Z</StartTime> <DurationTime>30</DurationTime> <Message>Simple Message Test</Message> <MCTransmission>0</MCTransmission> <MCPriority>0</MCPriority> <MCConfirmation>0</MCConfirmation> </SimpleMessageBlock>

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. <LCMessageBlock> <EventID> </EventID> <StartTime> T00:00:00Z</StartTime> <DurationTime>30</DurationTime> <DeviceClass> </DeviceClass> <UtilityEnrollmentGroup>0</UtilityEnrollmentGroup> <CriticalityLevel>1</CriticalityLevel> <CoolingTemperationSetPoint>3000</CoolingTemperationSetPoint> <HeatingTemperatureSetPoint>1500</HeatingTemperatureSetPoint> <DutyCycle>255</DutyCycle> <EventControl>0</EventControl> </LCMessageBlock>

Load Control Messaging Temperature Offset The following example illustrates how to send a load control message to set the cooling temperature offset 2 deg C (20 in the example below) and the heating temperature offset 3 deg C (30 in the example below). Since the start time has been set to T14:15:00Z, this load control event will be started Feb 23, 2012 at 8:15 AM CST. The 2 zeros on the end represent seconds and rarely other than 00 used. The 14:15 is UTC or Greenwich Mean Time – CST +6hr). The duration of the load control event is 45 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. <LCMessageBlock> <EventID> </EventID> <StartTime> T14:15:00Z</StartTime> <DurationTime>45</DurationTime> <DeviceClass> </DeviceClass> <UtilityEnrollmentGroup>0</UtilityEnrollmentGroup> <CriticalityLevel>1</CriticalityLevel> <CoolingTemperationOffset>20</CoolingTemperationOffset> <HeatingTemperatureOffset>30</HeatingTemperatureOffset> <DutyCycle>255</DutyCycle> <EventControl>0</EventControl> </LCMessageBlock>

Load Control Messaging Temperature Offset with Duty Cycle The Duty Cycle is 50 which means that the load control switches will react to this load control event. The switches will be on 50% of the time, and off 50% of the time. <LCMessageBlock> <EventID> </EventID> <StartTime> T14:15:00Z</StartTime> <DurationTime>45</DurationTime> <DeviceClass> </DeviceClass> <UtilityEnrollmentGroup>0</UtilityEnrollmentGroup> <CriticalityLevel>1</CriticalityLevel> <CoolingTemperationOffset>20</CoolingTemperationOffset> <HeatingTemperatureOffset>30</HeatingTemperatureOffset> <DutyCycle>50</DutyCycle> <EventControl>0</EventControl> </LCMessageBlock>

Price Signal The following example illustrates how to send a price message (11 cents) that starts immediately for a duration of 30 minutes. <PriceMessageBlock> <ProviderID> </ProviderID> <RateLabel>Rate Label1</RateLabel> <IssuerEventID>865888</IssuerEventID> <CurrentTime> T00:00:00Z</CurrentTime> <UOM>0</UOM> <Currency>USD</Currency> <PriceTier>1</PriceTier> <PriceTrailingDigit>2</PriceTrailingDigit> <RegisterTier>1</RegisterTier> <StartTime> T00:00:00Z</StartTime> <Duration>30</Duration> <Price>11</Price> <PriceRatio>255</PriceRatio> <GenerationPrice>11000</GenerationPrice> <GenerationRatio>95</GenerationRatio> <AlternateCostDelivered>2222</AlternateCostDelivered> <AlternateCostUnit>1</AlternateCostUnit> <AlternateCostTrailingDigit>4</AlternateCostTrailingDigit> </PriceMessageBlock>

Update Utility Enrollment Group The following example illustrates how to send an update utility enrollment group message to set the UEG of the HAN Device 001B0000B to UEG = 10. The ESIID and Meter Serial Number should also be populated accordingly. <DeviceUpdateUEGRequestList> <DeviceUpdateUEGRequest> <ESIID> </ESIID> <MeterSerialNumber> </MeterSerialNumber> <DeviceMACAddr>001B0000B </DeviceMACAddr> <UtilityEnrollmentGroup>10</UtilityEnrollmentGroup> </DeviceUpdateUEGRequest> </DeviceUpdateUEGRequestList>

HAN Device Provisioning API

HAN Device Deprovisioning API

HAN Device Messaging API

HAN API Starter Kit The HAN API Starter Kit is a soap UI-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 Users of this Starter Kit are assumed to have basic technical expertise in these areas: Downloading applications from the Internet Installation and setup of applications Creation and editing of XML documents Internet security including user ids, passwords, and the use of X.500 certificates Network communications including URLs, IP addresses and common network troubleshooting commands such as ping, telnet, FTP, etc.

HAN API Starter Kit Environmental Setup Staging
REPs can submit this environmental information for access to the SMT Staging environment: SSL certification –SMT will accept a Certificate Authority (CA) or self-signed certificate. A REP needs to provide to SMT with their SSL certificate for Staging environment setup. Signing certificate–SMT will accept a CA or self-signed signer certificate. A REP will need to provide SMT with their signer certificate for Staging environment setup. DUNS – An SMT system account will be created that REPs must use when accessing the SMT Staging environment. One or more DUNS number must be associated with the SMT system account. Entity Name – This is the preferred REP name.

HAN API Starter Kit Environmental Setup Production
REPs can submit this environmental information for access to the SMT Production environment. SSL certification –SMT will only accept a CA certificate. A REP needs to provide to SMT with their CA SSL certificate for Production environment setup. Signing certificate–SMT will accept a CA signer certificate. A REP will need to provide SMT with their CA signer certificate for Production environment setup. DUNS – An SMT system account will be created that REPs must use when accessing the SMT Staging environment. One or more DUNS number must be associated with the SMT system account. IP Address(es) – Access is restricted to the SMT Production Environment. The REP IP Address is needed to enable access. Entity Name – This is the preferred REP name.

HAN API Starter Kit Set up the Starter Kit Configure SSL
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 Troubleshooting
In the event that Start Kit users are not able invoke a web service via SOAPUI client, these troubleshooting steps should be: Review the soapUI error log. Records in the soapUI error log should indicate a range of communication problems and can be used to determine the root-cause of a failure. Soap Fault Codes

HAN API Starter Kit Troubleshooting
Check if you can ping the SMT Server, from the machine where the SOAPUI client is running? If ping succeeds, it means you are able to communicate to the server. Proceed to test telnet as described below. If you cannot ping the SMT server, soapUI requests are not reaching the SMT server. Determine and fix the cause of the problem that is impeding end-to-end communications. Check if you can telnet the SMT Server, from the machine where the SOAPUI client is running? If telnet succeeds, it means you are able to communicate to the server using port 5205. Check your public SSL key "Common Name" is same as the "hostname" of the server where SOAPUI client is running. The REP will need to generate and send a new certificate and submit it to SMT. For communications to the Production environment, validate that your public IP address matches with the value originally submitted to the SMT team during REP configuration. Starter Kit requests will only pass through the SMT firewall when they are submitted from defined IP addresses. If the submitted web service request failed with a SOAP Fault Exception, analyze the error code, description in the SOAP response and validate the input message. The actual SOAP Fault description in the response will contain a detailed message related to the specific input attributes. Check the input elements and retry the service with valid inputs Check to make sure the correct URL/endpoint has been selected

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.

Prerequisites for Interfaces · SMT will only accept CA issued certificates (SSL and Signer Cert) in its production environment. Selfsigned certificates (SSL or Code Signed) will not be accepted. · SMT will accept self-signed certificates for testing purposes only. Although the self-signed certificates will be accepted for testing, CA certificates are preferred. · It is assumed that partners will use Class 3 certificates. · The system account for TDSPs and REPs should exist in the SMT user repository and be known to TDSP and REP in advance. The system account is case sensitive. · SMT will only accept signed requests as per WS-Sec 1.1 specification for all the incoming requests. The SMT signature processing module does explicit checks for the signature of UserNameToken, Simple Object Access Protocol (SOAP) Body and Time stamp. Although the SOAP request may be signed, the request will be reject if these elements are not signed. · Signature Confirmation is not implemented.

Validation Parameters Following table describes validation parameters, source and purpose:

Validation Steps Following are the authentication and validation sequence that happens on the SMT perimeter: SMT does 2-way SSL hand-shake with the REP endpoint. SMT gets the REP name or string identifying REP by reading the HTTP Header variable. SMT performs Schema Validation.

Validation Steps Following are the authentication and validation sequence that happens on the SMT perimeter: SMT validates the signature of the incoming request. SMT validates the system account of the REP using the HTTP header variable ENTITY_NAME, UserName from UserNameToken, and RequesterType elements. SMT validates the DUNS number of REP using the HTTP header variable ENTITY_NAME, RequesterType and RequsterAuthenticationID elements If all the steps are successful, the request is sent to SMT internal systems. In the event of failure at any step, the fault message is sent with an appropriate fault code.

Certificate Authorities List American Express ANX Belacom-E-Trust C-and-W-HKT-SecureNet-CA Certipose Certisign Certplus Deutshe Entrust Equifax EUnet FESTE First-Data Global Sign GTE-CyberTrust Microsoft NetLock RSA Saunalahaden SecureNet SecureSign SwissKey TC-TrustCenter Thawte UTN-DATACORP Valicert Verisign ViaCode

HAN API Authentication and Authorization
This section discusses how the API authentication and authorization will be handled when direct web service request is made by the REPs to Smart Meter Texas Portal (SMTxP) Enterprise Service Bus. Clients who communicate with SMT using the HAN web service interface must support mutual authentication over SSL. DataPower and Tivoli components will authenticate users. Authorization is enforced by the SMT integration environment. Two kinds of tokens will be used for authentication: Username or SAML tokens. The majority of the HAN web service consumers are expected to use a Username token. In either case, token data is used to map the sender to a system account. When a Username token is sent, the User Name element identifies the system account. If a SAML token is passed, the NameId element identifies the system account. DataPower validates the originator by verifying the WS-Security signature using the signer certificate from the SMT certificate store. If the digital signature is valid and the user can be authenticated, the web service request is passed to the ESB. Otherwise, a SOAP fault is issued.

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 Device Testing Criteria
The following are the technical requirements necessary for HAN Device testing: 64-bit IEEE MAC address and installation code SEP 1.0 certification Note: If your device is not SEP 1.0 certified, contact ZigBee at or Production certificate Note: If your device does not have production certificates, contact Certicom at to register for production certificates.

HAN Device Test Cases

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

HAN Device Reprovisioning

joselito@us.ibm.com (Joselito Samoy)
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)

Thank you

HAN Coordination Update to Advanced Metering Implementation Team

Similar presentations

Presentation on theme: "HAN Coordination Update to Advanced Metering Implementation Team"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

HAN Coordination Update to Advanced Metering Implementation Team

Similar presentations

Presentation on theme: "HAN Coordination Update to Advanced Metering Implementation Team"— Presentation transcript:

Similar presentations

About project

Feedback