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-386) Need to AddBlock/Tier Tariff Message as part a Price Distribution Profile



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

Edward Cazalet  commented on ENERGYINTEROP-386:
-----------------------------------------------

Worth discussing.

While the block tariffs are not TeMIX profile compliant they are nonetheless a Tender.  I don't see a reason that all tenders in EMIX/EI need to be TeMIX compliant.  In my view the tender services should do the job.  As to another profiles for delivery to the SEP environment that is another issue.  

I fully expect that the SEP environment will have users who will want to be able to consume TeMIX services, block tariffs and OpenADR.,as examples.

I guess a question is, does the name of the service need to imply the profile or does the payload define the Ei profile?  I would expect the later.


> Need to Add Block/Tier Tariff Message as part a Price Distribution Profile
> --------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-386
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-386
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema, spec
>    Affects Versions: wd22
>         Environment: Bruce Bartell
>            Reporter: Bruce Bartell
>            Assignee: Bruce Bartell
>
> There is an example of the Consumption Block - Time of Use Tier message in EMIX.
> This needs to be defined as part of a profile in EI.
> As already discussed extensively, it  is not a transactive message -  a notice  of current retail price structure. Not sure if that means it needs to be separate from EiQuote. I am happy with any solution that keeps the intended TEMIX profile intact.
> Comments on the "example" payload are being submitted to EMIX.

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