🔥🔥 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-90-11:2020

BSI PD IEC TR 61850-90-11:2020

$215.11

Communication networks and systems for power utility automation – Methodologies for modelling of logics for IEC 61850 based applications

Published By Publication Date Number of Pages
BSI 2020 104
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]

1.1 General

This part of IEC 61850, which is a Technical Report, describes the methodologies for the modelling of logics for IEC 61850 based applications in power utility automation. In particular, it describes the functional view of logic based on existing logical nodes for generic process automation and the operational modes of the logic. Furthermore it includes the specification of the standard language to be applied to specific the logic as well as the related data exchange format between engineering tools and their application as well as the mapping of logic elements to IEC 61850 data types.

The examples or use cases given in this document are based on the class model introduced in IEC 61850-7-1 and defined in IEC 61850-7-3. The logical node and data names used in this document are defined in IEC 61850-7-4, the services applied in IEC 61850-7-2. The naming conventions of IEC 61850-7-2 are applied in this document also.

If extensions are needed in the application examples, the normative naming rules for multiple instances and private, compatible extensions of Logical Node (LN) Classes and Data Object Names defined in IEC 61850-7-1 are considered.

This document describes the use of IEC 61850 extensions for modelling logics, therefore it implies some tutorial material. However it is advisable to read IEC 61850-6 and IEC 61850-7-1 in conjunction with IEC 61850-7-3 and IEC 61850-7-2 first and IEC 61131-3 as reference for the programming language of logic.

The different logics included in any IED in an IEC 61850 based system can be classified into two groups:

  • Fixed Logic: These logics are predefined mostly for critical and complex functions. They are typically included in the IED´s defined application, potentially implemented in software, firmware or hardware, and are not modifiable with IEC 61850 tools and services. These logics are implementation specific. Fixed logic is out of the scope of this document.

  • Editable Logic: These are user configurable / programmable logics which shall be modelled through IEC 61850 configuration tools and be accessible by IEC 61850 services. These logics can be application specific.

The major goal of this document is to adopt the given functionality of an IED to fit to specific application function demands. This is to provide a definition of the methodology for describing and exchanging logics using an IEC 61850 compatible solution. As a benefit the same logic description will be valid and vendor-independent, so it could be used for different IEDs. It is up to the tools to understand this standard description in order to be able to manipulate the logics and to properly configure the IEDs.

Graphical representation of logic is currently out-of-scope of the IEC 61850 series, even if it is part of the PLCopen XML specification. The representation is subject to the engineering tools. Modelling logics requires some extension of the currently defined data model and / or an extension of the content in the SCL files which is described and which needs to be considered in later editions of IEC 61850-6 and IEC 61850-7-4. Some examples are included for guidance in Annex B.

PDF Catalog

