[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ENERGYINTEROP-738) Alignment of Market Price Granularity and Stream Price Granularity
[ https://issues.oasis-open.org/browse/ENERGYINTEROP-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Cox updated ENERGYINTEROP-738:
--------------------------------------
Labels: CLARITY (was: )
> Alignment of Market Price Granularity and Stream Price Granularity
> ------------------------------------------------------------------
>
> Key: ENERGYINTEROP-738
> URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-738
> Project: OASIS Energy Interoperation TC
> Issue Type: Bug
> Components: cts
> Affects Versions: ctsWD14
> Environment: Toby Considine - Editing Note
> Reporter: Toby Considine
> Assignee: Toby Considine
> Priority: Major
> Labels: CLARITY
>
> In Streams, we defined Price Granularity as follows
> Stream Price Granularity
> Price granularity expressed as an exponent. Applies to all Intervals in the Stream.
> Not required for all Facets. For example, if the price granularity is -3, and the value is 1500, the price is 1.500 currency units.
> And in Market (Product) definition we have:
> Price Granularity
> PRICE_GRAIN
> The allowed price unit, e.g. Price Granularity == 10 means that that any multiple of 10 CURRENCY units is acceptable, but any price not matching, say a price of 9 CURRENCY units, is rejected.
> We need to make sure that we do not create confusion between these two definitions.
--
This message was sent by Atlassian Jira
(v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]