RE: [energyinterop] Updated transactive payloads

["Ed Cazalet" <ed@cazalet.com>]

Clarification:
 
CreateTender allows for multiple Tenders in the Payload.  Each Tender is an
EMIX Product Description applied to an EMIX Base.  Only one EMIX Base with
one EMIX Product Description is allowed per Tender.  A Tender may be for
only a single interval or for multiple intervals as defined by the Product
Description and the EMIX Base..  Depending on Market Context the multiple
Tenders to a single Tenderee/CounterParty may be evaluated by the
Tenderee/CounterParty individually or simultaneously (such as by an ISO
dispatch optimization).  All such market processes are out of scope for EI
and EMIX. Note each Tender in CreateTender is bilateral with both a Tenderer
(Party) and a Tenderee (CounterParty).  One market process rule might be
that a Tender to an ISO or ISO-like CounterParty may not be canceled or
allowed to expire during a window of time specified by the market rules
during which the clearing of multiple Tenders is carried out.  Each Tender
can be IntegralOnly (True or False) as permitted by market rules expressed
in the Market Context.
 
Similarly, Transactions created by accepting a Tender using
CreateTransaction are always a Transaction between a single Party and a
Single CounterParty for a single EMIX Product Description applied to single
EMIX Base. A market such as an ISO may Create such Transactions
simultaneously per its market rules which are out of scope for EMIX and EI.
 
Correction to 1. below --  Change to
 
1.      For EiCreateTender, CreateTransaction and CreateQuote we need a
TenderID(1..*], TransactionID[1..*] and QuoteD[1..*]
Ed
 
Edward G. Cazalet, Ph.D.
101 First Street, Suite 552
Los Altos, CA 94022
650-949-5274
cell: 408-621-2772
ed@cazalet.com
www.cazalet.com
 
From: Ed Cazalet [mailto:ed@cazalet.com] 
Sent: Wednesday, October 12, 2011 9:50 PM
To: 'wtcox@CoxSoftwareArchitects.com'; 'energyinterop@lists.oasis-open.org'
Cc: 'Toby.Considine@gmail.com'
Subject: RE: [energyinterop] Updated transactive payloads
 
Looks good, suggest following changes:
 
1.      For EiCreateTransaction the Transaction ID should be deleted.
Assume the transactionId when the EICreatedTransaction payload is returned.
Follows EiCreateTender and EiCreateQuote.
2.      EiCreateTransaction needs  EiTransaction: EITransactionType[1..*].
Follows Tender and Quote
3.      I believe Create Tender, Transaction and Quote payloads need
TendereePartyID, CounterPartyID and QuotedPartyID all [1..*], respectively.
4.      Likewise I believe Created Tender, Transaction and Quote payloads
need TendererPartyID, PartyID and PublisherPartyID , respectively.
5.      For EiCancelQuote quotedrPartyID should be quoterPartyID ; there are
a few other similar typos in EiRequestTender and EiCanceledQuote.
6.      EiRequestTender needs MarketContext[1..*]
 
 
Terms like Bid, Offer, Order, Bidder, Offerer were rejected early in favor
of Tender, Party and CounterParty with Side = Buyer or Seller for the Party.
There is are lots of confusing conventions in the various market, but we
have a system and should stick with it.
 
Edward G. Cazalet, Ph.D.
101 First Street, Suite 552
Los Altos, CA 94022
650-949-5274
cell: 408-621-2772
ed@cazalet.com
www.cazalet.com
 
From: energyinterop@lists.oasis-open.org
[mailto:energyinterop@lists.oasis-open.org] On Behalf Of William Cox
Sent: Wednesday, October 12, 2011 8:27 PM
To: EITC
Cc: Ed Cazalet; Toby Considine
Subject: [energyinterop] Updated transactive payloads
 
All --

Here are cleaned up versions of the transactive payloads after several long
discussions. This is adjusted from the style I showed October 12 to one
where the tops of groups line up, making it easy to see what's not in a
pattern.

BTW my EAP is based on wd29 schemas. Available (I'll upload it) on request.

Issues remaining (see also the attached notes file and the diagrams for
details)

(1) Naming of parties.  For example, in Request:

Tender:    Tenderer, Tenderee
Transaction:    Party, CounterParty
Quote:    publisher, quoted

I've gone to party/CounterParty in Transaction, tendererParty/TendereeParty
in Tender, and publisherParty/quotedParty in Quote.

Gerry may be right on the interactions - if I receive a Create* I know that
I'm the counterparty. If I send a request* I could be either (are the
queries symmetric? need for the data queries).  So maybe it's not an issue.

(2) If we keep using Tender-specific party names, it should probably be
"TenderER" and "TenderEE" (to emphasize the differences). That's a global
(EiClasses and EiPayloads) change.

BTW investorwords.com says that the US term is Bidder.  I don't think that
has the same meaning. So I'm happy with "tenderer/tenderee" but I'm getting
happier with party/counterparty.

RequestOR is listed with RequestER  in my dictionaries. 

(3) How to show these figures - the parallel diagrams have proven extremely
valuable. Do we want/need a repeat or a subset for the respective sections?

(4) Ed Cazalet and I have come to the conclusion that a single emixBase is
what's needed in a tender, with 1..* eiTenders.  But Quote and Transaction
have 1..* and are not quite aligned.

Suggestions welcome on this point.

(5) I've added attributes to EiQuoteType, EiTenderType, and
EiTransactionType including the ...ID.  Should the transacting parties be
added?

Thanks!

bill
--
William Cox 
Email: wtcox@CoxSoftwareArchitects.com 
Web: http://www.CoxSoftwareArchitects.com 
+1 862 485 3696 mobile 
+1 908 277 3460 fax

Attachment: Transactive Payloads.jpg
Description: JPEG image

Attachment: Transactive Payloads.jpg
Description: JPEG image

Attachment: Transactive Payloads.jpg
Description: JPEG image