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-484) Reserves as Options



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

Toby Considine commented on EMIX-484:
-------------------------------------

New Ancillary Services Type addresses this issue. Full descriptive terms for any market context can be assigned through standard terms. Mark Context Name (new field) aslo helps to address this issue.

	<!-- 2.1 Ancillary Services -->
		<xs:element name="ancillaryService" type="power:AncillaryServiceType"/>
	<xs:complexType name="AncillaryServiceType">
		<xs:annotation>
			<xs:documentation>Power related Ancillary Service</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="emix:EmixOptionType">
				<xs:sequence>
				<xs:element ref="power:ancillaryServiceName"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!-- 2.1.1 Ancillary Services Names-->
	<xs:element name="ancillaryServiceName" type="power:AncillaryServiceNameType"/>
	<xs:simpleType name="AncillaryServiceNameType">
		<xs:union memberTypes="emix:EmixExtensionType power:AncillaryServiceNameEnumeratedType "/>
	</xs:simpleType>
	<xs:simpleType name="AncillaryServiceNameEnumeratedType">
		<xs:annotation>
			<xs:documentation>Enumerated Ancillary Service Names</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:token">
			<xs:enumeration value="energy"/>
			<xs:enumeration value="regulationServiceUp"/>
			<xs:enumeration value="regulationServiceDown"/>
			<xs:enumeration value="regulationServiceUpDown"/>
			<xs:enumeration value="synchronizedReserve"/>
			<xs:enumeration value="nonSynchronizedReserve"/>
		</xs:restriction>
	</xs:simpleType>


> Reserves as Options
> -------------------
>
>                 Key: EMIX-484
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-484
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>    Affects Versions: CSD03/PR03
>         Environment: IRC
>            Reporter: Toby Considine
>            Assignee: William Cox
>
> The IRC does not see the benefit of re-phrasing widely understood concepts for reserves.  See the CIM and IRC submitted work where  reserves are products.  The requirements of the varied products and how they are expressed is known to the utility industry, energy markets, Demand Response providers, businesses and residential customers who participate in the markets.
> Enable Emix to address these concerns by adding additional fields to the information exchanges that would meet the needs of the wholesale market.

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