-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: CTSPR01
-
Fix Version/s: ctsWD14
-
Component/s: cts
-
Labels:
-
Environment:
Horia Pop; Lateral Inc https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html
-
Resolution:
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]
| Field | Original Value | New Value |
|---|---|---|
| Labels | ARCH-CONF |
| Status | New [ 10000 ] | Open [ 1 ] |
| Environment | [https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html] Horia Pop; Lateral Inc | Horia Pop; Lateral Inc https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html |
We have removed Transactive State from the respective payloads.
Transactive State is described on lines 561-566 in CTS (https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01.html#_Toc85711690), and references EMIX (http://docs.oasis-open.org/emix/emix/v1.0/cs02/emix-v1.0-cs02.html#_Toc319594523).
There are subsets of Transactive State profiled in the TEMIX profile of EMIX and in the TEMIX profile of Energy Interoperation; the CTS subset excludes Indication of Interest from the EMIX TEMIX profile.
Software engineering has generally evolved beyond the object in which you read a flag to determine what the actual type is. Instead the trend for some years is to strongly-typed objects. CTS follows this latter set of rules, so transactive state should be eliminated.
| Assignee | Toby Considine [ toby.considine ] | William Cox [ williamcox ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | ctsWD14 [ 17669 ] | |
| Resolution | Remove Transactive State and discussion. | |
| Status | Resolved [ 5 ] | Applied [ 10002 ] |
Transition all APPLIED to CLOSED per Energy Interoperation TC Motion April 28, 2022.
| Status | Applied [ 10002 ] | Closed [ 6 ] |
Transactive State is described on lines 561-566 in CTS (https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01.html#_Toc85711690), and references EMIX (http://docs.oasis-open.org/emix/emix/v1.0/cs02/emix-v1.0-cs02.html#_Toc319594523).
There are subsets of Transactive State profiled in the TEMIX profile of EMIX and in the TEMIX profile of Energy Interoperation; the CTS subset excludes Indication of Interest from the EMIX TEMIX profile.
Software engineering has generally evolved beyond the object in which you read a flag to determine what the actual type is. Instead the trend for some years is to strongly-typed objects. CTS follows this latter set of rules, and transactive state should be eliminated.