[OASIS Issue Tracker] (ENERGYINTEROP-726) Tender Update

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

William Cox updated ENERGYINTEROP-726:
--------------------------------------
    Resolution: 
No action.

A capability to Update Tender potentially creates complex distributed agreement protocol issues. What is the status of an already issued contract that partially consumed a Tender, and still referencing that Tender, if the Price and/or the Quantity of that tender is Updated? In cases where the matching engine uses Time if Issue to award contract to the earlier of two similar tenders, is the original Tender date or the Updated Tender Date used?

The indicated action, that the Actor cancel the original tender and issues the new, is the appropriate choice. The expectation is that any part of the Tender consumed by a Contract prior to the "cancel" stands as it is.


  was:No action.


> Tender Update
> -------------
>
>                 Key: ENERGYINTEROP-726
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-726
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Horia Pop; Lateral Inc [https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html]
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>            Priority: Major
>              Labels: ARCH-CONF
>
> *Tender Facet - Update*
> The standard does not call for an Update Tender payload. There are multiple practical instances where an actor would have to update an uncommitted tender.Ã The alternative of canceling and resubmitting, introduces more implementation complexity, excessive communication, and dead time of potential missed transactions.Ã
> _[Lines 545]_



--
This message was sent by Atlassian Jira
(v8.3.3#803004)