This part of IEC 61850, which is a technical report, is focused on building application \/ function profiles and specifies a methodology to define Basic Application Profiles (BAPs). These Basic Application Profiles provide a framework for interoperable interaction within or between typical substation automation functions. BAPs are intended to define a subset of features of IEC 61850 in order to facilitate interoperability in a modular way in practical applications.<\/p>\n
It is the intention of this document to provide a common and generic way to describe the functional behaviour of a specific application function in the domain of power utility automation systems as a common denominator of various possible interpretations\/implementations of using IEC 61850.<\/p>\n
The guidelines in this document are based on the functional definitions of<\/p>\n
IEC 61850-5, Communication requirements for functions and device models, which gives a comprehensive overview of all application functions needed in a state-of-the-art substation automation implementation.<\/p>\n<\/li>\n
IEC TR 61850-7-500, Basic information and communication structure \u2013 Use of logical nodes for modelling application functions and related concepts and guidelines for substations, which illustrates and explains application functions for the substation\/protection domain of Logical Nodes in modelling simple and complex functions, to improve common understanding in modelling and data exchange, and finally to lead to interoperable implementations.<\/p>\n<\/li>\n
IEC TR 61850-90-3, Using IEC 61850 for condition monitoring diagnosis and analysis, which gives use cases and data modelling for condition monitoring diagnosis and analysis functions for substation and power grid facilities.<\/p>\n<\/li>\n<\/ul>\n
This document does not describe the applications and respective implementation requirements; the focus is on their typical information exchange including data and communication services and engineering conventions.<\/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 | ||||||
| 10<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 4 Methodology for profiling 4.1 General <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4.2 IEC 61850 profiling concept 4.2.1 General Figures Figure 1 \u2013 Stakeholders collaborate in user groups to create a common IOP profile <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4.2.2 IEC 61850 profile definition Figure 2 \u2013 Framework for profiling IEC 61850 <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 4.3 Basic Application Profiles (BAPs) <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 4.4 Basic Application Interoperability Profiles (BAIOPs) Figure 3 \u2013 Aggregating BAPs <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 4.5 Process from a use case to interoperability on SGAM function layer Figure 4 \u2013 Framework for testing a profile <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | Figure 5 \u2013 Relation between BAP and SGAM interoperability Figure 6 \u2013 Device features covered by profiles depending on compatibility levelsaccording to IEC Technical Committee 65, Industrial-process measurement, control and automation <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 4.6 Managing profiles 4.7 Implementation of BAPs in real projects Figure 7 \u2013 BAPs and BAIOPs as building blocks for user\/project specific implementation and testing <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | Annex A (informative)Example for BAP of distributed automation function\u201creverse blocking\u201d using BAP template A.1 Functional description Figure A.1 \u2013 Behaviour in the event of faults on an outflow bay <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Figure A.2 \u2013 Behaviour in the event of busbar faults <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | A.2 Description of use case and associated roles\/actors A.2.1 List of roles \/ actors A.2.2 Use case Figure A.3 \u2013 List of roles \/ actors reverse blocking Figure A.4 \u2013 Use case reverse blocking <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | A.2.3 Sequence diagram of typical interactions Figure A.5 \u2013 Sequence diagram reverse blocking <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | A.3 Logical architecture A.4 Allocation variants (conditional) A.5 Functional variants A.5.1 Core functional variants A.5.2 Noncore functional variants Figure A.6 \u2013 Logical architecture reverse blocking <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | A.6 Performance requirements A.6.1 Functional related A.6.2 Service related A.7 Description of data model per actor A.7.1 General <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | A.7.2 PTOC for blocked function (infeed bay) Tables Table A.1 \u2013 Selection of data attributes for PTOC of actor blocked <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | A.7.3 PTOC for blocking function 1 to n (outflow bay(s)) A.7.4 Monitoring Table A.2 \u2013 Selection of data attributes for PTOC of actor blocking Table A.3 \u2013 Selection of data attributes of PTOC for monitoring <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | A.8 Communication services A.9 Device related requirements (conditional) \u2013 Test behaviour A.10 Engineering tool related requirements A.11 Naming rules A.12 Capabilities for testing <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Annex B (informative)Example for BAP of \u201ccondition monitoring diagnosis functionsof on-load tap changer\u201d using BAP template B.1 Functional description Figure B.1 \u2013 Structure of LTC <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Figure B.2 \u2013 Overview of system configuration of LTC condition monitoring Figure B.3 \u2013 Typical system configuration of LTC condition monitoring system <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | B.2 Description of use case and associated roles\/actors B.2.1 List of roles \/ actors Table B.1 \u2013 List of actors <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | B.2.2 Use case Figure B.4 \u2013 Use cases <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | B.2.3 Sequence diagram of typical interactions Figure B.5 \u2013 Sequence diagram for monitoring operation property <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Figure B.6 \u2013 Sequence diagram for monitoring operation counts Figure B.7 \u2013 Sequence diagram for monitoring contact abrasion <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | Figure B.8 \u2013 Sequence diagram for monitoring oil temperature and flow Figure B.9 \u2013 Sequence diagram for monitoring operation of oil filter unit <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | B.3 Logical Architecture B.3.1 Overview Figure B.10 \u2013 Logical architecture <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | B.3.2 Monitoring operation property B.3.3 Monitoring operation counts Figure B.11 \u2013 Logical architecture for monitoring operation property Figure B.12 \u2013 Logical architecture for monitoring operation counts <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | B.3.4 Monitoring contact abrasion B.3.5 Monitoring LTC oil temperature and flow Figure B.13 \u2013 Logical architecture for monitoring contact abrasion Figure B.14 \u2013 Logical architecture for monitoring LTC oil temperature and flow <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | B.3.6 Monitoring operation of oil filter unit B.4 Allocation variants (conditional) B.5 Functional variants B.6 Performance requirements B.6.1 Functional related B.6.2 Service related Figure B.15 \u2013 Logical architecture for monitoring operation of oil filter unit <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | B.7 Description of data model per actor B.7.1 General B.7.2 SLTC Table B.2 \u2013 Selection of data attributes of SLTC <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | B.7.3 YLTC B.7.4 TTRQ B.7.5 TCTR Table B.3 \u2013 Selection of data attributes of YLTC Table B.4 \u2013 Selection of data attributes of TTRQ Table B.5 \u2013 Selection of data attributes of TCTR <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | B.7.6 SIML B.7.7 TTMP Table B.6 \u2013 Selection of data attributes of SIML Table B.7 \u2013 Selection of data attributes of TTMP <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | B.7.8 KFIL B.8 Communication services B.9 Device related requirements (conditional) B.10 Engineering tool related requirements B.11 Naming rules B.12 Capabilities for testing Table B.8 \u2013 Selection of data attributes of KFIL <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | Annex C (informative)Example for BAP of protection function \u201cline distance protection\u201dusing BAP template C.1 Functional description C.2 Description of use case and associated roles\/actors C.2.1 List of roles \/ actors <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | C.2.2 Use case Figure C.1 \u2013 Use case distance protection <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | C.2.3 Sequence diagram of typical interactions Figure C.2 \u2013 Sequence diagram distance protection <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | C.3 Logical architecture C.4 Allocation variants (conditional) C.5 Functional variants C.5.1 Core functional variants Figure C.3 \u2013 Logical architecture distance protection <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | C.5.2 Noncore functional variants (different features for testing) C.6 Performance requirements) C.6.1 Functional related C.6.2 Service related <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | C.7 Description of data model per actor Table C.1 \u2013 Description of data model <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | C.8 Communication services C.8.1 General C.8.2 Variant FA: Table C.2 \u2013 Services for variant FA <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | C.8.3 Variant FB: C.9 Device related requirements (conditional) C.9.1 Degraded operation behaviour Table C.3 \u2013 Services for variant FB <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | C.10 Engineering tool related requirements C.11 Naming rules C.12 Capabilites for testing Table C.4 \u2013 Degraded operation behaviours <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | Annex D (informative)Example of BAIOP for BAP reverse blocking(without process bus) D.1 General D.2 Test description D.2.1 General <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | D.2.2 Normal sequence of reverse blocking Figure D.1 \u2013 Normal sequence of application function reverse blocking Table D.1 \u2013 Description of normal operation of application function reverse blocking <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | D.2.3 Functional description of test environment D.2.4 Test reverse blocking \u2013 role blocking (without output to process) Figure D.2 \u2013 Functional test environment Figure D.3 \u2013 Test of role \u201cblocking\u201d <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | Table D.2 \u2013 Description of sequence for test of role \u201cblocking\u201d <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | D.2.5 Test reverse blocking \u2013 role blocked Figure D.4 \u2013 Test of role \u201cblocked\u201d <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | Table D.3 \u2013 Description of sequence for test of role \u201cblocked\u201d <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | Annex E (informative)Example of BAIOP for BAP of \u201ccondition monitoring diagnosis functions of on-load tap changer\u201d E.1 General E.2 Test description E.2.1 Overview <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | E.2.2 Sequence of monitoring the motor drive current value Figure E.1 \u2013 Sequence of monitoring the motor drive current value <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | Table E.1 \u2013 Description of the sequence of monitoring the motor drive current value <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – Guideline for definition of Basic Application Profiles (BAPs) using IEC 61850<\/b><\/p>\n |