BS EN 61970-405-2007 Energy management system application program interface (EMS-API) - Generic eventing and subscription (GES)《能量管理系统应用程序接口(EMS-API) 通用事项记录和订阅(GES)》.pdf

《BS EN 61970-405-2007 Energy management system application program interface (EMS-API) - Generic eventing and subscription (GES)《能量管理系统应用程序接口(EMS-API) 通用事项记录和订阅(GES)》.pdf》由会员分享，可在线阅读，更多相关《BS EN 61970-405-2007 Energy management system application program interface (EMS-API) - Generic eventing and subscription (GES)《能量管理系统应用程序接口(EMS-API) 通用事项记录和订阅(GES)》.pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 02/01/2008 08:02, Uncontrolled Copy, (c) BSIg49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58(

2、EMS-API) Part 405: Generic Eventing and Subscription (GES)The European Standard EN 61970-405:2007 has the status of a British StandardICS 33.200Energy management system application program interface BRITISH STANDARDBS EN 61970-405:2007BS EN 61970-405:2007Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA S

3、TANDARDS, 02/01/2008 08:02, Uncontrolled Copy, (c) BSIThis British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 October 2007 BSI 2007ISBN 978 0 580 56439 0Amendments issued since publicationAmd. No. Date Commentscontract. Users are responsible for i

4、ts correct application.Compliance with a British Standard cannot confer immunity from legal obligations.National forewordThis British Standard is the UK implementation of EN 61970-405:2007. It is identical to IEC 61970-405:2007.The UK participation in its preparation was entrusted to Technical Commi

5、ttee PEL/57, Power systems management and associated information exchange.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a EUROPEAN STANDARD EN 61970-405 NORME EUROPENNE EU

6、ROPISCHE NORM September 2007 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2007 CENELEC - All rights of exploitation in any fo

7、rm and by any means reserved worldwide for CENELEC members. Ref. No. EN 61970-405:2007 E ICS 33.200 English version Energy management system application program interface (EMS-API) - Part 405: Generic Eventing and Subscription (GES) (IEC 61970-405:2007) Interface de programmation dapplication pour s

8、ystme de gestion dnergie (EMS-API) - Partie 405: Evnements gnriques et souscriptions (GES) (CEI 61970-405:2007) Schnittstelle fr Anwendungsprogramme fr Energiemanagementsysteme (EMS-API) - Teil 405: bermitteln von Ereignismeldungen (GES) (IEC 61970-405:2007) This European Standard was approved by CE

9、NELEC on 2007-09-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 stand

10、ards may be obtained on application to the Central Secretariat 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 noti

11、fied to the Central Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuani

12、a, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 02/01/2008 08:02, Uncontrolled Copy, (c) BSIForeword The text of document 57/888/FDIS, future editio

13、n 1 of IEC 61970-405, prepared by IEC TC 57, Power systems management and associated information exchange, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61970-405 on 2007-09-01. The following dates were fixed: latest date by which the EN has to be implemented at na

14、tional level by publication of an identical national standard or by endorsement (dop) 2008-06-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2010-09-01 Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard I

15、EC 61970-405:2007 was approved by CENELEC as a European Standard without any modification. _ EN 61970-405:2007 2 Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 02/01/2008 08:02, Uncontrolled Copy, (c) BSICONTENTS INTRODUCTION.5 1 Scope.6 2 Normative references .7 3 Terms and definitions .7 4

16、 Generic Eventing and Subscription (Normative)7 4.1 Overview .7 4.1.1 General .7 4.1.2 Suitability of the GES to the integration of a variety of application categories .8 4.1.3 Suitability of the GES to the integration beyond the control center.8 4.1.4 Suitability of the GES to the integration of ti

17、ghtly coupled and loosely coupled applications (informative) .9 4.2 Using GES A consequently, power system specific (CIM-based) event filtering tools can be used instead of generic event filtering tools. CIM-based event filtering provides for more familiar as well as more powerful and easy to use co

18、nfiguration management. Furthermore, since the GES API can be deployed independent of any application category specific information model, GES component interfaces do not need to be recompiled when an information model changes. Thus, application category information model changes can be handled via

