smartgridlogical communicaons reference&architecture& p2030 smart... · smartgridlogical...

Smart Grid Logical Communica2ons Reference Architecture

Claudio Lima IEEE P2030 SG1 Architecture

DCN #154, Revision January 5th 2010

Outline

•  Smart Grid Layered Architecture Approach

•  Basic Defini2ons

•  Logical Interfaces and Modules

•  SG Logical Communica2ons Architecture

•  Mapping Use Cases and U2li2es Architectures

2

SG Layered Architecture Approach

3

P2030 SG

1 Arch Work

Generic (phase 1)

Specific (Actors) (phase 2)

C.R.Lima

The Smart Grid is a Large System of 17 Sub-‐Systems

DER Substa2on Automa2on

AMI/NAN

WAN

U2lity Control Center/AMI Enterprise

DA DER/µG

WASA

HAN, BAN, IAN

PEV, Storage, Renewables

3rd Party Providers

ISPs, Wireless Carriers, ILECs,

Cables Public Internet

Backhaul

Markets

Smart Meter

Workforce Mobility

The Smart Grid Framework

4

Logical Interfaces and Modules

5

•  Open

•  Interoperable

•  Modular

•  Secure

•  Scalable

•  Reliable

Key A]ributes for a SG Architecture Framework

The Architecture Needs to Provide the “Big Picture/Generic Approach” and at The Same Time it Needs to Break Down the Larger System Into Smaller Interoperable and Modular Components with Clear Inter-‐domain/Segment Demarca2on Points Specified.

SG Logical Communica2ons Architecture

6

SG Communica2ons Architecture Use

7

e.g. Microgrid Communica>ons Architecture

Distributed Automa>on Architecture

High-‐Level Communica2ons Architecture Framework (“catch all” diagram)

Specific SG Communica2ons Reference Architecture (modules)

Examples on How to Use the SG Generic Comm Arch Framework

1) Mapping of SG Use Cases (IEEE SG2, IEEE TF1/TF2, OpenSG, FERC 4+2, etc) Don’t need to use all the actors and interfaces, only the ones that “touch” the connec>ons/modules. This is a reduced version of the “catch-‐all” generic framework.

2) Mapping U2li2es Specific Architectures Use to map u>lity-‐specific SG architectures. This is also a reduced version of the generic diagram. It can be “customized” since each u>lity has their own specific architecture mapping. one-‐level down

Generic (phase 1)

Specific (Actors) (phase 2)

Use Case Mapping – example #1

8

Advanced Metering Infrastructure (AMI) Use Cases

Backhaul

U2lity Control/Opera2ons/

Enterprise LAN

Distribu2on Automa2on

Intelligent Field

Devices

Smart Meter

Customer Premise Network

E1

E4 E7 E12

E8

E14

CONTROL/OPERATIONS

DISTRIBUTION

CUSTOMER

Access Point (AP)

Neighborhood Area Network

(NAN)

Use Case Mapping – example #2

9

Distribu2on Substa2on

Network (hotspot)

Backhaul


Enterprise LAN Public Internet

3rd Party Network

Smart Meter


E1

E5

E14

E17

E23

E27

CONTROL/OPERATIONS

DISTRIBUTION

CUSTOMER

SERVICE PROVIDERS

Internet Service Provider

E20

Substa2on Automa2on Use Case

Energy Efficiency Management Through 3rd Party Value-‐ Added Energy Provider Use Case

Next Steps

10

•  Download from the IEEE Mentor DCN #154 •  h]ps://mentor.ieee.org/2030/documents

•  Call for Contribu2on: Please review this SG Architecture Framework

and provide comments to: (before January 20th 2009) -‐ Howard Choe, Chair SG1/Architecture ([email protected]) -‐ Claudio Lima, Vice Chair, SG1/Architecture ([email protected])

•  To be presented at the IEEE P2030 Plenary, Detroit January 2009

•  THANKS!

Back Up

11

End-‐to-‐End Smart Grid Communica2ons Architecture

12

End-‐to End Smart Grid Communica2ons Architecture

Actor Descrip2on Comments U>lity control, SCADA/substa>on automa>on and AMI enterprise LAN controls, supervises, manages and monitors all u>li>es assets, processes and customers.

