Issue Navigator - OASIS Technical Committees Issue Tracker

EMIX-544
In section 13.6.1, should a "serial number" be required for PowerRampSegmentType as it is for OfferSegmentType?
EMIX-528
Price Optionality
EMIX-527
supportForPrice Warrant
EMIX-520
Table E-1: mapping NAESB PAP03 requirements
EMIX-516
Source and Content Warrants
EMIX-515
Typo in emix-warrants:ControllabilityWarrantType
EMIX-488
Collector for Aaron Snyder comment 20110817
EMIX-479
CLONE -Ominibus Comments for Marty Burns - 469
EMIX-475
Ed Cazalet comment on WD31 Section 13 to End.
EMIX-474
Comments on WD 31 Specifications by Ed Cazalet
EMIX-471
CLONE -Editorial notes for WD29
EMIX-467
Chapter 14, Ancillary Services needs some editorial work
EMIX-466
controlabilityWarrantWarrant
EMIX-465
Editorial notes for WD29
EMIX-464
Line 117 - "WS-Calendar" - Please see the IRC submitted issues on WS-Calendar the use of generic catch all entities and the inheritance model
EMIX-463
Line 803 - "Reserves as Options" - 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.
EMIX-462
Line 438 - Where is product descritpion in this model?
EMIX-461
Line 577 - This is inconsistent with the implied definition of product description used in the doc. This model has measurements, location and price. This implies a transaction and not a definition of what is being sold.
EMIX-460
All - Starting with an information model (UML) is much clearer than the XSDs that are not good at showing relationships.
EMIX-459
Line 385 - "EMIX product..."
EMIX-458
Line 347 - prefer "does not have the same value". The impression that the energy can somehow do something different at a different time is misleading.
EMIX-457
Line 145 - same product, not the same value. See IRC submitted information model.
EMIX-455
Line 662 - EMIX should not make judgment calls on the comparability of energy sources, but the information exchanges required for such resources.
EMIX-454
Line 599 - Attributes: For Residential - definition should be provided not example - Attributes of power relating to frequency, voltage, etc
EMIX-453
Line 594 - "Charges MAY" - Unless MAY is an acronym throughout the document it should be replaced with may.
EMIX-452
Line 575 - Definition of Price
EMIX-451
Line 513 - "this is nor required" - not sure what is meant
EMIX-450
Line 502 - "The intervals can be as short as minutes..." - This sentence makes little sense.
EMIX-449
Line 489 - Precise what? The sentence stops.
EMIX-448
Lines 548-558 - Confusing section
EMIX-447
Line 401 - The ISO/RTO Council does not approve or accept the TeMIX principles and foundational basis. It was not in the previous version.
EMIX-446
Line 417 - Transactive relates to transactions, why is it in Product and Price. The transaction elements should be defined in the Energy Interoperation not in price and product.
EMIX-445
Line 353 - change "between grid systems..." to "between grid, business, and personal systems"
EMIX-444
Line 347 - 5kW is 5kW at 02:00 or 23:00. Stating it is a different product is not accurate. It may have different value, but it is the same thing.
EMIX-443
Line 280 - This paragraph discusses verification, while the subsequent paragraph states it's out of scope
EMIX-442
Line 185 - Speifies that extrensic properties must be able to clear in the market. Emix should focus on information exchange not defining what markets clear during their operation.
EMIX-441
Line 145 - It was noted in the last round of comments that the TC is misconstruing energy as a product.
EMIX-439
wd28: Clarify purpose/scope of Demand Charge structure.
EMIX-438
Line 786 Table 10.1 has two rows defining "Price".
EMIX-436
wd28: line 695 table 9-4 'consumption units'
EMIX-435
EMIX Core Abstract Types 'Schedule' and 'Component' definitions review
EMIX-434
Chapter 8 and 9 Issues
EMIX-433
Chapter 8 and 9 Editorial
EMIX-432
Table 7-2
EMIX-431
Table 7-1
EMIX-430
Chapter 7 Editorial
EMIX-429
Chapter 3 Table 3-7
EMIX-428
Chapter 3 Table 3-6
EMIX-427
Chapter 3 Issues
EMIX-426
Chapter 3 Editorial
EMIX-422
324: Price Base should be Price Modifier Base and should be optional.
EMIX-421
Chapter 2 Editorial
EMIX-420
Chapter 1 Issue
EMIX-419
Chapter 1 Editorial
EMIX-418
Update information on Transactive States in Section 11
EMIX-417
Line 496 - The term "gluon" is never defined.
EMIX-416
Line 489 - There is a typo. Should the word "price" be used instead of "precise"?
EMIX-415
Line 453 - There is a typo. "therefore"
EMIX-414
Line 390 - When you say that CEFACT defines the currency code, are you expecting the three character alpha code to be used or the numeric code to be used?
EMIX-411
EMIX Exit Criteria
EMIX-410
References to NAESB M&V Business Practices CLONE -Minor editorial issues
EMIX-397
Unnecessary clone for incomplete issues
EMIX-396
Clarify Option Writer
EMIX-395
Expand Defintions
EMIX-394
Review use of Periods throughout document
EMIX-393
Omnibus for Sharon Dinges issues from PR
EMIX-391
UID
EMIX-389
Schedule and Business Schedule
EMIX-384
wd23 csd02: Abstract -- reduce ambiguity / improve consistency
EMIX-381
Minor editorial issues
EMIX-379
need EMIX naming/design rules
EMIX-377
Consolidation and simplification of Transactive products
EMIX-376
Table 7-2 EMIX Base Product shows price & quantiy elements as well as duration however price and quantity elements are in the product descriptions some times with different names.
EMIX-375
Section 14 Spelling, Grammatical, Textural
EMIX-373
Section 14 Tables and Figures
EMIX-372
Section 13 Tables and Figures
EMIX-370
Section 12 Tables and Figures
EMIX-369
Section 11 Spelling, Grammatical, Textual
EMIX-368
Section 11 Tables and Figures
EMIX-367
Section 10 Tables and Figures Issues
EMIX-366
Section 10 Spelling, Grammatical, Textual
EMIX-365
Footnotes should neither make nor point to normative/non-normative references
EMIX-357
Section 4 Tables and Figures Issues
EMIX-355
Collector for Tables and Figures Issues 20110404
EMIX-354
EMIX does not specify messages but an information model
EMIX-353
302 Guide to Schema Structure
EMIX-350
Identify PDF version of the specification as authoritative
EMIX-349
Sections 1.5 and 3: Add text addressing why schema versioning is not needed in addition to namespace versioning/maintenance
EMIX-348
wd22-with-changes.doc: table numbering off
EMIX-347
Editorial issues, Section 1, wd22-with-change.doc
EMIX-345
146 Update Security section
EMIX-344
Collector for References Issues 20110404
EMIX-343
Acronyms -- need approach/rule for handling acronyms
EMIX-341
122 "postfixed" spelling error
EMIX-340
45 and 76 Correct references and use (normative and non-normative)
EMIX-339
Various minor editorial issues
EMIX-338
Line 16 Add reference for XML Schema
EMIX-337
45 Normative References need to be consistent with the document
EMIX-336
Page 1 Abstract needs to be in synchronization anticipated use
EMIX-335
wd22-with-changes.doc: Issues with Normative References (Sections 1.3) and Non-Normative References (Section 1.4)
EMIX-334
Add Glossary/Vocabulary section in spec for terms and acronyms/abbreviations
EMIX-333
Add language of Item and Itembase throughout specification
EMIX-327
Updated Appendix E (from wd21)
EMIX-326
Need simple temix transport XML example.
EMIX-319
wd19 .doc Use of the term 'optional'.
EMIX-318
wd19 .doc: clearly distinguish (and separate where possible) normative from non-normative information
EMIX-317
Namespace section issues
EMIX-316
wd 19 .doc: Clarification of 'transactive' and 'transactional'.
EMIX-315
WD 19 .doc Line 171: reword to clarify scope w.r.t. EI
EMIX-312
rationalize table headers, create definitions.
EMIX-309
Align table columns (and content type) to be consistent and create complete formal definitions.
EMIX-308
Move section 1.8 on ws-calendar to sections 2.2, 2.4, and Appendix
EMIX-298
Transactive State is not adequately explained in the wd 17 document. I suggest some minor wording changes and potential editing.
EMIX-291
CLONE -Line 386 - Real Power and Reactive Power are more accurate names to distinguish MW and MVAR
EMIX-289
Create Inheritance Rules for each Product and Resource
EMIX-286
Section 6 needs definitions to include Power Interval, Ramped Power Interval, Block Power, etc
EMIX-285
Line 457 QMax definition is not clear
EMIX-283
Line 543 - Add Aaron F. Snyder, EnerNex
EMIX-282
UML and EA on final work
EMIX-273
Line 482 - maintain frequency not accumulated frequency error
EMIX-272
Line 386 - Real Power and Reactive Power are more accurate names to distinguish MW and MVAR
EMIX-271
Line 338 - Should be "Delivery incurs specific costs that vary over time" OR "Product transport costs"
EMIX-270
All - Numbering of sections is inconsistent. E.g. section 8 has child sections 8.1.1.1 and 8.1.1.2, but no 8.1 or 8.1.1.
EMIX-269
Line 586 - "the product can offer" - should be resource
EMIX-268
Line 493 - "normally kilowatt-hours" - KW is Kilowatt not kilowatt hours.
EMIX-267
Line 475 - "perfoamcne" - performance
EMIX-266
Line 371 & 376 - "Minimum Power" - If buyer consumes than this rate...... more than or less than this rate??? Needs correction.
EMIX-265
Line 357 - "As define below" - as defined below
EMIX-264
Line 341 - "amount contracted for" - remove for
EMIX-263
Line 338 - transport should be lower case
EMIX-262
Line 287 - "communication is is" - Duplicate is and the sentence ends in a preposition... suggest "The format of this ID varies by the communication intentions."
EMIX-261
Line 214 - "the communicate" - that communicate
EMIX-260
Line 203 - "Loss change" - loss charge
EMIX-259
Line 202 - "amount contracted for" - remove for
EMIX-258
Line 199 - Transport should be lower case
EMIX-257
Line 170 - "may have to be" - may or may not be able to be stored...
EMIX-256
Line 127 - period not slash.
EMIX-255
Line 116 - "to making buying" - to make buying
EMIX-254
Line 111 - "Lack of standardized of messages" - delete of
EMIX-253
All - The Charter states "Models and requirements for cybersecurity and privacy will be addressed in the TC's work". How is cybersecurity addressed?
EMIX-252
All - The Charter states that the TC will define information models, where are they?
EMIX-251
All - Please use another phrase than gluon. Gluon is being used for product, for extension of elements, etc.... Either use the proper naming or use another "standard" naming.
EMIX-250
All - EMIX is building interactions with WSCalendar. Issues with WSCalendar have not been completely addressed, thus further issues could present themselves with EMIX when the WSCalendar is completed. Further complications may occur with Energy Interop.
EMIX-249
All - Under currency, shadow prices are not relevant. It is more of a price type enumeration rather than a currency
EMIX-248
All - If we are reading this document and understanding it correctly it also appears as if there is an attempt to combine different industry segments and functions together.
EMIX-247
All - It appears that the work undertaken here has attempted to come up with their own taxonomy rather than utilizing utility industry accustomed and seasoned taxonomy.
EMIX-246
Line 584-598 - Text on plans for A/S not relevant
EMIX-245
Line 607 - These are not requirements, they are product names, see CIM.
EMIX-244
Line 542 - "What are the rules?" - Consider removing statement or answering the question.
EMIX-243
Line 512 - Note field not completed.
EMIX-242
Line 496 - If this is the description of an offer/bid/award then there are several fields missing. If this is a description of the product then time, availabliity are not required but other fields are. See CIM and IRC information models.
EMIX-241
Line 477 - The use of "any" in this circumstance could mean you can set the startup cost for another resource. Since it does not clarify the definition, it should be removed.
EMIX-240
Line 475 - Offers may not contain any description of the resource except its id.
EMIX-239
Line 464 - Mrid is not defined in the document, and there is no definition in the note field. Should be defined.
EMIX-238
Line 464 - Maxima is a confusing term from physics regarding waveforms. This term is irrelevant to the utility industry and should be changed to a word more clearly understood by in the utility vernacular e.g. order.
EMIX-237
Line 464 - should be lower case descending
EMIX-236
Line 463 - There are many more resource attributes that the system operators would be interested in (See CIM and IRC information models). However, are any of these applicable to a price and product specification?
EMIX-235
Line 399 - Resource characteristics are submitted at time of registration in wholesale markets. Some characteristics may be overriden in economic bids
EMIX-234
Line 354 - Power Units - Did not see where it was defined.
EMIX-233
Line 337 - Transport costs also include transmission costs and distribution costs. These costs do not typically vary unlike the congestion charge which is an adder to the price, and losses are typically purchased by the buyer.
EMIX-232
Line 337 - The description is for a type of price (LMP) that is applied to the Energy product. It is not a transport product.
EMIX-231
Line 333 - Resources can be loads, they do not have to be under curtailment contracts.
EMIX-230
Line 329 - "also known as" - Reference? Only in this specification?
EMIX-229
Line 303 - This seems to say that everything is a Gluon rather than using the WS-Calendar standard to for just schedule. An information model (class diagram) would really help.
EMIX-228
Line 297 - Is this a product like Energy or SPIN or something else that includes other info.
EMIX-227
Line 297 - can be inherited from the gluon set - So this is part of the WS-Calendar standard and not EMIX?
EMIX-226
Line 295 - Please see the IRC submitted issues on WS-Calendar the use of generic catch all entities and the inheritance model
EMIX-225
Line 295 - StartingDateTime is marked as "Optional" but if it is required when scheduling a sequence and sequence is a mandatory field, this element could not be optional.
EMIX-224
Line 295 - Should state which are mandatory and which are optional, or only state the optional fields. Very confusing when some say mandatory and others are blank.
EMIX-223
Line 287 - It is not clear if this is the duration between notification and performance(e.g. lead time) or the delivery duration. Recommend calling it Option Exercise Lead Time to clearly stat what it is that is being conveyed.
EMIX-222
Line 287 - State the section in which it is defined.
EMIX-221
Line 283 - All of this additional info would be unnecessary if reserves were treated as products. See CIM and IRC work.
EMIX-220
Line 283 - 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.
EMIX-219
Line 283 - For $/MW prices the sum of all intervals as no meaning.
EMIX-218
Line 259 - Note fields not completed.
EMIX-217
Line 259 - Wholesale markets need to identify the resource in addition to the "parties";
EMIX-216
Line 259 - What else can it be; we need to express prices per unit at a rate of delivery (for bids/offers) and a price per unit (for LMP or clearing prices) See CIM and IRC submitted work.
EMIX-215
Line 259 - Location is an intrinsic property. How is it specified?
EMIX-214
Line 259 - Why the mention of shadow prices here? It is not a currency. However it may be useful to have another field for price type enumerated to shadow price, LMP, Clearing etc.
EMIX-213
Line 248 - Not clear, is the 15 minute lead time part of the product? Then disagree, these are resource properties see CIM and IRC submitted work.
EMIX-212
Line 241 - Uri is not defined.
EMIX-211
Line 230 - prefer "does not have the same value". The impression that the energy can somehow do something different at a different time is misleading.
EMIX-210
Line 208 - First paragraph adds no value
EMIX-209
Line 199 - Should be "Delivery incurs specific costs that vary over time" OR "Product transport costs"
EMIX-208
Line 175 - Must maintain an auditable trail such that it cannot be deleted from the system completely.
EMIX-207
Line 169 - What kind of product? energy?
EMIX-206
Line 143 - It states extrinsic properties and then discusses intrinsic energy. It should be either properties or energy.
EMIX-205
Line 120 - disagree, same product, not the same value.
EMIX-204
All - Grammar issues throughout the entire document.
EMIX-203
All - Transport costs also include transmission costs and distribution costs. These costs do not typically vary unlike the congestion charge which is an adder to the price, and losses are typically purchased by the buyer.
EMIX-202
All - We did not see the extensibility and subsetting in the spec for all the information exchange and would prefer to categorize/standardize the information interactions based on functional roles of actors in each market.
EMIX-201
Concerned with the proposal to reliance of WS calendar to the formulations being developed. While there may be opportunities to leverage the use of WS calendar to some of the areas being looked at it may create considerable challenges in the others.
EMIX-200
All - Also with these kind of over generalized standards the interoperability benefits sought will be completely lost. Moreover with too much padding the payloads and verification schema implemented will become rather costly.
EMIX-199
All - The identification of a field as optional should list this optionality in a standard location. Sometimes it is listed at the front of the field and sometimes at the end of the field. See table 3-2 line 267 for examples.
EMIX-198
All - Specification is used as both a definition and/or to define the data type. This is confusing and should be resolved for readability. See line 259 Party, Counterparty... it is defining data type and defining the element .
EMIX-197
Line 386 & 390 - This is a type and usage table, rather than specifically define the name of each element it should refer to a "type" table and the usage since this value may change.
EMIX-196
Line 469 - How does this treat multiple ramp rates? If there would be multiple entries such as one resource with four sets of table 7-5, this should be stated for clarity.
EMIX-195
Line 295 - reltions ....relations???
EMIX-194
Line 287 - If Emix Options is a variation of the Intrinsic Elements then Party is either the "Buyer" or "Seller". Why introducing "Promisor" or "Promisee". Are we assuming they are not the buyers and sellers?
EMIX-193
Line 259 - UID - Note - Is it anticipated that this element varies? Is it unique ? Needs description.

Refresh results

Export - CSV (All fields)

Export - CSV (Current fields)