18
OpenHAN Boot Camp July 19, 2010

OpenHAN Boot Camp

  • Upload
    tamah

  • View
    54

  • Download
    0

Embed Size (px)

DESCRIPTION

OpenHAN Boot Camp. July 19, 2010 . OpenHAN TF Overview. Chair Erich W. Gunther, EnerNex – [email protected] Co-chair Mary Zientara, Reliant Energy - [email protected] Task Groups: OpenHAN 2.0 Mary Zientara, Reliant Energy, chair Charlie Smith, GE, co-chair - PowerPoint PPT Presentation

Citation preview

Page 1: OpenHAN Boot Camp

OpenHAN Boot Camp

July 19, 2010

Page 2: OpenHAN Boot Camp

OpenHAN TF Overview Chair

Erich W. Gunther, EnerNex – [email protected]

Co-chair Mary Zientara, Reliant Energy - [email protected]

Task Groups: OpenHAN 2.0

Mary Zientara, Reliant Energy, chair Charlie Smith, GE, co-chair Charles Spirakis, Google, co-chair Zahra Makoui, PG&E, co-chair

Page 3: OpenHAN Boot Camp

OpenHAN TF Information Email reflector:

[email protected] Web meeting information:

Provided via email to all members of OpenHAN reflector Announced on the OpenSG sharepoint in the OpenHAN calendar

Web meeting times:

Meeting minutes and documents: http://osgug.ucaiug.org/sgsystems/openhan/default.aspx

Meeting Day PST MST CST EST

OpenHAN 2.0 Tuesday 9:00 am 10:00 am 11:00 am noon

Page 4: OpenHAN Boot Camp

OpenHAN Detroit F2F Agenda Monday, July 19th

SG Systems Boot Camp – OpenHAN @ 4:35 PM – Mary Zientar Note: Session is an overview for newcomers

Tuesday, July 20th 1:00 – 3:00 – OpenHAN 2.0 Work Session - Woodward C – 2 - Mary Zientara 3:30 – 5:30 - OpenHAN 2.0 Work Session - Woodward C – 2 - Mary Zientara

Wednesday, July 21st 1:00 – 3:00 - Joint session with SG Security - Woodward D – 2 - Mary Zientara 3:30 – 5:30 - OpenHAN 2.0 Work Session - Founders A – 3 - Mary Zientara

Thursday, July 22nd 10:30 – 12:00 - Work Session - Woodward D – 2 - Mary Zientara 12:00 – 1:00 pm - Closing Plenary – Report Outs

Page 5: OpenHAN Boot Camp

5

OpenHAN History2008

August 2008 UtilityAMI 2008 HAN SRS v1.04 released

2007

OpenHAN TF is formed to develop system requirements for the HAN

2009

June 2009Utility AMI 2008 HAN SRS v1.04 selected as a customer domain standard in the NIST Smart Grid Interoperability Standards Roadmap

October 2009OpenHAN 2.0 formed to develop the next version of the HAN SRS

2010

July 2010UCAIug HAN SRS v1.98 released

August 2010UCAIug HAN SRS v2.0 ratified

Page 6: OpenHAN Boot Camp

6

UCAIug HAN SRS v1.98Purpose

Define the system requirements for an open standard Home Area Network system

Promote open standards-based HANs that are interoperable Provide the vendor community with a common set of principles

and requirements around which to build products Ensure reliable and sustainable HAN platforms Support various energy policies in a variety of states,

provinces, and countries Empower consumers to manage their electricity consumption

by giving them the information and control they need to make decisions on their energy use

Page 7: OpenHAN Boot Camp

7

Scope of OpenHAN in the NIST conceptual model

Page 8: OpenHAN Boot Camp

8

HAN SRS v1.98The audiences for the HAN SRS are:

Utilities considering deploying AMI systems that interact with HANs Vendors that make AMI systems for Utilities that interact with HANs Vendors that make consumer products (e.g. programmable communicating

thermostats, energy management systems, load control switches, in-home displays, smart appliances, Plug-in Electric Vehicles (PEV), distributed energy resources, etc.)

Service Providers developing smart grid enabled programs for consumers (e.g. demand response, energy management, pre-pay, PEV programs, distributed energy resources, etc.)

Policy makers looking to understand how Utility AMI deployments that interact with HANs benefit and impact consumers

Industry alliances and standards organizations NIST Smart Grid Interoperability Panel (SGIP) activities (e.g. Smart Grid

Architectural Committee (SGAC), Cyber Security Working Group (CSWG), Smart Grid Testing and Certification Committee (SGTCC), etc.)

Page 9: OpenHAN Boot Camp

9

HAN SRS v1.98Guiding Principles

Capabilities1. Support Two-way Communication Between HAN Devices and Service

Providers2. Supports load control integration3. The AMI meter provides the HAN with direct access to Consumer-

specific usage data4. Provides a growth platform for future products which leverage the HAN

and meter data5. Supports three types of messaging: Public Information, Consumer-

Specific Information, and Control Signals6. Supports end-use metering and other utility meters7. Supports distributed energy resources

Assumptions8. Consumer owns the HAN9. HAN devices present additional security considerations10. The HAN is enabled by open and interoperable standards

Page 10: OpenHAN Boot Camp

10

HAN SRS v1.98Architectural Considerations

OpenHAN applies from the edge of the AMI System, where the Energy Services Interface (ESI) resides, to all relevant HAN Devices in the home

Energy Services Interface (ESI)o An interface which enables communication between authorized parties

and HAN devices that are registered to ito There may be more than one ESI in the premise (e.g. Utility ESI, 3rd

party ESI)o Utility ESI – provides interface between the Utility AMI network and HAN

