[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=26340#action_26340 ] 

Toby Considine commented on ENERGYINTEROP-474:
----------------------------------------------

This is because there is no real defintionion of Enrollment yet

There has been mention on the calls (and side conversations) that the IRC was going to weigh in with specific enrollment requirements during the review period. Understanding enrollment is also critical to underastanding the VEN/Respurce issue that is one of the weakest areas of the current specification.

During Enrollment, a VEN registers (itself as a Resource [EPRI]) (multiple Resources [others]) to particpate in Market Contexts....What does that mean? 

What does it mean to enroll a resource, and what information should be exchanged? Is it the EMIX Resource *exactly*? Is it something else? We know that some RUCs have specified a social component to DR, i.e., demographics rather than systems. For an aggregator, is 500 water heaters under contract a Resource? How about 500 homes of a special Demographic? There is an unresolved notion that a VTN can ask all its VENs for the nameplates of all their resources. Doing so obliterates the "E" in VEN.  These issues are all tied into the Enrollment Issue.

See the collector issue http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-473 and all the Deferred issues in this space for soem more.

> 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