OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[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=24611#action_24611 ] 

Edgardo Luzcando  commented on ENERGYINTEROP-295:
-------------------------------------------------

@ Bill The registration of: Service Location, Asset Group, and Resource addresses the IRC concerns.  From there it is just a matter to having the model support the necessary relationships to support the payloads of each registration.

@Bill
For 'Service Provider' the IRC used the definition (from NAESB work I believe): "An entity that coordinates demand resources to deliver demand response services", which makes no distinction of whether or not aggregation is used.

@Bill
The IRC model has DemandResponseEvent, DispatchInstruction, Schedule and Award as specializations of Notification.  In essence, the aforementioned four classes are types of Notifications, but their relationships (within the model) and payloads vary.  This could be modeled differently, but for the IRC it was important to note the differences because these interactions have different non-functional requirements (See http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/39645/Non-Functional%20Requirements%20Rev1_20100930.pdf)

@Bill
I think that Feedback and Status differences were addressed in a more recent conversation, thought I am not sure where to find this information now.

@Bill
We are meeting with Donna this Friday to discuss and finalize issues around MeterData rejection.







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