OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-301) Section 7:Register Services should include register Resource and Asset



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

Edward Cazalet  commented on ENERGYINTEROP-301:
-----------------------------------------------

Should Registration in general be in or out of scope in EI?

We have considered registration of parties, but we could register generators, delivery points, pnodes,etc..  Where would we stop?

In the case of DR we may consider enrollment in a program for already registered customers of a retail provider.  In that context there seems to be a desire to also "enroll" DR resources.

In TeMIX an option transaction is used to define who, what and when for a call option that is DR-like.  So "enrollment" occurs in the context of a transaction.  Enrollment is not a necessary construct for TeMIX.

My suggestion is that registration is out of scope for EI and DR enrollment of Resources and possibly Assets may be in scope in EI.

> Section 7: Register Services should include register Resource and Asset
> -----------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-301
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-301
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: csd01 - Public Review Draft
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>
> Registration process also includes the Registration of Resources and Assets.
> Registration of Resources and Assets is for the purpose of:
> •	identify a DR Resource for communications purposes;
> •	establish DR Resource accounts for accounting purposes;
> •	collect information from DR Resources prior to DR events for the purposes of determining which DR Resources to call upon during a DR Event; and to determine the nature of the DR signals to send to the DR Resources.

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




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]