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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

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


Subject: RE: [emix] [OASIS Issue Tracker] Commented: (EMIX-129) Block Power Price Must Have Blocks and Tiers


Any change to EMIX during a public review period delays Energy Interop by two months?!

We voted out the PR for EI a month ago and it is still not published. Then that makes at least three months.

 

We agreed to defer the resolution of the open issues on the SE2 compatible message until the public review period of EMIX in order to expedite the EI PR document, and now you tell me any change adds three months to the EI process.

 

Bruce Bartell

Xtensible Solutions

Mobile: +1.321.258.6500

bbartell@xtensible.net  |   www.xtensible.net

 

-----Original Message-----
From: OASIS Issues Tracker [mailto:workgroup_mailer@lists.oasis-open.org]
Sent: Thursday, August 04, 2011 5:00 PM
To: emix@lists.oasis-open.org
Subject: [emix] [OASIS Issue Tracker] Commented: (EMIX-129) Block Power Price Must Have Blocks and Tiers

 

 

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

 

Toby Considine commented on EMIX-129:

-------------------------------------

 

Good set of comments.

 

(0) In the OASIS process, any change necessitates necessitates another PR before any vote on a Committee Specification

- If OpenADR 2.0 is waiting on Energy Interop 1.0

- If Energy Interop 1.0 is waiting on EMIX 1.0

- If any change, by OASIS rules, necessitates another round of review

 

- then the ? "Do we need to delay 1.0 for this?" is "Do you want to delay EMIX until at least another 6 weeks, and thereby delay Alliance goals for another two months to get rid of an optional element?"

 

1) The price the customer is charged is in the tiers. I do not know what this other non-tier price would apply to in this case. I think that if it is a flat price it would be a different message.

>> got It. Its there because its in the base class. Perhaps it should be inherited by all intervals/tiers in which it is otherwise not specified. Perhaps it should be the base rpice on top of which relative or multiplier prices are used in all Tiers. Perhaps it should be ignored. Suggestion?

 

 

2) I don't understand the reply. Why are we representing power units in a retail tariff in the first place. And why would it vary by interval?

 

The first rule of EMIX is a universal language for making discoverable information known to the device. International markets are often in Joules instead of Watts. We can't justy say "the toaster should know it is in a California residential tariff"

 

As per interval, see the EMIX conformance rules. The information must be knowable for each interval, per the *information* model. That does not mean it must be *expressed* per each interval.

 

3)-

 

4) The top limit for each tier is used to order the tiers. There is no requirement that valid standards-based xml processing perserve order in any collection. The max seems an easy way to order them.

 

5)There are no comments on the original request. There will always be a last tier. Are up prposing that we require a huge number in the last one? or some other way of indicating this is the last tier.

 

>>I know that my service and my meter have definite knowable non-infinite maximum delivery rates. Perhaps the top tier should be the overall price (see 1), and you fall into it when you fall off the top. This would reduce the tiers per interval.

 

6) -

 

7)I can't gaurantee that they are all in url format, but I think almost anything without a space passes the restriction.

>> Its anyuri, not url, so that should be fine.

 

8)-

 

I think we are converging....

 

> Block Power Price Must Have Blocks and Tiers

> --------------------------------------------

> 

>                 Key: EMIX-129

>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-129

>             Project: OASIS Energy Market Information Exchange (eMIX) TC

>          Issue Type: Sub-task

>          Components: schema

>    Affects Versions: wd35

>         Environment: Bruce Bartell

>            Reporter: Bruce Bartell

>            Assignee: Toby Considine

>             Fix For: wd20

> 

> 

> Block Power rates have a price that is dependent on Block and Tier.

> Blocks are a the price boundaries based on consumption over time. Tiers are a dimension based on time of use.

> See spreadsheet at http://www.oasis-open.org/committees/download.php/42240/PriceMsgMapping%2020110519.xls and search for TimeTariffInterval

 

--

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

 

       

 

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.  Follow this link to all your TCs in OASIS at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

 

 



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