If an asset or resource is capable of separt metering of energy useage, then we could use the usage services (PAP 10) for that purpose. Of course, usage services for ancillary services would have to be fast and would normally be transmitted on a faster communication channel then settlement meter data but the services and payloads can be consistent.

Outstanding events can be queried by the EiEvent service operation EiSendEvents. This should be adjusted to ensure that VTN-to-VEN is acceptable.

We have not defined "event logs"--is there a proposal? A string?

Feedback information is at line 652 in wd16, and includes an XSD "any" for feedbackInfo. What do you suggest be included as "feedback information"? The attributes of EiFeedback are the same as those for OpenADR 1 Feedbback plus feedbackInfo.

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

I just want to point out that PAP 10 (at least in NAESB) is not applicable to wholesale, so if there is a specific suggestion of how it can be leveraged in EITC it should be clear that retail is covered and wholesale is not. Similarly with the notion of a DRAS, which is a concept common to retail but not wholesale.

Rephrasing and changing for security and privacy:

A VEN can get status information from its VTN anytime and may optionally include the following (see OpenADR 1.0 pg. 27):

Includes:
Event status (for all VENs of the VTN [is this secure? I'd say for the requesting VEN only]

• current outstanding events [feedback is from VEN to VTN; why would you request it from the VTN?]
• Event logs

A VTN can also get status information from its VENs anytime.

Includes:
communications status

• Currentstatus
• Last contact
• Current signals levels (included in simple client information requirements)
• Current participant manual control levels(opt‐out and opt-in)
• Communication logs
• Signal logs
• Manual control logs

The use of parts of NAESB PAP10 for feedback doesn't seem to be wholesale/retail related per Edgardo's note, but rather the confirmation and performance information. DRAS is not relevant to EI, so I've eliminated references in the above. The telemetry information used in wholesale markets would seem to perform a similar function.

This needs to be re-evaluated in terms of the M&V discussion with Edgardo, Donna Pratt, and Bill Cox on February 18.

Please evaluate comments and proposed resolution.

Bill: I generally agree with your suggested revisions for status information requests from VTNs (to VENs) and VENs (to VTNs) and responses. We need to make sure the information exchange is consistent with key requirements identified in OpenADR. Otherwise, this issue can be closed.