[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (EMIX-129) Block Power Price MustHave Blocks and Tiers
[ http://tools.oasis-open.org/issues/browse/EMIX-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26729#action_26729 ]
Toby Considine commented on EMIX-129:
-------------------------------------
The primary question is, can the tariff be represented, not does it look exactly like SE2's representation. As I read your comments, it appears that the information to describe the tariff can be represented.
I have some questions about the comments:
(1) <!-- we should not have to specifiy a price here -->
Is the observation that it is always an absolute price? Will it always be an absolute price? It is easy to imagine a base price which varies by consumer, but uses one of the other valuers (relative or multiplier) for the tiers. Or have I missed the point?
(2)<!--why is this mandatory? -->
EMIX is an information model that specifies the information is mandatory, but not the serialization. EMIX rules specify that it could be ibnherited from. say, a market context. Information model schemas are not necesarily the same as transactive schemas. FOr example, if there is a requirement to use WS-Interoperation in a particular set of interactions, then the extensibility elements MUST be eliminated from that schema. Once again, I think that we are blurring the different between mandatory informational elements and serialization rules. I confess that I fall into that trap at elast weekly.
(3)<!-- charges is mandatory, but all of the elements are optional -->
Good catch. Do we need to delay 1.0 for this? See comments in (2).
(4)<!-- this does not vary by Time in SE2-->
But it could. Italian power often has absolute limits on consumer consumption tied to particular tariffs. THere is no reason it could not apply to a tariff here as well. It is a difference, but do you think it is a problem?
(5)<!-- For each consumption block <power:maximumEnergyQuantity> is required. The highest block does not have a maximum.-->
In many parts of the country, using more than a given amount spikes you into a different tariff, or creates multi-year demand charges, or moves you out of reisdential. A lot of the tiers are tied to social engineering and social purposes, and maxima that throw you into a "high tariff if you use industrial amoutns of energy for your mansion" are likely. As you say, 99999 is possible, but I suspect that service to a residential house does not support that.
(6)emixbase requires: <emix:terms></emix:terms> (what is this for?)
see comments on (3) Any contract or tariff could have terms, but I agree that the terms collection should allow minoccurs=0.
(7)<emix:marketContext></emix:marketContext> (can we use this for tariff name? must be a uri?)-- we need a way to identify which tafiff this is for
Spot on. (I do not know what the tariff is is named)
www.pge.com/tariffs/tiered2011?
www.cpuc.ca.gov/puc/tariffs/pgetiers?
urn:pge:tariffs:redisdential-tiers-2011
It is a matter outside the scope of the TC whenter the URI is reachable, and whether, say, a PDF of the tariff is available there.
(8)<emix:integralOnly>false</emix:integralOnly> (check the definition) -- this is required. It is unclear what this is for when used in a tariff message.
If a Tier is integral only, you either buy the tier or you don't. If tiers are 0-100, 100-200, and I use 101, then I have bought the entire 100-200 tier. False means that I have not. This variable distinguishes between block purchases and requirements purchases. Many of today's residential appears always false, but there are prices in rural areas where you always buy all of the first tier, which is reflected itself as a minimum purchase per month.
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]