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-369) Opt containsadditional elements that are not in the submitted models - need explanationon why they are there



    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25397#action_25397 ] 

Bruce Bartell commented on ENERGYINTEROP-369:
---------------------------------------------

This is the language from NAESB PAP09 regarding opt in/out.

Opt in/out
This is used to temporarily opt in/out of DR Events and to override the normal operational constraints. The opt-in/out can be specified using the following criteria:
•	All events in a program indefinitely
•	Specific DR Event
•	All events in a specific time period.
In addition, there may be a schedule associated with the opt in/out state.

If we have to support opt-in because of this we will need a statement on how to handle or avoid contradictory values. 

> Opt contains additional elements that are not in the submitted models - need explanation on why they are there
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-369
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-369
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: schema
>    Affects Versions: wd22
>         Environment: Bruce Bartell
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>            Priority: Minor
>
> EIOptout:contractName - what is this for?
> venID is in twice once at root and again in EIOpt as 1->*. The defintions do nto match.
> The definition in the recurring element reads like a customer account ID ("If this ProgramConstraint is associated with a specific ParticipantAccount then this is the
> identifier of the ParticipantAccount that it is associated with.) 
> validDateTimes "These are the date/times during which a DR Event may be issued. If undefined then it is assumed that the DR Event may be issued at any time except as specified by the other constraints such as the black out dates and times." This looks like a program attribute.
> maxConsecutiveDaysFilter No defintion. Enumerator  of  Accept or Reject. Accept or reject what?
> blackOutDateTimes Redundant with optOutSchedule. I thought we were going to use this as Resourse Constraint?

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