OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (EMIX-366) Section 10 Spelling,Grammatical, Textual



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

Edward Cazalet  commented on EMIX-366:
--------------------------------------

The comment that resources have many applications brings up the issue of the scope of EMIX and EI with respect to Resources.

The charters for both PAP 03 and emix are focused on price and product communication.  

PAP 03 does not use the word Resource in its requirements.

The EMIX Charter uses the word Resource twice:
1:  Energy Interoperation will carry signals related to Distributed Energy Resources as well. 
2.  In the evolving transactive power grid (the "Smart Grid") these communications will involve energy consumers, producers, transmission and distribution systems, and must enable aggregation for both consumption and curtailment resources. Market makers, such as Independent System Operators (ISOs), Regional Transmission Operators (RTOs), utilities, and other evolving mechanisms need to deliver actionable information in consistent formats as the Smart Grid evolves

Neither of these citations would dictate the substantial focus of EMIX on Resources.

Resources can be highly complex and therefore communication of Resource Characteristics is Complex.

Resources are used by ISOs for centralized dispatch of generation and DR.   They take the view that an Offer is to be modeled as a Generic Resource often with many complex elements, constraints and charges based on complex FERC / ISO tariffs which is the antithesis of automated, simple price and product communication for the Smart Grid.  Whatever the merits of this approach it seems as if a major focus on Resources by EMIX should be carefully considered by the TC.

> Section 10 Spelling, Grammatical, Textual
> -----------------------------------------
>
>                 Key: EMIX-366
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-366
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>          Components: spec
>    Affects Versions: wd22
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Toby Considine
>            Priority: Minor
>
> Section 10 issues:
> Title should say "Energy Resources" rather than ...Offer Descriptions... - use is more broad.
> Early in section add "Resource describe the performance envelope--the maximum that a resource can deliver. The dynamic status of a resource can be managed with interaction protocols (see e.g. EiFeedback in [EnergyInteroperation]"
> NOTE it is an open issue whether to include "the needle" for a resource. I think that extending in the message and management system is the right approach, so I haven't raised the issue in EMIX.
> 628 Latin phrase should be in italics. Consider also for ex ante, etc
> 663 This section describes Base Resources (671, table caption). This should be "Resource Description".
> Also in section, these are not exactly "subclasses" but "extensions" - consider the terminology and make uniform through the document.
> 680 "Power Ramps are conformed based upon the type of appearance they make" - reword. Sentence is unclear as well as complex.
> 686 Remember, resources can be used without offering them to market. Offering to market is a benefit of using resources, limiting mismatch, but resources have applications beyond markets.  Applies to whole section.

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