CIM Issues #5303: 5302:5303 61970 portion of TransformerTank to TransformerTankInfo association - WG13 Issues - UCAIug Issue Tracking System

CIM Issues #5303

5302:5303 61970 portion of TransformerTank to TransformerTankInfo association

Added by Pat Brown almost 3 years ago. Updated 2 months ago.

Status:

Closed

Priority:

Normal

Author/Contact Info:

Pat Brown

Base Release:

Solution to be Applied To:

iec61970cim18v01_iec61968cim14v00_iec62325cim04v08_CIM101.0

Solution Version:

Solution Applied By:

Pat Brown

Completion Date:

CIM Keywords:

61968-AssetInfo, 61970-Wires

Breaking Change:

Breaking Change Description:

CIM Impacted Groups:

WG13, WG14

Requestor:

Pat Brown

Standard(s):

61968-11, 61968-4, 61970-301, 61968-13

Version:

Clause:

Sub-Clause:

Paragraph:

Table:

Originally Closed in Version:

Origination Date:

Origination ID:

Originally Assigned To:

Description

In the canonical UML, 61970 PowerSystemResource child classes inherit an association to AssetInfo. This means that, as a child of PowerSystemResource, the TransformerTank class has an allowed association to classes as diverse (and illogical) as EndDeviceInfo, SurgeArresterInfo and WireInfo. This situation forces 61970 profiles to articulate constraints that are actually universal and not profile-specific.

Files

2022-01-19 Device Datasheet TransformerTank TransformerTankInfo requested UML updates.docx	2022-01-19 Device Datasheet TransformerTank TransformerTankInfo requested UML updates.docx	570 KB		Pat Brown, 01/30/2022 05:22 AM
2022-01-30 Device Datasheet TransformerTank TransformerTankInfo requested UML updates.docx	2022-01-30 Device Datasheet TransformerTank TransformerTankInfo requested UML updates.docx	571 KB		Pat Brown, 01/30/2022 05:32 AM

Proposed Solution

Add an explicit association between TransformerTank and TransformerTankInfo.

Decision

18-Sep-2024 Joint TF Hybrid Meetings - Minneapolis:

Reviewed and the decision is to not implement the proposed change. We believe the existing association is sufficient. If we were to fix this then our position is that is must be fixed for all scenarios and not just this particular use case.

Release Notes

Add association TransformerTankInfo.TransformerTank, ensuring that the association source is TransformerTankInfo and the target is TransformerTank since the association ‘spans’ the 61968/61970 package divide.

See attached 2022-01-30 Device Datasheet TransformerTank TransformerTankInfo requested UML updates.docx for more detail on role descriptions.