🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BSI PD IEC/TR 61850-80-3:2015

BSI PD IEC/TR 61850-80-3:2015

$215.11

Communication networks and systems for power utility automation – Mapping to web protocols. Requirements and technical choices

Published By Publication Date Number of Pages
BSI 2015 94
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This part of IEC 61850, which is a technical report, describes the requirements and gives an overview of the technical solution for using Web Protocols as a new communication mapping (SCSM) for the IEC 61850 standard.

NOTE The notion of Web Protocols covers here the Web Services technologies, extended by other well deployed technologies based on standards used in the IT domain (IETF, ISO, W3C, OASIS, etc.). The advantage is that due to a lot of professional knowledge and practical experiences in the IT world the risk of non-interoperable solutions in the smart grid domain will decrease.

The structure of this part of IEC 61850 illustrates a two-step approach:

  • Collection of the use cases and requirements based upon emerging Smart Grid architectural considerations, taking into account the new extended scope of IEC 61850. Clause 6 proposes a synthesis of the global requirements, while the use cases of the various domains are described in Annex A. The considered domains are:

    • PV-inverters

    • Hydro and thermal generation

    • Wind power plants

    • Combined Heat and Power (CHP)

    • Smart customers

    • E-Mobility

    • Virtual Power Plants (VPP) and micro grids

    • Feeder automation

  • Evaluation and selection of technologies in order to build a consistent SCSM. Clause 7 presents the future SCSM 8-2, including an overview of the main selected technology: XMPP. The following goals have been particularly considered for the definition of this SCSM:

    • Identify a single profile supporting all the services required by the domains and defined today in ACSI.

    • Cover the full life cycle of a IEC 61850 system, in collaboration with the System Management work in WG10 (from configuration, through conformance testing, down to maintenance). For this purpose, this part of IEC 61850 may recommend some changes to other parts of the IEC 61850 series such as Parts 6 and 10, etc.

    • Deploy cyber-security to ensure a secure environment (in compliance with the IEC 62351 series).

    • Propose rules for cohabitation with other mappings such as IEC 61850-8-1 and IEC 61850-9-2, and possibly recommend communication profiles depending on specific application context (pole-top equipment, inside DER, connection of DER, etc.).

    • Only the A-Profile is addressed here. Nevertheless, support of TCP/IP and UDP/IP is required for the T-Profiles.

What is not included in the study:

  • Modification of objects specified in IEC 61850-7-3 and IEC 61850-7-4

  • Introduction of several competing web protocols profiles

The namespace of this document is: “(Tr)IEC 61850-80-3:2015”

PDF Catalog

