25.12.2012 Views

security profile for openadr - Open Smart Grid - OpenSG - UCA ...

security profile for openadr - Open Smart Grid - OpenSG - UCA ...

security profile for openadr - Open Smart Grid - OpenSG - UCA ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

590<br />

591<br />

592<br />

593<br />

594<br />

595<br />

596<br />

597<br />

598<br />

599<br />

600<br />

601<br />

602<br />

603<br />

604<br />

605<br />

606<br />

607<br />

608<br />

609<br />

610<br />

611<br />

612<br />

613<br />

614<br />

615<br />

616<br />

617<br />

618<br />

619<br />

620<br />

621<br />

Use Case 6: DR Controlling Entity Schedules DR Resource <strong>for</strong> Periodic<br />

Feedback (Point-to-point Push)<br />

Use Case Description: This interaction is used by the DR Resource to notify the DR<br />

Controlling Entity of the Resource’s status or state of the Resource during the event. The<br />

feedback is provided continuously during the event in intervals agreed upon by the<br />

parties. The per<strong>for</strong>mance feedback contains in<strong>for</strong>mation such as the load <strong>profile</strong> response<br />

characterization of the DR Resource in response to getting the DR signal and in<strong>for</strong>mation<br />

about the near real time electricity usage of the DR Resource.<br />

This use case is comprised of three interaction patterns:<br />

Preconditions:<br />

SECURITY PROFILE FOR OPENADR<br />

o Initiate periodic feedback.<br />

o Provide periodic feedback.<br />

o Change (terminate is a type of change) feedback request.<br />

• The DR Resource and DR Controlling Entity have all of the necessary network<br />

connections available.<br />

• The party with ownership, controlling interest or administrative responsibilities<br />

<strong>for</strong> the Resource has enrolled in a Demand Response Program that is administered<br />

by the DR Controlling Entity.<br />

Minimal Guarantees:<br />

• The DR Resource does not reveal any in<strong>for</strong>mation that could allow another party<br />

to present false identification, or intercept or alter future messages sent to the DR<br />

Controlling Entity.<br />

• The DR Controlling Entity does not process any invalid data.<br />

Success Guarantees:<br />

• The DR Controlling Entity receives continuous and timely (real time or near real<br />

time) feedback from the DR Resource during the entire Event per<strong>for</strong>mance<br />

window.<br />

Trigger:<br />

The trigger <strong>for</strong> this use case is based on an agreed upon reporting interval associated with<br />

a DR Event. Generally, the DR Controlling Entity will initiate the feedback interactions<br />

at the start of an Event.<br />

Version – 0.02<br />

<strong>UCA</strong> International Users Group December 15, 2011<br />

34

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!