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: [OASIS Issue Tracker] Commented: (EMIX-313) Price Type Semanticsnot aligned for priceAbsolute, priceMultiplier, priceRelative



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

Edward Cazalet  commented on EMIX-313:
--------------------------------------

OK, here comes a RANT, but please read.  

For me the term "value" is terrible. What does it mean? 

I prefer the simple term Price. If I know the price and I know the quantity then I know the extended price that I pay or get paid (Price*Quantity).

I also don't like the term Price Absolute.  A Price is a Price.  EMIX is all about clear price communication and if we don't know what a Price is then EMIX is not much help.  

Price Increase, Price Relative are in my opinion artifacts of our current requirements tariffs and DR programs where instead of posting the correct price we post a wrong price and then change it (but maybe not really because it might only be a signal or a price level.). Why not post the correct price and be done with it.  That said, I understand that EMIX has to accommodate adders and multipliers to price for compatibility with existing tariffs and DR programs.  

Some say we need both adders and multipliers.  How about curve?  It is out of scope, so EMIX can't transmit the elements of the entire utility tariff price calculation?

Adders and multipliers will go away in time and we will regret the term Price Absolute.  Some say we need both adders and multipliers and then maybe a curve.  Shall EMIX transmit the elements of the entire utility tariff price calculation?

RANT Over.

Suggest Price or emixPrice stand on its own and not be part of an substitution group.  DR can ignore this price when it needs to.

For DR we can have an emixPriceModifier that is either PriceMultiplier or Price Adder or something else.


> Price Type Semantics not aligned for priceAbsolute, priceMultiplier, priceRelative
> ----------------------------------------------------------------------------------
>
>                 Key: EMIX-313
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-313
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: wd18
>            Reporter: Bruce Bartell
>            Assignee: Toby Considine
>            Priority: Minor
>             Fix For: wd19
>
>
> priceAbsolute, priceMultiplier, priceRelative are in OpenADR.
> Current schema uses relativePrice & priceIncrease
> Price Relative can be an increase or decrease.
> Value associated with priceRelative is +/- value; Value associated with price Multiple is a multiplier.
> The term Ratio is usually experessed with a quotient; it will only be one value in this case.
> The should be an associated unit and currency specification. I am assuming this will be provided as used in the EI message, or will have to be added as part of this element.

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