Geneva, 9 January 2012 Requirements Architecture with Gap Analysis Yoshito SAKURAI Vice-chair FG Smart (Hitachi, Ltd. Japan) Workshop on Focus Group on Smart Grid (Geneva, 9 January 2012)

Geneva, 9 January Contents Requirements Deliverable With Gap analysis Architecture Deliverable With Gap analysis

Geneva, 9 January Procedure to identify requirements Use cases Requirements With Template Categorize Mapping Descriptions Gap Analysis

Geneva, 9 January Procedure 1 (Requirements) Use cases Requirements 83 use cases 174 requirements All the requirements are described with template. See example

Geneva, 9 January 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 RequirementDescription of requirement(s) Type of requirementRequired or May Optionally, and its condition if needed. BackgroundDescription for readability is provided. Reference Gap analysisRelationship between this requirement and conventional standard

6 Example (Requirement) New Requirement No.COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R Requirement No.I-i Domains / AddressWAN Position of requirements Plane: Transport Layer: Network and Data Link Layers RequirementIf 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 requirementRequired in the case of transport on NGN or managed IP network May Optionally in other cases BackgroundInformation for smart grid includes critical data which is sensitive of delay, delay variation, and loss. Therefore, performance on WAN should be clarified. ReferenceITU-T Y.1541 Gap analysisCurrently, 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 Example (Requirement) New Requirement No.COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R Requirement No.I-i AddressWAN Position of requirementsPlane: Transport Layer: Network and Data Link Layers RequirementIf 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 requirementRequired in the case of transport on NGN or managed IP network May Optionally in other cases BackgroundInformation for smart grid includes critical data which is sensitive of delay, delay variation, and loss. Therefore, performance on WAN should be clarified. ReferenceITU-T Y.1541 Gap analysisCurrently, 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. AS/A: Services/Applications COM: Communication PHY: Physical Equipment BSub-clause title XXSequential number CSource of a requirement I: Input document / U: Use case DRequirement type RQ: Required / P: Prohibited / R: Recommended / O: may Optionally

Geneva, 9 January Example (Requirement) New Requirement No.COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R Requirement No.I-i AddressWAN Position of requirementsPlane: Transport Layer: Network and Data Link Layers RequirementIf 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 requirementRequired in the case of transport on NGN or managed IP network May Optionally in other cases BackgroundInformation for smart grid includes critical data which is sensitive of delay, delay variation, and loss. Therefore, performance on WAN should be clarified. ReferenceITU-T Y.1541 Gap analysisCurrently, 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 Example (Requirement) New Requirement No.COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R Requirement No.I-i AddressWAN Position of requirementsPlane: Transport Layer: Network and Data Link Layers RequirementIf 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 requirementRequired in the case of transport on NGN or managed IP network May Optionally in other cases BackgroundInformation for smart grid includes critical data which is sensitive of delay, delay variation, and loss. Therefore, performance on WAN should be clarified. ReferenceITU-T Y.1541 Gap analysisCurrently, 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 Type of requirement: Required in the case of transport on NGN or managed IP network, May Optionally in other cases.

Geneva, 9 January Example (Requirement) New Requirement No.COM-CN-QoS-05-I-R, COM-CN-QoS-06-I-R Requirement No.I-i AddressWAN Position of requirementsPlane: Transport Layer: Network and Data Link Layers RequirementIf 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 requirementRequired in the case of transport on NGN or managed IP network May Optionally in other cases BackgroundInformation for smart grid includes critical data which is sensitive of delay, delay variation, and loss. Therefore, performance on WAN should be clarified. ReferenceITU-T Y.1541 Gap analysisCurrently, 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 Procedure 2 (Requirements) Categorize Smart Grid Services/Applications area Communication area Physical Equipment area See Fig.3 of Overview (Clause 7)

Geneva, 9 January Procedure 3: Example of Mapping b/w Use cases & Requirements Use cases Services/ Applications Communi- cation area Physical Equipment Demand Response DR & CEE2Customer Uses an EMS or IHD N/ACOM-CN- Gen-01-I-R PHY-MaSP- 02-I-O DR & CEE3Customer Uses Smart Appliances N/ACOM-CN- Gen-02-I-R PHY-MaSP- 03-I-O Annex A: Summary of Smart Grid Requirements with Use cases

Geneva, 9 January Procedure 4 (Requirements) Descriptions (Clause 7, 8, 9 of the deliverable) 7Requirements 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 Procedure 4 cont. (Requirements) 8Requirements for Communication area 8.1Communication Network domain 8.2Information Access domain 9.Requirements for Physical Equipment area 9.1Customer domain 9.2Distribution domain 9.3Operation domain 9.4Market/ Service Provider domains 9.5Bulk Generation and Transmission domains 9.6Multi domains

Geneva, 9 January 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 requirements 273 relations with study status Gap analysis (Requirements) SDOs Already studied For further study Study in progress Not identified Total ITU-T IEC GPP ETSI IEEE ISO/IEC JTC IETF5 218 ITU-R4 1 5 Total

Geneva, 9 January ITU-T 51%

Geneva, 9 January ITU-T 51%

Geneva, 9 January SG13 31%

Geneva, 9 January

Geneva, 9 January Architecture Deliverable (Clause 6,7 of the deliverable) 6 Reference architecture 6.1Simplified Domain Model in ICT perspective 6.2Reference Architecture of Smart Grid 7 Functional Architecture 7.1 Functional Model of Smart Grid 7.2Detailed Functional Architecture of Smart Grid 7.2.1Functional Architecture of Smart Metering and Load Control 7.2.2Functional Architecture of Energy Distribution and Management

Geneva, 9 January Reference Architecture

Geneva, 9 January Functional Model (Smart Grid) Resilience& Recovery

Geneva, 9 January Functional Model (Smart Metering and Load Control Service)

Geneva, 9 January Functional Model (Power Grid Monitoring and Control)

Geneva, 9 January Functional Model (Energy Usage and Distribution Management)

Geneva, 9 January Smart Grid Network Architecture (A Home with Multiple Networks and Connections to Utility Network and Other External Networks)

Geneva, 9 January Architecture Deliverable (Clause 8 of the deliverable) 8 Deployment Model of Smart Grid 8.1 Networks in Smart Grid 8.2 Smart Grid Network Architecture Home Area Network Architecture Neighborhood Area Network Architecture Wide Area Network Architecture

Geneva, 9 January 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 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 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 Interconnectio n Guidelines: HD 60634: IEC : IEC : EN : Analysis of Reference Point Functions (Part of Table 2 in clause 10)

Geneva, 9 January Standardization Activities for Smart Grid Networks (Part of Table 3 in clause 10) Communi cations technolo gies Standardization activitiesStatus Note (related works) IMTITU-R IMT-2000 family ITU-R IMT-Advanced family ITU-T SG13 3GPP Already studied NIST SGIP PAP02 Power Line Communi cation (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 1901Already studied IEEE ISO/IECStudy in progress ISO/IEC (V2G CI)

Thank you!