[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (EMIX-112) Detailed Corrections andProposed Improvements to WD 13 Specification
Detailed Corrections and Proposed Improvements to WD 13 Specification
---------------------------------------------------------------------
Key: EMIX-112
URL: http://tools.oasis-open.org/issues/browse/EMIX-112
Project: OASIS Energy Market Information Exchange (eMIX) TC
Issue Type: Improvement
Affects Versions: wd13
Reporter: Edward Cazalet
Assignee: William Cox
Fix For: wd14
WD 13 Comments by Cazalet
323: "/" should be ")"
330: Replace : After production, though, the commodity is commingled with other energy products with which 330 it is fully fungible.
With : After production, though, the commodity is commingled with production from other sources with which it is fully fungible.
333: Product should be lowercase?
364: Change 2.4 Time and Schedules as part of EMIX
to 2.4 EMIX Time and Schedules
376 Suggest inserting a new section that brings forward and expands sections 7.7.1 as follows:
2.5 Tenders and Transactions for Power Products and Resource Capabilities
The focus of EMIX is on price and product communication in support of commercial transactions. The messaging and interaction patterns for commercial transactions are out of scope for EMIX but worth a brief discussion here to provide context.
Transactions in most markets begin with Tenders (Offers to buy or sell) a Product by a Party to another Party. Once an agreement among Parties is reached a Transaction (contract) is executed. Then the parties to the Transaction must perform on the Transaction by arranging for supply, transport, consumption, settlement and payment. At every stage in this process clear communication of the Product and Price is essential.
In many electric grid markets an operator controls generation and transport and may enter into load curtailment contracts with customers. Control requires some knowledge of the capabilities of resources under control. Such capabilities may be augmented by economic bids. In EMIX we represent the resource characteristic and bids as an EMIX product that can be tendered to operators. The operators then determine transactions for resource outputs which can be represented using EMIX power products and prices.
Tenders can be expressed using either the semantics of Power Products or the semantics of Resource Capabilities. Transactions are described by Power Products. Transacting parties can determine the fitness of a resource to meet their needs based on the capabilities. Reserves are options to supply product within a given response rate at an agreed upon price.
430 to 432 move and insert paragraph after line 397.
433 to 448 - This material is redundant to the new Overview before this These sections should be deleted.
449 delete 3.2 Top-Level Information Items
449 Promote 3.2.1 The Intrinsic Elements to 3.2 Intrinsic Elements
delete 3.2.2 Container for Extrinsic Elements
and move 455 to Extrinsic Elements
466 delete section head 3.3.1 Warrant Information Examples -
Most of the material in 3.3.3 is repeated in section 11 where it likely belongs.
487 Table 4-1
Why are the product elements duration, price and quantity identified here when any product element could be set as a default in a gluon and overridden in an interval. It would be better to have a generic element here that could be any product description element including duration, price and quantity.
And in the emix schema ( line 106 in the emix.xsd ) only the gluon and the schedule are present.502:
<!-- 2.3 Product -->
<xs:complexType name="type-product">
<xs:annotation>
<xs:documentation>Product applies the productDescription to a sequence by means of a Gluon. If the Sequence is un-scheduled, the interval that determines the schedule for the sequence is indicated by the Gluon relation. See WS-Calendar for details.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="gluon" type="emix:gluon" minOccurs="0" maxOccurs="1"/>
<xs:element name="schedule" type="emix:sequence"/>
</xs:sequence>
</xs:complexType>
Suggest changing
<xs:complexType name="type-product">
<xs:complexType name="type-genericproduct">
for consistency with specification
508 Explanations do not line up with Figure.
We should not refer to generation but instead to power product in the example.
514 "w" in work is wrong font.
534 "Power product" should be" a Power Product"
535 insert a before Power Product and change Power Products to a Power Product
555: Table 6-1 - Constant Power Quantity What does it mean that the Quantity is defined in the Product Description? Where?
556 Table 6-1 Price Note: should be Unit Price "From EMIX" not defined.
694: Table 10-1
Transport Access Fee Note:
Fixed Charge (not dependent on quantity) to access transport system
should read
Need Transport Access fee unit (however all of this are in energy price units $/MWh so not sure we need them here.
Fixed Charge (not dependent on congestion) to access transport system
Transport Congestion Fee
Need Transport Access fee unit
Change Note to: congestion fee per unit of energy for energy flowing from receipt to delivery point. Can be a positive or negative price.
Transport Loss Factor, Float or Ratio ? Ratio of Power delivered to Power received.
Conversion loss factor - remove - I don't see how it applies unless it is DC terminal conversion losses not included in Transport Losses on a DC transmission line
556 Table 6-1 Service Location - Are you saying one could use a set of different intervals all with the same start time and duration, for example but each with a different service location.
556 Table 6-1; What does Performance mean? yet another use of the word performance. Vague because we are requiring a deep understanding of WS-Calendar.
570: note on 3rd line
Change : Customer is always charged for the minimum power and prices apply only up to a maximum power.
to
Customer must draw energy at least the minimum rate (power) and no more than the maximum rate during any measurement interval.
570 suggest removing the last three rows of Table 6.2
582 Table 6-6 - why do I need "node" here when Table 5-7 should have all of the location attributes
586 Why do we need a reference to Power Attributes in Table 6-7?
573 The term Power Rate should be avoided in this table and the full document. _ use just the definition of Power as a rate of delivery of energy.
633: Tenders, Transactions, and Options
Eliminate this section and leave the last paragraph of the section to follow the previous 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]