Transcript Link to presentation - Smart Grid Northwest

Pacific Northwest Smart Grid
Demo Interoperability Survey
Lessons Learned
Mark Osborn
September 2016
1
Since
1983
Energy and
environmental
consulting firm with
485 employees
33 years
of experience in energy
program support
2
Transactive Control / Internet of Things (iOT) Research
for QualityLogic, Inc.
Pacific Northwest Smart Grid Demonstration Project
(PNW-SGDP) ran from 2010 to 2015
The project’s budget was $178 million; half was provided by
USDOE, and half by the project partners
The transactive energy aspect of the project is unique in the
world:
It accomplished the interconnection and interoperability of thousands
of different makes and models of electronic devices on a scale never
before attempted
3
Pacific Northwest Smart Grid Demonstration
Project Objectives
Create the foundation of a sustainable
regional smart grid that continues to grow
following the completion of the project.
Develop and validate an interoperable
communication and control infrastructure
using incentive signals to:
•
•
Coordinate a broad range of customer and
utility assets, including demand response,
distributed generation and storage, and
distribution automation
Engage multiple types of assets across a
broad, five-state region; and reach from
generation through customer delivery.
Measure and
validate smart grid
costs and benefits
for customers,
utilities, regulators,
and the nation,
thereby laying the
foundation of
business cases for
future smart grid
investments.
4
Utilities Involved with PNW-SGDP
& Measure Categories
Avista Utilities
Benton PUD
City of Ellensburg*
Flathead Electric
Idaho Falls Power
Lower Valley Energy
Milton-Freewater
Northwestern Energy
Peninsula Light
Portland General Electric
UW/Seattle City Light
Totals
Transactive
Control
Reliability
Conservation
/Efficiency
Social
Totals
4
1
0
6
8
3
3
4
2
4
5
41
3
1
0
2
2
2
0
1
1
1
0
13
5
1
8
0
3
6
0
3
1
1
3
31
3
0
0
0
3
1
0
1
0
2
0
10
15
3
9
8
16
12
3
9
4
8
8
95
* Non-Transactive Project
5
Transactive Control – How it worked
Flathead
UW
Pen Light
Avista
Battelle &
Benton PUD
Northwestern
Milton-F
PGE
Lower Valley
Idaho Falls
Every 5 minutes, a value signal (TIS) with a 72 hour price forecast was sent to utility devices from Battelle
Every 5 minutes, a load/generation forecast (TFS) was to be returned to Battelle
6
Typical Utility Transactive Site Setup
Battelle – Grid Conditions
(TIS Initiation)
Utility FIREWALL
Transactive
Node
DISTRIBUTION EQUIPMENT
Intelligent Line Switching
Integration Server
(TFS Results)
SCADA
AMI
CVR
Smart Appliances
DRUs
Battery Storage
CUSTOMER EQUIPMENT
7
Sampling of iOT Devices,
Integrated for Transactive Operations
AVISTA
•
•
•
•
•
•
•
•
G&W Viper circuit reclosers for DMS
Cooper voltage regulators for Volt-Var
Optimization
S&C capacitor banks for Volt-Var
Optimization
SEL smart faulted circuit indicators for
DMS
Howard smart transformers for DMS
Itron meters provided new functionality
for AMI
EcoBEE smart thermostats provided
Residential DR
Trayer switchgear for DMS
FLATHEAD ELECTRIC
•
•
•
•
Spirae Bluefin Server for
transactive management
General Electric’s Web services link
to Demand Response Load Control
Automated DR server.
GE DR-capable smart appliances,
sending demand response loadreduction signals over the Internet.
Aclara TWACS power line carrier
system collecting end-use metering
information and sending one-way
DR control signals to a TWACS
water heater controller.
8
Sampling of iOT Devices,
Integrated for Transactive Operations
LOWER VALLEY ENERGY
•
•
Water Heater Demand
Response Units
Conservation Voltage Reduction
System
–
•
reduces voltage on East Jackson,
Wyoming distribution feeders
resulting in lower energy
consumption.
100kW / 100 kWh Battery
Storage System
–
Grid-connected battery that can
charge or discharge, either taking
energy from the grid or exporting
power to the grid.
MILTON-FREEWATER
•
•
•
Feeder Level Peak Shaving Voltage
Reduction -- Utilizes existing line
voltage regulators to lower voltage at
peak loading times
Demand Response Load Control -Utilizes new TWACS power line carrier
communications and residential load
control units to interrupt loads to
water heaters, HVAC, and heat pumps
Grid Friendly Appliances -- Utilizes
autonomous controllers to
temporarily curtail water heaters
when a local voltage reduction is
observed.
9
Sampling of iOT Devices,
Integrated for Transactive Operations
PORTLAND GENERAL ELECTRIC
•
Residential DR water heaters and 5MW battery storage
system -- fully transactive
•
Microgrid Operations -- overseen by a human operator
UNIVERSITY OF WASHINGTON
•
utilizing PGE’s proprietary Distributed Energy Resources
Management System, GenOnSys.
–
–
–
•
•
Artificial intelligence system predicted feeder loads,
then a neural network optimizer optimized DER and DR.
Woodward Master Synchronizer and Load Control
(MSLC) and Digital Synchronizer and Load Control
(DSLC) modules used for generator load balancing while
islanded
Modicon PLC for battery system/inverter system for
monitoring and control of solar smoothing, arbitrage
and TIS control.
Pole mounted Intellirupters smart feeder switching
system used for self-healing capability after power
outages.
Protection and safety functions by Schweitzer
Engineering Laboratories (SEL) relays communicating via
mirrored bits.
•
•
Spirae integration server is connected
to a Cisco Mediator which was linked
to a Johnson Controls BacNet building
management system
BacNet Devices transfer transactive
commands to perform building DR
actions.
Cisco Mediator is connected to the
Electro Industries/GuageTech (EIG)
Smart Meters (Nexus Meters) to allow
access by the UW Electrical
Workstation running EIG Meter
Access Software to view Itron Smart
Meter data.
10
Problem 1 – Vendor Support/Financial Health
Many newly
introduced products
• Lacking financial
support, equipment
maturity or vendor
customer support
Two energy storage
vendors declared
bankruptcy during the
project
• One came out of
bankruptcy
• One stranded the
utility’s assets
11
Problem 2 – New Systems Integration
Challenges
Each utility was faced with a complicated custom integration
process involving many diverse mostly proprietary systems
A totally new Transactive Control System (TC) needed to
be integrated
Only a few utilities had actually tried to connect two way
communications between their utility system and their
customer’s systems/equipment before participation in the
PNW-SGDP.
12
Problem 3 - Limited Use of Standards
Reasons Standards were not used:
•
•
•
•
Choice of standard left to vendors
Lack of vendor support for standards
Immature standards
Utilities didn’t want to impose a standard on vendors
Two most common standards used – DNP3 &
MultiSpeak
Followed closely by Modbus, OpenADR and a
couple instances of BacNet
13
Problem 4 – When a Standard isn’t a Standard
When a standard protocol was used
• Different vendors used optional registers
• Different release versions from connecting system
• Areas in the standard that need to be accessed by a
separate connecting system
Immature standards maybe worse than no
standard at all
(Elements of standards changed throughout project, standard support
organizations were slow, poorly funded with no testing and certification program)
14
Planning Lessons Learned
1. Choose products that are:
1.
2.
3.
4.
Market ready with better financial backing
Tested more fully
Offering long-term support commitments
Better able to integrate with current systems
2. Specify the standards to be used in the project RFP and design process
(Don’t leave it up to the vendor)
3. Pay more attention to communication-interfaces at the start of a
project and during project design
(Communication connections were often neglected over power issues by utilities)
4. Avoid Immature standards – choose mature standards
(Immature standards that change frequently often requires replacement of existing
hardware and also require many more work-arounds or proprietary equipment
modifications that must be made to get things to work)
15
Vendor Lessons Learned
1. Be watchful of the initial
comm interface information
provided by vendors
3.
(The sales people may not know, or want
to explain, the limitations of their systems
going into a significant project sale)
2. Avoid falling into the
routine of using your
current vendor for loyalty
or anticipated ease
(Interoperability may be just as easy, or
easier, with a new solution and new
vendor rather than the current vendor and
their existing solution which may be
proprietary or a force fit)
Get vendor commitments
on data requirements
up-front to ensure all
performance needs are met
(accuracy and data flow rates)
4.
Press for better product
development cycles by
vendors to identify and
eliminate issues such as:
3.
4.
5.
Data corruption
Difficult upgrade process
Standards variations and
communications errors
16
Operations Lessons Learned
1. Put a key human resource in charge
of each communication interface
between devices
(Assure a clearly-written requirement is
developed between vendors and utility
before installation)
2. Lab test all communications systems
prior to deployment
(Utilities should spend significantly more
time in a bench test or test lab environment
to assure interfaces between systems
interoperate as needed for the project)
3.
Explore alternatives
to the use of XML
for Big Data
solutions such as
“stream processing”
or “Hadoop”
(XML was found to slow
throughput when many
records had to
be analyzed)
17
Overall Project Lessons Learned
1. Focus on the
interoperability
standards to be used
(Interoperability Issues ran
rampant – too many proprietary
systems had to be custom
integrated in a “one-off” fashion)
2. Test, Test, and Test
(An interconnection lab or
integrated bench testing system
should be established prior to
any field deployment)
3. Mature interoperability
standards are desperately
needed for any similar
future attempts
(Use test harnesses and require
certification)
4. Provide support to
standards organizations
(Your support is needed for welldeveloped standards programs
for all communications systems
planned to be used)
18
ANY
QUESTIONS
19
Mark Osborn
Senior Associate, Energy Services
Office (503) 467-7108
[email protected]
More Info: www.pnwsmartgrid.org
Facebook.com/CadmusGroup
@CadmusGroup
Linkedin.com/company/the-cadmus-group
20
Acknowledgment: "This material is based upon work supported by the
Department of Energy under Award Number DE-OE0000190.”
Disclaimer: "This report was prepared as an account of work sponsored by
an agency of the United States Government. Neither the United States
Government nor any agency thereof, nor any of their employees, makes any
warranty, express or implied, or assumes any legal liability or responsibility
for the accuracy, completeness, or usefulness of any information, apparatus,
product, or process disclosed, or represents that its use would not infringe
privately owned rights. Reference herein to any specific commercial product,
process, or service by trade name, trademark, manufacturer, or otherwise
does not necessarily constitute or imply its endorsement, recommendation,
or favoring by the United States Government or any agency thereof. The
views and opinions of authors expressed herein do not necessarily state or
reflect those of the United States Government or any agency thereof.”
21