Next in thread → Next in month →

[OASIS Issue Tracker] (ENERGYINTEROP-707) Sides or Signs

From
OASIS Issues Tracker <>
Date
2022-04-28T02:43:02+00:00
ID
Thread
[OASIS Issue Tracker] (ENERGYINTEROP-707) Sides or Signs
[ https://issues.oasis-open.org/browse/ENERGYINTEROP-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-707:
--------------------------------------
    Resolution: 
The point on signed values is well-taken; Energy Interoperation 1.0 uses signed "curtailment" for DR events.

The Energy Interoperation base standard is far more complex for Tenders and Transactions - the base type is EmixBaseType, which has been greatly simplified in CTS.

The use of Side rather than a signed quantity integrates and works with financial market terminology.

No action.


> Sides or Signs
> --------------
>
>                 Key: ENERGYINTEROP-707
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-707
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Donald Hammerstrom https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00008/2111DJH_CTS_Review.pdf
>            Reporter: Toby Considine
>            Assignee: William Cox
>            Priority: Major
>              Labels: ARCH-CONF
>
> There are 30 specific recommendations in the "Specific Recommendations" section of the submitted Hammerstrom paper. I have numbered them all for traceability as I recombine them into specific issues. The original white paper/submission can be read in the URI under "environment"There are 30 specific recommendations in the "Specific Recommendations" section of the submitted Hammerstrom paper. I have numbered them all for traceability as I recombine them into specific issues. The original white paper/submission can be read in the URI under "environment"
> 4. Line 64: The âSide attributeâ in an energy market is unneeded if signed quantities are used. How would a battery system offer to transition from being a buyer to being a seller at a given price, for example? It is potentially problematic that a baseline is being assumed but not defined for all TE implementations.Â11. Section 2.2.2: The attribute Side (i.e., Buy or Sell) is unneeded if signed quantities are employed.Â



--
This message was sent by Atlassian Jira
(v8.3.3#803004)
Next in thread → Next in month →