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-382) Are the PowerConstraints in the correct Schema?



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

Bruce Bartell commented on EMIX-382:
------------------------------------

Resource and Power schemas are both in the EMIX package. If the decision is to make Resource Constraints part of EI they would have to be in an EI schema.
In either case, the contstraints lists must be extensible without changing the base schemas.

> Are the Power Constraints in the correct Schema?
> ------------------------------------------------
>
>                 Key: EMIX-382
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-382
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: wd23
>            Reporter: Toby Considine
>            Assignee: William Cox
>
> We have three schemas in EMIX, EMIX, Power, and Resource. The constraint base type and the market independent constraints and requirements are part of EMIX. The EMIX schema has no power-specific attributes, including, in particular, no power-specific constraints. The constraints in the EMIX schema are all tied to duration, schedule, or economic requirements. These would all apply as well to steam or the natural gas, or for that matter, to Apple Orchards and to Seafood.
> We have four specific extensions to the Constraints class for use in power markets. These rely on the attributes defined in the power schema. These are:
> MinimumLoad	Constraint on Minimum Load that a Resource can maintain (powerQuantity)
> MaximumPower	Constraint on Maximum Power available from a resource (powerQuantity)
> MaximumEnergy	Constraint on Maximum Energy available from a resource (energyQuantity)
> MinimumLoadReduction	Minimum request for load reduction (e.g., MW rating of a discrete pump) (powerQuantity)
> These constraints are currently in Resource. Some recent comments have suggested that they should be in Power instead. Committee discussion and guidance would be welcome.
> Note: I have at several times considered whether Resource should be combined in toto into Power.xsd, but backed off when there were so many discussion of using resource.xsd inside ASHRAE SPC201.

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