| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 42151.71-2024 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Communication networks and systems for power utility automation - Part 7-1: Basic communication structure - Principles and models
| Valid |
GB/T 42151.71-2024
|
PDF similar to GB/T 42151.71-2024
Basic data | Standard ID | GB/T 42151.71-2024 (GB/T42151.71-2024) | | Description (Translated English) | Communication networks and systems for power utility automation - Part 7-1: Basic communication structure - Principles and models | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | F21 | | Classification of International Standard | 29.240.10 | | Word Count Estimation | 178,184 | | Date of Issue | 2024-12-31 | | Date of Implementation | 2025-07-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 42151.71-2024: Communication networks and systems for power utility automation - Part 7-1: Basic communication structure - Principles and models
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
ICS 29.240.10
CCSF21
National Standard of the People's Republic of China
Power automation communication network and system
Part 7-1.Basic communication structure principles and models
(IEC 61850-7-1.2020, IDT)
Released on 2024-12-31
2025-07-01 Implementation
State Administration for Market Regulation
The National Standardization Administration issued
Table of Contents
Preface IX
Introduction Ⅹ
1 Scope 1
2 Normative references 1
3 Terms and definitions 3
4 Abbreviations 3
5 Overview of the concepts of the IEC 61850 series 4
5.1 Purpose 4
5.2 Substation Automation System Topology and Communication Functions 5
5.3 Substation Automation System Information Model 6
5.4 Application of logical node modeling defined in IEC 61850-7-4 8
5.5 Semantics of data appending 10
5.6 Information exchange services 12
5.7 Mapping services to specific communication protocols 14
5.8 Automation system configuration 14
5.9 Summary 15
6 Modeling methods of IEC 61850 series 15
6.1 Decomposition of application functions and information 15
6.2 Creating an Information Model Using a Step-by-Step Synthesis Approach 17
6.3 Example of IED synthesis 19
6.4 Information Exchange Model 20
7 Application Perspective 38
7.1 Overview 38
7.2 Modeling the first step - logical nodes and data 39
7.3 Logical Node Mode and Behavior 42
7.4 Measurement range of monitoring functions and use of alarms 43
7.5 Data used to control operating permissions 43
7.6 Data for blocking functions described by logical nodes 43
7.7 Data for logical node input/output blocking (operation blocking) 44
7.8 Data used for testing 45
7.9 Logical nodes for extended logging functions 48
8 Device Perspective49
8.1 Overview 49
8.2 Modeling Step 2---Logical Device Model 49
9 Communication perspective 56
9.1 Overview 56
9.2 Service Model of IEC 61850 Series 56
9.3 Virtualization 58
9.4 Basic information exchange mechanism 59
9.5 Client-Server Components 60
9.6 Logical Node and Logical Node Communication 63
9.7 Interfaces within and between devices 63
10 Physical Devices, Application Models, and Communications Intersection 64
11 Relationship between IEC 61850-7-2, IEC 61850-7-3 and IEC 61850-7-4 65
11.1 Class Definition Refinement 65
11.2 Example 1 - Logical Node and Data Object Classes 66
11.3 Example 2 - Relationship between IEC 61850-7-2, IEC 61850-7-3 and IEC 61850-7-4 70
12 Formal Specification Methods 71
12.1 Notation of ACSI Classes 71
12.2 Class Modeling 72
12.3 Service Parameter Table 79
12.4 Reference Example 80
13 Namespace82
13.1 Overview 82
13.2 Namespaces defined in the IEC 61850-7-X series 83
13.3 Namespace Dependencies 86
13.4 Namespace Specification 90
13.5 Referencing Namespaced Attributes 90
13.6 Namespace Deprecation 92
14 New Versions of Classes and Common Rules for Object Class Extensions 93
14.1 Overview 93
14.2 Basic Rules 93
14.3 Private Namespace Extension Rules 96
14.4 Extensions within the product standard namespace 97
14.5 Extension of the Transitional Namespace 97
14.6 Extensions to Base and Domain Namespaces 97
14.7 Multiple instances of logical nodes for specialized functions and complex functions 98
14.8 Specialization using digital extension data 99
14.9 Example of a new logical node 99
14.10 Example 100 of New Data
15 Compatibility between different versions of the standard 100
Appendix A (Informative) Logical Nodes and Data Overview 101
A.1 Compatible logical node classes and data classes (IEC 61850-7-4) 101
A.2 Public Data Class Specification (IEC 61850-7-3) 101
Appendix B (Informative) Allocation of data to each logical node 104
Appendix C (Informative) Application of Substation Configuration Language (SCL) 106
C.1 Overview 106
C.2 Option 106 in SCL and logical nodes
C.3 Option 106 in SCL and data
Appendix E (Informative) Relationship between Logical Nodes and PICOM 109
Appendix F (Informative) Mapping ACSI to Actual Communication Systems 110
F.1 Overview 110
F.2 Example of IEC 61850-8-1 mapping 112
Appendix G (Normative) Engineering of LGOS/LSVS 117
G.1 General 117
G.2 LGOS/LSVS Engineering Using IED Configuration Tool (ICT) 117
G.3 LGOS/LSVS Engineering Using System Configuration Tool (SCT) 118
Appendix H (Normative) GOOSE/SMV Subscription Configuration 120
H.1 Overview 120
H.2 Input binding workflow provided by SCT 121
H.3 Input binding provided by ICT (for late binding) 121
Appendix I (Informative) Version 3 Namespace Specification 123
I.1 Example 1---Namespace Dependency 123
I.2 Example 2 - Standardized data objects used in a standardized logical node 124
I.3 Example 3 - Edition 2 equipment. Standardized data objects introduced in IEC 61850-7-4.2007B 125
I.4 Example 4 - Edition 2 equipment. Standardized logical node 126 introduced in IEC 61850-7-4.2007B
I.5 Example 5 - Version 1 equipment. Logical node 127 in technical report
I.6 Example 6 - Version 2.1 device. logical node 129 of the new CDC defined in the technical report
I.7 Example 7 - Version 2.1 Device. Device for Product Family Standard 130
I.8 Example 8 - Standardized logical nodes introduced by other domain applications 131
I.9 Example 9 - Standardized logical node 133 introduced by other domain applications and moved to IEC 61850-7-4
Appendix J (Normative) Examples of use case scenarios for illustrating the common rules of Chapter 14 136
J.1 Overview 136
J.2 Example 1 - Private LN 136 using standardized DO
J.3 Example 2 - Standardized DO 136 used in standardized LN
J.4 Example 3 - Second edition equipment. Standardized data objects introduced in IEC 61850-7-4.2007B 137
J.5 Example 4 - Edition 2 equipment. Standardized LN 138 introduced in IEC 61850-7-4.2007B
J.6 Example 5 - Version 1 or 2 equipment. Logical node 139 in technical report
J.7 Example 6 - Version 2.1 Device. Defining Logical Node 141 in the Technical Report for a New CDC
J.8 Example 7 - Version 2.1 Device. Product Family Standard Device 142
J.9 Example 8 - Standardized logical nodes introduced by other domain applications 143
J.10 Example 9 - Standardized logical nodes introduced from other domain applications and then transferred to IEC 61850-7-4 145
Appendix K (Normative) General requirements and recommendations on compatibility between different versions of IEC 61850 148
K.1 Overview 148
K.2 Use cases related to data models 154
K.3 Use cases related to services 165
References 168
Figure 1 Relationship between modeling and mapping parts of the IEC 61850 series 4
Figure 2 Example of substation automation topology 6
Figure 3 Conceptual modeling approach 7
Figure 4 Logical node information classification 9
Figure 5 Equipment construction (principle) 10
Figure 6.Location information represented in tree form (conceptual) 11
Figure 7 Service Excerpt 13
Figure 8 Example of communication mapping 14
Figure 9 Summary 15
Figure 10 Decomposition and combination process (conceptual) 16
Figure 11 XCBR information described in tree form 18
Figure 12 Example of IED configuration 19
Figure 13 Output and input model (principle) 20
Figure 14 Output Model (Step 1) (Conceptual) 22
Figure 15 Output Model (Step 2) (Conceptual) 22
Figure 16 GSE output model (conceptual) 23
Figure 17 Fixed value data (conceptual) 24
Figure 18 Simulation value input model (step 1) (conceptual) 25
Figure 19 Range and dead zone value (conceptual) 26
Figure 20 Simulation value input model (step 2) (conceptual) 27
Figure 21 Report and log model (conceptual) 28
Figure 22 Dataset members and reports 29
Figure 23 Cache report control block (conceptual) 30
Figure 24 Cache time 31
Figure 25 Data set members and inclusion-bitstring (inclusion bit string) 32
Figure 26 Log Control Block (Conceptual) 33
Figure 27 Peer-to-peer data value publishing model (conceptual) 34
Figure 28 Statistics and historical statistical data conceptual model (1) 35
Figure 29 Statistics and historical statistical data conceptual model (2) 36
Figure 30 Concept of service tracking model --- Example. Control service tracking 38
Figure 31 Real-world devices 39
Figure 32 Logical nodes and data (IEC 61850-7-2) 40
Figure 33 A simple example of modeling 41
Figure 34 Basic components 41
Figure 35 Logical nodes and PICOM 42
Figure 36 Logical node connection (conforming to the external perspective of IEC 61850-7-X series) 42
Figure 37 Mode and behavior data (IEC 61850-7-4) 42
Figure 38 Data with restricted access to control operations (IEC 61850-7-4) 43
Figure 39 Data for logical node input/output blocking (IEC 61850-7-4) 44
Figure 40 Data 45 for receiving simulation signals
Figure 80 GOOSE subscription supervision state machine 46
Figure 81 SV subscription supervision state machine 46
Figure 41 Input signal for testing 47
Figure 42 Test mode example 47
Figure 43 Logical node (GLOG) used to expand the logging function 48
Figure 44 Logical device components 49
Figure 45 Logical devices and LLN0/LPHD 50
Figure 46 Public Data Class DPL 51
Figure 47 Logical devices in proxy/gateway 52
Figure 79 Logical devices in a proxy or gateway (functional naming) 53
Figure 48 Logical device 54 that monitors the health status of external devices
Figure 49 Logical device management hierarchy 55
Figure 50 ACSI communication method 56
Figure 51 Virtualization 58
Figure 52 Virtualization and usage 59
Figure 53 Information Flow and Modeling 59
Figure 54 Application of GSE model 60
Figure 55 Basic components of the server 61
Figure 56 Interaction between application process and application layer (client/server) 61
Figure 57 Example of service 62
Figure 58 Client/Server and Logical Node 62
Figure 59 Client and server roles 62
Figure 60 Logical node and logical node communication 63
Figure 61 Interfaces within and between devices 64
Figure 62 Component layering from different perspectives (summary) 65
Figure 63 Data Class Refinement 66
Figure 64 Data object class instance (conceptual) 70
Figure 65 Relationship between the various parts of IEC 61850 (IEC 61850-7-2, IEC 61850-7-3 and IEC 61850-7-4) 71
Figure 66 Example of an abstract data model for IEC 61850-7-×73
Figure 67 Relationship between TrgOp and report 78
Figure 68 Sequence diagram 80
Figure 69 Reference 80
Figure 70 Use of FCD and FCDA 81
Figure 71 Object name and object reference 82
Figure 72 Definition of name and semantics 83
Figure 73 Namespace as a class archive 84
Figure 74 All instances are taken from classes in a single namespace 84
Figure 75 Examples taken from multiple namespaces 85
Figure 76 Inherited namespace 86
Figure 77 Basic namespace dependencies 87
Figure 78 Other namespace dependencies 89
Figure 79 Basic expansion rules Figure 94
Figure B.1 Example of control and relay protection logical nodes forming one physical device 104
Figure B.2 Merging unit and sample value exchange (topology) 105
Figure B.3 Merging Units and Sample Value Exchange (Data) 105
Figure C.1 SCL application of logical nodes (conceptual) 106
Figure C.2 SCL application of data (conceptual) 107
Figure E.1 Data exchange between sub-functions (logical nodes) 109
Figure E.2 Relationship between PICOM and the client/server model 109
Figure F.1 ACSI mapping to application layer 110
Figure F.2 ACSI mapping (conceptual) 111
Figure F.3 ACSI 112 mapped to communication stack/protocol suite
Figure F.4 Mapping to MMS (conceptual) 112
Figure F.5 Mapping method 113
Figure F.6 Mapping to MMS named variable detailed description 114
Figure F.7 Example of MMS named variable (process value) 114
Figure F.8 Using MMS named variables and named variable tables 115
Figure F.9 MMS information report message 115
Figure F.10 Mapping example 116
Figure G.1 LGOS/LSVS Engineering 117
Figure G.2 LGOS/LSVS Engineering Implementation by IED Configuration Tool (ICT) 118
Figure G.3 LGOS/LSVS engineering implemented by system configuration tools 119
Figure H.1 GOOSE/SMV subscription engineering workflow 120
Figure H.2 Input bindings provided by SCT 121
Figure H.3 Input binding provided by ICT (for late binding) 122
Figure I.1 Private LN using standardized DO (version 2) 124
Figure I.2 Standardized data objects used in standardized logical nodes 125
Figure I.3 Second edition equipment. Standardized data objects introduced in IEC 61850-7-4.2007B 126
Figure I.4 Second edition equipment. Standardized logical nodes introduced in IEC 61850-7-4.2007B 127
Figure I.5 Version 1 equipment. Logical nodes in technical report 128
Figure I.6 Version 2 equipment. Logical nodes in technical report 129
Figure I.7 Version 2.1 Device. Logical Nodes in Technical Report Define New CDC 130
Figure I.8 Version 2.1 Device. Standardized LNs for other domain extensions 131
Figure I.9 2nd edition equipment. Standardized LN 132 introduced in IEC 61850-7-420.2009
Figure I.10 Edition 2.1 equipment. Standardized LN 133 introduced in IEC 61850-7-420.2015
Figure I.11 2nd edition equipment. IEC 61850-7-420.2009 introduces the standardized LN 134 moved to IEC 61850-7-4.2007
Figure I.12 Edition 2.1 equipment. IEC 61850-7-420.2009 introduces LN 135 moved to IEC 61850-7-4.2007
Figure J.1 Private LN using standardized DO (version 2) 136
Figure J.2 Standardized DO 137 used in standardized LN
Figure J.3 Standardized data objects introduced in Edition 2 equipment. IEC 61850-7-4.2007B 138
Figure J.4 2nd edition equipment. Standardized LN 139 introduced in IEC 61850-7-4.2007B
Figure J.5 Version 1 Equipment. Logical Node 140 in Technical Report
Figure J.6 Version 2 equipment. Logical nodes in technical report 141
Figure J.7 Logical nodes in the technical report for version 2.1 equipment. defining new CDCs 142
Figure J.8 Version 2.1 equipment. Standardized LN 143 extended by other fields
Figure J.9 2nd edition equipment. Standardized LN 144 introduced in IEC 61850-7-420.2009
Figure J.10 Edition 2.1 equipment. Standardized LN 145 introduced in IEC 61850-7-420.2015
Figure J.11 2nd edition equipment. Standardized LN 146 transferred from IEC 61850-7-420.2009 to IEC 61850-7-4.2007
Figure J.12 Edition 2.1 equipment. Standardized LN 147 introduced and transferred from IEC 61850-7-420.2009 to IEC 61850-7-4.2007
Table 1 Logical node group 8
Table 2 XCBR logical node class (conceptual) 17
Table 3 Excerpt of integer status settings 24
Table 4 Comparison of data access methods 29
Table 5 ACSI Model and Services 57
Table 6 Circuit breaker logical node 67
Table 7 Dual Point Controllable (DPC) 68
Table 8 ACSI Class Definition 72
Table 9 Single Point State Public Data Class (SPS) 74
Table 10 Quality component attribute definition 74
Table 16 DetailQual Detailed quality attributes 75
Table 11 Functional constraints (summary) 77
Table 12 Trigger options 77
Table 13 General logical node class definition 78
Table 14 Summary of Logical Node Nameplate Public Data Class (LPL) 91
Table 15 Abstract public data class (BasePrimitiveCDC) summary 91
Table A.2 List of public data classes (excerpt) 101
Table K.1 Information users and information providers 148
Table K.2 Data model use case 151
Table K.3 Service use case 153
Table K.4 Use cases where data is prohibited 153
Table K.5 Adding new basic types 154
Table K.6 DA extension CDC using new FC 155
Table K.7 Adding a new DA using an existing type and FC 156
Table K.8 Adding a new DO based on a new CDC using existing types and FC 157
Table K.9 Adding new DO 157 based on existing CDC
Table K.10 Rename DO 158
Table K.11 Renaming DA, subDO or subDA 158
Table K.12 Deprecation of FC 159
Table K.13 Deprecation of DA 160
Table K.14 Delete DA 160
Table K.15 Deprecation of DO 161
Table K.16 Using weaker existence conditions 161
Table K.17 Using a stronger existence condition 161
Table K.18 Extending enumeration with enumeration value 162
Table K.19 Modify the enumeration value in the enumeration list 163
Table K.20 Deprecated enumeration values in enumeration list 163
Table K.21 Extension of PACKEDLIST 164
Table K.22 Size of extension name/reference 164
Table K.23 Adding new basic types 165
Table K.24 Adding new control block 165
Table K.25 Adding new services 165
Table K.26 Adding new attributes to the control block 166
Table K.27 Deprecated control block class 167
Table K.28 Using a stronger existence condition 167
Foreword
This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents"
Drafting.
This document is part 71 of GB/T 42151 "Electric power automation communication networks and systems". GB/T 42151 has been published as follows
part.
--- Part 3.General requirements;
--- Part 4.System and project management;
--- Part 5.Communication requirements for functional and device models;
--- Part 6.Communication configuration description language for power automation systems related to intelligent electronic devices;
--- Part 7-1.Basic communication structure principles and models;
--- Part 7-2.Basic information and communication structure Abstract Communication Service Interface (ACSI);
--- Part 7-7.IEC 61850 related data model machine processable format for tools;
--- Part 8-1.Specific Communication Service Mapping (SCSM) Mapping to MMS (ISO 9506-1 and ISO 9506-2) and
ISO /IEC 8802-3.
This document is equivalent to IEC 61850-7-1.2020 "Electric power automation communication networks and systems Part 7-1.Basic communication architecture"
Principles and Models
Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents.
This document was proposed by the China Electricity Council.
This document is under the jurisdiction of the National Technical Committee for Standardization of Power System Management and Information Exchange (SAC/TC82).
This document was drafted by. China Electric Power Research Institute Co., Ltd., State Grid Electric Power Research Institute Co., Ltd., State Grid Corporation of China
National Electric Power Dispatching and Control Center, China Southern Power Grid Electric Power Dispatching and Control Center, Tianjin Jingui Huihai Technology Development Co., Ltd., State Grid
Zhejiang Electric Power Co., Ltd., Beijing Sifang Relay Protection Automation Co., Ltd., Xuji Group Co., Ltd., State Grid Jiangsu Electric Power Co., Ltd.
China Electric Power Corporation, State Grid Nanjing Automation Co., Ltd., State Grid Tianjin Electric Power Company, Jicheng Electronics Co., Ltd., Jiangsu Hongyuan Electric Co., Ltd.
The company, State Grid Sichuan Electric Power Company Electric Power Research Institute, State Grid Jibei Electric Power Co., Ltd., Dongfang Electronics Co., Ltd., Changyuan Shenzhen
Ruijibao Automation Co., Ltd., State Grid Shanxi Electric Power Company, Nanjing Nanrui Jibao Electric Co., Ltd., Shanghai Siyuan Hongrui Automation Co., Ltd.
company.
The main drafters of this document are. Li Jinsong, Li Wenzhuo, Shen Jian, Chang Naichao, Li Jin, Zhou Bin, Tang Yongjian, Du Qiwei, Ren Yanming, Liao Zeyou,
Peng Zhiqiang, Dou Renhui, Ren Zhenxing, Zheng Xiang, Yao Nan, Zhang Haiyan, Chen Jian, Zhu Xiaolei, Wang Yongfu, Yang Song, Zheng Yongkang, Wang Huapeng, Han Kai, Sheng Fu,
Liu Yongxin, Wei Jieru, Wang Peiqi, Huang Xinping, Li Qiang, Wei Lifeng, Ge Liqing, Ge Huan, and Yang Bin.
Introduction
GB/T 42151 "Electric Power Automation Communication Network and System" aims to provide interoperability for all devices in the electric power automation system.
It consists of the following parts.
--- Part 1.Introduction. The purpose is to introduce the overview of this document.
--- Part 2.Terminology. The purpose is to list the terms and definitions used in this document.
--- Part 3.General requirements. The purpose is to introduce the overall requirements of communication networks, with an emphasis on quality requirements.
--- Part 4.System and project management. The purpose is to describe the requirements for system and project management processes and the requirements for engineering and testing
Dedicated support tools required.
--- Part 5.Communication requirements for functions and device models. The purpose is to specify the communication requirements for various functions of the power automation system.
--- Part 6.Communication configuration description language for power automation systems related to intelligent electronic devices. The purpose is to
exchange of intelligent electronic device capability descriptions in a way that allows for the exchange of power automation system capabilities between tools provided by different manufacturers
describe.
--- Part 7.Basic communication structure of power automation system. The purpose is to define a hierarchical class model and the services provided by these classes.
services to enable communication between devices.
--- Part 8.Specific communication service mapping SCSM. The purpose is to provide substation control layer and bay layer and station control layer and
Communication mapping between bay layers.
--- Part 9.Specific Communication Service Mapping SCSM. The purpose is to provide substation bay layer and process layer and bay layer and
Communication mapping between process layers.
--- Part 10.Conformance testing. The purpose is to specify the standard technology for implementing conformance testing and to use when proposing performance parameters
specific measurement techniques.
This document outlines the communication and interaction between power automation systems (such as protection devices, circuit breakers, transformers, substation masters, etc.)
Architecture.
This document is part of a set of specifications that detail a hierarchical communication architecture for power automation. This architecture was chosen to provide a class (representing
Layered Information Model) and abstract definition of services, making the specification independent of specific protocol stacks, implementations, and operating systems.
The purpose of IEC 61850 is to achieve interoperability between intelligent electronic devices (IEDs) provided by different suppliers, more precisely
In other words, it is the interoperability of functions performed by various power automation systems, which are often located in equipment (physical and electronic) provided by different suppliers.
Interoperable functions can represent the interface between a process (e.g. a circuit breaker) or a substation automation function (e.g. a protection function).
This document describes the concepts and methods used in IEC 61850 with simple examples of functions.
This document describes the relationship between the other parts of IEC 61850 and finally defines how interoperability is achieved.
Note. Interchangeability means the ability to replace equipment from the same supplier or different suppliers, using the same communication interface and providing at least the same functionality, without
Capabilities that will have an impact on the rest of the system. If the difference in functionality is acceptable, the replacement may require some changes in the system.
Interoperability implies standardization of functions and even equipment, both of which are beyond the scope of IEC 61850.Interchangeability complies with the interoperability provisions of IEC 61850.
This document is applicable to all relevant personnel engaged in communication standardization and system standardization in the power automation industry.
A summary and introduction to IEC 61850-7-4, IEC 61850-7-3, IEC 61850-7-2, IEC 61850-6 and IEC 61850-8-1.
Power automation communication network and system
Part 7-1.Basic communication structure principles and models
1 Scope
This document describes the modeling approach, communication principles and information models used in the various parts of IEC 61850-7-×.
From a holistic perspective, this paper helps readers understand the following basic modeling concepts and description methods.
---Substation-specific information model for power automation system;
---Equipment functions for power automation;
---Communication system that provides interoperability for power equipment.
This document explains and provides information on the relationship between IEC 61850-7-4, IEC 61850-7-3, IEC 61850-7-2 and IEC 61850-5.
Detailed requirements and explanation of how the abstract services and models of the IEC 61850-7-X series are mapped to the specific communication services defined in IEC 61850-8-1
protocol.
The concepts and models of this document can also be used to describe information models and functions in other applications as follows.
---Hydropower plant;
---Information exchange between substations;
---Information exchange for distribution automation;
---Information exchange between substation and control center;
---Metric information exchange;
--- Status monitoring and diagnosis;
--- Information exchange with engineering systems for equipment configuration.
Note 1.The examples and excerpts in this document are taken from other parts of the IEC 61850 series. These excerpts are used to explain the concepts and methods.
The examples and excerpts are informative.
NOTE 2 Examples in this document use class names defined in IEC 61850-7-4, IEC 61850-7-3 (e.g. logical node class XCBR) and in IEC 61850-
Service name defined in IEC 61850-7-2.Canonical name defined only in IEC 61850-7-4, IEC 61850-7-3 and IEC 61850-7-2.
Note 3.This document is not a comprehensive guidance material. It is recommended to read this document first and then read it in conjunction with IEC 61850-7-4, IEC 61850-7-3 and IEC 61850-7-2.
Read, and it is recommended to also read, IEC 61850-1 and IEC 61850-5.
NOTE 4.This document does not discuss specific implementations.
2 Normative references
The contents of the following documents constitute the essential clauses of this document through normative references in this document.
For referenced documents without a date, only the version corresponding to that date applies to this document; for referenced documents without a date, the latest version (including all amendments) applies to
This document.
Note. GB/T 16720.1-2005 Industrial Automation System Manufacturing Message Specification Part 1.Service Definition (ISO 9506-1.2003, IDT)
Note. GB/T 16720.2-2005 Industrial Automation System Manufacturing Message Specification Part 2.Protocol Specification (ISO 9506-2.2003, IDT)
|