Use cases utilizing an ems
Download
1 / 9

Use Cases Utilizing an EMS - PowerPoint PPT Presentation


  • 112 Views
  • Updated On :

Use Cases Utilizing an EMS. [email protected] Both Direct & Consumer Control. Thermostat Refrigerator Washer/dryer Dishwasher A/C Pool PEV. Utility event control. ESI. Daily control. Utility event signal. EMS. Continuous realtime usage readings. Lights

Related searches for Use Cases Utilizing an EMS

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Use Cases Utilizing an EMS' - mahalia


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Use cases utilizing an ems l.jpg

Use CasesUtilizing an EMS

[email protected]


Both direct consumer control l.jpg
Both Direct & Consumer Control

  • Thermostat

  • Refrigerator

  • Washer/dryer

  • Dishwasher

  • A/C

  • Pool

  • PEV

Utility event control

ESI

Daily control

Utility event signal

EMS

Continuous realtime usage readings

  • Lights

  • Motion detectors

  • ...


Both direct consumer control3 l.jpg

Issues

Both Direct & Consumer Control

ESI

Zigbee SE profile

Secure utility HAN

EMS

“Unsecure” personal network

Issue: Utility processes must allow EMS to register even though not a specific controlled device in rate plan

Zigbee HA or other profile

Fact: EMS must reside on 2 (Zigbee) logical networks

Issue: Implementations of EMS Zigbee interface device require 2+ complete radios and stacks = cost & complexity

Fact: EMS must use 2 (or more) Zigbee profiles


Direct control via ems proxy l.jpg
Direct Control via EMS Proxy

Utility event control

ESI

Utility event signal

Daily control

EMS

Continuous realtime usage readings


Direct control via ems proxy5 l.jpg

Issues

Direct Control via EMS Proxy

Issue: An intermediate device (EMS) must act as a proxy at the protocol level – no current requirement in OpenHAN or Zigbee

ESI

Secure utility HAN

EMS

“Unsecure” personal network

Fact & issue: EMS must use 2 (or more) Zigbee profiles and 2 logical networks

Issue: Utility processes must allow EMS to register as a proxy – no current requirement

Issue: EMS implementation may need to be certified by utility as trusted to fulfill proxy actions


Cost incentives no direct control l.jpg
Cost Incentives, No Direct Control

Extended existing use case

Utility event/cost control from EMS under user choice

ESI

  • Utility event signal

  • Public broadcast

  • Cost + emergency

Daily control

EMS

Continuous realtime usage readings


Cost incentives no direct control7 l.jpg

Issues

Cost Incentives, No Direct Control

Extended existing use case

ESI

EMS

Fact & issue: EMS must still use 2 (or more) Zigbee profiles and 2 logical networks

Issue: EMS must still be registered securely to read the meter

Note: The logical separation of the ESI and meter must be maintained


2 additional use case factors l.jpg
2 Additional Use Case Factors

Apply to each previous use case

ESP 2

ESP 3

Utility backhaul

  • DR aggregator

  • Renewable provider

  • Neighborhood microgrid

Internet

ESI primary

ESI 2

ESI 3

EMS

  • PEV

  • Gas

  • Water

  • Local generation

  • Local storage

  • Multiple ESIs, via various routes:

  • Utility backhaul  primary ESI  HAN  EMS

  • Internet direct  EMS

  • Internet  home network  EMS

  • Multiple meters, via:

  • Primary ESI  HAN

  • Meter direct to HAN

ESP = Energy Service Provider


A comprehensive solution l.jpg
A Comprehensive Solution

  • Standards could apply utility-grade security to individual HAN messages

    • Current security credentials

      • Apply to all communications of all devices on a logical network

      • Logical and physical network are treated as one (at least in most current implementations)

      • Thus for one device to talk to another they must be registered on the same logical network

    • Potential solution (on a single logical/physical HAN)

      • Most messages: utilize existing wireless network security

      • Messages requiring higher security, privacy or confirmation: additional SEP-level security is applied at low level in the stack

      • Could be based on one or more of: specific message; message type; source/destination pair

      • Utility-controlled devices must support this higher security but inexpensive dimmers, etc, would not need to

      • This solves all stated issues but would be a significant architectural change


ad