[OASIS Issue Tracker] Commented: (EMIX-490) PAP03 Req #2: apparentgap; suitability across entire smart grid

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

    [ http://tools.oasis-open.org/issues/browse/EMIX-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26962#action_26962 ] 

William Cox commented on EMIX-490:
----------------------------------

NAESB's consensus Business Practice Standards for PAPs 03, 04, and 09 call for randomization in PAP09, where the control signal is defined. This is parallel to how e.g. 61850 does it, combining the signal information model with schedule information. By factoring out schedule and including the smoothing (more than randomization) information with the change message exactly the same effect is gained.

See separate technical note on block and tier price information. This work in progress, outside the specification, shows the expression of the Block and Tier tariff information model; any environment that supports that can take EMIX intormation and use it.

Cross-cutting standards such as this are ineffective if their information model is a union of all consumers' information models; SEP2 has reached 0.7 at this point, and the price information can be used in an SEP and any other facility environment.

Recommend close no action.

> PAP03 Req #2: apparent gap; suitability across entire smart grid
> ----------------------------------------------------------------
>
>                 Key: EMIX-490
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-490
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>    Affects Versions: CSD03/PR03
>         Environment: Aaron Snyder
>            Reporter: Aaron Snyder 
>            Assignee: William Cox
>
> Requirement Text:
> The price model shall be suitable for use across the entire Smart Grid.
> Apparent Gap:
> Not suitable across entire grid because it doesn't yet map to SEP2.0 which is expected to operate intra-customer premise and at the ESI boundary. Also WS-Calendar doesn't support randomization of behavior relative to price signals.

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