Professional Documents
Culture Documents
to Integration
Smart grid-related blogs, newsletters,
and conferences have endured numerous debates and
discussions around the issue of whether or not the smart
grid is being integrated correctly. While most debates
focus on approach, methodology, and the sequence of
what needs to be done, there is insufficient discussion
about what is actually meant by smart grid integration. This article attempts to present a holistic view of
smart grid integration and argues for the importance
of developing system integration maps based on a
utilitys strategic smart grid road map.
Faced with diverse technological, organizational, and
business issues that adversely affect the bottom line, utility companies are contemplating immediate changes and/
or upgrades of their technologies, business processes, and
organization. At the same time, however, the realities of
insufficient resources, regulatory impediments, and technological hurdles have prevented the development of concrete plans and concerted actions in this regard.
A closer look at mainstream discussions within the
utility industry reveals that, despite consensus about
the need for change, there is no agreement across the
board in any given utility about a smart grid road map
and integration map. The absence of industrywide
standards and blueprints for smart grid integration has
further compounded the issue. The silo mentality of
the constituent parts of the utility organization drives
the generation folks to push for expanding generation
capacity through the integration of renewables, the
transmission people to urge expansion of transmission capacity through automation, and the distribution community to argue for integration of new assets,
technologies, and intelligence on the downstream side
of the network.
52
By Hassan Farhangi
1540-7977/14/$31.002014IEEE
may/june 2014
Perspectives
on Smart
Grid Development
Furthermoreand given the fact that each group has traditionally been exposed to certain vendors and technology providers for its respective siloeach constituency tends to
regard the technologies and solutions offered by those vendors as the answer to much larger,
systemwide problems. And in the utility environment, these problems by default transcend
the confines of a single silo.
The situation is further complicated by the diversity of views, interests, and approaches
advocated by vendors and technology providers in the field. Influenced (and constrained) by
its core competencies and technologies, each vendor defines the problems, and therefore the
solutions, in the way that best suits its own technologies and products. One should therefore
not be surprised to hear different suppliers put different spins on basic concepts such as distribution automation, demand response, and so on. The irony is that they are mostly sincere
in what they are advocating. The issue is whether any of their prescriptions is the Holy Grail
needed to solve the utilitys smart grid integration puzzle. This seems to be a reenactment
of Rumis story of the blind men and the elephant. Each person has his own understanding
of what the creature is based on what part he has managed to touch. The absence of sight
(or light) has convinced each and every one of the righteousness of his version of the truth,
ignoring the fact that the smart grids systemwide issues require all its constituent parts
to work together and implement a collective strategy for doing what needs to be done. In
Rumis words, If each of us held a candle there, and if we went in together, we could see it.
AMI Database
Architecture
Portal
Technology
EMS Ver 1
ZigBee Network
with Smart Energy
Profile
MODBUS
Integration
Techniques
ANSI-C12.19
Data Aggregation
MDMS
ANSI C12.22
Smart Metering
Mobile EMS
Ver 1
Mobile EMS
Dashboard
End Customer
Experience
Social Science
Factors in Energy
Management
Scientific Paper
On EMS
Load Shedding
Scheduling
EMS Ver 2
Pricing Signal
Broadcast
Time of Use
Tariff
Maximum
Demand Tariff
Asset
Management
Dashboard
Microgrid
Asset
Manager
Integrated
Microgrid Sensor
Network
Microgrid
Substations
Automation
Integration of
Thermal Turbine
Integration of
Storage
Integration of
Wind Turbine
Integration of
Solar Modules
Microgrid
Controller
Integration
SGCC Topology
EMS Ver 3
End-Customer
Experience
Social Science
Factors in Energy
Management
Scientific Paper
On DSM
Net Metering
Protection and
Switching
Synchronization
Energy
Transactions
Revenue Models
EMS Ver 4
DC Distribution
Network
DC Protection
and Switching
Scientific Paper
On DC Microgrid
EMS Ver 5
End-Customer
Experience
Load Prediction
and Profiling
EV Charge
Manager
DC Microgrid Pilot
EV Charge Pilot
A6: Microgrid
Islanding
E1: Rural DC
Microgrid
D1: Intelligent
Transportation Network
may/june 2014
Dedicated Fibre
Scientific Paper
On IEC 61850
2012
ZigBee Sensor,
Thermostat and
IHD
Building
Automation
2011
BCIT/BC
Hydro
Smart Microgrid
RD&D
Road Map
C5: Microgrid
Asset Management
A3: Advanced
EMS
B2: Dynamic
Tariffs
C4: Distribution
Automation
A2: Mobile
EMS
Residence Competition
C3: WAN Network
Version 0.7
Date: 5 Feb. 2011
Author: Dr. Hassan Farhangi
Status: Proprietary and Confidential
Paper
Tool
IP
Pilot
DC
Stream
EV
Stream
Revenue Automation
Stream
Stream
EMS
Stream
Legend:
2010
2013
end to end or for all capabilities. Different smart grid functions require the integration of different assets, with different
capabilities and different requirements. As such, a smart grid
integration map must adhere closely to the utilitys strategic
road map and to the intended smart grid functionalities that
need to be enabled in each stage of development.
In practice, smart grid integration has taken many
twists and turns. It is unlikely that North American utilities have followed similar modalities and approaches to
smart grid integration. It is more logical to assume that
each utility has taken a unique path toward implementing
its smart grid plans.
Capabilities
Technologies
Intelligent Appliances
Intelligent
Agents
ROI
Intelligent
Applications
Emission Control
Smart
Grid
Load Management
Preventive/Self-Healing
Substation Automation
Network
Management
Distributed
Control
Smart
Sensors
Distribution Automation
Customer Information System
AMI
Asset Management
Outage Detection and Restoration
Two-Way
Communication
One-Way
Com.
Customer Portals
Distributed/Co Gen
Demand Response
AMR
Automated Billing
Investments
Billing and
Accounting
Finance
DOC
Management
Corporate
HR
Biz Ops
Trading
Scheduling
Settlements
Forecasting
System Planning
System
Planning
Capacity
Planning
Network
Planning
Data
Warehousing
Engineering
Maintenance Parts/
Work
Asset
Scheduling Supply Management Management
Sys Ops
EMS
DMS
OMS
Customer Service
CIS
MDM
IVR
Backhaul Coms
Field Coms
Fiber
Network
WiMax
Network
Station Bus
(Revenue Data)
WiMax
Revenue Data
Residential
Metering
IPP
Color Code
Broadband
PLC
Process Bus
(Breakers, Switchgear,
Reclosers, Transformers)
Commercial
Metering
Narrowband/
Broadband
PLC
Industrial
Metering
Gateways
Biofuel
Wind
Data
Data
Warehousing
Microwave
Network
Net Meters
PV
GIS
Public
Proprietary RF
Network
Two-Way Coms
DSM
ERP
COM
HR:
ERP:
DOC:
Document Management
EMS:
DMS:
OMS:
DSM:
Demand-Side Management
GIS:
CIS:
MDM:
IVR:
PLC:
WiMax:
RF:
Radio Frequency
PV:
Photovoltaic
Communication Systems
IPP:
VVO:
Volt/Var Optimization
CVR:
Small
Hydro
Asset
enterprise functions, utility operations, and revenue management (e.g., contingency management, asset management,
energy market participation, and so on), while others traverse local downstream layers of the system, involving field
and prosumer-facing assets (e.g., demand response, load
management, and so forth). It is the latter group that places
a heavy burden on the AMI system, as it requires close integration and tight operational linkages to AMI system components, protocols, and technologies. A poorly designed and
implemented AMI system would prove to be inhibitive for
the efficient implementation and/or correct operation of such
downstream smart grid functions.
all jurisdictions. Having said that, and regardless of a utilitys 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 utilitys 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 utilitys
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 toand 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 utilitys 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. Neverthelessand regardless of the environment to
which they are attachedeach 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 systems relevant points
of termination.
Application Layer
Smart Grid
Smart Grid
Enterprise
Smart Grid
Enterprise
Applications
Enterprise
Applications
Applications
Enterprise Bus
ICT Layer
Security Regime
Communication
Infrastructure
Utility Assets
Generation
Transmission
Distribution
b#3
b#
D-Sub#1
T-S
u
D-Sub#2
D-Sub#4
M1
HAN#1
M2
HAN#2
M3
HAN#3
Power
Plant#1
T-S
u
T-Sub#1
b#
SG-A
pp#5
SG-App#3
SG-A
pp#4
Feeder
D-Su
SG-App#1 SG-App#2
Power
Plant#2
Local Area
Network (LAN)
Home Area
Network (HAN)
may/june 2014
Transformer
WAN
Interface
Field Area
Network
Interface
Feeder A
Recloser
Volt/Var and CVR
Optimization Engine
DMZ
Timing and
Syncronization
LAN
Interface
AMI Headend
DAU
Substation Bus
Substation
Area
Network
One would certainly hope that utilities quest for infrastructure modernization will not come to a screeching halt. Utilities will no doubt attempt to integrate additional smart grid
functionalities based on their particular priorities and road
maps. Two such functionsones many utilities intend to
implement nextare VVO and CVR. The U.S. Department
of Energys recent studies in energy conservation across the
United States indicated that CVR functions, if integrated
across less than half of U.S. feeders, could potentially yield
more than a 2% reduction in demand on the U.S. electrical system. In fact, it is public knowledge that many utilities
regard VVO and CVR as high priorities for implementation
on critically congested feeders. It has been claimed that the
ROI ration for VVO and CVR integration is six to one, with
a payback period of two to three years. That is certainly a
great incentive to regard investment in advanced VVO and
CVR as the next item on the integration map of many utilities after AMI.
Prior to AMI, the VVO and CVR functions in distribution substations (if they existed at all) used a statistically
aggregated profile of feeder load to determine the settings
and configurations of capacitor banks, tab changers, voltage regulators, and other devices used to correct the feeders power factor and to ensure compliance of the voltage
gradient across the entire feeder, from substation to the last
customer, with ANSI and IEEE requirements. Given the
fact that no real-time information about the actual voltage
samples across the feeder was available, the settings and
configurations for such VVO and CVR assets were either
ineffective or inefficient.
VR
Caps
VR
Caps
RF/PLC Interface
Power
SCADA
Data
Substation EMS
Distribution Substation
EMS
HAN
EMS
HAN
EMS
HAN
EMS
HAN
62
MCU
Residential Load-H
Smart Meter-H
PLC
Modem
Capacitor Banks
Unit
Sub. Capacitor
Banks Unit
Cap. Bank
Switch
AFE
Line Voltage
Regulator
Distribution Transformer
12.5 kV/0.4 kv
..
..
Voltage Regulator
Switch
MCU
Smart Meter-B
MV Breaker
Residential Load-B
PLC
Modem
Substation MV Bus
AFE
PLC
Modem
IA-IED
MCU
Substation Transformer
138-kv/12.5-kV
Transformer On-Load
Tap Changer
MV Breaker
Load Bank
MV
Distributed
Breaker Generation Source
12.5 kV
Capacitor Banks
Unit
MCU
AFE
Smart Meter-A
Residential Load-A
PLC
Modem
AFE
VVO/CVR
Opt. Engine
HV Breaker
Substation HV Bus
To HV Substation
may/june 2014
N5-2 Smart
Meters
D2
T2
Rooftop
B2
Smart Inverters
Net
Meter
N=3
PVs
Var Injection
Point-2
Bi
Var Injection
Point-3
Feeder
Capacitor
Bank
N5-1 Smart
Meters
T3
N=4
N=5
Net
Meter
T4
DK
EV
Net Meter
D1
DG Source
Var Injection
Point-4
Smart Inverter
Cj
C2
C1
N3 Smart Meters
N=1
Var Injection
Point-1
T1
N=2
B1
A8
A2
Communication Flow
Dist. Network Flow
Substation
Capacitor
Bank
Substation Transformer
with Tap-Changer
CVR
Server
IEC 61850
VVO
Engine
EMS
Server
HV/MV Substation
N2 Smart Meters
Feeder
Capacitor
Bank
A1
Litmus Test
As discussed earlier, a forward-looking smart grid integration
map is critical for the realization of a smart grid. And given the
64
cost involved in integrating new technologies and functionalities into the existing grid, the smart grid integration map could
prove to be either the savior or the Achilles heel of a utilitys
smart grid program. In making that judgment, every utility
has to review the operational requirements of its medium- and
long-term smart grid functions and determine if its smart grid
integration map supports a seamless transition from where it is
now to where it would like to be in the future.
In addition to the examples discussed at length above,
there are several other commonly identified smart grid capabilities that may be considered as a litmus test for ascertaining the suitability of a utilitys smart grid integration
map. These include:
Distributed generation: As discussed earlier, concerns about cogeneration synchronization, var control,
voltage stability, and so on have convinced utilities of
the need to achieve a level of integration (notwithstanding the regulatory impediments that exist in
various jurisdictions across North America) between
feeder assets and behind-the-meter, customer-owned
equipment. Given the fact that the point of common
coupling between the utility and the customer is the
smart meter, such a level of integration must be facilitated by the utilitys smart grid integration map.
Sensor networks on the low-voltage (LV) side of the
distribution system: Although such sensory data on the
LV side (such as those from phasor measurement units)
have not yet been established as a critical requirement,
one should assume that should that become a necessity,
the AMI infrastructure could be the primary means of
supporting such real-time data (through an auxiliary
channel) and transporting them to the substation. The
alternative to using the existing AMI assets for such
data would be to construct a dedicated, low-latency
communication system with a universal communication
protocol and mission-critical availability and resilience,
together with secure and intrusion-resistant multitier
access, as the carrier of such data for the upper layers of
the system. That could be quite costly. Again, no matter
what the chosen architecture for the implementation of
sensor networks, a utilitys smart grid integration map
must include provisions for supporting additional data
networks going forward.
Customer-side EMS: EMSs on the customer side
of distribution systems are often regarded as killer
apps enabling accurate, reliable, real-time, and endto-end energy management functions. Given the
trend toward designing distribution substations as
energy hubs in charge of achieving cost-effective
management of power and services transactions
between producers and consumers (prosumers),
it is paramount to move away from a broadcastbased, global utility pricing and tariff-signaling
system to a real-time, substation-based, local pricing signal. Just as the price of gas is never the same
may/june 2014
Enterprise Bus
Agent
BP20
Agent
BP11
Agent
BP21
Agent
BP00
Agent
BP20
Agent
BP01
Firewall
Agent
BP21
Agent
BP10
Agent
BP20
Agent
BP11
Agent
BP21
HAN
HAN
HAN
HAN
HAN
RF/PLC
Proprietary
Protocol
ZigBee
SEP 2.0
Distribution
Networks
Agent
BP21
Agent
BP10
Backhaul
Networks
Agent
BP20
Firewall
Utility Data
Warehouse
Data
Enterprise Apps
Servers
DR Server
Outage
Management
Server
Asset
Management
Server
Billing Server
MDMS Server
DAU
DAU
DAU
may/june 2014
Conclusions
The central theme in all of the examples discussed in this
article is the need to have a forward-looking smart grid
integration map that empowers utilities to add incremental
functionalities to their existing grid, if and when required,
without the need to redo any of their previous investments.
Given the examples discussed abovewhich cannot by any
stretch of the imagination be considered comprehensive
the utilities have to be extremely careful about the initial
investments they make in this regard. That does not appear
to be always the case, however, as some of the choices that
have already been made in the early stages of the process
have not been encouraging.
The AMI model implemented in many jurisdictions
across North America, for example, relies on local data
collection units (often referred to as DAUs) as the primary
interface between smart meters and MDM system applications in the back office. In such a model, the local distribution substation will either be totally disconnected from the
AMI system that monitors the customers feeding off its feeders or if there is any communication between smart meters
and substation equipment, the data will have to go through
the round robin of being captured by DAUs locally, passed
on to the appropriate MDM system in the remote back office,
and handed over to the SCADA head end in the back office
before finding its way through the SCADA network from the
back office down into the substation.
It goes without saying that such long delays in data and
command communication would make it nearly impossible
to efficiently run any number of smart grid capabilities
that rely on distributed command and control and as such
require local analytics and decision making. Such applications are by default substation-resident, with a stringent
need for unimpeded access to real-time data from smart
meters, sensors, and other termination points associated
with that substation. In other words, smart meters should
ideally be substations over-the-fence intelligent electronic devices (IEDs), fully engaged in real-time data and
command exchange with substation-resident functions;
failing this, they are nothing more than an interim solution
for automating billing and revenue management.
Finally, a utilitys smart grid integration map must support
the realization of the utilitys integrated network domains,
66
Biography
Hassan Farhangi is with the British Columbia Institute of
Technology, Vancouver, Canada.
p&e
may/june 2014