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