This part of IEC 61850, which is a technical report, establishes modelling concepts that help the user to understand how to apply the models defined in IEC 61850-7-4 and IEC 61850-7-3 to implement practical applications.<\/p>\n
This document provides the basic concepts that are valid for all application domains using IEC 61850. Domain specific concepts are defined in other technical reports as in the document range of IEC 61850-7-5xx; as an example, IEC 61850-7-500 describes modelling concepts for functions related to substation automation.<\/p>\n
On one side the number of potential topics for cross-domain modelling may be very high but on the other side it may be limited by domain specific restrictions often created by the historical evolution of IEC 61850 in the domains.<\/p>\n
The first topic selected is the common control of power utility primary objects by means of the power utility automation systems based mainly on the long experience in substation automation systems. Common attributes for reliable power utility automation systems in all domains are quality and health. A special function having a broad application range in power utility automation systems is the scheduling of services as provided by the domain distributed energy resources (DER) used in smart grids, especially also for electric mobility. Not yet so much discussed in the context of IEC 61850 but very important for all IEDs is the impact of restart (power cycle) on the data model parameters. Non-agreed behaviour will raise problems for interoperability in multi-vendor systems.<\/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 | ||||||
| 6<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions 3.2 Abbreviated terms 4 Control 4.1 Control authorization 4.1.1 Basics <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 4.1.2 Validating a control request Figures Figure 1 \u2013 Communication vs. application layer model for controls <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | Tables Table 1 \u2013 Dependence of checking Interlocking (IL) conditionson the control command and on the server configuration <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | Table 2 \u2013 Dependence of checking synchronism (CS) conditionson the control command and on the server configuration <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4.1.3 Exclusive control authorization for one out of multiple actors of the same level of control hierarchy Figure 2 \u2013 Different levels of control authority (example) <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4.1.4 Different control permissions for different actors of the same level of control hierarchy 4.2 Control authority for process equipment 4.2.1 Control commands for process equipment from automations instead of HMI <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | Table 3 \u2013 Use case 1 definition <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5 Quality and its propagation 5.1 Standard processing principle 5.1.1 General 5.1.2 Respecting behaviour <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 5.1.3 LN specific calculations 5.1.4 detailQual is not propagated 5.1.5 Configurable propagation of the value of the element \u2018source\u2019 5.1.6 operatorBlocked is not propagated 5.2 Special processing principle for (single phase) XCBR mapping to CSWI 5.2.1 General <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | Figure 3 \u2013 Single-phase monitoring of the CB position <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5.2.2 Respecting the Behaviour 5.2.3 LN specific calculations 5.2.4 Propagation of detailQual 5.2.5 Substitution of switchgear position signals <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5.2.6 operatorBlocked is not propagated 5.3 Conclusion Table 4 \u2013 Example of fixed rules: Boolean OR out of two input signals <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6 Health and its application 6.1 General 6.2 The use of LPHD.PhyHealth, LLN0.Health, LN.Health and LN.EEHealth <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | Table 5 \u2013 Health in IEC 61850-7-4 <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6.3 Health in Proxy-IEDs, in LNs of type Mirror and in a LD hierarchy <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Figure 4 \u2013 Examples of use of Health and EEHealth in models <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7 Special functions 7.1 Use of cross domain schedules and scheduler 7.1.1 Introduction Figure 5 \u2013 FSCH and FSCC LN class <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.1.2 Example 1 Figure 6 \u2013 State Machine Figure 7 \u2013 Relation between schedule controller, schedules and entity scheduled <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Figure 8 \u2013 Use case charging architecture <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | Figure 9 \u2013 LN instances and relationships in example 1 Figure 10 \u2013 Timelines associated to the example 1 <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 7.1.3 Example 2 Figure 11 \u2013 LN instances and relationships in example 2 <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Figure 12 \u2013 Timelines associated to the example 2 <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 8 Restoration of functions\/communication after IED restart (power cycle) 8.1 Functional description 8.2 Priorities 8.3 Stored and non-stored data <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Table 6 \u2013 Examples for stored and non-stored data for restart <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – IEC 61850 Modelling concepts<\/b><\/p>\n |