19、declarative action rather than programmatic action. EN 61970-405:2007 10 Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 02/01/2008 08:02, Uncontrolled Copy, (c) BSI4.2 Using GES A GES Eventing does not include access to messaging-specific functionality such as message broker service QOS. How

20、ever, since GES Eventing is a component interface that is independent of what middleware is deployed between components, the lack of a messaging specific interface is appropriate. The JMS Publish/Subscribe model defines how components use JMS to publish and subscribe to messages related to a well-kn

21、own node in a content-based hierarchy. GES Eventing calls these nodes Areas and JMS calls these nodes topics. By relying on the area/topic as an intermediary, event/message publishers are kept independent of subscribers and vice versa. Many messaging service providers, such as MQSeries, group topics

22、 into hierarchies and provide various options for subscribing to parts of the hierarchy. GES Area strings consist of an array of area names (fully qualified pathnames) created as a result of navigating a hierarchical area map. Neither GES Eventing nor JMS places any restriction on what an area/topic

23、 object represents. It might be a leaf in a topic hierarchy or it might be a larger part of the hierarchy (for subscribing to a general class of information). Frequently, users like to see data organized in accordance with a well-known topic hierarchy. GES does not standardize the presentation of we

24、ll-known (e.g. CIM based) hierarchical views. IECTC57 Namespaces as described in IEC 61970-402 Common Services specification is used with GES in the same way that OPC Batch is used with OPC Data Access and OPC Alarms and Events by providing a means by which servers can present well-known hierarchica

25、l views. The use of the IECTC57 Namespaces together with the IArea/ICategory/IType (refer to Figure 7) interfaces provide the base for CIM-oriented subscription. Thus, GES with Common Services provide a standard mechanism for describing how CIM objects are ordered in a hierarchy as well as a way for

26、 components to use those hierarchies when setting up event (document) subscriptions. 4.2.4 Subscription filtering GES subscription filtering provides the ability to specify property values that are used to qualify a subscription. In SQL terms, this addition to the GES Filtering is equivalent to addi

27、ng a “where” clause. For example, a subscriber can indicate that it wishes to receive New Transformer Installation events as well as indicate that it only wants to receive New Transformer Installation events pertaining to transformers produced by a given manufacturer. A GES Subscription object (refe

28、r to Figure 7) maintains a filter specification set up by a client. The filter is used to specify what notifications shall be sent to the client. A server may support various filter functions and a client can ask the Subscription Home object what filter functions are supported. The subscription home

29、 is also used to create any number of subscription manger objects. Each subscription manger is associated with a client that has implemented callback object so that the server can send alarm and event notifications to the client. 4.2.5 GES Publish/Subscribe wildcards 4.2.5.1 General GES Eventing doe

30、s not support “wild card” functionality in topic subscription strings. For example, GES Eventing allows components to subscribe to events on the basis of event Category (e.g. “Transformer Installation Request”) or on the basis of topics (e.g. all work orders for breakers), but there is no facility t

31、o choose all areas at a given level. This specification extends GES Eventing with support for wildcards in topic based filtering. The GES Events interfaces are not changed in order to add support for wild cards in area paths. EN 61970-405:2007 12 Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS

32、, 02/01/2008 08:02, Uncontrolled Copy, (c) BSIThis specification requires a well-known URI for the wildcard. The URI for the wildcard is: http:/omg.org/schema/GES#WILDCARD 4.2.5.2 Example topic hierarchies (informative) To illustrate how subscription topic trees are used, consider a topic tree that

33、consists of a CIM containment model hierarchy as shown in Figure 3. An example area string created by navigating the above tree might be “IECTC57PhysicalModel/NorthArea/AirportSubstation”. In this case, a subscriber could receive all events that pertain to this topic including breaker, transformer,

34、and load-related events. However, if one wants to subscribe to breaker related events from all substations, then the GES requires that the user specifically includes the name of each substation node one may be interested in. This specification includes the added capability to create an area string (

35、array of area names) without having to manually navigate to every node on is interested in. Such a topic string may appear as “IECTC57 PhysicalModel/*/*/Breakers”. North Area Airport Sub Industrial Blvd SubBreaker 12 Load 22 Breaker 13 Transformer 33 Transformer 32 IECTC57Physical Model IEC 1324/07

