IEC61970/61968 CIM v15 模型

WG13 CIM15 Issues and Update Report

Updated 2011-096-0420

Added new issues dated after 2011-06-042/10/2011, and newly closed issues

1 Introduction

This document summarizes the CIM issues and changes for CIM 15 up to the document

date. Included are changes from IEC 61970 CIM14 to the current working draft of

CIM15 listed under Referenced Documents.

Change tracking is contained in the Microsoft Word version of this document from the

 [4] White paper describing distribution and transformer network model changes

“TransmissionDistributionTransformer and CutsJumpers vx.doc” (Now

incorporated into IEC61970-301 Ed 5 draft

 [5] iec61970-301r2927_iec61970cim15v3223.docx

 [6] iec61970cim15v32_iec61968cim11v13_iec62325cim01v07cim15v28-

changes.docx

3 Process for Content of this Document

This document was created to reflect all open issues in the referenced issue spreadsheet.

Each open issue appears one time in this document under one category that most closely

represents the issue. As issued are closed they will remain in this document and be

assumed all changes for CIM15 are based on the release of CIM14v15 as the official

CIM14 release.

Highlights of changes include:

 Object naming supports any number of alternate names for an IdentifiedObject.

 Several ENTSO-E related issues from the latest IOP July 2010.

 Common transmission and distribution network models. This has been a

collaborative work with WG14 that made major contributions.

 Revised phase shifter model that has been collaborative work with ENTSO-E

members that contributed the model.

 Inclusion of dynamics package from the EPRI sponsored CIM for dynamics

develop the CIM it is important to focus on real needs and create focused projects

that develop the CIM. Having lots of unresolved issues take management

resources. Hence it is better to close and reopen when there is a real need for a

solution. Once an actual need for a solution exists the issue will be revisited.

The object naming change breaks usages of localName, pathName and description

attributes that has been moved to a new naming model. However,

IdentifiedObject.aliasName is kept for backwards compatibility. It is recommended to

move to the new name data model.

The addressed ENTSO-E issues are listed in sections 4.1.20. Not yet solved issues are

listed in section .

 TransformerWinding is renamed to TransformerEnd and inherits IndetifiedObject.

Hence it becomes a part of the power transformer only.

 The new model describes both the star impedance model used in transmission and

the meshed impedance model used in distribution.

 Distribution transformers may consist of multiple transformer tanks. The new

class TransformerTank describes this.

 The test report classes has been moved to assets package.

The issue 13_2 phase shifter model change is not backwards compatible. The changes

introduce new classes with attributes relevant to the tap changer type. The change is

described in [4].

With the inclusion of the CIM for dynamics the ratedS attribute was moved from

1020200.”

This standard model reference document can be found in the WG13/Working

Documents/CIM for Dynamic Models – EPRI Project folder on the WG13 SharePoint

site. This document can be freely distributed.

For future versions of the dynamics model this may be refactored by creating base classes

having common attributes.

Issues Closed in CIM 15

4.1.1 Display layouts for exchange

This is the follow-up to the “paper interop” that occurred in January 2008 in San Jose.

The main point would be to support the exchange of display layouts without the

 798 - change attribute name TiePoint.tiePointMWRating to PowerRating

 800 - change attribute name congestChargeMax to maxCongestCharge

 805 -enumeration name is the same as the attribute name in

HostControlArea.controlAreaMode

4.1.3 Data types and Unit Symbols

The following section contains data type issues

 621 Purpose of class Unit class? Replace with UnitSymbol?

 622 Labels should use / or “per” consistently

 627 Introduce a new UnitSymbol (m3/s).

 693 Several Curve/Schedule classes have in their docs reference to units...

 776 BasicIntervalSchedule cannot handle currency type units

 777 - Move Unit to MEAS package since specific to MEAS.

 779 – document AbsoluteDate better/differently

 782 – Rename KWActivePower to KiloActivePower

 792 - change type of HydroPump.pumpDischAtMinHead

 795 - change type of HydroPowerPlant.plantDischargeCapacity

 796 - change type of HydroGeneratingUnit.hydroWaterCost

 797 - New datatype : CostPerVolume and a new Enumeration

MonetaryAmountPerVolume

 801 - needs to introduce a generic Rate datatype

 802 - needs to introduce a new datatype and a new enumeration to take care of

time interval

 806 - FreqBiasFactor type for HostContolArea.frequencyBiasFactor is missing

 813 - description in Domain package and in 301 document is out of date

regarding multiple attributes and Rose specifics

 1311 - Rename <<Datatype>> stereotype to <<CIMDatatype>>

 c-054 – Decimial primitive

 c-056 – new interval compounds for Date and Time

 c-057 – Change Money value to Decimal

 13_47 - Length unitMultipler should not be const (ToClose)



4.1.4 Load modeling

The load model has been revised considerably in CIM 12, but there are still lsome issues

related to it

 287 Station supply\

4.1.5 Generation Modeling

This group contains the following issues

 265 - Remote Control switch.

 390 - The following attributes lacks documentation...

 804 - missing doc EnergyTransaction.Reason

 807 - missing doc for Reserve

 808 - missing doc for TieLine

 c-042 – Documenation for class BaseVoltage



4.1.7 Object hierarchy, naming and identification

This group contains the following issues