Meter, Facility Interfaces Distrib/Grid Ops, Markets/Services Domains Metering Backend Meter Interface Metering Network Customer Facility Domain Service Provider Network (for demand response and other services) Service Providers Facility ESI Distributed Storage Facility Network Legend Interface Communication link Communication network Energy Services Interface Logically consider the meter (power/energy measurement device) separately from the communication of demand response signals with the facility. Two important points for standardization that will ease integration and provide flexibility to configuring large numbers of connections in metering and demand response types of applications are 1) meter interface and 2) facility interface. The Meter Interface “exposes” meter functionality for use by the metering service provider. If allowed, the interface could also be used by a facility system to read its own meter. The Facility Energy Services Interface (ESI) is the interface for all service providers sending signals to or receiving information from a building information system; for example, an energy service provider communicating demand response signals. It focuses on the needs of both sides, while “hiding” the details of how each side lives up to its end of the bargain. The ESI allows communicating information such as price, schedule, and emergency alerts, but does not define models of appliances, HVAC, PEV, storage, or distributed generation equipment. This allows things to change on either side of the interface without the other side needing to change as long as the interface stays the same. This also keeps the interface simple (a major objective). This abstract model supports flexible system designs that allow for combined or separate metering and demand response systems that coordinate through back-end business systems or a unified metering and demand response network managed by one company’s system. Standards, such as ANSI C12.18, 19, need to be reviewed for how they fit with a Meter Interface specification using this type of perspective. Similarly, demand response potential standards, such as OpenADR should be viewed from this perspective. Of course, all layers and cross-cutting issues (e.g., security and privacy, per the Interoperability Context-Setting Framework) need to be addressed through agreements at these interface points as well. Inside the facility, multiple applications co-exist on the facility network. One of these is the Energy Management System (EMS) which will manage the various generation and storage assets along with electrical loads. Internal interfaces are depicted to each of these: distributed loads (e.g., appliances), distributed generation, electric vehicles, and distributed storage. Review of existing standards and gaps should concentrate on these interfaces and involve the appropriate stakeholders. Again, the layers of interoperability and cross-cutting issues need to be addressed through agreements at these interface points just as they are with the other interfaces. Electric Vehicles Distributed Loads Distributed Generation ESI

ORIGINAL Demand Response Use Cases: Actors and Logical Interfaces Operations Customer Distribution Service Provider Meter or Smart Meter EMS Grid Operations DR Services Provider Markets Aggregator Retail Market Device/ HAN Device Distributed Generation Smart Appliance Display Distribution Management 3 1 4 2 5 9 6 7 8 10 16 17 11 12 14 15 18 19 20 21 13 ORIGINAL Demand Response Use Cases: Actors and Logical Interfaces HAN: Home Area Network EMS: Energy Management System DR: Demand Response Communications Association / Connector Logical Interfaces Actor 1 Actor 2 # ID Key: DR

B2G Demand Response Use Cases: Operations Customer Distribution Meter or Smart Meter Facility ESI/ HAN interface to EMS Grid Operations DR Services Provider/ aggregator Markets Retail Market maker Distributed Generation Smart Appliance/ Distributed Load Display Distribution Management 3 1 4 2 5,9 10 16 11 15 18 13 B2G Demand Response Use Cases: Actors and Logical Interfaces HAN: Home Area Network EMS: Energy Management System DR: Demand Response Communications Association / Connector Logical Interfaces Actor 1 Actor 2 # ID Key: Distributed Storage/ EV 19 ? 6 Service Provider DR Removed Interfaces: 7 (meter doesn’t get market signals), 8 (SP talks to devices through ESI), 12 (no grid op cnx to HAN device), 14 (not sure on this one), 17 (same as 18), 20-21 (meter doesn’t talk to devices, but for AMI case ESI can be put in meter)

I2G Demand Response Use Cases: Actors and Logical Interfaces Market and Aggregator Operations Grid Operations Distribution Management 13 3 10 & 11 Customer Gateway/ Facility ESI 14 Aggregator 4&5 4, 7 & 11 DR Resource Meters or Smart Meters 17 16 1 2 20 Distributed Generation 6 & 7 23 19 Industrial EMS Wholesale/ Retail Market Industrial Central Generation 22 24 DR 25 I2G Demand Response Use Cases: Actors and Logical Interfaces Communications Association / Connector Logical Interfaces Actor 1 Actor 2 # ID Key: ESI: Energy Services Interface EMS: Energy Management System DR: Demand Response

I2G Logical Communications Architecture Market and Aggregator Operations Distribution Grid Operations Wholesale/ Retail Market Aggregator Distribution Management Customer Gateway/ Facility ESI DR Resource Industrial EMS Distributed Generation I2G Logical Communications Architecture DR Industrial Central Generation ESI: Energy Services Interface EMS: Energy Management System DR: Demand Response Meters or Smart Meters Communications domain Key: 5