BS EN 61970-1-2006 Energy management system application program interface (EMS-API) - Guidelines and general requirements《能量管理系统应用程序接口(EMS-API) 指南和一般要求》.pdf

《BS EN 61970-1-2006 Energy management system application program interface (EMS-API) - Guidelines and general requirements《能量管理系统应用程序接口(EMS-API) 指南和一般要求》.pdf》由会员分享，可在线阅读，更多相关《BS EN 61970-1-2006 Energy management system application program interface (EMS-API) - Guidelines and general requirements《能量管理系统应用程序接口(EMS-API) 指南和一般要求》.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、 g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58(EMS-API) Part 1: Guidelines and general requirements The European Standard EN 61970-1:2006 has the

2、 status of a British StandardICS 33.200Energy management system application program interface BRITISH STANDARDBS EN61970-1:2006BS EN 61970-1:2006This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2006 BSI 2006ISBN 0 580 48967 1Cross-refe

3、rencesThe British Standards which implement international or European publications referred to in this document may be found in the BSI Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British

4、 Standards Online.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations.Summary of pagesThis document comprises a front c

5、over, an inside front cover, the EN title page, pages 2 to 41 and a back cover.The BSI copyright notice displayed in this document indicates when the document was last issued.Amendments issued since publicationAmd. No. Date CommentsA list of organizations represented on this committee can be obtaine

6、d on request to its secretary. present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK.National forewordThis British

7、 Standard is the official English language version of EN 61970-1:2006. It is identical with IEC 61970-1:2005.The UK participation in its preparation was entrusted to Technical Committee PEL/57, Power systems management and associated information exchange, which has the responsibility to: aid enquire

8、rs to understand the text;EUROPEAN STANDARD EN 61970-1 NORME EUROPENNE EUROPISCHE NORM May 2006 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B

9、- 1050 Brussels 2006 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 61970-1:2006 E ICS 33.200 English version Energy management system application program interface (EMS-API) Part 1: Guidelines and general requirements (IEC 61970

10、-1:2005) Interface de programmation dapplication pour systme de gestion dnergie (EMS-API) Partie 1: Lignes directrices et exigences gnrales (CEI 61970-1:2005) Schnittstelle der Anwendungsprotokolle von Energieverwaltungssystemen (EMS-API) Teil 1: Leitfaden und allgemeine Anforderungen (IEC 61970-1:2

11、005) This European Standard was approved by CENELEC on 2005-12-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 bibliograph

12、ical references concerning such national standards 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

13、 CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Icela

14、nd, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Foreword The text of document 57/777/FDIS, future edition 1 of IEC 61970-1, prepared by IEC TC 57, Power systems manage

15、ment and associated information exchange, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61970-1 on 2005-12-01. The following dates were fixed: latest date by which the EN has to be implemented at national level by publication of an identical national standard or by

16、 endorsement (dop) 2006-12-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2008-12-01 Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard IEC 61970-1:2005 was approved by CENELEC as a European Standard with

17、out any modification. _ EN 61970-1:2006 2 3 EN 61970-1:2006 CONTENTS INTRODUCTION 5 1 Scope 6 2 Normative References 6 3 Terms and definitions .6 4 System integration7 4.1 Integration scenarios .7 4.2 Integration considerations7 4.3 Component-based interfaces .10 4.4 Relationship to IEC 61968 series

18、 of standards.11 5 EMS-API reference model 12 5.1 General.12 5.2 Control center environment13 5.3 Application context 13 5.4 Application 13 5.5 Component14 5.6 Legacy application and wrappers.14 5.7 Component model .15 5.8 Component container 16 5.9 Component adapter .16 5.10 Component execution sys

19、tem 17 5.11 Middleware17 5.12 Communication profiles .18 5.13 Reference model examples18 6 EMS-API standards 20 6.1 General.20 6.2 CIM (IEC 61970-3XX)20 6.3 CIS (IEC 61970-4XX) 23 6.4 CIS technology mappings (IEC 61970-5XX) .24 7 General expected infrastructure functionality 24 7.1 General.24 7.2 Co

20、mponent Container25 7.3 Middleware26 7.4 Communication Profile Services 26 7.5 Utility-specific services 27 Annex A (informative) Component models28 Annex B (informative) Typical applications and functions .32 Annex C (informative) Utility issues with standard component models 37 Annex D (informativ

21、e) Examples of component execution systems and middleware products .39 Annex ZA (normative) Normative references to international publications with their corresponding European publications 41 Bibliography .40 EN 61970-1:2006 4 Figure 1 EMS-API Reference Model.12 Figure 2 EMS using EMS-API component

22、 standard interfaces 19 Table 1 Benefits of Component-based Interfaces .11 Table 2 Examples of EMS application contexts.13 Table B.1 Typical applications and functions 32 5 EN 61970-1:2006 INTRODUCTION This standard is part of the IEC 61970 series that defines application program interfaces (APIs) f

23、or an energy management system (EMS). This standard is based to a large extent upon the work of the EPRI Control Center API (CCAPI) research project (RP-3654-1). The principle objectives of the EPRI CCAPI project are to: reduce the cost and time needed to add new applications to an EMS or other syst

24、em1; protect the investment in existing applications that are working effectively; improve the capability to exchange information between disparate systems both within and external to the control center environment. The technical approach is to provide an integration framework for interconnecting ex

