openhan tf meeting where do we go next? erich w. gunther

16
OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Upload: regina-craig

Post on 18-Jan-2016

218 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

OpenHAN TF MeetingWhere do we go next?Erich W. Gunther

Page 2: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Agenda OpenHAN Overview Work Plan Discussion Next Steps

Page 3: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Promotes open standards-based HANs that are interoperable

Provides the vendor community with a common set of principles and requirements around which to build products

Ensures reliable and sustainable HAN platforms Supports various energy policies in a variety of states,

provinces, and countries Empowers end users with the information they need to

make decisions on their energy use by enabling the vision of a home energy ecosystem

UtilityAMI 2008 HAN SRS

Page 4: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

HAN SRS Ratification Vote UnanimousMar 7, 2008

AEP SCE SDG&E PG&E Detroit Edison FPL

BC Hydro Entergy Consumers Energy CenterPoint Energy Oncor EDF

Endorsing Utilities:

Duke EnergyReliant Energy

Page 5: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

HAN Standards Overview

7

Requirements Technology Certification

UCAIUG

Open DR

Open AMI Utility AMI

AMI enterprise AMI SEC Open HAN

Utility driven requirements

Vendor implementation models of the

utility requirements

Technology agnostic HAN requirements

Security requirements for the AMI system

Back office integrations

requirements

IEC

HAN StandardsZigBee®

HomePlug®

ZB + HP Joint Working Group

Joint SC

Technical WG Marketing WGMarket

requirements and alignment

Chaired by Reliant

Answer the technical questions

Chaired by SCE

Compliance WG

Define certification

process

Joint steering committee

chaired by PG&E

IP ConnectivityTG

Smart Energy Profile WG

ZigBee Security WG

ZB QualificationGroup

HomePlug 1.0 HomePlug CC

IEEESAE

IETF

Other Standards

802.15.4 HAN2.4 GHz

802.15 NAN SG900 MHz

SAE J2836 ROLL

IPSO

Wireless M-Bus

802.11

Bluetooth

ZARC

Utility communications architecture international

users group

Any standards activity that touches the HAN in any way.

ZigBee Architecture Review committee

Acts as the technical oversight committee and

authority

Recently re-established to review ZigBee security issues

Utility HAN public profile

Defining ZigBee’s IP

gateway functionality

Goal of integrating to a common application layer independent of the underlying physical platform

High bandwidth PLC communications std

Lower bandwidth PLC communication

std

Low power wireless mesh technology

Electric Vehicle communications

HAN standard getting traction in

Europe

Oversee ZigBee certification

Routing over low

power and lossy

networks

ZigBee Labs

HomePlug Labs

802.15 Labs

ComprehensiveCertification

Labs

TBD

MSC

MWG

No specified labs exist at the

moment

1. NTS

2. TUV

No specified labs. NTS and TUV

execute their own conformance testing

Marketing Steering

Committee

Marketing Working Group

6lWPAN

Skinny IP (UDP) over

802.15.4

Page 6: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Dec 2007 6

HAN Guiding Principles

Value Proposition

Guiding Principles

Use Cases

Platform Independent Requirements

Platform Requirements

(Technology Specific)

System Criteria

Page 7: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Dec 2007 7

HAN Guiding Principles

Capabilities Supports a secure two way communication with the meter Supports load control integration Provides direct access to usage data Provides a growth platform for future products which leverage HAN

and meter data Supports three types of communications: public price signaling,

consumer specific signaling and control signaling Supports distributed generation and sub-metering

Assumptions Consumer owns the HAN* Meter to HAN interface is based on open standards Implementation is appropriate given the value and the cost Technology obsolescence does not materially impact the overall value

Page 8: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Dec 2007 8

HAN Use Cases

Value Proposition

Guiding Principles

Use Cases

Platform Independent Requirements and

Architecture Considerations

Platform Requirements

(Technology Specific)

System Criteria

Page 9: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Dec 2007 9

Use Case Scope

Abstracted to highest level for rapid adoption (i.e., more details to follow) note: previous work has been more detailed

Concentrates on Utility to HAN interactions Device ownership independent (e.g.,

registration is the same whether or not the utility supplies the device)

Interactions are based on Utility relevant activities only (Ignores other HAN activities within the premise – e.g., Home Automation)

Required device functionality will be specified in subsequent phases (i.e., platform independent requirements)

Page 10: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Dec 2007 10

Organization

System Management and Configuration Depot Configuration Installation and Provisioning Utility Registration Remote Diagnostics Maintenance and Troubleshooting

Load Control and Energy Management Voluntary Mandatory Opt-out

Energy Management System Energy Storage and Distribution User Information HAN Metering

Page 11: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Dec 2007 11

Platform Independent Requirements

Value Proposition

Guiding Principles

Use Cases

Platform Independent Requirements and

Architecture Considerations

Platform Requirements

(Technology Specific)

System Criteria

Page 12: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Dec 2007 12

Requirements Overview

Requirements are platform independent Requirement are to products applied via device

mappings (Appendix) Special class of requirements for an AMI

gateway (See Mappings) Two types of compliance

Technology/alliance – application and communication compliance (e.g., message structures)

Vendor/product – compliant with device mapping requirements

Page 13: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Work Plan Discussion No consensus yet on next steps Needs to be driven by industry need

This is the only way to get the volunteers needed to do the work

Stated need to update the SRS New use cases Lessons learned from SEP 2.0 and utility projects Conformance

General discussion What do we need to support deployments – what are the hot buttons?

Page 14: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Use Cases Proposed in 2008 Installation - ZBHP

Deregistration Reconstituting Security after failure/replacement

Medical appliances inside the home Discovery for various utility program use

PEV - ZBHP Fallback modes in degraded condition - ZBHP

Failure mode cases missing in general Pre-pay - ZBHP Energy messages (pricing and usage) - ZBHP Duty cycle control Energy storage

Multiple dwelling units and high rises (Toronto has some) Dynamic T&D integration

Page 15: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Use Case Development Prioritize, select, develop narrative

Page 16: OpenHAN TF Meeting Where do we go next? Erich W. Gunther

Questions?

For any additional information, please do not hesitate to contact us

Note: Full participation requires UCAIug membership – join at http://www.ucaiug.org/

UCAIug Board Members:

Erich W. GuntherEnerNex [email protected]

Wayne R. LongcoreConsumers Energy

[email protected]