Geneva, 9 January 2012
RequirementsArchitecture
with Gap Analysis
Yoshito SAKURAIVice-chairFG Smart
(Hitachi, Ltd. Japan)
Workshop on Focus Group on Smart Grid
(Geneva, 9 January 2012)
Geneva, 9 January 2012 2
Contents
Requirements DeliverableWith Gap analysis
Architecture DeliverableWith Gap analysis
Geneva, 9 January 2012 3
Procedure to identify requirements
Use cases Requirements With Template
CategorizeMappingDescriptionsGap Analysis
Geneva, 9 January 2012 4
Procedure 1 (Requirements)
Use cases Requirements 83 use cases 174 requirements
All the requirements are described with template.
See example
Geneva, 9 January 2012 5
Template New Requirement No.
Identification of requirements in main text
Requirement No. Identification of requirements
Domains / Address
Position of Requirements
Identification of planes and layers
Requirement Description of requirement(s)
Type of requirement Required or May Optionally, and its condition if needed.
Background Description for readability is provided.
Reference
Gap analysis Relationship between this requirement and conventional standard
6
Example (Requirement)
New Requirement No. COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-RRequirement No. I-i-0035-1Domains / Address WANPosition of requirements
Plane: Transport
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 should be controlled to comply with IP layer performance.
Type of requirement Required in the case of transport on NGN or managed IP network
May Optionally in other casesBackground Information for smart grid includes critical data which is
sensitive of delay, delay variation, and loss. Therefore, performance on WAN should be clarified.
Reference ITU-T Y.1541Gap 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.
Appendix I: Source materials for requirements
Geneva, 9 January 2012 7
Example (Requirement) New Requirement No. COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-RRequirement No. I-i-0035-1Address WANPosition of requirements Plane: Transport
Layer: Network and Data Link LayersRequirement 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.
Type of requirement Required in the case of transport on NGN or managed IP network
May Optionally in other casesBackground Information for smart grid includes critical data which is sensitive of
delay, delay variation, and loss. Therefore, performance on WAN should be clarified.
Reference ITU-T Y.1541Gap 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.
<A-B-XX-C-D>A S/A: Services/Applications
COM: CommunicationPHY: Physical Equipment
B Sub-clause titleXX Sequential numberC Source of a requirement I: Input document / U: Use case D Requirement type RQ: Required / P: Prohibited / R: Recommended / O: may Optionally
Geneva, 9 January 2012 8
Example (Requirement) New Requirement No. COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-RRequirement No. I-i-0035-1Address WANPosition of requirements Plane: Transport
Layer: Network and Data Link LayersRequirement 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.
Type of requirement Required in the case of transport on NGN or managed IP network
May Optionally in other casesBackground Information for smart grid includes critical data which is sensitive of
delay, delay variation, and loss. Therefore, performance on WAN should be clarified.
Reference ITU-T Y.1541Gap 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.
Original Contribution Number
Related Domain or Target Address
Reference Documents
Geneva, 9 January 2012 9
Example (Requirement) New Requirement No. COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-RRequirement No. I-i-0035-1Address WANPosition of requirements Plane: Transport
Layer: Network and Data Link LayersRequirement 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.
Type of requirement Required in the case of transport on NGN or managed IP network
May Optionally in other casesBackground Information for smart grid includes critical data which is sensitive of
delay, delay variation, and loss. Therefore, performance on WAN should be clarified.
Reference ITU-T Y.1541Gap 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.
Requirement: 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.
Type of requirement:
Required in the case of transport on NGN or managed IP network,
May Optionally in other cases.
Geneva, 9 January 2012 10
Example (Requirement) New Requirement No. COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-RRequirement No. I-i-0035-1Address WANPosition of requirements Plane: Transport
Layer: Network and Data Link LayersRequirement 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.
Type of requirement Required in the case of transport on NGN or managed IP network
May Optionally in other casesBackground Information for smart grid includes critical data which is sensitive of
delay, delay variation, and loss. Therefore, performance on WAN should be clarified.
Reference ITU-T Y.1541Gap 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.
Background information
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 11
Procedure 2 (Requirements)
CategorizeSmart Grid Services/Applications areaCommunication areaPhysical Equipment area
See Fig.3 of Overview (Clause 7)
Geneva, 9 January 2012 12
Procedure 3: Example of Mappingb/w Use cases & Requirements
Use cases Services/ Applications
Communi-cation area
Physical Equipment
Demand Response
--- --- --- ---
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
DR & CEE2 Customer Uses an EMS or IHD
N/A COM-CN-Gen-01-I-R
PHY-MaSP-02-I-O
DR & CEE3 Customer Uses Smart Appliances
N/A COM-CN-Gen-02-I-R
PHY-MaSP-03-I-O
Annex A: Summary of Smart Grid Requirements with Use cases
Geneva, 9 January 2012 13
Procedure 4 (Requirements)
Descriptions (Clause 7, 8, 9 of the deliverable)
7 Requirements for Grid Services/Applications area
7.1 Customer domain7.2 Operation domain7.3 Service Provider domain7.4 Markets domain7.5 Bulk Generation domain7.6 Transmission and Distribution domains7.7 Multi domains
Geneva, 9 January 2012 14
Procedure 4 cont. (Requirements)
8 Requirements for Communication area8.1 Communication Network domain8.2 Information Access domain
9. Requirements for Physical Equipment area9.1 Customer domain9.2 Distribution domain9.3 Operation domain9.4 Market/ Service Provider domains9.5 Bulk Generation and Transmission domains9.6 Multi domains
Geneva, 9 January 2012 15
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 16
174 requirements 273 relations with study status
Gap analysis (Requirements)
SDOsAlready studied
For further study
Study in progress
Not identified
Total
ITU-T 89 24 27 140
IEC 5 8 23 19 55
3GPP 5 18 23
ETSI 8 1 8 17
IEEE 10 4 2 16ISO/IEC JTC
16 2 1 9
IETF 5 2 1 8
ITU-R 4 1 5
Total 132 35 84 22 273
Geneva, 9 January 2012 17
ITU-T 51%
Geneva, 9 January 2012 18
ITU-T 51%
Geneva, 9 January 2012 19
SG1331%
Geneva, 9 January 2012 20
Geneva, 9 January 2012 21
Architecture Deliverable(Clause 6,7 of the deliverable)
6 Reference architecture6.1 Simplified Domain Model in ICT perspective6.2 Reference Architecture of Smart Grid
7 Functional Architecture7.1 Functional Model of Smart Grid7.2 Detailed Functional Architecture of Smart Grid7.2.1 Functional Architecture of Smart Metering and Load Control7.2.2 Functional Architecture of Energy Distribution and Management
Geneva, 9 January 2012 22
Reference Architecture
Operations(RTO/ISO/Transmission/Distribution Ops)
MarketsRetailer /
Wholesaler
Aggregator
Energy Market Clearinghouse
ISO/RTO Participant
Market Services Interface
Plant Control System
Generators
EMS WAMS
SCADA
PrivateNetworks/
LAN
PrivateNetworks/
LAN
Metering System
Bulk Generation/Transmission/Distribution
Service ProvidersUtility
ProviderCIS
Billing
Third-Party Provider
Retail Energy Provider
CIS
Billing
Home/Building Manager Provider
Aggregator Others
Common Functionality Platform Provider
GW/Energy Service
Interface (ESI)
Smart metering
Customer Equipment,
HVAC,SmartAppliances,
CustomerEMS
Electric Storage
Electric Vehicle
LANLAN
Substation Devices
Field Devices/ sensors
Distributed Generation
Substation Controller
Electric Storage
Data collector
Applications/Data base mgnt
Demand Response
Backbone Networks
Distributed Generation
Service Provider domain
Grid domain Customer domain
4
32
5
1
Communication NetworkCommunication Network
Premises Networks(HAN, LAN)
Premises Networks(HAN, LAN)
Operations(RTO/ISO/Transmission/Distribution Ops)
MarketsRetailer /
Wholesaler
Aggregator
Energy Market Clearinghouse
ISO/RTO Participant
Market Services Interface
Plant Control System
Generators
EMS WAMS
SCADA
PrivateNetworks/
LAN
PrivateNetworks/
LAN
Metering System
Bulk Generation/Transmission/Distribution
Service ProvidersUtility
ProviderCIS
Billing
Third-Party Provider
Retail Energy Provider
CIS
Billing
Home/Building Manager Provider
Aggregator Others
Common Functionality Platform Provider
GW/Energy Service
Interface (ESI)
Smart metering
Customer Equipment,
HVAC,SmartAppliances,
CustomerEMS
Electric Storage
Electric Vehicle
LANLAN
Substation Devices
Field Devices/ sensors
Distributed Generation
Substation Controller
Electric Storage
Data collector
Applications/Data base mgnt
Demand Response
Backbone Networks
Distributed Generation
Service Provider domain
Grid domain Customer domain
4
32
5
1
Communication NetworkCommunication Network
Premises Networks(HAN, LAN)
Premises Networks(HAN, LAN)
Geneva, 9 January 2012 23
Functional Model (Smart Grid)
Resilience& Recovery
Geneva, 9 January 2012 24
Functional Model (Smart Metering and Load Control Service)
End-User functions
Power Grid Functions Application Functions
Smart Metering Functions Energy Control Functions
Network Functions
Security Physical, System
s, operations F
unctions Authentication and Identification , A
ccountability A
ccess Control, D
ata Integrity, Privacy P
ersevering
Managem
ent Functions Application M
anagement Function
Device M
anagement Function
Netw
ork Managem
ent Function
Two-way Power
Function
Substation LAN/SCADA real-time data transport
DR Function
PEV charging Function
Home/ Business/ Industrial Network FunctionHAN/ BAN/ IAN configuration function
Information Handling/Storage Function
Smart Meter Headend Function
DR Application Function
Energy Pricing Function
Business Data Transport Function
Customer Subscription/ Billing Function
Meter Reading Function
Load Monitor& Control Function
Metering Data TransportFunction
Core Data Transport function
DR Client function
Home/ Industrial
energy mgmt
function
Generation & Storage
Management Function
ESI function (gateway/ sec)
Load Monitor &
Control Function
Meter Control & Maintenance Function
Fault Monitoring & Protection
Geneva, 9 January 2012 25
Functional Model (Power Grid Monitoring and Control)
Managem
ent Functions
Application Managem
ent FunctionDevice M
anagement Function
Network M
anagement Function
Security Physical, System
s, operations F
unctions Authentication and Identification , Accountability Access Control, Data Integrity, Privacy Persevering
Smart Metering Functions
End-User functions
Power Grid Functions
Application Functions
Energy Control Functions
Network Functions
DER (local Generation
and Storage) Function
Home/ Business/ Industrial Network Function
DER Function
Protection and Control
Function
Core Data Transport Function
DER Control
Function
QoSManagement
Function SCADA Real-time Transport Function
Fault Location/Isolation/Recovery Function
Sensing & Measurement Function
Time Synchroniza
tion Function
Data Aggregation
Function
Substation LAN/SCADA real-time data transport
ESI/LAN
Data Aggregation/ De-Aggregation
Function
Time Synchronization Function
Wide Area Awareness Function
DR Application Function
Operation Control Function
Asset Management
Function
Geneva, 9 January 2012 26
Functional Model (Energy Usage and Distribution Management)
Security Physical, System
s, operations F
unctions Authentication and Identification , Accountability Access Control, Data Integrity, Privacy Persevering
Managem
ent Functions
Application Managem
ent FunctionDevice M
anagement Function
Network M
anagement Function
End-User functions
Power Grid Functions
Application Functions
Smart Metering Functions Energy Control Functions
Network Functions
Protection and
Control Function
DER (Distributed Generation)
Function
Substation LAN/SCADA real-time data transport
DR Client Function
DER (Local Generation
and Storage) Function
Home/ Business / Industrial Network Function
ESI/LAN
Energy Usage Management Function
Smart Meter Headend Function
DR Application Function
Demand Forecast Function
Capacity planning function
Wholesale Marketing Function
Meter Reading FunctionDER control Function
Load Monitor& Control Function
SCADA Real-Time Transport
Function QoSManagement Function
Core data Transport function
Geneva, 9 January 2012 27
Smart Grid Network Architecture(A Home with Multiple Networks and Connections to
Utility Network and Other External Networks)
Utility HAN
Residential Broadband Network
Router
ESI
Utility Network
(NAN)
ISP IP Network
Geneva, 9 January 2012 28
Architecture Deliverable(Clause 8 of the deliverable)
8 Deployment Model of Smart Grid8.1 Networks in Smart Grid8.2 Smart Grid Network Architecture8.2.1 Home Area Network Architecture8.2.2 Neighborhood Area Network
Architecture8.2.3 Wide Area Network Architecture
Geneva, 9 January 2012 29
Architecture Deliverable(Clause 9 of the deliverable)
9 Sample Implementation of Smart Grid Applications9.1 ITU-T G.9970 Home Network Transport and Application Layer Architecture9.2 Architecture with the HAN and Relevant External Interactions9.3 Architecture Focusing on Interface between HGW and PEV9.4 Example of Implementation Platforms to Support Energy Management Services9.5 Architecture of a Communication Infrastructure to Provide Energy Related Services
Geneva, 9 January 2012 30
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 31
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 Point 1
This reference point provides connectivity between the power grid domain and service provider, customer, and smart meter domains through communication networks. …………..Distributed Energy Resources (DER):
PAP07: Energy Storage Interconnection Guidelines:
HD 60634:IEC 61850-7-420:IEC 61850-7-410:EN 61400-25:
Analysis of Reference Point Functions(Part of Table 2 in clause 10)
Geneva, 9 January 2012 32
Standardization Activities for Smart Grid Networks (Part of Table 3 in clause 10)
Communications
technologies
Standardization activities StatusNote
(related works)
IMT ITU-R IMT-2000 familyITU-R IMT-Advanced familyITU-T SG133GPP
Already studied
NIST SGIP PAP02
Power Line Communication (PLC)
TU-T SG15 G.9960/9961(G.hn), G.9963 (G.hn-MIMO), G.9972 (G.cx), G.9955/9956 (G.hnem)
Already studied
IEEE 1901 Already studied
IEEE1901.2
ISO/IEC Study in progress
ISO/IEC15118 (V2G CI)
Thank you!
Recommended