[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (EMIX-481) EMIX Product
[ http://tools.oasis-open.org/issues/browse/EMIX-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27103#action_27103 ]
Toby Considine commented on EMIX-481:
-------------------------------------
in EMIX, a Product is a Product Description applied to a schedule, so by defintion an EMIX Product has time.
A product Description appears to be what you are looking for here.
Ancillary services are expectations for how something will perform during a period, i.e., for this availability, one needs to be ready to have this product description ready to go. Ancillary services have an embedded product, so thaat has time, or at leasdt an interval. That interval maay be specified, or unspecified, it may have an embedded "15 minutes" but no start time, or no duration at all. It can be invoked by reference "That Duration, for which there is a known uid, here, do it for 14 minutes starting at 111:47 - i.e. a known process is invoked with a schedule. What is required is the details filled out in a way that is only known at invocation.
Is the desire to create a market definition? EMIX 1.0 does not have a specification for that; we received strong guidance from the IRC and others to *not* do that. If *I* had to do that with the pieces on hand, I would use something like the standard terms, in which a product description and a set of terms are linked.
"Here is a market, for real power, must be able to respond in under 5 minutes, for up to 15 minutes...." might be an ancillary service market
"Here is a market, for real power, in 100MW bids, schedule on the hour..." might be an generation market
Are you looking for that instead? I'd be happy to work on defining one of those with current semantic elements - but I need a reality check from someone in the markets to work with.
> EMIX Product
> ------------
>
> Key: EMIX-481
> URL: http://tools.oasis-open.org/issues/browse/EMIX-481
> Project: OASIS Energy Market Information Exchange (eMIX) TC
> Issue Type: Sub-task
> Environment: IRC
> Reporter: Toby Considine
> Assignee: William Cox
>
> The text and table in this section imply that the "product description" is the service like energy, spinning reserve etc and that "product" is the generic term for offers and bids of that product description (ie. it has time, price, quantity associate with it). This is an unfortunate naming convention. It also conflicts later with the product description schema that also appears to have price.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]