The u>lity control/opera>on network and AMI enterprise controls, monitor, supervises and manages data flows from meters, SCADA, substa>ons and all cri>cal and non-‐cri>cal informa>on flow. The control/opera>ons center can be a single integrated en>ty that manages T&D or one control en>ty (DMS/EMS) for each transmission and distribu>on grid segment, depending on the type of u>lity or energy service provided model (ISO, RTO, co-‐ops/munis, overseas, energy retailers, etc)

Backhaul network connects the u>lity control/opera>ons and enterprise LAN with distribu>on substa>ons networks, distributed energy resources and NAN last mile networks overlaid on power distribu>on systems.

The backhaul network can either be owned by the u>lity or managed by a telecom/cable service provider. It can be wireline (dial-‐up, T1, cable, fiber, etc) or wireless (3G, Wimax, PTP or PMO radios, etc). A typical NAN might have more than one backhaul/access points (APs) connected to the WAN. In some cases the backhaul is not used in an Smart Grid architecture when centralized u>lity opera>ons manages the connec>ons to the last mile through their own facility.

Distribu>on substa>on network is comprised of local Ethernet networks that contains SCADA, Intelligent Electronic Devices (IEDs), Remote Terminal Unit (RTU), Phasor Measurement Unit (PMU) and other field devices that needs to be controlled and monitored via the backhaul network. IEC 61850/DNP3 are the protocols of choice for this network.

The distribu>on substa>on is controlled and supervised remotely via u>lity’s backhaul and interconnects to distributed energy resources/microgrids, distribu>on automa>on (DA), NAN/AMI networks and connects to the feeder/distribu>on electricity grid.


Enterprise LAN

Backhaul

Distribu2on Substa2on

Network (hotspot)

Smart Grid Logical Communica2ons Reference Architecture Actors Defini2ons

13

Actor Descrip2on Comments Distribu>on energy resources (DER) network is comprised of all renewable and no-‐renewable sources (e.g. wind/solar/diesel, etc), not part of the centralized energy genera>on. These energy resources could be interconnected through a local area network (LAN). Access communica>ons gateways can then connect these DER and storage LAN networks to the main grid. U>lity scale storage energy systems is also considered.

These area medium-‐large (MW) distributed energy genera>on and storage energy resources that are connected to substa>ons and/or AMI/NAN networks. In most cases, the genera>on sources (e.g. microgrids) are located in campus, industrial parks, etc. U>lity-‐scale renewable are remotely located from the energy consump>on centers and requires new transmission lines and communica>ons links to be built (if not available) to control these remote assets.

Access point (AP) is the device that collects aggregates all data coming from/to end devices/users through the NAN/FAN AMI networks. It also interfaces with backhaul/WAN.

APs can be considered part of the AMI/NAN network. These devices have rou>ng and traffic handling capabili>es to priori>ze mul>ple data flows. More than one AP might be used in the NAN/AMI to collect data (e.g. smart meter reading) and connect to the backhaul transport network.

Neighborhood area network (NAN) connects to smart meters, distributed automa>on (field devices), and distributed energy resources/microgrids and u>lity scale storage.

NAN is part of the Advanced Metering Infrastructure (AMI) and it can either use wireless (RF mesh/802.15.4G, Wimax, 3G, RF radios, etc) or wireline networks (BPL/PLC, fiber, cable, etc). It can also be either narrow or broadband, depending on the short vs. long-‐term strategies and service poreolio to be offered by the u>li>es. NAN can also become FAN when dealing with DA/field devices and substa>ons. It’s unusual for a NAN to interconnect to distribu>on substa>ons.

Workforce mobile network is used by the u>lity’s workforce to provide servicing, maintenance and normal day-‐to-‐day opera>ons.

It uses u>lity owned-‐AMI/NAN networks or 3G/Wimax services provided by wireless service providers. The substa>on hot spots can be used in conjunc>on with this network to download/access broadband data from the control center.

Distributed Energy Resources/Storage

Network

Access Point (AP)

Neighborhood Area Network

(NAN)

Workforce Mobile Network

14

Actor Descrip2on Comments Distribu>on automa>on (DA) network is comprised of intelligent field devices located on feeder/distribu>on poles (e.g. cap banks, reclosures, switches, smart transformers, etc). It’s connected to the u>lity control center through the AMI/NAN-‐FAN network.

