BSI PD IEC TS 61850-1-2:2020
$189.07
Communication networks and systems for power utility automation – Guidelines on extending IEC 61850
| Published By | Publication Date | Number of Pages |
| BSI | 2020 | 48 |
This part of IEC 61850, which is a technical specification, is intended for any users but primarily for standardization bodies that are considering using IEC 61850 as a base standard within the scope of their work and are willing to extend it as allowed by the IEC 61850 standards. This document identifies the required steps and high-level requirements in achieving such extensions of IEC 61850 and provides guidelines for the individual steps.
Within that scope, this document addresses the following cases:
-
The management of product-level standards for products that have an interface based on IEC 61850
-
The management of domain-level standards based on IEC 61850
-
The management of transitional standards based on IEC 61850
-
The management of private namespaces based on IEC 61850
-
The development of standards offering the mapping of IEC 61850 data model at CDC level
-
The development and management of IEC 61850 profiles for domains (underlying the role of IEC TR 62361-103 and IEC TR 61850-7-6)
This document includes both technical and process aspects:
On the technical side, this document:
-
Highlights the main basic requirements (mostly referring to the appropriate parts of the series which host the requirements or recommendations)
-
Lists all possible flexibilities offered by the standards
-
Defines which flexibilities are allowed/possible per type of extension cases
On the process side, the document covers:
-
The initial analysis of how the existing IEC 61850 object models and/or communication services may be applied and what allowed extensions may be required for utilizing them in new or specific domains (including private ones). The results of that step are expected to be documented
-
The extension of the IEC 61850 object models for new domains. The typical associated work is to identify existing logical nodes which can be reused “as is”, to determine if existing logical nodes can be extended, or to define new logical nodes
-
The purpose and process to use transitional namespaces, which are expected to be merged eventually into an existing standard namespace
-
The management of standard namespaces
-
The development of private namespaces
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 4 | CONTENTS |
| 6 | FOREWORD |
| 8 | 1 Scope |
| 9 | 2 Normative References |
| 10 | 3 Terms and definitions |
| 12 | 4 Key principles reminder 4.1 General 4.2 Namespace introduction 4.2.1 General |
| 13 | 4.2.2 Basic namespaces |
| 14 | 5 Main cases of extensions of IEC 61850 5.1 Namespace extensions and associated rules 5.1.1 General 5.1.2 Domain namespaces 5.1.3 Product standard namespaces 5.1.4 Transitional namespaces |
| 15 | 5.1.5 Private namespaces 5.2 IEC 61850 profiles for domains 5.3 Mapping of IEC 61850 data model to other protocols at CDC level 6 What to extend in relation with IEC 61850? 6.1 List of basic requirements 6.1.1 General 6.1.2 IEC 61850 structure reminder |
| 16 | Figures Figure 1 – IEC 61850 documentation structure |
| 17 | 6.1.3 Main deliverables and their positioning in IEC 61850 documentation structure Figure 2 – Extensions deliverables positioned in the IEC 61850 document structure |
| 18 | 6.1.4 Intellectual property requirements Tables Table 1 – Typical deliverables attached to IEC 61850 extensions |
| 19 | 6.1.5 Editorial Recommendations 6.1.6 Data Model extension requirements |
| 21 | Table 2 – Normative information related to a namespace(for example for IEC61850‑7‑420:2009A release 5) Table 3 – Informative information related to a namespace(for example for IEC61850‑7‑420:2009A release 5) |
| 25 | Table 4 – Classification of Abbreviations in regardsof their contribution to form a DO Name (examples) |
| 27 | Table 5 – Semantic description frame and requirements |
| 28 | 6.1.7 XML namespace extensions |
| 29 | 6.1.8 Cyber-security requirements 6.1.9 Conformance Testing requirements 6.1.10 Maintenance of standard extension document |
| 30 | Figure 3 – Handling versioning information for official IEC publication |
| 31 | Figure 4 – Handling versioning information during the internal IEC writing process |
| 32 | Figure 5 – Example of tissue fix sequence and its impact on versioning information |
| 33 | 6.1.11 Backward compatibility treatment Table 6 – Typical compatibility assessment Table 7 – Typical compatibility assessment and associated compatibility rules – detailed discussion |
| 34 | Table 8 – Typical compatibility table |
| 35 | 6.2 List of IEC 61850 flexibilities 6.2.1 General 6.2.2 Data Model flexibilities |
| 37 | 6.2.3 Communication services 6.2.4 SCL language |
| 39 | 6.3 Allowed flexibilities per extension cases Table 9 – Allowed flexibilities per extension cases |
| 41 | 7 The main activities for extending IEC 61850 7.1 Typical activities applying to all types of extension 7.1.1 General Figure 6 – Activities related to IEC 61850 extensions |
| 42 | 7.1.2 List the main use cases for extending IEC 61850 -> deliverable P1 7.1.3 Ensure knowledge of the existing IEC 61850 content 7.1.4 Identify possible IEC 61850 gaps 7.1.5 Build-up IEC 61850 extensions 7.1.6 Maintain IEC 61850 extensions 7.2 Define a standard namespace (product, domain or transitional) – if needed -> deliverable P2a or P2b 7.2.1 General |
| 43 | 7.2.2 Get a model manager nominated 7.2.3 Get the proposed model reviewed 7.2.4 Publish a namespace extension |
| 44 | 7.3 Define “standard” profile(s) – if needed –> deliverable P3 (and P4) 7.3.1 General 7.3.2 Define interoperability objectives 7.3.3 Publish profile(s) -> deliverable P3 7.3.4 Publish profile(s) testing -> deliverable P4 |
| 45 | Annex A (informative)IEC 61850 roadmap (example) |
| 46 | Figure A.1 – Example of IEC 61850 roadmap |
| 47 | Bibliography |
Related products
-
BSI PD IEC TS 61850-1-2:2020+A1:2022
Communication networks and systems for power utility automation – Guideline on extending IEC 61850 Published…