25、isting applications/systems that is based on a common architecture and information model; independent of the underlying technology. The principal task of the IEC 61970 series of standards is to develop a set of guidelines and standards to facilitate 1) the integration of applications developed by di

26、fferent suppliers in the control center environment2and 2) the exchange of information to systems external to the control center environment. The scope of these specifications includes other transmission systems as well as distribution and generation systems external to the control center that need

27、to exchange real-time operational data with the control center. Therefore, another related goal of these standards is to enable the integration of existing legacy systems as well as new systems built to conform to these standards in these application domains. The complete set of standards includes t

28、he following parts: Part 1: Guidelines and general requirements Part 2: Glossary Part 3XX: Common Information Model (CIM) Part 4XX: Component Interface Specification (CIS) Part 5XX: CIS Technology Mappings IEC 61970-1 provides a set of guidelines and general infrastructure capabilities needed for th

29、e application of the EMS-API interface standards. It describes the reference model that provides the framework for the application of the other parts of the EMS-API standards. This reference model is based on a component architecture, which places the focus of the standards on component interfaces f

30、or information exchange between applications in a control center environment. The model is also applicable to similar information exchanges between control center applications and systems external to the control center environment, such as other control centers, Independent System Operators (ISOs),

31、Regional Transmission Organizations (RTOs), and Distribution Management Systems (DMS). IEC 61970-1 also includes general capabilities for the integration infrastructure, which while not part of this standard, is expected to provide certain essential services to support the EMS-API interface standard

32、s. _ 1Ideally, an application should be installed on a system with minimal effort and no modification of source code; i.e., the way software packages are installed on a desktop computer. The EMS-API Project goal is to at least approach that ideal by reducing the often significant efforts currently r

33、equired to install third-party applications in an EMS. 2The control center environment includes traditional transmission control within a utility as well as the newer Independent System Operators (ISOs) and Regional Transmission Operators (RTOs), which are not affiliated with any one utility. EN 619

34、70-1:2006 6 ENERGY MANAGEMENT SYSTEM APPLICATION PROGRAM INTERFACE (EMS-API) Part 1: Guidelines and general requirements 1 Scope This part of the IEC 61970 series provides a set of guidelines and general infrastructure capabilities required for the application of the EMS-API interface standards. Thi

35、s part of the IEC 61970 series describes typical integration scenarios where these standards are to be applied and the types of applications to be integrated. A reference model is defined to provide a framework for the application of the other parts of these EMS-API standards. This reference model i

36、s based on a component architecture that places the focus of the standards on component interfaces for information exchange between applications in a control center environment. While the primary objective of the EMS-API is to support the integration of applications within the control center, the re

37、ference model is also applicable to information exchanges between control center applications and systems external to the control center environment, such as other control centers, ISOs, RTOs, and distribution systems. This standard describes the role of the other parts of the standard, including th

38、e Common Information Model (CIM) in the IEC 61970-3XX series, the Component Interface Specifications (CIS) in the IEC 61970-4XX series, and Technology Mappings in the IEC 61970-5XX series. This part of the IEC 61970 series also includes general capabilities that are needed by the integration infrast

39、ructure to facilitate the exchange of information via the component interfaces specified by the CIS. While the integration infrastructure itself is not part of this standard, it is expected to provide certain essential services to support the EMS-API interface standards. These services are enumerate

40、d in Clause 6. This part of the IEC 61970 series does not specify individual implementations or products, nor does it constrain the representation of information within a computer system application. This standard specifies the externally visible interfaces, including semantics and syntax, required

41、to support the interoperability of products supplied by different vendors. 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referen

42、ced document (including any amendments) applies. IEC 61970-2, Energy management system application program interface (EMS-API) Part 2: Glossary IEC 61970-301, Energy management system application program interface (EMS-API) Part 301: Common Information Model (CIM) base 3 Terms and definitions For th

43、e purposes of this document, the terms and definitions given in IEC 61970-2 apply. 7 EN 61970-1:2006 4 System integration 4.1 Integration scenarios Energy management systems are an assemblage of various software subsystems (SCADA, generation control, load forecast, etc.). The guidelines created for

44、this area (or portions thereof) apply to several different integration scenarios. This work recognizes that existing systems with their unique interfaces will need to evolve to use the interfaces specified in this work. The following different types of integration situations are envisaged. While the

45、se are typical scenarios, they are only a subset of the possible examples. a) Integration of applications developed by different suppliers into one homogenous system: In this scenario, independently developed application components (such as an Optimal Power Flow (OPF) are integrated into a system (w

46、hich includes supporting infrastructure). This allows the system integrator to more easily integrate an individual component into any system, whether it is an existing system or a newly developed system. b) On-line data exchange between separate systems: The control center needs to communicate with

47、other, separate systems within the corporation and between enterprises. Loosely coupled integration schemes are needed to exchange information. Examples include information exchanges with a DMS, the corporate accounting system, or another EMS. Enterprise integration scenarios generally fit into this

48、 category. c) Integration of separate systems sharing some engineering data: This corresponds to the situation where application packages from different vendors use partly overlapping engineering modeling data (such as the impedance of a line segment). d) Exchange of serialized data between the same

49、 applications in different systems: Limited integration can be achieved by using file transfer techniques. An agreed upon format is used for this type of export/import exchange. The use of File Transport Protocol (FTP) and an eXtensible Markup Language (XML)-based format file (or document) for the exchange of power sysem models is an example of this scenario. e) Developing a new application in a homogenous system: This corresponds to vendors or utilities