{"id":276254,"date":"2024-10-19T18:35:35","date_gmt":"2024-10-19T18:35:35","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61850-7-12011a12020\/"},"modified":"2024-10-25T15:01:49","modified_gmt":"2024-10-25T15:01:49","slug":"bs-en-61850-7-12011a12020","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61850-7-12011a12020\/","title":{"rendered":"BS EN 61850-7-1:2011+A1:2020"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
4<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | European foreword Endorsement notice <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 4 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5 Overview of the IEC 61850 series concepts 5.1 Objective Figures Figure 1 \u2013 Relations between modelling and mapping parts of the IEC 61850 series <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.2 Topology and communication functions of substation automation systems <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5.3 The information models of substation automation systems Figure 2 \u2013 Sample substation automation topology <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | Figure 3 \u2013 Modelling approach (conceptual) <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 5.4 Applications modelled by logical nodes defined in IEC 61850-7-4 Tables Table 1 \u2013 LN groups <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Figure 4 \u2013 Logical node information categories Figure 5 \u2013 Build-up of devices (principle) <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.5 The semantic is attached to data Figure 6 \u2013 Position information depicted as a tree (conceptual) <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.6 The services to exchange information <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure 7 \u2013 Service excerpt <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 5.7 Services mapped to concrete communication protocols 5.8 The configuration of the automation system Figure 8 \u2013 Example of communication mapping <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 5.9 Summary <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 6 Modelling approach of the IEC 61850 series 6.1 Decomposition of application functions and information Figure 9 \u2013 Summary <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Figure 10 \u2013 Decomposition and composition process (conceptual) <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 6.2 Creating information models by stepwise composition Table 2 \u2013 Logical node class XCBR (conceptual) <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 11 \u2013 XCBR1 information depicted as a tree <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 6.3 Example of an IED composition <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 6.4 Information exchange models 6.4.1 General Figure 12 \u2013 Example of IED composition <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 6.4.2 Output model Figure 13 \u2013 Output and input model (principle) <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 14 \u2013 Output model (step 1) (conceptual) <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 15 \u2013 Output model (step 2) (conceptual) Figure 16 \u2013 GSE output model (conceptual) <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Figure 17 \u2013 Setting data (conceptual) <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 6.4.3 Input model Table 3 \u2013 Excerpt of integer status setting <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure 18 \u2013 Input model for analogue values (step 1) (conceptual) <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure 19 \u2013 Range and deadbanded value (conceptual) <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Figure 20 \u2013 Input model for analogue values (step 2) (conceptual) <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Figure 21 \u2013 Reporting and logging model (conceptual) <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Figure 22 \u2013 Data set members and reporting Table 4 \u2013 Comparison of the data access methods <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Figure 23 \u2013 Buffered report control block (conceptual) <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 24 \u2013 Buffer time <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Figure 25 \u2013 Data set members and inclusion-bitstring Figure 26 \u2013 Log control block (conceptual) <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Figure 27 \u2013 Peer-to-peer data value publishing model (conceptual) <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 6.4.4 Model for statistical and historical statistical data <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Figure 28 \u2013 Conceptual model of statistical and historical statistical data (1) <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 6.4.5 Model for system functions Figure 29 \u2013 Conceptual model of statistical and historical statistical data (2) <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 7 Application view 7.1 General Figure 30 \u2013 Concept of the service tracking model \u2013 Example: control service tracking <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure 31 \u2013 Real world devices <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 7.2 First modelling step \u2013 Logical nodes and data Figure 32 \u2013 Logical nodes and data (IEC 61850-7-2) <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure 33 \u2013 Simple example of modelling Figure 34 \u2013 Basic building blocks <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure 35 \u2013 Logical nodes and PICOM Figure 36 \u2013 Logical nodes connected (outside view in IEC 61850-7-x series) <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 7.3 Mode and behaviour of a logical node 7.4 Use of measurement ranges and alarms for supervision functions Figure 37 \u2013 Mode and behaviour data (IEC 61850-7-4) <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 7.5 Data used for limiting the access to control actions 7.6 Data used for blocking functions described by logical nodes 7.7 Data used for logical node inputs\/outputs blocking (operational blocking) 7.7.1 General Figure 38 \u2013 Data used for limiting the access to control actions (IEC 61850-7-4) <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 7.7.2 Blocking incoming commands 7.7.3 Blocking process outputs Figure 39 \u2013 Data used for logical node inputs\/outputs blocking (IEC 61850-7-4) <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 7.8 Data used for testing 7.8.1 General 7.8.2 Multicast signals used for simulation Figure 40 \u2013 Data used for receiving simulation signals <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 7.8.3 Input signals used for testing Figure 80 \u2013 GOOSE subscription supervision state machine Figure 81 \u2013 SV subscription supervision state machine <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Figure 41 \u2013 Example of input signals used for testing <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 7.8.4 Test mode 7.9 Logical node used for extended logging functions Figure 42 \u2013 Test mode example <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 8 Device view 8.1 General Figure 43 \u2013 Logical node used for extended logging functions (GLOG) <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 8.2 Second modelling step \u2013 logical device model 8.2.1 The logical device concept Figure 44 \u2013 Logical device building block <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 8.2.2 The device nameplate Figure 45 \u2013 Logical devices and LLN0\/LPHD <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 8.2.3 Gateways and proxies Figure 46 \u2013 The common data class DPL <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 47 \u2013 Logical devices in proxies or gateways <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure 79 \u2013 Logical devices in proxies or gateways (functional naming) <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 8.2.4 Logical devices for monitoring external device health 8.2.5 Logical devices management hierarchy Figure 48 \u2013 Logical devices for monitoring external device health <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Figure 49 \u2013 Logical devices management hierarchy <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 9 Communication view 9.1 General 9.2 The service models of the IEC 61850 series <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure 50 \u2013 ACSI communication methods Table 5 \u2013 ACSI models and services <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 9.3 The virtualisation <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 9.4 Basic information exchange mechanisms Figure 51 \u2013 Virtualisation Figure 52 \u2013 Virtualisation and usage <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Figure 53 \u2013 Information flow and modelling Figure 54 \u2013 Application of the GSE model <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 9.5 The client-server building blocks 9.5.1 Server Figure 55 \u2013 Server building blocks <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 9.5.2 Client-server roles Figure 56 \u2013 Interaction between application processand application layer (client\/server) Figure 57 \u2013 Example for a service Figure 58 \u2013 Client\/server and logical nodes <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 9.6 Logical nodes communicate with logical nodes Figure 59 \u2013 Client and server roles <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | 9.7 Interfaces inside and between devices Figure 60 \u2013 Logical nodes communicate with logical nodes <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | 10 Where physical devices, application models and communication meet Figure 61 \u2013 Interfaces inside and between devices <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | 11 Relationships between IEC 61850-7-2, IEC 61850-7-3 and IEC 61850-7-4 11.1 Refinements of class definitions Figure 62 \u2013 Component hierarchy of different views (excerpt) <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | 11.2 Example 1 \u2013 Logical node and data object class Figure 63 \u2013 Refinement of the DATA class <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table 6 \u2013 Logical node circuit breaker <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table 7 \u2013 Controllable double point (DPC) <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | 11.3 Example 2 \u2013 Relationship of IEC 61850-7-2, IEC 61850-7-3, and IEC 61850-7-4 Figure 64 \u2013 Instances of a Data object class (conceptual) <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Figure 65 \u2013 Relation between parts of the IEC 61850 series <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | 12 Formal specification method 12.1 Notation of ACSI classes 12.2 Class modelling 12.2.1 Overview Table 8 \u2013 ACSI class definition <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Figure 66 \u2013 Abstract data model example for IEC 61850-7-x <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 12.2.2 Common data class Table 9 \u2013 Single point status common data class (SPS) <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Table 10 \u2013 Quality components attribute definition <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table 16 \u2013 Attributes of DetailQual <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table 11\u2013 Functional constraints (excerpt) Table 12\u2013 Trigger option <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | 12.2.3 Logical node class Figure 67 \u2013 Relation of TrgOp and Reporting <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Table 13 \u2013 GenLogicalNodeClass definition <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 12.3 Service parameters tables <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 12.4 Referencing instances Figure 68 \u2013 Sequence diagram Figure 69 \u2013 References <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Figure 70 \u2013 Use of FCD and FCDA <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 13 Namespaces 13.1 General Figure 71 \u2013 Object names and object reference <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | 13.2 Namespaces defined in the IEC 61850-7-x series Figure 72 \u2013 Definition of names and semantics <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Figure 73 \u2013 Name space as class repository <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Figure 74 \u2013 All instances derived from classes in a single name space <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Figure 75 \u2013 Instances derived from multiple namespaces Figure 76 \u2013 Inherited namespaces <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | 13.3 Namespaces dependencies 13.3.1 General 13.3.2 Basic namespaces dependencies <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Figure 77 \u2013 Basic namespaces dependencies <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | 13.3.3 Other namespaces dependencies Figure 78 \u2013 Other namespaces dependencies <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | 13.4 Specification of namespaces 13.5 Attributes for references to namespaces 13.5.1 General <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | 13.5.2 Attribute for logical device namespace (ldNs) 13.5.3 Attribute for logical device basic namespace (LLN0.NamPlt.lnNs) Table 14 \u2013 Excerpt of logical node name plate common data class (LPL) Table 15 \u2013 Excerpt of the abstract common data class BasePrimitiveCDC <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | 13.5.4 Attribute for logical node namespace (lnNs) 13.5.5 Attribute for data namespace (dataNs) 13.5.6 Attribute for common data class namespace (cdcNs) 13.5.7 Attribute for naming a common data class name (cdcName) <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | 13.6 Deprecation of namespaces 14 Common rules for new version of classes and for extension of object classes 14.1 General 14.2 Basic rules 14.2.1 General <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Figure 79 \u2013 Basic extension rules diagram <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | 14.2.2 Use of optional information 14.2.3 General rules for enumerations types and enumeration-based data objects and attributes 14.3 Rules for extensions within private namespace 14.3.1 Rules for LN classes <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | 14.3.2 New LN classes 14.3.3 Rules for Common Data Classes <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | 14.3.4 Rules for enumeration types and enumeration-based data objects and attributes 14.4 Extensions made within product standard namespaces 14.5 Extensions made within transitional namespaces 14.6 Extensions made within basic and domain namespaces <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 14.7 Multiple instances of LN classes for dedicated and complex functions 14.7.1 Example for time overcurrent 14.7.2 Example for PDIS 14.7.3 Example for power transformer 14.7.4 Example for auxiliary network <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | 14.8 Specialisation of data by use of number extensions 14.9 Examples for new LNs 14.10 Example for new Data <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 15 Compatibility between different versions of the standard <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Annexes Annex A (informative) Overview of logical nodes and data A.1 Compatible logical node classes and data classes (IEC 61850-7-4) A.1.1 List of LN groups (IEC 61850-7-4) A.1.2 LN classes (IEC 61850-7-4) A.1.3 Data object classes (IEC 61850-7-4) A.2 Common data class specifications (IEC 61850-7-3) Table A.2 \u2013 List of common data classes (excerpt) <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Annex B (informative) Allocation of data to logical nodes Figure B.1 \u2013 Example for control and protection LNs combined in one physical device <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Figure B.2 \u2013 Merging unit and sampled value exchange (topology) Figure B.3 \u2013 Merging unit and sampled value exchange (data) <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Annex C (informative) Use of the substation configuration language (SCL) C.1 General C.2 SCL and options in logical nodes Figure C.1 \u2013 Application of SCL for LNs (conceptual) <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | C.3 SCL and options in data Figure C.2 \u2013 Application of SCL for data (conceptual) <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Annex D (xxx) <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Annex E (informative) Relation between logical nodes and PICOMs Figure E.1 \u2013 Exchanged data between subfunctions (logical nodes) Figure E.2 \u2013 Relationship between PICOMS and client\/server model <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Annex F (informative) Mapping the ACSI to real communication systems F.1 General Figure F.1 \u2013 ACSI mapping to an application layer <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Figure F.2 \u2013 ACSI mappings (conceptual) <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | F.1.1 Mapping example (IEC 61850-8-1) Figure F.3 \u2013 ACSI mapping to communication stacks\/profiles Figure F.4 \u2013 Mapping to MMS (conceptual) <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Figure F.5 \u2013 Mapping approach <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Figure F.6 \u2013 Mapping detail of mapping to a MMS named variable Figure F.7 \u2013 Example of MMS named variable (process values) <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | Figure F.8 \u2013 Use of MMS named variables and named variable list <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | Figure F.9 \u2013 MMS information report message <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | Figure F.10 \u2013 Mapping example <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Annex G (normative) LGOS\/LSVS engineering G.1 General <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | G.2 LGOS\/LSVS engineering by the ICT Figure G.1 \u2013 LGOS\/LSVS engineering <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | G.3 LGOS\/LSVS engineering by the SCT Figure G.2 \u2013 LGOS\/LSVS engineering by ICT <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Figure G.3 \u2013 LGOS\/LSVS engineering by the SCT <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Annex H (normative) GOOSE\/SMV Subscription Configuration H.1 General Figure H.1 \u2013 GOOSE\/SMV subscription engineering workflow <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | H.2 SCT supplied input binding workflow Figure H.2 \u2013 SCT supplied input binding <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | H.3 ICT supplied input binding (for later binding) Figure H.3 \u2013 ICT supplied input binding (for later binding) <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Annex I (informative) Specification of namespaces for Edition 3 I.1 Namespaces dependencies I.1.1 General I.1.2 Namespaces dependencies <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | I.2 Example 2 \u2013 Standardized data objects used in standardized LNs Figure I.1 \u2013 Private LN using standardized DOs (Edition 2) <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | I.3 Example 3 \u2013 Edition 2 device: standardized data object introduced in IEC61850-7-4:2007B Figure I.2 \u2013Standardized data objects used in standardized LNs <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | I.4 Example 4 \u2013 Edition 2 device: standardized LN introduced in IEC61850-7-4:2007B Figure I.3 \u2013 Edition 2 device: standardized data object introduced in IEC61850-7-4:2007B <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | I.5 Example 5 \u2013 Edition 1 device: Logical nodes in technical reports Figure I.4 \u2013 Edition 2 device: standardized LN introduced in IEC61850-7-4:2007B <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Figure I.5 \u2013 Edition 1 device: Logical nodes in technical reports <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | I.6 Example 6- Edition 2.1 device: Logical nodes in technical reports defining new CDCs Figure I.6 \u2013 Edition 2 device: Logical nodes in technical reports <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | I.7 Example 7- Edition 2.1 device: devices for product family standards Figure I.7 \u2013 Edition 2.1 device: Logical nodes in technical reports defining new CDCs <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | I.8 Example 8 \u2013 Standardized logical nodes introduced by other domain applications Figure I.8 \u2013 Edition 2.1 device: standardized LNs extended by other domains <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Figure I.9 \u2013 Edition 2 device: standardized LN introduced in IEC 61850-7-420:2009 <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | I.9 Example 9 \u2013 Standardized logical nodes introduced by other domain applications than moved to IEC 61850-7-4 Figure I.10 \u2013 Edition 2.1 device: standardized LN introduced in IEC 61850-7-420:2015 <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | Figure I.11 \u2013 Edition 2 device: standardized LN moved from introduced in IEC 61850-7-420:2009 to IEC 61850-7-4:2007 <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Figure I.12 \u2013 Edition 2.1 device: standardized LN moved from introduced in IEC 61850-7-420:2009 to IEC 61850-7-4:2007 <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | Annex J (normative) Use case scenarios examples for clarifying the common rules of Clause 14 J.1 General J.2 Example 1 \u2013 Private LN using standardized DOs Figure J.1 \u2013 Private LN using standardized DOs (Edition 2) <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | J.3 Example 2 \u2013 Standardized data objects used in standardized LNs J.4 Example 3 \u2013 Edition 2 device: standardized data object introduced in IEC61850-7-4:2007B Figure J.2 \u2013Standardized data objects used in standardized LNs <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | J.5 Example 4 \u2013 Edition 2 device: standardized LN introduced in IEC61850-7-4:2007B Figure J.3 \u2013 Edition 2 device: standardized data object introduced in IEC61850-7-4:2007B <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | J.6 Example 5 \u2013 Edition 1 or 2 device: Logical nodes in technical reports Figure J.4 \u2013 Edition 2 device: standardized LN introduced in IEC61850-7-4:2007B <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Figure J.5 \u2013 Edition 1 device: Logical nodes in technical reports <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | J.7 Example 6- Edition 2.1 device: Logical nodes in technical reports defining new CDCs Figure J.6 \u2013 Edition 2 device: Logical nodes in technical reports <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | J.8 Example 7- Edition 2.1 device: devices for product family standards Figure J.7 \u2013 Edition 2.1 device: Logical nodes in technical reports defining new CDCs <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | J.9 Example 8 \u2013 Standardized logical nodes introduced by other domain applications Figure J.8 \u2013 Edition 2.1 device: standardized LNs extended by other domains <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Figure J.9 \u2013 Edition 2 device: standardized LN introduced in IEC 61850-7-420:2009 <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | J.10 Example 9 \u2013 Standardized logical nodes introduced by other domain applications than moved to IEC 61850-7-4 Figure J.10 \u2013 Edition 2.1 device: standardized LN introduced in IEC 61850-7-420:2015 <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | Figure J.11 \u2013 Edition 2 device: standardized LN moved from introduced in IEC 61850-7-420:2009 to IEC 61850-7-4:2007 <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Figure J.12 \u2013 Edition 2.1 device: standardized LN moved from introduced in IEC 61850-7-420:2009 to IEC 61850-7-4:2007 <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Annex K (normative) General requirements and recommendations regarding compatibility issues between different versions of IEC 61850 K.1 Overview K.1.1 General K.1.2 Definitions (to go to part 2): <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | K.1.3 Introduction to compatibility discussion K.1.4 Assumptions Table K.1 \u2013 Information users and information providers <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | K.1.5 Generic rules <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | K.1.6 Overview on use cases Table K.2 \u2013 Data model use cases <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | Table K.3 \u2013 Services use cases <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | Table K.4 \u2013 Data Forbidden cases <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | K.2 Use cases related to the data model K.2.1 Use case 1: Add new type K.2.2 Use case 2: Add new FC Table K.5 \u2013 Add new basic type <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | K.2.3 Use case 3: Extend CDC with elements of existing types and FCs Table K.6 \u2013 Extend CDC with DA of new FC Table K.7 \u2013 Add new DA using existing type and FCs <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | K.2.4 Use case 4: Add a new DataObject (DO) based on new CDCs Table K.8 \u2013 Add a new DO based on new CDC using existing types and FCs <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | K.2.5 Use case 5: Add a new DO based on existing CDCs K.2.6 Use case 6: Rename a DO K.2.7 Use case 7: Rename a DA, subDO or subDA Table K.9 \u2013 Adding a new DO based on existing CDC Table K.10 \u2013 Renaming a DO <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | K.2.8 Use case 8: Deprecation of a FC Table K.11 \u2013 Renaming a DA, subDO or subDA <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | K.2.9 Use case 9: Deprecation of a DA K.2.10 Use case 10: Removal of a DA Table K.12 \u2013 Deprecation of a FC Table K.13 \u2013 Deprecation of a DA <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | K.2.11 Use case 11: Deprecation of a DO K.2.12 Use case 12: Use a weaker presence condition Table K.14 \u2013 Removal of a DA Table K.15 \u2013 Deprecation of a DO <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | K.2.13 Use case 13: Use a stronger presence condition K.2.14 Use case 14: Extend Enumeration List with an enumerated value Table K.16 \u2013 Use of a weaker presence condition Table K.17 \u2013 Use of a stronger presence condition <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | K.2.15 Use case 15: Modification of an Enumerated value Table K.18 \u2013 Extend an enumeration with an enumerated value Table K.19 \u2013 Modification of an enumerated value from an enumeration list <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | K.2.16 Use case 16: Deprecation of an Enumerated value K.2.17 Use case 17: Extension of a PACKED LIST K.2.18 Use case 18: Extend Name Length Table K.20 \u2013 Deprecate an enumerated value from an enumeration list Table K.21 \u2013 Extension of a PACKED LIST <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | K.3 Use cases related to the services K.3.1 Use case 30: Add new type Table K.22 \u2013 Extend size of names \/ references Table K.23 \u2013 Add new basic type <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | K.3.2 Use case 31: Using new control block class K.3.3 Use case 32: Using new services Table K.24 \u2013 Adding new Control Blocks Table K.25 \u2013 Adding new services <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | K.3.4 Use case 33: Extending control block class with an attribute of existing type K.3.5 Use case 34: Rename a service parameter not associated with a control block attribute K.3.6 Use case 35: Removing \/ Deprecating Control Block Classes Table K.26 \u2013 Add new attributes in control block Table K.27 \u2013 Deprecating control block class <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | K.3.7 Use case 36: Using a stronger presence condition Table K.28 \u2013 Using a stronger presence condition <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – Basic communication structure. Principles and models<\/b><\/p>\n |