Workshop on Focus Group on Smart Grid
(Geneva, 9 January 2012)
Requirements
Architecture
with Gap Analysis
Yoshito SAKURAI
Vice-chair
FG Smart
(Hitachi, Ltd. Japan)
Geneva, 9 January 2012
Contents
Requirements Deliverable
With Gap analysis
Architecture Deliverable
With Gap analysis
Geneva, 9 January 2012
2
Procedure to identify requirements
Use cases  Requirements
With Template
Categorize
Mapping
Descriptions
Gap Analysis
Geneva, 9 January 2012
3
Procedure 1 (Requirements)
Use cases  Requirements
83 use cases  174 requirements
All the requirements are described
with template.
 See example
Geneva, 9 January 2012
4
Template
New Requirement
No.
Requirement No.
Identification of requirements in main text
Identification of requirements
Domains / Address
Position of
Requirements
Requirement
Identification of planes and layers
Type of requirement
Required or May Optionally, and its condition
if needed.
Background
Description for readability is provided.
Description of requirement(s)
Reference
Gap analysis
Geneva, 9 January 2012
Relationship between this requirement and
conventional standard
5
Example (Requirement)
Appendix I: Source materials for requirements
New Requirement No.
Requirement No.
Domains / Address
Position of
requirements
COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R
I-i-0035-1
WAN
Plane: Transport
Requirement
If information is communicated on IP, QoS class should be
specified in each communication for smart grid. Required
performance between edges of WAN on IP layer should be
specified every application, and should be categorized into
Classes 0, 1, 2, 3, 4, U according to ITU-T Y.1541 [ITU-T
Y.1541]. Moreover, on data link layer, performance should be
controlled to comply with IP layer performance.
Required in the case of transport on NGN or managed IP
network
Type of requirement
Background
Reference
Gap analysis
Layer: Network and Data Link Layers
May Optionally in other cases
Information for smart grid includes critical data which is
sensitive of delay, delay variation, and loss. Therefore,
performance on WAN should be clarified.
ITU-T Y.1541
Currently, ITU-T Y.1541 does not mention smart gird in
guidance for IP QoS classes. Since smart grid can be supported
as an application on NGN or other managed IP network
including utility network, smart grid should be added to
6
guidance for IP QoS classes.
Example (Requirement)
New Requirement No.
Requirement No.
Address
Position of requirements
Requirement
Type of requirement
Background
Reference
Gap analysis
Geneva, 9 January 2012
COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R
I-i-0035-1
WAN
Plane: Transport
<A-B-XX-C-D>
Layer: Network
and Data Link Layers
If information
isS/A:
communicated
on IP, QoS class should be specified
A
Services/Applications
in each communication for smart grid. Required performance between
COM:
edges of WAN on
IP layerCommunication
should be specified every application, and
should be categorized
into
Classes 0, 1,Equipment
2, 3, 4, U according to ITU-T
PHY:
Physical
Y.1541 [ITU-T Y.1541]. Moreover, on data link layer, performance
Sub-clause
title
shouldB
be controlled
to comply with
IP layer performance.
Required
case of transportnumber
on NGN or managed IP network
XXin the Sequential
May Optionally in other cases
C
Source of a requirement
Information for smart grid includes critical data which is sensitive of
delay, delay variation,
and loss.
Therefore, performance
WAN
I: Input
document
/ U: Useoncase
should be clarified.
D
Requirement type
ITU-T Y.1541
Currently, ITU-T
Y.1541
does not mention
gird in guidance
RQ:
Required
/ P: smart
Prohibited
/ for
IP QoS classes. Since smart grid can be supported as an application on
R: Recommended / O: may Optionally
NGN or other managed IP network including utility network, smart
grid should be added to guidance for IP QoS classes.
7
Example (Requirement)
New Requirement No.
Requirement No.
Address
Position of requirements
COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R
I-i-0035-1
WAN
Plane: Transport
Original Contribution Number
Layer: Network and Data Link Layers
Requirement
If information is communicated on IP, QoS class should be specified
in each communication for smart grid. Required performance between
edges of WAN on IP layer should be specified every application, and
should be categorized into Classes 0, 1, 2, 3, 4, U according to ITU-T
Y.1541 [ITU-T Y.1541]. Moreover, on data link layer, performance
Related Domain
shouldor
be controlled to comply with
IP layer performance.
Reference
Type of requirement
Required in the case of transport on NGN or managed IP network
Target Address
Background
Reference
Gap analysis
Geneva, 9 January 2012
Documents
May Optionally in other cases
Information for smart grid includes critical data which is sensitive of
delay, delay variation, and loss. Therefore, performance on WAN
should be clarified.
ITU-T Y.1541
Currently, ITU-T Y.1541 does not mention smart gird in guidance for
IP QoS classes. Since smart grid can be supported as an application on
NGN or other managed IP network including utility network, smart
grid should be added to guidance for IP QoS classes.
8
Example (Requirement)
New Requirement No.
Requirement No.
Address
Position of requirements
Requirement
Type of requirement
Background
Reference
Gap analysis
Geneva, 9 January 2012
COM-CN-QoS-05-I-R,
COM-CN-QoS-06-I-R
Requirement:
Required performance
I-i-0035-1
between edges of WAN on IP layer
WAN
should be specified every application,
Plane: Transport
and
categorized into
Layer: Network
andshould
Data Link be
Layers
0, 1,on2,IP,3,
U should
according
to
If informationClasses
is communicated
QoS4,
class
be specified
in each communication
for smart grid. Required performance between
ITU-T Y.1541.
edges of WAN on IP layer should be specified every application, and
should be categorized into Classes 0, 1, 2, 3, 4, U according to ITU-T
Y.1541 [ITU-T Y.1541]. Moreover, on data link layer, performance
should be controlled to comply with IP layer performance.
Required in the case of transport on NGN or managed IP network
May Optionally in other cases
Information for smart grid includes critical data which is sensitive of
delay, delay variation,
Therefore, performance on WAN
Typeandofloss.
requirement:
should be clarified.
ITU-T Y.1541 Required in the case of transport
Currently, ITU-Ton
Y.1541
does or
not mention
smart gird
guidance for
NGN
managed
IPinnetwork,
IP QoS classes. Since smart grid can be supported as an application on
May IP
Optionally
in other
cases.
NGN or other managed
network including
utility network,
smart
grid should be added to guidance for IP QoS classes.
9
Example (Requirement)
New Requirement No.
COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R
Requirement No.
I-i-0035-1
Address
WAN
Gap analysis:
Background
Position of requirements Plane: Transport
ITU-T Y.1541 does
information Layer: NetworkCurrently,
and Data Link Layers
not
mention
smart
gird
in
Requirement
If information is
communicated
on IP, QoS
class should
be specified
in each communication
for smart for
grid. Required
performance
between
guidance
IP QoS
classes.
edges of WAN on IP layer should be specified every application, and
Since
be to ITU-T
should be categorized
into smart
Classes 0, 1,grid
2, 3, 4, can
U according
Y.1541 [ITU-Tsupported
Y.1541]. Moreover,as
on data
layer, performance
anlinkapplication
should be controlled to comply with IP layer performance.
NGN
oron other
managed
Type of requirement
Required in theon
case of
transport
NGN or managed
IP networkIP
May Optionallynetwork
in other cases including utility
Background
Information for smart grid includes critical data which is sensitive of
network, smart grid should
delay, delay variation, and loss. Therefore, performance on WAN
be added to guidance for IP
should be clarified.
Reference
ITU-T Y.1541
QoS classes
Gap analysis
Currently, ITU-T Y.1541 does not mention smart gird in guidance for
IP QoS classes. Since smart grid can be supported as an application on
NGN or other managed IP network including utility network, smart
grid should be added to guidance for IP QoS classes.
Geneva, 9 January 2012
10
Procedure 2 (Requirements)
Categorize
Smart Grid Services/Applications area
Communication area
Physical Equipment area
See Fig.3 of Overview (Clause 7)
Geneva, 9 January 2012
11
Procedure 3: Example of Mapping
b/w Use cases & Requirements
Annex A: Summary of Smart Grid Requirements with Use cases
Use cases
Demand
Response
.
.
.
Services/
Applications
Communication area
Physical
Equipment
---
---
---
---
.
.
.
.
.
.
.
.
.
.
.
.
DR & CEE2
Customer
Uses an
EMS or IHD
N/A
COM-CNGen-01-I-R
PHY-MaSP02-I-O
DR & CEE3
Customer
Uses Smart
Appliances
N/A
COM-CNGen-02-I-R
PHY-MaSP03-I-O
Geneva, 9 January 2012
12
Procedure 4 (Requirements)
Descriptions
7
(Clause 7, 8, 9 of the deliverable)
Requirements for
Grid Services/Applications area
7.1
Customer domain
7.2
Operation domain
7.3
Service Provider domain
7.4
Markets domain
7.5
Bulk Generation domain
7.6
Transmission and Distribution domains
7.7
Multi domains
Geneva, 9 January 2012
13
Procedure 4 cont. (Requirements)
8
Requirements for Communication area
8.1
Communication Network domain
8.2
Information Access domain
9. Requirements for Physical Equipment area
9.1
Customer domain
9.2
Distribution domain
9.3
Operation domain
9.4
Market/ Service Provider domains
9.5
Bulk Generation and Transmission domains
9.6
Multi domains
Geneva, 9 January 2012
14
Procedure 5 (Requirements)
Gap Analysis
(Clause 10)
174 requirements 
273 relations with SDOs (incl. ITU-T)
Note: One requirement often relates
plural SDOs such as
……… IEC and ITU-T, IEEE and IETF, etc.
Geneva, 9 January 2012
15
Gap analysis (Requirements)
174 requirements  273 relations
with study status
SDOs
Already
studied
ITU-T
IEC
3GPP
ETSI
IEEE
ISO/IEC
JTC 1
IETF
ITU-R
Total
Geneva, 9 January 2012
89
5
5
8
10
6
5
4
132
For
Study in
Not
further
Total
progress identified
study
24
27
140
8
23
19
55
18
23
1
8
17
4
2
16
2
1
35
2
1
84
9
1
22
8
5
273
16
ITU-T
51%
Geneva, 9 January 2012
17
ITU-T
51%
Geneva, 9 January 2012
18
SG13
31%
Geneva, 9 January 2012
19
Geneva, 9 January 2012
20
Architecture Deliverable
(Clause 6,7 of the deliverable)
6
6.1
6.2
Reference architecture
Simplified Domain Model in ICT perspective
Reference Architecture of Smart Grid
7
Functional Architecture
7.1 Functional Model of Smart Grid
7.2 Detailed Functional Architecture of Smart Grid
7.2.1 Functional Architecture of Smart Metering
and Load Control
7.2.2 Functional Architecture of Energy Distribution
and Management
Geneva, 9 January 2012
21
Reference Architecture
Service Provider domain
Service Providers
Operations
Markets
Utility
Provider
(RTO/ISO/Transmission/Distribution Ops)
Retailer /
Wholesaler
WAMS
EMS
Applications/Data base mgnt
Third-Party Provider
CIS
Aggregator
Energy Market
Clearinghouse
Demand Response
Private
Private
Networks/
Networks/
LAN
LAN
SCADA
ISO/RTO
Participant
CIS
Retail Energy
Provider
Billing
Home/Building
Manager Provider
Billing
Common Functionality
Platform Provider
Metering System
Aggregator
Others
4
Backbone Networks
Communication
Communication Network
Network
1
2
Market Services
Interface
Data collector
LAN
LAN
Field Devices/
sensors
Plant Control
System
Generators
Electric Storage
Substation
Devices
Substation
Controller
Distributed
Generation
3
Electric
Vehicle
Smart
metering
GW/Energy
Service
Interface (ESI)
5
Customer
EMS
Distributed
Generation
Premises
Premises Networks
Networks
(HAN,
(HAN, LAN)
LAN)
Customer
Equipment,
HVAC,Smart
Appliances,
Electric
Storage
Bulk Generation/Transmission/Distribution
Grid domain
Geneva, 9 January 2012
Customer domain
22
Functional Model (Smart Grid)
Resilience& Recovery
Geneva, 9 January 2012
23
Functional Model
(Smart Metering and Load Control Service)
DR Function
Customer Subscription/
Billing Function
Smart Meter Headend Function
DR Client
function
DR Application
Function
Home/
Industrial
energy
mgmt
function
Information
Handling/Storage
Function
Business Data
Transport Function
Energy Control Functions
Smart Metering Functions
Meter Reading Function
Home/ Business/
Industrial
Network Function
HAN/ BAN/ IAN
configuration
function
Fault Monitoring & Protection
Load Monitor& Control Function
Meter Control & Maintenance
Function
ESI function
(gateway/ sec)
Substation
LAN/SCADA
real-time
data
transport
PEV charging
Function
Load
Monitor &
Control
Function
Physical, Systems, operations
Authentication and Identification , Accountability
Access Control, Data Integrity, Privacy Persevering
Energy Pricing Function
Security
Functions
Application Functions
Management Functions
Power Grid
Functions
Application Management Function
Device Management Function
Network Management Function
End-User
functions
Network Functions
Generation &
Storage
Management
Function
Core Data
Transport function
Two-way
Power
Function
Geneva, 9 January 2012
Metering Data TransportFunction
24
Functional Model
(Power Grid Monitoring and Control)
DER (local
Generation
and Storage)
Function
DER
Function
Protection
and Control
Function
Smart Metering
Functions
Sensing &
Measureme
nt Function
Home/
Business/
Industrial
Network
Function
Data
Aggregation
Function
Substation
LAN/SCADA
real-time
data
transport
Geneva, 9 January 2012
Energy Control Functions
DER
Control
Function
Fault
Location/Isol
ation/Recove
ry Function
Time
Synchroniza
tion
Function
ESI/LAN
Operation Control
Function
Asset
Management
Function
Wide Area
Awareness
Function
Time Synchronization
Function
Data Aggregation/
De-Aggregation
Function
Network Functions
QoS
Management
Function
Core Data
Transport
Function
Physical, Systems, operations
Authentication and Identification , Accountability
Access Control, Data Integrity, Privacy Persevering
DR Application
Function
Security
Functions
Application Functions
Management Functions
Power Grid
Functions
Application Management Function
Device Management Function
Network Management Function
End-User
functions
SCADA Real-time
Transport
Function
25
Functional Model
(Energy Usage and Distribution Management)
DR
Application
Function
Demand Forecast
Function
Energy Usage
Management
Function
Smart Metering Functions
Wholesale
Marketing
Function
Capacity planning
function
Energy Control Functions
DER control
Function
Meter Reading Function
Load Monitor& Control
Function
Home/
Business /
Industrial
Network
Function
ESI/LAN
Network Functions
Substation
LAN/SCADA
real-time
data
transport
Geneva, 9 January 2012
SCADA RealTime Transport
Function
QoS
Management
Function
Physical, Systems, operations
Authentication and Identification , Accountability
Access Control, Data Integrity, Privacy Persevering
Protection
and
Control
Function
Smart Meter
Headend Function
Security
Functions
DER (Local
Generation
and Storage)
Function
DER
(Distributed
Generation)
Function
Application Functions
Management Functions
DR Client
Function
Power Grid
Functions
Application Management Function
Device Management Function
Network Management Function
End-User
functions
Core data
Transport
function
26
Smart Grid Network Architecture
(A Home with Multiple Networks and Connections to
Utility Network and Other External Networks)
Utility
ISP IP
Network Network
(NAN)
Router
ESI
Utility
HAN
Geneva, 9 January 2012
Residential
Broadband
Network
27
Architecture Deliverable
(Clause 8 of the deliverable)
8
8.1
8.2
8.2.1
8.2.2
8.2.3
Deployment Model of Smart Grid
Networks in Smart Grid
Smart Grid Network Architecture
Home Area Network Architecture
Neighborhood Area Network Architecture
Wide Area Network Architecture
Geneva, 9 January 2012
28
Architecture Deliverable
(Clause 9 of the deliverable)
9
Sample Implementation of Smart Grid Applications
9.1 ITU-T G.9970 Home Network Transport
and Application Layer Architecture
9.2 Architecture with the HAN
and Relevant External Interactions
9.3 Architecture Focusing on Interface
between HGW and PEV
9.4 Example of Implementation Platforms
to Support Energy Management Services
9.5 Architecture of a Communication Infrastructure
to Provide Energy Related Services
Geneva, 9 January 2012
29
Architecture Deliverable
(Clause 10 of the deliverable)
10
Standards Gap Analysis
10.1
Functions across Reference Points
and Applicable Standards
10.2
Recommendations for Future Work
Geneva, 9 January 2012
30
Analysis of Reference Point Functions
(Part of Table 2 in clause 10)
Reference
Point
Information/
Operations
Across the
Reference
Point
Gaps being
Addressed by
SGIP Priority
Action Plans
and Related
Standards
Partial List of
Relevant
Standards in
Addition to those
in PAP Column
Reference This reference point provides connectivity
Point 1
between the power grid domain and service
provider, customer, and smart meter domains
through communication networks. …………..
Distributed
Energy
Resources
(DER):
Geneva, 9 January 2012
PAP07: Energy
Storage
Interconnectio
n Guidelines:
HD 60634:
IEC 61850-7-420:
IEC 61850-7-410:
EN 61400-25:
31
Standardization Activities for Smart
Grid Networks (Part of Table 3 in clause 10)
Communi
cations
Standardization activities
technolo
gies
IMT
ITU-R IMT-2000 family
ITU-R IMT-Advanced family
ITU-T SG13
3GPP
Power
Line
Communi
cation
(PLC)
Status
Note
(related
works)
Already
studied
NIST SGIP
PAP02
TU-T SG15 G.9960/9961(G.hn), Already
G.9963 (G.hn-MIMO),
studied
G.9972 (G.cx),
G.9955/9956 (G.hnem)
IEEE 1901
Already
studied
ISO/IEC
Geneva, 9 January 2012
Study in
progress
IEEE1901.2
ISO/IEC151
18 (V2G CI)
32
Thank you!
yoshito.sakurai.hn@hitachi.com