DA field devices are connected by AMI/NAN-‐FAN networks. It provides intelligence to the distribu>on feeders to improve the quality of the electricity supplied to the end user, Volt-‐Var op>miza>on, outage management and others. There may be a separate AMI network to handle DA and substa>on traffic only since it is expected that this network will handle cri>cal u>lity assets, real-‐>me data/sensing and broadband traffic in the near future. In another scheme a single and integrated AMI network approach will handle smart meters and DA.

Smart meters are part of the AMI scheme and for some u>li>es are the demarca>on point between the u>lity’s and the customer. In most cases the smart meters have both WAN and HAN communica>ons modules that interfaces with the AMI/NAN and HAN/customer premises network, respec>vely. The smart meter provides electricity reading, demand response commands, pricing informa>on, connect/disconnect commands, etc.

Smart meters are installed by u>li>es in the customer’s premises to manage, monitor and control customer’s energy supply/demand. It provides wireless (ZigBee, Wifi, etc) or wireline (HomePlug, etc) communica>on with customer’s energy management/display devices (HEMS, IHDs) and/or Energy Service Interfaces (ESI), sub-‐meters, broadband access routers, etc. If RF mesh technology is used, these meters communicates to each other in their neighborhood.

Customer premise network is comprised of home area network (HAN), building/business area (BAN) network and industrial area networks (IAN). Some u>li>es consider the HAN to have only four devices (home energy management system (HEMS), smart thermostat, HVAC, and pool pump).

Customer premises network also interfaces with 3rd party energy service providers through broadband access routers and other advanced services, such as renewable/microgrid, customer storage systems, and plug-‐in-‐vehicle (PEV) through ESI devices.

Distribu2on Automa2on

Intelligent Field

Devices

Smart Meter


15

Actor Descrip2on Comment Customer grade renewable (solar/wind) and storage systems are connected to customer premises network through Energy Service Interfaces (ESI), using either wireline or (and) wireless HAN networks (e.g. ZigBee).

Customer’s energy resources can be used to balance the u>lity’s electricity load. When smart transformers are installed, energy can be supplied by customers back to the grid. It’s expected that customers will have a balanced poreolio of energy generated locally (in their premises) and supplied by the u>lity, with ra>o that can dynamic change during outages or energy peaks periods.

Plug-‐in-‐electric-‐vehicle (PEV) or plug-‐in-‐hybrid electric vehicle (PHEV) are considered as both load (to balance energy supply) and source/storage (to provide power back to the grid/vehicle-‐to-‐grid V2G).

PEV is ini>ally considered as a load when sta>onary, where energy is drawn from the grid to charge their bakeries. Proper dimensioning of the u>li>es distribu>on networks with PEV adop>on forecast is important to avoid unexpected peaks of energy consump>on during the charging of the PEVs. The mobile/roaming case is also consider when PEV needs to access charging, billing and posi>oning informa>on. The business case for PEV as a source of energy (V2G) to the grid is s>ll to be validated.

Internet service providers (ISPs), such as cables, DSLs, Wimax and others will connect to the customer premises network through broadband access routers. Most likely these routers will have an energy management layer/solware to handle energy informa>on from the customer or to communicate to to 3rd party energy informa>on providers.

ISPs will likely to offer energy management services through their broadband routers (“trojan horse”) to their customers as part of their broadband mul>ple player service strategy. In another scheme, 3rd party value-‐added energy service providers will access customer premises network energy devices, through ISP broadband routers, and will offer managed energy services to customers.

Solar/Wind/Storage

Internet Service Provider

Plug-‐in Electric Vehicle (PEV)

16

Actor Descrip2on Comments Wireless networks will play a role in AMI/NAN networks, DA, substa>on automa>on, backhaul, workforce automa>on, and also on PEV mobile/roaming schemes. Wireless networks can use 3G (CDMA/GSM/GPRS/IDEN), 4G (Wimax, LTE), or satellite technologies.

Wireless Service Providers (WSP) will most likely be the preferred choice for some u>li>es to deploy their AMI/NAN networks. Here WSPs are used in the context connec>ng PEVs when they’re driving to/from home-‐work. In some circumstance, inter-‐grid communica>ons must be provided through the wireless network so drivers can access informa>on (such as nearest charging sta>on, pricing schemes, etc) on road through their mobile phones or on-‐board energy management systems .

3rd party value-‐added energy services can offer managed energy services (home and building), demand response and other emerging services to end consumers and u>li>es.

