[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: FW: [emix] Call and Put Options for EMIX.
The equivalent statement for EnergyInterop is: “The Energy Interoperation TC works to define interaction between Smart Grids and their end nodes, including Smart Buildings, Enterprises, Industry, Homes, and Vehicles. The TC develops data and communication models that enable the interoperable and standard exchange of signals for dynamic pricing, reliability, and emergencies. The TC's agenda also extends to the communication of market participation data (such as bids), load predictability, and generation information.” "If flies are allowed to vote, how meaningful would a poll on what to have for dinner be, and what would be on the menu?" - Unknown
From: Considine, Toby (Campus Services IT) Remember: EMIX is Price and Product communication. Period. What are we buying. What are we selling. How do we describe the product. EnergyInterop is the interactions to acquire energy, including the important acquiring someone else’s negative consumption. EnergyInterop is where contracts for energy behavior and deliveries are offered, executed, and performed. The message payload for EnergyInterop is usually EMIX. Quality is a part of the Product. It must also be separable to describe the actual delivery. This sounds like a separate component within EMIX. TWIST looks like an EnergyInterop thing. All three of David’s tiers look like EnergyInterop things to me. We keep going down these ratholes. We need to stay in the scope of the respective charters. “The OASIS eMIX TC works to define standards for exchanging energy characteristics, availability, and schedules to support the free and effective exchange of information.” "If flies are allowed to vote, how meaningful would a poll on what to have for dinner be, and what would be on the menu?" - Unknown
From: David RR Webber (XML) [mailto:david@drrw.info] Toby, I'm still grappling with all this - and seeing we need tiered layers and clear separation. Right now we seem to be mixing it all into one big cement mixer and grinding it up - that is NOT good! OK - so who many types of EMIX messages are we building? - Tier 1 - eMarketplace for commodity trading (EMIX-CT) - Tier 2 - Contract, marketplace and delivery management (EMIX-eBay) - Tier 3 - Power delivery (EMIX-PWR) I'd suggest that Tier 1 - we really need to look at existing stuff - like TWIST - instead of reinventing the wheel. And then just publish a TWIST-EMIX profile and workflow patterns with specific power-centric criteria / codelists / vocabulary. Similarly Tier 2 - OASIS ebXML Contract work covers this already - again just need a profile showing how. Tier 3 - OK - this is IMHO where we do build XML - maybe two sets EMIX-PWR (power exchange) and EMIX-GRID (device configuration) So the answer to the question is Yes! But lets see how to do that using existing work like TWIST...? Thanks, DW
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]