[OASIS Issue Tracker] Created: (ENERGYINTEROP-186) General - Evenat edge conformance group. Go to OpenADR.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

General - Even at edge conformance group. Go to OpenADR.
--------------------------------------------------------

                 Key: ENERGYINTEROP-186
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-186
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
          Components: spec
    Affects Versions: wd14
         Environment: SGIP-PAP09 Girish Ghatikar
            Reporter: Toby Considine
            Assignee: Toby Considine


Even at edge conformance group. Go to OpenADR. Very clearly defines simple and smart client information. Simple/smart - for a smart can send RTP (day ahead, current). If Simple - don't have sophisticated control, won't look. Can map into simple - from 10-20 all the time, 20-60 dim the lights, 60 or more do shedding and shifting.  Directly map into simple clients. ON the conf side - clients receive, HML hourly, does this particular device say "certify" that EI OADR 2 - conform to simple or smart client information.


T : assume a market with simple sine waves. Evening down 10%, up 10% is high. In another market - wider swing. Say now have something on top?  GG good point, not a conf statement. Impl is customer specific - what you can do at strat side is indep of conformance. Can't get it done - customer side - see dynamic price paper. Example on mapping prices to simple operation is just one example. Look at LMP - CAISO. Moderate may not be any more. How do you address price vol at the customer side. WTC: HML - only that H>M>L .

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira