idnits 2.17.1 draft-ietf-eman-applicability-statement-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 18, 2012) is 4329 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-11) exists of draft-ietf-eman-applicability-statement-00 == Outdated reference: A later version (-14) exists of draft-ietf-eman-requirements-06 == Outdated reference: A later version (-13) exists of draft-ietf-eman-energy-monitoring-mib-02 == Outdated reference: A later version (-19) exists of draft-ietf-eman-framework-04 == Outdated reference: A later version (-20) exists of draft-ietf-eman-battery-mib-05 == Outdated reference: A later version (-09) exists of draft-parello-eman-definitions-05 Summary: 0 errors (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Energy Management Working Group B. Schoening 3 Internet Draft Independent Consultant 4 Intended status: Informational Mouli Chandramouli 5 Expires: December 18, 2012 Cisco Systems Inc. 6 Bruce Nordman 7 Lawrence Berkeley National Laboratory 8 June 18, 2012 10 Energy Management (EMAN) Applicability Statement 11 draft-ietf-eman-applicability-statement-01 13 Abstract 15 The objective of Energy Management (EMAN) is to provide an 16 energy management framework for networked devices. This 17 document presents the applicability of the EMAN framework for a 18 variety of scenarios. This document lists use cases and target 19 devices that can potentially implement the EMAN framework and 20 associated SNMP MIB modules. These use cases are useful for 21 identifying requirements for the framework. Further, we 22 describe the relationship of the EMAN framework to relevant 23 other energy monitoring standards and architectures. 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance 28 with the provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet 31 Engineering Task Force (IETF), its areas, and its working 32 groups. Note that other groups may also distribute working 33 documents as Internet-Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six 36 months and may be updated, replaced, or obsoleted by other 37 documents at any time. It is inappropriate to use Internet- 38 Drafts as reference material or to cite them other than as "work 39 in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html 46 This Internet-Draft will expire on December 18, 2012. 48 Copyright Notice 50 Copyright (c) 2012 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with 58 respect to this document. Code Components extracted from this 59 document must include Simplified BSD License text as described 60 in Section 4.e of the Trust Legal Provisions and are provided 61 without warranty as described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction ...............................................3 66 1.1. Energy Management Overview .............................4 67 1.2. EMAN WG Document Overview ..............................4 68 1.3. Energy Measurement .....................................5 69 1.4. Energy Management ......................................5 70 1.5. EMAN Framework Application .............................6 71 2. Scenarios and Target Devices ...............................7 72 2.1. Network Infrastructure Energy Objects ..................7 73 2.2. Devices Powered by and Connected to a Network Device ...8 74 2.3. Devices Connected to a Network .........................9 75 2.4. Power Meters ..........................................10 76 2.5. Mid-level Managers ....................................11 77 2.6. Gateways to Building Systems ..........................11 78 2.7. Home Energy Gateways ..................................12 79 2.8. Data Center Devices ...................................13 80 2.9. Energy Storage Devices ................................14 81 2.10. Industrial Automation Networks .......................15 82 2.11. Printers .............................................15 83 2.12. Off-Grid Devices .....................................16 84 2.13. Demand/Response ......................................17 85 2.14. Power Capping ........................................18 86 3. Use Case Patterns .........................................18 87 3.1. Metering ..............................................18 88 3.2. Metering and Control ..................................18 89 3.3. Power Supply, Metering and Control ....................18 90 3.4. Multiple Power Sources ................................19 92 4. Relationship of EMAN to other Standards ...................19 93 4.1. Data Model and Reporting ..............................19 94 4.1.1. IEC - CIM......................................19 95 4.1.2. DMTF...........................................20 96 4.1.3. ODVA...........................................21 97 4.1.4. Ecma SDC......................................21 98 4.1.5. IEEE-ISTO Printer Working Group (PWG)..........22 99 4.1.6. ASHRAE.........................................22 100 4.1.7. ZigBee.........................................23 101 4.2. Measurement ...........................................23 102 4.2.1. ANSI C12.......................................23 103 4.2.2. IEC62301.......................................24 104 4.3. Other .................................................24 105 4.3.1. ISO............................................24 106 4.3.2. EnergyStar.....................................25 107 4.3.3. SmartGrid......................................25 108 5. Limitations ...............................................26 109 6. Security Considerations ...................................26 110 7. IANA Considerations .......................................27 111 8. Acknowledgements ..........................................27 112 9. Open Issues ...............................................27 113 10. References ...............................................27 114 10.1. Normative References .................................27 115 10.2. Informative References ...............................28 117 1. Introduction 119 The focus of the Energy Management (EMAN) framework is energy 120 monitoring and management of energy objects [EMAN-DEF]. The 121 scope of devices considered are network equipment and its 122 components, and devices connected directly or indirectly to 123 the network. The EMAN framework enables monitoring 124 (heterogeneous devices to report their energy consumption) 125 and, if permissible, control. There are multiple scenarios 126 where this is desirable, particularly considering the 127 increased importance of limiting consumption of finite energy 128 resources and reducing operational expenses. 130 The EMAN framework [EMAN-FRAMEWORK] describes how energy 131 information can be retrieved from IP-enabled devices using 132 Simple Network Management Protocol (SNMP), specifically, 133 Management Information Base (MIBs) for SNMP. 135 This document describes typical applications of the EMAN 136 framework, as well as its opportunities and limitations. Other 137 standards that are similar to EMAN but address different domains 138 are described. This document contains references to those other 139 standards and describes how they relate to the EMAN framework. 141 The rest of the document is organized as follows. Section 2 142 contains a list of use cases or network scenarios that EMAN 143 shall address. Section 3 contains an abstraction of the use case 144 scenarios to distinct patterns. Section 4 deals with the 145 standards related to EMAN and applicable to EMAN. 147 1.1. Energy Management Overview 149 EMAN addresses the electrical energy consumed by devices 150 connected to a network. A first step to increase the energy 151 efficiency in networks and buildings is to enable energy objects 152 to report their energy usage over time. The EMAN framework 153 addresses this problem with an information model for some 154 electrical equipment: energy object identification, energy 155 object context, power measurement and power characteristics. 157 The EMAN WG framework defines SNMP MIB modules based on the 158 information model. By implementing the SNMP MIB modules, any 159 energy object can report its energy consumption according to the 160 information model. In that context, it is important to 161 distinguish energy objects that can only report their own energy 162 usage from devices that can also collect and aggregate energy 163 usage of other energy objects. 165 Target devices and scenarios considered for Energy Management 166 are presented in Section 2 with detailed examples. 168 1.2. EMAN WG Document Overview 170 The EMAN working group charter called for producing a series of 171 Internet standard drafts in the area of energy management. The 172 following drafts were created by the working group. 174 Applicability Statement [EMAN-AS] this document presents the 175 use cases and scenarios for energy management. In addition, 176 other relevant energy standards and architectures are listed. 178 Requirements [EMAN-REQ] this document presents the 179 requirements of energy management and the scope of the devices 180 considered. 182 Framework [EMAN-FRAMEWORK] This document defines a framework 183 for providing Energy Management for devices within or 184 connected to communication networks. 186 Energy-Aware MIB [EMAN-AWARE-MIB] This document proposes a MIB 187 module that characterizes a device's identity, context and the 188 relationship to other entities. 190 Monitoring MIB [EMAN-MONITORING-MIB] This document defines a 191 MIB module for monitoring the power and energy consumption of 192 a device. The MIB module contains an optional module for 193 metrics associated with power characteristics. 195 Battery MIB [EMAN-BATTERY-MIB] This document contains a MIB 196 module for monitoring characteristics of an internal battery. 198 Energy Management Terminology [EMAN-DEF] This document lists 199 the definitions for the common terms used in the Energy 200 Management Working Group. 202 1.3. Energy Measurement 204 More and more devices are able to measure and report their own 205 energy consumption. Smart power strips and some Power over 206 Ethernet (PoE) switches can meter consumption of connected 207 devices. However, when managed and reported through proprietary 208 means, this information is minimally useful at the enterprise 209 level. 211 The primary goal of the EMAN MIBs is to enable reporting and 212 management within a standard framework that is applicable to a 213 wide variety of end devices, meters, and proxies. This enables a 214 management system to know who's consuming what, when, and how at 215 any time by leveraging existing networks, across various 216 equipment, in a unified and consistent manner. 218 Given that an energy object can consume energy and/or provide 219 energy to other devices, there are three types of energy 220 measurement: energy input to a device, energy supplied to other 221 devices, and net (resultant) energy consumed (the difference 222 between energy input and provided). 224 1.4. Energy Management 226 Beyond energy monitoring, the EMAN framework provides mechanisms 227 for energy control. 229 There are many cases where reducing energy consumption of 230 devices is desirable, such as when the device utilization is low 231 or when the electricity is expensive or in short supply. 233 In some cases, energy control requires considering the energy 234 object context. For instance, in a building during non-business 235 hours: usually not all phones would be turned off to keep some 236 phones available in case of emergency; office cooling is usually 237 not turned off totally, but the comfort level is reduced. 239 Energy object control requires flexibility and support for 240 different polices and mechanisms: from centralized management 241 with a network management station, to autonomous management by 242 individual devices, and alignment with dynamic demand-response 243 mechanisms. 245 The EMAN framework can be used as a tool for the demand/response 246 scenario where in response to time-of-day fluctuation of energy 247 costs or possible energy shortages, it is possible to respond 248 and reduce the energy consumption for the network devices, 249 effectively changing its power state. 251 1.5. EMAN Framework Application 253 A Network Management System (NMS) is the entity that requests 254 information from compatible devices using SNMP protocol. An NMS 255 implements many network management functions, e.g. security 256 management, or identity management. An NMS that deals 257 exclusively with energy is called EnMS Energy Management System. 258 It may be limited to monitoring energy use, or it may also 259 implement control functions. In a typical application of the 260 EMAN framework, management software collects energy information 261 for devices in the network. 263 Energy management can be implemented by extending existing SNMP 264 support to the EMAN specific MIBs. SNMP provides an industry 265 proven and well-known mechanism to discover, secure, measure, 266 and control SNMP-enabled end devices. The EMAN framework 267 provides an information and data model to unify access to a 268 large range of devices. 270 The scope of the target devices and the network scenarios 271 considered for energy management are listed in Section 2. 273 2. Scenarios and Target Devices 275 In this section a selection of scenarios for energy management 276 are presented. The fundamental objective of the use cases is to 277 list important network scenarios that the EMAN framework should 278 solve. These use cases then drive the requirements for the EMAN 279 framework. 281 Each scenario lists target devices for which the energy 282 management framework can be applied, how the reported-on devices 283 are powered, and how the reporting is accomplished. While there 284 is some overlap between some of the use cases, the use cases 285 serve as illustrative network scenarios EMAN framework supports. 287 2.1. Network Infrastructure Energy Objects 289 This scenario covers network devices and their components. Power 290 management of energy objects is considered as a fundamental 291 requirement of energy management of networks. 293 It can be important to monitor the energy consumption and 294 possibly manage the power state of these devices at a 295 granularity level finer than just the entire device. For these 296 devices, the chassis draws power from one or more sources and 297 feeds all its internal components. It is highly desirable to 298 have monitoring available for individual components, such as 299 line cards, processors, and hard drives as well as peripherals 300 like USB devices. 302 As an illustrative example, consider a switch with the following 303 grouping of sub-entities for which energy management could be 304 useful. 306 . physical view: chassis (or stack), line cards, service 307 modules of the switch. 308 . component view: CPU, ASICs, fans, power supply, ports 309 (single port and port groups), storage and memory. 311 The ENTITY-MIB provides the containment tree framework, for 312 uniquely identifying the physical sub-components of network 313 devices. A component can be an Energy Object and the ENTITY-MIB 314 containment tree shall express if that Energy Object belongs to 315 another Energy Object (e.g. line-card Energy Object contained in 316 a chassis Energy Object. The table entPhysicalContainsTable 317 which has the index of entPhysicalChildIndex and the MIB object 318 entPhysicalContainedIn which points to the containing entity. 320 The essential properties of this use case are: 322 . Target devices: network devices such as routers, switches 323 and their components. 324 . How powered: typically by a PDU on a rack or from a wall 325 outlet. The components of a device are powered by the 326 device chassis. 327 . Reporting: direct power measurement can be performed at a 328 device level. Components can report their power consumption 329 directly or the chassis/device that can report on behalf of 330 some components. 332 2.2. Devices Powered by and Connected to a Network Device 334 This scenario covers Power over Ethernet (PoE) devices. A PoE 335 Power Sourcing Equipment (PSE) device [RFC3621] (e.g. a PoE 336 switch) provides power to a Powered Device (PD) (e.g. a desktop 337 phone). For each port, the PSE can control the power supply 338 (switching it on and off) and meter actual power provided. PDs 339 obtain network connectivity as well as power over a single 340 connection so the PSE can determine which device is associated 341 with each port. 343 PoE ports on a switch are commonly connected to devices such as 344 IP phones, wireless access points, and IP cameras. The switch 345 needs power for its internal use and to supply power to PoE 346 ports. Monitoring the power consumption of the switch (supplying 347 device) and the power consumption of the PoE end-points 348 (consuming devices) is a simple use case of this scenario. 350 It is also possible to illustrate the relationships between 351 entities. The PoE IP phone is powered by the switch. If there 352 are many IP phones connected to the same switch and the power 353 consumption of all the IP phones can be aggregated by the 354 switch. In that case, the switch performs the aggregation 355 function for other entities. 357 The essential properties of this use case are: 359 . Target devices: power over Ethernet devices such as IP 360 phones, wireless access points, and IP cameras. 361 . How powered: PoE devices are connected to the switch port 362 which supplies power to those devices. 363 . Reporting: PoE device power consumption is measured and 364 reported by the switch (PSE) which supplies power. In 365 addition, some devices can have support for the EMAN 366 framework. 368 This use case can be subdivided into two sub cases: 370 a) The end device supports the EMAN framework, in which case 371 this device is an EMAN Energy Object by itself, with its own 372 UUID, like in scenario "Devices Connected to a Network" 373 below. The device is responsible for its own power reporting 374 and control. 376 b) The end device does not have EMAN capabilities, and the 377 power measurement may not be able to be performed 378 independently, and so is only performed by the supplying 379 device. This scenario is similar to the "Mid-level Manager" 380 below. 382 In the sub case (a) note that two power usage reporting for the 383 same device are available: one performed by the PD itself and 384 one performed by the PSE. Device specific implementations will 385 dictate which one if the most accurate. 387 It is also possible to illustrate the relationships between 388 entities. The PoE IP phone is powered by the switch. If there 389 are many IP phones connected to the same switch and the power 390 consumption of all the IP phones can be aggregated by the 391 switch. In that case, the switch performs the aggregation 392 function for other entities. 394 2.3. Devices Connected to a Network 396 The use case covers the metering relationship between an energy 397 object and the parent energy object it is connected to, while 398 receiving power from an external source such as a power brick. 400 An example is a PC which has a network connection to a switch, 401 but draws power from a wall outlet. In this case, the PC can 402 report power usage by itself, ideally through the EMAN 403 framework. 405 The wall outlet the PC is plugged in can be metered for example 406 by a Smart PDU, or unmetered. 408 a) If metered, the PC has a powered-by relationship to the Smart 409 PDU, and the Smart PDU will act as a "Mid-Level Manager" 410 b) If unmetered - or running on batteries - the PC will report 411 its own energy usage as any other Energy Object to the switch, 412 and the switch can possibly provide aggregation. 414 Note that a) and b) are not mutually exclusive. 416 In terms of relationships between entities, the PC has a powered 417 by relationship to the PDU and if the power consumption of the 418 PC is metered by the PDU then there is a metered by relation 419 between the PC and the PDU. 421 The essential properties of this use case are: 423 . Target devices: Energy objects that have a network 424 connection, but receive power supply from another source. 425 . How powered: Children (e.g.: PCs)receive power supply from 426 the wall outlet (unmetered), or a PDU (metered). That can 427 also be powered autonomously (batteries). 428 . Reporting: Devices can measure and report the power 429 consumption directly via the EMAN framework, or, 430 communicate it to the network device (switch) and the 431 switch can report the device's power consumption via the 432 EMAN framework. 434 2.4. Power Meters 436 Some electrical devices are not equipped with instrumentation to 437 measure their own power and accumulated energy consumption. 438 External meters can be used to measure the power consumption of 439 such electrical devices as well as collections of devices. 440 This use case covers the proxy relationship of energy objects 441 able to measure or report the power consumption of external 442 electrical devices, not natively connected to the network. 443 Examples of such metering devices are smart PDUs and smart 444 meters. 446 Three types of external metering are relevant to EMAN: PDUs, 447 standalone meters, and utility meters. External meters can 448 measure consumption of a single device or a set of devices. 450 Power Distribution Unit (PDUs) have inbuilt meters for each 451 socket and so can measure the power supplied to each device in 452 an equipment rack. The PDUs have remote management functionality 453 which can measure and possibly control the power supply of each 454 outlet. 456 Standalone meters can be placed anywhere in a power distribution 457 tree are allocated to specific devices. 458 Utility meters monitor and report accumulated power consumption 459 of the entire building. There can be sub-meters to measure the 460 power consumption of a portion of the building. 462 The essential properties of this use case are: 464 . Target devices: PDUs and meters. 465 . How powered: From traditional mains power but as passed 466 through a PDU or meter. 467 . Reporting: The PDUs reports power consumption of downstream 468 devices, usually a single device per outlet. 470 The meters can have a metering relationship and possibly 471 aggregation relationship between the meters and the devices for 472 which power consumption is accumulated and reported by the 473 meter. 475 2.5. Mid-level Managers 477 This use case covers aggregation of energy management data at 478 "mid-level managers" that can provide energy management 479 functions for themselves as well as associated devices. 481 A switch can provide energy management functions for all devices 482 connected to its ports, whether or not these devices are powered 483 by the switch or whether the switch provides immediate network 484 connectivity to the devices; such a switch is a mid-level 485 manager, offering aggregation of power consumption data for 486 other devices. Devices report their EMAN data to the switch and 487 the switch aggregates the data for further reporting. 489 The essential properties of this use case: 491 . Target devices: Devices which can perform aggregation; 492 commonly a switch or a proxy 493 . How powered: Mid-level managers can be are commonly 494 powered by a PDU or from a wall outlet and can be powered 495 by any method. 496 . Reporting: The middle-manager aggregates the energy data 497 and reports that data to a NMS or higher mid-level manager. 499 2.6. Gateways to Building Systems 501 This use case describes energy management of buildings. Building 502 Management Systems (BMS) have been in place for many years using 503 legacy protocols not based on IP. In these buildings, a gateway 504 can provide a proxy relationship between IP and legacy building 505 automation protocols. The gateway can provide an interface 506 between the EMAN framework and relevant building management 507 protocols. 509 Due to the potential energy savings, energy management of 510 buildings has received significant attention. There are gateway 511 network elements to manage the multiple components of a building 512 energy management system such as Heating, Ventilation, and Air 513 Conditioning (HVAC), lighting, electrical, fire and emergency 514 systems, elevators, etc. The gateway device uses legacy building 515 protocols to communicate with those devices, collects their 516 energy usage, and reports the results. 518 The gateway performs protocol conversion and communicates via 519 RS-232/RS-485 interfaces, Ethernet interfaces, and protocols 520 specific to building management such as BACNET [ASHRAE], MODBUS 521 [MODBUS-Protocol], or Zigbee [ZIGBEE]. 523 The essential properties of this use case are: 525 . Target devices: Building energy management devices - HVAC 526 systems, lighting, electrical, fire and emergency systems. 527 . How powered: Any method. 528 . Reporting: The gateway collects energy consumption of non- 529 IP systems and communicates the data via the EMAN 530 framework. 532 2.7. Home Energy Gateways 534 This use case describes the scenario of energy management of a 535 home. The home energy gateway is another example of a proxy that 536 interfaces to the electrical appliances and other devices in a 537 home. This gateway can monitor and manage electrical equipment 538 (refrigerator, heating/cooling, washing machine etc.) using one 539 of the many protocols that are being developed for the home area 540 network products. 542 In its simplest form, metering can be performed at home. Beyond 543 the metering, it is also possible to implement energy saving 544 policies based on energy pricing from the utility grid. The EMAN 545 information model can be applied to the protocols under 546 consideration for energy management of a home. 548 The essential properties of this use case are: 550 . Target devices: Home energy gateway and smart meters in a 551 home. 552 . How powered: Any method. 553 . Reporting: Home energy gateway can collect power 554 consumption of device in a home and possibly report the 555 metering reading to the utility. 557 Beyond the canonical setting of a home drawing power from the 558 utility, it is also possible to envision an energy neutral 559 situation wherein the buildings/homes that can produce and 560 consume energy with reduced or zero net importing energy from 561 the utility grid. There are many energy production technologies 562 such as solar panels, wind turbines, or micro generators. This 563 use case illustrates the concept of covers self-contained energy 564 generation and consumption and possibly the aggregation of the 565 energy use of homes. 567 2.8. Data Center Devices 569 This use case describes energy management of a data center. 571 Energy efficiency of data centers has become a fundamental 572 challenge of data center operation, as datacenters are big 573 energy consumers and have expensive infrastructure. The 574 equipment generates heat, and heat needs to be evacuated though 575 a HVAC system. 577 A typical data center network consists of a hierarchy of 578 electrical energy objects. At the bottom of the network 579 hierarchy are servers mounted on a rack; these are connected to 580 top-of-the-rack switches, which in turn are connected to 581 aggregation switches, and then to core switches. Power 582 consumption of all network elements, servers, and network 583 storage devices in the data center should be measured. Energy 584 management can be implemented on different aggregation levels, 585 at the network level, Power Distribution Unit (PDU) level, and 586 server level. 588 Beyond the network devices, storage devices and servers, data 589 centers contain UPSs to provide back-up power for the network, 590 storage devices in the event in the event of a power outage. A 591 UPS can provide backup power for many devices in a data center 592 for a finite period of time. Energy monitoring of such energy 593 storage devices is vital from a data center network operations 594 point of view. Presently, the UPS MIB can be useful in 595 monitoring the battery capacity, the input load to the UPS and 596 the output load from the UPS. Currently, there is no link 597 between the UPS MIB and the ENTITY MIB. 599 Thus from a Data center energy management point of view, in 600 addition, to monitoring the energy usage of network devices, it 601 is also important to monitor the remaining capacity of the UPS. 603 In addition to monitoring the power consumption of a data 604 center, additional power characteristic metrics should be 605 monitored. Some of these are dynamic variations in the input 606 power supply from the grid referred to as power characteristics 607 is one metric. Secondly, how the devices utilize the power in 608 terms of efficiency can be useful to monitor these metrics. 610 Lastly, the nameplate power consumption (the worst case possible 611 power draw) of all devices will make it possible to know an 612 aggregate of the potential worst-case power usage and compare it 613 to the budgeted power in the data center. 615 The essential properties of this use case are: 617 . Target devices: All IT devices in a data center, such as 618 network equipment, servers, and storage devices, as well as 619 power and cooling infrastructure. 620 . How powered: Any method but commonly by one or more PDUs. 621 . Reporting: Devices may report on their own behalf, or for 622 other connected devices as described in other use cases. 624 2.9. Energy Storage Devices 626 There are two types of devices with energy storage: those whose 627 primary function is to provide power to another device (e.g. a 628 UPS), and those with a different primary function, but have an 629 energy storage as a component as an alternate internal power 630 source (e.g. a notebook). This use case covers both types of 631 products. 633 The energy storage can be a conventional battery, or any other 634 means to store electricity such as a hydrogen cell. 636 An internal battery can be a back-up or an alternative source of 637 power to mains power. As batteries have a finite capacity and 638 lifetime, means for reporting the actual charge, age, and state 639 of a battery are required. An internal battery can be viewed as 640 a component of a device and thus could have the containment 641 relationship from an ENTITY-MIB perspective to the device that 642 contains the battery 644 Battery systems are used in mobile telecom towers including for 645 use in remote locations. It is important to monitor the 646 remaining battery life and raise an alarm when the battery life 647 is below a threshold. 649 The essential properties of this use case are: 651 . Target devices: Devices that have an internal battery 652 . How powered: From internal batteries or mains power 653 . Reporting: The device reports on its internal battery 655 2.10. Industrial Automation Networks 657 Energy consumption statistics in the industrial sector are 658 staggering. The industrial sector alone consumes about half of 659 the world's total delivered energy, and a significant user of 660 electricity. Thus, the need for optimization of energy usage in 661 this sector is natural. 663 Industrial facilities consume energy in process loads, and in 664 non-process loads. 666 The essential properties of this use case are: 668 . Target devices: Devices used in industrial automation 669 . How powered: Any method. 670 . Reporting: Currently, CIP protocol is currently used for 671 reporting energy for these devices 673 2.11. Printers 675 This use case describes the scenario of energy monitoring and 676 management of printers. 678 Printers in this use case stand in for all imaging equipment, 679 also including multi-function devices (MFDs), copiers, scanners, 680 fax machines, and mailing machines. 682 Energy use of printers has been an industry concern for several 683 decades, and they usually have sophisticated power management 684 with a variety of low-power modes, particularly for managing 685 energy-intensive thermo-mechanical components. Printers also 686 have long made extensive use of SNMP for end-user system 687 interaction and for management generally, and cross-vendor 688 management systems manage fleets of printers in enterprises. 689 Power consumption during active modes can vary widely, with high 690 peak levels. 692 Printers can expose detailed power state information, distinct 693 from operational state information, with some printers reporting 694 transition states between stable long-term states. Many also 695 support active setting of power states, and setting of policies 696 such as delay times when no activity will cause automatic 697 transition to a lower power mode. Other features include 698 reporting on components, counters for state transitions, typical 699 power levels by state, scheduling, and events/alarms. 701 Some large printers also have a "Digital Front End" which is a 702 computer that performs functions on behalf of the physical 703 imaging system. These typically have their own presence on the 704 network and are sometimes separately powered. 706 There are some unique characteristics of printers from the point 707 of view energy management. While the printer is not in use, 708 there are timer based low power states, which consume very 709 little power. On the other hand, while the printer is printing 710 or copying the cylinder needs to be heated so that power 711 consumption is quite high but only for a short period of time 712 (duration of the print job). Given this work load, periodic 713 polling of power levels alone would not suffice. 715 The essential properties of this use case are: 717 . Target devices: All imaging equipment. 718 . How powered: Typically AC from a wall outlet. 719 . Reporting: Devices report for themselves by implementing 720 [EMAN-MONITORING-MIB]. 722 2.12. Off-Grid Devices 724 This use case concerns self-contained devices that use energy 725 but are not connected to an infrastructure power delivery grid. 726 These devices typically scavenge energy from environmental 727 sources such as solar energy or wind power. The device generally 728 contains a closely coupled combination of 730 . power scavenging or generation component(s) 731 . power storage component(s) (e.g., battery) 732 . power consuming component(s) 734 With scavenged power, the energy input is often dependent on the 735 random variations of the weather. These devices therefore 736 require energy management both for internal control and remote 737 reporting of their state. In order to optimize the performance 738 of these devices and minimize the costs of the generation and 739 storage components, it is desirable to vary the activity level, 740 and, hopefully, the energy requirements of the consuming 741 components in order to make best use of the available stored and 742 instantaneously generated energy. With appropriate energy 743 management, the overall device can be optimized to deliver an 744 appropriate level of service without over provisioning the 745 generation and storage components. 747 In many cases these devices are expected to operate 748 autonomously, as continuous communications for the purposes of 749 remote control is either impossible or would result in excessive 750 power consumption. Non continuous polling requires the ability 751 to store and access later the information collected while the 752 communication was not possible. 754 The essential properties of this use case are: 756 Target Devices: Remote network devices (mobile network) that 757 consume and produce energy 758 How Powered: Can be battery powered or using natural energy 759 sources 760 Reporting: Devices report their power usage but only 761 occasionally. 763 2.13. Demand/Response 765 Demand/Response from the utility or grid is a common theme that 766 spans across some of the use cases. In some situations, in 767 response to time-of-day fluctuation of energy costs or sudden 768 energy shortages due power outages, it may be important to 769 respond and reduce the energy consumption of the network. 770 From EMAN use case perspective, the demand/response scenario can 771 apply to a Data Center or a Building or a residential home. As a 772 first step, it may be important to monitor the energy 773 consumption in real-time of a Data center, building or home 774 which is already discussed in the previous use cases. Then based 775 on the potential energy shortfall, the Energy Management System 776 (EMS) could formulate a suitable response, i.e., the EMS could 777 shut down some selected devices that may be considered 778 discretionary or uniformly reduce the power supplied to all 779 devices. For multi-site data centers it may be possible to 780 formulate policies such as follow-the-moon type of approach, by 781 scheduling the mobility of VMs across Data centers in different 782 geographical locations. 784 2.14. Power Capping 786 Power capping is a technique to limit the total power 787 consumption of a server. This technique can be useful for power 788 limited data centers. Based on workload measurements, the server 789 can choose the optimal power state of the server in terms of 790 performance and power consumption. When the server operates at 791 less than the power supply capacity, it runs at full speed. When 792 the server power would be greater than the power supply 793 capacity, it runs at a slower speed so that its power 794 consumption matches the available power supply capacity. This 795 gives vendors the option to use smaller, cost-effective power 796 supplies that allow real world workloads to run at nominal 797 themselves. 799 3. Use Case Patterns 801 The use cases presented above can be abstracted to the following 802 broad patterns. 804 3.1. Metering 806 -energy objects which have capability for internal metering 807 - energy objects which are metered by an external device 809 3.2. Metering and Control 811 - energy objects that do not supply power, but can perform only 812 power metering for other devices 814 - energy objects that do not supply power, but can perform both 815 metering and control for other devices 817 3.3. Power Supply, Metering and Control 819 - energy objects that supply power for other devices but do not 820 perform power metering for those devices 822 - energy objects that supply power for other devices and also 823 perform power metering 825 - energy objects supply power for other devices and also perform 826 power metering and control for other devices 828 3.4. Multiple Power Sources 830 - energy objects that have multiple power sources and metering 831 and control is performed by one source 833 - energy objects that have multiple power sources and metering 834 is performed by one source and control another source 836 4. Relationship of EMAN to other Standards 838 EMAN as a framework is tied to other standards and efforts that 839 deal with energy. Existing standards are leveraged when 840 possible. EMAN helps enable adjacent technologies such as Smart 841 Grid. 843 The standards most relevant and applicable to EMAN are listed 844 below with a brief description of their objectives, the current 845 state and how that standard relates to EMAN. 847 4.1. Data Model and Reporting 849 4.1.1. IEC - CIM 851 The International Electro-technical Commission (IEC) has 852 developed a broad set of standards for power management. Among 853 these, the most applicable to EMAN is IEC 61850, a standard for 854 the design of electric utility automation. The abstract data 855 model defined in 61850 is built upon and extends the Common 856 Information Model (CIM). The complete 61850 CIM model includes 857 over a hundred object classes and is widely used by utilities 858 worldwide. 860 This set of standards was originally conceived to automate 861 control of a substation (facilities which transfer electricity 862 from the transmission to the distribution system). While the 863 original domain of 61850 is substation automation, the extensive 864 data model has been widely used in other domains, including 865 Energy Management Systems (EMS). 867 IEC TC57 WG19 is an ongoing working group to harmonize the CIM 868 data model and 61850 standards. 870 Concepts from IEC Standards have been reused in the EMAN WG 871 drafts. In particular, AC Power Quality measurements have been 872 reused from IEC 61850-7-4. The concept of Accuracy Classes for 873 measure of power and energy has been adapted from ANSI C12.20 874 and IEC standards 62053-21 and 62053-22. 876 4.1.2. DMTF 878 The Distributed Management Task Force (DMTF)[DMTF] has 879 standardized management solutions for managing servers and PCs, 880 including power-state configuration and management of elements 881 in a heterogeneous environment. These specifications provide 882 physical, logical and virtual system management requirements for 883 power-state control. 885 The EMAN Framework references the DMTF Power Profile and Power 886 State Set. 888 4.1.2.1. Common Information Model Profiles 890 The DMTF uses CIM-based (Common Information Model) 'Profiles' to 891 represent and manage power utilization and configuration of 892 managed elements (note that this is not the 61850 CIM). Key 893 profiles for energy management are 'Power Supply' (DSP 1015), 894 'Power State' (DSP 1027) and 'Power Utilization Management' (DSP 895 1085).These profiles define monitoring and configuration of a 896 Power Managed Element's static and dynamic power saving modes, 897 power allocation limits and power states, among other features. 899 Reduced power modes can be established as static or dynamic. 900 Static modes are fixed policies that limit power use or 901 utilization. Dynamic power saving modes rely upon internal 902 feedback to control power consumption. 904 Power states are eight named operational and non operational 905 levels. These are On, Sleep-Light, Sleep-Deep, Hibernate, Off- 906 Soft, and Off-Hard. Power change capabilities provide 907 immediate, timed interval, and graceful transitions between on, 908 off, and reset power states. Table 3 of the Power State Profile 909 defines the correspondence between the ACPI and DMTF power state 910 models, although it is not necessary for a managed element to 911 support ACPI. Optionally, a TransitingToPowerState property can 912 represent power state transitions in progress. 914 4.1.2.2. DASH 916 DMTF DASH [DASH] (Desktop And Mobile Architecture for System 917 Hardware) addresses managing heterogeneous desktop and mobile 918 systems (including power) via in-band and out-of-band 919 communications. DASH provides management and control of managed 920 elements like power, CPU, etc. using the DMTF's WS-Management 921 web services and CIM data model. 923 Both in service and out-of-service systems can be managed with 924 the DASH specification in a fully secured remote environment. 925 Full power lifecycle management is possible using out-of-band 926 management. 928 4.1.3. ODVA 930 The Open DeviceNet Vendors Association (ODVA) is an association 931 for industrial automation companies and defines the Common 932 Industrial Protocol (CIP). Within ODVA, there is a special 933 interest group focused on energy. 935 The Open DeviceNet Vendors Association (ODVA) is developing an 936 energy management framework for the industrial sector. There 937 are synergies between the ODVA and EMAN approaches to energy 938 management. 940 There are many similar concepts between the ODVA and EMAN 941 frameworks towards monitoring and management of energy aware 942 devices. In particular, one of the concepts being considered 943 different energy meters based on if the device consumes 944 electricity or produces electricity or a passive device. 946 ODVA defines a three-part approach towards energy management: 947 awareness of energy usage, consuming energy more efficiently, 948 and exchanging energy with the utility or others. Energy 949 monitoring and management promote efficient consumption and 950 enable automating actions that reduce energy consumption. 952 The foundation of the approach is the information and 953 communication model for entities. An entity is a network- 954 connected, energy-aware device that has the ability to either 955 measure or derive its energy usage based on its native 956 consumption or generation of energy, or report a nominal or 957 static energy value. 959 4.1.4. Ecma SDC 961 The Ecma International committee on Smart Data Centre (TC38-TG2 962 SDC [Ecma-SDC]) is in the process of defining semantics for 963 management of entities in a data center such as servers, 964 storage, and network equipment. It covers energy as one of many 965 functional resources or attributes of systems for monitoring and 966 control. It only defines messages and properties, and does not 967 reference any specific protocol. Its goal is to enable 968 interoperability of such protocols as SNMP, BACNET, and HTTP by 969 ensuring a common semantic model across them. Four power states 970 are defined, Off, Sleep, Idle and Active. The standard does not 971 include actual energy or power measurements in kWor kWh. 973 The 14th draft of SDC process was published in March 2011 and 974 the development of the standard is still underway. When used 975 with EMAN, the SDC standard will provide a thin abstraction on 976 top of the more detailed data model available in EMAN. 978 4.1.5. IEEE-ISTO Printer Working Group (PWG) 980 The IEEE-ISTO Printer Working Group (PWG) defines SNMP MIB 981 modules for printer management and has recently defined a "PWG 982 Power Management Model for Imaging Systems v1.0" [PWG5106.4] and 983 a companion SNMP binding in the "PWG Imaging System Power MIB 984 v1.0" [PWG5106.5]. This PWG model and MIB are harmonized with 985 the DMTF CIM Infrastructure [DSP0004] and DMTF CIM Power State 986 Management Profile [DSP1027] for power states and alerts. 988 The PWG would like its MIBs to be harmonized as closely as 989 possible with those from EMAN. The PWG covers many topics in 990 greater detail than EMAN, as well as some that are specific to 991 imaging equipment. The PWG also provides for vendor-specific 992 extension states (i.e., beyond the standard DMTF CIM states.) 994 4.1.6. ASHRAE 996 In the U.S., there is an extensive effort to coordinate and 997 develop standards related to the "Smart Grid". The Smart Grid 998 Interoperability Panel, coordinated by the government's National 999 Institute of Standards and Technology, identified the need for a 1000 building side information model (as a counterpart to utility 1001 models) and specified this in Priority Action Plan (PAP) 17. 1002 This was designated to be a joint effort by American Society of 1003 Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE) 1004 and National Electrical Manufacturers Association (NEMA), both 1005 ANSI approved SDO's. The result is to be an information model, 1006 not a device level monitoring protocol. 1008 The ASHRAE effort addresses data used only within a building as 1009 well as data that may be shared with the grid, particularly as 1010 it relates to coordinating future demand levels with the needs 1011 of the grid. The model is intended to be applied to any 1012 building type, both residential and commercial. It is expected 1013 that existing protocols will be adapted to comply with the new 1014 information model, as would any new protocols. 1016 There are four basic types of entities in the model: generators, 1017 loads, meters, and energy managers. 1019 The metering part of this model overlaps with the EMAN framework 1020 to a large degree, though there are features unique to each. 1021 The load part speaks to control capabilities well beyond what 1022 EMAN covers. Details of generation and of the energy management 1023 function are outside of EMAN scope. 1025 A public review draft of the ASHRAE standard is expected soon, 1026 and at that point detailed comparison of the two models can be 1027 made. There are no apparent major conflicts between the two 1028 approaches, but there are likely areas where some harmonization 1029 is possible, and regardless, a description of the 1030 correspondences would be helpful to create. 1032 4.1.7. ZigBee 1034 The Zigbee Smart Energy 2.0 effort[ZIGBEE] focuses on wireless 1035 communication to appliances and lighting. Zigbee 1.x is not 1036 based on IP, whereas Zigbee 2.0 is supposed to interoperate with 1037 IP. It is intended to enable building energy management and 1038 enable direct load control by utilities. 1040 ZigBee protocols are intended for use in embedded applications 1041 requiring low data rates and low power consumption. ZigBee 1042 defines a general-purpose, inexpensive, self-organizing mesh 1043 network that can be used for industrial control, embedded 1044 sensing, medical data collection, smoke and intruder warning, 1045 building automation, home automation, etc. 1047 Zigbee is currently not an ANSI recognized SDO. 1049 The EMAN framework addresses the needs of IP-enabled networks 1050 through the usage of SNMP, while Zigbee looks for completely 1051 integrated and inexpensive mesh solution. 1053 4.2. Measurement 1055 4.2.1. ANSI C12 1057 The American National Standards Institute (ANSI) has defined a 1058 collection of power meter standards under ANSI C12. The primary 1059 standards include communication protocols (C12.18, 21 and 22), 1060 data and schema definitions (C12.19), and measurement accuracy 1061 (C12.20). European equivalent standards are provided by IEC 1062 62053-22.ANSI C12.20 defines accuracy classes for watt-hour 1063 meters. 1065 All of these standards are oriented toward the meter itself, and 1066 are therefore very specific and used by electricity distributors 1067 and producers. 1069 The EMAN standard references ANSI C12 accuracy classes. 1071 4.2.2. IEC 1073 IEC 62301, "Household electrical appliances Measurement of 1074 standby power", [IEC62301] specifies a power level measurement 1075 procedure. While nominally for appliances and low-power modes, 1076 many aspects of it apply to other device types and modes and it 1077 is commonly referenced in test procedures for energy using 1078 products. 1080 While the standard is intended for laboratory measurements of 1081 devices in controlled conditions, many aspects of it are 1082 informative to those implementing measurement in products that 1083 ultimately report via EMAN. 1085 4.3. Other 1087 4.3.1. ISO 1089 The ISO [ISO] is developing an energy management standard, ISO 1090 50001, to complement ISO 9001 for quality management, and ISO 1091 14001 for environment management. The intent of the framework is 1092 to facilitate the creation of energy management programs for 1093 industrial, commercial and other entities. The standard defines 1094 a process for energy management at an organization level. It 1095 does not define the way in which devices report energy and 1096 consume energy. 1098 ISO 50001 is based on the common elements found in all of ISO's 1099 management system standards, assuring a high level of 1100 compatibility with ISO 9001 (quality management) and ISO 14001 1101 (environmental management). ISO 50001 benefits includes: 1103 o Integrating energy efficiency into management practices and 1104 throughout the supply chain 1106 o Energy management best practices and good energy management 1107 behaviors 1108 o benchmarking, measuring, documenting, and reporting energy 1109 intensity improvements and their projected impact on 1110 reductions in greenhouse gas (GHG) emissions 1111 o Evaluating and prioritizing the implementation of new energy- 1112 efficient technologies 1114 ISO 50001 has been developed by ISO project committee ISO/PC 1115 242, Energy management. EMAN is complementary to ISO 9001. 1117 4.3.2. EnergyStar 1119 The US Environmental Protection Agency (EPA) and US Department 1120 of Energy (DOE) jointly sponsor the Energy Star program [ESTAR]. 1121 The program promotes the development of energy efficient 1122 products and practices. 1124 To qualify as Energy Star, products must meet specific energy 1125 efficiency targets. The Energy Star program also provides 1126 planning tools and technical documentation to encourage more 1127 energy efficient building design. Energy Star is a program; it 1128 is not a protocol or standard. 1130 For businesses and data centers, Energy Star offers technical 1131 support to help companies establish energy conservation 1132 practices. Energy Star provides best practices for measuring 1133 current energy performance, goal setting, and tracking 1134 improvement. The Energy Star tools offered include a rating 1135 system for building performance and comparative benchmarks. 1137 There is no immediate link between EMAN and EnergyStar, one 1138 being a protocol and the other a set of recommendations to 1139 develop energy efficient products. However, Energy Star could 1140 include EMAN standards in specifications for future products, 1141 either as required or rewarded with some benefit. 1143 4.3.3. SmartGrid 1145 The Smart Grid standards efforts underway in the United States 1146 are overseen by the US National Institute of Standards and 1147 Technology [NIST].NIST is responsible for coordinating a public- 1148 private partnership with key energy and consumer stakeholders in 1149 order to facilitate the development of smart grid standards. The 1150 NIST smart grid standards activities are monitored and 1151 facilitated by the SGIP (Smart Grid Interoperability Panel). 1153 This group has working groups for specific topics including 1154 homes, commercial buildings, and industrial facilities as they 1155 relate to the grid. A stated goal of the group is to harmonize 1156 any new standard with the IEC CIM and IEC 61850. 1158 When a working group detects a standard or technology gap, the 1159 team seeks approval from the SGIP for the creation of a Priority 1160 Action Plan (PAP), a private-public partnership to close the 1161 gap. There are currently 17 PAPs. PAP 17 is discussed in 1162 section 4.1.6. 1164 PAP 10 addresses "Standard Energy Usage Information". 1165 Smart Grid standards will provide distributed intelligence in 1166 the network and allow enhanced load shedding. For example, 1167 pricing signals will enable selective shutdown of non critical 1168 activities during peak-load pricing periods. These actions can 1169 be effected through both centralized and distributed management 1170 controls. 1172 There is an obvious functional link between SmartGrid and EMAN 1173 in the form of demand response, even if the EMAN framework does 1174 not take any specific step toward SmartGrid communication. As 1175 EMAN framework enables control, it can be used to realize power 1176 savings in the demand response through translation of a signal 1177 from an outside entity. 1179 5. Limitations 1181 EMAN Framework addresses the needs of energy monitoring in terms 1182 of measurement and, considers limited control capabilities of 1183 energy monitoring of networks. 1185 EMAN does not create a new protocol stack, but rather defines a 1186 data and information model useful for measuring and reporting 1187 energy and other metrics over SNMP. 1189 The EMAN framework does not address questions regarding 1190 SmartGrid, electricity producers, and distributors even if there 1191 is obvious link between them. 1193 6. Security Considerations 1195 EMAN shall use SNMP protocol for energy management and thus has 1196 the functionality of SNMP's security capabilities. SNMPv3 1197 [RFC3411] provides important security features such as 1198 confidentiality, integrity, and authentication. 1200 7. IANA Considerations 1202 This memo includes no request to IANA. 1204 8. Acknowledgements 1206 Firstly, the authors would like thank Emmanuel Tychon for taking 1207 the lead for this draft and his contributions towards to this 1208 draft. 1210 The authors would like to thank Jeff Wheeler, Benoit Claise, 1211 Juergen Quittek, Chris Verges, John Parello, and Matt Laherty, 1212 for their valuable contributions. 1214 The authors would like to thank Georgios Karagiannis for use 1215 case involving energy neutral homes, Elwyn Davies for off-grid 1216 electricity systems, and Kerry Lynn for the comment on the 1217 Demand/Response scenario. 1219 9. Open Issues 1221 OPEN ISSUE 1: Should review ASHRAE SPC 201P standard when it is 1222 released for public review 1224 . Need to review ASHRAE information model and the use cases 1225 and how it relates to EMAN 1227 OPEN ISSUE 2: Should the Applicability Statement cover concepts 1228 that are only developed to implement the requirements in the 1229 framework, or only cover concepts that already are well-defined? 1231 10. References 1233 10.1. Normative References 1235 [RFC3411] An Architecture for Describing Simple Network 1236 Management Protocol (SNMP) Management Frameworks, RFC 1237 3411, December 2002. 1239 [RFC3621] Power Ethernet MIB, RFC 3621, December 2003. 1241 10.2. Informative References 1243 [DASH] "Desktop and mobile Architecture for System Hardware", 1244 http://www.dmtf.org/standards/mgmt/dash/ 1246 [NIST] http://www.nist.gov/smartgrid/ 1248 [Ecma-SDC] Ecma TC38 / SDC Task Group, "Smart Data Centre 1249 Resource Monitoring and Control (DRAFT)", March 2011. 1251 [EMAN-AS] Tychon, E., B. Schoening, Mouli Chandramouli, Bruce 1252 Nordman, "Energy Management (EMAN) Applicability 1253 Statement", draft-ietf-eman-applicability-statement- 1254 00.txt, December 2011. 1256 [EMAN-REQ] Quittek, J., Winter, R., Dietz, T., Claise, B., and 1257 M. Chandramouli, "Requirements for Energy Management ", 1258 draft-ietf-eman-requirements-06 (work in progress), 1259 March 2012. 1261 [EMAN-MONITORING-MIB] M. Chandramouli, Schoening, B., Dietz, T., 1262 Quittek, J. and B. Claise "Energy and Power Monitoring 1263 MIB ", draft-ietf-eman-energy-monitoring-mib-02, 1264 March 2012. 1266 [EMAN-AWARE-MIB] J. Parello, and B. Claise, "draft-ietf-eman- 1267 energy-aware-mib-05", work in progress, March 2012. 1269 [EMAN-FRAMEWORK] Claise, B., Parello, J., Schoening, B., J. 1270 Quittek and B. Nordman, "Energy Management Framework", 1271 draft-ietf-eman-framework-04, March 2012. 1273 [EMAN-BATTERY-MIB] Quittek, J., Winter, R., and T. Dietz, 1274 "Definition of Managed Objects for Battery Monitoring" 1275 draft-ietf-eman-battery-mib-05.txt, March 2012.. 1277 [EMAN-DEF] J. Parello "Energy Management Terminology", draft- 1278 parello-eman-definitions-05, Work in progress, March 1279 2012. 1281 [DMTF] "Power State Management ProfileDMTFDSP1027 Version 2.0" 1282 December2009. 1283 http://www.dmtf.org/sites/default/files/standards/docum 1284 ents/DSP1027_2.0.0.pdf 1286 [ESTAR] http://www.energystar.gov/ 1288 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1434 1290 [ASHRAE] http://collaborate.nist.gov/twiki- 1291 sggrid/bin/view/SmartGrid/PAP17Information 1293 [ZIGBEE] http://www.zigbee.org/ 1295 [ISO] http://www.iso.org/iso/pressrelease.htm?refid=Ref1337 1297 [DSP0004] DMTF Common Information Model (CIM) Infrastructure, 1298 DSP0004, May 2009. 1299 http://www.dmtf.org/standards/published_documents/DSP00 1300 04_2.5.0.pdf 1302 [DSP1027] DMTF Power State Management Profile, DSP1027, December 1303 2009. 1304 http://www.dmtf.org/standards/published_documents/DSP10 1305 27_2.0.0.pdf 1307 [PWG5106.4] IEEE-ISTO PWG Power Management Model for Imaging 1308 Systems v1.0, PWG Candidate Standard 5106.4-2011, 1309 February 2011.ftp://ftp.pwg.org/pub/pwg/candidates/cs- 1310 wimspower10-20110214-5106.4.mib 1312 [PWG5106.5] IEEE-ISTO PWG Imaging System Power MIB v1.0, PWG 1313 Candidate Standard 5106.5-2011, February 2011. 1315 [IEC62301] International Electrotechnical Commission, "IEC 62301 1316 Household electrical appliances Measurement of standby 1317 power", Edition 2.0, 2011. 1319 [MODBUS-Protocol] Modbus-IDA, "MODBUS Application Protocol 1320 Specification V1.1b", December 2006. 1322 Authors' Addresses 1324 Brad Schoening 1325 44 Rivers Edge Drive 1326 Little Silver, NJ 07739 1327 USA 1328 Email:brad@bradschoening.com 1330 Mouli Chandramouli 1331 Cisco Systems, Inc. 1332 Sarjapur Outer Ring Road 1333 Bangalore, 1334 India 1335 Phone: +91 80 4426 3947 1336 Email: moulchan@cisco.com 1338 Bruce Nordman 1339 Lawrence Berkeley National Laboratory 1340 1 Cyclotron Road, 90-4000 1341 Berkeley 94720-8136 1342 USA 1344 Phone: +1 510 486 7089 1345 Email: bnordman@lbl.gov