[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] Registration and Party IDs
Attached is the set of defined terms and actor relationship diagram that the IRC prepared for the NAESB wholesale requirements phase of PAP09. This is the agreed-upon terminology that was also adopted by the retail group working on PAP09 at NAESB. These are redline versions of the final standards. I believe that NAESB reached some type of agreement to share ratified versions of the standards with OASIS. Much of the terminology below does not line up with generally accepted electric industry terminology. Additionally, the use of a single term (such as resource) to represent multiple types of actors makes it much more difficult to understand EMIX. Regards, Donna Donna K. Pratt Manager, Demand Response Products New York Independent System Operator 10 Krey Boulevard Rensselaer, NY 12144 Tel: 518-356-8758 From: Ed Cazalet [mailto:ed@cazalet.com] Please see my update to David’s definitions below.
Edward G. Cazalet, Ph.D. 101 First Street, Suite 552 Los Altos, CA 94022 650-949-5274 cell: 408-621-2772 From: Considine, Toby (Campus Services IT) [mailto:Toby.Considine@unc.edu] I think it has to be. If a Party can register resources in two different market contexts, then it can have more than one account…. Let’s walk through the range of this week’s examples that EdK and Phil provided Chain, Ikea, multiple branches, in multiple Utility territories, potentially working with a different aggregator for each state. Say it enrolls with EnerNOC for Northern CA, directly with Sempra for San Diego, with SCE for Los Angeles. If the Party is IKEA, then that is three accounts… Single store, Edkea, multicast from ESP (which may be PG&E) to the components of the registered resource. Commercial Building, registers each floor as a separate resource in the same account to enable the ESP to give him an human-friendly UI for response Commercial Building, registers AC as a DR asset with one ESP, registers all drives and motors in building to Utility as a Regulation service. Resources registered with two different companies, likely to be two different Accounts…. This is why I think we are not clear yet. We have an ESI (which is a black box) with is associated with one or more Measurement Points which may be Meters or Virtual Meters, which may be Provider-owned or not, in accord with market rules. An ESI can provide a number of services on behalf of a Party. Is the ESI identifier a PartyID? If a [building] has two ESIs, does it have two PartyIDs? I am not clear yet. The thing associated with [owning?] an ESI can [enroll or register] with a number of other Partys exposing services. To do so, it presumeable sets up a means of payment, of billing, and may meet certain requirements [bond, line of credit, …] that qualify it to participate in that business relationship. I think we said on Wednesday that Utilities call this Enrolling, and ISOs Registering. It could be said that the Account is the name of this pre-qualification to do business. [Maybe we should call it Qualification]. This suggests that Account is many to Many. In the examples above: Ikea might associate each new store built in SCE territory with an existing Account with SCE. This would require an ESI ID of some kind which can be either assigned to or associated with an Account. If the ESI ID == PartyID, then the Account might be the thing that can persist across Chain Stores… If this is correct, then we have: An ESI comes to market and is assigned a PartyID. During Enrollment in each Market, it is either assigned an Account, or becomes associated with an existing account. During Registration, a Party that wishes to act as a VEN at defines a Resource (one or more WS Addressing points, and one or more Measurement Points, and a capability) with an Account in the market it is registering in. A Party may do this several times. During Registration, a Party that wishes to act as a VTN at does what… During Registration, a Party that wishes to transact does what… Under this Model, - an ESI can have any number of Accounts. - An Account can be associated with any number of ESIs, each identified by a PartyID. - A Resource works within a single Account as administered by a single ESI in its interactions with a single Market The separation of the Admin and Operational interfaces of the VEN discussed yesterday I will not go into until we agree on the above… [Note: Ed Cazalet’s reply crossed in the mail, and I believe it is compatible with the model below “If this is correct”] tc "It is the theory that decides what can be observed." - Albert Einstein
From: Gerald Gray [mailto:gerald.gray@guiding-principle.com] Is it possible for a Party to have more than 1 account? From: Toby Considine [mailto:tobyconsidine@gmail.com] On Behalf Of Toby Considine If a party is a business entity with an associated account, what is an account? Or is party what happens during [was registration, now identification? credentialing? Exposition?] An account is created (or associated) during [enrollment or registration] Resource associated with account during [registration or enrollment] "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
From: Holmberg, David [mailto:david.holmberg@nist.gov] Updated definitions based on the discussions on the EI call yesterday. Below and attached (includes notes).
From: Holmberg, David A spreadsheet with some definitions for discussion.
From: Considine, Toby (Campus Services IT) [mailto:Toby.Considine@unc.edu] 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
From: Holmberg, David [mailto:david.holmberg@nist.gov] 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 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
|
Defined Terms-Phase 2 redline-2010-12-07.doc
PAP 09 Wholesale (revised jb November 22, 2010)-dkp12072010.doc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]