PDF Pages PDF Title
4 CONTENTS
8 FOREWORD
10 INTRODUCTION
11 1 Scope
12 2 Normative references
13 3 Terms and definitions
14 4 Abbreviated terms
5 Main involved sub-systems and stakeholders
15 Figures
Figure 1 – Architecture overview
Tables
Table 1 – Main involved sub-systems and stakeholders
16 6 Requirements description
6.1 General
6.2 Scope of this clause
6.2.1 ACSI classes to be mapped
17 6.2.2 Network type
6.3 Requirements list
6.3.1 Transfer time
6.3.2 Throughput
6.3.3 Data integrity (error probability)
6.3.4 Reliability
6.3.5 Availability
18 6.3.6 Interoperability
6.3.7 Cyber security
19 6.3.8 Device size
6.3.9 Dynamic extension of the system
6.3.10 Sensitivity to cost of bandwidth
6.3.11 Availability of commercial and open source tools
Figure 2 – Device communicating with different trust levels
20 6.3.12 Intellectual property
6.3.13 Perenniality / Stability of the solution
6.3.14 Request for additional resources and engineering
6.3.15 Simplicity and easy implementation of the communication solution
6.3.16 Ability to become a SCSM / Difficulty in filling the gap
6.3.17 One single solution for all smart grid applications
6.3.18 Products’ time-to-market
21 6.3.19 Minimize standardization effort
7 SCSM technical description
7.1 Technology assessment and choice
22 7.2 XMPP overview
7.2.1 Principles
Figure 3 – Architecture main choices
23 7.2.2 Address scheme
7.2.3 Scalability and redundancy
Figure 4 – XMPP architecture overview
24 7.2.4 Server federation
7.2.5 Stanza example
Figure 5 – XMPP Federation
25 7.2.6 Presence monitoring
7.3 Communication stack overview
Figure 6 – Example of a XMPP telegram
26 Figure 7 – Simplified communication stack
Table 2 – ACSI services to be mapped
27 7.4 Definition of the XML payload
Table 3 – MMS objects and services in use within this SCSM
28 Figure 8 – XER encoding vs BER encoding
29 Figure 9 – ASN.1 abstract definition of MMS PDUs (extract)
Figure 10 – Example of XER payloads
30 7.5 Transport of XML payloads over XMPP
7.5.1 Mapping over XMPP overview
Figure 11 – ACSI XML Message schema for XER payload (extract)
31 7.5.2 Rules for mapping solicited services
Figure 12 – XMPP architecture for IEC 61850
33 7.5.3 Mapping of unsolicited services
7.5.4 Usage of presence monitoring
34 7.6 Cyber security
7.6.1 Security with XMPP
Figure 13 – XMPP using TLS and Simple Authentication and Security Layer (SASL)
35 7.6.2 Choice of technical solutions for security
7.7 Mapping synthesis
Figure 14 – End to end security over XMPP
36 Figure 15 – Synthesis of SCSM 8-2 structure
Table 4 – Mapping synthesis
37 7.8 Synergy with existing 8-1 mapping
Figure 16 – SCSM 8-1 and 8-2 synergy
38 Figure 17 – Control center with dual stack SCSM 8-1 / SCSM 8-2
39 Figure 18 – Gateway between SCSM 8-1 and SCSM 8-2
40 Annex A (informative) Use cases and requirements for each domain
A.1 Use cases for PV-inverters
A.1.1 Scope of this clause
A.1.2 Architecture overview
Figure A.1 – PV – Architecture overview for data connections to an industrial plant
41 A.1.3 Use cases
Figure A.2 – PV – Architecture overview for data connections to a residential plant
Table A.1 – Use case list
42 A.2 Use cases for hydro and thermal generation
A.2.1 Scope of this clause
A.2.2 Architecture overview
43 A.2.3 Use cases
Figure A.3 – Power plants – Typical power operator network architecture
Figure A.4 – Power plants – Relationship between the actors
44 Table A.2 – Power plants – Use case list
45 A.3 Use cases for wind power
A.3.1 Scope of this clause
A.3.2 Architecture overview
46 Figure A.5 – Examples of the variety of topologies required/supported for wind power
Figure A.6 – Example of use within the wind plant
47 Figure A.7 – Example of use between the wind plant and a control center
Figure A.8 – Diagram of data use hierarchy levels in condition monitoring
48 A.3.3 Use cases
Table A.3 – Wind – List of actors
49 Table A.4 – Wind – Use case list
51 A.4 Use cases for CHP
A.4.1 Scope of this clause
52 A.4.2 Architecture overview
Figure A.9 – Types of CHP plants
53 Figure A.10 – CHP – Example of a system architecture
54 Figure A.11 – Number of CHPs in Germany
55 Figure A.12 – CHP use cases and involved actors
56 A.4.3 Use cases
Table A.5 – CHP – Use case list
57 Figure A.13 – CHP – Graphical presentation of frequency control within the European power system
Figure A.14 – CHP – Frequency control time characteristic
61 A.4.4 References for CHP domain
A.5 Use cases of domain Smart Customer (DR)
A.5.1 Scope of this clause
Table A.6 – CHP – Other use cases not feasible with existing ACSI
62 A.5.2 Architecture overview
Figure A.15 – Smart customer – Main actors
63 Figure A.16 – Smart customer – Main elements ofthe smart customer domain (right column)
Figure A.17 – Smart customer – Logical model for customer premises communications
64 A.5.3 Use cases
Figure A.18 – Smart customer – Communication relationships
65 Table A.7 – Smart customer – Use case list
Table A.8 – Smart customer – Other use cases not feasible with existing ACSI
66 A.6 Use cases for E-Mobility
A.6.1 Scope of this clause
A.6.2 Architecture overview
A.6.3 Use cases
Figure A.19 – E-Mobility – Architecture overview
67 Table A.9 – E-Mobility – Use case list
72 A.7 Use cases for VPP and Microgrid
A.7.1 Scope of this clause
73 A.7.2 Architecture overview
Figure A.20 – Architectural picture of a microgrid
74 A.7.3 Use cases
Figure A.21 – Architectural picture of a VPP
Table A.10 – VPP/Microgrid – Use case list
75 Table A.11 – VPP/Microgrid – Other use cases not feasible with existing ACSI
76 A.8 Use cases for feeder automation
A.8.1 Scope of this clause
A.8.2 Architecture overview
77 Figure A.22 – FA – Distributed architecture of a feeder automation system
78 Figure A.23 – FA – Semi-centralized architecture of a feeder automation system
79 Figure A.24 – FA – Centralized architecture of a feeder automation system
80 A.8.3 Use cases
Table A.12 – FA – Use case list
81 A.9 Required services and performances
Table A.13 – FA – Other use cases not feasible with existing ACSI
Table A.14 – Synthesis – Usage of modeling classes
82 Table A.15 – Synthesis of transfer times
83 Table A.16 – Synthesis – New proposed functions
84 Annex B (informative) Examples of MMS XER payloads
B.1 General
B.2 GetLogicalNodeDirectory
90 B.3 Report

Related products

BSI PD IEC/TR 61850-80-3:2015
$215.11