Project

General

Profile

CIM Issues #6785

Modelling of Ward and Extended Ward Equivalent by EquivalentInjection

Added by Chavdar Ivanov 7 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Chavdar Ivanov
Base Release:
CIM18
Solution to be Applied To:
CIM18v11
Solution Version:
CIM18v11
Solution Applied By:
Chavdar Ivanov
Completion Date:
06/04/2024
CIM Keywords:
61970-Equivalents
Breaking Change:
Yes
Breaking Change Description:
Attributes are moved
CIM Impacted Groups:
WG13
Requestor:
Standard(s):

61970-301, 61970-452

Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:

Description

The current EquivalentInjection jas some gaps that prevent to use it to represent ward or extended ward equivalent.
Therefore it is recommended to apply the following changes:
- Add attribute EquivalentInjection.kind, type EquivalentInjectionKind
- add enumeration EquivalentInjectionKind
- add enum quivalentInjectionKind.ward
- add enum quivalentInjectionKind.extendedWard
- move r, x, from SC profile to EQ profile as they can be used for the power flow calculation. The negative and zero sequence should stay in SC profile

Define a rule that ward equivalent cannot be regulating voltage so we have dependency between the .kind attribute and the attributes related to the regulating capability

There could be an option to reuse the regulatingCapability instead of adding .kind, but we will need to refer to ward and extended ward in the description

Some references
ward: https://pandapower.readthedocs.io/en/v2.1.0/elements/ward.html
extended ward: https://pandapower.readthedocs.io/en/v2.1.0/elements/xward.html

Decision

15 May 2024
we agree to create 2 subclasses: WardEquivalent ExtendedWardEquivalent
- ExtendedWardEquivalent would have r, x, and the regulating status and voltage attributes all required attributes in the profile
- EquivalentInjection will be abstract in the profile

Martin will double check.

Marting replied - see notes.

The issue can be implemented and closed

Release Notes

The following classes were added WardEquivalent ExtendedWardEquivalent
The ExtendedWardEquivalent has r, x, and the regulating status and voltage attributes all required attributes in the profile. The attributes are moved from EquivalentInjection. ExtendedWardEquivalent gets r0, r2, x0, x2 as part of the SC profiles
EquivalentInjection is abstract in the profile
The association with ReactiveCapabilityCurve is moved to ExtendedWardequivalent
Attribute regulationCapability is deleted as ExtendedWardEquivalent always has the capability to regulate. The regulationStatus is kept for SSH usage to have the ability to deactivate the voltage control although this is also questionable as this will turn the Extended ward to a ward.

Changes are applied in EQ, SC and SSH profiles.

Also available in: Atom PDF