energyinterop — archive

RE: [energyinterop] Registration and Party IDs

From: Toby Considine <[email protected]>
To: [email protected]
Date: Wed, 27 Jul 2011 14:06:00 -0000

Some inconsistency here… If a Party is 1-1 with a VEN (if it is a VEN), and if a VEN is 1-1 with a Resource, why do we need a ResourceID? Can a resource be moved to a different VEN? Can a Resource be transferred to a different Party? Is it because a Resource can be resold by an aggregator? “You can’t have multiple Parties per customer” So are all Wallmarts in North America identified as the same PartyID? If so, Registration is primarily concerns with identifying your PartyId. tc " It is the theory that decides what can be observed ." - Albert Einstein Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com From: Holmberg, David [mailto:[email protected]] Sent: Wednesday, July 27, 2011 9:55 AM To: [email protected]; 'Bartell, Bruce'; 'Ed Cazalet'; 'Koch, Edward'; [email protected] Subject: RE: [energyinterop] Registration and Party IDs Toby, It seems you and EdC have a different perspective on Party. You seem to view it as equivalent to a resource, such that VEN is identified with a PartyID. EdC sees it as a customer with an account (or a customer with a SDP). This allows a Party to have multiple resources. Thus, a VEN has an associated PartyID, but a Party may have 0 to * Resources. Bill agrees with this, I think, or at least that a Party is not the same as a Resource. I think then that a Party is tied closely to a customer and you can’t have multiple Parties per customer. But a VEN and Resource are 1 to 1. Interesting question about VTN/VEN, buyer/seller. I think a customer has a PartyID, and enters into market transactions to either buy or sell some resource. If selling, there should be an indication of that role, but not a SellerID, and there will be an associated ResourceID (for the generator or DR resource). If buying, there will be an indication of that role, and no associated ResourceID. A VEN should have an associated PartyID, SDP (meter mRID maybe, premise location?), and URL. Whether something is acting as VEN or VTN is maybe simply a role that is also indicated in a service exchange. David From: Toby Considine [mailto:[email protected]] On Behalf Of Toby Considine Sent: Wednesday, July 27, 2011 9:10 AM To: 'Bartell, Bruce'; 'Ed Cazalet'; Holmberg, David; 'Koch, Edward'; [email protected] Subject: RE: [energyinterop] Registration and Party IDs Slight change of pace here – into the schemas We seem to be congealing around “Registration is how you get a Party ID” A VEN is identified by a PartyID A VTN is identified by a PartyID A Transactive [agent] is identified by a PartyID Several Parties may be part of some larger entity. If the Parties are acting as VENs, we may call that larger entity a Customer. - A Customer is the business entity behind 1-to-many VENs that have a common relationship to the entity behind a VTN , each identified by a PartyID. - Is there a common entity behind multiple VTNs that should have an ID as well? - Is there a common entity behind multiple [agents] as well? Parties have Roles: “Buyer” and “Seller”. Should we have a BuyerID and a SellerID instead of a CustomerID and “%%%”? The eiParty is an existing type. The type consists of a partyID, a partyName, and a partyRole. Is this correct? Does it line up with the narrative above? If so, then it implies that a party enrolling as both a VTN and as a VEN should have two PartyIDs. This does not feel correct. Where does the eiParty fit in the Transactive world? tc "He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you." - Fredrich Nietzche Toby Considine TC9, Inc TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Email: [email protected] Phone: (919)619-2104 http://www.tcnine.com/ blog: www.NewDaedalus.com