OpenADR 2.0 DR Program Guide Certification Documentation

1 Introduction The OpenADR Demand Response Implementation Program Guide (referred to hereafter as the Program Guide) contains templates for common Demand Response (DR) programs and best practices recommendations for using OpenADR with those programs. The following DR programs are included in the Program Guide: • Capacity Bidding Program (CBP) • Critical Peak Pricing Program (CPP) • Distributed Energy Resources DR Program (DER) • Fast DR Dispatch Program (FDR) • Public Station Electric Vehicle RealTime Pricing Program (EVP) • Residential Electric Vehicle Time of Use Program (EVR) • Thermostat Program (THR) OpenADR 2.0 VTNs and VENs may obtain certification for one or more of the Demand Response Programs noted above. The objective of certification is to ensure VTNs and VENs can be easily deployed in DR programs where the technical requirements defined by Utilities also model the Program Guide recommendations. The purpose of this document is to provide all the information necessary to successfully certify that VENs and VTNs follow the Program Guide recommendations contained in the Program Guide. This documentation is divided into the following major sections: • Section 2, Test Methodology This section provides a detailed description of the test methodology used for the Program Guide certification test cases. • Section 3, Test Execution This section provides guidance on how to configure and execute the A or B profile DR Program Guide certification test cases. Note that this section assumes users are familiar with the A and B profile Test User Guides provided as part of the OpenADR message exchange certification documentation packages. • Section 4, Test Case Definitions This section provides detailed documentation for each of the required test cases used in certifying devices for conformance to Program Guide recommendations. • Annex A, PICS This section contains documentation that must be submitted to the test lab as part of the certification process. Readers should carefully review section 2, Test Methodology, before reviewing the balance of this document or attempting to run Program Guide certification test cases.

