CIM Issues #6547: European extensions introduced in CIM17v40 are not compliant to the CIM Modelling Guidelines document. - CIM Joint Issues - UCAIug Issue Tracking System

CIM Issues #6547

European extensions introduced in CIM17v40 are not compliant to the CIM Modelling Guidelines document.

Added by Todd Viegut about 1 year ago. Updated about 1 year ago.

Status:

Closed

Priority:

High

Solution Version:

CIM18v08

Breaking Change:

Breaking Change Description:

CIM Impacted Groups:

WG13, WG14, WG16

Requestor:

todd.viegut@gmail.com

Standard(s):

Version:

Clause:

Sub-Clause:

Paragraph:

Table:

Origination Date:

Origination ID:

Originally Assigned To:

Description

The use of multiple inheritance is currently strictly prohibited within normative CIM and is overtly prescribed within formal rules in the CIM Modelling Guidelines publication maintained by the CIM model managers. These changes were first merged into the model in the CIM18v06 release. However, historically the modelling is associated with CIM17 and appears as normative European extensions in an Annex of IEC 61970-301 Ed 7.1. Therefore, this issue must be discussed in a Joint WG meeting.

Refer to: https://redmine.ucaiug.org/issues/6548

Files

IEC UTF Joint In-Person Meetings - Minneapolis, MN - Decisions on how transition European Extension in CIM17 into CIM18.docx	IEC UTF Joint In-Person Meetings - Minneapolis, MN - Decisions on how transition European Extension in CIM17 into CIM18.docx	276 KB		Todd Viegut, 10/24/2023 05:17 AM
23-Oct-2023 - Joint WG Modeling Topics - PM Session - Modelling Guidelines.pptx	23-Oct-2023 - Joint WG Modeling Topics - PM Session - Modelling Guidelines.pptx	213 KB		Todd Viegut, 10/24/2023 05:17 AM

Decision

23-Oct-2023 Hybrid Meetings - Minneapolis, MN:

Discussed in this week's Joint WG meetings with the following decisions as outcomes:

1) We should put more detail into the attribute descriptions as we move forward (like the approach WG16 has taken between NA and European markets). This does not need to happen before the merge next week.
2) All attributes and classes will be brought into normative CIM (for example, the ExtEuOperationalLimitType.kind attribute will be moved into the OperationaLimitType (normative) class and, as agreed, a stereotype of <<European>> is to be be added to it)
3) We have classes in the Inf* packages that need to be corrected. The issue is that multiple inheritance appears in the UML diagrams generated into the 301/302/457, etc. The decisions / fix for this issue will be as follows: Prior to a 301 document generation the entire Inf* package (top level) is to be deleted (not permanently) before doc generation. This is applicable to all WGs (WG13, WG14, WG16)
4) For the upcoming broad model merge (of all CIM packages across WGs) we only need to implement Decision 2 (above). Therefore, Chavdar will produce a CIM18v08 release that will correct the issues as described here. An additional WG13 issue will be created to track the specific of the changes to the Grid package.

NOTE: Details of the meetings notes in Minneapolis are attached as well as the PPT presentation.

Related issues