[OASIS Issue Tracker] Commented: (EMIX-486) TeMix addresses thisuse case

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

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

Joshua Phillips commented on EMIX-486:
--------------------------------------

TeMIX Products are listed as a subset.  Toby explained this was an attempt to complete minimize an EMIX profile.  This is all well and good, but identifying a subset in the standard, particularly one that limits what would be  required for communicating price and product in the normative part of the standard is concerning.  The IRC supports moving TeMIX to a separate document outside of the normative document.  If it were to be edited to state : "Section 12: Examples of EMIX Profiles"  then go on to state this section provides an example of a subset of EMIX and how it can have conformance rules applied,...  Not "Section 12: TeMIX Products"  .... Conformance rules 1-10.  The difference is one is how to make a conformance / example of a subset. the other is the subset and conformance rules. 


Chat notes from 8/23 workshop:
RP discussed - maybe in a profile in EI where TEMIX's profile is. A whole subset of TEMIX conformance rules in TEMIX section 12, which I don't understand why we'd have TEMIX rather than (also) IRC profiles.

[15:10] Bill Cox: SO people interacting with those amreks would have.

[15:13] Bill Cox: B: work on it...

[15:14] Bill Cox: JP: Don't nec want an IRC profile, rather remove the TEMIX profile as a separate documeent. Other separate products and markets?

[15:14] Bill Cox: Comment earlier in the ocument - TEMIX as a specialization - here's the TEMIX product and how it works.

[15:15] Bill Cox: EC: Answer some of those questions...in terms of "is it implemented" - not sure that's a requirement in any case. Most transactions in bilateral markets are for products like TEMIX - energy over a period. Fit well with products into ISO markets with the exception of a resource offer. When I specify a load bid - energy over an hour at a particular location etc.

[15:16] Bill Cox: Nothing particurly new or unique about those TEMIX products. Really just drawing on the way most transactions are done, even in part in IRC markets. Or at least communicated.

[15:16] Bill Cox: Nothing says how the market works, and nothing in the TEMIX model that says how the IRC and IRC markets work.

[15:17] Bill Cox: If I want to restrict the set of products and how dewscripbed for the IRC markets or a tariff - can have a set of named products. IN those mcould say "not the full fleixbility of the emix model
and want to restrict in some way.

[15:17] Bill Cox: Don't see that as an "endorsement" of emix, IRC can step forward and say what it wants.

[15:17] Bill Cox: T: A couple of threads - TEMIX and what's in there would also apply to the OpenADR profile and may not be used in wholesale markets

[15:18] Bill Cox: B: This is EMIX meeting

[15:18] Bill Cox: T: Do some groups see value in standardizing and others not? One thing we've heard repeatedly from IRC that they didn't want their business practices in a standard where they might be mandated.

[15:18] Bill Cox: T: Others say they want what they're doing as concrete as they can be. Some argue in, some out, not sure how to cut that baby in half.

[15:19] Bill Cox: T: Not just stepping up but some people saw value in being standardized.

[15:20] Bill Cox: JP I guess ideally - you mentioned OpenADR in EI - would it be more appropriate; TEMIX in the standard shows how to break into a profile. TEMIX is an example, breaking down into how it can be a profile.

[15:20] Bill Cox: B: Is the problem putting a name on it?

[15:21] Bill Cox: JP Think the problem is putting a name as a asparate subset.

[15:21] Bill Cox: T: Think that's a common pattern - common WS-Security standrads we use without considerable profiles baked into the standards.

[15:21] Bill Cox: ACTION JP update 486 for discussion


> TeMix addresses this use case
> -----------------------------
>
>                 Key: EMIX-486
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-486
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>         Environment: IRC
>            Reporter: Toby Considine
>            Assignee: William Cox
>
> Using TeMix as the sole communicator of market clearing price for energy.  The IRC has repeatedly expressed concern with TeMix being the underlying base for the information exchanges, rather than  adopting currently shared practices of the IRC markets, the only developed wholesale energy markets, and expanding on common practices to integrate new forms of market participants.

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