[OASIS Issue Tracker] Commented: (ENERGYINTEROP-474) eiEnroll Notin WD25

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

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

Bruce Bartell commented on ENERGYINTEROP-474:
---------------------------------------------

The replacement for Register Resource obviously will not make it in CD02.

This is not a new topic. We had several TC workshops on this. There was a mapping document for Resource contributed on 2/14/2011 http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/41128/Service%20Inventory%20Mapping%20OADR%20to%20EI%2020110210_bb.xls
We discussed the contents in several TC workshops. (Look at the DR Resrouce tab, it may jog your memory.)

It is based on the Register Resource service defined in the contribution on 12/8/2010 http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/40522/OpenSG%20OpenADR%20SD%20-%20WS%20r0.91.doc. The Service  Defintions are based on the requirements and data objects defined on the System Requirements Specification contributed 9/29/2010
http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/40522/OpenSG%20OpenADR%20SD%20-%20WS%20r0.91.doc

At some point the Virtual End Node becomes a real end node. We must be able to associate the Resource with a meter (Service Delivery Point) at the end, otherwise none of this works. The Resource also has capbilities and constraints that are needed to do planning by the aggregators or utilities. 
As far as I can tell, most or all of the elements are already defined. Ramp rates can represent capabilities (although IRC contributed additional classes here), and there are resource constraints already defined in EMIX. Nobody asked for a nameplate.


> eiEnroll Not in WD25
> --------------------
>
>                 Key: ENERGYINTEROP-474
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-474
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: wd25
>         Environment: Bartell
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>
> The enrollment services are not in wd25 in spec or schema payloads.
> Is this going  to be in CD02? or later?
> I am assuming that this is where the resoruce "capabilities and constraints" will be defined.
> Capabilities as what can be shed/generate over time (ramps) and contraints as min/max per # items that were already defined for resoruces.

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