IEEE Power & Energy Magazine - May/June 2014 - 59

all jurisdictions. Having said that, and regardless of a utility's current baselines, operational priorities, and organizational abilities to devise smart grid system integration maps,
the ideal way to approach smart grid system integration is
to analyze each smart grid capability in terms of its core
decision-making and "data-customer/command-supplier"
interface requirements. that analysis will identify to which
domain such functions will belong; to which layer they will
have to reside or be attached; and what their data processing,
command and control, interface protocol, and communication requirements will be.
Figure 4 is an attempt to take the smart grid functions
of Figure 3 and map them across different layers of a fully
integrated smart grid system. in such an approach, smart
grid functions are seen as cutting across multiple layers of
utility structures, including but not limited to corporate,
engineering, field operations, and distribution systems. this
approach turns the utility's traditional silo structures on its
head, as it traverses organizational boundaries for efficient
and cost-effective realization of target smart grid functions.
what is critical in this approach is not how a particular function needs to be realized, but where it belongs as an entity
providing other entities in its vicinity with the services for
which it is designed. association with a given layer will then
determine the performance metrics of the assets needed to
support the efficient operation of that capability.
moreover, the layered approach attempts to identify the
nature of each layer in terms of the dominance of data processing and communication technologies versus the utility's
traditional assets. this does not necessarily mean that a layer
that is dominated by data processing does not depend on
communication technologies or other existing utility assets.
by its nature, each smart grid capability will have to rely on
all three constituent components of the smart grid: power
systems, telecommunication, and information technology.
Furthermore, the layered approach embeds within it the
notion of the temporal and spatial requirements of each layer.
more stringent requirements for access to real-time data will
place a layer closer to layers that produce such data and vice
versa. in other words, the proximity of layers to each other
is directly proportional to their interface and data and command exchange requirements. as an example, the emS and
the volt/var optimization (VVo) and conservation voltage
reduction (CVr) layers have to be in close proximity to each
other and to the field assets with which they have a direct,
real-time, and unimpeded data exchange relationship. the
same is not true for the billing layer, which can be placed
further away from and without a need for real-time connections to field assets.
it goes without saying that not all functions within each
layer need to be integrated at the same time. each utility
could pick and choose one or more functions from each
layer and decide when and how they need to be realized.
regardless of the integration plan for each function, however, what is critical is to understand which layer it will
may/june 2014

belong to-and as such, what its data processing, command and control, interface protocol, and communication
requirements will be. this understanding will ensure that
the architecture of the system, the communication topology,
the adopted technologies, and the associated protocols are
chosen in such a way that they will lend themselves to the
future integration of new functionalities and capabilities.
that is the only way to ensure that the gradual transition to
the smart grid is managed without excessive reengineering
and expensive overhauls.
as discussed, each utility's enterprise function places a
particular set of requirements on different layers of the system in terms of its vital specifications, such as data structures, protocols, security regime, latency, throughput, and,
last but not least, interactions with the actual assets. in reality, of course, applications can and should reside where their
function is required: some will exist within a substation,
some in the utility back office, and others on the enterprise
bus. nevertheless-and regardless of the environment to
which they are attached-each application must have the
ability to communicate seamlessly and efficiently with relevant system nodes as and when required. For instance, an
asset management application has to communicate with all
the relevant assets assigned to it from the different domains
of generation, transmission, and distribution.
as an example, a utility that intends to roll out its smart
meters first and subsequently integrate an asset management application over its vital system assets has to ensure
that the ami system it is integrating will lend itself well
(as a set of distinct assets) to seamless integration with the
asset management application it will be rolling out in the
future. it goes without saying that it would not be acceptable to have patchworks of individual asset management
tools for different categories of assets. in other words, no
utility would be happy using an asset management tool for
its smart meters, another for its relays, switches, reclosers,
and protection components, and yet another for its transmission equipment. one would therefore expect that a major
requirement for the selection of any ami solution would
be its ability to interface with existing or future smart grid
functionalities, enabling on-demand or event-based reporting of the health, configuration, settings, and maintenance
schedule of all ami assets, including meters, head ends,
and communication equipment. Similarly, a utility planning
to implement dynamic pricing and toU tariffs has to ensure
that its ami system is capable of handling and/or relaying
such real-time information for the system's relevant points
of termination.

