[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ENERGYINTEROP-201) Line 706: OptOutequivalent in IRC model includes: economic, emergency, must run, notparticipating, outage run status, override status, participating.
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Holmberg updated ENERGYINTEROP-201:
------------------------------------------
Proposal: The proposed resolution then is to leave everything as is, and get confirmation from the IRC that this meets their needs. (see comment below)
Resolution: (Public review 1 resolution that was not agreed upon by the committee: Added Reason string to OptOuts. A later activity will permit defintion of constrained sets of strings.) (was: Added Reason string to OptOuts. A later activity will permit defintion of constrained sets of strings.)
Assignee: Edgardo Luzcando (was: William Cox)
I discussed this issue with Bill Cox, Toby, Bruce, and EdK. There is apparently a requirement in the NAESB req docs for an "Opt-In" approach, but Ed Koch did not know the source of that, whether there is really a need, or simply it was a use case discussed that might be useful. OpenADR is the basis for the current Constraint and Opt-Out approach, and the current approach has the blessing of the OpenADR TF (I believe). Bill pointed out that the EiConstraint service actually has both positive (acceptSchedule) and negative (notAcceptSchedule) views of the constraints, but Bill thought adding this positive/negative element to OptOut (or changing the name to something like "tempConstraint") would be problematic.
To the issue of text strings, which are presently covered with the "reason" attribute in the EiOptout class, Bruce didn't like the name "reason" since maybe it didn't express the idea of the project codes that would be passed in this text string (such as the IRC text items mentioned here, i.e., "economic, emergency, must run, not participating, outage run status, override status, participating.") We can change the name if there is a better suggestion that everyone agrees to.
The proposed resolution then is to leave everything as is, and get confirmation from the IRC that this meets their needs.
> Line 706: OptOut equivalent in IRC model includes: economic, emergency, must run, not participating, outage run status, override status, participating.
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ENERGYINTEROP-201
> URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-201
> Project: OASIS Energy Interoperation TC
> Issue Type: Improvement
> Components: spec
> Affects Versions: wd15
> Environment: Bruce Bartell wd15 line 706
> Reporter: Bruce Bartell
> Assignee: Edgardo Luzcando
> Fix For: wd17
>
>
> Group should respond on actual requirement. Does Retail DR really have opt-in programs? Are the remaining items applicable?
> Recommend expanding Option to be equivalent to commit or dispatch status and revising the service names accordingly.
--
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]