{"id":254771,"date":"2024-10-19T16:50:11","date_gmt":"2024-10-19T16:50:11","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61850-7-12011\/"},"modified":"2024-10-25T12:16:07","modified_gmt":"2024-10-25T12:16:07","slug":"bs-en-61850-7-12011","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61850-7-12011\/","title":{"rendered":"BS EN 61850-7-1:2011"},"content":{"rendered":"
IEC 61850-7-1:2011 introduces the modelling methods, communication principles, and information models that are used in the various parts of the IEC 61850-7 series. The purpose is to provide – from a conceptual point of view – assistance to understand the basic modelling concepts and description methods for: – substation-specific information models for power utility automation systems, – device functions used for power utility automation purposes, and – communication systems to provide interoperability within power utility facilities. Compared to the first edition, this second edition introduces: – the model for statistical and historical statistical data, – the concepts of proxies, gateways, LD hierarchy and LN inputs, – the model for time synchronisation, – the concepts behind different testing facilities, – the extended logging function. It also clarifies certain items.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | English \n CONTENTS <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 2 Normative references <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 3 Terms and definitions 4 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5 Overview of the IEC\u00a061850 series concepts 5.1 Objective Figures \n Figure 1 \u2013 Relations between modelling and mapping parts of the IEC\u00a061850 series <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 5.2 Topology and communication functions of substation automation systems 5.3 The information models of substation automation systems Figure 2 \u2013 Sample substation automation topology <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Figure 3 \u2013 Modelling approach (conceptual) <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.4 Applications modelled by logical nodes defined in IEC\u00a061850-7-4 Tables \n Table 1 \u2013 LN groups <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Figure 4 \u2013 Logical node information categories Figure 5 \u2013 Build-up of devices (principle) <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.5 The semantic is attached to data Figure 6 \u2013 Position information depicted as a tree (conceptual) <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5.6 The services to exchange information Figure 7 \u2013 Service excerpt <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.7 Services mapped to concrete communication protocols <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 5.8 The configuration of the automation system Figure 8 \u2013 Example of communication mapping <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.9 Summary Figure 9 \u2013 Summary <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 6 Modelling approach of the IEC\u00a061850 series 6.1 Decomposition of application functions and information Figure 10 \u2013 Decomposition and composition process (conceptual) <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 6.2 Creating information models by stepwise composition <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Table 2 \u2013 Logical node class XCBR (conceptual) <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Figure 11 \u2013 XCBR1 information depicted as a tree <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 6.3 Example of an IED composition 6.4 Information exchange models Figure 12 \u2013 Example of IED composition <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Figure\u00a013 \u2013 Output and input model (principle) <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure 14 \u2013 Output model (step 1) (conceptual) <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figure 15 \u2013 Output model (step 2) (conceptual) Figure 16 \u2013 GSE output model (conceptual) <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Figure 17 \u2013 Setting data (conceptual) <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table 3 \u2013 Excerpt of integer status setting <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 18 \u2013 Input model for analogue values (step 1) (conceptual) <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Figure 19 \u2013 Range and deadbanded value (conceptual) <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Figure 20 \u2013 Input model for analogue values (step 2) (conceptual) <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 21 \u2013 Reporting and logging model (conceptual) <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 22 \u2013 Data set members and reporting Table 4 \u2013 Comparison of the data access methods <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 23 \u2013 Buffered report control block (conceptual) <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Figure 24 \u2013 Buffer time <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure 25 \u2013 Data set members and inclusion-bitstring Figure 26 \u2013 Log control block (conceptual) <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure 27 \u2013 Peer-to-peer data value publishing model (conceptual) <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Figure 28 \u2013 Conceptual model of statistical and historical statistical data (1) <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Figure 29 \u2013 Conceptual model of statistical and historical statistical data (2) <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 30 \u2013 Concept of the service tracking model\u00a0\u2013\u00a0Example: control service tracking <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 7 Application view 7.1 General Figure 31 \u2013 Real world devices <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 7.2 First modelling step \u2013 Logical nodes and data Figure 32 \u2013 Logical nodes and data (IEC\u00a061850-7-2) <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Figure 33 \u2013 Simple example of modelling Figure 34 \u2013 Basic building blocks <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Figure 35 \u2013 Logical nodes and PICOM Figure 36 \u2013 Logical nodes connected (outside view in IEC\u00a061850-7-x series) <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 7.3 Mode and behaviour of a logical node 7.4 Use of measurement ranges and alarms for supervision functions Figure\u00a037 \u2013 Mode and behaviour data (IEC\u00a061850-7-4) <\/td>\n<\/tr>\n | ||||||
61<\/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) Figure\u00a038 \u2013 Data used for limiting the access to control actions (IEC\u00a061850-7-4) <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 7.8 Data used for testing Figure 40 \u2013 Data used for receiving simulation signals <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Figure 41 \u2013 Example of input signals used for testing <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 7.9 Logical node used for extended logging functions Figure 42 \u2013 Test mode example <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 8 Device view 8.1 General Figure 43 \u2013 Logical node used for extended logging functions (GLOG) <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 8.2 Second modelling step \u2013 logical device model Figure 44 \u2013 Logical device building block <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Figure 46 \u2013 The common data class DPL <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Figure 47 \u2013 Logical devices in proxies or gateways <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Figure\u00a048 \u2013 Logical devices for monitoring external device health <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Figure 49 \u2013 Logical devices management hierarchy <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 9 Communication view 9.1 General 9.2 The service models of the IEC\u00a061850 series <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Figure 50 \u2013 ACSI communication methods Table 5 \u2013 ACSI models and services <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 9.3 The virtualisation <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 9.4 Basic information exchange mechanisms Figure 51 \u2013 Virtualisation Figure 52 \u2013 Virtualisation and usage <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Figure 53 \u2013 Information flow and modelling Figure 54 \u2013 Application of the GSE model <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 9.5 The client-server building blocks Figure 55 \u2013 Server building blocks <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 56 \u2013 Interaction between application processand application layer (client\/server) Figure 57 \u2013 Example for a service <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 9.6 Logical nodes communicate with logical nodes Figure 58 \u2013 Client\/server and logical nodes Figure 59 \u2013 Client and server roles <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 9.7 Interfaces inside and between devices Figure 60 \u2013 Logical nodes communicate with logical nodes <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 10 Where physical devices, application models and communication meet Figure 61 \u2013 Interfaces inside and between devices <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 11.2 Example 1 \u2013 Logical node and data class Figure 63 \u2013 Refinement of the DATA class <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table 6 \u2013 Logical node circuit breaker <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table 7 \u2013 Controllable double point (DPC) <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Figure 64 \u2013 Instances of a DATA class (conceptual) <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 11.3 Example 2 \u2013 Relationship of IEC\u00a061850-7-2, IEC\u00a061850-7-3, and IEC\u00a061850-7-4 Figure 65 \u2013 Relation between parts of the IEC\u00a061850 series <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 12 Formal specification method 12.1 Notation of ACSI classes Table 8 \u2013 ACSI class definition <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 12.2 Class modelling Figure 66 \u2013 Abstract data model example for IEC\u00a061850-7-x <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Table 9 \u2013 Single point status common data class (SPS) <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table 10 \u2013 Quality components attribute definition Table 11 \u2013 Basic status information template (excerpt) <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure 67 \u2013 Relation of TrgOp and Reporting Table 12 \u2013 Trigger option <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table 13 \u2013 GenLogicalNodeClass definition <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 12.3 Service tables Figure 68 \u2013 Sequence diagram <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | 12.4 Referencing instances Figure 69 \u2013 References <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure 70 \u2013 Use of FCD and FCDA <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure 71 \u2013 Object names and object reference <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 13 Name spaces 13.1 General Figure 72 \u2013 Definition of names and semantics <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | 13.2 Name spaces defined in the IEC\u00a061850-7-x series Figure 73 \u2013 One name with two meanings <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Figure 74 \u2013 Name space as class repository <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Figure 75 \u2013 All instances derived from classes in a single name space <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Figure 76 \u2013 Instances derived from multiple name spaces Figure 77 \u2013 Inherited name spaces <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 13.3 Specification of name spaces <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 13.4 Attributes for references to name spaces <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table 14 \u2013 Excerpt of logical node name plate common data class (LPL) Table 15 \u2013 Excerpt of common data class <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | 14 Common rules for new version of classes and for extension of classes 14.1 General 14.2 Basic rules <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 14.3 Rules for LN classes Figure 78 \u2013 Basic extension rules diagram <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | 14.4 Rules for common data classes and control block classes <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | 14.5 Multiple instances of LN classes for dedicated and complex functions <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 14.6 Specialisation of data by use of number extensions 14.7 Examples for new LNs 14.8 Example for new Data <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Annex A (informative) \nOverview of logical nodes and data <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table A.1 \u2013 Excerpt of data classes for measurands <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Table A.2 \u2013 List of common data classes (excerpt) <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Annex B (informative) \nAllocation of data to logical nodes Figure B.1 \u2013 Example for control and protection LNs combined in one physical device <\/td>\n<\/tr>\n | ||||||
117<\/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 | ||||||
119<\/td>\n | Annex C (informative) \nUse of the substation configuration language (SCL) Figure C.1 \u2013 Application of SCL for LNs (conceptual) <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Figure C.2 \u2013 Application of SCL for data (conceptual) <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Annex D (informative) \nApplying the LN concept to options for future extensions Figure D.1 \u2013 Seamless communication (simplified) <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Figure D.2 \u2013 Example for new logical nodes <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Figure D.3 \u2013 Example for control center view and mapping to substation view <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Annex E (informative) \nRelation 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 | ||||||
127<\/td>\n | Annex F (informative) \nMapping the ACSI to real communication systems Figure F.1 \u2013 ACSI mapping to an application layer <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | Figure F.2 \u2013 ACSI mappings (conceptual) <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Figure F.5 \u2013 Mapping approach <\/td>\n<\/tr>\n | ||||||
131<\/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 | ||||||
132<\/td>\n | Figure F.8 \u2013 Use of MMS named variables and named variable list <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Figure F.9 \u2013 MMS information report message <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Figure F.10 \u2013 Mapping example <\/td>\n<\/tr>\n | ||||||
135<\/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 |