Project

General

Profile

CIM Issues #6147

[GMDM #1] Streamlining of tank-based transformer modelling

Added by Yang Feng about 2 years ago. Updated 2 months ago.

Status:
In Progress
Priority:
Normal
Author/Contact Info:
Pat Brown
Base Release:
Solution to be Applied To:
CIM19
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
61968-AssetInfo, 61968-Assets, 61970-Wires
Breaking Change:
Breaking Change Description:
Unclear at the moment
CIM Impacted Groups:
WG13
Requestor:
Pat Brown
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:
Pat Brown

Description

Currently, the modelling of an unbalanced (tank-based) transformer can be accomplished in a variety of ways, using a multitude of combinations of classes and associations. The number of possible alternatives is an impediment to interoperability. A number of the classes used in describing transformers for network modelling purposes are also resident in the 61968 package, not the 61970 package, despite the fact that they were designed to support network analysis, not asset management, use cases.
This issue suggests the articulation of a comprehensive, cohesive approach to tank-based transformer modelling which would accomplish the following:
• Support the modelling of tank-based transformers in strictly electrical terms
• Support the modelling of tank-based transformers using test results
• Support the definition of ‘catalog’ information of both kinds of modelling (electrical terms and test results)
• Align with the current balanced (non-tank-based) transformer modelling described by 61970-301 and -452
• Augment the current non-tank-based modelling to allow modelling of those transformers with test results
The net outcome is anticipated to significantly leverage existing classes, attributes and associations. Likely changes include a few new associations that clarify (and support validation of) intended usage, perhaps some moving of attributes from one class to another and the move of a number of classes from the 61968 package to the 61970 package.

Files

GMDM 1 - Streamlining of tank-based transformer modelling.docx GMDM 1 - Streamlining of tank-based transformer modelling.docx 1.26 MB Pat Brown, 05/24/2023 08:36 AM

Decision

Oslo, 13 June 2023
Proposal for changes will need to be prepared. Possible solution is to copy some of the attributes from info classes to transformer.
Volunteers: Martin, Pat, Jugoslav

18-Sep-2024 Joint TF Hybrid Meetings:
Revisited this issue. Agreed it is CIM19. Celso and Andres volunteered to take this on. Martin volunteers to provide a list properties on the asset side that ought to be on the equipment side.

When we reviewed Redmine issue #6148 today we identified it overlaps. We've closed that issue out and moved its proposed solution here for consideration (and so that it wasn't lost):

3 attributes were copied from TapChangerInfo to TapChanger: .ctRating, .ctRatio and .ptRatio. This obviated the need to include TapChangerInfoobjects in the GMDM profiles and data exchanges.

Also available in: Atom PDF