PDF Pages PDF Title
2 undefined
4 CONTENTS
8 FOREWORD
9 Tables
Table 1 – Tracking information of (Tr) IEC 61850-90-11:2019A namespace building-up
10 INTRODUCTION
11 1 Scope
1.1 General
12 1.2 Published versions of this standard and related namespace name
1.3 Namespace name and version
Table 2 – Reference between published versions of the standard and related namespace name
Table 3 – Attributes of data model namespace
13 1.4 Code Component distribution
1.4.1 General
1.4.2 Data model namespace code component
Table 4 – Attributes of xsd namespace
14 1.4.3 XML schema namespace code component
2 Normative references
3 Terms and definitions
15 4 Abbreviated terms
5 Use cases
5.1 General
16 5.2 Use case 1 – Busbar disconnector coupled in a double busbar arrangement
Table 5 – Use case 1 definition
17 5.3 Use case 2 – Delayed breaker trip and blocking after 1st low gas pressure alarm
Table 6 – Use case 2 definition
18 5.4 Use case 3 – Bay connected to a busbar
Table 7 – Use case 3 definition
19 5.5 Use case 4 – Definite trip
Table 8 – Use case 4 definition
20 5.6 Use case 5 – “Direct transfer open operation”
Table 9 – Use case 5 definition
21 5.7 Use case 6 – Line outage detection in a breaker and a half scheme
22 Table 10 – Use case 6 definition
23 5.8 Use case 7 – Unit trip logic
Table 11 – Use case 7 definition
24 5.9 Use case 8 – Data quality management
Table 12 – Use case 8 definition
25 Table 13 – Example of a quality definition
26 5.10 Use case 9 – Switchgear control on the example of a busbar change-over sequence
Table 14 – Use case 9 definition
27 5.11 Conclusions
6 Functional requirements for logic modelling
6.1 Performance requirements
28 6.2 Specific management of Common Data Class (CDC) attributes
6.2.1 General
6.2.2 Quality
Figures
Figure 1 – Performance timing concepts
29 6.2.3 Time stamp
6.3 Switchgear control
6.3.1 Variant A: Control commands using control services on CSWI.Pos
30 6.3.2 Variant B: Control commands using GOOSE messages to XCBR/XSWI
Figure 2 – Scheme of variant A
31 6.3.3 Variant C: Control commands using GOOSE messages to CSWI
Figure 3 – Scheme of variant B
32 6.3.4 Conclusions on switchgear control issued by logics
Figure 4 – Scheme of variant C
33 6.3.5 Functional restrictions
Table 15 – Data object definition for control outputs
Table 16 – Configurations for the control output conditioner
34 7 Intended engineering process of logic
7.1 General
35 Figure 5 – Engineering process for logic based on IEC 61131-3
36 7.2 Management of logic at IED level
7.3 Distributed logic management
8 Logic modelling
8.1 Functional view for logics
37 Figure 6 – Functional view of a logical node
Figure 7 – Logic unit inside a GAPC logical node
38 8.2 Logical node instantiation hosting logic units
8.3 Operational modes
Figure 8 – GAPC logical node instantiation
39 8.4 Logic unit engine execution state
8.5 Change of logics IEC 61131 parameters and schemes
Table 17 – Data object definition for operational modes
Table 18 – PlcOpModeKind enumeration definition
40 8.6 Variable types and qualifiers
8.7 Variable names and binding conventions
Table 19 – Variable types and qualifiers
Table 20 – Allowed IEC 61131-3 qualifiers for data variables
41 8.8 Management of data quality attributes
Figure 9 – Binding
42 8.9 Management of time stamp
Figure 10 – Management of quality data attributes
43 8.10 Substitution model
Table 21 – Data object definition for time stamp calculation
Table 22 – CalcTimeAssignmentMethodKind enumeration definition
44 8.11 Management of switchgear controls
8.12 Analogue values
8.13 Services
Table 23 – Data object definition for analogue measured values
45 8.14 Initialisation
8.15 Standard language to describe the content of a logic unit
8.16 Mapping of IEC 61850 data types and IEC 61131-3 / PLCopen XML data types
8.16.1 General
8.16.2 IEC 61850 basic types mapping to IEC 61131-3
Table 24 – Mapping of basic data types from IEC 61850-7-2
46 8.16.3 IEC 61850 Common ACSI Types mapping to IEC 61131-3
8.16.4 IEC 61850 constructed attribute classes mapping to IEC 61131-3
Table 25 – Mapping of constructed attribute classes from IEC 61850-7-3
48 8.16.5 IEC 61850 CDC mapping to IEC 61131-3
49 Table 26 – Mapping of Common Data Classes from IEC 61850-7-3
55 8.16.6 IEC 61850 logical node data objects mapping to IEC 61131-3
8.17 Operators
8.18 Logics monitoring, testing and debugging
8.19 IEC TR 61850-90-11 data model namespace definition
8.19.1 General
8.19.2 Abbreviations
Table 27 – Normative abbreviations for data object names
56 8.19.3 Logical node classes
Figure 11 – Class diagram LogicalNodes_90_11::LogicalNodes_90_11
57 Figure 12 – Class diagram LNGroupG::LNGroupG
58 Table 28 – Data objects of GAPCExt
59 8.19.4 Enumerated data attribute types
Figure 13 – Class diagram DOEnums_90_11::DOEnums_90_11
60 8.20 IEC TR 61850-90-11 XML namespace definition
8.20.1 General
8.20.2 XML element
Table 29 – Literals of PlcOpModeKind
Table 30 – Literals of CalcTimeAssignmentMethodKind
61 9 Conformance testing
Figure 14 – UML representation of the IEC TR 61850-90-11 XML namespace
62 10 Testing of logic functions
11 Effects on other parts of IEC 61850
11.1 IEC 61850-5
11.2 IEC 61850-7-4
11.3 IEC 61850-6
11.4 IEC 61850-10
Table 31 – SICS Table G.1 – IED configurator conformance statement
63 Annexes
Annex A (informative) Use of SCL extension facilities for Logic Modelling
66 Annex B (informative) PLD example
B.1 Overview
B.2 PLD file
Figure B.1 – PLD file hosted in a GAPC LN instance (on the example of use case 5 – Direct transfer open operation)
72 B.3 Use of a logic unit in a GAPC logical node instance
75 Annex C (informative) Type compatibility for input/blocking references
Table C.1 – CDC types for InRef/BlkRef
76 Annex D (informative) Semantic of name plate attributes
Table D.1 – Semantics of name plate attributes of GAPC LN with Logic unit instances
77 Annex E (informative) Quality behaviour in user-defined logics
Figure E.1 – Quality behaviour table
78 Annex F (informative) Proposal of a solution for quality handling
F.1 Two ways of engineering logics
F.1.1 General
F.1.2 Details of the solution ”quality handling” and the extensions needed
79 Table F.1 – New CF attributes of DPC
80 F.1.3 Application example for “processed as invalid”
F.1.4 Effects on other parts of IEC 61850
F.2 SCD including definitions for quality handling
Table F.2 – ComBehaviourKind enumeration definition
Table F.3 – Configurations for the example
85 F.3 Lessons learnt from this exercise
86 Annex G (informative) Example of an engineering workflow
G.1 Workflow of interfacing the logics part (written in IEC 61131) in the IEC 61850 configuration, starting from SCD file
Table G.1 – Workflow definition
88 G.2 Lessons learnt from this exercise
89 Annex H (informative) Proposal of a protection against IEC 61131 engineering changes
90 Annex I (informative) Mapping from IEC 61850 CDC to PLCOpen XML
103 Bibliography

Related products

BSI PD IEC TR 61850-90-11:2020
$215.11