Bsi bs en 61970 453 2014

NORME EUROPÉENNE English Version Energy management system application program interface EMS-API - Part 453: Diagram layout profile IEC 61970-453:2014 Interface de programmation d'appli

BSI Standards Publication

application program interface (EMS-API)

A list of organizations represented on this committee can be obtained onrequest to its secretary.

This publication does not purport to include all the necessary provisions of

a contract Users are responsible for its correct application

© The British Standards Institution 2014.Published by BSI Standards Limited 2014ISBN 978 0 580 80258 4

NORME EUROPÉENNE

English Version

Energy management system application program interface

(EMS-API) - Part 453: Diagram layout profile (IEC 61970-453:2014)

Interface de programmation d'application pour système de

gestion d'énergie (EMS-API) -

Partie 453: Profil de disposition du diagramme

(CEI 61970-453:2014)

Schnittstelle für Anwendungsprogramme für Netzführungssysteme (EMS-API) - Teil 453: Diagramm Entwurfsprofile (IEC 61970-453:2014)

This European Standard was approved by CENELEC on 2014-04-01 CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CENELEC member

This European Standard exists in three official versions (English, French, German) A version in any other language made by translation

under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the

same status as the official versions

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,

Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,

Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,

Turkey and the United Kingdom

European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels

© 2014 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members

Ref No EN 61970-453:2014 E

Foreword

The text of document 57/1409/FDIS, future edition 2 of IEC 61970-453, prepared by IEC/TC 57,

"Power systems management and associated information exchange" was submitted to the CENELEC parallel vote and approved by CENELEC as EN 61970-453:2014

IEC-The following dates are fixed:

• latest date by which the document has

to be implemented at national level by

publication of an identical national

standard or by endorsement

(dop) 2015-01-01

• latest date by which the national

standards conflicting with the

document have to be withdrawn

(dow) 2017-04-01

This document supersedes EN 61970-453:2008

EN 453:2014 includes the following significant technical changes with respect to EN 453:2008:

61970-a) The SVG elements and its data model have been replaced by the Diagram Layout Package, which

is now an integral part of the IEC 61970-301 (CIM) model

b) The exchange is in accordance with and is a part of the IEC 61970 profile concept

c) A glue point object has been introduced to model explicit connections between graphics elements Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent rights

IEC 61968-11 NOTE Harmonised as EN 61968-11

IEC 61970-1 NOTE Harmonised as EN 61970-1

IEC/TS 61970-2 NOTE Harmonised as CLC/TS 61970-2

IEC 61970-452 NOTE Harmonised as EN 61970-452

IEC 61970-301 - Energy management system application

program interface (EMS-API) - Part 301: Common information model (CIM) base

EN 61970-301 -

IEC 61970-501 - Energy management system application

program interface (EMS-API) - Part 501: Common Information Model Resource Description Framework (CIM RDF) schema

EN 61970-501 -

IEC/TR 62541-1 - OPC unified architecture -

Part 1: Overview and concepts CLC/TR 62541-1 -

CONTENTS

INTRODUCTION 6

1 Scope 7

2 Normative references 7

3 Terms and definitions 7

4 Use Cases 8

4.1 General use cases for diagram exchange 8

4.2 Simple bay diagram example 10

5 Diagram layout exchange profile 12

5.1 General 12

5.2 Diagram layout profile classes 13

5.2.1 General 13

5.2.2 Diagram 14

5.2.3 DiagramObject 14

5.2.4 DiagramObjectGluePoint 15

5.2.5 DiagramObjectPoint 15

5.2.6 DiagramObjectStyle 16

5.2.7 TextDiagramObject 16

5.2.8 VisibilityLayer 17

5.2.9 Abstract classes – IdentifiedObject 17

5.2.10 Enumerations – OrientationKind 18

6 Graphical rendering 18

6.1 General 18

6.2 Single point objects 18

6.3 Multiple point objects 19

6.4 Gluing points 20

6.5 Diagram object style 21

6.6 Diagram layout exchange process 21

7 Examples 23

7.1 Data instantiation and encoding 23

7.2 Simple bay example use case 25

Annex A (informative) Benefits and format conversion from IEC 61970-453 Edition 1 to Edition 2 27

Bibliography 28

Figure 1 – System overview 9

Figure 2 – Bay diagram as rendered 10

Figure 3 – Bay diagram drawn in GIS style 11

Figure 4 – Bay diagram drawn in SCADA style 12

Figure 5 – Diagram layout information model 13

Figure 6 – Conventions used for representing object instances and associations 18

Figure 7 – Single point diagram objects 19

Figure 8 – Multiple point diagram objects 20

Figure 9 – Disconnector with glue point 20

Figure 10 – Disconnector and breaker with glue points 21

Figure 11 – Profiles within IEC standards 22

