-
Type: Improvement
-
Status: Closed
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: wd23
-
Fix Version/s: None
-
Component/s: schema
-
Labels:None
-
Resolution:
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.