[OASIS Issue Tracker] Commented: (EMIX-358) TemixType is missingConstraints

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/EMIX-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25160#action_25160 ] 

Edward Cazalet  commented on EMIX-358:
--------------------------------------

TeMIX is set up for automated processing.  It is also intended to work with standard length intervals. For example if some wants to offer a tender for a specific hour then can do.  They don't need a constraint.  Constraints don't look like a good way to do standard intervals.  ws-calendar aready had standard durations like a minute, hour, day or month.  All we need to required is that the interval start on the beginning of the minute, hour, day, month or year , for example.

We can have a emix tender with all kinds of constraints and ramp rates and lead time.  A Temix Tender has an expires time. That is all we need. if your accept a Tender before a tender expires then you must start delivering on the Transaction at its start time.

In the case of a  temix option it could be an option for a month and with a notice time you can excise the option for any hour.  But with an intent to keep things simple i don't want to put any more complexity into TeMIX.  There are other ways using the basic TeMIX to most things the complex constraints etc do.
l
We one creates lots of product all slightly different then commerce is more difficult.  How do I compare the prices of tenders for products with different constraints when the constraints are so complex and arbitrary.  And then when I get a portfolio of all of these different products I will need complex tools to evaluate them.  Standardize product are essential to commence and TeMIX is a subset of eMIX product that are chosen to meed the needs of the industry.  The product set may evolve over time.  And we can have whatever constraints, ramp rate, complex tariffs, load curtailment and generation resources we want to build into EMIX to better deal with current practice.

Also conformance testing for TeMIX having so many constraints available just adds to the difficulty.





> TemixType is missing Constraints
> --------------------------------
>
>                 Key: EMIX-358
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-358
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>          Components: schema
>    Affects Versions: wd22
>         Environment: WIlliam Cox
>            Reporter: William Cox
>             Fix For: wd23
>
>
> The TemixType in the schema is missing Constraints. See Table on line 406 and issue EMIX-357.

-- 
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