-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: csprd02 Public Review Draft
-
Fix Version/s: None
-
Component/s: spec
-
Labels:None
-
Resolution:
Subject: [emix] Comments on emix-v1.0-csprd02
From: "Dinges, Sharon" <sdinges@trane.com>
Date: Fri, 20 May 2011 14:42:29 +0000
To: "emix@lists.oasis-open.org" <emix@lists.oasis-open.org>
Great job to the primary authors - this is a great specification.
Here are my suggested changes:
Editor: add ~212 to dinges #s to get .odt numbers (may be diff #s when converted back)
259: Suggest changing to: "... by one Party to another Party"
Ed.
(s/b 471 in .odt, but is instead 440)
Done.
372: Suggest changing to: "... can be offered..."
Ed.
(574)
Done.
453: change "therefor" to "therefore"
Ed.
(665)
Done
454: change "has is" to "is" - for Minimum Recovery Duration and
Minimum Duration Between Invocations
Ed.
(666)
Done
454: (throughout document, actually) - adhere to consistent use of the period (.)
punctuation mark in tables, bullets, etc.
Ed.
(666)
-
-
- tbd at last pass
-
454: Why do Availability Schedule and Unavailability Schedule have identical definitions
- I would expect a slight difference
Ed.
(666)
Done.
Also see Jira issue 389 on definition of 'Schedule'.
473: suggest changing to: "... meter, an aggregation..."
Ed.
(687)
Done
479: suggest changing to: "... Purchase Order, on each..."
Ed.
(695)
Done.
489: existing wording not clear: "... not include quantity or precise."
Ed.
(707)
Done.
492: suggest changing from "This illustration" to "Figure 6-1" (since it is on the following page)
Ed.
(710)
Done.
507, 512: Change comma to a period
Ed.
(728, 734)
Done
510: add space to: "Table 4-1describe"
Ed.
(731)
Done.
513: Product Description: change "nor" to "not"
Ed.
(735)
Done.
515: suggest changing to: "... Sequence as a temporally..."
Ed.
(737)
Done.
519: existing wording not clear for Relation: "... one Interval to other..."
Ed.
(Table 7, line 742, Relation)
***
Need better definition. Add to list.
Cannot find 'relation' in schema.
Cannot find 'unit price' in schema.
Table needs some context. Doesn't make sense as it is.
531: change to: "Electrical energy and must..."
Ed.
(755)
Done.
537: existing wording not clear: "... could be brought market..."
Ed.
(763)
Done.
548: add colon after "that"
Ed.
(774)
Done.
549a: revise to be consistent with 762: "energy = power * duration"
Ed.
(775)
Done.
551: change "with in" to "within"
Ed.
(778)
Done.
575: Price Relative: change wording to: "... and of a..."
Ed.
(807)
Done.
590: Price - change from "... choice one of a Price..." to "... choice of either Price..."
Ed.
(825)
Done.
590, 599: Energy Units - revise description to read: "Denominates the units to which the Price applies."
Ed.
(825, 835)
Done.
599: Block Energy Price: revise wording to read: "... Quantify and the price for the next..."
Ed.
(835)
Done.
603 616: (and throughout), standardizes on "TeMIX" rather than "TEMIX"
Ed.
Done.
603: remove extra period at end of sentence
Ed.
(840)
Done.
608: change "intervals" to "interval"
Ed.
(845)
Done.
612, 790: (throughout) Energy Item equation
- why is this "Time" rather than duration, as in 549?
Make consistent throughout, if appropriate
Ed.
(849 - Energy Item)
Removed these equations as they are superflous.
Done.
623, 624: Revise to read:
"One charge can be applied to each of the products as above, so is defined here.
That charge is the Demand Charge, as defined below:"
Ed.
(861,862)
Done.
625: Measurement Interval: change to "Granularity of Power Use..."
Ed.
(863 - Measurement)
Done.
625: What is the right term: "floor", Demand Charge Floor", "Demand Floor"
- it is used in three different ways in this table... make consistent
Ed.
(863 - table 9)
Done as per comment.
633: Full Requirements Power: "Demand Charges" is an incomplete thought...
Ed.
(872 - Table 9)
Deleted.
Done.
633: Full Requirements Power Maximum and Minimum:
existing wording not clear: "... draw energy at least the minimum rate"
Ed.
(872 - Table 9)
Done.
633: Hourly Day Ahead Pricing: change to "Full Requirements Power"
Ed.
(872 - Table 9)
Done.
634: add period to end of sentence
Ed.
(872 - Table 9)
Done.
676, 683: (and elsewhere in document):
standardize on the use of either "min" or "minutes"
but, do not mix the units
Ed.
(921, 922)
Done.
678: change to: "... as above, to capabilities..."
Ed.
(923)
Done.
683: change from "100MW" to "100 MW"
Ed.
(929)
Done.
703: Constraints - change from "below" to "in Table 10-2"
Ed.
(953 - constraints)
Done.
710: Staging Ramp and Recovery Ramp: change to "An array of Power..."
Ed.
(961)
Done.
736: change to something like: "... many markets, they Offer Curves..."
Ed.
(993)
Done.
787: clean up the "Error!" reference
Ed.
(1052 - 1053)
-
-
- Document creation/processing error needs fixing.
Is highlighted in RED.
- Document creation/processing error needs fixing.
-
792: Strike Price: - where is "Option Writer" defined?
Ed.
(1057 - table 11)
***
Also mentioned in Option Holder element definition.
Either need to stop referring to 'Option Writer'
(find other term to refer to other side) or define it.
If it's not needed as an element in the schema, then delete?
Otherwise add to schema.
792: Granularity - change from "at10:00" to "at 10:00"
Ed.
(1057 - table 11)
Done.
820: Power Frequency - change from "Powr Quality" to "Power Quality"
Ed.
(1089 Table 13)
Done.
834: Transport Loss Factor
- modify parantheses to match Conversion Loss Factor:
"Loss Factor * purchase amount = delivered amount).
Also, throughout the document,
be consistent in what is on the left side of each equation,
and what is on the right side - both methods are used.
Ed.
(1106 - Table 14)
Removed such equations.
Done.
867: change "Conformance" to "conformance",
unless there is a deliberate reason for the capitalization
Ed.
(1146)
Done.
875: add period to end of sentence
Ed.
(1156)
Done.
Regards,
- Sharon
Sharon E. Dinges, CEM
System Applications Engineer; Smart Grid Standards Initiatives Lead l Desk: 651.407.4244 l mobile:763.954.0469
sdinges@trane.com l Trane - Ingersoll Rand Climate Solutions l 4833 White Bear Pkwy, St. Paul, MN 55110
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.