[OASIS Issue Tracker] Commented: (ENERGYINTEROP-214) Add amechanism for VEN to send status information to VTNs - a with request fromVTN (WD15, section 5):

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Girish Ghatikar  commented on ENERGYINTEROP-214:
------------------------------------------------

Bill: I agree with Ed Cazalet that we could leverage PAP10/OpenADE for FEEDBACK information as it relates to real-time energy usage. This request was not related to feedback 0 it was "STATUS" information. For the sake of clarity, in OpenADR 1.0 (pg. 27) the feedback information is included as following (and might go beyond the PAP10/OpenADE requirements):

"5. The DRAS feedback client (VEN in EI) at the participant site sends the system load status to the DRAS (VTN in EI). This is a feedback mechanism that is used to record how the participant site responded to the DR event or status of the facility outside an event (e.g. near real time load). It includes the following information:

- Program identifier
- Facility identifier
- Date and time of the event (shed or shift)
- Shed data in kW/kWh
- Near real time load
- Load reduction end uses (Heating, ventilation and air conditioning [HVAC], lighting)
- Event Type (Day‐ahead, Day‐of)
6. The utility program settlement program measures usage in a facility and conducts the settlement activity in the Utility Information System. This process is beyond the scope of this document."

The STATUS information goes beyond this --
 
A participant (VEN manager) can get status information from VTN anytime and include the following (see OpenADR 1.0 pg. 27):

a. Event status (for all participants): o 
- current outstanding events such as load reduction potential based upon all participants in program (optional) and Feedback from DRAS Clients (for those that have optional feedback)
- Eventlogs (I think it's important to have this for the sake of accountability). 

The program manager (VTN manager) can also get status information from the VTN anytime and may include (see OpenADR 1.0, pg 27, 28):

a.  DRAS Client (VEN in EI) communications status
- Currentstatus 
- Last contact
- Current signals levels (included in simple client information requirements) 
- Current participant manual control levels(opt‐out)
 - Communication logs
- Signal logs
- Manual control logs




> Add a mechanism for VEN to send status information to VTNs - a with request from VTN (WD15, section 5):
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-214
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-214
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>    Affects Versions: wd15
>         Environment: Girish Ghatikar wd15 line 619 // wd16 line 618 Section 5
>            Reporter: Girish Ghatikar 
>            Assignee: Girish Ghatikar 
>             Fix For: wd17
>
>
> EiFeedback Service (WD 15, ln 652), where the VEN sends feedback information that aids DR market requirements (e.g., real-time telemetry of energy usage for Ancillary services.). Separating feedback from status gives a way to add mechanism for separate transaction and requirements that are independent of each other. For Status, the VTN request the VEN status anytime (VTN responds), which will include following information on the VEN status (OpenADR 1.0, pg, 31):
> a. DR Event Status (includes outstanding events, feedback information, event logs, etc.). 

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