Realities on the Ground
the approach advocated in Figure 4 is unfortunately not
the norm. it is probable that most utilities will attempt to
integrate smart grid functions with their operations starting at two extreme ends of the system hierarchy: at the bottom of the chain through rollout of ami systems and at
ieee power & energy magazine

59



Table of Contents for the Digital Edition of IEEE Power & Energy Magazine - May/June 2014

IEEE Power & Energy Magazine - May/June 2014 - Cover1
IEEE Power & Energy Magazine - May/June 2014 - Cover2
IEEE Power & Energy Magazine - May/June 2014 - 1
IEEE Power & Energy Magazine - May/June 2014 - 2
IEEE Power & Energy Magazine - May/June 2014 - 3
IEEE Power & Energy Magazine - May/June 2014 - 4
IEEE Power & Energy Magazine - May/June 2014 - 5
IEEE Power & Energy Magazine - May/June 2014 - 6
IEEE Power & Energy Magazine - May/June 2014 - 7
IEEE Power & Energy Magazine - May/June 2014 - 8
IEEE Power & Energy Magazine - May/June 2014 - 9
IEEE Power & Energy Magazine - May/June 2014 - 10
IEEE Power & Energy Magazine - May/June 2014 - 11
IEEE Power & Energy Magazine - May/June 2014 - 12
IEEE Power & Energy Magazine - May/June 2014 - 13
IEEE Power & Energy Magazine - May/June 2014 - 14
IEEE Power & Energy Magazine - May/June 2014 - 15
IEEE Power & Energy Magazine - May/June 2014 - 16
IEEE Power & Energy Magazine - May/June 2014 - 17
IEEE Power & Energy Magazine - May/June 2014 - 18
IEEE Power & Energy Magazine - May/June 2014 - 19
IEEE Power & Energy Magazine - May/June 2014 - 20
IEEE Power & Energy Magazine - May/June 2014 - 21
IEEE Power & Energy Magazine - May/June 2014 - 22
IEEE Power & Energy Magazine - May/June 2014 - 23
IEEE Power & Energy Magazine - May/June 2014 - 24
IEEE Power & Energy Magazine - May/June 2014 - 25
IEEE Power & Energy Magazine - May/June 2014 - 26
IEEE Power & Energy Magazine - May/June 2014 - 27
IEEE Power & Energy Magazine - May/June 2014 - 28
IEEE Power & Energy Magazine - May/June 2014 - 29
IEEE Power & Energy Magazine - May/June 2014 - 30
IEEE Power & Energy Magazine - May/June 2014 - 31
IEEE Power & Energy Magazine - May/June 2014 - 32
IEEE Power & Energy Magazine - May/June 2014 - 33
IEEE Power & Energy Magazine - May/June 2014 - 34
IEEE Power & Energy Magazine - May/June 2014 - 35
IEEE Power & Energy Magazine - May/June 2014 - 36
IEEE Power & Energy Magazine - May/June 2014 - 37
IEEE Power & Energy Magazine - May/June 2014 - 38
IEEE Power & Energy Magazine - May/June 2014 - 39
IEEE Power & Energy Magazine - May/June 2014 - 40
IEEE Power & Energy Magazine - May/June 2014 - 41
IEEE Power & Energy Magazine - May/June 2014 - 42
IEEE Power & Energy Magazine - May/June 2014 - 43
IEEE Power & Energy Magazine - May/June 2014 - 44
IEEE Power & Energy Magazine - May/June 2014 - 45
IEEE Power & Energy Magazine - May/June 2014 - 46
IEEE Power & Energy Magazine - May/June 2014 - 47
IEEE Power & Energy Magazine - May/June 2014 - 48
IEEE Power & Energy Magazine - May/June 2014 - 49
IEEE Power & Energy Magazine - May/June 2014 - 50
IEEE Power & Energy Magazine - May/June 2014 - 51
IEEE Power & Energy Magazine - May/June 2014 - 52
IEEE Power & Energy Magazine - May/June 2014 - 53
IEEE Power & Energy Magazine - May/June 2014 - 54
IEEE Power & Energy Magazine - May/June 2014 - 55
IEEE Power & Energy Magazine - May/June 2014 - 56
IEEE Power & Energy Magazine - May/June 2014 - 57
IEEE Power & Energy Magazine - May/June 2014 - 58
IEEE Power & Energy Magazine - May/June 2014 - 59
IEEE Power & Energy Magazine - May/June 2014 - 60
IEEE Power & Energy Magazine - May/June 2014 - 61
IEEE Power & Energy Magazine - May/June 2014 - 62
IEEE Power & Energy Magazine - May/June 2014 - 63
IEEE Power & Energy Magazine - May/June 2014 - 64
IEEE Power & Energy Magazine - May/June 2014 - 65
IEEE Power & Energy Magazine - May/June 2014 - 66
IEEE Power & Energy Magazine - May/June 2014 - 67
IEEE Power & Energy Magazine - May/June 2014 - 68
IEEE Power & Energy Magazine - May/June 2014 - 69
IEEE Power & Energy Magazine - May/June 2014 - 70
IEEE Power & Energy Magazine - May/June 2014 - 71
IEEE Power & Energy Magazine - May/June 2014 - 72
IEEE Power & Energy Magazine - May/June 2014 - 73
IEEE Power & Energy Magazine - May/June 2014 - 74
IEEE Power & Energy Magazine - May/June 2014 - 75
IEEE Power & Energy Magazine - May/June 2014 - 76
IEEE Power & Energy Magazine - May/June 2014 - 77
IEEE Power & Energy Magazine - May/June 2014 - 78
IEEE Power & Energy Magazine - May/June 2014 - 79
IEEE Power & Energy Magazine - May/June 2014 - 80
IEEE Power & Energy Magazine - May/June 2014 - 81
IEEE Power & Energy Magazine - May/June 2014 - 82
IEEE Power & Energy Magazine - May/June 2014 - 83
IEEE Power & Energy Magazine - May/June 2014 - 84
IEEE Power & Energy Magazine - May/June 2014 - 85
IEEE Power & Energy Magazine - May/June 2014 - 86
IEEE Power & Energy Magazine - May/June 2014 - 87
IEEE Power & Energy Magazine - May/June 2014 - 88
IEEE Power & Energy Magazine - May/June 2014 - 89
IEEE Power & Energy Magazine - May/June 2014 - 90
IEEE Power & Energy Magazine - May/June 2014 - 91
IEEE Power & Energy Magazine - May/June 2014 - 92
IEEE Power & Energy Magazine - May/June 2014 - 93
IEEE Power & Energy Magazine - May/June 2014 - 94
IEEE Power & Energy Magazine - May/June 2014 - 95
IEEE Power & Energy Magazine - May/June 2014 - 96
IEEE Power & Energy Magazine - May/June 2014 - 97
IEEE Power & Energy Magazine - May/June 2014 - 98
IEEE Power & Energy Magazine - May/June 2014 - 99
IEEE Power & Energy Magazine - May/June 2014 - 100
IEEE Power & Energy Magazine - May/June 2014 - 101
IEEE Power & Energy Magazine - May/June 2014 - 102
IEEE Power & Energy Magazine - May/June 2014 - 103
IEEE Power & Energy Magazine - May/June 2014 - 104
IEEE Power & Energy Magazine - May/June 2014 - 105
IEEE Power & Energy Magazine - May/June 2014 - 106
IEEE Power & Energy Magazine - May/June 2014 - 107
IEEE Power & Energy Magazine - May/June 2014 - 108
IEEE Power & Energy Magazine - May/June 2014 - 109
IEEE Power & Energy Magazine - May/June 2014 - 110
IEEE Power & Energy Magazine - May/June 2014 - 111
IEEE Power & Energy Magazine - May/June 2014 - 112
IEEE Power & Energy Magazine - May/June 2014 - 113
IEEE Power & Energy Magazine - May/June 2014 - 114
IEEE Power & Energy Magazine - May/June 2014 - 115
IEEE Power & Energy Magazine - May/June 2014 - 116
IEEE Power & Energy Magazine - May/June 2014 - 117
IEEE Power & Energy Magazine - May/June 2014 - 118
IEEE Power & Energy Magazine - May/June 2014 - 119
IEEE Power & Energy Magazine - May/June 2014 - 120
IEEE Power & Energy Magazine - May/June 2014 - 121
IEEE Power & Energy Magazine - May/June 2014 - 122
IEEE Power & Energy Magazine - May/June 2014 - 123
IEEE Power & Energy Magazine - May/June 2014 - 124
IEEE Power & Energy Magazine - May/June 2014 - 125
IEEE Power & Energy Magazine - May/June 2014 - 126
IEEE Power & Energy Magazine - May/June 2014 - 127
IEEE Power & Energy Magazine - May/June 2014 - 128
IEEE Power & Energy Magazine - May/June 2014 - Cover3
IEEE Power & Energy Magazine - May/June 2014 - Cover4
https://www.nxtbook.com/nxtbooks/pes/powerenergy_091020
https://www.nxtbook.com/nxtbooks/pes/powerenergy_070820
https://www.nxtbook.com/nxtbooks/pes/powerenergy_050620
https://www.nxtbook.com/nxtbooks/pes/powerenergy_030420
https://www.nxtbook.com/nxtbooks/pes/powerenergy_010220
https://www.nxtbook.com/nxtbooks/pes/powerenergy_111219
https://www.nxtbook.com/nxtbooks/pes/powerenergy_091019
https://www.nxtbook.com/nxtbooks/pes/powerenergy_070819
https://www.nxtbook.com/nxtbooks/pes/powerenergy_050619
https://www.nxtbook.com/nxtbooks/pes/powerenergy_030419
https://www.nxtbook.com/nxtbooks/pes/powerenergy_010219
https://www.nxtbook.com/nxtbooks/pes/powerenergy_111218
https://www.nxtbook.com/nxtbooks/pes/powerenergy_091018
https://www.nxtbook.com/nxtbooks/pes/powerenergy_070818
https://www.nxtbook.com/nxtbooks/pes/powerenergy_050618
https://www.nxtbook.com/nxtbooks/pes/powerenergy_030418
https://www.nxtbook.com/nxtbooks/pes/powerenergy_010218
https://www.nxtbook.com/nxtbooks/pes/powerenergy_111217
https://www.nxtbook.com/nxtbooks/pes/powerenergy_091017
https://www.nxtbook.com/nxtbooks/pes/powerenergy_070817
https://www.nxtbook.com/nxtbooks/pes/powerenergy_050617
https://www.nxtbook.com/nxtbooks/pes/powerenergy_030417
https://www.nxtbook.com/nxtbooks/pes/powerenergy_010217
https://www.nxtbook.com/nxtbooks/pes/powerenergy_111216
https://www.nxtbook.com/nxtbooks/pes/powerenergy_091016
https://www.nxtbook.com/nxtbooks/pes/powerenergy_070816
https://www.nxtbook.com/nxtbooks/pes/powerenergy_050616
https://www.nxtbook.com/nxtbooks/pes/powerenergy_030416
https://www.nxtbook.com/nxtbooks/pes/powerenergy_010216
https://www.nxtbook.com/nxtbooks/ieee/powerenergy_010216
https://www.nxtbook.com/nxtbooks/pes/powerenergy_111215
https://www.nxtbook.com/nxtbooks/pes/powerenergy_091015
https://www.nxtbook.com/nxtbooks/pes/powerenergy_070815
https://www.nxtbook.com/nxtbooks/pes/powerenergy_050615
https://www.nxtbook.com/nxtbooks/pes/powerenergy_030415
https://www.nxtbook.com/nxtbooks/pes/powerenergy_010215
https://www.nxtbook.com/nxtbooks/pes/powerenergy_111214
https://www.nxtbook.com/nxtbooks/pes/powerenergy_091014
https://www.nxtbook.com/nxtbooks/pes/powerenergy_070814
https://www.nxtbook.com/nxtbooks/pes/powerenergy_050614
https://www.nxtbook.com/nxtbooks/pes/powerenergy_030414
https://www.nxtbook.com/nxtbooks/pes/powerenergy_010214
https://www.nxtbookmedia.com