Issue Navigator - OASIS Technical Committees Issue Tracker

ENERGYINTEROP-505
Suggested supplementary optional data classes with additional (optional) data types, detailed below
ENERGYINTEROP-507
Section 10 - There is confusion about how to get a VTN Market Context outside the framework of a specific event
ENERGYINTEROP-511
Registration cancellation parameters ill-defined
ENERGYINTEROP-504
Add Reading Type as optional element in ei:Market Context for use in eiQuote
ENERGYINTEROP-503
Incorrect verb use in service operation names
ENERGYINTEROP-500
Update response names from Send to Reply
ENERGYINTEROP-498
Baseline needs to have specific date/time intervals associated
ENERGYINTEROP-478
Line 1085 Figures 8-5, 8-6, 8-9 attribute names ext_ref_73, ref_element72, ext_ref_16
ENERGYINTEROP-469
Line 863 EiTender Operation Names are wrong in the table
ENERGYINTEROP-471
EiFeedback Section 8.1.5 line 1020 is too high a level heading
ENERGYINTEROP-466
Editorial Collector for wd24
ENERGYINTEROP-463
1284 add and dynamic tarrifs to end of sentance.
ENERGYINTEROP-458
792 : Section 5.6 Push and Pull Patterns needs to be generalized to all EI Operations
ENERGYINTEROP-473
Resources - Define Resouce and explore its use Collector
ENERGYINTEROP-456
878 - Table 9 offer, offoror and offeree should be tender, tenderor and tenderee.
ENERGYINTEROP-460
834 Need a Register Account Service?
ENERGYINTEROP-472
Re-factoring and Normalization Collector
ENERGYINTEROP-240
Section 6 uses "contract" while sections 5 and 7 use "agreement"; they should be consistent and use "contract"
ENERGYINTEROP-245
line 681: What distinction is implied by the term partyEndPoint vs. Party URI?
ENERGYINTEROP-234
Figures 7, 8 need to lose the ERM and acquire a VTN...Verify service names in Figure 8
ENERGYINTEROP-235
Change cardinality of EventInfo within EiEvent (WD16- 642)
ENERGYINTEROP-231
Need a location for the permanent location of the EPRI/Horst paper
ENERGYINTEROP-239
We have to have some better variant on Conformance when we release Energy Interoperation for public review
ENERGYINTEROP-229
Location attributes within EiEvent are weak. (WD16 - 642)
ENERGYINTEROP-223
line 697 and line 702 (table): There is no operation to delete a quote yet the table has EIDeleteQuote
ENERGYINTEROP-224
line 716 regarding possible change of "Contract to Aggreement"
ENERGYINTEROP-233
Figure 6 is a repeat of of figure 1. This is OK, the narrative reprise works with the text. Figure 6 should probably be decorated with the VTN/VEN labels to show development, and not an error.
ENERGYINTEROP-217
Create a support service (WD 15, 16; section 7)
ENERGYINTEROP-236
Requires Program communication services to match price communication services
ENERGYINTEROP-218
line 460: "This work assumes that there is no direct interaction across the ESI." However there are assets on the other side of the ESI that have direct interation in eiEvent and eiConstraint.
ENERGYINTEROP-220
line 517: Structure of Interactions is different for Transactive Services and VTN/VEN Services
ENERGYINTEROP-227
Need more explicit definition of how wscal::Sequnce is used to describe the EiEvent time periods (WD16 - 642)
ENERGYINTEROP-222
line 660: Change Transaction Services to Transactive Services consistent with first line of section.
ENERGYINTEROP-228
Line 618: Need to be clear that events can be raised for any valid reason agreed to by the parties to a transaction.
ENERGYINTEROP-215
Remove 0-* as optional requirements/services/elements as it creates interoperability challenges (WD15, ln 643-649)
ENERGYINTEROP-209
Critical: Remove dependencies to WSCal via EMIX (WD15, ln 642-644, figure 9)
ENERGYINTEROP-212
UML Class Diagrams for EiEvent and Associated Classes, Operation Payloads (WD15, ln. 643-649)
ENERGYINTEROP-208
Critical: Provide mechanism for events schedules inside of EiEvent Service (WD 15, ln. 627-644)
ENERGYINTEROP-207
Critical: Include simple client information in EiEvent Service text and figure 9 (WD15, ln. 619-644, figure 9)
ENERGYINTEROP-211
Critical: Provide mechanism for dynamic pricing EventInfoTypeID (WD15, pg 642-644)
ENERGYINTEROP-203
Line 718 Section 7.3.1 - Feedback vs. Status
ENERGYINTEROP-199
Line 685: Constraints are applicable to Both Asset and Resource.
ENERGYINTEROP-197
Line 624. "a price event is performed using a SendQuote operation" is followed by table with xxEvent operations.
ENERGYINTEROP-194
Figures 2,3,4,7 refer to ERM party. I do not see that term defined.
ENERGYINTEROP-196
Lines 649, 624 Figure 10 identifies EISend... and EISent payloads. There is no matching service in the table on line 624.
ENERGYINTEROP-193
General - Beat the horse - we've identifed the issue with respect to levels
ENERGYINTEROP-191
General - One thing is a model : DR is done by having a building integrator spend 2 weeks.
ENERGYINTEROP-195
Lines 598, 604 where is the interaction for DR Standing Bid defined?
ENERGYINTEROP-188
General - Talking to CAISO - they understand the logic behind this. They are looking into providing level for the different situations, rather than or on top of comm price.
ENERGYINTEROP-189
General - Two interp you can give to a level that you exchanged. One is that you've exchanged/sent a price table, and the label is an index into the table. In scope for PAP09 and EI. The other is information for load shedding. Then DLC is another thing.
ENERGYINTEROP-186
General - Even at edge conformance group. Go to OpenADR.
ENERGYINTEROP-187
General - Price means a lot to customer, not a lot to customer load shed strategies unless customer can respond to a spec price...has to be some exchange from a price to a level - up to the program to decide. Communication has to be possible.
ENERGYINTEROP-185
General - Direct reaction to Rish - understand toasters need HML, interact with those. What are the conformance rules for HML? If it's only kinda high or medium?
ENERGYINTEROP-182
General - Need a better understanding of how schedules are tied to eventinfo type.
ENERGYINTEROP-183
General - Dyn price, not just real time prices.
ENERGYINTEROP-177
591 - Comment on l591 - dig deeper and understand what it means. If want to transmit a price...simpler. An EiEvent never contains a price. Agree with M should be able to include other data items. No notion of the simple levels of price from OpenADR.
ENERGYINTEROP-171
613 - One - issues about gluon
ENERGYINTEROP-181
General - Don't see simple price levels -- can be an instance of the eventinfo type
ENERGYINTEROP-169
610 - Looking at relationship of events for the deployment level.
ENERGYINTEROP-165
472, 477 - Typo - promissee should be promissor
ENERGYINTEROP-164
469 - Define terminology - define or refererence.
ENERGYINTEROP-162
435, 454-455 - Are buyers and seller defined before? The place you get tripped up are words used every day.
ENERGYINTEROP-159
401-407 - Looking at 4 essential market activites. Where is (or is not) the distribution of day ahead price/RTP?
ENERGYINTEROP-161
397 - Assumes timely automated metering? Also automated pricing information
ENERGYINTEROP-157
414 - Moving target - rewrite to current "tender" etc
ENERGYINTEROP-166
492 - Redundant IJK,...in drawing. Why is [last] K and second level C & D shown? They're not doing anything.
ENERGYINTEROP-160
404 - In EMIX we're moving from offers to bids; need to clarify here
ENERGYINTEROP-153
341 - Rewrite section
ENERGYINTEROP-172
Sections 6.3 and 6.4 - Sections list services. Documentation looks pretty good. Do you intend/would it be a good idea to present state machines that show the various states for this and the lifecycles?
ENERGYINTEROP-154
377 - In scope - info models for contract and product distrib. Explain. Is product connection the product definition in EMIX?
ENERGYINTEROP-150
231 - "Energy consumers" line.... Need better explanation. Unclear how manage your local energy supply. Seems curtailment is not part of their local energy supply.
ENERGYINTEROP-109
Line 328 Section 2.1 Does scope only include transactive energy, DR and DER interactions
ENERGYINTEROP-111
line 492 says we will be begin with Transactive interactions but then we jump directly to DR interactions
ENERGYINTEROP-104
All - Terminology; see how the next draft is.
ENERGYINTEROP-97
886 - Some way to characterize/clarify what the potential applications of this standard may be.
ENERGYINTEROP-99
874 - If there's a testing and conformance process, could be referenced.
ENERGYINTEROP-94
886 - Note in regard to performance expectations. Talks about performance parameters in terms of seconds. Is this suitable within this document given that some networks are and have been deployed.
ENERGYINTEROP-100
874 - True for entire document. Def scope and divided the sections. Within each could be much bigger conformance scopes, or a separate entity might be addressing each.
ENERGYINTEROP-98
874 - My question - assuming conformance related to testing and cert - not clear what we're trying to certify here?
ENERGYINTEROP-83
754 row 1 - Consistency across document.
ENERGYINTEROP-87
760 - Not programs; NAESB is doing a spec
ENERGYINTEROP-78
742 - Invoking a DR reliability event. But say "DR event" - does this mean it can't be used for anything else? Only reliability event?
ENERGYINTEROP-80
750-751 - Not sure what this means? Doesn't seem like a sentence. May be missing a period after Participant. Don't' understand what you're saying.
ENERGYINTEROP-69
690 - Diagram could be more clearly.
ENERGYINTEROP-75
718 - General is really more DR services and needs to be more clearly defined.
ENERGYINTEROP-82
754 - "set and retained until deleted" - are we talking about who deletes it? Do we need to clarify?
ENERGYINTEROP-72
710 - Challenge in sentence "derived from..."
ENERGYINTEROP-65
674 - Wholesale reducing energy. Could have two different aggregator, one with a set of pool pumps and another with a set of Air Conditioners. Might bifurcate down the chain, higher converse. If blue circles taken out of columns might be easier to read.
ENERGYINTEROP-71
690 - Have a figure like that in the SRS where we model the logical components.
ENERGYINTEROP-68
674 - General comment - defined two actors, NOT two CLASSES of actors.
ENERGYINTEROP-58
674 - Context again - not drawn here.
ENERGYINTEROP-59
674 - Don't have two bosses. More than two?
ENERGYINTEROP-55
640 - After outlining that Party is either, why not use it instead of "Entity"? Use "Party".
ENERGYINTEROP-76
738 - "Dr" should be "DR". If service name blank, should be Dr, but in text DR.
ENERGYINTEROP-63
674 - Last part - situation, follow A=E=L. Single context could be a single event issued by A. Go to E, playing role of an asset. A node could be both participant and ERM. I think that could be ok.
ENERGYINTEROP-60
674 - Can have two bosses - say AC program, lighting program, could have two different companies controlling that resource with potentially different programs.
ENERGYINTEROP-57
674 - At very end said Figure 5, seems to refer to Figure 6.
ENERGYINTEROP-61
674 - Incorporated same concepts in SRS from the EPRI paper.
ENERGYINTEROP-66
674 - Entity A when I look in columns, says BE and E are in the same program. Or enrolled as Participants. (in the same program)
ENERGYINTEROP-56
640 - Interactions - is it important or worthwhile to note that interactions are always in a context, and if so, should we say that the parties play different roles in a given context?
ENERGYINTEROP-64
674 - Last part - situation, follow A=E=L. Single context could be a single event issued by A. Go to E, playing role of an asset. A node could be both participant and ERM. I think that could be ok.
ENERGYINTEROP-54
640 - Figure numbers under the figures and the text don't line up.
ENERGYINTEROP-49
If we've def diff between "energy" and "smart energy" -- I think we should, don't know the energy.
ENERGYINTEROP-62
674 - Different program in that case
ENERGYINTEROP-51
599 - Discuss whether M&V in scope or not. Utility settlement, separate transaction. Not sure whether in the scope. Active discussion. NAESB Wholesale and retail M&V, bigger issue to look.
ENERGYINTEROP-52
600 - Is this ESI definition in sync with OpenHAN and SEP 2.0 or the other references? Rish: Use NIST definition of ESI. NIST has very clearly defined in the Framework.
ENERGYINTEROP-42
563 - Subsections under 3.1 are normative definitions. But none appear to be definitions of terms. Descriptions and pointers.
ENERGYINTEROP-48
587 - A: Reduction contracts. But first two sentences talk about market ops. Confusing.
ENERGYINTEROP-43
559 - Would you/should you be putting a reference to those actors here, or listing those actors? Terms of actors for service definitions only have three actors that are somewhat generic. If not explicitly using actors, may strike the paragraph.
ENERGYINTEROP-47
587 - Suggest bullets to be consistent.
ENERGYINTEROP-45
575 - State that these terms are defined by reference to EMIX without saying which . Need reference. Don't remember the point "Real Time Price" or "Forward Price" of other terms. Better binding would be useful.
ENERGYINTEROP-38
501 - A bit of editorial stretching. E.g. l514. This should be a more technical document.
ENERGYINTEROP-26
420 - In double quotes - quote - cite Stephanie Hamilton.
ENERGYINTEROP-22
390 - Say "Does include other forms.." - make it positive.
ENERGYINTEROP-21
383 - Second sentence. What does deep integration mean?
ENERGYINTEROP-27
420 - Is that only in the case of collaborative energy? How does it apply?
ENERGYINTEROP-19
357 2.2.2 - Bullets not consistent. First bullet on 359, implies indentation. 362-363 - just for clarity, information (H/P/Projected) put that in front of load and usage. Not limited to... not connected to just load and usage.
ENERGYINTEROP-13
332 - Energy Information Service Provider should be EISP (not ESP). Possible typo.
ENERGYINTEROP-10
212 - Should we be using info model that's already developed?
ENERGYINTEROP-11
252 - Should ref TCP, etc
ENERGYINTEROP-6
TOC - Section 1 - through. 2. guiding principles, philosophy. Section 3 vocabulary, specific services. 4 is architecture.
ENERGYINTEROP-8
208-240 - Question on diagram: Generator I assume is the power plant, not the DER? Not customer? Include the ISO to generator?
ENERGYINTEROP-2
33 - Nothing that limits it to DR. (Correct) Broader than DR.
ENERGYINTEROP-4
49, 35 - OASIS SOA and TC - don't have the doc. Is there list of definitions and abbreviation.
ENERGYINTEROP-654
Errors in UML Diagrams
ENERGYINTEROP-648
WD34 Spec : Correct EiDelivery diagram and Figure errors.
ENERGYINTEROP-637
Add request identifier to all requests (Createm Cancel, Request) that have multuiple payloads
ENERGYINTEROP-650
WD 34 Section 6.3 Improvements to description of Enrollment for Transactive Market Contexts
ENERGYINTEROP-636
Defined the ordering of Events
ENERGYINTEROP-635
Please define Pending as in "Pending Event"
ENERGYINTEROP-634
Please define Active as in "Active Event"
ENERGYINTEROP-645
Correct WD34 UML DIagrams with refElementXXX
ENERGYINTEROP-639
Make Target optional in DistributeEvent
ENERGYINTEROP-630
5.2.2 Application Specific Extensions appear to violate the statement on 475 on no direct interaction across the ESI.
ENERGYINTEROP-638
Create paragraphs discussing VEN and Resource and Multiplicity for [end of] section 3
ENERGYINTEROP-629
475 - statement that there are no direct interactions across the ESI does not seem to be enforced in EI.
ENERGYINTEROP-625
Add additional filters to eiRequestEvent and eiRequestPendingEvent.
ENERGYINTEROP-624
eiRequestPendingEvent :transactionName and eiRequestEvent:transactionName seems to be unnecessary.
ENERGYINTEROP-617
Change EiDelivery to use EMIXBase and change Service names to Request and Reply.
ENERGYINTEROP-619
WD33 Figure 8-1 Service Consumer should be Actor and Service Provider should be EnrollAdminParty.
ENERGYINTEROP-614
EIReports section is still very unclear
ENERGYINTEROP-600
Create RequestPendingEvents/ReplyPendingEvent operations in EiEvent Service; add definition of "Pending"
ENERGYINTEROP-588
Add Elements to match each of the enumerated types
ENERGYINTEROP-593
Recommended edits to WD32 payloads for transactive services.
ENERGYINTEROP-587
Reading Type is muddled
ENERGYINTEROP-591
Use consistent naming in Stream-derived types
ENERGYINTEROP-585
Multi-address event delivery
ENERGYINTEROP-603
Editorial comments wd32 Section 4
ENERGYINTEROP-590
Report Service in Spec does not reflect all Operations; Split into separate section
ENERGYINTEROP-597
Add an Interval to Request and Reply payloads to limit responses to that interval if present
ENERGYINTEROP-529
Feedback Collector PR02
ENERGYINTEROP-528
Attributes in EiMarketContext not in the right context for events
ENERGYINTEROP-526
Make eitc:eventDescriptor:operatingDay optional
ENERGYINTEROP-527
Add priority attribute to the EIEvent description
ENERGYINTEROP-524
Continuity of Transaction
ENERGYINTEROP-520
Customer is now defined as an Enrollment Entity in the Specification but is not yet in the corresponding schema.
ENERGYINTEROP-521
Enrolling Entity should include Market Partiicpant and System Operator ( see Table 7.1)
ENERGYINTEROP-516
CLONE -Con Edison use case (Patricia Robison)-- need feedback every 5 min: what can you shed now, for how long? (and what ramp rate?)
ENERGYINTEROP-506
Section 4.4 - "These durations are expressed in the Emix Resource Description" - Emix Resource Description not included
ENERGYINTEROP-502
Remove eventSchedules from eiMarketContext
ENERGYINTEROP-501
Con Edison use case (Patricia Robison)-- need feedback every 5 min: what can you shed now, for how long? (and what ramp rate?)
ENERGYINTEROP-497
Baseline Quantity May need to be optional
ENERGYINTEROP-493
EiTender issues including spelling
ENERGYINTEROP-495
EiTransaction Service issues and errors
ENERGYINTEROP-491
How to treat overlapping events.
ENERGYINTEROP-490
Do not support eiChangeEvent - Use cancel and create to do changes to existing event.
ENERGYINTEROP-457
900 Table 9 L createdContractAck should be createdTransactionAck
ENERGYINTEROP-468
Add new signal type
ENERGYINTEROP-462
1091 Change Title to VTN/VEN Support Services as these services are not used by Transactive Interacttions.
ENERGYINTEROP-454
741: editorial
ENERGYINTEROP-452
423: Rewording needed to make clear that Transactive Energy is about both Market Based and Non-Market Based Energy Interactions
ENERGYINTEROP-448
660 : Account concept in WD24 is under developed.
ENERGYINTEROP-446
Front matter editorial issues wd24
ENERGYINTEROP-450
717 Clarification of the Roles of Resources, Curtailment and Generation
ENERGYINTEROP-443
745: Section 5.4 is VEN/VTN centric
ENERGYINTEROP-439
Section 3 Minor Edits
ENERGYINTEROP-440
461 conform language regarding option parties to that of EMIX.
ENERGYINTEROP-442
550 : 3,2.3 VTN and VEN invoking services on each other and 3.2.4 DR interactions are not consistent with interactions in 3.3.2.
ENERGYINTEROP-449
686 Improper Figure Title
ENERGYINTEROP-432
Ei Response Type Proposal: WD23 - WIP7
ENERGYINTEROP-431
wd34 schema: ws-calendar shcema w/ multiple additional zips
ENERGYINTEROP-430
wd23: normative references link to ws-calendar spec gets '404 not found' error
ENERGYINTEROP-426
Interaction pattern diagrams for EIQuote and EIEvent services are missing interactions
ENERGYINTEROP-427
Missing attributes in the payloads for the EIQuote and EIEvent service that are used to support non-repudiation.
ENERGYINTEROP-417
Proposed changes to the wd24 wip 1 EiClasses.xsd schemas
ENERGYINTEROP-420
Refactoring - was Proposed changes to the wip 8 EiEvent.xsd schemas (and other dependencies)
ENERGYINTEROP-416
Improved References to UCAIug work
ENERGYINTEROP-410
Need to add current value to signals
ENERGYINTEROP-412
Section 5.4 Naming of Services and Operations and Section 5.5 Push and Pull Patterns Needs Editing
ENERGYINTEROP-408
Recommended changes to energyinterop-1-0-schema-wd23-wip7 version of schema
ENERGYINTEROP-405
Deal with Fig 6-6 per earlier notes
ENERGYINTEROP-407
The term offer is still used in a few places in the latest Ei Schemas
ENERGYINTEROP-402
Baseline as part of Event message may not be needed
ENERGYINTEROP-397
Collector for Interaction Patterns
ENERGYINTEROP-365
EiResource use of power:meterID
ENERGYINTEROP-363
Pnode differences in EiEnrollment
ENERGYINTEROP-371
What is purpose of new EILocation element
ENERGYINTEROP-374
Event::vtnComment looks like an invitation to non-interoperability
ENERGYINTEROP-368
Use EMIX:BusinessScheduleType in OptOut & OptIn Schedule creates some ambiguity
ENERGYINTEROP-362
Schemas appear to use an eMIX power structure not based on IEC 61970

Refresh results

<< Previous 1 2 3

Export - CSV (All fields)

Export - CSV (Current fields)