BSI PD IEC/TS 62361-102:2018
$215.11
Power systems management and associated information exchange. Interoperability in the long term – CIM. IEC 61850 harmonization
Published By | Publication Date | Number of Pages |
BSI | 2018 | 122 |
This part of IEC 62361, which is a Technical Specification, outlines a technical approach for achieving effective information exchange between power system installations governed by IEC 61850 and business systems integrated with IEC CIM standard data exchanges, based on a selected specific set of use cases, but also with the goal of creating a framework that will extend successfully to other use cases in the future. This document includes proposals to ‘harmonize’ the two standards by adapting or extending existing information models and/or defining new models, where such changes will enable more effective communication. Both current and future directions of models will be considered. The report will take into account existing standards for semantics, services, protocols, system configuration language, and architecture.
It was intended to be coordinated with IEC 61850 and all affiliated subgroups as well as IEC 61968 and IEC 61970. This edition of the document was prepared based on Edition 2 of IEC 61850-6 (2009), IEC 61850-7-3 and IEC 61850-7-4 and has been updated to match the forthcoming Edition 2.1. Mapping to other parts of IEC 61850 is incomplete. Mapping has been considered for the CIM classes defined in IEC 61970-301. The mapping to CIM classes defined in IEC 61968-11 and other standards is incomplete.
This document suggests a technical approach by which two of the leading standards for software interoperability that serve the electric utility industry (the Common Information Model, CIM, and the IEC 61850 model) can cooperate in order to enable effective data exchanges between the domains covered by these standards. Both of these standards are maintained by the International Electrotechnical Committee (IEC).
A number of studies and reports have already been produced on the subject of harmonization as listed in the Bibliography.
The work leading to this Technical Specification has considered how exchanges required by commonly understood use cases might be mapped between the standard models in order to determine the harmonizing changes suggested for the relevant models. The report references any papers, reports or other documents that provided data for this harmonization.
The approach is to define a transformation of the data governed by IEC 61850 SCL XSD to data governed by CIM UML. The transformations in this document are defined based on the use cases presented in this document. Only SCL data relevant to these use cases is transformed.
The aim is to allow the development of tools that perform automatic transformation from an SCL instance file into a CIM based instance model that can then be exported using existing standards such as IEC 61970-552: CIMXML Model exchange format.
These transformations will result in CIM-side processes that can distribute the information as needed for configuration of specific CIM applications. It is also presumed that the result of this exchange will be to enable creation of real-time CIM-side clients for IEC 61850 system data.
The heart of the SCL to CIM transformation specification defined in this document is a mapping between the two information models. Wherever this mapping has been judged to be unnecessarily complex, changes have been recommended to the existing information models.
A major objective, however, has been to define a solution that does not change either SCL or CIM UML without a mechanism to supply backward compatibility.
The transformation specification is only for structural modelling. IEC 61970-301 states “CIM entities have no behaviour.” IEC 61850-5 states “the behaviour of the functions itself are … outside the scope of this standard”.
This document is a Technical Specification − not a standard. Paragraphs introduced by the word Recommendation are recommendations for revisions to some of the IEC 61850 and CIM standards. It is anticipated that if these recommendations are accepted, then this report can be revised and elevated to a standard.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
4 | CONTENTS |
9 | FOREWORD |
11 | INTRODUCTION |
12 | 1 Scope |
13 | 2 Normative references 3 Terms, definitions and abbreviated terms |
14 | 3.1 Terms and definitions 3.2 Abbreviated terms |
15 | 4 Use case summary 4.1 General 4.2 SCADA/EMS/DMS configuration from IEC 61850 SCL |
16 | 4.3 Importing SCADA/EMS/DMS requirements into IEC 61850 SCL 4.3.1 General 4.3.2 Recommendation for harmonization: SCL Process/Substation/Line section 4.4 SCADA commissioning use case |
17 | 4.5 Volt Var control use case Figures Figure 1 – IEC 61850 and CIM data flows |
18 | 4.6 Wide Area Monitoring, Protection and Control (WAMPAC) for transient stability 5 Mapping SCL to SCADA/EMS/DMS relevant CIM 5.1 Business requirements Figure 2 – Mapping for Wide Area Monitoring Protection and Control |
19 | 5.2 Profiles 5.3 IEC 61850 modelling principles 5.3.1 Introduction 5.3.2 System Configuration description Language (SCL) 5.3.3 Logical Devices and Logical Nodes |
20 | 5.3.4 SCL sections 5.4 Mapping overview 5.4.1 SCL Document Types |
21 | 5.4.2 General mapping principles Tables Table 1 – Overview of SCL and CIM counterparts |
23 | Figure 3 – Equipment mapping |
24 | 5.5 SCL Substation section mapping 5.5.1 Overview Figure 4 – Example of equipment and status measurement mapping |
26 | Figure 5 – UML class diagram of SCL entities showing inheritance |
27 | Figure 6 – UML class diagram of SCL entities showing inheritance and containment |
28 | 5.5.2 SCL elements and CIM classes mapping Figure 7 – UML class diagram of SCL equipment connectivity and phase information |
29 | Table 2 – Mapping between SCL data types and CIM classes |
31 | 5.6 Equipment types and codes 5.6.1 General 5.6.2 Equipment type code mapping Table 3 – Equipment type codes |
33 | 5.6.3 Recommendation for harmonization: SCL Equipment Type codes |
34 | Table 4 – Equipment type codes – proposed modified descriptions |
35 | 5.6.4 Recommendation for harmonization: SCL PSRType Figure 8 – Composite Switch example. Table 5 – Equipment type codes – proposed additional codes |
36 | 5.6.5 Recommendation for harmonization: CIM BusbarSection and Junction 5.6.6 Recommendation for harmonization: CIM Fan, Motor, Batteries and charging systems 5.7 Naming and identification mapping 5.7.1 General |
37 | 5.7.2 Naming and identification example Table 6 – Name mapping |
38 | 5.7.3 Recommendation for harmonization: SCL naming and identification 5.7.4 Recommendation for harmonization: CIM naming and identification: 5.8 Voltage mapping 5.8.1 General Table 7 – Proposed CIM NameType class naming conventions |
39 | 5.8.2 Voltage mapping example 5.8.3 Voltage level additional attributes 5.9 Connectivity modelling 5.9.1 SCL Connectivity (single line diagram) modelling Table 8 – Base voltage mapping |
40 | Table 9 – Attributes for terminal |
41 | 5.9.2 Recommendation for harmonization: SCL unconnected terminals 5.9.3 Connectivity and Terminal example Table 10 – Attributes for ConnectivityNode |
42 | Figure 9 – Substation section connectivity example |
44 | 5.9.4 Transformation of current transformer models 5.10 Phase modelling 5.10.1 General |
45 | Figure 10 – Three-phase (left) and single-phase control (right) |
46 | 5.10.2 Phase mapping example Table 11 – Comparison of IEC 61850 and CIM Phase values Table 12 – Breaker mapping scenarios |
47 | Figure 11 – Unbalanced phase switching example |
49 | 5.10.3 Recommendation for harmonization: SCL Phase modeling 5.10.4 Recommendation for harmonization: CIM SinglePhaseKind 6 Extension syntax for drawing layout coordinates 6.1 General 6.2 Recommendation for harmonization: Drawing layout syntax |
50 | 7 Logical Node mapping 7.1 Logical Node containers 7.2 CIM Measurement associations 7.2.1 General |
51 | 7.2.2 Recommendation for harmonization: CIM SCADA package Figure 12 – Current CIM SCADA package |
52 | 7.3 Logical Node classes relevant to CIM Figure 13 – Revised SCADA package |
53 | Table 13 – Mapping IEC 61850 Logical Nodes to CIM classes |
55 | 8 Measurement mapping 8.1 General 8.2 CIM Measurement Types Logical Node and Data Object mapping 8.2.1 General |
56 | Table 14 – IEC 61850 DataObjects vs Current CIM measurement types |
57 | 8.2.2 Recommendation for harmonization: CIM Measurement types Table 15 – IEC 61850 DataObjects for non-three phase measurements Table 16 – IEC 61850 DataObjects for CIM control types |
58 | 8.3 Measurement associations 8.4 CSWI or XSWI/XCBR as source of switch position information 8.5 Direction of positive flow 8.5.1 General |
59 | 8.5.2 Recommendation for harmonization: SCL power flow direction 8.5.3 Recommendation for harmonization: CIM power flow direction 8.6 CIM Extensions for Distribution – Metering Model and Reading Types |
60 | 9 Real time data exchange mapping 9.1 Measurement identification 9.2 Common Data Class mapping Figure 14 – Signal identification as defined in IEC 61850-7-2 |
61 | 9.3 Common Data Class mapping to IEC 60870 and CIM Measurements Figure 15 – UML model of MV, DEL and WYE data classes |
62 | Table 17 – Mapping IEC 61850 Common Data Classes to IEC 60870information objects and CIM classes |
64 | 9.4 Common Data Class mapping to IEEE1815 and CIM 9.5 Data Attribute mapping 9.5.1 General Table 18 – Mapping IEEE1815 data point types to CIM classes |
65 | 9.5.2 Quality flag mapping Table 19 – Mapping IEC 61850 real time data attributes to CIM classes/attributes |
66 | 9.5.3 Non-real time measurement attribute mapping 9.5.4 Recommendation for harmonization: CIM measurement classes 10 Control Model 10.1 CIM Control Modelling 10.1.1 General Table 20 – Mapping IEC 61850 Non-real time data attributes to CIM classes/attributes |
67 | 10.1.2 Recommendation for harmonization: CIM control model Figure 16 – Current CIM Control Model |
68 | 10.1.3 Recommendation for harmonization: CIM CONTROL TYPES 10.2 Automated control sequences 11 Protection modelling Figure 17 – Proposal for revised CIM Control Model |
69 | Figure 18 – Present IEC 61970 Protection Model |
70 | 12 Communication model 13 Settings and attributes Table 21 – Mapping SCL Communication elements |
72 | Table 22 – Mapping IEC 61850 settings to CIM attributes |
82 | Annex A (informative)Use case details A.1 SCADA/EMS/DMS configuration from IEC 61850 SCL Description A.1.1 Name of use case A.1.2 Scope and objectives of use case A.1.3 Narrative of use case |
84 | A.1.4 General remarks A.2 Use case diagrams |
85 | Figure A.1 – Activity diagram part 1 – Create and review system specification description |
86 | Figure A.2 – Activity diagram part 2 – Create and review system configuration description |
87 | Figure A.3 – Sequence diagram |
88 | A.3 Technical details A.3.1 Actors: People, systems, applications, databases, the power system, and other stakeholders |
91 | A.3.2 Preconditions, assumptions, post condition, events A.3.3 References / Issues |
92 | A.3.4 Further Information on the use case for classification / mapping A.4 Step by step analysis of use case A.4.1 Pre-conditions |
93 | A.4.2 Steps – Normal |
95 | A.4.3 Steps – Alternative, error management, and/or maintenance/backup scenario |
96 | A.5 Information exchanged A.6 Common terms and definitions |
97 | Annex B (informative)Use case details B.1 Wide Area Monitoring, Protection and Control system (WAMPAC) for Transient stability B.1.1 Name of Use Case |
98 | B.1.2 Scope and objectives of use case |
105 | B.1.3 Narrative of use case |
107 | B.2 Use case diagrams |
108 | B.3 Technical details B.3.1 Actors: People, systems, applications, databases, the power system, and other stakeholders |
109 | B.3.2 Preconditions, assumptions, post condition, event B.3.3 References / issues |
110 | B.3.4 Further information on the use case for classification / mapping B.4 Step by step analysis of use case B.4.1 Overview of scenarios |
111 | B.4.2 Steps – Alternative, error management, and/or maintenance/backup scenario |
113 | B.5 Information exchanged |
117 | Annex C (informative)Recommendations C.1 Recommendations for IEC 61850 |
118 | C.2 Recommendations for CIM based standards, particularly IEC 61970-301 |
119 | C.3 Recommendations for joint working groups |
120 | Bibliography |