Updated definitions based on the discussions on the EI call yesterday. Below and attached (includes notes).
Energy Interop model term definitions, DGH 7/28/2011 draft 2 |
| |
Party | A customer, some business entity, with an associated account. A Party establishes an identity for itself and registers in some market in order to interact in that market (tenders and transactions). It may identify and register Resources (each with associated premise address and measurement point). A Party may also own zero Resources, such as when purchasing forward power, or trading in the wholesale markets. A Party receives a PartyID relevant to a specific Market via enrollment/registration, and thus may have multiple PartyIDs. |
Resource | The EMIX Resource.xsd model describes a range of potential operational responses. The model allows parties to describe a wide range of operations, both generation and curtailment. [EMIX Section 13]. Resources may represent a generator or a load response or aggregations. In interactions involving Resources it may be useful to describe either (1) the proposed or actual operation of a Resource, or (2) the range of capability of a Resource. EMIX Resource Descriptions are an extension of the EMIX Product Description. A Product is a description of place, commodity and schedule (intervals) in the context of a tender or transaction.
A Resource (may?) have an associated measurement point. For a physical generator or facility providing DR, this may be the utility meter. It could also be an aggregation of meter data for an aggregated Resource. Or it could be a sub-meter value or estimated measurement value (no real sensor) for some real or virtual generator within a facility.
From the perspective of the VTN, a Resource has a single associated VEN. The Resource itself may be associated with multiple VENs if participating in service interactions with multiple VTNs. |
Meter | A physical meter with a meter ID. We agreed that we would favor speaking in terms of measurement points, since meters (tradional pysical sensor on an electric line) are not always required to provide a sufficiently accurate measurement. |
VTN | A role in a service interaction, the virtual top node. A Party enters a transaction, assuming a VTN or VEN role. |
VEN | A role in a service interaction, the virtual end node. A Party enters a transaction, assuming a VTN or VEN role. |
ESI | An ESI is the service interface point, acting as VEN or VTN. There is a 1 to 1 relationship with VTN/VEN. A Resource has a single VEN/VTN/ESI for each Counter Party (MarketContext). The ESI is the logical interface point which might have a HW box you can point to, while VTN/VEN denotes the role in the service interaction. |
buyer/seller | Roles in transaction (Each transaction/tender has a side). Not clear on relationship to VTN/VEN--those apply mostly to DR it seems, whereas buyer/seller to market transactions. |
Participant | Same as Party. A Participant may be uniquely assocated with a Resource if and only if it has only one Resource, as per some out of scope DR program requirement. |
OADR client | There is no client in the OpenADR sense. A Resource has an URL for its VEN; that is, there is a single VEN speaking for the Resource to handle:
EiRegister/EiEnroll, EiAvail and EiOpt, EiFeedback and EiStatus. We may allow for EiEvent notifications to be optionally delivered to multiple URLs and optionally to pay attention to responses from each, but have a single VEN for a particular Resource that handles the services other than EiEvent responses. |
From: Holmberg, David
Sent: Wednesday, July 27, 2011 10:55 AM
To: 'Considine, Toby (Campus Services IT)'; Toby.Considine@gmail.com; 'Bartell, Bruce'; 'Ed Cazalet'; 'Koch, Edward'; energyinterop@lists.oasis-open.org; William Cox
Subject: RE: [energyinterop] Registration and Party IDs
A spreadsheet with some definitions for discussion.
David
From: Considine, Toby (Campus Services IT) [mailto:Toby.Considine@unc.edu]
Sent: Wednesday, July 27, 2011 10:05 AM
To: Holmberg, David; Toby.Considine@gmail.com; 'Bartell, Bruce'; 'Ed Cazalet'; 'Koch, Edward'; energyinterop@lists.oasis-open.org
Subject: RE: [energyinterop] Registration and Party IDs
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:david.holmberg@nist.gov]
Sent: Wednesday, July 27, 2011 9:55 AM
To: Toby.Considine@gmail.com; 'Bartell, Bruce'; 'Ed Cazalet'; 'Koch, Edward'; energyinterop@lists.oasis-open.org
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:tobyconsidine@gmail.com] On Behalf Of Toby Considine
Sent: Wednesday, July 27, 2011 9:10 AM
To: 'Bartell, Bruce'; 'Ed Cazalet'; Holmberg, David; 'Koch, Edward'; energyinterop@lists.oasis-open.org
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