cim model manager report

© Siemens Energy, Inc. 2008Energy Automation

CIM ModelManager Report

Kurt HunterCIM Users Group Meeting

13 May 2009

Copyright © Siemens Energy, Inc. 2008. All rights reserved.

CMM Report

Topics

o Background

o Responsibilities of CIM Model Manager

o WG 13 CIM Roadmap

o CIM Issues Process

o CIM Versioning

o Recent CIM Changes

o CIM Priorities for 2009


CMM Report Background

Background

o Prior to the formation of the CIM Users Group in 2005, the CIM UML model was passed between volunteers from WG 13 and 14 to make necessary changes

o To assist with the establishment of the CIM Users Group, Siemens, ABB, and Areva agreed to fund the position of CIM Model Manager for the first three years.

2006 - Kurt Hunter, Siemens 2007 – Lars-Ola Osterlund, ABB 2008 – Kendall Demaree, Areva

o For 2009, Siemens agreed to fund the position again.


CMM Report Responsibilities of CIM Model Manager

Responsibilities of CIM Model Manager

o Manage and maintain the integrated CIM UML model

o Coordinate model changes with WG 14 and WG 16

o Manage the CIM issues list

o Facilitate WG 13 Issues discussions

o Produce the IEC 61970-301 document

o Assist CIM UG in answering questions from users

o Report to WG 19 and other IEC working groups


CMM Report WG 13 CIM Roadmap

WG 13 CIM Roadmap

o WG 13 Part 301 is on a yearly release cycle.

o WG 13 CIM Roadmap provides an overview of planned and completed CIM UML model changes.

o Serves as the main driver, in addition to CIM issues, behind changes to the CIM UML model.



Version 12 13 14

Profile

Draft May 2007 May 2008 May 2009

Test IOP10

September 2007

IOP11

September 2008

IOP12

September 2009Release Q1 2008 Q1 2009 Q1 2010

Addressed

Issues

SI units

Data type system

Control model

Load model

Equivalents model

Other minor changes

OWL meta data

Multiple inheritance

Tools

CIM Issues

CIM for planning

ERCOT issues

CIM Issues

2008 WG 13 CIM Roadmap



Version 13 14 15

Profile

Draft June 2008 May 2009 May 2010

Test IOP

October 2008

IOP

September 2009

IOP

September 2010Release Q1 2009 Q1 2010 Q1 2011

Addressed

Issues

OWL meta data

Tools, EA transition

CIM Issues

CIM for planning

ERCOT issues

Operational limits

61968 integration

Dynamics Models

DC models

CIM Issues

Multiple inheritance

Datatypes

OWL meta data

Solution exchange

CIM Issues

Contextual models

2009 WG 13 CIM Roadmap



Typical Yearly Cycle Plan


CMM Report CIM Issues for 2009

CIM 2009 Yearly Cycle

2009

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

2010

CPSMInteroperability

Test

DynamicsInteroperability

Test

UCTEInteroperability

Test

Finalize UMLAnd

Produce CIM 14Release

Resolve Issues fromInteroperability Tests


CMM Report CIM Issues Process

CIM Issues

UML Model andProfile Changes

InteroperabilityTests


CMM Report CIM Issues Process

CIM Issues Process consists of three primary components:

o Issues Submission

o Issues Resolution

o Issues Tracking


CMM Report CIM Issues Process - Submission

CIM Issues Submission

o In the past issues have been written second hand from information in emails, discussions at Interop Tests, etc.

o Consequently, issues that could not be resolved quickly are frequently difficult to interpret when coming back to them.

o Currently requiring issues to be written by the submitter, preferably using the CIM Users Group website.



CIM Users Group Website:http://cimug.ucaiug.org



Model Issues Summary



Submitting a New Issue



New Issue Submission Form



Tips for CIM Issues Submission

o Be as specific and detailed as possible.

o If possible, include a detailed proposed resolution to the issue. A UML model or UML class diagram can be submitted with the issue as an attachment.

