CIM Model Manager Report Kurt Hunter CIM Users Group Meeting 13 May 2009

CMM Report Topics Background Responsibilities of CIM Model Manager WG 13 CIM Roadmap CIM Issues Process CIM Versioning Recent CIM Changes CIM Priorities for 2009

Background CMM Report Background 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 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 For 2009, Siemens agreed to fund the position again.

CMM Report Responsibilities of CIM Model Manager Manage and maintain the integrated CIM UML model Coordinate model changes with WG 14 and WG 16 Manage the CIM issues list Facilitate WG 13 Issues discussions Produce the IEC 61970-301 document Assist CIM UG in answering questions from users Report to WG 19 and other IEC working groups

CMM Report WG 13 CIM Roadmap WG 13 Part 301 is on a yearly release cycle. WG 13 CIM Roadmap provides an overview of planned and completed CIM UML model changes. Serves as the main driver, in addition to CIM issues, behind changes to the CIM UML model.

CMM Report WG 13 CIM Roadmap Version 12 13 14 Profile Draft May 2007 May 2008 May 2009 Test IOP10 September 2007 IOP11 September 2008 IOP12 September 2009 Release Q1 2008 Q1 2009 Q1 2010 Addresse d 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

CMM Report WG 13 CIM Roadmap Version 13 14 15 Profile Draft June 2008 May 2009 May 2010 Test IOP October 2008 September 2009 September 2010 Release Q1 2009 Q1 2010 Q1 2011 Addresse d Issues OWL meta data Tools, EA transition CIM Issues CIM for planning ERCOT issues Operational limits 61968 integration Dynamics Models DC models Multiple inheritance Datatypes Solution exchange Contextual models

CMM Report WG 13 CIM Roadmap Typical Yearly Cycle Plan

CMM Report CIM Issues for 2009 CIM 2009 Yearly Cycle Finalize UML And Produce CIM 14 Release UCTE Interoperability Test Dynamics Interoperability Test CPSM Interoperability Test Resolve Issues from Interoperability Tests 2009 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2010

CMM Report CIM Issues Process Interoperability Tests UML Model and Profile Changes

CMM Report CIM Issues Process CIM Issues Process consists of three primary components: Issues Submission Issues Resolution Issues Tracking

CMM Report CIM Issues Process - Submission CIM Issues Submission In the past issues have been written second hand from information in emails, discussions at Interop Tests, etc. Consequently, issues that could not be resolved quickly are frequently difficult to interpret when coming back to them. Currently requiring issues to be written by the submitter, preferably using the CIM Users Group website.

CMM Report CIM Issues Process - Submission CIM Users Group Website: http://cimug.ucaiug.org

CMM Report CIM Issues Process - Submission Model Issues Summary

CMM Report CIM Issues Process - Submission Submitting a New Issue

CMM Report CIM Issues Process - Submission New Issue Submission Form

CMM Report CIM Issues Process - Submission Tips for CIM Issues Submission Be as specific and detailed as possible. 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. For proposed model extensions include a detailed use case. Review the CIM issues spreadsheet before submitting to determine is the issue has been submitted previously.

CMM Report CIM Issues Process - Submission CIM Naming Rules*: Class names are UpperCamelCase (GeneratingUnit). Attribute names are lowerCamelCase (raiseRampRate). Association role names are UpperCamelCase. Association role names are required, but association names are not. Names shall be singular unless the concept is plural. Names shall not include a unit name (“ratedVoltage”, not “ratedKV”). Attribute names shall not include the class name. *(sample list, not exhaustive)

CMM Report CIM Issues Process - Submission CIM Naming Rules (cont’d)*: Use of abbreviations is allowed, but not recommended. Acronyms can be used, but the expanded terms must be included in the definition. Association role names should use the corresponding end side class as the base role name. *(sample list, not exhaustive)

CMM Report CIM Issues Process - Submission CIM Issues Spreadsheet includes fields for: Working Group (WG 13, WG 14, WG 16 or combined) Issue No. (Unique # assigned by CMM) Author / Contact Information Date Submitted Package (Wires, Core, Assets, etc.) Description of Issue Proposed Resolution Decision Person Assigned Due Date Status

CMM Report CIM Issues Process - Resolution CIM Issues Resolution Simple issues may be resolved by the CMM and then sent to WG 13 members for approval. 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. Complex or controversial issues will be discussed face to face at WG 13 and WG 14 meetings. All WG 13 CIM changes are tracked in a spreadsheet.

CMM Report CIM Issues Process - Resolution CIM Changes Spreadsheet includes fields for: Change Number (assigned by CMM) Action (New, Change, Delete) Package (Wires, Core, etc.) Subject (Affected class, attribute, or association) Subject Type (Class, Attribute, or Association) Description Issue Reference Number (from CIM Issues List) New CIM Revision Author Date of Change Comments

CMM Report CIM Issues Process - Resolution CIM Changes Spreadsheet Sample

CIM Issues – 1375 issues (WG 13 and 14) since 2000 CMM Report CIM Issues - 2009 CIM Issues – 1375 issues (WG 13 and 14) since 2000 Open Issues - Jan. 2009 WG 13 WG 14 Combined 202 32 40 New Issues Since Jan. 2009 WG 13 WG 14 Combined 18 25 4 Open Issues - May 2009 WG 13 WG 14 Combined 132 31 23

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: CIM version number is 14 Working version is 4

CMM Report CIM Versioning CIM UML Model Versioning Versioning is maintained in both the UML model content and the model file name. File name example: iec61970cim14v04_iec61968cim10v21_combined.eap Enterprise Architect UML of combined WG 13 / WG 14 models WG 13 CIM Version WG 14 CIM Version

CMM Report CIM Versioning CIM UML Model Versioning The UML package IEC61968 includes class IEC61968CIMVersion. Attribute IEC61968CIMVersion.date = 2009-03-01 Attribute IEC61968CIMVersion.version = IEC61968CIM10v21 The UML package IEC61970 includes class IEC61970CIMVersion. Attribute IEC61970CIMVersion.date = 2009-02-27 Attribute IEC61970CIMVersion.version = IEC61970CIM14v04

CMM Report CIM Versioning CIM Version Attributes

CMM Report Recent CIM Changes Recent Major CIM UML Model Changes Planning Model Extensions (BusNameMarker, Mutual Coupling) Ownership Control Area Definitions Regulation Modeling Changes Load Response Characteristics State Variables (exchange of solved cases) Equivalents Operational Limits Contingencies Branch Group “Interface” Monitoring

CMM Report Recent CIM Changes BusNameMarker

CMM Report Recent CIM Changes Mutual Coupling

CMM Report Recent CIM Changes Ownership

CMM Report Recent CIM Changes Control Area

CMM Report Recent CIM Changes Regulating Equipment

CMM Report Recent CIM Changes Load Response Characteristics

CMM Report Recent CIM Changes State Variables (Solution Exchange)

CMM Report Recent CIM Changes State Variables (Solution Exchange)

CMM Report Recent CIM Changes Equivalents

CMM Report Recent CIM Changes Operational Limit Sets

CMM Report Recent CIM Changes Contingencies

CMM Report Recent CIM Changes Branch Groups

CMM Report CIM Issues for 2009 CIM Issues/Priorities for 2009 UCTE Exchange Support State Variable Display Layout Exchange HVDC Modeling EPRI CIM-for-Planning Dynamics Models Old Issue Clean-up Equivalents Enhancements Load Model Clean-up WG13/14 Multiple Inheritance Compound Datatypes WG16 Integration

CIM Model Manager Report Questions? kurt.hunter@siemens.com