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.

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.

The guidelines in this document are based on the functional definitions of

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.
IEC TR 61850-7-500, Basic information and communication structure – 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.
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.

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.

PDF Catalog

PDF Pages	PDF Title
2	undefined
4	CONTENTS
8	FOREWORD
10	INTRODUCTION
11	1 Scope 2 Normative references
12	3 Terms and definitions
13	4 Methodology for profiling 4.1 General
14	4.2 IEC 61850 profiling concept 4.2.1 General Figures Figure 1 – Stakeholders collaborate in user groups to create a common IOP profile
15	4.2.2 IEC 61850 profile definition Figure 2 – Framework for profiling IEC 61850
16	4.3 Basic Application Profiles (BAPs)
18	4.4 Basic Application Interoperability Profiles (BAIOPs) Figure 3 – Aggregating BAPs
20	4.5 Process from a use case to interoperability on SGAM function layer Figure 4 – Framework for testing a profile
21	Figure 5 – Relation between BAP and SGAM interoperability Figure 6 – Device features covered by profiles depending on compatibility levelsaccording to IEC Technical Committee 65, Industrial-process measurement, control and automation
22	4.6 Managing profiles 4.7 Implementation of BAPs in real projects Figure 7 – BAPs and BAIOPs as building blocks for user/project specific implementation and testing
23	Annex A (informative)Example for BAP of distributed automation function“reverse blocking” using BAP template A.1 Functional description Figure A.1 – Behaviour in the event of faults on an outflow bay
24	Figure A.2 – Behaviour in the event of busbar faults
25	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 – List of roles / actors reverse blocking Figure A.4 – Use case reverse blocking
26	A.2.3 Sequence diagram of typical interactions Figure A.5 – Sequence diagram reverse blocking
27	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 – Logical architecture reverse blocking
28	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
29	A.7.2 PTOC for blocked function (infeed bay) Tables Table A.1 – Selection of data attributes for PTOC of actor blocked
30	A.7.3 PTOC for blocking function 1 to n (outflow bay(s)) A.7.4 Monitoring Table A.2 – Selection of data attributes for PTOC of actor blocking Table A.3 – Selection of data attributes of PTOC for monitoring
31	A.8 Communication services A.9 Device related requirements (conditional) – Test behaviour A.10 Engineering tool related requirements A.11 Naming rules A.12 Capabilities for testing
32	Annex B (informative)Example for BAP of “condition monitoring diagnosis functionsof on-load tap changer” using BAP template B.1 Functional description Figure B.1 – Structure of LTC
33	Figure B.2 – Overview of system configuration of LTC condition monitoring Figure B.3 – Typical system configuration of LTC condition monitoring system
34	B.2 Description of use case and associated roles/actors B.2.1 List of roles / actors Table B.1 – List of actors
35	B.2.2 Use case Figure B.4 – Use cases
36	B.2.3 Sequence diagram of typical interactions Figure B.5 – Sequence diagram for monitoring operation property
37	Figure B.6 – Sequence diagram for monitoring operation counts Figure B.7 – Sequence diagram for monitoring contact abrasion
38	Figure B.8 – Sequence diagram for monitoring oil temperature and flow Figure B.9 – Sequence diagram for monitoring operation of oil filter unit
39	B.3 Logical Architecture B.3.1 Overview Figure B.10 – Logical architecture
40	B.3.2 Monitoring operation property B.3.3 Monitoring operation counts Figure B.11 – Logical architecture for monitoring operation property Figure B.12 – Logical architecture for monitoring operation counts
41	B.3.4 Monitoring contact abrasion B.3.5 Monitoring LTC oil temperature and flow Figure B.13 – Logical architecture for monitoring contact abrasion Figure B.14 – Logical architecture for monitoring LTC oil temperature and flow
42	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 – Logical architecture for monitoring operation of oil filter unit
43	B.7 Description of data model per actor B.7.1 General B.7.2 SLTC Table B.2 – Selection of data attributes of SLTC
46	B.7.3 YLTC B.7.4 TTRQ B.7.5 TCTR Table B.3 – Selection of data attributes of YLTC Table B.4 – Selection of data attributes of TTRQ Table B.5 – Selection of data attributes of TCTR
47	B.7.6 SIML B.7.7 TTMP Table B.6 – Selection of data attributes of SIML Table B.7 – Selection of data attributes of TTMP
48	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 – Selection of data attributes of KFIL
49	Annex C (informative)Example for BAP of protection function “line distance protection”using BAP template C.1 Functional description C.2 Description of use case and associated roles/actors C.2.1 List of roles / actors
50	C.2.2 Use case Figure C.1 – Use case distance protection
51	C.2.3 Sequence diagram of typical interactions Figure C.2 – Sequence diagram distance protection
52	C.3 Logical architecture C.4 Allocation variants (conditional) C.5 Functional variants C.5.1 Core functional variants Figure C.3 – Logical architecture distance protection
53	C.5.2 Noncore functional variants (different features for testing) C.6 Performance requirements) C.6.1 Functional related C.6.2 Service related
54	C.7 Description of data model per actor Table C.1 – Description of data model
56	C.8 Communication services C.8.1 General C.8.2 Variant FA: Table C.2 – Services for variant FA
57	C.8.3 Variant FB: C.9 Device related requirements (conditional) C.9.1 Degraded operation behaviour Table C.3 – Services for variant FB
58	C.10 Engineering tool related requirements C.11 Naming rules C.12 Capabilites for testing Table C.4 – Degraded operation behaviours
59	Annex D (informative)Example of BAIOP for BAP reverse blocking(without process bus) D.1 General D.2 Test description D.2.1 General
60	D.2.2 Normal sequence of reverse blocking Figure D.1 – Normal sequence of application function reverse blocking Table D.1 – Description of normal operation of application function reverse blocking
62	D.2.3 Functional description of test environment D.2.4 Test reverse blocking – role blocking (without output to process) Figure D.2 – Functional test environment Figure D.3 – Test of role “blocking”
63	Table D.2 – Description of sequence for test of role “blocking”
64	D.2.5 Test reverse blocking – role blocked Figure D.4 – Test of role “blocked”
65	Table D.3 – Description of sequence for test of role “blocked”
67	Annex E (informative)Example of BAIOP for BAP of “condition monitoring diagnosis functions of on-load tap changer” E.1 General E.2 Test description E.2.1 Overview
68	E.2.2 Sequence of monitoring the motor drive current value Figure E.1 – Sequence of monitoring the motor drive current value
69	Table E.1 – Description of the sequence of monitoring the motor drive current value
70	Bibliography

Published By	Publication Date	Number of Pages
BSI	2019	72


PDF Format	Searchable	Printable	Preview Now

Status	Definitive
Pages	72
Publication Date	2019-01-23
ISBN	978 0 539 00722 0
Standard Number	PD IEC TR 61850-7-6:2019
Title	Communication networks and systems for power utility automation – Guideline for definition of Basic Application Profiles (BAPs) using IEC 61850
Identical National Standard Of	IEC TR 61850-7-6:2019
Descriptors	Formats (data), Communication networks, Automation, Data, Data formats
Publisher	BSI
Committee	PEL/57
ICS Codes	33.200 - Telecontrol. Telemetering

BSI PD IEC TR 61850-7-6:2019

PDF Catalog

Related products