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

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

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


Subject: [OASIS Issue Tracker] (ENERGYINTEROP-730) Transactive State


     [ https://issues.oasis-open.org/browse/ENERGYINTEROP-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-730:
--------------------------------------
    Labels: ARCH-CONF  (was: )

> Transactive State
> -----------------
>
>                 Key: ENERGYINTEROP-730
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-730
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: [https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html]ÂHoria Pop; Lateral Inc
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>            Priority: Major
>              Labels: ARCH-CONF
>
> *Transactive State*
> Transactive state values are not documented in CTS nor [EMIX]. While one can imply the meaning, the boundaries of each state seem vague when analyzed. Is there an implied order too? What state would a delivered and settled tender take? Delivery or publication?Ã What about in a market where settlement occurs at the time of the transaction before delivery?
> Having the same transactive state map over both tenders and transaction is a stretch when taking the individual values.Ã This dual-use also becomes a source of conflictual information and implementations intent between a tender transactive state and the transaction transactive state.
> _[Lines 555, 599]_



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