| 1 |
<pre>Internet Engineering Task Force (IETF) B. Schoening |
| 2 |
Request for Comments: 7603 Independent Consultant |
| 3 |
Category: Standards Track M. Chandramouli |
| 4 |
ISSN: 2070-1721 Cisco Systems, Inc. |
| 5 |
B. Nordman |
| 6 |
Lawrence Berkeley National Lab |
| 7 |
August 2015 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Energy Management (EMAN) Applicability Statement</span> |
| 11 |
|
| 12 |
Abstract |
| 13 |
|
| 14 |
The objective of Energy Management (EMAN) is to provide an energy |
| 15 |
management framework for networked devices. This document presents |
| 16 |
the applicability of the EMAN information model in a variety of |
| 17 |
scenarios with cases and target devices. These use cases are useful |
| 18 |
for identifying requirements for the framework and MIBs. Further, we |
| 19 |
describe the relationship of the EMAN framework to other relevant |
| 20 |
energy monitoring standards and architectures. |
| 21 |
|
| 22 |
Status of This Memo |
| 23 |
|
| 24 |
This is an Internet Standards Track document. |
| 25 |
|
| 26 |
This document is a product of the Internet Engineering Task Force |
| 27 |
(IETF). It represents the consensus of the IETF community. It has |
| 28 |
received public review and has been approved for publication by the |
| 29 |
Internet Engineering Steering Group (IESG). Further information on |
| 30 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 31 |
|
| 32 |
Information about the current status of this document, any errata, |
| 33 |
and how to provide feedback on it may be obtained at |
| 34 |
<a href="http://www.rfc-editor.org/info/rfc7603">http://www.rfc-editor.org/info/rfc7603</a>. |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Schoening, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2015 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
Table of Contents |
| 73 |
|
| 74 |
<a href="#section-1">1</a>. Introduction ................................................. <a href="#page-3">3</a> |
| 75 |
<a href="#section-1.1">1.1</a>. Energy Management Overview ............................... <a href="#page-4">4</a> |
| 76 |
<a href="#section-1.2">1.2</a>. EMAN Document Overview ................................... <a href="#page-4">4</a> |
| 77 |
<a href="#section-1.3">1.3</a>. Energy Measurement ....................................... <a href="#page-5">5</a> |
| 78 |
<a href="#section-1.4">1.4</a>. Energy Management ........................................ <a href="#page-5">5</a> |
| 79 |
<a href="#section-1.5">1.5</a>. EMAN Framework Application ............................... <a href="#page-6">6</a> |
| 80 |
<a href="#section-2">2</a>. Scenarios and Target Devices ................................. <a href="#page-6">6</a> |
| 81 |
<a href="#section-2.1">2.1</a>. Network Infrastructure Energy Objects .................... <a href="#page-6">6</a> |
| 82 |
<a href="#section-2.2">2.2</a>. Devices Powered and Connected by a Network Device ........ <a href="#page-7">7</a> |
| 83 |
<a href="#section-2.3">2.3</a>. Devices Connected to a Network ........................... <a href="#page-8">8</a> |
| 84 |
<a href="#section-2.4">2.4</a>. Power Meters ............................................. <a href="#page-9">9</a> |
| 85 |
<a href="#section-2.5">2.5</a>. Mid-level Managers ...................................... <a href="#page-10">10</a> |
| 86 |
<a href="#section-2.6">2.6</a>. Non-residential Building System Gateways ................ <a href="#page-10">10</a> |
| 87 |
<a href="#section-2.7">2.7</a>. Home Energy Gateways .................................... <a href="#page-11">11</a> |
| 88 |
<a href="#section-2.8">2.8</a>. Data Center Devices ..................................... <a href="#page-12">12</a> |
| 89 |
<a href="#section-2.9">2.9</a>. Energy Storage Devices .................................. <a href="#page-13">13</a> |
| 90 |
<a href="#section-2.10">2.10</a>. Industrial Automation Networks ......................... <a href="#page-14">14</a> |
| 91 |
<a href="#section-2.11">2.11</a>. Printers ............................................... <a href="#page-14">14</a> |
| 92 |
<a href="#section-2.12">2.12</a>. Demand Response ........................................ <a href="#page-15">15</a> |
| 93 |
<a href="#section-3">3</a>. Use Case Patterns ........................................... <a href="#page-16">16</a> |
| 94 |
<a href="#section-3.1">3.1</a>. Metering ................................................ <a href="#page-16">16</a> |
| 95 |
<a href="#section-3.2">3.2</a>. Metering and Control .................................... <a href="#page-16">16</a> |
| 96 |
<a href="#section-3.3">3.3</a>. Power Supply, Metering and Control ...................... <a href="#page-16">16</a> |
| 97 |
<a href="#section-3.4">3.4</a>. Multiple Power Sources .................................. <a href="#page-16">16</a> |
| 98 |
<a href="#section-4">4</a>. Relationship of EMAN to Other Standards ..................... <a href="#page-17">17</a> |
| 99 |
<a href="#section-4.1">4.1</a>. Data Model and Reporting ................................ <a href="#page-17">17</a> |
| 100 |
<a href="#section-4.1.1">4.1.1</a>. IEC - CIM........................................ <a href="#page-17">17</a> |
| 101 |
<a href="#section-4.1.2">4.1.2</a>. DMTF............................................. <a href="#page-17">17</a> |
| 102 |
<a href="#section-4.1.3">4.1.3</a>. ODVA............................................. <a href="#page-19">19</a> |
| 103 |
<a href="#section-4.1.4">4.1.4</a>. Ecma SDC......................................... <a href="#page-19">19</a> |
| 104 |
<a href="#section-4.1.5">4.1.5</a>. PWG.............................................. <a href="#page-19">19</a> |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Schoening, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 111 |
|
| 112 |
|
| 113 |
<a href="#section-4.1.6">4.1.6</a>. ASHRAE........................................... <a href="#page-20">20</a> |
| 114 |
<a href="#section-4.1.7">4.1.7</a>. ANSI/CEA......................................... <a href="#page-21">21</a> |
| 115 |
<a href="#section-4.1.8">4.1.8</a>. ZigBee........................................... <a href="#page-21">21</a> |
| 116 |
<a href="#section-4.2">4.2</a>. Measurement ............................................. <a href="#page-22">22</a> |
| 117 |
<a href="#section-4.2.1">4.2.1</a>. ANSI C12......................................... <a href="#page-22">22</a> |
| 118 |
<a href="#section-4.2.2">4.2.2</a>. IEC 62301........................................ <a href="#page-22">22</a> |
| 119 |
<a href="#section-4.3">4.3</a>. Other ................................................... <a href="#page-22">22</a> |
| 120 |
<a href="#section-4.3.1">4.3.1</a>. ISO.............................................. <a href="#page-22">22</a> |
| 121 |
<a href="#section-4.3.2">4.3.2</a>. Energy Star...................................... <a href="#page-23">23</a> |
| 122 |
<a href="#section-4.3.3">4.3.3</a>. Smart Grid....................................... <a href="#page-23">23</a> |
| 123 |
<a href="#section-5">5</a>. Limitations ................................................. <a href="#page-24">24</a> |
| 124 |
<a href="#section-6">6</a>. Security Considerations ..................................... <a href="#page-24">24</a> |
| 125 |
<a href="#section-7">7</a>. References .................................................. <a href="#page-25">25</a> |
| 126 |
<a href="#section-7.1">7.1</a>. Normative References .................................... <a href="#page-25">25</a> |
| 127 |
<a href="#section-7.2">7.2</a>. Informative References .................................. <a href="#page-25">25</a> |
| 128 |
Acknowledgements ............................................... <a href="#page-27">27</a> |
| 129 |
Authors' Addresses ............................................. <a href="#page-28">28</a> |
| 130 |
|
| 131 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 132 |
|
| 133 |
The focus of the Energy Management (EMAN) framework is energy |
| 134 |
monitoring and management of energy objects [<a href="./rfc7326" title=""Energy Management Framework"">RFC7326</a>]. The scope of |
| 135 |
devices considered are network equipment and their components, and |
| 136 |
devices connected directly or indirectly to the network. The EMAN |
| 137 |
framework enables monitoring of heterogeneous devices to report their |
| 138 |
energy consumption and, if permissible, control. There are multiple |
| 139 |
scenarios where this is desirable, particularly considering the |
| 140 |
increased importance of limiting consumption of finite energy |
| 141 |
resources and reducing operational expenses. |
| 142 |
|
| 143 |
The EMAN framework [<a href="./rfc7326" title=""Energy Management Framework"">RFC7326</a>] describes how energy information can be |
| 144 |
retrieved from IP-enabled devices using Simple Network Management |
| 145 |
Protocol (SNMP), specifically, Management Information Base (MIB) |
| 146 |
modules for SNMP. |
| 147 |
|
| 148 |
This document describes typical applications of the EMAN framework as |
| 149 |
well as its opportunities and limitations. It also reviews other |
| 150 |
standards that are similar in part to EMAN but address different |
| 151 |
domains, describing how those other standards relate to the EMAN |
| 152 |
framework. |
| 153 |
|
| 154 |
The rest of the document is organized as follows. <a href="#section-2">Section 2</a> contains |
| 155 |
a list of use cases or network scenarios that EMAN addresses. |
| 156 |
<a href="#section-3">Section 3</a> contains an abstraction of the use case scenarios to |
| 157 |
distinct patterns. <a href="#section-4">Section 4</a> deals with other standards related and |
| 158 |
applicable to EMAN. |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Schoening, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Energy Management Overview</span> |
| 170 |
|
| 171 |
EMAN addresses the electrical energy consumed by devices connected to |
| 172 |
a network. A first step to increase the energy efficiency in |
| 173 |
networks and the devices attached to the network is to enable energy |
| 174 |
objects to report their energy usage over time. The EMAN framework |
| 175 |
addresses this problem with an information model for electrical |
| 176 |
equipment: energy object identification, energy object context, power |
| 177 |
measurement, and power characteristics. |
| 178 |
|
| 179 |
The EMAN framework defines SNMP MIB modules based on the information |
| 180 |
model. By implementing these SNMP MIB modules, an energy object can |
| 181 |
report its energy consumption according to the information model. |
| 182 |
Based on the information model, the MIB documents specify SNMP MIB |
| 183 |
modules, but it is equally possible to use other mechanisms such as |
| 184 |
YANG module, Network Conference Protocol (NETCONF), etc. |
| 185 |
|
| 186 |
In that context, it is important to distinguish energy objects that |
| 187 |
can only report their own energy usage from devices that can also |
| 188 |
collect and aggregate energy usage of other energy objects. |
| 189 |
|
| 190 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. EMAN Document Overview</span> |
| 191 |
|
| 192 |
The EMAN work consists of the following Standard Track and |
| 193 |
Informational documents in the area of energy management. |
| 194 |
|
| 195 |
Applicability Statement (this document) |
| 196 |
|
| 197 |
Requirements [<a href="./rfc6988" title=""Requirements for Energy Management"">RFC6988</a>]: This document presents requirements of |
| 198 |
energy management and the scope of the devices considered. |
| 199 |
|
| 200 |
Framework [<a href="./rfc7326" title=""Energy Management Framework"">RFC7326</a>]: This document defines a framework for |
| 201 |
providing energy management for devices within or connected to |
| 202 |
communication networks and lists the definitions for the common |
| 203 |
terms used in these documents. |
| 204 |
|
| 205 |
Energy Object Context MIB [<a href="./rfc7461" title=""Energy Object Context MIB"">RFC7461</a>]: This document defines a MIB |
| 206 |
module that characterizes a device's identity, context, and |
| 207 |
relationships to other entities. |
| 208 |
|
| 209 |
Monitoring and Control MIB [<a href="./rfc7460" title=""Monitoring and Control MIB for Power and Energy"">RFC7460</a>]: This document defines a MIB |
| 210 |
module for monitoring the power and energy consumption of a |
| 211 |
device. |
| 212 |
|
| 213 |
The MIB module contains an optional module for metrics |
| 214 |
associated with power characteristics. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Schoening, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 223 |
|
| 224 |
|
| 225 |
Battery MIB [<a href="./rfc7577" title=""Definition of Managed Objects for Battery Monitoring"">RFC7577</a>]: This document defines a MIB module for |
| 226 |
monitoring characteristics of an internal battery. |
| 227 |
|
| 228 |
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Energy Measurement</span> |
| 229 |
|
| 230 |
It is increasingly common for today's smart devices to measure and |
| 231 |
report their own energy consumption. Intelligent power strips and |
| 232 |
some Power over Ethernet (PoE) switches can meter consumption of |
| 233 |
connected devices. However, when managed and reported through |
| 234 |
proprietary means, this information is difficult to view at the |
| 235 |
enterprise level. |
| 236 |
|
| 237 |
The primary goal of the EMAN information model is to enable reporting |
| 238 |
and management within a standard framework that is applicable to a |
| 239 |
wide variety of end devices, meters, and proxies. This enables a |
| 240 |
management system to know who's consuming what, when, and how by |
| 241 |
leveraging existing networks across various equipment in a unified |
| 242 |
and consistent manner. |
| 243 |
|
| 244 |
Because energy objects may both consume energy and provide energy to |
| 245 |
other devices, there are three types of energy measurement: energy |
| 246 |
input to a device, energy supplied to other devices, and net |
| 247 |
(resultant) energy consumed (the difference between energy input and |
| 248 |
supplied). |
| 249 |
|
| 250 |
<span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>. Energy Management</span> |
| 251 |
|
| 252 |
The EMAN framework provides mechanisms for energy control in addition |
| 253 |
to passive monitoring. There are many cases where active energy |
| 254 |
control of devices is desirable, for example, during low device |
| 255 |
utilization or peak electrical price periods. |
| 256 |
|
| 257 |
Energy control can be as simple as controlling on/off states. In |
| 258 |
many cases, however, energy control requires understanding the energy |
| 259 |
object context. For instance, during non-business hours in a |
| 260 |
commercial building, some phones must remain available in case of |
| 261 |
emergency, and office cooling is not usually turned off completely, |
| 262 |
but the comfort level is reduced. |
| 263 |
|
| 264 |
Energy object control therefore requires flexibility and support for |
| 265 |
different policies and mechanisms: from centralized management by an |
| 266 |
energy management system to autonomous control by individual devices |
| 267 |
and alignment with dynamic demand-response mechanisms. |
| 268 |
|
| 269 |
The power states specified in the EMAN framework can be used in |
| 270 |
demand-response scenarios. In response to time-of-day fluctuation of |
| 271 |
energy costs or grid power shortages, network devices can respond and |
| 272 |
reduce their energy consumption. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Schoening, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h3"><a class="selflink" id="section-1.5" href="#section-1.5">1.5</a>. EMAN Framework Application</span> |
| 282 |
|
| 283 |
A Network Management System (NMS) is an entity that requests |
| 284 |
information from compatible devices, typically using the SNMP |
| 285 |
protocol. An NMS may implement many network management functions, |
| 286 |
such as security or identity management. An NMS that deals |
| 287 |
exclusively with energy is called an Energy Management System (EnMS). |
| 288 |
It may be limited to monitoring energy use, or it may also implement |
| 289 |
control functions. An EnMS collects energy information for devices |
| 290 |
in the network. |
| 291 |
|
| 292 |
Energy management can be implemented by extending existing SNMP |
| 293 |
support with EMAN-specific MIBs. SNMP provides an industry-proven |
| 294 |
and well-known mechanism to discover, secure, measure, and control |
| 295 |
SNMP-enabled end devices. The EMAN framework provides an information |
| 296 |
and data model to unify access to a large range of devices. |
| 297 |
|
| 298 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Scenarios and Target Devices</span> |
| 299 |
|
| 300 |
This section presents energy management scenarios that the EMAN |
| 301 |
framework should solve. Each scenario lists target devices for which |
| 302 |
the energy management framework can be applied, how the reported-on |
| 303 |
devices are powered, and how the reporting or control is |
| 304 |
accomplished. While there is some overlap between some of the use |
| 305 |
cases, the use cases illustrate network scenarios that the EMAN |
| 306 |
framework supports. |
| 307 |
|
| 308 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Network Infrastructure Energy Objects</span> |
| 309 |
|
| 310 |
This scenario covers the key use case of network devices and their |
| 311 |
components. For a device aware of one or more components, our |
| 312 |
information model supports monitoring and control at the component |
| 313 |
level. Typically, the chassis draws power from one or more sources |
| 314 |
and feeds its internal components. It is highly desirable to have |
| 315 |
monitoring available for individual components, such as line cards, |
| 316 |
processors, disk drives, and peripherals such as USB devices. |
| 317 |
|
| 318 |
As an illustrative example, consider a switch with the following |
| 319 |
grouping of subentities for which energy management could be useful. |
| 320 |
|
| 321 |
o Physical view: chassis (or stack), line cards, and service |
| 322 |
modules of the switch. |
| 323 |
|
| 324 |
o Component view: CPU, Application-Specific Integrated Circuits |
| 325 |
(ASICs), fans, power supply, ports (single port and port |
| 326 |
groups), storage, and memory. |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Schoening, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 335 |
|
| 336 |
|
| 337 |
The ENTITY-MIB [<a href="./rfc6933" title=""Entity MIB (Version 4)"">RFC6933</a>] provides a containment model for uniquely |
| 338 |
identifying the physical subcomponents of network devices. The |
| 339 |
containment information identifies whether one Energy Object belongs |
| 340 |
to another Energy Object (e.g., a line-card Energy Object contained |
| 341 |
in a chassis Energy Object). The mapping table, |
| 342 |
entPhysicalContainsTable, has an index, entPhysicalChildIndex, and |
| 343 |
the table, entPhysicalTable, has a MIB object, |
| 344 |
entPhysicalContainedIn, that points to the containing entity. |
| 345 |
|
| 346 |
The essential properties of this use case are: |
| 347 |
|
| 348 |
o Target devices: network devices such as routers and switches, |
| 349 |
as well as their components. |
| 350 |
|
| 351 |
o How powered: typically by a Power Distribution Unit (PDU) on a |
| 352 |
rack or from a wall outlet. The components of a device are |
| 353 |
powered by the device chassis. |
| 354 |
|
| 355 |
o Reporting: Direct power measurement can be performed at a |
| 356 |
device level. Components can report their power consumption |
| 357 |
directly, or the chassis/device can report on behalf of some |
| 358 |
components. |
| 359 |
|
| 360 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Devices Powered and Connected by a Network Device</span> |
| 361 |
|
| 362 |
This scenario covers Power Sourcing Equipment (PSE) devices. A PSE |
| 363 |
device (e.g., a PoE switch) provides power to a Powered Device (PD) |
| 364 |
(e.g., a desktop phone) over a medium such as USB or Ethernet |
| 365 |
[<a href="./rfc3621" title=""Power Ethernet MIB"">RFC3621</a>]. For each port, the PSE can control the power supply |
| 366 |
(switching it on and off) and usually meter actual power provided. |
| 367 |
PDs obtain network connectivity as well as power over a single |
| 368 |
connection so the PSE can determine which device is associated with |
| 369 |
each port. |
| 370 |
|
| 371 |
PoE ports on a switch are commonly connected to devices such as IP |
| 372 |
phones, wireless access points, and IP cameras. The switch needs |
| 373 |
power for its internal use and to supply power to PoE ports. |
| 374 |
Monitoring the power consumption of the switch (supplying device) and |
| 375 |
the power consumption of the PoE endpoints (consuming devices) is a |
| 376 |
simple use case of this scenario. |
| 377 |
|
| 378 |
This scenario illustrates the relationships between entities. The |
| 379 |
PoE IP phone is powered by the switch. If there are many IP phones |
| 380 |
connected to the same switch, the power consumption of all the IP |
| 381 |
phones can be aggregated by the switch. |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Schoening, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 391 |
|
| 392 |
|
| 393 |
The essential properties of this use case are: |
| 394 |
|
| 395 |
Target devices: Power over Ethernet devices such as IP phones, |
| 396 |
wireless access points, and IP cameras. |
| 397 |
|
| 398 |
How powered: PoE devices are connected to the switch port that |
| 399 |
supplies power to those devices. |
| 400 |
|
| 401 |
Reporting: PoE device power consumption is measured and reported |
| 402 |
by the switch (PSE) that supplies power. In addition, some |
| 403 |
edge devices can support the EMAN framework. |
| 404 |
|
| 405 |
This use case can be divided into two subcases: |
| 406 |
|
| 407 |
a) The endpoint device supports the EMAN framework, in which case |
| 408 |
this device is an EMAN Energy Object by itself with its own |
| 409 |
Universally Unique Identifier (UUID). The device is |
| 410 |
responsible for its own power reporting and control. See the |
| 411 |
related scenario "Devices Connected to a Network" below. |
| 412 |
|
| 413 |
b) The endpoint device does not have EMAN capabilities, and the |
| 414 |
power measurement may not be able to be performed independently |
| 415 |
and is therefore only performed by the supplying device. This |
| 416 |
scenario is similar to the "Mid-level Manager" below. |
| 417 |
|
| 418 |
In subcase (a), note that two power usage reporting mechanisms for |
| 419 |
the same device are available: one performed by the PD itself and one |
| 420 |
performed by the PSE. Device-specific implementations will dictate |
| 421 |
which one to use. |
| 422 |
|
| 423 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Devices Connected to a Network</span> |
| 424 |
|
| 425 |
This use case covers the metering relationship between an energy |
| 426 |
object and the parent energy object to which it is connected, while |
| 427 |
receiving power from a different source. |
| 428 |
|
| 429 |
An example is a PC that has a network connection to a switch but |
| 430 |
draws power from a wall outlet. In this case, the PC can report |
| 431 |
power usage by itself, ideally through the EMAN framework. |
| 432 |
|
| 433 |
The wall outlet to which the PC is plugged in can be unmetered or |
| 434 |
metered, for example, by a Smart PDU. |
| 435 |
|
| 436 |
a) If metered, the PC has a powered-by relationship to the Smart |
| 437 |
PDU, and the Smart PDU acts as a "mid-level manager". |
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Schoening, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 447 |
|
| 448 |
|
| 449 |
b) If unmetered, or operating on batteries, the PC will report its |
| 450 |
own energy usage as any other Energy Object to the switch, and |
| 451 |
the switch may possibly provide aggregation. |
| 452 |
|
| 453 |
These two cases are not mutually exclusive. |
| 454 |
|
| 455 |
In terms of relationships between entities, the PC has a powered-by |
| 456 |
relationship to the PDU, and if the power consumption of the PC is |
| 457 |
metered by the PDU, then there is a metered-by relation between the |
| 458 |
PC and the PDU. |
| 459 |
|
| 460 |
The essential properties of this use case are: |
| 461 |
|
| 462 |
o Target devices: energy objects that have a network connection |
| 463 |
but receive power supply from another source. |
| 464 |
|
| 465 |
o How powered: endpoint devices (e.g., PCs) receive power supply |
| 466 |
from the wall outlet (unmetered), a PDU (metered), or can be |
| 467 |
powered autonomously (batteries). |
| 468 |
|
| 469 |
o Reporting: The power consumption can be reported via the EMAN |
| 470 |
framework |
| 471 |
- by the device directly, |
| 472 |
- by the switch with information provided to it by the device, |
| 473 |
or |
| 474 |
- by the PDU from which the device obtains its power. |
| 475 |
|
| 476 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Power Meters</span> |
| 477 |
|
| 478 |
Some electrical devices are not equipped with instrumentation to |
| 479 |
measure their own power and accumulated energy consumption. External |
| 480 |
meters can be used to measure the power consumption of such |
| 481 |
electrical devices as well as collections of devices. |
| 482 |
|
| 483 |
Three types of external metering are relevant to EMAN: PDUs, |
| 484 |
standalone meters, and utility meters. External meters can measure |
| 485 |
consumption of a single device or a set of devices. |
| 486 |
|
| 487 |
Power Distribution Units (PDUs) can have built-in meters for each |
| 488 |
socket and can measure the power supplied to each device in an |
| 489 |
equipment rack. PDUs typically have remote management capabilities |
| 490 |
that can report and possibly control the power supply of each outlet. |
| 491 |
|
| 492 |
Standalone meters can be placed anywhere in a power distribution tree |
| 493 |
and may measure all or part of the total. Utility meters monitor and |
| 494 |
report accumulated power consumption of the entire building. There |
| 495 |
can be submeters to measure the power consumption of a portion of the |
| 496 |
building. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Schoening, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 503 |
|
| 504 |
|
| 505 |
The essential properties of this use case are: |
| 506 |
|
| 507 |
o Target devices: PDUs and meters. |
| 508 |
|
| 509 |
o How powered: from traditional mains power but supplied through |
| 510 |
a PDU or meter (where "mains power" is the standard AC power |
| 511 |
drawn from the wall outlet). |
| 512 |
|
| 513 |
o Reporting: PDUs report power consumption of downstream devices, |
| 514 |
usually a single device per outlet. Meters may report for one |
| 515 |
or more devices and may require knowledge of the topology to |
| 516 |
associate meters with metered devices. |
| 517 |
|
| 518 |
Meters have metered-by relationships with devices and may have |
| 519 |
aggregation relationships between the meters and the devices for |
| 520 |
which power consumption is accumulated and reported by the meter. |
| 521 |
|
| 522 |
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Mid-level Managers</span> |
| 523 |
|
| 524 |
This use case covers aggregation of energy management data at "mid- |
| 525 |
level managers" that can provide energy management functions for |
| 526 |
themselves and associated devices. |
| 527 |
|
| 528 |
A switch can provide energy management functions for all devices |
| 529 |
connected to its ports whether or not these devices are powered by |
| 530 |
the switch or whether the switch provides immediate network |
| 531 |
connectivity to the devices. Such a switch is a mid-level manager, |
| 532 |
offering aggregation of power consumption data for other devices. |
| 533 |
Devices report their EMAN data to the switch and the switch |
| 534 |
aggregates the data for further reporting. |
| 535 |
|
| 536 |
The essential properties of this use case: |
| 537 |
|
| 538 |
o Target devices: devices that can perform aggregation; commonly |
| 539 |
a switch or a proxy. |
| 540 |
|
| 541 |
o How powered: mid-level managers are commonly powered by a PDU |
| 542 |
or from a wall outlet but can be powered by any method. |
| 543 |
|
| 544 |
o Reporting: The mid-level manager aggregates the energy data and |
| 545 |
reports that data to an EnMS or higher mid-level manager. |
| 546 |
|
| 547 |
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Non-residential Building System Gateways</span> |
| 548 |
|
| 549 |
This use case describes energy management of non-residential |
| 550 |
buildings. Building Management Systems (BMS) have been in place for |
| 551 |
many years using legacy protocols not based on IP. In these |
| 552 |
buildings, a gateway can provide a proxy function between IP networks |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Schoening, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 559 |
|
| 560 |
|
| 561 |
and legacy building automation protocols. The gateway provides an |
| 562 |
interface between the EMAN framework and relevant building management |
| 563 |
protocols. |
| 564 |
|
| 565 |
Due to the potential energy savings, energy management of buildings |
| 566 |
has received significant attention. There are gateway network |
| 567 |
elements to manage the multiple components of a building energy |
| 568 |
management system such as Heating, Ventilation, and Air Conditioning |
| 569 |
(HVAC), lighting, electrical, fire and emergency systems, elevators, |
| 570 |
etc. The gateway device uses legacy building protocols to |
| 571 |
communicate with those devices, collects their energy usage, and |
| 572 |
reports the results. |
| 573 |
|
| 574 |
The gateway performs protocol conversion and communicates via |
| 575 |
RS-232/RS-485 interfaces, Ethernet interfaces, and protocols specific |
| 576 |
to building management such as BACnet (a protocol for building |
| 577 |
automation and control networks) [<a href="#ref-BACnet" title=""BACnet Webpage"">BACnet</a>], Modbus [<a href="#ref-MODBUS" title=""MODBUS Application Protocol Specification"">MODBUS</a>], or ZigBee |
| 578 |
[<a href="#ref-ZIGBEE" title=""The ZigBee Alliance"">ZIGBEE</a>]. |
| 579 |
|
| 580 |
The essential properties of this use case are: |
| 581 |
|
| 582 |
o Target devices: building energy management devices -- HVAC |
| 583 |
systems, lighting, electrical, and fire and emergency systems. |
| 584 |
|
| 585 |
o How powered: any method. |
| 586 |
|
| 587 |
o Reporting: The gateway collects energy consumption of non-IP |
| 588 |
systems and communicates the data via the EMAN framework. |
| 589 |
|
| 590 |
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Home Energy Gateways</span> |
| 591 |
|
| 592 |
This use case describes the scenario of energy management of a home. |
| 593 |
The home energy gateway is another example of a proxy that interfaces |
| 594 |
with electrical appliances and other devices in a home. This gateway |
| 595 |
can monitor and manage electrical equipment (e.g., refrigerator, |
| 596 |
heating/cooling, or washing machine) using one of the many protocols |
| 597 |
that are being developed for residential devices. |
| 598 |
|
| 599 |
Beyond simply metering, it's possible to implement energy saving |
| 600 |
policies based on time of day, occupancy, or energy pricing from the |
| 601 |
utility grid. The EMAN information model can be applied to the |
| 602 |
energy management of a home. |
| 603 |
|
| 604 |
The essential properties of this use case are: |
| 605 |
|
| 606 |
o Target devices: home energy gateway and smart meters in a home. |
| 607 |
|
| 608 |
o How powered: any method. |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Schoening, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 615 |
|
| 616 |
|
| 617 |
o Reporting: The home energy gateway can collect power |
| 618 |
consumption of device in a home and possibly report the meter |
| 619 |
reading to the utility. |
| 620 |
|
| 621 |
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Data Center Devices</span> |
| 622 |
|
| 623 |
This use case describes energy management of a data center. Energy |
| 624 |
efficiency of data centers has become a fundamental challenge of data |
| 625 |
center operation, as data centers are big energy consumers and have |
| 626 |
an expensive infrastructure. The equipment generates heat, and heat |
| 627 |
needs to be evacuated through an HVAC system. |
| 628 |
|
| 629 |
A typical data center network consists of a hierarchy of electrical |
| 630 |
energy objects. At the bottom of the network hierarchy are servers |
| 631 |
mounted on a rack; these are connected to top-of-the-rack switches, |
| 632 |
which in turn are connected to aggregation switches and then to core |
| 633 |
switches. Power consumption of all network elements, servers, and |
| 634 |
storage devices in the data center should be measured. Energy |
| 635 |
management can be implemented on different aggregation levels, i.e., |
| 636 |
at the network level, the Power Distribution Unit (PDU) level, and/or |
| 637 |
the server level. |
| 638 |
|
| 639 |
Beyond the network devices, storage devices, and servers, data |
| 640 |
centers contain Uninterruptable Power Systems (UPSs) to provide back- |
| 641 |
up power for the facility in the event of a power outage. A UPS can |
| 642 |
provide backup power for many devices in a data center for a finite |
| 643 |
period of time. Energy monitoring of energy storage capacity is |
| 644 |
vital from a data center network operations point of view. |
| 645 |
Presently, the UPS MIB can be useful in monitoring the battery |
| 646 |
capacity, the input load to the UPS, and the output load from the |
| 647 |
UPS. Currently, there is no link between the UPS MIB and the ENTITY |
| 648 |
MIB. |
| 649 |
|
| 650 |
In addition to monitoring the power consumption of a data center, |
| 651 |
additional power characteristics should be monitored. Some of these |
| 652 |
are dynamic variations in the input power supply from the grid, |
| 653 |
referred to as power quality metrics. It can also be useful to |
| 654 |
monitor how efficiently the devices utilize power. |
| 655 |
|
| 656 |
Nameplate capacity of the data center can be estimated from the |
| 657 |
nameplate ratings (which indicate the maximum possible power draw) of |
| 658 |
IT equipment at a site. |
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Schoening, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 671 |
|
| 672 |
|
| 673 |
The essential properties of this use case are: |
| 674 |
|
| 675 |
o Target devices: IT devices in a data center, such as network |
| 676 |
equipment, servers, and storage devices, as well as power and |
| 677 |
cooling infrastructure. |
| 678 |
|
| 679 |
o How powered: any method, but commonly by one or more PDUs. |
| 680 |
|
| 681 |
o Reporting: Devices may report on their own behalf or for other |
| 682 |
connected devices as described in other use cases. |
| 683 |
|
| 684 |
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Energy Storage Devices</span> |
| 685 |
|
| 686 |
Energy storage devices can have two different roles: one type whose |
| 687 |
primary function is to provide power to another device (e.g., a UPS) |
| 688 |
and one type with a different primary function but that has energy |
| 689 |
storage as a component (e.g., a notebook). This use case covers |
| 690 |
both. |
| 691 |
|
| 692 |
The energy storage can be a conventional battery or any other means |
| 693 |
to store electricity, such as a hydrogen cell. |
| 694 |
|
| 695 |
An internal battery can be a back-up or an alternative source of |
| 696 |
power to mains power. As batteries have a finite capacity and |
| 697 |
lifetime, means for reporting the actual charge, age, and state of a |
| 698 |
battery are required. An internal battery can be viewed as a |
| 699 |
component of a device and can be contained within the device from an |
| 700 |
ENTITY-MIB perspective. |
| 701 |
|
| 702 |
Battery systems are often used in remote locations such as mobile |
| 703 |
telecom towers. For continuous operation, it is important to monitor |
| 704 |
the remaining battery life and raise an alarm when this falls below a |
| 705 |
threshold. |
| 706 |
|
| 707 |
The essential properties of this use case are: |
| 708 |
|
| 709 |
o Target devices: devices that have an internal battery or |
| 710 |
external storage. |
| 711 |
|
| 712 |
o How powered: from batteries or other storage devices. |
| 713 |
|
| 714 |
o Reporting: The device reports on its power delivered and state. |
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Schoening, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Industrial Automation Networks</span> |
| 730 |
|
| 731 |
Energy consumption statistics in the industrial sector are |
| 732 |
staggering. The industrial sector alone consumes about half of the |
| 733 |
world's total delivered energy and is a significant user of |
| 734 |
electricity. Thus, the need for optimization of energy usage in this |
| 735 |
sector is natural. |
| 736 |
|
| 737 |
Industrial facilities consume energy in process loads and non-process |
| 738 |
loads. |
| 739 |
|
| 740 |
The essential properties of this use case are: |
| 741 |
|
| 742 |
o Target devices: devices used in an industrial sector. |
| 743 |
|
| 744 |
o How powered: any method. |
| 745 |
|
| 746 |
o Reporting: The Common Industrial Protocol (CIP) is commonly |
| 747 |
used for reporting energy for these devices. |
| 748 |
|
| 749 |
<span class="h3"><a class="selflink" id="section-2.11" href="#section-2.11">2.11</a>. Printers</span> |
| 750 |
|
| 751 |
This use case describes the scenario of energy monitoring and |
| 752 |
management of printers. Printers in this use case stand in for all |
| 753 |
imaging equipment, including Multi-function Devices (MFDs), scanners, |
| 754 |
fax machines, and mailing machines. |
| 755 |
|
| 756 |
Energy use of printers has been a long-standing industry concern, and |
| 757 |
sophisticated power management is common. Printers often use a |
| 758 |
variety of low-power modes, particularly for managing energy- |
| 759 |
intensive thermo-mechanical components. Printers also have long made |
| 760 |
extensive use of SNMP for end-user system interaction and for |
| 761 |
management generally, with cross-vendor management systems able to |
| 762 |
manage fleets of printers in enterprises. Power consumption during |
| 763 |
active modes can vary widely, with high peak usage levels. |
| 764 |
|
| 765 |
Printers can expose detailed power state information, distinct from |
| 766 |
operational state information, with some printers reporting |
| 767 |
transition states between stable long-term states. Many also support |
| 768 |
active setting of power states and policies, such as delay times, |
| 769 |
when inactivity automatically transitions the device to a lower power |
| 770 |
mode. Other features include reporting on components, counters for |
| 771 |
state transitions, typical power levels by state, scheduling, and |
| 772 |
events/alarms. |
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Schoening, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 783 |
|
| 784 |
|
| 785 |
Some large printers also have a "Digital Front End", which is a |
| 786 |
computer that performs functions on behalf of the physical imaging |
| 787 |
system. These typically have their own presence on the network and |
| 788 |
are sometimes separately powered. |
| 789 |
|
| 790 |
There are some unique characteristics of printers from the point of |
| 791 |
view energy management. While the printer is not in use, there are |
| 792 |
timer-based low power states, which consume little power. On the |
| 793 |
other hand, while the printer is printing or copying, the cylinder is |
| 794 |
heated so that power consumption is quite high but only for a short |
| 795 |
period of time. Given this work load, periodic polling of power |
| 796 |
levels alone would not suffice. |
| 797 |
|
| 798 |
The essential properties of this use case are: |
| 799 |
|
| 800 |
o Target devices: all imaging equipment. |
| 801 |
|
| 802 |
o How powered: typically, AC from a wall outlet. |
| 803 |
|
| 804 |
o Reporting: The devices report for themselves. |
| 805 |
|
| 806 |
<span class="h3"><a class="selflink" id="section-2.12" href="#section-2.12">2.12</a>. Demand Response</span> |
| 807 |
|
| 808 |
The theme of demand response from a utility grid spans across several |
| 809 |
use cases. In some situations, in response to time-of-day |
| 810 |
fluctuation of energy costs or sudden energy shortages due power |
| 811 |
outages, it may be important to respond and reduce the energy |
| 812 |
consumption of the network. |
| 813 |
|
| 814 |
From the EMAN use case perspective, the demand-response scenario can |
| 815 |
apply to a data center, building, or home. Real-time energy |
| 816 |
monitoring is usually a prerequisite so that during a potential |
| 817 |
energy shortfall the EnMS can provide an active response. The EnMS |
| 818 |
could shut down selected devices that are considered lower priority |
| 819 |
or uniformly reduce the power supplied to a class of devices. For |
| 820 |
multisite data centers, it may be possible to formulate policies such |
| 821 |
as the follow-the-sun type of approach by scheduling the mobility of |
| 822 |
Virtual Machines (VMs) across data centers in different geographical |
| 823 |
locations. |
| 824 |
|
| 825 |
The essential properties of this use case are: |
| 826 |
|
| 827 |
o Target devices: any device. |
| 828 |
|
| 829 |
o How powered: traditional mains AC power. |
| 830 |
|
| 831 |
o Reporting: Devices report in real time. |
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Schoening, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 839 |
|
| 840 |
|
| 841 |
o Control: demand response based upon policy or priority. |
| 842 |
|
| 843 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Use Case Patterns</span> |
| 844 |
|
| 845 |
The use cases presented above can be abstracted to the following |
| 846 |
broad patterns for energy objects. |
| 847 |
|
| 848 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Metering</span> |
| 849 |
|
| 850 |
- Energy objects that have the capability for internal metering |
| 851 |
|
| 852 |
- Energy objects that are metered by an external device |
| 853 |
|
| 854 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Metering and Control</span> |
| 855 |
|
| 856 |
- Energy objects that do not supply power but can perform power |
| 857 |
metering for other devices |
| 858 |
|
| 859 |
- Energy objects that do not supply power but can perform both |
| 860 |
metering and control for other devices |
| 861 |
|
| 862 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Power Supply, Metering, and Control</span> |
| 863 |
|
| 864 |
- Energy objects that supply power for other devices but do not |
| 865 |
perform power metering for those devices |
| 866 |
|
| 867 |
- Energy objects that supply power for other devices and also |
| 868 |
perform power metering |
| 869 |
|
| 870 |
- Energy objects that supply power for other devices and also |
| 871 |
perform power metering and control for other devices |
| 872 |
|
| 873 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Multiple Power Sources</span> |
| 874 |
|
| 875 |
- Energy objects that have multiple power sources, with metering and |
| 876 |
control performed by the same power source |
| 877 |
|
| 878 |
- Energy objects that have multiple power sources supplying power to |
| 879 |
the device with metering performed by one or more sources and |
| 880 |
control performed by another source |
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Schoening, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Relationship of EMAN to Other Standards</span> |
| 898 |
|
| 899 |
The EMAN framework is tied to other standards and efforts that |
| 900 |
address energy monitoring and control. EMAN leverages existing |
| 901 |
standards when possible, and it helps enable adjacent technologies |
| 902 |
such as Smart Grid. |
| 903 |
|
| 904 |
The standards most relevant and applicable to EMAN are listed below |
| 905 |
with a brief description of their objectives, the current state, and |
| 906 |
how that standard relates to EMAN. |
| 907 |
|
| 908 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Data Model and Reporting</span> |
| 909 |
|
| 910 |
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. IEC - CIM</span> |
| 911 |
|
| 912 |
The International Electrotechnical Commission (IEC) has developed a |
| 913 |
broad set of standards for power management. Among these, the most |
| 914 |
applicable to EMAN is IEC 61850, a standard for the design of |
| 915 |
electric utility automation. The abstract data model defined in |
| 916 |
61850 is built upon and extends the Common Information Model (CIM). |
| 917 |
The complete 61850 CIM model includes over a hundred object classes |
| 918 |
and is widely used by utilities worldwide. |
| 919 |
|
| 920 |
This set of standards were originally conceived to automate control |
| 921 |
of a substation (a facility that transfers electricity from the |
| 922 |
transmission to the distribution system). However, the extensive |
| 923 |
data model has been widely used in other domains, including Energy |
| 924 |
Management Systems (EnMS). |
| 925 |
|
| 926 |
IEC TC57 WG19 is an ongoing working group with the objective to |
| 927 |
harmonize the CIM data model and 61850 standards. |
| 928 |
|
| 929 |
Several concepts from IEC Standards have been reused in the EMAN |
| 930 |
documents. In particular, AC Power Quality measurements have been |
| 931 |
reused from IEC 61850-7-4. The concept of Accuracy Classes for |
| 932 |
measurement of power and energy has been adapted from ANSI C12.20 and |
| 933 |
IEC standards 62053-21 and 62053-22. |
| 934 |
|
| 935 |
<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>. DMTF</span> |
| 936 |
|
| 937 |
The Distributed Management Task Force (DMTF) has defined a Power |
| 938 |
State Management profile [<a href="#ref-DMTF-DSP1027">DMTF-DSP1027</a>] for managing computer systems |
| 939 |
using the DMTF's Common Information Model (CIM). These |
| 940 |
specifications provide physical, logical, and virtual system |
| 941 |
management requirements for power-state control services. The DMTF |
| 942 |
standard does not include energy monitoring. |
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Schoening, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 951 |
|
| 952 |
|
| 953 |
The Power State Management profile is used to describe and manage the |
| 954 |
Power State of computer systems. This includes controlling the Power |
| 955 |
State of an entity for entering sleep mode, awakening, and rebooting. |
| 956 |
The EMAN framework references the DMTF Power Profile and Power State |
| 957 |
Set. |
| 958 |
|
| 959 |
<span class="h5"><a class="selflink" id="section-4.1.2.1" href="#section-4.1.2.1">4.1.2.1</a>. Common Information Model Profiles</span> |
| 960 |
|
| 961 |
The DMTF uses CIM-based 'Profiles' to represent and manage power |
| 962 |
utilization and configuration of managed elements (note that this is |
| 963 |
not the 61850 CIM). Key profiles for energy management are 'Power |
| 964 |
Supply' (DSP 1015), 'Power State' (DSP 1027), and 'Power Utilization |
| 965 |
Management' (DSP 1085). These profiles define many features for the |
| 966 |
monitoring and configuration of a Power Managed Element's static and |
| 967 |
dynamic power saving modes, power allocation limits, and power |
| 968 |
states. |
| 969 |
|
| 970 |
Reduced power modes can be established as static or dynamic. Static |
| 971 |
modes are fixed policies that limit power use or utilization. |
| 972 |
Dynamic power saving modes rely upon internal feedback to control |
| 973 |
power consumption. |
| 974 |
|
| 975 |
Power states are eight named operational and non-operational levels. |
| 976 |
These are On, Sleep-Light, Sleep-Deep, Hibernate, Off-Soft, and Off- |
| 977 |
Hard. Power change capabilities provide immediate, timed interval, |
| 978 |
and graceful transitions between on, off, and reset power states. |
| 979 |
Table 3 of the Power State Profile defines the correspondence between |
| 980 |
the Advanced Configuration and Power Interface [<a href="#ref-ACPI" title=""Advanced Configuration and Power Interface Specification"">ACPI</a>] and DMTF power |
| 981 |
state models, although it is not necessary for a managed element to |
| 982 |
support ACPI. Optionally, a TransitioningToPowerState property can |
| 983 |
represent power state transitions in progress. |
| 984 |
|
| 985 |
<span class="h5"><a class="selflink" id="section-4.1.2.2" href="#section-4.1.2.2">4.1.2.2</a>. DASH</span> |
| 986 |
|
| 987 |
DMTF Desktop and Mobile Architecture for System Hardware [<a href="#ref-DASH" title=""Desktop and Mobile Architecture for System Hardware"">DASH</a>] |
| 988 |
addresses managing heterogeneous desktop and mobile systems |
| 989 |
(including power) via in-band and out-of-band communications. DASH |
| 990 |
uses the DMTF's Web Services for Management (WS-Management) and CIM |
| 991 |
data model to manage and control resources such as power, CPU, etc. |
| 992 |
|
| 993 |
Both in-service and out-of-service systems can be managed with the |
| 994 |
DASH specification in a fully secured remote environment. Full power |
| 995 |
life-cycle management is possible using out-of-band management. |
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Schoening, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h4"><a class="selflink" id="section-4.1.3" href="#section-4.1.3">4.1.3</a>. ODVA</span> |
| 1010 |
|
| 1011 |
The Open DeviceNet Vendors Association (ODVA) is an association for |
| 1012 |
industrial automation companies that defines the Common Industrial |
| 1013 |
Protocol (CIP). Within ODVA, there is a special interest group |
| 1014 |
focused on energy and standardization and interoperability of energy- |
| 1015 |
aware devices. |
| 1016 |
|
| 1017 |
The ODVA is developing an energy management framework for the |
| 1018 |
industrial sector. There are synergies and similar concepts between |
| 1019 |
the ODVA and EMAN approaches to energy monitoring and management. |
| 1020 |
|
| 1021 |
ODVA defines a three-part approach towards energy management: |
| 1022 |
awareness of energy usage, energy efficiency, and the exchange of |
| 1023 |
energy with a utility or others. Energy monitoring and management |
| 1024 |
promote efficient consumption and enable automating actions that |
| 1025 |
reduce energy consumption. |
| 1026 |
|
| 1027 |
The foundation of the approach is the information and communication |
| 1028 |
model for entities. An entity is a network-connected, energy-aware |
| 1029 |
device that has the ability to either measure or derive its energy |
| 1030 |
usage based on its native consumption or generation of energy, or |
| 1031 |
report a nominal or static energy value. |
| 1032 |
|
| 1033 |
<span class="h4"><a class="selflink" id="section-4.1.4" href="#section-4.1.4">4.1.4</a>. Ecma SDC</span> |
| 1034 |
|
| 1035 |
The Ecma International standard on Smart Data Centre [<a href="#ref-Ecma-SDC" title=""Smart Data Centre Resource Monitoring and Control"">Ecma-SDC</a>] |
| 1036 |
defines semantics for management of entities in a data center such as |
| 1037 |
servers, storage, and network equipment. It covers energy as one of |
| 1038 |
many functional resources or attributes of systems for monitoring and |
| 1039 |
control. It only defines messages and properties and does not |
| 1040 |
reference any specific protocol. Its goal is to enable |
| 1041 |
interoperability of such protocols as SNMP, BACnet, and HTTP by |
| 1042 |
ensuring a common semantic model across them. Four power states are |
| 1043 |
defined, Off, Sleep, Idle, and Active. The standard does not include |
| 1044 |
actual energy or power measurements. |
| 1045 |
|
| 1046 |
When used with EMAN, the SDC standard will provide a thin abstraction |
| 1047 |
on top of the more detailed data model available in EMAN. |
| 1048 |
|
| 1049 |
<span class="h4"><a class="selflink" id="section-4.1.5" href="#section-4.1.5">4.1.5</a>. PWG</span> |
| 1050 |
|
| 1051 |
The IEEE Industry Standards and Technology Organization (ISTO) |
| 1052 |
Printer Working Group (PWG) defines open standards for printer- |
| 1053 |
related protocols for the benefit of printer manufacturers and |
| 1054 |
related software vendors. The Printer WG covers power monitoring and |
| 1055 |
management of network printers and imaging systems in the PWG Power |
| 1056 |
Management Model for Imaging Systems [<a href="#ref-PWG5106.4" title=""PWG Power Management Model for Imaging Systems 1.0"">PWG5106.4</a>]. Clearly, these |
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Schoening, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
devices are within the scope of energy management since they receive |
| 1066 |
power and are attached to the network. In addition, there is ample |
| 1067 |
scope for power management since printers and imaging systems are not |
| 1068 |
used that often. |
| 1069 |
|
| 1070 |
The IEEE-ISTO Printer Working Group (PWG) defines SNMP MIB modules |
| 1071 |
for printer management and, in particular, a "PWG Power Management |
| 1072 |
Model for Imaging Systems v1.0" [<a href="#ref-PWG5106.4" title=""PWG Power Management Model for Imaging Systems 1.0"">PWG5106.4</a>] and a companion SNMP |
| 1073 |
binding in the "PWG Imaging System Power MIB v1.0" [<a href="#ref-PWG5106.5" title=""PWG Imaging System Power MIB v1.0"">PWG5106.5</a>]. This |
| 1074 |
PWG model and MIB are harmonized with the DMTF CIM Infrastructure |
| 1075 |
[<a href="#ref-DMTF-DSP0004">DMTF-DSP0004</a>] and DMTF CIM Power State Management Profile |
| 1076 |
[<a href="#ref-DMTF-DSP1027">DMTF-DSP1027</a>] for power states and alerts. |
| 1077 |
|
| 1078 |
These MIB modules can be useful for monitoring the power and Power |
| 1079 |
State of printers. The EMAN framework takes into account the |
| 1080 |
standards defined in the Printer Working Group. The PWG may |
| 1081 |
harmonize its MIBs with those from EMAN. The PWG covers many topics |
| 1082 |
in greater detail than EMAN, including those specific to imaging |
| 1083 |
equipment. The PWG also provides for vendor-specific extension |
| 1084 |
states (beyond the standard DMTF CIM states). |
| 1085 |
|
| 1086 |
The IETF Printer MIB [<a href="./rfc3805" title=""Printer MIB v2"">RFC3805</a>] is on the Standards Track, but that |
| 1087 |
MIB module does not address power management. |
| 1088 |
|
| 1089 |
<span class="h4"><a class="selflink" id="section-4.1.6" href="#section-4.1.6">4.1.6</a>. ASHRAE</span> |
| 1090 |
|
| 1091 |
In the U.S., there is an extensive effort to coordinate and develop |
| 1092 |
standards related to the "Smart Grid". The Smart Grid |
| 1093 |
Interoperability Panel, coordinated by the government's National |
| 1094 |
Institute of Standards and Technology, identified the need for a |
| 1095 |
building side information model (as a counterpart to utility models) |
| 1096 |
and specified this in Priority Action Plan (PAP) 17. This was |
| 1097 |
designated to be a joint effort by the American Society of Heating, |
| 1098 |
Refrigerating and Air-Conditioning Engineers (ASHRAE) and the |
| 1099 |
National Electrical Manufacturers Association (NEMA), both ANSI- |
| 1100 |
approved Standards Development Organizations (SDOs). The result is |
| 1101 |
to be an information model, not a protocol. |
| 1102 |
|
| 1103 |
The ASHRAE effort [<a href="#ref-ASHRAE" title=""ASHRAE SPC 201 P Information Page"">ASHRAE</a>] addresses data used only within a building |
| 1104 |
as well as data that may be shared with the grid, particularly as it |
| 1105 |
relates to coordinating future demand levels with the needs of the |
| 1106 |
grid. The model is intended to be applied to any building type, both |
| 1107 |
residential and commercial. It is expected that existing protocols |
| 1108 |
will be adapted to comply with the new information model, as would |
| 1109 |
new protocols. |
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Schoening, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
There are four basic types of entities in the model: generators, |
| 1122 |
loads, meters, and energy managers. The metering part of the model |
| 1123 |
overlaps to a large degree with the EMAN framework, though there are |
| 1124 |
features unique to each. The load part speaks to control |
| 1125 |
capabilities well beyond what EMAN covers. Details of generation and |
| 1126 |
of the energy management function are outside of EMAN scope. |
| 1127 |
|
| 1128 |
A public review draft of the ASHRAE standard was released in July |
| 1129 |
2012. There are no apparent major conflicts between the two |
| 1130 |
approaches, but there are areas where some harmonization is possible. |
| 1131 |
|
| 1132 |
<span class="h4"><a class="selflink" id="section-4.1.7" href="#section-4.1.7">4.1.7</a>. ANSI/CEA</span> |
| 1133 |
|
| 1134 |
The Consumer Electronics Association (CEA) has approved ANSI/CEA-2047 |
| 1135 |
[<a href="#ref-ANSICEA" title=""CEA 2047 CE Energy Usage Information (CE-EUI)"">ANSICEA</a>] as a standard data model for Energy Usage Information. The |
| 1136 |
primary purpose is to enable home appliances and electronics to |
| 1137 |
communicate energy usage information over a wide range of |
| 1138 |
technologies with pluggable modules that contain the physical-layer |
| 1139 |
electronics. The standard can be used by devices operating on any |
| 1140 |
home network including Wi-Fi, Ethernet, ZigBee, Z-Wave, and |
| 1141 |
Bluetooth. The Introduction to ANSI/CEA-2047 states that "this |
| 1142 |
standard provides an information model for other groups to develop |
| 1143 |
implementations specific to their network, protocol and needs." It |
| 1144 |
covers device identification, current power level, cumulative energy |
| 1145 |
consumption, and provides for reporting time-series data. |
| 1146 |
|
| 1147 |
<span class="h4"><a class="selflink" id="section-4.1.8" href="#section-4.1.8">4.1.8</a>. ZigBee</span> |
| 1148 |
|
| 1149 |
The ZigBee Smart Energy Profile 2.0 (SEP) effort [<a href="#ref-ZIGBEE" title=""The ZigBee Alliance"">ZIGBEE</a>] focuses on |
| 1150 |
IP-based wireless communication to appliances and lighting. It is |
| 1151 |
intended to enable internal building energy management and provide |
| 1152 |
for bidirectional communication with the power grid. |
| 1153 |
|
| 1154 |
ZigBee protocols are intended for use in embedded applications with |
| 1155 |
low data rates and low power consumption. ZigBee defines a general- |
| 1156 |
purpose, inexpensive, self-organizing mesh network that can be used |
| 1157 |
for industrial control, embedded sensing, medical data collection, |
| 1158 |
smoke and intruder warning, building automation, home automation, |
| 1159 |
etc. |
| 1160 |
|
| 1161 |
ZigBee is currently not an ANSI-recognized SDO. |
| 1162 |
|
| 1163 |
The EMAN framework addresses the needs of IP-enabled networks through |
| 1164 |
the usage of SNMP, while ZigBee provides for completely integrated |
| 1165 |
and inexpensive mesh solutions. |
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Schoening, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Measurement</span> |
| 1178 |
|
| 1179 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. ANSI C12</span> |
| 1180 |
|
| 1181 |
The American National Standards Institute (ANSI) has defined a |
| 1182 |
collection of power meter standards under ANSI C12. The primary |
| 1183 |
standards include communication protocols (C12.18, 21 and 22), data |
| 1184 |
and schema definitions (C12.19), and measurement accuracy (C12.20). |
| 1185 |
European equivalent standards are provided by IEC 62053-22. |
| 1186 |
|
| 1187 |
These very specific standards are oriented to the meter itself and |
| 1188 |
are used by electricity distributors and producers. |
| 1189 |
|
| 1190 |
The EMAN framework [<a href="./rfc7326" title=""Energy Management Framework"">RFC7326</a>] references the Accuracy Classes |
| 1191 |
specified in ANSI C12.20. |
| 1192 |
|
| 1193 |
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. IEC 62301</span> |
| 1194 |
|
| 1195 |
IEC 62301, "Household electrical appliances - Measurement of standby |
| 1196 |
power" [<a href="#ref-IEC62301" title=""Household electrical appliances - Measurement of standby power"">IEC62301</a>], specifies a power-level measurement procedure. |
| 1197 |
While nominally for appliances and low-power modes, its concepts |
| 1198 |
apply to other device types and modes, and it is commonly referenced |
| 1199 |
in test procedures for energy using products. |
| 1200 |
|
| 1201 |
While the standard is intended for laboratory measurements of devices |
| 1202 |
in controlled conditions, aspects of it are informative to those |
| 1203 |
implementing measurement in products that ultimately report via EMAN. |
| 1204 |
|
| 1205 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Other</span> |
| 1206 |
|
| 1207 |
<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. ISO</span> |
| 1208 |
|
| 1209 |
The International Organization for Standardization (ISO) [<a href="#ref-ISO" title=""ISO launches ISO 50001 energy management standard"">ISO</a>] is |
| 1210 |
developing an energy management standard, ISO 50001, to complement |
| 1211 |
ISO 9001 for quality management and ISO 14001 for environmental |
| 1212 |
management. The intent is to facilitate the creation of energy |
| 1213 |
management programs for industrial, commercial, and other entities. |
| 1214 |
The standard defines a process for energy management at an |
| 1215 |
organizational level. It does not define the way in which devices |
| 1216 |
report energy and consume energy. |
| 1217 |
|
| 1218 |
ISO 50001 is based on the common elements found in all of ISO's |
| 1219 |
management system standards, assuring a high level of compatibility |
| 1220 |
with ISO 9001 and ISO 14001. ISO 50001 benefits include: |
| 1221 |
|
| 1222 |
o Integrating energy efficiency into management practices and |
| 1223 |
throughout the supply chain. |
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Schoening, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
o Using energy management best practices and good energy |
| 1234 |
management behaviors. |
| 1235 |
|
| 1236 |
o Benchmarking, measuring, documenting, and reporting energy |
| 1237 |
intensity improvements and their projected impact on reductions |
| 1238 |
in greenhouse gas (GHG) emissions. |
| 1239 |
|
| 1240 |
o Evaluating and prioritizing the implementation of new energy- |
| 1241 |
efficient technologies. |
| 1242 |
|
| 1243 |
ISO 50001 has been developed by ISO project committee ISO TC 242, |
| 1244 |
Energy Management. EMAN is complementary to ISO 9001. |
| 1245 |
|
| 1246 |
<span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>. Energy Star</span> |
| 1247 |
|
| 1248 |
The U.S. Environmental Protection Agency (EPA) and U.S. Department of |
| 1249 |
Energy (DOE) jointly sponsor the Energy Star program [<a href="#ref-ESTAR">ESTAR</a>]. The |
| 1250 |
program promotes the development of energy efficient products and |
| 1251 |
practices. |
| 1252 |
|
| 1253 |
To qualify as Energy Star, products must meet specific energy |
| 1254 |
efficiency targets. The Energy Star program also provides planning |
| 1255 |
tools and technical documentation to encourage more energy-efficient |
| 1256 |
building design. Energy Star is a program; it is not a protocol or |
| 1257 |
standard. |
| 1258 |
|
| 1259 |
For businesses and data centers, Energy Star offers technical support |
| 1260 |
to help companies establish energy conservation practices. Energy |
| 1261 |
Star provides best practices for measuring current energy |
| 1262 |
performance, goal setting, and tracking improvement. The Energy Star |
| 1263 |
tools offered include a rating system for building performance and |
| 1264 |
comparative benchmarks. |
| 1265 |
|
| 1266 |
There is no immediate link between EMAN and Energy Star, one being a |
| 1267 |
protocol and the other a set of recommendations to develop energy- |
| 1268 |
efficient products. However, Energy Star could include EMAN |
| 1269 |
standards in specifications for future products, either as required |
| 1270 |
or rewarded with some benefit. |
| 1271 |
|
| 1272 |
<span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>. Smart Grid</span> |
| 1273 |
|
| 1274 |
The Smart Grid standards efforts underway in the United States are |
| 1275 |
overseen by the U.S. National Institute of Standards and Technology |
| 1276 |
[<a href="#ref-NIST" title=""Smart Grid Homepage"">NIST</a>]. NIST is responsible for coordinating a public-private |
| 1277 |
partnership with key energy and consumer stakeholders in order to |
| 1278 |
facilitate the development of Smart Grid standards. These activities |
| 1279 |
are monitored and facilitated by the Smart Grid Interoperability |
| 1280 |
Panel (SGIP). This group has working groups for specific topics |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Schoening, et al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
including homes, commercial buildings, and industrial facilities as |
| 1290 |
they relate to the grid. A stated goal of the group is to harmonize |
| 1291 |
any new standard with the IEC CIM and IEC 61850. |
| 1292 |
|
| 1293 |
When a working group detects a standard or technology gap, the team |
| 1294 |
seeks approval from the SGIP for the creation of a Priority Action |
| 1295 |
Plan (PAP), a private-public partnership to close the gap. PAP 17 is |
| 1296 |
discussed in <a href="#section-4.1.6">Section 4.1.6</a>. |
| 1297 |
|
| 1298 |
PAP 10 addresses "Standard Energy Usage Information". Smart Grid |
| 1299 |
standards will provide distributed intelligence in the network and |
| 1300 |
allow enhanced load shedding. For example, pricing signals will |
| 1301 |
enable selective shutdown of non-critical activities during peak |
| 1302 |
price periods. Actions can be effected through both centralized and |
| 1303 |
distributed management controls. |
| 1304 |
|
| 1305 |
There is an obvious functional link between Smart Grid and EMAN in |
| 1306 |
the form of demand response even though the EMAN framework itself |
| 1307 |
does not address any coordination with the grid. As EMAN enables |
| 1308 |
control, it can be used by an EnMS to accomplish demand response |
| 1309 |
through translation of a signal from an outside entity. |
| 1310 |
|
| 1311 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Limitations</span> |
| 1312 |
|
| 1313 |
EMAN addresses the needs of energy monitoring in terms of measurement |
| 1314 |
and considers limited control capabilities of energy monitoring of |
| 1315 |
networks. |
| 1316 |
|
| 1317 |
EMAN does not create a new protocol stack, but rather defines a data |
| 1318 |
and information model useful for measuring and reporting energy and |
| 1319 |
other metrics over SNMP. |
| 1320 |
|
| 1321 |
EMAN does not address questions regarding Smart Grid, electricity |
| 1322 |
producers, and distributors. |
| 1323 |
|
| 1324 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 1325 |
|
| 1326 |
EMAN uses SNMP and thus has the functionality of SNMP's security |
| 1327 |
capabilities. SNMPv3 [<a href="./rfc3411" title=""An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks"">RFC3411</a>] provides important security features |
| 1328 |
such as confidentiality, integrity, and authentication. |
| 1329 |
|
| 1330 |
<a href="./rfc7460#section-10">Section 10 of [RFC7460]</a> and <a href="./rfc7461#section-6">Section 6 of [RFC7461]</a> mention that power |
| 1331 |
monitoring and management MIBs may have certain privacy implications. |
| 1332 |
These privacy implications are beyond the scope of this document. |
| 1333 |
There may be additional privacy considerations specific to each use |
| 1334 |
case; this document has not attempted to analyze these. |
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Schoening, et al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 1346 |
|
| 1347 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 1348 |
|
| 1349 |
[<a id="ref-RFC3411">RFC3411</a>] Harrington, D., Presuhn, R., and B. Wijnen, "An |
| 1350 |
Architecture for Describing Simple Network Management |
| 1351 |
Protocol (SNMP) Management Frameworks", STD 62, <a href="./rfc3411">RFC 3411</a>, |
| 1352 |
DOI 10.17487/RFC3411, December 2002, |
| 1353 |
<<a href="http://www.rfc-editor.org/info/rfc3411">http://www.rfc-editor.org/info/rfc3411</a>>. |
| 1354 |
|
| 1355 |
[<a id="ref-RFC3621">RFC3621</a>] Berger, A. and D. Romascanu, "Power Ethernet MIB", |
| 1356 |
<a href="./rfc3621">RFC 3621</a>, DOI 10.17487/RFC3621, December 2003, |
| 1357 |
<<a href="http://www.rfc-editor.org/info/rfc3621">http://www.rfc-editor.org/info/rfc3621</a>>. |
| 1358 |
|
| 1359 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 1360 |
|
| 1361 |
[<a id="ref-ACPI">ACPI</a>] ACPI, "Advanced Configuration and Power Interface |
| 1362 |
Specification", Revision 5.0b, November 2013, |
| 1363 |
<<a href="http://www.acpi.info/spec30b.htm">http://www.acpi.info/spec30b.htm</a>>. |
| 1364 |
|
| 1365 |
[<a id="ref-ANSICEA">ANSICEA</a>] ANSI, "CEA 2047 CE Energy Usage Information (CE-EUI)", |
| 1366 |
ANSI/CEA-2047, August 2014. |
| 1367 |
|
| 1368 |
[<a id="ref-ASHRAE">ASHRAE</a>] NIST, "ASHRAE SPC 201 P Information Page", |
| 1369 |
<<a href="http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP17Information">http://collaborate.nist.gov/twiki-sggrid/</a> |
| 1370 |
<a href="http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP17Information">bin/view/SmartGrid/PAP17Information</a>>. |
| 1371 |
|
| 1372 |
[<a id="ref-BACnet">BACnet</a>] "BACnet Webpage", <<a href="http://www.bacnet.org">http://www.bacnet.org</a>>. |
| 1373 |
|
| 1374 |
[<a id="ref-DASH">DASH</a>] DMTF, "Desktop and Mobile Architecture for System |
| 1375 |
Hardware", <<a href="http://www.dmtf.org/standards/mgmt/dash/">http://www.dmtf.org/standards/mgmt/dash/</a>>. |
| 1376 |
|
| 1377 |
[<a id="ref-DMTF-DSP0004">DMTF-DSP0004</a>] |
| 1378 |
DMTF, "Common Information Model (CIM) Infrastructure", |
| 1379 |
DSP0004, Version 2.5.0, May 2009, <<a href="http://www.dmtf.org/standards/published_documents/DSP0004_2.5.0.pdf">http://www.dmtf.org/</a> |
| 1380 |
<a href="http://www.dmtf.org/standards/published_documents/DSP0004_2.5.0.pdf">standards/published_documents/DSP0004_2.5.0.pdf</a>>. |
| 1381 |
|
| 1382 |
[<a id="ref-DMTF-DSP1027">DMTF-DSP1027</a>] |
| 1383 |
DMTF, "Power State Management Profile", DSP1027, Version |
| 1384 |
2.0.0, December 2009, <<a href="http://www.dmtf.org/standards/published_documents/DSP1027_2.0.0.pdf">http://www.dmtf.org/standards/</a> |
| 1385 |
<a href="http://www.dmtf.org/standards/published_documents/DSP1027_2.0.0.pdf">published_documents/DSP1027_2.0.0.pdf</a>>. |
| 1386 |
|
| 1387 |
[<a id="ref-Ecma-SDC">Ecma-SDC</a>] Ecma International, "Smart Data Centre Resource |
| 1388 |
Monitoring and Control", Standard ECMA-400, Second |
| 1389 |
Edition, June 2013, <<a href="http://www.ecma-international.org/publications/standards/Ecma-400.htm">http://www.ecma-international.org/</a> |
| 1390 |
<a href="http://www.ecma-international.org/publications/standards/Ecma-400.htm">publications/standards/Ecma-400.htm</a>>. |
| 1391 |
|
| 1392 |
[<a id="ref-ESTAR">ESTAR</a>] Energy Star, <<a href="http://www.energystar.gov/">http://www.energystar.gov/</a>>. |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Schoening, et al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
[<a id="ref-IEC62301">IEC62301</a>] IEC, "Household electrical appliances - Measurement of |
| 1402 |
standby power", IEC 62301:2011, Edition 2.0, January |
| 1403 |
2011. |
| 1404 |
|
| 1405 |
[<a id="ref-ISO">ISO</a>] ISO, "ISO launches ISO 50001 energy management standard", |
| 1406 |
June 2011, |
| 1407 |
<<a href="http://www.iso.org/iso/news.htm?refid=Ref1434">http://www.iso.org/iso/news.htm?refid=Ref1434</a>>. |
| 1408 |
|
| 1409 |
[<a id="ref-MODBUS">MODBUS</a>] Modbus-IDA, "MODBUS Application Protocol Specification", |
| 1410 |
Version 1.1b, December 2006, <<a href="http://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b.pdf">http://www.modbus.org/docs/</a> |
| 1411 |
<a href="http://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b.pdf">Modbus_Application_Protocol_V1_1b.pdf</a>>. |
| 1412 |
|
| 1413 |
[<a id="ref-NIST">NIST</a>] NIST, "Smart Grid Homepage", August 2010, |
| 1414 |
<<a href="http://www.nist.gov/smartgrid/">http://www.nist.gov/smartgrid/</a>>. |
| 1415 |
|
| 1416 |
[<a id="ref-PWG5106.4">PWG5106.4</a>] IEEE-ISTO, "PWG Power Management Model for Imaging |
| 1417 |
Systems 1.0", PWG Candidate Standard 5106.4-2011, |
| 1418 |
February 2011, <<a href="ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimspower10-20110214-5106.4.pdf">ftp://ftp.pwg.org/pub/pwg/candidates/</a> |
| 1419 |
<a href="ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimspower10-20110214-5106.4.pdf">cs-wimspower10-20110214-5106.4.pdf</a>>. |
| 1420 |
|
| 1421 |
[<a id="ref-PWG5106.5">PWG5106.5</a>] IEEE-ISTO, "PWG Imaging System Power MIB v1.0", PWG |
| 1422 |
Candidate Standard 5106.5-2011, February 2011. |
| 1423 |
|
| 1424 |
[<a id="ref-RFC3805">RFC3805</a>] Bergman, R., Lewis, H., and I. McDonald, "Printer MIB |
| 1425 |
v2", <a href="./rfc3805">RFC 3805</a>, DOI 10.17487/RFC3805, June 2004, |
| 1426 |
<<a href="http://www.rfc-editor.org/info/rfc3805">http://www.rfc-editor.org/info/rfc3805</a>>. |
| 1427 |
|
| 1428 |
[<a id="ref-RFC6933">RFC6933</a>] Bierman, A., Romascanu, D., Quittek, J., and M. |
| 1429 |
Chandramouli, "Entity MIB (Version 4)", <a href="./rfc6933">RFC 6933</a>, |
| 1430 |
DOI 10.17487/RFC6933, May 2013, |
| 1431 |
<<a href="http://www.rfc-editor.org/info/rfc6933">http://www.rfc-editor.org/info/rfc6933</a>>. |
| 1432 |
|
| 1433 |
[<a id="ref-RFC6988">RFC6988</a>] Quittek, J., Ed., Chandramouli, M., Winter, R., Dietz, |
| 1434 |
T., and B. Claise, "Requirements for Energy Management", |
| 1435 |
<a href="./rfc6988">RFC 6988</a>, DOI 10.17487/RFC6988, September 2013, |
| 1436 |
<<a href="http://www.rfc-editor.org/info/rfc6988">http://www.rfc-editor.org/info/rfc6988</a>>. |
| 1437 |
|
| 1438 |
[<a id="ref-RFC7326">RFC7326</a>] Parello, J., Claise, B., Schoening, B., and J. Quittek, |
| 1439 |
"Energy Management Framework", <a href="./rfc7326">RFC 7326</a>, |
| 1440 |
DOI 10.17487/RFC7326, September 2014, |
| 1441 |
<<a href="http://www.rfc-editor.org/info/rfc7326">http://www.rfc-editor.org/info/rfc7326</a>>. |
| 1442 |
|
| 1443 |
[<a id="ref-RFC7460">RFC7460</a>] Chandramouli, M., Claise, B., Schoening, B., Quittek, J., |
| 1444 |
and T. Dietz, "Monitoring and Control MIB for Power and |
| 1445 |
Energy", <a href="./rfc7460">RFC 7460</a>, DOI 10.17487/RFC7460, March 2015, |
| 1446 |
<<a href="http://www.rfc-editor.org/info/rfc7460">http://www.rfc-editor.org/info/rfc7460</a>>. |
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Schoening, et al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
[<a id="ref-RFC7461">RFC7461</a>] Parello, J., Claise, B., and M. Chandramouli, "Energy |
| 1458 |
Object Context MIB", <a href="./rfc7461">RFC 7461</a>, DOI 10.17487/RFC7461, |
| 1459 |
March 2015, <<a href="http://www.rfc-editor.org/info/rfc7461">http://www.rfc-editor.org/info/rfc7461</a>>. |
| 1460 |
|
| 1461 |
[<a id="ref-RFC7577">RFC7577</a>] Quittek, J., Winter, R., and T. Dietz, "Definition of |
| 1462 |
Managed Objects for Battery Monitoring", <a href="./rfc7577">RFC 7577</a>, |
| 1463 |
DOI 10.17487/RFC7577, July 2015, |
| 1464 |
<<a href="http://www.rfc-editor.org/info/rfc7577">http://www.rfc-editor.org/info/rfc7577</a>>. |
| 1465 |
|
| 1466 |
[<a id="ref-ZIGBEE">ZIGBEE</a>] "The ZigBee Alliance", <<a href="http://www.zigbee.org/">http://www.zigbee.org/</a>>. |
| 1467 |
|
| 1468 |
Acknowledgements |
| 1469 |
|
| 1470 |
Firstly, the authors thank Emmanuel Tychon for taking the lead on the |
| 1471 |
initial draft and making substantial contributions to it. The |
| 1472 |
authors also thank Jeff Wheeler, Benoit Claise, Juergen Quittek, |
| 1473 |
Chris Verges, John Parello, and Matt Laherty for their valuable |
| 1474 |
contributions. The authors also thank Kerry Lynn for the use case |
| 1475 |
involving demand response. |
| 1476 |
|
| 1477 |
|
| 1478 |
|
| 1479 |
|
| 1480 |
|
| 1481 |
|
| 1482 |
|
| 1483 |
|
| 1484 |
|
| 1485 |
|
| 1486 |
|
| 1487 |
|
| 1488 |
|
| 1489 |
|
| 1490 |
|
| 1491 |
|
| 1492 |
|
| 1493 |
|
| 1494 |
|
| 1495 |
|
| 1496 |
|
| 1497 |
|
| 1498 |
|
| 1499 |
|
| 1500 |
|
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Schoening, et al. Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc7603">RFC 7603</a> EMAN Applicability Statement August 2015</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
Authors' Addresses |
| 1514 |
|
| 1515 |
Brad Schoening |
| 1516 |
Independent Consultant |
| 1517 |
44 Rivers Edge Drive |
| 1518 |
Little Silver, NJ 07739 |
| 1519 |
United States |
| 1520 |
|
| 1521 |
Phone: +1 917 304 7190 |
| 1522 |
Email: [email protected] |
| 1523 |
|
| 1524 |
|
| 1525 |
Mouli Chandramouli |
| 1526 |
Cisco Systems, Inc. |
| 1527 |
Sarjapur Outer Ring Road |
| 1528 |
Bangalore 560103 |
| 1529 |
India |
| 1530 |
|
| 1531 |
Phone: +91 80 4429 2409 |
| 1532 |
Email: [email protected] |
| 1533 |
|
| 1534 |
|
| 1535 |
Bruce Nordman |
| 1536 |
Lawrence Berkeley National Laboratory |
| 1537 |
1 Cyclotron Road, 90-2000 |
| 1538 |
Berkeley, CA 94720-8130 |
| 1539 |
United States |
| 1540 |
|
| 1541 |
Phone: +1 510 486 7089 |
| 1542 |
Email: [email protected] |
| 1543 |
|
| 1544 |
|
| 1545 |
|
| 1546 |
|
| 1547 |
|
| 1548 |
|
| 1549 |
|
| 1550 |
|
| 1551 |
|
| 1552 |
|
| 1553 |
|
| 1554 |
|
| 1555 |
|
| 1556 |
|
| 1557 |
|
| 1558 |
|
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
Schoening, et al. Standards Track [Page 28] |
| 1565 |
</pre> |