Figure 12 – Disconnector diagram object instantiation 23

Figure 13 – IEC 61970-552 Encoding for disconnector diagram data 24

Figure 14 – Bay diagram example with objects outlined GIS style 25

Figure 15 – Bay diagram example with objects outlined SCADA/EMS style 26

Common Information Model (CIM) Base

This standard is one of the IEC 61970-4x series that define utility control centre component interface specifications (CIS4) IEC 61970-4x specifies the functional requirements for interfaces that a component (or application) shall implement to exchange information with other components (or applications) and/or to access publicly available data in a standard way The component interfaces describe the specific message contents and services that can be used by applications for this purpose The implementation of these messages in a particular technology is described in the IEC 61970-5x series

Energy Management Systems employ a variety of schematic and quasi-geographic presentations in their user interfaces These are sometimes generated automatically, but more often are hand-drawn and require considerable labour to create and maintain Most of this labour goes into the arrangement, or ‘layout’ of the power system elements within the overall diagram When network models are exchanged, as defined in IEC 61970-452 and IEC 61968-13 standards, it is desirable to be able to exchange these layouts

IEC 61970-453 specifies guidelines for the exchange of diagram layout information for schematic data that is encoded using IEC 61970-552

_

1 Footnote 1 applies to the French version only

2 Footnote 2 applies to the French version only

3 Footnote 3 applies to the French version only

4 Footnote 4 applies to the French version only

ENERGY MANAGEMENT SYSTEM APPLICATION

PROGRAM INTERFACE (EMS-API) – Part 453: Diagram layout profile

1 Scope

This part of IEC 61970 is a member of the IEC 61970-450 to 499 series that, taken as a whole, defines, at an abstract level, the content and exchange mechanisms used for data transmitted between control centre components

Included in this part of IEC 61970 are the general use cases for exchange of diagram layout data, and guidelines for linking the layout definitions with CIM data Guidelines for management of schematic definitions through multiple revisions are also included

2 Normative references

The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application For dated references, only the edition cited applies For undated references, the latest edition of the referenced document (including any amendments) applies

IEC 60050, International electrotechnical vocabulary

IEC 61970-301, Energy management system application program interface (EMS-API) –

Part 301: Common information model (CIM) base

IEC 61970-501, Energy management system application program interface (EMS-API) –

Part 501: Common Information Model Resource Description Framework (CIM RDF) schema

IEC/TR 62541-1, OPC Unified Architecture – Part 1: Overview and concepts

3 Terms and definitions

For the purposes of this document, the terms and definitions given in IEC 60050, as well as the following, apply

3.1

instance of a class that models a Real-World Object6 with a unique identity

Note 1 to entry: A domain object inherits from a CIM IdentifiedObject A domain object is normally not a diagram

5 Footnote 5 applies only to the French version

6 Footnote 6 applies only to the French version

7 Footnote 7 applies to the French version only

Note 1 to entry: The diagram is an identified container for the diagram objects Examples of diagrams include substation schematics, transportation or distribution network orthogonal schematics, or pseudo-geographical schematics A diagram has a well-defined coordinate space

3.3

representation of domain objects or static background

Note 1 to entry: The diagram is composed of diagram objects

Note 2 to entry: An example for domain objects includes breakers An example for static background object includes lakes

3.4

diagram object style

definition of how to render diagram objects possibly based on the state of domain objects

Note 1 to entry: Typically, the diagram object style is resolved in a very specific way for each system

4 Use Cases

4.1 General use cases for diagram exchange

Figure 1 shows a high-level view of using diagram layout data exchange with potential systems that can make use of the diagram layout data

_

8 Footnote 8 applies to the French version only

Figure 1 – System overview

An examination of the use cases for such exchanges revealed that the diagrams being exchanged are not fixed graphic presentations Instead the diagrams vary considerably in appearance as attributes of CIM objects change, and they support important user interaction For example, a SCADA one-line in its creator’s system is supporting live control of the power system, while in a receiver’s system it is merely used for reference so that a neighbour can understand what the system looks like beyond its own border These variations are typically not easy or appropriate to map between the source and receiving systems because of the degree of difference in the way those systems are designed

In the specification of diagrams, one common element is that the style of displaying an object

of a certain kind is usually defined once and then re-used, but the placement of objects must

be adjusted whenever new elements are added to the data model This placement and maintenance of placement is where most of the labour investment takes place that users would like to preserve As a result, this standard is limited to the exchange of diagram layouts (meaning the arrangement of CIM objects in a display space) rather than a complete exchange of all characteristics of a graphic presentation

With this proposed standard, instead of maintaining duplicate schematics for different applications, the schematics are exported by one system and imported by the other system Diagram layout profile is an extension to the CIM power system model exchange IEC 61970-

