An Overview of Smart Grid Standards

Download Report

Transcript An Overview of Smart Grid Standards

An Overview of Smart Grid Standards
Erich W. Gunther
[email protected]
February 2009
Why Use Standards?
•
•
•
•
•
•
Avoid re-inventing the wheel
Learn from industry best practices
Specify requirements more easily
Reduce integration costs
Prevent single vendor “lock-in”
Vendors share a much larger market

2
Making Standards Work
Items critical to a
Utilities
And
successful
Vendors
Direct
Lessons
Learned,
standard:
Participation
Innovations,
Application Notes
• Mature spec
Standards
Test Procedures,
• Involved user group
Revised more
Implementation
Rapidly
Guidelines
• Certification
process
• Revision process
Users’
Standards
Access to Working
Groups
Organizations
Drafts
• Marketing, labeling
• Implementations
Errors Detected
• Tool sets
Consensus Acheived
3
Why International Standards?
• Several Advantages
– Time-tested process
– Proven fair and open
– Can be accelerated if needed
• Other alternatives:
– “de Facto” needs a market-maker
– Industry consortia can work well
• E.g. ZigBee, HomePlug, Cable Labs
– User groups can create requirements specifications
• E.g. OpenHAN, AMI-SEC, AMI-Enterprise
– Work even better if endorsed by a standards org
4
Standards in the Smart Grid
Real-time Simulation
Wide-Area Reliability
Network Optimization
Customer Participation
Participation in Energy Markets
• EPRI IntelliGrid Architecture, http://www.intelligrid.info
• Catalog of Use Cases, Standards, Technologies
5
Smart Grid Comm Standards Domains
6
Enterprise and Control Center
Name / No.
Description
Status
IEC 60870-6
Inter-Control Center Protocol
Widespread
IEC 62325
ebXML for Power Systems
In development
IEC 61970
Common Information Model /
Generic Interface Definitions
(CIM/GID)
In use; mostly
single-vendor
IEC 61968
Interfaces for Distribution
Management
Mostly still in
development
Multispeak
NRECA Enterprise web services
In use; not flexible
•
•
•
•
There is a culture of manual integration
Very labour-intensive and costly
Object models and services defined, but…
A variety of underlying technologies: UML, XML,
OWL, XSD, RDF, OPC
• Working on agreement on a design framework
7
T&D Wide-Area Networks
Name
Notes
Frame Relay
Packet-switched, no reliability guarantee
SONET
Campus or city backbones
WDM
Wavelength Division Multiplexing – follows SONET
Microwave
Proprietary, used in geographically difficult areas
Satellite
Various proprietary technologies, costly
Trunked Radio
Licensed, one broadcast channel, one return
Spread-Spectrum Unlicensed frequencies, more efficient
IP Radio
Like trunked radio but with IP addressing
• Many of these are considered obsolete or
aging in the general IT world
• Still in common use in the power system
8
T&D Substations
Name / No.
Description
Status
IEC 61850
Object models, self-describing, highspeed relaying, process bus
Widespread in Europe,
beginning here
DNP3
Distributed Network Protocol
Most popular in NA
Modbus
Evolved from process automation
Close second
COMTRADE Fault Capture file format
Widespread
PQDIF
Power Quality file format
In use
IEC 62351
Security for power systems
Recently released
•
•
•
•
Automation common in transmission
Business case tough in distribution
Well-known problems and solutions
Moving to the next level
9
Access Wide-Area Networks
Name
Notes
PSTN
Public Switched Telephone Network – dial-up, leased lines
DSL
Digital Subscriber Line - Telco IP-based home access
Cable
DOCSIS standard for coax IP-based home access
WiMAX
WiFi with a backbone, cellular-type coverage
Cellular
Various technologies e.g. GSM/GPRS or CDMA/EVDO
FTTH
Fiber to the Home. Passive Optical Networks (PONs)
PLC
Narrowband Power Line Carrier – the “old stuff”
Access BPL
Broadband over power line to the home
Paging
Various proprietary systems, POCSAG
• Used to reach the Collector or Substation
• Too expensive, too unreliable or too slow for
actual access to home
10
Field Area Networks – Distribution and AMI
• Offerings mostly proprietary
– Wireless mesh, licensed or unlicensed
– Power line carrier, narrowband or
broadband
– New standard activity just started in 2008
A B
• Open standards not useful yet
– Cellular, WiMAX, ADSL, Cable, FITL
– Not economical or not reliable or both
– Mostly only reach the Collector level
Metering
Network
Network
A
Metering
Network
Network
B
• Interop solution: common upper layer
– Network layer preferred: IP suite
– Most don’t have bandwidth
• Application layer instead: ANSI C12.22
– Too flexible, not enough interoperability
– Need guidelines, profile from users
A
B
• More bandwidth the main solution!
11
Home Area Networks
Name
Number
Notes
Ethernet
IEEE 802.3
Substation LANs, usually fiber optic
WiFi
IEEE 802.11
Access by field tool, neighborhood AMI net
ZigBee
IEEE 802.15.4
Customer premises automation network
HomePlug 1.0, AV, BPL
Powerline comms, in and outside premises
6LowPAN
The “approved” IPv6 wireless interface
IEEE 802.15.4
OpenHAN HAN SRS
v1.04-2008
Power Industry requirements definition!
• ZigBee and HomePlug alliance
– Popular open specifications
• LONWorks, Insteon, Z-Wave, X10 –
popular proprietary networks
• Challenges coming in Electric Vehicles
12
Distributed Resources and Commercial
Name / No.
Description
Status
OPC
Application interface
Widespread in industry
IEC 61400-25
Wind Power
In use; turf war
DRBizNet
California initiative
In development
BACNet
Building automation
In use; many profiles
OpenADR
Automated Demand Response
In development
IEEE 1547
Basic principles of DER
In use
IEC 61850-7-420
Information models for DER
Just released
• Rapidly growing, but tend to
be “islands of automation”
• Concerns over integration with
power utilities
• Need to get people talking
13
Another Look at Smart Grid Standards
Example
Members
External
Portal
Enterprise
Metering System
WAN
Collector
Field
LAN
Meter / Gateway
$
!
HAN
Normal NOR
Critical PEND
MAL
Emergency
Program ACTI
RID
ING
Emergency
Peak
Event OV
Stage 1 VEStage 2 ER E
Current
Temp
03/03/2007
8:48am
Stat
us
Progr
AW
am:
AY
Example
Technologies
Retailers
Aggregators
Regulators
Customers
Providers
Internet Protocols
World-Wide Web
ebXML
IEC 60870-6 ICCP
MDMS
CIS/Billing
OMS
WMS
EMS/DMS
IEC 61970
IEC 61968
Web Services
Multispeak
Message Buses
Routers
Towers
Ground Stations
Repeaters
Rings
SONET, WDM, ATM
MPLS
Frame Relay
Satellite
Microwave
IEC 61850
DNP3
Relays
Modems
Bridges
Access Points
Insertion Points
WiMAX
BPL / PLC
Wireless Mesh
ADSL
Cellular
Cable (DOCSIS)
Thermostats
In-Home Displays
Smart Appliances
Field Tools
PCs
Building Automation
ZigBee
WiFi
LonWorks
BACnet
HomePlug
OpenHAN
14
Standards Challenges for Smart Grids
• Need Common Object
Models
• Wishy-washy standards
• More bandwidth in the field
• Proprietary field networks
• Too many stds. in the home
• Merging power and industry
• Merging meters and
distribution automation
• Holistic security
$
!
Normal NOR
Critical PEND
MAL
Emergency
Program ACTI
RID
ING
Emergency
Peak
Event OV
Stage 1 VEStage 2 ER E
Current
Temp
03/03/2007
8:48am
Stat
us
Progr
AW
am:
AY
15
Summary
Essential
Promising
Needed
IP-based networks
IEC 61970 CIM/GID
IEC 61968 Distribution
IEC 61850 Substations
IEC 62351 Security
DNP3
ANSI C12.19, C12.22
AMI-SEC
OpenHAN
WiMAX
ZigBee / HomePlug
OpenADR
6LowPAN
BACNet
OPC/UA
NERC CIPs
Standard Field LANs
Modems for Field LANs
More field bandwidth!
CIM Design Framework
CIM Application Security
CIM/61850 Harmonization
IEC 61850 Outside Sub
ANSI C12 Guidelines
Finish AMI-SEC
Asset Mgmt, DER, PHEV
We have the technology.
We have the lessons learned.
We just have to apply it!
16
Address design in breadth and depth
17
Address design in breadth and depth
• A software application is evident to users only at one
level
– Must operate transparently to the appropriate depth to interact
with other systems
– May be tied to key hardware elements of the system
– If tied, must be upgradable and extensible
– If hardware is exchanged, must continue transparent operation
(with some configuration)
• At the physical level, not allways possible to have an
appropriate connection that facilitates openness and
competition (e.g., meter under-glass interface for
communications boards; multi-vendor interface inside of
relays)
18
Recommended focus areas
• Standard field LANs (FANs)
– Innovation drived by vendor tension
• More field bandwidth
– Eliminate single-purpose networks and facilitate innovation
• CIM design framework
– Tighten allowable choices and develop implementation guide
• CIM application security
– Guidelines needed for verifiable security
• CIM / IEC 61850 harmonization
– Motivate users group to eliminate identified gaps
• IEC 61850 outside of the substation
– Incentivize vendors to extend reach of products and systems
19
Recommended focus areas, pt. 2
• ANSI C12 guidelines
– Demand demonstrations of interoperable products
• Finish AMI-SEC work products
– Component catalog and implementation guide
• Asset Management
– Incentivize utilities to leverage infrastructure to better manage
business
• Distributed Energy Resources
– Re-think and re-design hardware and software to account for
two-way energy flow
• Plug-in Hybrid Electric Vehicles
– Need policies, regulations, business model, standards, etc.
20
Key Strategies
• Drive stakeholders from standards development to
interoperability demonstrations
• Holistic targets eliminate single-purpose design and
incompatibilities
– Technical, communications, environment, regulation, etc.
• Apply systems engineering and third-party metrics to
avoid single-entity rate-or-return projects
21
Key recommendations
• DOE GridWise Architecture Interoperability Checklist
should be used by policy makers to evaluate utility
proposals
• Smart Grid News technology/product/project checklist or
equivalent should be used to validate “smartgridness”
• Standards-based solutions should be favored over
proprietary solutions via legislation, rules and regulations
• Desired outcomes and important characteristics (e.g.,
interoperability) should be specified by policy makers
rather than specific standards (where possible)
• Research needed to accelerate development and fill the
gaps in security, smart grid networks, device
management, information privacy and field network
interoperability
22