3rd party networks most can communicate to customer’s energy devices through broadband Internet routers (Wifi routers, cable modems, ADSL modems, Wimax modems, etc) and customers’ wireless/wireline HAN network (e.g. Zigbeen, HomePlug, etc) to manage in premise control switches, actuators, motors, energy resources, loads and other any other intelligent devices.

Public Internet will be the primary communica>on layer between u>lity enterprise data centers, market, and 3rd party energy providers.

A certain level of protocol security must be provided to all levels of energy management services through the Internet cloud. Most likely all 3rd party energy service providers and some u>lity services will be connected through the public Internet.

Markets will provide energy informa>on services with variable energy/electricity pricing informa>on to allow dynamic exchange of energy services to/from consumers and u>li>es, establishing a buyers/sellers energy market.

Markets will communicate to 3rd party providers and u>li>es through secure public Internet connec>ons.

Wireless Network

Public Internet

3rd Party Network

Markets

17

Smart Grid Logical Communica2ons Reference Architecture Interfaces/Connec2vity Defini2ons

Interface Descrip2on Comments

E1 U#lity Control/Opera#on, Enterprise LAN to/from Backhaul/WAN Network

Either owned by the u#lity or managed by a telecom service provider through a security connec#on (e.g. VPN)

E2 U#lity Control/Opera#on, Enterprise LAN to/from Distribu#on Automa#on/Field Devices

This is a centrally-‐based network where the communica#ons to/from u#lity center does not require backhaul. It is usually owned by the u#li#es.

E3 U#lity Control/Opera#on, Enterprise LAN to/from the Smart Meters

This is a centrally-‐based network where the communica#ons to/from u#lity center does not require backhaul. It is usually owned by the u#li#es.

E4 Backhaul to/from Access Point (AP) The AP is the demarca#on point between the NAN/FAN-‐AMI and the backhaul. It can be also called collector, aggrega#on point or gateway. It usually contains dual radio communica#ons interfaces, one facing the backhaul (e.g. 3G radio) and another one facing the last mile network (e.g. NAN RF mesh radio). It can be a mesh RF collector, a point-‐to-‐mul#point RF radio (e.g. Wimax) or a wireline access node (e.g. BPL/PLC).

E5 Backhaul to/from Distribu#on Substa#on Network (hot spot)

This is the connec#vity between the distribu#on substa#on networks and the u#lity control/opera#on/SCADA network via the backhaul WAN network. Typical connec#ons are usually a secure wireline (e.g. T1 line,, dial-‐up) or wireless point-‐to-‐point microwave radio links. In some cases, the substa#on networks are connected together.

18


E6 Backhaul/WAN Network to/from U#lity Scale Distributed Energy Resource (DER) and Storage Network

It provides the distributed energy resource (DER) communica#on integra#on to the grid (connec#ng u#lity scale solar/wind and other non-‐renewable DER)/microgrids to/from the backhaul/WAN network to/from the u#lity control/opera#ons and/or enterprise center. It also interconnects u#lity scale energy storage networks and systems.

E7 Access Point (AP) to/from Neighborhood Area Network (NAN)

The AP can also be considered as an element of the NAN, or just an interface between the NAN and the Backhaul.

E8 Neighborhood Area Network( NAN) to/from Distribu#on Network (Distributed Automa#on)

It interconnects the NAN (usually in this case also called Field Area Networks (FAN)) to the distribu#on network (distribu#on automa#on (DA)), also called Feeder Network which contains intelligent field devices that goes on poles, such as cap banks, reclosures, switches, smart transformers, field sensors, etc ). Some elements of the DA are also found within the distribu#on substa#ons.

E9 Neighborhood Area Network (NAN) to/from U#lity Scale Distributed Energy Resource (DER) and Storage Network

This is an alterna#ve to E6 where the connec#vity to the u#lity scale distributed energy resources, located within the u#lity’s distribu#on network, is done through the NAN/AMI network.

E10 Distribu#on Substa#on Network (hot spot) to/from Distribu#on Network (Distributed Automa#on)

It provides the connec#vity between the distribu#on substa#on networks and the distribu#on network (distribu#on automa#on) field devices. It can use radio or wireline (BPL/PLC) hubs (e.g. towers) within the distribu#on substa#on to connect to distribu#on network field devices.