OpenADR 2.0 DR Program Guide Certification Documentation Revision Number: 1.0.1 Document Status: Final Released: June 10, 2016 OpenADR 2.0 DR Program Guide Certification Documentation Revisions Version 1.0 1.0.1 Changes Final version released Updated Thermostat Program sample report Date/Editor JZ - 2/22/16 JZ – 6/10/16 Copyright © OpenADR Alliance (2016) All rights Reserved -2- OpenADR 2.0 DR Program Guide Certification Documentation Contents Copyright © OpenADR Alliance (2016) All rights Reserved -3- OpenADR 2.0 DR Program Guide Certification Documentation Introduction The OpenADR Demand Response Implementation Program Guide (referred to hereafter as the "Program Guide") contains templates for common Demand Response (DR) programs and best practices recommendations for using OpenADR with those programs The following DR programs are included in the Program Guide: • Capacity Bidding Program (CBP) • Critical Peak Pricing Program (CPP) • Distributed Energy Resources DR Program (DER) • Fast DR Dispatch Program (FDR) • Public Station Electric Vehicle Real-Time Pricing Program (EVP) • Residential Electric Vehicle Time of Use Program (EVR) • Thermostat Program (THR) OpenADR 2.0 VTNs and VENs may obtain certification for one or more of the Demand Response Programs noted above The objective of certification is to ensure VTNs and VENs can be easily deployed in DR programs where the technical requirements defined by Utilities also model the Program Guide recommendations The purpose of this document is to provide all the information necessary to successfully certify that VENs and VTNs follow the Program Guide recommendations contained in the Program Guide This documentation is divided into the following major sections: • Section 2, Test Methodology - This section provides a detailed description of the test methodology used for the Program Guide certification test cases • Section 3, Test Execution - This section provides guidance on how to configure and execute the A or B profile DR Program Guide certification test cases Note that this section assumes users are familiar with the A and B profile Test User Guides provided as part of the OpenADR message exchange certification documentation packages • Section 4, Test Case Definitions - This section provides detailed documentation for each of the required test cases used in certifying devices for conformance to Program Guide recommendations • Annex A, PICS - This section contains documentation that must be submitted to the test lab as part of the certification process Readers should carefully review section 2, Test Methodology, before reviewing the balance of this document or attempting to run Program Guide certification test cases Copyright © OpenADR Alliance (2016) All rights Reserved -4- OpenADR 2.0 DR Program Guide Certification Documentation Test Methodology Terms and Acronyms The following terms and abbreviations are used in this document: Term Description CBP CMP CPP DER DR DUT_VEN DUT_VTN EV EVP EVR FDR SMP TH_VEN TH_VTN THR TYP VEN VTN Capacity Bidding Program Complex Use Case Critical Peak Pricing Program Distributed Energy Resources Program Demand Response Device Under Test Virtual End Node (VEN) Device Under Test Virtual Top Node (VTN) Electric Vehicle Public Station Electric Vehicle Real-Time Pricing Program Residential Electric Vehicle Time of Use Program Fast DR Dispatch Program Simple Use Case Test harness playing the role of the VEN Test harness playing the role of the VTN Thermostat Program Typical Use Case Virtual End Node Virtual Top Node Scope Certification tests will be limited to validating the best practices recommendations in the Program Guide are followed for a given Demand Response program It is assumed that devices being submitted for certification have passed the message exchange certification process, and the test cases defined in this document will focus solely on validating the Program Guide recommendations Methodology Test cases will model the simple, moderate, and complex use case examples defined in the Program Guide The test harness will play the role of the opposite party (VEN or VTN) in interactions with the Device under Test (DUT) Each test case will define a set of prerequisites, a test scenario consisting of a sequence of VEN/VTN message exchanges, and an expected result Test scenarios validate the following types of behavior: • The ability to send or receive each of the event signals recommended • The ability to target resources specified in the event and to cause the behavior of those resources to change in proportion to the signal values specified in the event • The ability to exhibit the recommended default optIn/optOut response • For B profile devices, the ability to qualify resources participating in an event using oadrCreateOpt if recommended in the guide, and to cause resources to adapt their behavior in response to that qualification • For B profile devices, the ability to request and publish each of the reports recommended for a given program (if any) and to populate each report with realistic data for each of the requested data points In order to ensure VTNs and VENs can be easily deployed in DR Programs that also model the Program Guide recommendations, some aspects of the testing defined herein will be functional in nature and go beyond testing the simple exchange of messages between VTNs and VENs Program Guide certification testing for A profile VENs will be limited to the simple use case Copyright © OpenADR Alliance (2016) All rights Reserved -5- OpenADR 2.0 DR Program Guide Certification Documentation scenarios utilizing only those signals and services supported by the A profile In order to validate the functional behavior of a VEN being tested, the VEN implementer will be required to provide the following capabilities as part of the VEN submitted for certification testing: • Two mock load shedding resources that can be uniquely addressed using eiTarget resourceIDs that will visibly respond to changes in the signal values received as part of a DR event The two mock resources associated with the VEN must be able demonstrate three levels of load shed for each signal equivalent to the simple signal's medium, high, and special load shed levels • B profile VENs must return telemetry data for each required report using either a real data source whose values are variable in nature or use a mock data source that will produce random values within a realistic range for the type of data contained in the report • The ability to configure the VEN to respond to either a simple signal or a more complex signal where both are contained in the event payload Validation of successful test execution will be done both programmatically and through operator observations of DUT behavior Each test scenario will contain matching VTN and VEN test cases Event durations, interval time frames, and reporting characteristics have been modified from those shown in the Program Guide to facilitate reasonable test case execution times Not all programs defined in the Program Guide have all three use case scenarios defined: Simple, Typical, and Complex Test cases will only be defined where use case scenarios exist in the Program Guide Some programs defined in Program Guide may only be practical in a push or pull exchange mode due to network latency or fire wall issues The following programs have only push or pull test cases: • Pull Only Test Cases o Residential Electric Vehicle Time of Use Program • Push Only Test Cases o Fast DR Program Visual observation of ramp up or recovery times is out of scope for certification testing, although testable values will be sent as part of the Fast DR Dispatch test cases, and if the DUT_VEN performs ramp up and/or recovery behavior it will not cause the test cases to fail The test cases not specify specific values for reportDataSource in the oadrRegisterReport payloads as there is no actionable behavior associated with these values and the VEN DUT may not have complete control of the values populated in this object Test Case Organization The Program Guide test cases will be distributed as a separate folders within the same Eclipse projects distributed for the A and B profile message exchange certification tests The Program Guide tests are organized as follows within these projects: • testcases o pull  DR_Program_Guide • [Program Name] Copyright © OpenADR Alliance (2016) All rights Reserved -6- OpenADR 2.0 DR Program Guide Certification Documentation o VEN o VTN   • [Test Case Name(s)] [Program Name] o o [Test Case Name(s)] push  DR_Program_Guide • [Program Name] o VEN o VTN   • [Test Case Name(s)] [Test Case Name(s)] [Program Name] o Note that the A profile Program Guide test cases not have standalone "selftest" test cases The VEN and VTN Program Guide test cases for the same test scenario were designed to be run against each other for self testing purposes Test Case Numbering Test case numbering uses the following pattern: XXX_ZZZ_UV_TH_WWW_1 XXX = Three letters designating the DR Program • CBP = Capacity Bidding Program • CPP = Critical Peak Pricing Program • DER = Distributed Energy Resources DR Program • EVP = Public Station Electric Vehicle Real-Time Pricing Program • EVR = Residential Electric Vehicle - Time of Use Program • FDR = Fast DR Dispatch Program • THR = Thermostat Program ZZZ = The use case scenario being tested: • SMP = Simple use case • TYP = Typical use case • CMP = Complex use case U = A letter indicating the profile for the test case • A = OpenADR 2.0a Profile • B = OpenADR 2.0b Profile V = A digit indicating the exchange model tested: • 1= Pull Test • = Push Test TH_WWW = The "TH" stands for Test Harness and the "WWW" indicates the role the test harness will play, either "VEN" or "VTN" This helps the user keep track of the role that the test harness is playing during payload exchanges _1 = An optional postfix to indicate that the test case should be started before the device under test Copyright © OpenADR Alliance (2016) All rights Reserved -7- OpenADR 2.0 DR Program Guide Certification Documentation An example test case would be CPP_TYP_B1_TH_VEN_1 This would be a B profiles pull test for Critical Peak Pricing that uses the typical use case data set, where the Test Harness plays the role of the VEN and the target for testing is the VTN This test case should be started before the DUT_VTN Copyright © OpenADR Alliance (2016) All rights Reserved -8- OpenADR 2.0 DR Program Guide Certification Documentation DUT Configuration Capabilities The VEN must have the following configuration capabilities: • The ability to map the resourceID strings to mock or real resources associated with the device under test • If necessary, the ability for the test operator to trigger the generation of mock data used in each of the data points in a report required by the Program Guide test cases • The ability for the test operator to observe changes in resource behavior in proportion to event signal interval values This can be an indicator in a console log output, or some visual or behavioral indicator • The ability to set event signal interval value thresholds that trigger resource load shed behavior Note that that the interval values send by the test harness can be control by modifying the Test Harness properties • The ability for the test operator to trigger oadrCreateOpt to modify the resources participating in an event, if the Program Guide template under test requires that functionality The VTN must have the following configuration capabilities: • The ability for the test operator to dispatch the event payloads defined in this test specification for the Program Guide template under test • The ability for the test operator to trigger reports requests defined in this test specification for the Program Guide template under test DUT Transport and Security Configuration Test cases for a given DR Program template will be executed once as part of the certification process using the transport and exchange model decision tree shown below: • Thermostat Program (THR) and Residential Electric Vehicle Time of Use Program (EVR) test cases shall be tested over HTTP Pull • The Fast DR Dispatch (FDR) test cases shall be run over XMPP if supported by the DUT Otherwise use HTTP Push • If the DUT does not support HTTP transport, tests cases shall be run over XMPP • If the DUT supports only the HTTP Transport and does not support the push exchange model, test cases shall be run over HTTP Pull • Each remaining DR program supported by the DUT shall be tested using an alternating combination of the supported transports and exchange models (push, pull) All test cases will be run with the test harness configured for HTTP_SHA256_Security or XMPP_SHA256_Security security Test Harness Program Guide Property Values Signal Interval Values The test harness will have the following new configuration properties added to facilitate setting event signal interval values that are used in outbound oadrDistributeEvent payloads sent by the Test Harness These same property values will determine the test operator's Copyright © OpenADR Alliance (2016) All rights Reserved -9- OpenADR 2.0 DR Program Guide Certification Documentation expectations as to the load shedding behavior of the DUT_VEN The configuration property keys shown below will be used in the test case definitions Values shown are defaults and may be changed as needed for testing with a specific DUT: Property Default Value Simple_Medium Simple_High Simple_Special Electricity_Price_Medium Electricity_Price_High Electricity_Price_Special Load_Dispatch_Delta_Medium Load_Dispatch_Delta_High Load_Dispatch_Delta_Special Load_Dispatch_Setpoint_Medium Load_Dispatch_Setpoint_High Load_Dispatch_Setpoint_Special Load_Control_TempOffset_Medium Load_Control_TempOffset_High Load_Control_TempOffset_Special Load_Control_Capacity_Medium Load_Control_Capacity_High Load_Control_Capacity_Special Bid_Load_Setpoint_Medium Bid_Load_Setpoint_High Bid_Load_Setpoint_Special Bid_Price_Value 0.21 0.25 0.31 -10 -20 -30 60 50 40 60 50 40 1.00 Validation of inbound oadrDistributeEvents sent from the VTN DUT will not include matching the PayloadFloat values received in interval data with the values above, although the prompts to the test user will request these values be configured in the event Implementation dependent issues may prevent an exact match of values Units Values Some Event signals and reports require additional information for the units used payloads as show in the table below As these properties are used across multiple signal and report names, you may need to modify these property values on a test case by test case basis Property Default Value powerReal_itemUnits powerReal_siScaleCode powerReal_powerAttributes_hertz powerReal_powerAttributes_voltage powerReal_powerAttributes_ac currencyPerKWh_itemUnits currencyPerKWh_siScaleCode temperature_itemUnits W k 60 110 true USD none fahrenheit ResourceID Values The B test harness has a single property called ResourceIDs that contains an array of resource names The test case definitions in this document use the following properties array index identifiers in the test definitions Values shown are defaults and may be changed as needed for testing with a specific DUT: Properties Array Identifier Default Value ResourceIDs[0] "resource1" Copyright © OpenADR Alliance (2016) All rights Reserved - 10 - OpenADR 2.0 DR Program Guide Certification Documentation Use Case Data Set • Event o o o o o o o o Notification: N/A Start Time: Current time + minute Duration: minutes Randomization: minute Ramp Up: None Recovery: None Number of signals: Signal Name: simple       o • Units: N/A Number of intervals Interval Duration(s):2 minutes Interval Value(s): Simple_Medium Signal Target: None Signal Name: LOAD_CONTROL       o o o o Signal Type: level Signal Type: x-loadControlLevelOffset Units: Temperature Number of intervals Interval Duration(s):2 minutes Interval Value(s): Load_Control_TempOffset_Medium Signal Target: None Event Targets: ResourceIDs[0], ResourceIDs[1] Priority: VEN Response Required: always VEN Expected Response: optIn Reports o o o o o o Report Name: TELEMETRY_STATUS Report Frequency: minute Report Granularity: minute Report Subject: Thermostat (all data points)xReading Type: x-notApplicable (all data points) Data Point      o Report Type: x-resourceStatus (oadrOnline, oadrLevelOffset:current) Units: x-notApplicable Well Known rID Property: ThermostatState_Status_WellKnown_rID Well Known rID Values: ThermostatState_Status_LevelOffset_Current_Range Data Point      o Report Type: setpoint Units: temperature Well Known rID Property: ThermostatState_CurrentTemp_WellKnown_rID Well Known rID Values: ThermostatState_CurrentTemp_Range Data Point   Report Type: setPoint Copyright © OpenADR Alliance (2016) All rights Reserved - 54 - OpenADR 2.0 DR Program Guide Certification Documentation    o  Well Known rID Property: ThermostatState_CoolTempSetting_WellKnown_rID Well Known rID Values: ThermostatState_CoolTempSetting_Range Report Type: operatingState Units: customUnit Well Known rID Property: ThermostatState_HVACModeSetting_WellKnown_rID Well Known rID Values: ThermostatState_HVACModeSetting_Range Report Type: operatingState Units: customUnit Well Known rID Property: ThermostatState_HVACMode_WellKnown_rID Well Known rID Values: ThermostatState_HVACMode_Range Report Type: operatingState Units: customUnit Well Known rID Property: ThermostatState_FanModeSetting_WellKnown_rID Well Known rID Values: ThermostatState_FanModeSetting_Range Report Type: operatingState Units: customUnit Well Known rID Property: ThermostatState_CurrentHoldMode_WellKnown_rID Well Known rID Values: ThermostatState_CurrentHoldMode_Range Data Point      o Units: temperature Data Point      o Report Type: setPoint Data Point      o Data Point      o Well Known rID Values: ThermostatState_HeatTempSetting_Range Data Point     o Well Known rID Property: ThermostatState_HeatTempSetting_WellKnown_rID Data Point      o Units: temperature Report Type: operatingState Units: customUnit Well Known rID Property: ThermostatState_CurrentAwayMode_WellKnown_rID Well Known rID Values: ThermostatState_CurrentAwayMode_Range Data Point      Report Type: operatingState Units: customUnit (percent) Well Known rID Property: ThermostatState_CurrentHumidity_WellKnown_rID Well Known rID Values: ThermostatState_Current Humidity_Range Copyright © OpenADR Alliance (2016) All rights Reserved - 55 - OpenADR 2.0 DR Program Guide Certification Documentation Copyright © OpenADR Alliance (2016) All rights Reserved - 56 - OpenADR 2.0 DR Program Guide Certification Documentation Pull Test Sequence Step TH_VEN oardRegisterReport TH_VTN [oadrRegisteredReport] oadrPoll oadrCreatedEvent oadrDistributeEvent Prompts/Notes TH_VEN Note: publish a metadata report containing the reports required by the DUT VTN for this test case TH_VTN Note: This payload response will not be used if testing a real device TH_VEN Prompt: TH_VTN Prompt: TH_VTN Note: Include all signals defined in use case data set oadrResponse TH_VTN Prompt: TH_VEN Prompt: 10 11 oadrPoll 12 13 14 oadrCreatedReport 15 16 oadrUpdateReport 17 18 oadrUpdateReport oadrCreateReport TH_VTN Note: Request report defined in use case data set by searching test harness database for the report Verify report name, rID values, units, reportType oadrResponse TH_VTN Note: Wait until two instances of the report are delivered before exiting test case oadrUpdatedReport TH_VEN Note: Deliver two instances of report at the requested reportBackDuration before exiting test case oadrUpdatedReport Copyright © OpenADR Alliance (2016) All rights Reserved - 57 - OpenADR 2.0 DR Program Guide Certification Documentation Push Test Sequence Step TH_VEN oardRegisterReport TH_VTN [oadrRegisteredReport] oadrDistributeEvent Prompts/Notes TH_VEN Note: publish a metadata report containing the reports required by the DUT VTN for this test case TH_VTN Note: This payload response will not be used if testing a real device TH_VEN Prompt: TH_VTN Prompt: TH_VTN Note: Include all signals defined in use case data set HTTP Ack oadrCreatedEvent oadrResponse 10 oadrCreateReport 11 12 oadrCreatedReport 13 14 oadrUpdateReport 15 16 oadrUpdateReport TH_VTN Prompt: TH_VEN Prompt: TH_VTN Note: Request report defined in use case data set by searching test harness database for the report Verify report name, rID values, units, reportType TH_VTN Note: Wait until two instances of the report are delivered before exiting test case oadrUpdatedReport TH_VEN Note: Deliver two instances of report at the requested reportBackDuration before exiting test case oadrUpdatedReport THR Complex Use Case Test Case Root ID THR_CMP_B1_ THR_CMP_B0_ B Pull Test Case B Push Test Case TH_VEN Verify that the DUT_VTN can send the event signal(s) defined in the THR complex use case data set TH_VTN Verify that the DUT_VEN can receive the event signal(s) defined in the THR complex use case data set and act upon the event Prerequisites DUT_VTN is in a registered state Expected Results 1) Verify that event payload signal characteristics defined in use case data set match received payload 1) DUT_VEN is in a registered state 2) DUT_VEN configured to respond to complex interval value(s) shown in use case data set 1) Confirm DUT_VEN opts in to event 2) Confirm DUT_VEN executes the event, monitoring that only the targeted resources shed load in proportion to the complex interval signal values defined in the use case data set 3) Confirm that the when the DUT_VEN issues the oadrCreateOpt, it stops execution of ResourceIDs[0] Objective Use Case • Event Copyright © OpenADR Alliance (2016) All rights Reserved - 58 - OpenADR 2.0 DR Program Guide Certification Documentation o o o o o o o o Data Set Notification: N/A Start Time: Currenttime + minute Duration: minutes Randomization: minutes Ramp Up: None Recovery: None Number of signals:2 Signal Name: simple       o  • Units: N/A Number of intervals: Interval Duration(s): minute, minutes Interval Value(s): Simple_High, Simple_Medium Signal Target: None Signal Name: LOAD_CONTROL      o o o o Signal Type: level Signal Type: x-loadControlCapacity Units: None Number of intervals Interval Duration(s): minute, minutes Interval Value(s): Load_Control_Capacity_High, Load_Control_Capacity_Medium Signal Target: None Event Targets: ResourceIDs[0], ResourceIDs[1] Priority: VEN Response Required: always VEN Expected Response: optIn, outOut ResourceIDs[0] (oadrCreateOpt) Report(s) o None Pull Test Sequence Step TH_VEN oadrPoll oadrCreatedEvent TH_VTN oadrDistributeEvent Prompts/Notes TH_VEN Prompt: TH_VTN Prompt: TH_VTN Note: Include all signals defined in use case data set oadrResponse TH_VTN Prompt: TH_VEN Note: optOut ResourceIDs[0] with oadrCreateOpt once the event transitions to Load_Control_Capacity_Medium oadrCreateOpt oadrCreatedOpt Copyright © OpenADR Alliance (2016) All rights Reserved - 59 - OpenADR 2.0 DR Program Guide Certification Documentation TH_VTN Prompt: Copyright © OpenADR Alliance (2016) All rights Reserved - 60 - OpenADR 2.0 DR Program Guide Certification Documentation Push Test Sequence Step TH_VEN TH_VTN oadrDistributeEvent Prompts/Notes TH_VEN Prompt: TH_VTN Prompt: TH_VTN Note: Include all signals defined in use case data set HTTP Ack oadrCreatedEvent oadrResponse TH_VTN Prompt: TH_VEN Note: optOut ResourceIDs[0] with oadrCreateOpt once the event transitions to Load_Control_Capacity_Medium oadrCreateOpt oadrCreatedOpt TH_VTN Prompt: Copyright © OpenADR Alliance (2016) All rights Reserved - 61 - OpenADR 2.0 DR Program Guide Certification Documentation Annex A - PICS OpenADR 2.0b Program Guide Protocol Implementation Conformance Statement (PICS) Valid for Certification as of February 22, 2016 Manufacturer: Product Type: Product Name: Firmware Revision: Tested OpenADR 2.0b Program Guide version: Date OpenADR Message Exchange Certification Competed 1.0 Disclaimer: The information provided in this document can be made available to the general public in order to identify the tested versions, features and options By signing this document, the manufacturer confirms that all information provided in this document is correct and the applicable features have been tested Manufacturer Name: Representative Name and Title: _ Signature: Date: _ Copyright © OpenADR Alliance (2016) All rights Reserved - 62 - OpenADR 2.0 DR Program Guide Certification Documentation A.1 Introduction The purpose of this PICS document is to provide a mechanism whereby a supplier of an implementation based on the following requirements may provide information about the implementation in a standardized manner Information provided by the supplier will be used to assess the implementation's compliance to the requirements, as well as to configure the certification tests performed on the implementation A.2 References - OpenADR 2.0 Demand Response Program Implementation Guide, Version 1.0 A.3 Abbreviations and Conventions The PICS information comprises information in a tabular format as follows: • Item Column – A number which identifies the item in the table • Capability Column – A brief description of the requirement • Reference Column or Section Header – A reference to a specific requirement in the specification • Status Column – Contains notations regarding the requirements o M – Mandatory o O – Optional o N/A – Not applicable o X – Prohibited o O-i – Qualified Optional (mutually exclusive or selectable options from a set identified with the same “I” value) o C-i –Conditional (status dependent on support of other optional requirements , identified in footnotes at bottom of table with “i” being a reference integer for the footnote(s)) • Support Column – Yes or No answer is required If feature is not applicable, answer No • Values Allowed Column – Optional column representing set of values allowed • Values Supported Column – Optional column where supplier can indicate a set of values supported by the implementation A.4 Instructions for Completing the PICS The first part of the PICS document, System Identification, is to be completed as indicated with the information necessary to fully identify both the supplier and the implementation Copyright © OpenADR Alliance (2016) All rights Reserved - 63 - OpenADR 2.0 DR Program Guide Certification Documentation The main part of the PICS document is a fixed format questionnaire Answers to questionnaire items are to be provided in the rightmost column by simply marking an answer to indicate a choice, typically Yes or No If an implementation fails to support a mandatory item, or supports a prohibited item, the supplier should provide supplementary information with the PICS document explaining the rationale for the exception A.5 Documents Required for Final Certification - This PICS document Manufacturer’s Declaration of Conformity Completed Test Report from appointed test house A.6 Implementation and Supplier Information Date of Statement Product Name Product Model Number Version Number(s) Non-Default Hardware Configuration Non-Default Software Configuration Supplier Name, Address, Phone, Email Contact name, email, phone for questions A.7 Basic Device Configuration Role Support [ ]Yes [ ]No [ ]Yes [ ]No Profile Support [ ]Yes [ ]No VEN VTN “A” Profile Copyright © OpenADR Alliance (2016) All rights Reserved - 64 - OpenADR 2.0 DR Program Guide Certification Documentation “B” Profile [ ]Yes [ ]No Transport SimpleHTTP - Pull SimpleHTTP - Push XMPP - Push Support [ ]Yes [ ]No [ ]Yes [ ]No [ ]Yes [ ]No A.8 A Profile Pull Program Guide Template Support Item Requirement Capacity Bidding Program (CBP) Requirements from Program Guide Section 9.2.2 Critical Peak Pricing Program (CBP) Requirements from Program Guide Section 9.1.2 Residential Electric Vehicle Time of Use Program (EVR) Requirements from Program Guide Section 9.5.2 Thermostat Program (THR) Requirements from Program Guide Section 9.3.2 Statu s Support O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No Copyright © OpenADR Alliance (2016) All rights Reserved - 65 - OpenADR 2.0 DR Program Guide Certification Documentation A.9 A Profile Push Program Guide Template Support Item Requirement Capacity Bidding Program (CBP) Requirements from Program Guide Section 9.2.2 Critical Peak Pricing Program (CPP) Requirements from Program Guide Section 9.1.2 Fast DR Dispatch Program (FDR) Requirements from Program Guide Section 9.4.2 Thermostat Program (THR) Requirements from Program Guide Section 9.3.2 Statu s Support O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No A.10 B Profile Pull Program Guide Template Support Item Requirement Capacity Bidding Program (CPP) Requirements from Program Guide Section 9.2.2 Critical Peak Pricing Program (CBP) Requirements from Program Guide Section 9.1.2 Distributed Energy Resources DR Program (DER) Requirements from Program Guide Section 9.7.2 Public Station Electric Vehicle Real-Time Pricing (EVP) Requirements from Program Guide Section 9.6.2 Residential Electric Vehicle Time of Use Program (EVR) Requirements from Program Guide Section 9.5.2 Thermostat Program (THR) Requirements from Program Guide Section 9.3.2 Statu s Support O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No Copyright © OpenADR Alliance (2016) All rights Reserved - 66 - OpenADR 2.0 DR Program Guide Certification Documentation A.11 B Profile Push Program Guide Template Support Item Requirement Capacity Bidding Program (CBP) Requirements from Program Guide Section 9.2.2 Critical Peak Pricing Program (CPP) Requirements from Program Guide Section 9.1.2 Distributed Energy Resources DR Program (DER) Requirements from Program Guide Section 9.7.2 Fast DR Dispatch Program (FDR) Requirements from Program Guide Section 9.4.2 Public Station Electric Vehicle Real-Time Pricing (EVP) Requirements from Program Guide Section 9.6.2 Thermostat Program (THR) Requirements from Program Guide Section 9.3.2 Status Support O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No O [ ]Yes [ ]No A.12 A Profile DR Program Guide Properties Settings Please paste any non default A profile Program Guide specific test harness properties settings required to successfully pass the certification tests A Profile Properties Settings Copyright © OpenADR Alliance (2016) All rights Reserved - 67 - OpenADR 2.0 DR Program Guide Certification Documentation A.13 B Profile DR Program Guide Properties Settings Please paste any non default B profile Program Guide specific test harness properties settings required to successfully pass the certification tests B Profile Properties Settings Copyright © OpenADR Alliance (2016) All rights Reserved - 68 - ... © OpenADR Alliance (2016) All rights Reserved -2- OpenADR 2.0 DR Program Guide Certification Documentation Contents Copyright © OpenADR Alliance (2016) All rights Reserved -3- OpenADR 2.0 DR Program. .. DR_ Program_ Guide • [Program Name] Copyright © OpenADR Alliance (2016) All rights Reserved -6- OpenADR 2.0 DR Program Guide Certification Documentation o VEN o VTN   • [Test Case Name(s)] [Program. .. Copyright © OpenADR Alliance (2016) All rights Reserved - 26 - OpenADR 2.0 DR Program Guide Certification Documentation 10 oadrCreateReport 11 12 oadrCreatedReport 13 14 oadrUpdateReport 15 16 oadrUpdateReport