452, and will be orchestrated along with the existing CIM XML model exchange and updates provided using the existing CIM XML Incremental file format as defined in IEC 61970-552 IEC 61970-552 also describes how payload headers provide information as to how payloads fit together

IEC 0423/14

This process can be applied for initial schematics construction as well as for continuous maintenance

The importing system can create its graphics displays from the imported data, or the diagram layout data can serve as additional documentation and means of understanding for the domain data exchange

4.2 Simple bay diagram example

Diagrams are constructed using different approaches This subclause illustrates this using a simple bay drawing Figure 2 shows a typical representation of a bay

Figure 2 – Bay diagram as rendered

In a GIS system, lines are typically drawn up to the centre point of the symbol This is shown

in Figure 3 (transparent symbol is used for illustration) This construction method is independent if the symbol size, i.e the drawing looks “pretty” even when the importing system used a smaller symbol size than the original one

IEC 0424/14

Figure 3 – Bay diagram drawn in GIS style

In a SCADA system, lines are typically drawn to align with the terminals of the object represented by the symbol This is shown in Figure 4 (transparent symbol is used for illustration) This construction method gives a closer representation of the electrical topology, but depends on a certain symbol size

IEC 0425/14

Figure 4 – Bay diagram drawn in SCADA style

5 Diagram layout exchange profile

5.1 General

Profile namespace: http://iec.ch/TC57/61970-453/DiagramLayout/2#

This standard specifies an exchange profile for schematics with the following characteristics

• A generic method for linking the diagram object to the domain data Domain data and diagram layout data can be exchanged together with the domain data, or separately from each other with the assumption that domain data will have already been imported should diagram layout data be imported separately

• It does not require or imply a specific domain data format Therefore, it supports domain data modelled according to the IEC 61970-301 Common information model (CIM) that is exchanged in the IEC 61970-501 format (CIM RDF schema) Diagram layout data

references domain data in compliance with IEC/TR 62541-1, OPC Unified Architecture)

• The intended usage of this standard is that the source of a diagram will use the standard

to encode the layout of their diagram as they created it It is then incumbent upon any receiver to supply the means of using that diagram layout in their system

– In the simplest situation, if the source uses Switch object placements, the receiver creates a generic Switch template in the receiver’s system that will be used to render Switches (i.e there is no exchange of Switch templates)

– In more complex situations, a 1:1 correspondence may not be desirable, and receivers may have to create generic transformations in order to use exchanges

– However, in both situations, it is expected that once an investment is made in a strategy for rendering, repeated imports may be carried out automatically

• Supports the exchange of diagram objects that have no relationship to domain data, i.e., pure static background objects

IEC 0426/14

• Supports multiple representations of the same domain object in the same or different diagrams

• Allows the diagram to be used as the unit of exchange, providing a straightforward approach to partial exchange, or an exchange between systems that have a separate model and repository for diagram layout data

• Supports assignment of diagram objects to layers or other means, for showing or hiding information based on zoom level and/or user interest

• A generic method for proprietary extensions to enable full round tripping (export and import back into the same system) without information loss within a system, and without breaking the standard exchange format

5.2 Diagram layout profile classes

The diagram layout classes are a part of IEC 61970-301 and as such are associated to the domain data using the standard UML association relationship A new sub-package in IEC 61970-301 contains the classes required for expressing schematic data for domain objects as illustrated in Figure 5

Figure 5 – Diagram layout information model

IEC 0427/14

5.2.2 Diagram

The Diagram represents the diagram being exchanged The initialView attributes can be used

to specify an initial view with the x,y coordinates of the diagonal points The coordinate system is a standard Cartesian coordinate system and the orientation attribute defines a positive or negative orientation A positive orientation gives standard “right-hand” orientation, with negative orientation indicating a “left-hand”; orientation For 2D diagrams, a positive orientation will result in X values increasing from left to right and Y values increasing from bottom to top A negative orientation gives the “left-hand”; orientation (favoured by computer graphics displays) with X values increasing from left to right and Y values increasing from top

to bottom

orientation 0 1 OrientationKind The Diagram represents the diagram being

exchanged The initialView attributes can be used to specify an initial view with the x,y coordinates of the diagonal points The coordinate system is a standard Cartesian coordinate system and the orientation attribute defines a positive or negative orientation x1InitialView 0 1 Float X coordinate of the first corner of the initial view

x2InitialView 0 1 Float X coordinate of the second corner of the initial view y1InitialView 0 1 Float Y coordinate of the first corner of the initial view

y2InitialView 0 1 Float Y coordinate of the second corner of the initial view

mRID 0 1 String see IdentifiedObject

name 0 1 String see IdentifiedObject

The DiagramObject class defines an object that defines one or more points in a given space

This object can be associated with anything that subclasses IdentifiedObject in

IEC 61970-301