第三部分公用信息模型(CIM)(303).doc

标准分类号 备案号 D DL L 中中华华人人民民共共和和国国电电力力行行业业标标准准 D DL L T T X XX XX XX XX X 2 20 00 00 0 I Id dt t I IE EC C 6 61 19 97 70 0 3 30 03 3 1 19 99 99 9 能能量量管管理理系系统统应应用用程程序序接接口口 E EM MS S A AP PI I 第第 3 30 03 3 篇篇 公公用用信信息息模模型型 C CI IM M S SC CA AD DA A Energy Management System Application Program Interface EMS API Part 303 Common Information Model CIM SCADA 讨讨论论稿稿 200X XX XX 发布 200X XX XX实施 中华人民共和国国家经济贸易委员会 发布 DL T XXXXX 200X I 目目 次次 IEC 前前言言 II IEC 绪绪言言 III 1 范范围围 1 2 引引用用标标准准 1 3 定定义义及及缩缩写写 2 3 1 能量管理系统 EMS 2 3 2 应用程序接口 API 2 4 公公用用信信息息模模型型 CIM 规规范范 2 4 1 CIM 建模表示法 2 4 2 MODELLING PRINCIPLES 2 4 3 SCADA 3 4 3 1Measurements 4 4 3 2Structuring and naming of measurements 4 4 3 3SCADA specific 5 附附录录 A 用用于于控控制制中中心心应应用用程程序序接接口口用用的的公公用用信信息息模模型型 6 A 1 逻逻辑辑结结构构 6 A 1 1 概述 6 A 1 2 上下文环境 Context 6 A 2 包结构 PACKAGE ARCHITECTURE 7 A 2 1 SCADA 监视控制及数据采集 包 7 A 2 1 1 AccumulatorInput 累计量输入 类 7 A 2 1 2 AlarmGroup 报警组 类 8 A 2 1 3 AnalogInput 模拟量输入 类 9 A 2 1 4 CalculationParameter 计算参数 类 10 A 2 1 5 CommunicationLink 通信线路 类 10 A 2 1 6 Control 控制 类 11 A 2 1 7 CurrentTransformer 电流互感器 类 12 A 2 1 8 RTU 类 12 A 2 1 9 ScanBlock 扫描块 类 13 A 2 1 10 Setpoint 设定点 类 13 A 2 1 11 StatusInput 状态量输入 类 14 A 2 1 12 Telemetry 遥测 类 15 A 2 1 13 VoltageTransformer 电压互感器 类 16 DL T XXXXX 200X II I IE EC C 前前言言 1 ICE 国际电工委员会 是一个由所有的国家电工委员会 IEC 国家委员会 组成的世界性的 标准化组织 IEC 的目标是在电工和电子领域内所有的标准化问题上 促进国际间的合 作 为此目的以及一些其它的活动 IEC 出版了各种国际标准 标准的制订委托给技术 委员会 凡对该专题感兴趣的任一国家委员会均可参与此制订工作 凡与 IEC 有联系的 国际的 政府的和非政府的组织也可参与此先期工作 IEC 与国际标准化组 ISO 根据双 方协议达成的条件密切合作 2 由于每一个技术委员会中都有来自所有关心的国家委员会的代表 因此 IEC 在一些技术 问题上作出的正式决定或达成的协议均尽可能地表达了在有关论题上的国际协商一致性 3 所产生的文件以建议的形式供国际使用 并以标准 技术报告或导则的形式出版 正是 在这种意义上为各国家委员会接受的 4 为促进国际间的统一 IEC 的国家委员会要负责将 IEC 的国际标准最大限度地 不加变 动地在本国或本地区的标准之中应用 凡 IEC 标准与相应的国家或地区标准 中有差异之 处 均应在后者中指明 5 对于宣称符合 IEC 标准之一的任何设备 IEC 皆不提供标记程序 marking procedure 不会以此表示赞同 更不会对此负责 6 应注意 本国际标准的某些要素可能涉及到专利问题 对于标识此类专利权的一部或全 部 IEC 概不负责 国际标准IEC 61970 303由 IEC 第 57 技术委员会准备 电力系统控制和有关通信 本标准的文本以下列文件为基础 询问草稿投票表决报告 57 XXX CD57 XXX RVD 附录 A 是本标准整体的一部分 DL T XXXXX 200X III I IE EC C 绪绪言言 This standard is one of the IEC 61970 series which define an application program interface API for an energy management system EMS This standard is based upon the work of the EPRI Control Center API CCAPI research project RP 3654 1 and standards produced by OPC foundation The principle objectives of the EPRI CCAPI project are to Reduce the cost and time needed to add new applications to an EMS Protect the investment in existing applications that are working effectively in an EMS The principal task of the CCAPI Project is to develop a set of guidelines or specifications to enable the creation of plug in applications1 in the control center environment The task for OPC foundation is to provide standards for access of data provided by numerous data sources either industrial or electrical process devices or data bases having measurements This part of the standard IEC 61970 303 defines the SCADA logical view of the common information model CIM Part IEC 61970 301 defines the core elements and the logical view of the physical aspects of Energy Management System information Part IEC 61970 302 defines the financial and energy scheduling logical view The CIM is an abstract model that represents all the major objects in an electric utility enterprise typically contained in an EMS information model This model includes public classes and attributes for these objects as well as the relationships between them The CIM is part of the overall EMS API framework The purpose of the EMS API standard is to facilitate the integration of EMS applications developed independently by different vendors between entire EMS systems developed independently or between an EMS system and other systems concerned with different aspects of power system operations such as generation or distribution management This is accomplished by defining standard application program interfaces to enable these applications or systems to access public data and exchange information independent 1 A plug in application is defined to be a piece of software that may be installed on a system with minimal effort i e the way software packages are installed on a desktop computer The CCAPI Project goal is to at least approach that ideal by reducing the often significant efforts currently required to install third party applications in an EMS DL T XXXXX 200X IV of how such information is represented internally The CIM specifies the semantics for this API Other parts of this standard specify the syntax for the API The objects represented in the CIM are abstract in nature and may be used in a wide variety of applications The use of the CIM goes far beyond its application in an EMS This standard should be understood as a tool to enable integration in any domain where a common power system model is needed to facilitate interoperability and plug compatibility between applications and systems independent of any particular implementation DL T XXXXX XX 中华人民共和国电力行业标准中华人民共和国电力行业标准 能能量量管管理理系系统统应应用用程程序序接接口口 3 30 03 3 篇篇 公公用用信信息息模模型型 C CI IM M S SC CA AD DA A D DL L T T X XX XX XX XX X 2 20 00 00 0 I Id dt t I IE EC C 6 61 19 97 70 0 3 30 03 3 1 19 99 99 9 1 1 范范围围 This International Standard specifies a Common Information Model CIM which provides a logical view of the physical aspects of SCADA information within any enterprise that share SCADA data between applications This part of the CIM is an abstract model that represents all the major objects contained in a SCADA information model By providing a standard way of representing SCADA entities as object classes and attributes along with their relationships the CIM facilitates the integration of applications developed independently by different vendors between systems developed independently or between aSCADA system and other systems concerned with different aspects of power system or other industrial process operations This is accomplished by defining a standard information model to enable these applications or systems to exchange information independent of how such information is represented internally The object classes represented in the CIM are abstract in nature and may be used in a wide variety of applications This standard should be understood as a tool to enable integration in any domain where a SCADA information model is needed to facilitate interoperability and plug compatibility between applications and systems independent of any particular implementation The information model is intended to support API specifications for access of data described according to this information model Such APIs are the OPC foundation specifications the OMG Data Access for Iindustrial Systems DAIS specification and the IEC 61970 40 x specification 2 2 引引用用标标准准 下面的标准文档包含了各类条款 通过在本文的引用 构成了本国际标准的条文 在本标准 出版时 所指的版本是有效的 所有的标准文档都会修订 因此鼓励基于本国际标准的协议各 方调查应用下述标准化文档的最新版本的可能性 IEC 和 ISO 的成员维持目前有效的国际标准 的注册 目前还没有定义参考标准 Comment YunCQ1 页 2 Component 统一译为组件 和 61970 2 一致 DL T XXXXX XX 2 3 3 定定义义及及缩缩写写 对于一般的词汇定义 参考国际电工词汇表 IEC60050 在本国际标准中 应用附件 A 及下文 给定的术语和定义 3 3 1 1 能能量量管管理理系系统统 E EM MS S 一种计算机系统 包括提供基本支持服务的软件平台 以及提供使发电和输电设备有效运行 所需功能的一套应用软件 以便用最小成本保证适当的供电安全性 3 3 2 2 应应用用程程序序接接口口 A AP PI I 由可执行应用组件提供的公用函数集 供其他可执行应用组件使用 4 4 公公用用信信息息模模型型 C CI IM M 规规范范 4 4 1 1 C CI IM M 建建模模表表示示法法 CIM 用面向对象建模技术来定义 具体地说 CIM 规范使用统一建模语言 UML 表示法 它把 CIM 定义为一组包 CIM 中的每一个包包含一个或多个类图 用图形表示该包中的所有类及它们的关系 然后 根据每一个类的属性及其与其它类的关系 用文字形式定义各个类 UML 表示法在对象管理集团 OMG 的各种文档及几本已出版的书籍中叙述 4 4 2 2 M Mo od de el ll li in ng g p pr ri in nc ci ip pl le es s The CIM originally did not have much information about the origin of attributes or relations As IEC standards for sub parts of the CIM now are evolving there is a need to modularize the CIM such that each sub part contain relevant sets of class attribute and relation definitions Different ways to achive such modularization exist The one used here is to define sets of attributes specific for an application or usage The sets are defined as classes called mix ins The attributes defined by mix ins are inherited into the classes implementing the attributes The RWOs are typically inherits from mix ins The RWOs will then be extended with attributes originating from many different needs The idea with mix ins is graphically shown below DL T XXXXX XX 3 Application 2 Application N Application 1 Mixin class 1 1 Mixin class 1 2 Mixin class 1 N RWO class 1 Mixin class 2 1 Mixin class 2 2 Mixin class 2 N RWO class 2 Figure 1 Mix in application specific classes in RWO classes Figure 1 shows how mix in classes Mixin class 1 1 Mixin class 1 2 etc are inherited by different RWO classes 1 and 2 It also indicates how mix ins originates from different applications 1 2 and N The mix ins are dependent only on the RWO class definitions which becomes the spine in the model It is important to make the spine as small and simple as possible and let the complexity move into mix ins to create a modular and flexible model 4 4 3 3 S SC CA AD DA A S SC CA AD DA A 专专用用包包 This standard IEC 61970 303 contains entities to model information used by Supervisory Control and Data Acquisition SCADA applications Supervisory control supports operator control of equipment such as opening or closing a breaker Data acquisition gathers telemetered data from various sources The subtypes of the Telemetry entity deliberately match the OPC foundation specifications and IEC 61850 definitions The functionality and information model in a SCADA is generic and independent of the industrial process it supervises and controls This means a SCADA can be configured for a wide range of industrial processes like power transmission power generation power distribution water and sewage management oil and gas district heating pulp and paper DL T XXXXX XX 4 food manufacturing To manage a particular industrial process specific supervision and control systems are built on top of a SCADA For power transmission and generation such systems are called Energy Management Systems EMS and for power distribution Distribution Management Systems DMS In contrary to a SCADA the functionality and information model in a EMS or DMS is power system specific This means the objects appearing in an EMS DMS information model typically correspond to real equipment e g transformers transmission lines breakers etc and are described in other 61970 30 x series documents than this Information dealt with in this model is divided in a SCADA specific part relevant for the functionality found in a SCADA and generic part also described in the 61970 301 document relevant to both SCADA EMS and DMS The information is modeled in the three packages Measurements generic Structuring and naming of measurements generic SCADA specific 4 4 3 3 1 1M Me ea as su ur re em me en nt ts s Measurements are used to represent the state variables that can be found in industrial processes Each industrial process has it s specific types of measurements and a power system typically has power flows and voltages These measurements are analog In addition there are discrete measurements e g breaker positions and fault indications and counters e g energy accumulators The name Measurement indicates that the state variables are measured This is not nessecarily the case as many measurements are calculated in the SCADA or EMS DMS In an EMS there are several applications that calculate values for measurements e g State Estimation and Optimal Power Flow As a consequence a measurement may have a number of alternate values e g manually supplied telemetered state estimated optmized etc This means the measurement model is required to support alternate values comming from diffrent sources as the original CIM does 4 4 3 3 2 2S St tr ru uc ct tu ur ri in ng g a an nd d n na am mi in ng g o of f m me ea as su ur re em me en nt ts s In a SCADA measurements are usually hierarchically organized The hierarchical structure is often used for naming of measurements and is a convenient way to identify and find particular measurements A measurement name is then constructed from the object names found traversing the path from the measurement to the root of the hierachy It is common to have measurements as part of the equipment it measures The actual equipment is different for different industrial processes but from a SCADA perspective the type of the objects representing the equipment does not matter What matters is the way the objects are organized as this is important for the measurement naming provided hierachy based naming is used For this reason the information model in this document is based on typeless objects that can be freely organized in hierarchical structures Objects modelling process equipment are called Real World Objects RWO The RWOs is a more generic representation of the PowerSystemResource defined in 61970 301 According to the 1346 1 standard the following names are defined single level designation the name private to a RWO disregarding it s position in a hierarchical structure multi level designation the name corresponding to the collection of single level designations found in the path from the RWO to the root of the hierarchy The multilevel designation then is very similar to a file path or a URI Uniform Resource Identifier DL T XXXXX XX 5 An EMS or DMS deals with equipment that is specific to the industrial process e g power transformers transmission lines breakers etc The RWOs then becomes specialized to this equipment For a power system the first level of specialization is the PowerSystemResource The flexible structuring supported by the SCADA RWO model then becomes highly restricted From a SCADA point of view it is legal create any structure of RWOs From the power system view found in an EMS or DMS it does not make sense to create a breaker containg a transmission line many more meaningless examples can be imagined For this reason the 61970 301 standard contains an explicit model of the structure composition rules allowed NOTE it is assumed the PowerSystemResource self relating MemberOf relation is removed as it violates the composition rules 4 4 3 3 3 3S SC CA AD DA A s sp pe ec ci if fi ic c This package contains information supporting functions performed in a SCADA Functions typically are communication e g RTU and inter center process data handling e g scaling limit supervision gradient supervision etc event and alarm handling historical and trend data recording control HMI For SCADA and remote communication a number of different standards exist e g IEC 61850 7 for utility substation communication IEC 60870 6 TASE 1 TASE 2 for intercenter communication IEC 870 5 101 for RTU communication This standard is intended not to interfere with these communication standards and for this reason all information related to the communication sub system is deliberatly left out There is however an overlap between information models used in the communication standards above and this standard is to some extent harmonized with the others and where an harmonization is not possible a crossrefernce is included NOTE The mapping and harmonization is not complete More work to do here Comment REPEAT2 Rose ClassDiagram MDLfilename ccapi mdl CategoryName Logical x 20View DiagramName Main DL T XXXXX XX 6 附附录录 A A 用用于于控控制制中中心心应应用用程程序序接接口口用用的的公公用用信信息息模模型型 标标准准的的附附录录 A A 1 1 逻逻辑辑结结构构 A A 1 1 1 1 概概述述 公用信息模型 CIM 代表了一个综合的 EMS 信息的逻辑示图 其定义包括了公共的类及属性 以及其相互关系 A A 1 1 2 2 上上下下文文环环境境 C Co on nt te ex xt t CIM 分割成若干子包 参考 1 中的域包 Domain Package 定义了用于其他包的数据类型 包中的类是按字母排顺序列出的 类的固有属性先列出 继承的属性列于其后 每一类中固有的关 连先列出 继承的关连列于其后 根椐参与关连的各个类的作用对关连进行了描述 对聚合性仅在 该作用包含聚合时才列出 下图表示出最高层次的包及它们间的依赖关系 Generation Domain WiresLoadModel Core Meas Topology Outage ProtectionFinancialEnergy Scheduling Reservation SCADA 图 A 1 CIM 最高层次的包 每一包中每一类的模型信息均完全描述 固有属性及继承属性的属性信息列表格式如下 属属性性名名 Attribute Name 属属性性类类型型 Attribute Type 属属性性文文档档 Attribute Documentation 域包中的类包括一个属性类型的度量单位选项 关连 Association 则是按参与关连的类的作用而列出的 对固有作用及继承作用的信息列 表格式如下 Comment REPEAT3 Rose ClassCategory MDLfilename ccapi mdl CategoryName SCADA Comment REPEAT4 Rose ClassDiagram MDLfilename ccapi mdl CategoryName SCADA DiagramName Main Comment REPEAT5 Rose Class MDLfilename ccapi m dl ClassName AccumulatorInput DL T XXXXX XX 7 本类基数集 作用名 对侧类基数集 对侧类名作用文档 CardinalityFrom Role Name CardinalityTo Role ToClass Name 本类基数集 是指所描述的类的多值性 值 指任选的关连 值 n 表示允许关连的数目不定 对侧类基数集 表示关连中另一侧类的多值性及基数 A A 2 2 包包结结构构 P Pa ac ck ka ag ge e A Ar rc ch hi it te ec ct tu ur re e A A 2 2 1 1 S SC CA AD DA A 监监视视控控制制及及数数据据采采集集 包包 包含了用于 SCADA 的建模信息的实体 监视控制支持操作员对设备控制 如合断一个开关 数据采集则从不同数据源采集遥测数据 遥测实体 Telemetry entity 的子类与 UCA 及 IEC61850 的定义完全匹配 这一包也支持告警表达 但是它并不是打算给其它应用使用的 PowerSystemResource from Core OperatedBy 0 StatusInput Operates 0 OperatedBy 0 AccumulatorInput Operating 0 Control 0 0 OperatedBy 0 0 OperatedBy MemberOf 0 Contains 0 CommunicationLink Operates 0 Setpoint OperatedBy 0 MemberOf 1 Contains 1 1 RTU 0 0 MemberOf SuppliesSignalFor 0 CTSignalSuppliedFrom 0 SuppliesSignalFor 0 VTSignalSuppliedFrom 0 AnalogInput 0 0 OperatedBy MemberOf 0 Contains 0 1 ScanBlock 1 1 1 MemberOf SignalForCT 0 1 DerivesSignalFrom 0 CurrentTransformer 0 0 SuppliesSignalFor SignalForVT 0 1 DerivesSignalFrom 0 VoltageTransformer 0 0 SuppliesSignalFor AssociatedWith 0 1 Telemetry 0 0 1 MemberOf DataSourceFor 0 1 Contains 0 1 MemberOf 0 CalculationParameter SetContains 0 MemberOfSet 0 Measures 0 MeasuredBy 0 1 PowerSystemResource from Core MeasuresTerm 0 MeasuredBy 0 1 Terminal from Core 0 1 0 DerivesSignalFrom 0 1 0 DerivesSignalFrom Contains 0 AlarmGroup MemberOf 1 MemberOf 1 MeasurementValue from Meas 0 1 0 1 DataSourceFor 0 1 0 MemberOf Contains 0 1 Measurement from Meas 0 0 MemberOf 0 0 1 MeasuredBy 0 0 1 MeasuredBy 0 1 MemberOf 1 0 1 MemberOf 图 A 2 SCADA 主包 A A 2 2 1 1 1 1 A Ac cc cu um mu ul la at to or rI In np pu ut t 累累计计量量输输入入 类类 脉冲计数器测量装置 在装置中保留有一个数 被加数 将其与另一数 加数 相加 用总 和取代被加数 从从Telemetry 遥遥测测 中中派派生生 AccumulatorInput 累累计计量量输输入入 的的属属性性 固固有有属属性性 Comment REPEAT6 Rose Attribute MDLfilename ccapi m dl AccumulatorInput Class maxAc cumCount Comment REPEAT7 Rose Class MDLfilename ccapi m dl ClassName Telemetry Comment REPEAT