[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] Energy Interop Resources
Well, as you logged in Jira the other day, the use of the Word Resource in EI is different than the use of the word Resource in EMIX I am open to 1) Suggestions for naming this thing. (“Guava”) 2) Words to use for non-recursive definitions of the “Guava” Tc "It is the theory that decides what can be observed." - Albert Einstein
From: Ed Cazalet [mailto:ed@cazalet.com] Some suggestions. Let’s not use the term “products” for “resources” . Resources are a means of providing products. A VTN may purchase the right to use a VEN resource capability to produce energy products. 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] As requested, a preliminary write-up of our Resource discussions. For comments, please use the numbered PDF. Thanks tc Energy Interop Resources (which may, as Ed Cazalet suggested, be misnamed) As defined in the EPRI white paper, all interaction is between the VEN and the VTN. Neither the VEN or the VTN can interact through the other or see past the other. EI is symmetric, in that a given VTN-VEN pair could swap rules for a different market interaction. EI is recursive, in that a VEN MAY be the interface to a microgrid that is itself managed by the VTN-VEN interactions of EI; in that internal market the system which exposes a VEN interface to the outside world may expose a VTN interface. The inner workings of the “internal” microgrid might be by BACnet, or by LONTalk, or by OPC, or by SEP, or by KNX, or by any mix of open and proprietary protocols. The “internal” microgrid might be a municipal utility, an office park, or an industrial site that manages its internal energy using Energy Interoperation. Whatever the communications and interactions of the internal grid, the direct interactions through the exterior-facing VEN are the same: none. Resources as Distinguishable ProductsDuring enrollment, a VEN may choose to register one or more products with the VTN. These products are known as Resources. The VTN has no direct interaction with these resources. As in a restaurant, wherein the customer may request published menu items from the waitress, the VTN may transact for published resources from the VEN. Just as the customer is not allowed to fetch food from the kitchen, nor to order off menu meals, so the VTN is not able to interact directly with the systems that underlie each resource, or to request resources that are not registered. The products represented by the resources may be distinguished by any number of characteristics. EMIX product definitions are distinguished by attributes that include schedule, location, and source and responsiveness. Investopedia defines product differentiation thus: It may be as simple as packaging the goods in a creative way, or as elaborate as incorporating new functional features. Sometimes differentiation does not involve changing the product at all, but creating a new advertising campaign or other sales promotions instead. The products represented by EI Resources may be as concrete as an industrial stone crusher or as abstract as an aggregator’s product, “Air Conditioning for the Elderly”. A Resource may be able to respond both up and down, as can a domestic water heater, or have unidirectional gradations of response, as might a thermostat. A VEN may even wish to register Resources for which no response is possible, say, at-home medical equipment. EI makes no assertion as to what might distinguish two products or as to why different resources are registered by the same VEN. EI does not require that all load controlled by a VEN be indicated in resources. There may be market rules that require such “full registration” for all participants, but EI does not. Enrollment and Withdrawal of ResourcesA VEN MAY choose to enroll a single Resource, and reveal no information about its internal systems. A VEN may have no Resources. Some markets may require that all participants Enroll, even if they are able to provide no resources. A VEN may enroll new Resources and withdraw other Resources. Having withdrawn its Resources, a VEN may again have no enrolled Resources. A VEN with no Resources is unable to participate in VEN-VTN based markets. It is not in scope to define the market rules for VENs without Resources Ancillary Reporting RequirementsSome markets may have reporting requirements beyond those defined in Energy Interoperation. Energy Interoperation neither requires these requirements, nor supports them. Examples of such requirements discussed in the Committee include: 1. Nameplate information for exact identification of assets behind each Resource 2. Location information to identify local distribution effects of Resources exposed by a single VEN that are distributed geographically (if allowed). 3. Customer information to enable a third party to audit the market and determine if a single Resources is being sold multiple times 4. Demographic information about the people represented by each VEN. All such information is outside the scope of Energy Interoperation. To the extent that participant business rules or market rules requires this information, Energy Interoperation will support this requirement, but it will not include or enforce these requirements. (Perhaps this means that we need to have an approval status on each Resource: Pending, Approved, Refused. Perhaps only Resources approved by the VTN can come to market. If so, that Approval is out of scope; it is merely a reflection of an out-of-band Enrollment.) "If something is not worth doing, it`s not worth doing well"
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]