36、Figure 3 Populated namespace example for IECTC57PhysicalModel (informative) 4.2.6 Browsing IECTC57 namespaces with GES 4.2.6.1 General IEC 61970-402 Common Services defines three trees or sub-trees used for topic based subscriptions: IECTC57PhysicalModel IECTC57ClassModel IECTC57ISModel IECTC57Physi

37、calModel contains subscription topic nodes representing the containment hierarchy of instances of CIM classes, for example control areas, substations, bays, breakers, etc. To browse this hierarchy, GES uses the IArea browse interface (refer to Figure 7). IECTC57ClassModel contains subscription topic

38、 nodes representing the class hierarchy of CIM classes, for example the Power System Resource class, AC Conducting Equipment class, Switch class, Breaker class, etc. To browse this hierarchy, GES uses the IType browse interface (refer to Figure 7). IECTC57ISModel contains subscription topic nodes re

39、presenting the hierarchy of events types. To browse this hierarchy, GES uses the ICategory interface (refer to Figure 7). Using OPC with GES, clients browse all subscription topic nodes with Area browsing by putting them into the same tree. The single OPC namespace tree may be divided into the three

40、 sub trees: IECTC57PhysicalModel, IECTC57ClassModel, and IECTC57ISModel. As data EN 61970-405:2007 13 Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 02/01/2008 08:02, Uncontrolled Copy, (c) BSIdescribing the properties is different depending on the sub-tree in question, the GES approach is t

41、o have sub-tree specific browsers returning data specific for the sub-trees, i.e. IArea and IType and ICategory (refer to Figure 7) for the IECTC57PhysicalModel, IECTC57ClassModel, and IECTC57ISModel topic trees respectively. Therefore, GES browsing does not required three sub trees. Using GES, IECT

42、C57PhysicalModel, IECTC57ClassModel, and IECTC57 ISModel are the roots of independent topic trees. 4.2.6.2 Mapping GES browsing to OPC browsing 4.2.6.2.1 General In order to compensate for the lack of native support for Resource IDs and Type in OPC, special properties shall be introduced into a GES

43、compliant OPC namespace. 4.2.6.2.2 Custom property required for Resource ID OPC differs from DAIS in that only names can be used to subscribe to events. In order to facilitate a consistent mapping from OPC to DAIS, every node in an OPC implementation of the IECTC57 Namespaces shall have a custom pro

44、perty defined named “Resource ID”. This property contains the value of the Resource ID for that object. The OPC Custom Property Index for this property shall be 10 000. The format of this property shall be an ASCII string representation of hex digits: xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx. 4.2.6.2.3 C

45、ustom property required for Resource Type OPC differs from GES in that only names can be used to subscribe to events. In order to facilitate a consistent mapping from OPC to GES, every node in an OPC implementation of the IECTC57 Namespaces shall have a custom property defined named “Resource ID”. T

46、his property contains the value of the Resource ID for that object. The OPC Custom Property Index for this property shall be 10 001. The value of this custom property for items in the IECTC57PhysicalModel shall be the same as GES Type in the IECTC57ClassModel. 4.2.6.2.4 Custom property required for

47、Type Resource ID OPC differs from GES in that only names can be used to subscribe to events. In order to facilitate a consistent mapping from OPC to GES, every node in an OPC implementation of the IECTC57PhysicalModel Namespace shall have a custom property defined named “Type Resource ID”. This prop

48、erty contains the value of the Resource ID for the type of that object. The OPC Custom Property Index for this property shall be 10 002. The format of this property shall be an ASCII string representation of hex digits: xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx. 4.2.6.2.5 Custom property required for Gene

49、ric Data Access Type OPC differs from GES in that only names can be used to subscribe to events. In order to facilitate a consistent mapping from OPC to GES, every attribute node in an OPC implementation of the IECTC57 Namespaces shall have a custom property defined named “Generic Data Access Type”. This property identifies the GDA Simple Value data type of the attribute. The OPC Custom Property Index for this property shall be 10 003. 4.2.6.2.6 Custom property required for Modelled OPC differs from GES in that only names can b