CIM Issues #6452
Allow multiple RatioTapChanger on one TransformerEnd
61970-301,61970-452
Description
The current cardinality only allows one RatioTapChanger to be associated to a PowerTransformerEnd. I've come across multiple scenarios where a transformer may have two RatioTapChanger on one PowerTransformerEnd, one of which is on-load tap changer and the other one is off-load tap changer. Attached I've added one example from a real customer data describing it.
Files
Proposed Solution
Change the cardinality to 1:0..2 (if this is allowed) or to 1:0..*
Most of the cases I have seen is to have two RatioTapChanger, never encountered more than two scenario
In addition there is a need to discuss: The possibility to have both a PhaseTapChangerTable and a RatioTapChangerTable assigned to a TapChanger in EQ and an attribute in SSH to denote which is active (reported by HOPS)
In addition there is a request to have a tap changer that has both ratio and phase tap changer on same winding and the winding connection angle is changing as part of the operational processes.
Slides are attached
Decision
Call 18 Oct 2023
the group is not sure that we need to change the cardinality. We rather have this modelled in a different way. Suggested to have a wider discussion in Minneapolis meeting - 23 Oct 2023
Multiple decisions are recorded in the attached document. Final agreement is to add this to the canonical CIM and profiles
Release Notes
Applied changes in canonical CIM
- added class StepOperationalLimitTable
- added class StepLimitTablePoint with attributes step and factor
- the association end RatioTapChanger.TransformerEnd is changed from 1 to 0..1
- new association is added between RatioTapChanger and TransformerEnd
- added class ConnectionAngleTapChangerTable with attribute ConnectionAngleTapChangerTable.windingConnectionAngle
- added class ConnectionAngleTapChanger
- added ConnectionAngleTapChanger.minWindingConnectionAngle, maxWindingConnectionAngle, connectionAngleStepSize, windingConnectionAngle, normalWindingConnectionAngle
- added class ImpedanceTapChangerTabular
- added class ImpedanceTapChangerTable
- added class ImpedanceTapChangerTablePoint with the following attributes: xEnd1, xEnd2, xEnd3, rEnd1, rEnd2, rEnd3, step, ratio, angle.
- the text "Note that the upper boundary is not constrained to 100 percent." is added to TapChangerTablePoint.b, .g, .r, .x
Changes are also applied to EQ (452) and SSH profiles (456)
Updated by Yang Feng almost 2 years ago
- Standard(s) changed from 61970-301/452 to 61970-301,61970-452
Updated by Chavdar Ivanov over 1 year ago
- Status changed from New to Open
- Decision updated (diff)
Updated by Chavdar Ivanov about 1 year ago
- File Tap_changer_issues.pptx Tap_changer_issues.pptx added
Updated by Chavdar Ivanov about 1 year ago
Updated the presentation with additional issues
Updated by Chavdar Ivanov 12 months ago
Updated by Chavdar Ivanov 12 months ago
Updated by Domagoj Peharda 3 months ago
Please reopen this case, the end names of two associations from RatioTapChanger to TransformerEnd is the same: TransformerEnd.
Association end names should be unique among all specialisations of a class. For example, if IdentifiedObject associates to the Name class with an end name of “Name”, no specialisation of IdentifiedObject may create another association whose end name is “Name” regardless of the class to which it associates. Note that any number of associations from other classes may use the same name (e.g. “IdentifiedObject”) as the association end name on the IdentifiedObject end of the association, as long as the prior rule of uniqueness among specializations is respected.