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-673) Bias in Matching Algorithm

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

William Cox updated ENERGYINTEROP-673:
Updated introduction on use of Actor and Facet terminology throughout

Expanded existing text on when and how to use a market ID as a counterparty, including when a group matching approach is used.

> Bias in Matching Algorithm
> --------------------------
>                 Key: ENERGYINTEROP-673
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-673
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Trevor Hardy, PNNL https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00000.html
>            Reporter: Toby Considine
>            Assignee: William Cox
>            Priority: Critical
>              Labels: CLARITY, MARKET
>             Fix For: ctsWD14
> page 16 line 261-262
> It has already been stated that CTS does not prescribe the nature of the matching engine but doesn't the definition of part and counter-party at least strongly imply some kind of matched bi-lateral trade? Double-auctions can artificially create the appearance of bi-lateral trades after the clearing price and quantity have been established but it would be a layer of artifice. For the concept of "party" and "counter-party" to be an integral part of CTS seems to heavily lean towards bi-lateral matching engines.

This message was sent by Atlassian Jira

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