idnits 2.17.1 draft-parello-eman-definitions-09.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 10 longer pages, the longest (page 3) being 67 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 53 has weird spacing: '...ch term conta...' -- The document date (October 19, 2013) is 3813 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Parello 3 Internet-Draft Cisco Systems, Inc. 4 Intended Status: Informational 5 Expires: April 19, 2014 October 19, 2013 7 Energy Management Terminology 8 draft-parello-eman-definitions-09 10 Status of this Memo 12 This Internet-Draft is submitted in full conformance with 13 the provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet 16 Engineering Task Force (IETF), its areas, and its working 17 groups. Note that other groups may also distribute working 18 documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of 21 six months and may be updated, replaced, or obsoleted by 22 other documents at any time. It is inappropriate to use 23 Internet-Drafts as reference material or to cite them other 24 than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be 30 accessed at http://www.ietf.org/shadow.html 32 This Internet-Draft will expire on April 19, 2014. 34 Copyright Notice 36 Copyright (c) 2013 IETF Trust and the persons identified as 37 the document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's 40 Legal Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the 42 date of publication of this document. Please review these 43 documents carefully, as they describe your rights and 44 restrictions with respect to this document. Code Components 45 extracted from this document must include Simplified BSD 46 License text as described in Section 4.e of the Trust Legal 47 Provisions and are provided without warranty as described 48 in the Simplified BSD License. 50 Abstract 52 This document contains definitions and terms used in the 53 Energy Management Working Group. Each term contains a 54 definition(s), example, and reference to a normative, 55 informative or well know source. Terms originating in this 56 draft should be either composed of or adapted from other 57 terms in the draft with a source. The defined terms will 58 then be used in other drafts as defined here 60 Table of Contents 62 1. Introduction.......................................... 63 3 64 2. Terminology........................................... 65 3 66 3. Relationship to Other Standards....................... 67 9 68 4. Security Considerations............................... 69 9 70 5. IANA Considerations................................... 71 9 72 6. References............................................ 73 9 74 7. Acknowledgments...................................... 75 10 77 1. Introduction 79 Within Energy Management there are terms that may seem 80 obvious to a casual reader but in fact require a rigorous 81 and sourced definition. To avoid any confusion in terms 82 among the working group drafts, one glossary / lexicon of 83 terms should exist that all drafts can refer to. This will 84 avoid a review of terms multiplied across drafts. 86 This draft will contain a glossary of definitions of terms 87 that can be agreed upon by the working group outside of the 88 context of drafts and then included in or sourced to this 89 draft. 91 Each term will contain a definition(s), a normative or 92 informative reference, an optional example, an optional 93 comment(s) listed a note(s). 95 All terms should be rooted with a well-known reference. If 96 a definition is taken verbatim from a reference then the 97 source is listed in square brackets. If a definition is 98 derived from a well-known reference then the source is 99 listed as "Adapted from" with the reference listed in 100 square brackets. If a defined term is newly defined here 101 the reference will indicate as such by stating "herein" and 102 if applicable list any composing terms from this document. 104 The terms are listing in an order that aids in reading 105 where terms may build off a previous term as opposed to an 106 alphabetical ordering. Some terms that are common in 107 electrical engineering or that describe common physical 108 items use a lower case notation. 110 2. Terminology 112 $ Energy Management 113 Energy Management is a set of functions for measuring, 114 modeling, planning, and optimizing networks to ensure 115 that the network and network attached devices use energy 116 efficiently and appropriately for the nature of the 117 application and the cost constraints of the organization. 119 Reference: Adapted from [ITU-T-M-3400] 121 NOTES: 122 1. Energy management refers to the activities, methods, 123 procedures and tools that pertain to measuring, modeling, 124 planning, controlling and optimizing the use of energy in 125 networked systems [NMF]. 127 2. Energy Management is a management domain which is 128 congruent to any of the FCAPS areas of management in the 129 ISO/OSI Network Management Model [TMN]. Energy Management 130 for communication networks and attached devices is a 131 subset or part of an organization's greater Energy 132 Management Policies. 134 $ Energy Management System (EnMS) 135 An Energy Management System is a combination of hardware 136 and software used to administer a network with the 137 primary purpose of energy management. 139 Reference: Adapted from [1037C] 141 NOTES: 142 1. An Energy Management System according to [ISO50001] 143 (ISO-EnMS) is a set of systems or procedures upon which 144 organizations can develop and implement an energy policy, 145 set targets, action plans and take into account legal 146 requirements related to energy use. An ISO-EnMS allows 147 organizations to improve energy performance and 148 demonstrate conformity to requirements, standards, and/or 149 legal requirements. 151 2. Example ISO-EnMS: Company A defines a set of policies 152 and procedures indicating there should exist multiple 153 computerized systems that will poll energy from their 154 meters and pricing / source data from their local 155 utility. Company A specifies that their CFO should 156 collect information and summarize it quarterly to be sent 157 to an accounting firm to produce carbon accounting 158 reporting as required by their local government. 160 3. For the purposes of EMAN, the definition from [1037C] 161 is the preferred meaning of an Energy Management System 162 (EnMS). The definition from [ISO50001] can be referred to 163 as ISO Energy Management System (ISO-EnMS). 165 $ Energy Monitoring 166 Energy Monitoring is a part of Energy Management that 167 deals with collecting or reading information from Energy 168 Objects to aid in Energy Management. 170 $ Energy Control 171 Energy Control is a part of Energy Management that deals 172 with directing influence over Energy Objects. 174 $ electrical equipment 175 A general term including materials, fittings, devices, 176 appliances, fixtures, apparatus, machines, etc., used as 177 a part of, or in connection with, an electric 178 installation. 179 Reference: [IEEE100] 181 $ non-electrical equipment (mechanical equipment) 182 A general term including materials, fittings, devices 183 appliances, fixtures, apparatus, machines, etc., used as 184 a part of, or in connection with, non-electrical power 185 installations. 187 Reference: Adapted from [IEEE100] 189 $ device 190 A piece of electrical or non-electrical equipment. 191 Reference: Adapted from [IEEE100] 193 $ component 194 A part of an electrical or non-electrical equipment 195 (device). 196 Reference: Adapted from [ITU-T-M-3400] 198 $ power inlet 199 A Power Inlet (or simply inlet) is an interface at which 200 a device or component receives energy from another device 201 or component. 203 $ power outlet 204 A power outlet (or simply outlet) is an interface at 205 which a device or component provides energy to another 206 device or component. 208 $ energy 209 That which does work or is capable of doing work. As used 210 by electric utilities, it is generally a reference to 211 electrical energy and is measured in kilowatt hours 212 (kWh). 214 Reference: [IEEE100] 216 $ power 217 The time rate at which energy is emitted, transferred, or 218 received; usually expressed in watts (joules per second). 220 Reference: [IEEE100] 222 $ demand 223 The average value of power or a related quantity over a 224 specified interval of time. Note: Demand is expressed in 225 kilowatts, kilovolt-amperes, kilovars, or other suitable 226 units. 228 Reference: [IEEE100] 230 NOTES: 231 1. While IEEE100 defines demand in kilo measurements, for 232 EMAN we use watts with any suitable metric prefix. 234 NOTES 235 1. Energy is the capacity of a system to produce external 236 activity or perform work [ISO50001] 238 $ provide energy 239 A device (or component) "provides" energy to another 240 device if there is an energy flow from this device to the 241 other one. 243 $ receive energy 244 A device (or component) "receives" energy from another 245 device if there is an energy flow from the other device 246 to this one. 248 $ meter (energy meter) 249 a device intended to measure electrical energy by 250 integrating power with respect to time. 252 Reference: Adapted from [IEC60050] 254 $ battery 255 one or more cells (consisting of an assembly of 256 electrodes, electrolyte, container, terminals and usually 257 separators) that are a source and/or store of electric 258 energy. 260 Reference: Adapted from [IEC60050] 262 $ Power Interface 263 A power inlet, outlet, or both. 265 $ Nameplate Power 266 The Nameplate Power is the nominal Power of a device as 267 specified by the device manufacturer. 269 $ Power Attributes 270 Measurements of the electrical current, voltage, phase 271 and frequencies at a given point in an electrical power 272 system. 273 Reference: Adapted from [IEC60050] 275 NOTES: 276 1. Power Attributes are not intended to be judgmental 277 with respect to a reference or technical value and are 278 independent of any usage context. 280 $ Power Quality 281 Characteristics of the electrical current, voltage, phase 282 and frequencies at a given point in an electric power 283 system, evaluated against a set of reference technical 284 parameters. These parameters might, in some cases, relate 285 to the compatibility between electricity supplied in an 286 electric power system and the loads connected to that 287 electric power system. 289 Reference: [IEC60050] 291 NOTES: 292 1. Electrical characteristics representing power quality 293 information are typically required by customer facility 294 energy management systems. It is not intended to satisfy 295 the detailed requirements of power quality monitoring. 296 Standards typically also give ranges of allowed values; 297 the information attributes are the raw measurements, not 298 the "yes/no" determination by the various standards. 300 Reference: [ASHRAE-201] 302 $ Power State 303 A Power State is a condition or mode of a device that 304 broadly characterizes its capabilities, power 305 consumption, and responsiveness to input. 307 Reference: Adapted from [IEEE1621] 309 $ Power State Set 310 A Power State Set is a collection of Power States that 311 comprises a named or logical control grouping. 313 $ Energy Object 314 An Energy Object is an information model (class) that 315 represents a piece of equipment that is part of, or 316 attached to, a communications network which is monitored, 317 controlled, or aids in the management of another device 318 for Energy Management. 320 $ Energy Management Domain 321 An Energy Management Domain is a set of Energy Objects 322 that is considered one unit of management. 324 $ Energy Object Identification 325 Energy Object Identification is a set of attributes that 326 enable an Energy Object to be universally unique or 327 linked to other systems. 329 $ Energy Object Context 330 Energy Object Context is a set of attributes that allow 331 an Energy Management System to classify an Energy Object 332 within an organization. 334 $ Energy Object Relationship 335 An Energy Object Relationship is an association among 336 Energy Objects. 338 NOTES 339 1. Relationships can be named and could include 340 Aggregation, Metering, and Power Source. 341 Reference: Adapted from [CHEN] 343 $ Power Source Relationship 344 A Power Source Relationship is an Energy Object 345 Relationship where one Energy Object provides power to 346 one or more Energy Objects. These Energy Objects are 347 referred to as having a Power Source Relationship. 349 $ Metering Relationship 350 A Metering Relationship is an Energy Object Relationship 351 where one Energy Object measures power, energy, demand or 352 power attributes of one or more other Energy Objects. The 353 measuring Energy Object has a Metering Relationship with 354 each of the measured objects. 356 $ Aggregation Relationship 357 An Aggregation Relationship is an Energy Object 358 Relationship where one Energy Object aggregates Energy 359 Management information of one or more other Energy 360 Objects. The aggregating Energy Object has an Aggregation 361 Relationship with each of the other Energy Objects. 363 $ Proxy Relationship 364 A Proxy Relationship is an Energy Object Relationship 365 where one Energy Object provides the Energy Management 366 capabilities on behalf of one or more other Energy 367 Objects. These Energy Objects are referred to as having a 368 Proxy Relationship. 370 3. Relationship to Other Standards 372 When applicable the [IEEE100] was used as the preferred 373 source. If a term was not available from [IEEE100], then 374 [IEC60050] was used. When these were multiple items from 375 [IEEE100], [IEC60050] or [ISO50001], there were all included. 377 4. Security Considerations 379 None 381 5. IANA Considerations 383 None 385 6. References 387 Normative References 389 Informative References 391 [IEEE1621] "Standard for User Interface Elements in Power 392 Control of Electronic Devices Employed in 393 Office/Consumer Environments", IEEE 1621, 394 December 2004 396 [ITU-T-M-3400] TMN recommandation on Management Functions 397 (M.3400), 1997 399 [NMF] "Network Management Fundamentals", Alexander Clemm, 400 ISBN: 1-58720-137-2, 2007 402 [TMN] "TMN Management Functions : Performance Management", 403 ITU-T M.3400 405 [1037C] US Department of Commerce, Federal Standard 1037C, 406 http://www.its.bldrdoc.gov/fs-1037/fs-1037c.htm 408 [IEEE100] "The Authoritative Dictionary of IEEE Standards 409 Terms" 410 http://ieeexplore.ieee.org/xpl/mostRecentIssue.js 411 p?punumber=4116785 413 [ISO50001] "ISO 50001:2011 Energy management systems - 414 Requirements with guidance for use", 415 http://www.iso.org/ 417 [IEC60050] International Electrotechnical Vocabulary 418 http://www.electropedia.org/iev/iev.nsf/welcome?o 419 penform 421 [ASHRAE-201] "ASHRAE Standard Project Committee 201 422 (SPC 201)Facility Smart Grid Information 423 Model", http://spc201.ashraepcs.org 425 [CHEN] "The Entity-Relationship Model: Toward a Unified 426 View of Data", Peter Pin-shan Chen, ACM 427 Transactions on Database Systems, 1976 429 7. Acknowledgments 431 The author would like to thank the authors of the current 432 working group drafts for the discussions and definition 433 clarifications. 435 This document was prepared using 2-Word-v2.0.template.dot. 437 Authors' Addresses 439 John Parello 440 Cisco Systems, Inc. 441 3550 Cisco Way 442 San Jose, California 95134 443 US 445 Phone: +1 408 525 2339 446 Email: jparello@cisco.com