ASHRAE Journal -November 2012 - B18

OpenADR 1.0 Public specification based on a “de-facto” standard in California. Commercially deployed to foster DR adoption and, initially, to meet California’s automation goals. No compliance tests/certification program. Focused on retail programs, pilots for wholesale markets and ancillary services. Limited feedback capabilities.

OpenADR 2.0 Public specification based on a formal industry standard and NIST’s U.S. smart grid activities. Conforms to the U.S. Smart Grid Interoperability Panel (SGIP) interoperability framework. Has compliance test-tools/certification program. Services for retail and wholesale markets, operations, and distributed energy resources. Explicit feedback capabilities and enhanced schedule, dynamic pricing, and other services.

Table 1: Differences between OpenADR 1.0 and 2.0. programs to allow vendors to develop, test, and demonstrate their ability to integrate with OpenADR signals.

PJM OpenADR Pilot
OpenADR 2.0 was piloted for wholesale DR market communications during spring 2012. PJM (the independent transmission system and wholesale market operator in all or parts of 13 mid-Atlantic States and the District of Columbia) worked with IPKeys Technologies with the goal to test the ability of OpenADR 2.0 to securely implement some core DR use cases for PJM’s wholesale DR programs. There were five participants in the pilot in addition to PJM: a membership warehouse and supercenter-retailer with a headquarters-based monitoring and control system (Participant 1), a grocery chain retailer with no building automation (BA), a fast food restaurant with a cogeneration system, an energy reseller acting as a demand aggregator, and a commercial office building with no BA. The IPKeys Energy Interop Server and System (“EISS”)* was used by all participants to implement the pilot. The EISS system enables automatic reduction of energy consumption during periods of high prices with the implementation of machine-to-machine interactions and preprogrammed facility strategies for load reduction. All participants, except Participant 1, used IPKeys-provided end point units called EISSBoxes. These units connected over the Internet to poll PJM’s EISS Server. The EISSBoxes provide dry contact outputs to signal end use equipment. Meter telemetry (reporting energy usage) was obtained by current transformers recording one minute interval data. Four second telemetry rates were also implemented for future use in the regulation markets. Participant 1 created an OpenADR 2.0 client to receive messages then used its existing infrastructure to signal stores’ energy management systems. This infrastructure also allowed real-time telemetry monitoring of the load shed. The pilot was used to implement three use cases: (UC1) a traditional demand response event, (UC2) a price based load response event and (UC3) the verification of load shed with real-time meter telemetry. UC1 demonstrated two-way machineto-machine conveyance of DR signals and receipt of automated confirmation messages. UC2 conveyed PJM pricing node (i.e.,

A commercial and industrial (C&I) facility manager or a heating, ventilation and air-conditioning (HVAC) consultant may use lighting, HVAC or other end-use control strategies to respond automatically to an OpenADR signal. Common commercial building DR control strategies include HVAC global zone temperature adjustment, pre-cooling (for buildings with significant thermal mass), and lighting level adjustment (bi-level switching or dimming). Such HVAC and lighting strategies are well studied from field data and can provide a 10% to 14% average shed.11 Implementing DR in the industrial sector is more challenging. There is a wide variation in loads and processes across industrial sectors and even within sectors, with resource-dependent loads influenced by external factors such as customer orders or time-critical processing. The uses of OpenADR in the industrial sector have proven that, with careful planning and preparation, there are significant opportunities for DR.12 Recent studies from the DRRC describe DR strategies for peak load reduction in different types of industrial facilities (data centers,13 water and waste water facilities,14 and refrigerated warehouses and food processing facilities15,16). substation) Locational Marginal Prices (LMP) to end point devices as part of the PJM Price Responsive Demand program; the end point included logic to shed load based on pricing levels and return confirmation of the load shed. Pricing logic with hysteresis was implemented in the EISSBoxes. UC3 demonstrated receipt of one-minute interval meter telemetry collected via multiple methods including pulse counting and current transformers. The OpenADR 2.0 Profile A was used as the framework for the pilot with the addition of some services from Profile B. Specifically, the EiEvent service10 was used to communicate DR event signals for UC1 and return acknowledgement. For UC2, prices were sent via the EiEvent service with a Profile B payload; if a preset price was exceeded, then the end point EISSBox or other hardware returned notification of load shed. For UC3,

Demand Response Strategies

*Mention of commercial products or services in this paper does not imply approval or endorsement by NIST, nor does it imply that such products or services are necessarily the best available for the purpose.

B18

B A C n e t ® To d a y a n d t h e S m a r t G r i d | A S u p p l e m e n t t o A S H R A E J o u r n a l

November 2012
ASHRAE Journal -November 2012

Table of Contents for the Digital Edition of ASHRAE Journal -November 2012