E11 Distribu#on Substa#on Network (hot spot) to/from U#lity Scale Distributed Energy Resource (DER) and Storage Network

It interconnects the u#lity scale distributed energy resources (DER)/microgrids to/from the u#lity control/opera#ons/enterprise center through the distribu#on substa#ons.

E12 Neighborhood Area Network (NAN) to/from the Smart Meters

Connects the smart meters through wireline or wireless NAN. Smart meters could be residen#al (including building/business) or industrial-‐grade.

19


E13 Neighborhood Area Network (NAN) to/from Workforce Mobile Network

This could either be owned by the u#lity or managed by a wireless service provider. It interconnects the mobile work force (for workforce automa#on) with the u#lity control/opera#ons center through the NAN.

E14 Smart Meter to/from the Customer Premise Network

This is the internal connec#vity between the smart meter and the customer premise network, which can also be defined as Home Area Network (HAN), Building/Business Area Network (BAN) or Industrial Area Network (IAN). It uses in-‐premise wireline or wireless standards interfaces (e.g. ZigBee, HomePlug, Wifi, etc) to connect to customer’s devices.

E15 Customer Premise Network to/from Plug-‐in-‐Vehicles (PEV)

It provides connec#vity between the customer’s network and the PEV (usually through a Energy Service Interface (ESI) device). There are two cases for the PEV connec#vity; (i) sta#onary and (ii) mobile. The later is connected to a wireless service provider when the vehicle is mobile and/or roaming (see interface E18). The customer premise network could be residen#al, commercial or industrial scale.

E16 Customer Premise Network to/from Renewable Energy Resources/ Microgrids (Wind/Solar) and Storage Energy Systems

It provides connec#vity between the customer’s network and renewable energy resources/ microgrids (solar/wind) and storage energy systems.

E17 Customer Premise Network to/from Internet Service Provider

It connects the customer premise network to a Internet service provider (ISPs: DSL, Cable, Wimax, etc). It usually uses broadband routers to provide high speed Internet services to the end users.

E18 Plug-‐in-‐Vehicles (PEV) to/from Wireless Service Provider

This connec#vity is used when the vehicle is mobile and/or roaming and needs to access loca#on, pricing and/or billing informa#on using on-‐board energy informa#on systems. The wireless service provider could use 3G/GSM, 4G/Wimax or satellite transponder technology inside the vehicle.

E19 Wireless Service Provider to/from Internet Service Provider

It connects the Internet service providers (ISPs) to the mobile operator’s networks and vice-‐versa.

20


E20 Internet Service Provider to/from Public Internet

It connects the Internet service providers (ISPs) to the public Internet.

E21 Wireless Service Provider to/from Public Internet

It connects the wireless service providers (WSPs) to the public Internet.

E22 Wireless Service Provider to/from 3rd Party Network

It connects the wireless service providers (WSPs) to the 3rd Party Network (Value-‐Added Service (VAS) Provider).

E23 3rd Party Network to/from Public Internet It connects the 3rd Party Network (Value-‐Added Service (VAS) Provider) to the Public Internet.

E24 3rd Party Network to/from Markets It connects the 3rd Party Network (Value-‐Added Service (VAS) Provider) to the Markets for energy/electricity price signaling informa#on.

E25 3rd Party Network to/from U#lity Control/Opera#on, Enterprise LAN

It connects the 3rd Party Network (Value-‐Added Service (VAS) Provider) to the U#lity control/opera#on/enterprise center. Usually is part of an OpenADE data exchange arrangement where the 3rd party network access customer metering/billing and energy consump#on informa#on through u#lity’s data repositories. Other schemes involve 3rd party demand response and other services.

E26 Markets to/from Public Internet It connects the market with u#li#es and other 3rd party providers through the public Internet.

E27 U#lity Control/Opera#on, Enterprise LAN to/from Public Internet

It connects the u#lity control/opera#on/enterprise center to 3rd party service provider, Internet service provider, wireless service provider and other providers through the public Internet.

21

AMI Use Cases to Architecture Interfaces Mapping

22

Substa2on Automa2on and Energy Efficiency Management Through 3rd Party Value-‐Added Energy Provider Use Cases to Architecture Interfaces Mapping

23

smartgridlogical communicaons reference&architecture& p2030 smart... · smartgridlogical...

Documents