o For proposed model extensions include a detailed use case.

o Review the CIM issues spreadsheet before submitting to determine is the issue has been submitted previously.



CIM Naming Rules*:

o Class names are UpperCamelCase (GeneratingUnit).o Attribute names are lowerCamelCase (raiseRampRate).o Association role names are UpperCamelCase.o Association role names are required, but association names are

not.o Names shall be singular unless the concept is plural.o Names shall not include a unit name (“ratedVoltage”, not

“ratedKV”).o Attribute names shall not include the class name.

*(sample list, not exhaustive)



CIM Naming Rules (cont’d)*:

o Use of abbreviations is allowed, but not recommended.

o Acronyms can be used, but the expanded terms must be included in the definition.

o Association role names should use the corresponding end side class as the base role name.

*(sample list, not exhaustive)



CIM Issues Spreadsheet includes fields for:

o Working Group (WG 13, WG 14, WG 16 or combined)

o Issue No. (Unique # assigned by CMM)

o Author / Contact Information

o Date Submitted

o Package (Wires, Core, Assets, etc.)

o Description of Issue

o Proposed Resolution

o Decision

o Person Assigned

o Due Date Status


CMM Report CIM Issues Process - Resolution

CIM Issues Resolution

o Simple issues may be resolved by the CMM and then sent to WG 13 members for approval.

o More complex issues will be discussed during WG 13 and WG 14 CIM issues conference calls. Resolution of an issue may be reached during calls or may be deferred to the next WG 13 or WG 14 meeting.

o Complex or controversial issues will be discussed face to face at WG 13 and WG 14 meetings.

o All WG 13 CIM changes are tracked in a spreadsheet.



CIM Changes Spreadsheet includes fields for:

o Change Number (assigned by CMM)

o Action (New, Change, Delete)

o Package (Wires, Core, etc.)

o Subject (Affected class, attribute, or association)

o Subject Type (Class, Attribute, or Association)

o Description

o Issue Reference Number (from CIM Issues List)

o New CIM Revision

o Author

o Date of Change

o Comments



CIM Changes Spreadsheet Sample


CMM Report CIM Issues - 2009

CIM Issues – 1375 issues (WG 13 and 14) since 2000

WG 13 WG 14 Combined202 32 40

New Issues Since Jan. 2009

Open Issues - Jan. 2009


Open Issues - May 2009



CMM Report CIM Versioning

CIM UML Model Versioning

Version names include both the major CIM version number and the working (minor) version number.

In iec6197014v04:

o CIM version number is 14

o Working version is 4




Versioning is maintained in both the UML model content and the model file name.

File name example:

iec61970cim14v04_iec61968cim10v21_combined.eap

WG 13 CIM Version

WG 14 CIM Version

Enterprise Architect UML of combined WG 13 / WG 14

models




The UML package IEC61968 includes class IEC61968CIMVersion.

Attribute IEC61968CIMVersion.date = 2009-03-01Attribute IEC61968CIMVersion.version = IEC61968CIM10v21

The UML package IEC61970 includes class IEC61970CIMVersion.

Attribute IEC61970CIMVersion.date = 2009-02-27Attribute IEC61970CIMVersion.version = IEC61970CIM14v04



CIM Version Attributes


CMM Report Recent CIM Changes

Recent Major CIM UML Model Changes

o Planning Model Extensions (BusNameMarker, Mutual Coupling)o Ownershipo Control Area Definitionso Regulation Modeling Changeso Load Response Characteristicso State Variables (exchange of solved cases)o Equivalents o Operational Limitso Contingencieso Branch Group “Interface” Monitoring



class BusNameMarker

IdentifiedObject

BusNameMarker

IdentifiedObject

ConnectivityNode

IdentifiedObject

TopologicalNode

+BusNameMarker

0..1

+ConnectivityNode

0..*

+ConnectivityNodes 0..*

+TopologicalNode 0..1

BusNameMarker



class MutualCoupling

MutualCoupling

+ b0ch: Susceptance+ distance11: Length+ distance12: Length+ distance21: Length+ distance22: Length+ g0ch: Conductance+ r0: Resistance+ x0: Resistance

Core::Terminal

ACLineSegment

Conductor

Equipment

Core::ConductingEquipment

Core::IdentifiedObject

+Terminals 0..*

+ConductingEquipment 1

+HasFirst_MutualCoupling

0..*

+First_Terminal

1

+HasSecond_MutualCoupling

0..*

+Second_Terminal

1

Mutual Coupling



class Ownership

IdentifiedObject

OperatingShare

+ percentage: PerCent

OperatingParticipantPowerSystemResource

+OperatingShare

0..*

+PowerSystemResource 1

+OperatingShare

0..*

+OperatingParticipant 1

Ownership



class ControlArea2

PowerSystemResource

ControlArea

+ netInterchange: ActivePower+ pTolerance: ActivePower+ type: ControlAreaTypeKind

TieFlow

+ positiveFlowIn: Boolean

IdentifiedObject

Core::Terminal

Equipment

Production::GeneratingUnit

AltTieMeas

+ priority: Integer

AltGeneratingUnitMeas

+ priority: Integer

IdentifiedObject

LoadModel::EnergyArea

MeasurementValue

Meas::AnalogValue

Measurement

Meas::Analog

ControlAreaGeneratingUnit

+TieFlow 0..*

+ControlArea 1

+TieFlow 0..2

+Terminal 1

+AltTieMeas 0..*

+TieFlow 1

+ControlArea

0..1

+EnergyArea

0..1

+AltGeneratingUnit 0..*

+AnalogValue1

+AltTieMeas

0..* +AnalogValue

1+MemberOf_Measurement

1+Contain_MeasurementValues

1..*

+AltGeneratingUnitMeas 0..*

+ControlAreaGeneratingUnit1

+ControlAreaGeneratingUnit 0..*

+ControlArea

1

+ControlAreaGeneratingUnit0..*

+GeneratingUnit 1

Control Area



class RegulatingEquipment2

IdentifiedObject

Core::Terminal

PowerSystemResource

TapChanger

ConductingEquipment

RegulatingCondEq

RegularIntervalSchedule

RegulationSchedule

FrequencyConverter

SynchronousMachine

StaticVarCompensator

ShuntCompensator

PowerSystemResource

RegulatingControl

+ discrete: Boolean+ mode: RegulatingControlModeKind+ targetRange: Float+ targetValue: Float

+RegulationSchedule

0..1

+RegulatingControl0..*

+RegulatingCondEq

0..* +RegulatingControl

0..1

+TapChanger

0..*

+RegulatingControl

0..1

+Terminal 0..1

+RegulatingControl

0..*

Regulating Equipment



class Load Response Characteristics

NonConformLoad ConformLoad

ConductingEquipment

Wires::EnergyConsumer

IdentifiedObject

LoadResponseCharacteristic

+ exponentModel: Boolean+ pConstantCurrent: Float+ pConstantImpedance: Float+ pConstantPower: Float+ pFrequencyExponent: Float+ pVoltageExponent: Float+ qConstantCurrent: Float+ qConstantImpedance: Float+ qConstantPower: Float+ qFrequencyExponent: Float+ qVoltageExponent: Float

+EnergyConsumer

0..*

+LoadResponse

0..1

Load Response Characteristics



State Variables (Solution Exchange)class StateVariables2

StateVariable

SvInjection

+ pNetInjection: ActivePower [0..1]+ qNetInjection: ReactivePower [0..1]

SvVoltage

+ angle: AngleRadians [0..1]+ v: Voltage [0..1]

StateVariable does NOTinherit from IdentifiedObject.

IdentifiedObject

Topology::TopologicalNode

SvShortCircuit

+ r0PerR: Float [0..1]+ sShortCircuit: ApparentPower [0..1]+ x0PerX: Float [0..1]+ xPerR: Float [0..1]

+SvShortCircuit 0..1

+TopologicalNode 1

+SvVoltage 0..1

+TopologicalNode

1

+SvInjection 0..1

+TopologicalNode

1



State Variables (Solution Exchange)class StateVariables1

RegulatingCondEq

Wires::ShuntCompensator

StateVariable

SvStatus

+ inService: Boolean [0..1]

SvPowerFlow

+ p: ActivePower [0..1]+ q: ReactivePower [0..1]

SvTapStep

+ continuousPosition: Float [0..1]+ position: Integer [0..1]

StateVariable does NOTinherit from IdentifiedObject.

IdentifiedObject

Core::Terminal

+ connected: Boolean [0..1]

Equipment

Core::ConductingEquipment PowerSystemResource

Wires::TapChanger

SvShuntCompensatorSections

+ continuousSections: Float [0..1]+ sections: Integer [0..1]

+Terminals 0..*

+ConductingEquipment 1

+SvTapStep 0..1

+TapChanger 1

+SvShuntCompensatorSections 0..1

+ShuntCompensator 1

+SvPowerFlow 0..1

+Terminal1

+SvStatus 0..1

+ConductingEquipment1



class Equivalents

EquivalentShunt

+ b: Susceptance [0..1]+ g: Conductance [0..1]

EquivalentBranch

+ r: Resistance [0..1]+ x: Reactance [0..1]

ConductingEquipment

EquivalentEquipment

ConnectivityNodeContainer

EquivalentNetwork

+EquivalentEquipments 0..*

+EquivalentNetwork 1

Equivalents



class OperationalLimits

IdentifiedObject

OperationalLimitSet

IdentifiedObject

OperationalLimit

+ type: String

ActivePowerLimit

+ value: ActivePower

ApparentPowerLimit

+ value: ApparentPower

CurrentLimit

+ value: CurrentFlow

VoltageLimit

+ value: Voltage

IdentifiedObject

Core::Terminal

OperationalLimitType

+ acceptableDuration: Seconds+ direction: OperationalLimitDirectionKind

+OperationalLimitValue 0..*

+OperationalLimitSet 1

+OperationalLimitSet

0..* +Terminal

0..1

+OperationalLimit

0..* +OperationalLimitType

0..1

Operational Limit Sets



class Contingency

IdentifiedObject

Contingency

+ mustStudy: Boolean [0..1] = "false"

IdentifiedObject

ContingencyElement

ContingencyEquipment

+ contingentStatus: ContingencyEquipmentStatusKindPowerSystemResource

Core::Equipment

«enumeration»ContingencyEquipmentStatusKind

inService outOfService

+ContingencyEquipment

0..* +Equipment

1

+ContingencyElement 0..*

+Contingency 1

Contingencies



class BranchGroup

IdentifiedObject

BranchGroup

+ maximumActivePower: ActivePower+ maximumReactivePower: ReactivePower+ minimumActivePower: ActivePower+ minimumReactivePower: ReactivePower+ monitorActivePower: Boolean+ monitorReactivePower: Boolean

IdentifiedObject

Core::TerminalBranchGroupTerminal

+ positiveFlowIn: Boolean

+BranchGroupTerminal 0..*

+BranchGroup 1

+BranchGroupTerminal

0..* +Terminal

1

Branch Groups


CMM Report CIM Issues for 2009

CIM Issues/Priorities for 2009

o UCTE Exchange Support o State Variable o Display Layout Exchangeo HVDC Modelingo EPRI CIM-for-Planning Dynamics Models o Old Issue Clean-upo Equivalents Enhancementso Load Model Clean-up WG13/14o Multiple Inheritanceo Compound Datatypeso WG16 Integration


CIM Model Manager Report

Questions?

[email protected]

cim model manager report

Documents