[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-295) 247: MissingInteractions and Data Elements
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24602#action_24602 ]
Toby Considine commented on ENERGYINTEROP-295:
----------------------------------------------
There are some potentially thorny issues in the use of an unconstrained interface pricing point.
Pnode, anode, service location, and service delivery point are all essentially fungible as "a meter or a place where things could/should/would be metered. Service area is something different.
Service areas were conceived of a way to advertise regional availability of a price. "DR Price event for the industrial area between Highway 7 and the bypass this afternoon." Any particular node is theoretically a part of an infinite number of service areas.
If it is the intent that a registration imply "I am asserting that I qualify for the event in this region", as part of a dynamic process, and perhaps a step toward micro-auctions, then one can imagine a conversation such as:
"Congestion event in region x,y,z,w - looking for DR proposals"
"I'm in registering as within region bounded by x,y,z,w"
"here are the bid signals"
If this is what is intended, then the unconstrained Interface Pricing Point is fine. Otherwise, this should be conformed to excluse Service Area.
> 247: Missing Interactions and Data Elements
> --------------------------------------------
>
> Key: ENERGYINTEROP-295
> URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-295
> Project: OASIS Energy Interoperation TC
> Issue Type: Bug
> Components: spec
> Affects Versions: csd01 - Public Review Draft
> Reporter: Edgardo Luzcando
> Assignee: Edgardo Luzcando
> Priority: Critical
>
> "The service definitions provided by the IRC cannot be fully mapped to the existing specification. See details of current mappings here: http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/40404/Mapping_IRC-to-EITC_Interactions_20101124.docx. All 35 Interactions need to be accounted for to account for the IRC requirements. The payloads of the interactions are largely missing as well. There is an understanding that the Interactions (and corresponding payloads) currently missing are not there because they specificication is still under development, but there is concern of when this will be incorporated into the specification to allow sufficient time to review.
> This issue affect a large portion of the specification (namely sections 7, 8 and 9) where all the current EI services are defined. These services do not currently include the IRC Interactions and corresponding data elements."
--
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]