Energy Management Terminology
draft-parello-eman-definitions-04
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Author | John Parello | ||
| Last updated | 2011-12-04 (Latest revision 2011-10-26) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-parello-eman-definitions-04
Network Working Group
Internet-Draft J. Parello
Intended Status: Informational Cisco Systems, Inc.
Expires: June 4, 2012 December 4, 2011
Energy Management Terminology
draft-parello-eman-definitions-04
Status of this Memo
This Internet-Draft is submitted to IETF in full
conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its
working groups. Note that other groups may also
distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a
maximum of six months and may be updated, replaced, or
obsoleted by other documents at any time. It is
inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be
accessed at http://www.ietf.org/shadow.html
This Internet-Draft will expire on February, 2012.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons
identified as the document authors. All rights
reserved.
This document is subject to BCP 78 and the IETF
Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on
the date of publication of this document. Please
review these documents carefully, as they describe
your rights and restrictions with respect to this
document. Code Components extracted from this
document must include Simplified BSD License text as
described in Section 4.e of the Trust Legal Provisions
<Parello> Expires June 4, 2012 [Page 1]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
and are provided without warranty as described in the
Simplified BSD License.
Abstract
This document contains definitions and terms used in
the Energy Management Working Group. Each term
contains a definition(s), example, and reference to a
normative, informative or well know source. Terms
originating in this draft should be either composed of
or adapted from other terms in the draft with a
source. The defined terms will then be used in other
drafts as defined here.
<parello> Expires June 4, 2012 [Page 2]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
Table of Contents
1. Introduction............................................. 3
2. Terminology.............................................. 5
Energy Management........................................ 5
Energy Management System (EnMS).......................... 5
ISO Energy Management System............................. 6
Energy................................................... 6
Power.................................................... 7
Demand................................................... 7
Power Quality............................................ 7
Electrical Equipment..................................... 8
Non-Electrical Equipment (Mechanical Equipment).......... 8
Energy Object............................................ 8
Electrical Energy Object................................. 8
Non-Electrical Energy Object............................. 9
Energy Monitoring........................................ 9
Energy Control........................................... 9
Energy Management Domain................................. 9
Energy Object Identification............................ 10
Energy Object Context................................... 10
Energy Object Relationship.............................. 10
Aggregation Relationship................................ 11
Metering Relationship................................... 11
Power Source Relationship............................... 11
Proxy Relationship...................................... 12
Dependency Relationship................................. 12
Energy Object Parent.................................... 12
Energy Object Child..................................... 12
Power State............................................. 13
Power State Set......................................... 13
Nameplate Power......................................... 13
3. Security Considerations................................. 14
4. IANA Considerations..................................... 14
5. Acknowledgments......................................... 14
6. References.............................................. 14
Normative References.................................... 14
Informative References.................................. 14
1. Introduction
Within Energy Management there are terms that may
seem obvious to a casual reader but in fact require a
<parello> Expires June 4, 2012 [Page 3]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
rigorous and sourced definition. To avoid any
confusion in terms among the working group drafts,
one glossary / lexicon of terms should exist that all
drafts can refer to. This will avoid a review of
terms multiplied across drafts.
This draft will contain a glossary of definitions of
terms that can be agreed upon by the working group
outside of the context of drafts and then included in
or sourced to this draft.
Each term will contain a definition(s), a normative
or informative reference, an optional example, an
optional comment(s) listed a note(s).
All terms should be rooted with a well-known
reference. If a definition is taken verbatim from a
reference then the source is listed in square
brackets. If a definition is derived from a well-
known reference then the source is listed as "Adapted
from" with the reference listed in square brackets.
If a defined term is newly defined here the reference
will indicate as such by stating "herein" and if
applicable list any composing terms from this
document.
When applicable the [IEEE100] was used as the
preferred source. If a term was not available from
[IEEE100], then [IEC60050] was used. When these were
multiple items from [IEEE100], [IEC60050] or
[ISO50001], there were all included.
<parello> Expires June 4, 2012 [Page 4]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
2. Terminology
Energy Management
Energy Management is a set of functions for measuring,
modeling, planning, and optimizing networks to ensure
that the network elements and attached devices use
energy efficiently and is appropriate for the nature
of the application and the cost constraints of the
organization.
Reference: Adapted from [ITU-T-M-3400]
Example: A set of computer systems that will poll
electrical meters and store the readings
NOTES:
1. Energy management refers to the activities, methods,
procedures and tools that pertain to measuring,
modeling, planning, controlling and optimizing the
use of energy in networked systems [NMF].
2. Energy Management is a management domain which is
congruent to any of FCAPS areas of management in the
ISO/OSI Network Management Model [TMN]. Energy
Management for communication networks and attached
devices is a subset or part of an organization's
greater Energy Management Policies.
Energy Management System (EnMS)
An Energy Management System is a combination of
hardware and software used to administer a network
with the primarily purpose being Energy Management.
Reference: Adapted from [1037C]
<parello> Expires June 4, 2012 [Page 5]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
Example: A single computer system that polls data from
devices using SNMP
NOTES:
1. An Energy Management System according to [ISO50001]
(ISO-EnMS) is a set of systems or procedures upon
which organizations can develop and implement an
energy policy, set targets, action plans and take
into account legal requirements related to energy
use. An EnMS allows organizations to improve energy
performance and demonstrate conformity to
requirements, standards, and/or legal requirements.
2. Example ISO-EnMS: Company A defines a set of
policies and procedures indicating there should
exist multiple computerized systems that will poll
energy from their meters and pricing / source data
from their local utility. Company A specifies that
their CFO should collect information and summarize
it quarterly to be sent to an accounting firm to
produce carbon accounting reporting as required by
their local government.
3. For the purposes of EMAN, the definition from
[1037C] is the preferred meaning of an Energy
Management System (EnMS). The definition from
[ISO50001] can be referred to as ISO Energy
Management System (ISO-EnMS).
ISO Energy Management System
Energy Management System as defined by [ISO50001]
Reference: herein
Energy
That which does work or is capable of doing work. As
used by electric utilities, it is generally a
reference to electrical energy and is measured in
kilo-watt hours (kWh).
<parello> Expires June 4, 2012 [Page 6]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
Reference: [IEEE100]
NOTES
1. Energy is the capacity of a system to produce
external activity or perform work [ISO50001]
Power
The time rate at which energy is emitted, transferred,
or received; usually expressed in watts (or in joules
per second).
Reference: [IEEE100]
Demand
The average value of power or a related quantity over
a specified interval of time. Note: Demand is
expressed in kilowatts, kilovolt-amperes, kilovars, or
other suitable units.
Reference: [IEEE100]
NOTES:
1. typically kilowatts
2. Energy providers typically bill by Demand
measurements as well as for maximum Demand per
billing periods. Power values may spike during
short-terms by devices, but Demand measurements
recognize that maximum Demand does not equal maximum
Power during an interval.
Power Quality
Characteristics of the electric current, voltage and
frequencies at a given point in an electric power
system, evaluated against a set of reference technical
parameters. These parameters might, in some cases,
<parello> Expires June 4, 2012 [Page 7]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
relate to the compatibility between electricity
supplied in an electric power system and the loads
connected to that electric power system.
Reference: [IEC60050]
Electrical Equipment
A general term including materials, fittings, devices,
appliances, fixtures, apparatus, machines, etc., used
as a part of, or in connection with, an electric
installation.
Reference: [IEEE100]
Non-Electrical Equipment (Mechanical Equipment)
A general term including materials, fittings, devices
appliances, fixtures, apparatus, machines, etc., used
as a part of, or in connection with, non-electrical
power installations.
Reference: Adapted from [IEEE100]
Energy Object
An Energy Object (EO) is a piece of equipment that is
part of or attached to a communications network that
is monitored, controlled, or aids in the management of
another device for Energy Management.
Reference: herein
Electrical Energy Object
An Electrical Energy Object (EEO) is an Energy Object
that is a piece of Electrical Equipment
Reference: herein, Electrical Equipment
<parello> Expires June 4, 2012 [Page 8]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
Non-Electrical Energy Object
A Non-Electrical Energy Object (NEEO) an Energy Object
that is a piece of Non-Electrical Equipment.
Reference: herein, Non-Electrical Equipment.
Energy Monitoring
Energy Monitoring is a part of Energy Management that
deals with collecting or reading information from
Energy Objects to aid in Energy Management.
Reference: herein
NOTES:
1. This could include Energy, Power, Demand, Power
Quality, Context and/or Battery information.
Energy Control
Energy Control is a part of Energy Management that
deals with directing influence over Energy Objects.
Reference: herein
NOTES:
1. Typically in order to optimize or ensure its
efficiency.
Energy Management Domain
An Energy Management Domain is a set of Energy
Objects.
Reference: herein
Example: All EEO's drawing power from the same
distribution panel with the same AC voltage within a
building, or all EEO's in a building for which there
<parello> Expires June 4, 2012 [Page 9]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
is one main meter, would comprise an Energy Management
Domain.
NOTES:
1. Typically, this set will have as members all EO's
that are powered from the same source.
Energy Object Identification
Energy Object Identification is a set of attributes
that enable an Energy Object to be: uniquely
identified among all Energy Management Domains; linked
to other systems; classified as to type, model, and or
manufacturer.
Reference: herein
Energy Object Context
Energy Object Context is a set of attributes that
allow an Energy Management System to classify the use
of the Energy Object within an organization.
Reference: herein
NOTES:
1. The classification could contain the use and/or the
ranking of the Energy Object as compared to other
Energy Objects in the Energy Management Domain.
Energy Object Relationship
An Energy Objects Relationship is a functional
association between one or more Energy Objects
Reference: herein
NOTES
<parello> Expires June 4, 2012 [Page 10]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
1. Relationships can be named and could include
Aggregation, Metering, Power Source, Proxy and
Dependency.
Reference: herein
Aggregation Relationship
An Energy Object may aggregate the Energy Management
information of one or more Energy Objects and is
referred to as an Aggregation Relationship.
Reference: herein
NOTES:
1. Aggregate values may be obtained by reading values
from multiple Energy Objects and producing a single
value of more significant meaning such as average,
count, maximum, median, minimum, mode and most
commonly sum [SQL].
Metering Relationship
An Energy Object may measure the Power or Energy of
another Energy Object(s) and is referred to as a
Metering Relationship.
Reference: herein
Example: a PoE port on a switch measures the Power it
provides to the connected Energy Object.
Power Source Relationship
An Energy Object may be the source of or distributor
of Power to another Energy Object(s) and is referred
to as a Power Source Relationship.
Reference: herein
Example: a PDU provides power for a connected host.
<parello> Expires June 4, 2012 [Page 11]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
Proxy Relationship
An Energy Object that provides Energy Management
capabilities on behalf of another Energy Object is
referred to a Proxy Relationship.
Reference: herein
Example: a protocol gateways device for Building
Management Systems (BMS) with subtended devices.
Dependency Relationship
An Energy Object may be a component of or rely
completely upon another Energy Object to operate and
is referred to as a Dependency Relationship.
Example: A Switch chassis with multiple line cards.
Reference: herein
Energy Object Parent
An Energy Object Parent is an Energy Object that
participates in an Energy Object Relationships and is
considered as providing the capabilities in the
relationship.
Reference: herein
Energy Object Child
An Energy Object Child is an Energy Object that
participates in an Energy Object Relationships and is
considered as receiving the capabilities in the
relationship.
Reference: herein
<parello> Expires June 4, 2012 [Page 12]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
Power State
A Power State is a condition or mode of a device that
broadly characterizes its capabilities, power
consumption, and responsiveness to input.
Reference: Adapted from [IEEE1621]
NOTES:
1. A Power State can be seen as a power setting of an
Energy Object that influences the power
consumption, the available functionality, and the
responsiveness of the Energy Object.
2. A Power State can be viewed as one method for
Energy Control
Power State Set
A collection of Power States that comprise one named
or logical grouping of control is a Power State Set.
Reference: herein
Example: The states {on, off, and sleep} as defined in
[IEEE1621], or the 16 power states as defined by the
[DMTF] can be considered two different Power State
Sets.
Nameplate Power
The Nameplate Power is the maximal (nominal) Power
that a device can support.
Reference: herein
NOTES:
1. This is typically determined via load testing and
is specified by the manufacturer as the maximum
value required for operating the device. This is
sometimes referred to as the worst-case Power. The
actual or average Power may be lower. The
<parello> Expires June 4, 2012 [Page 13]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
Nameplate Power is typically used for provisioning
and capacity planning.
3. Security Considerations
None
4. IANA Considerations
None
5. Acknowledgments
The author would like to thank the authors of the
current working group drafts for the discussions and
definition clarifications
6. References
Normative References
Informative References
[IEEE100] "The Authoritative Dictionary of IEEE
Standards Terms"
http://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?pun
umber=4116785
[IEEE1621] "Standard for User Interface Elements in
Power Control of Electronic Devices Employed
in Office/Consumer Environments", IEEE 1621,
December 2004.
[IEC60050] International Electrotechnical Vocabulary
http://www.electropedia.org/iev/iev.nsf/welco
me?openform
[ISO50001] "ISO 50001:2011 Energy management systems -
Requirements with guidance for use",
http://www.iso.org/
[DMTF] "Power State Management Profile DMTF DSP1027
Version 2.0" December 2009
<parello> Expires June 4, 2012 [Page 14]
Internet-Draft <draft-parello-eman-definitions> Dec 2011
http://www.dmtf.org/sites/default/files/stand
ards/documents/DSP1027_2.0.0.pdf
[TMN] "TMN Management Functions : Performance
Management", ITU-T M.3400
[NMF] "Network Management Fundamentals", Alexander
Clemm, ISBN: 1-58720-137-2, 2007
[ITU-T-M-3400] TMN recommandation on Management
Functions (M.3400), 1997
[1037C] US Department of Commerce, Federal Standard
1037C, http://www.its.bldrdoc.gov/fs-1037/fs-
1037c.htm
[SQL] ISO/IEC 9075(1-4,9-11,13,14):2008
7. Authors' Addresses
John Parello
Cisco Systems, Inc.
3550 Cisco Way
San Jose, California 95134
US
Phone: +1 408 525 2339
Email: jparello@cisco.com
<parello> Expires June 4, 2012 [Page 15]