[OASIS Issue Tracker] Commented: (ENERGYINTEROP-207) Critical:Include simple client information in EiEvent Service text and figure 9(WD15, ln. 619-644, figure 9)

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

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23629#action_23629 ] 

Toby Considine commented on ENERGYINTEROP-207:
----------------------------------------------

c) Agree that NTP et al. are just fine for Time. It is an interesting question whther in a given program or given package, Assets should be required to use the VTN as their [NTP] server... In any case, that would be out of scope.

b) I though that after Florida, and with Albert's guidance, Normal / Mod / High became the Program, that a Program was monotonic increasing on some severity / scarciy scale, and that any program could be defined with the information: Levels: 7, Normal Price: 3, [Current] Level: 4. 

Rish: do you think the entire program set, as above, should be re-communicated in the EventStatus?







> Critical: Include simple client information in EiEvent Service text and figure 9 (WD15, ln. 619-644, figure 9)
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-207
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-207
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: wd15
>         Environment: Girish Ghatikar wd15 lines 619-644 and figure 9
>            Reporter: Girish Ghatikar 
>            Assignee: Girish Ghatikar 
>
> OpenADR 1.0 EventState.xsd includes SimpleClientDREventData with following elements, which are similar to those offered by other standards  (e.g., Zigbee/SEP):
> a, DR Event status (EventStatus in OpenADR 1.0)
>  - The EventStatus can take these values: NONE, FAR, NEAR, ACTIVE, CANCELED
> b. Operation Modes (OperationModeValue in OpenADR 1.0)
>  - the OperationModeValue can take these values: NORMAL, MOD, HIGH, SPECIAL
> c. Current Time (currentTime in OpenADR 1.0)

-- 
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