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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

637<br />

638<br />

639<br />

640<br />

641<br />

642<br />

643<br />

644<br />

645<br />

646<br />

647<br />

648<br />

649<br />

650<br />

651<br />

652<br />

653<br />

654<br />

655<br />

656<br />

657<br />

658<br />

659<br />

660<br />

661<br />

662<br />

663<br />

664<br />

Use Case 7: DR Resource Notifies DR Controlling Entity of Event<br />

Per<strong>for</strong>mance with Feedback by Request (Point-to-point Pull)<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 as requested by the DR Controlling Entity. The per<strong>for</strong>mance<br />

feedback contains in<strong>for</strong>mation such as the load <strong>profile</strong> response characterization of the<br />

DR Resource in response to getting the DR signal and in<strong>for</strong>mation about the near real<br />

time electricity usage of the DR Resource. This case differs from the prior use case in<br />

that the request from the DR Controlling Entity is <strong>for</strong> a single reply without a recurring<br />

schedule.<br />

Preconditions:<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 timely (real time or near real time) feedback<br />

from the DR Resource.<br />

Trigger:<br />

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

SECURITY PROFILE FOR OPENADR<br />

Version – 0.02<br />

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

36

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

Saved successfully!

Ooh no, something went wrong!