deviceso Other ESI – provides interface between other communication media

(e.g. internet, cell phone, EMS, etc.) and HAN devices registered to it

Page 11: OpenHAN Boot Camp

11

HAN SRS v1.98Architectural Considerations, continued

Commissioning, Registration, Enrollmento Commissioning is the process by which a HAN device obtains

access to a specific physical network and allows the device to be discovered on that network

o Registration is the process by which a Commissioned HAN device is authorized to communicate on a logical network by exchanging security credentials with an ESI

o Enrollment is the process by which a Consumer enrolls a HAN device in a Service Provider program (e.g. demand response, energy management, PEV program, etc.)

Page 12: OpenHAN Boot Camp

12

HAN SRS v1.98

CommissionedNetwork admission of HAN

device on HAN

CommissionedNetwork admission of HAN

device on HAN

RegisteredAuthentication established

between HAN device and ESI

RegisteredAuthentication established

between HAN device and ESI

Pre-commissionedNon-HAN operation of devicePre-commissioned

Non-HAN operation of device

EnrolledService Provider granted rights

to access HAN device

EnrolledService Provider granted rights

to access HAN device

Page 13: OpenHAN Boot Camp

13

HAN SRS v1.98Architectural Considerations, continued

OpenHAN SRS is agnostic to device ownership Some HAN devices may reside on more than one ESI OpenHAN SRS is agnostic to electric market structure and

may be used in integrated utility markets as well as consumer choice electric markets

There may be multiple communication paths into the HAN (e.g. Utility AMI, internet, cell phone network, EMS, etc.)

OpenHAN SRS addresses the following special applicationso Plug-in-Electric Vehicle (PEV) o Energy Management System (EMS)o Distributed Energy Resources (DER)

Page 14: OpenHAN Boot Camp

14

HAN SRS v1.98HAN System Requirements

Application Requirements Control applications respond to control signals Measurement and Monitor applications provide internal data and status Processing applications consume, process, and act on external and

internal data Human Machine Interface (HMI) provides Consumers a means to

provide input into an application or to view information from an application

Communication Requirements Commissioning is the network process of adding a HAN device on the

HAN to allow the device to communicate with other devices and involves network scanning, selection, admission, and configuration

Control of a node involving self-organization, path selection, mitigation

Page 15: OpenHAN Boot Camp

15

HAN SRS v1.98HAN System Requirements, continued

Security Requirements Access Controls and Confidentiality address data protection for data-at-

rest and data-in-transit Registration is the network process to authenticate and authorize HAN

device participation with an ESI and includes initialization, authentication, correlation, authorization, and de-register

Enrollment is the process by which a Consumer enrolls a HAN device in a Service Provider’s program (e.g. demand response, energy management, pre-pay, PEV programs, distributed generation, pricing, messaging, etc.) and gives certain rights to the Service Provider to communicate with their HAN device

Integrity preserves the HAN operating environment through resistance and recovery

Accountability will allow for monitoring malicious activities through audit and non-repudiation

Page 16: OpenHAN Boot Camp

16

HAN SRS v1.98HAN System Requirements, continued

Performance Requirements Ensure applications or other factors do not limit the performance of the

system, which is dependent upon availability, reliability, maintainability, scalability, upgradeability, quality and latency

Operations, Maintenance, and Logistics Requirements Manufacturing and Distribution - Vendor’s pre-installation activities

including pre-Commissioning settings, application configuration, labeling, support for multiple distribution channels

Installation – Documentation for the physical placement of the device and support systems

Manage, Maintain – ensure HAN device diagnostic, management and trouble shooting capabilities including alarming, logging, testing, device reset, and monitoring

Page 17: OpenHAN Boot Camp

17

HAN SRS v1.98Requirements Mapping to Logical Devices

Provides guidance to Service Providers and vendors For reference only and should not limit the needs of Service Providers

or vender innovation Mapping Categories

o CP or Commissioning Process– Minimum requirement for the Commissioning process. These requirements are mandatory and must be included to support the process of Commissioning a HAN device on the HAN.

o RP or Registration Process - Minimum requirement for the Registration process. These requirements are mandatory and must be included to support the process of Registering a HAN device on the ESI.

o BF or Basic Functionality – Minimum requirement that the OpenHAN TF recommends is needed to support the basic functionality of the logical HAN device.

o S or Security – Minimum requirement for HAN security. These requirements are mandatory and must be included to protect the HAN against compromises to the confidentiality, integrity, and availability of the HAN

o O or Optional – An optional requirement that may be included to support a Service Provider program or allow a vendor to differentiate their product.

o NA or Not Applicable - This requirement is not applicable to this logical HAN Device.

Page 18: OpenHAN Boot Camp

18

HAN SRS v1.98Requirements Mapping to Logical Devices, continued

Mapping table located after each requirement section

Logical Device Primary Functionality 1 Energy Services Interface (ESI) Network Control and Coordination 2 Utility ESI Network Control and Coordination 3 Programmable Communicating

Thermostat (PCT) HVAC Control

4 In-Home Display (IHD) Display of Energy Information

5 Energy Management System (EMS)

Controlling end-device energy

6 Load Control Resource Control 7 AMI meter Energy Measurement 8 HAN Non-Electric Meter Resource Measurement 9 Smart Appliance Intelligent Response

10 Electric Vehicle Supply Equipment (EVSE)

Charging a PEV

11 Plug-in Electric Vehicle (PEV) Electric transportation

12 End-Use Measurement Device (EUMD)

Metering of an end-device load

1