[OASIS Issue Tracker] Commented: (EMIX-425) MIscellaneous EditorialChanges

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Toby Considine commented on EMIX-425:
-------------------------------------

736: The TeMIX sections should be after the Transport Product section as TeMIX uses the Transport Product. 
739 Change 

TeMIX products use transactive interactions to acquire blocks of Power. TeMIX emphasizes simple interactions and requires minimal knowledge of one's trading partner. All TeMIX Products are subscriptions for Power over a single Delivery Interval. Subscriptions impose an obligation on the buyer to purchase and the seller to deliver a TeMIX Power Product. This simplicity reduces the number of products and interactions. 

There are only four types of TeMIX Products: 
To: 

TeMIX is a subset or profile of the EMIX Products. This section brings together all of the TeMIX products and definitions in one place. 

TeMIX Products are blocks of Power with a constant rate of delivery (subscription) over a single interval. 

There are four types of TeMIX Products: 
755: Change 
A TeMIX Delivery Interval is specified by a Duration and Start Time. When a TeMIX Product is specified for a set of Delivery Intervals, then elements that do not vary by Delivery Interval may be specified in a Gluon. However, each TeMIX Delivery Interval is transacted independently of the others in the set. 
A TeMIX Power Product defines a subscription for Power over a Delivery Interval. The subscribed power of TeMIX Power Product is constant over all measured (metered) Intervals within a TeMIX Delivery Interval. 
To: 
A TeMIX Delivery Interval is specified by a Duration and Start Time. When a TeMIX Product is specified for a set of Delivery Intervals, then elements that do not vary by Delivery Interval may be specified in a Gluon or the Standard Terms. 

Each TeMIX Delivery Interval is transacted independently of the others. 

The rate of delivery of a TeMIX Power Product is constant over all measured (metered) Intervals within a TeMIX Delivery Interval. 

Done. Will post reformed chapter to Chairs to see if I have met their requirements...


> MIscellaneous Editorial Changes
> -------------------------------
>
>                 Key: EMIX-425
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-425
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>    Affects Versions: wd28
>            Reporter: Edward Cazalet 
>            Assignee: William Cox
>             Fix For: wd29
>
>
> 163: remove "product"  -wait to use the term product until we defined it.
> 177:  "energy wholesale and financial markets" to
> "forward and futures wholesale energy markets and financial markets"
> 178 : The Energy Interoperation TC defines a TeMIX profile using a subset of the Energy Interoperation services.  The information model for the TeMIX services is a subset of EMIX information model.
> 249:
> (ISO refers to Independent System Operators providing for pre- existing tight power pools provide non-discriminatory access to transmission. RTO refers to Regional Transmission Organizations that administer the transmission grid on a regional basis.)
> (ISO refers to Independent System Operators provide non-discriminatory access to transmission, operate spot markets and maintain grid reliability. RTO refers to Regional Transmission Organizations that perform the ISO functions on a regional basis.)
> 267: Transport
> Need to allow for Transport as a price for transport between two points in addition to transport represented as charges.  Suggest rewrite as follows"
> "Product transport from a point of injection to a grid to a point of takeout to a grid is also described by the EMIX information model.  Produce transport can be characterized by the quantity transported and the price or by the transport quantity and the costs.
> In some cases the price of product may also cover Transport services."
> 314: Product Description needs updating with respect to Standard Terms so that elements of a Product Description may reside in Standard Terms or in Components of a Schedule.
> 336: There are many wholesale grid
> 390: Transactive State - delete Transport Commitment as it is not used anywhere in EMIX.
> 443: Party Type should be Party Role
> 483: Performance oriented terms should be in Resource.xsd
> 485: Section 5.2 Schedule Oriented Terms
> This section conflates when a product is available with when a party may be able to respond to a service message and when a Resource may be available or unavailable.
> 485 Schedule related terms indicate schedules that define a potential product offering. A product may only be available on weekends, or may not be able to respond outside of normal office hours.
> Should be revised to 
> "Schedule related terms indicate schedules that when a product may be available or when and interaction may occur. A product may only be available on weekends, or a party may not be able to respond outside of normal office hours."
> Market Requirements should be in Resources.xsd as they apply only to markets in which resources can be tendered.  
> However Market Granularity should be in the Standard Terms Set (Table 16-2);
> 442: and 452 Change Party Type to Party Role
> 537 should refer to Temporal Granularity which should be in a different section than vAvailability and Availability.
> 560: Figure 6-1.
> Product Description should be at the top
> Put Price where Offer is and take is out of the Gluon (Price)
> 612:  Title should be "Defined Energy Terms"
> 691: why are transport charges here when they are also expressed in a later section.  Eliminate transport charges here. 
> 736: The TeMIX sections should be after the Transport Product section as TeMIX uses the Transport Product.
> 739 Change
> TeMIX products use transactive interactions to acquire blocks of Power. TeMIX emphasizes simple interactions and requires minimal knowledge of one's trading partner. All TeMIX Products are subscriptions for Power over a single Delivery Interval. Subscriptions impose an obligation on the buyer to purchase and the seller to deliver a TeMIX Power Product. This simplicity reduces the number of products and interactions. 
> There are only four types of TeMIX Products:
> To: 
> TeMIX is a subset or profile of the EMIX Products.  This section brings together all of the TeMIX products and definitions in one place.
> TeMIX Products are blocks of Power with a constant rate of delivery (subscription) over a single interval. 
> There are four types of TeMIX Products:
> 755: Change
> A TeMIX Delivery Interval is specified by a Duration and Start Time. When a TeMIX Product is specified for a set of Delivery Intervals, then elements that do not vary by Delivery Interval may be specified in a Gluon. However, each TeMIX Delivery Interval is transacted independently of the others in the set. 
> A TeMIX Power Product defines a subscription for Power over a Delivery Interval. The subscribed power of TeMIX Power Product is constant over all measured (metered) Intervals within a TeMIX Delivery Interval.
> To:
> A TeMIX Delivery Interval is specified by a Duration and Start Time. When a TeMIX Product is specified for a set of Delivery Intervals, then elements that do not vary by Delivery Interval may be specified in a Gluon or the Standard Terms.  
> Each TeMIX Delivery Interval is transacted independently of the others. 
> The rate of delivery of a TeMIX Power Product is constant over all measured (metered) Intervals within a TeMIX Delivery Interval.
> 775: 
> 803: Transport Product should be defined as Point of Receipt, Point of Delivery, Price, Quantity (MW/kW) and Interval (start time and duration).  Transport costs are as defined.  If one is using a transport price, transport costs are irrelevant.  I suggest both the price and cost models be presented as alternatives. 
> 979  Move Standard Terms much closer to the front of the document close to first schedule and gluon descriptions.
> 997: Rename Granularity as Temporal Granularity

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