CIM Issues » WG13 Issues

Call 18 Oct 2023
Different options are possible:
-Option 1: Changing descriptions and moving attributes to SSH, or
-Option 2: In the EQ have the normal values and have another attribute (optional) in SSH
Option 2 is better option and should be implemented if there is no disagreement in Minneapolis meeting the week of 23 Oct 2023

If option 2 is approved the changes will be

Create the following attributes and add them to EQ profile in 452
GeneratingUnit.normalMaxOperatingP
GeneratingUnit.normalMinOperatingP
EquivalentInjection.normalMinP
EquivalentInjection.normalMaxP
ExternalNetworkInjection.normalMinP
ExternalNetworkInjection.normalMaxP
EquivalentInjection.normalMinQ
EquivalentInjection.normalMaxQ
ExternalNetworkInjection.normalMinQ
ExternalNetworkInjection.normalMaxQ

Add the following attributes in SSH (456), remove attributes from EQ (452) and modify the descriptions so that it is clear that SSH value depends on the operating mode
GeneratingUnit.maxOperatingP
GeneratingUnit.minOperatingP
EquivalentInjection.minP
EquivalentInjection.maxP
ExternalNetworkInjection.minP
ExternalNetworkInjection.maxP
EquivalentInjection.minQ
EquivalentInjection.maxQ
ExternalNetworkInjection.minQ
ExternalNetworkInjection.maxQ

18-Sep-2024 Joint TF Hybrid Meetings - Minneapolis:
Revisited again and reviewed. Agree to the below:

Create the following attributes which is a revision of the previous proposal. Add these to EQ profile in 452
GeneratingUnit.normalMaxEconomicP
GeneratingUnit.normalMinEconomicP
EquivalentInjection.normalMinP
EquivalentInjection.normalMaxP
ExternalNetworkInjection.normalMinP
ExternalNetworkInjection.normalMaxP
EquivalentInjection.normalMinQ
EquivalentInjection.normalMaxQ
ExternalNetworkInjection.normalMinQ
ExternalNetworkInjection.normalMaxQ

Add the following attributes in SSH (456), remove attributes from EQ (452) and modify the descriptions so that it is clear that SSH value depends on the operating mode
GeneratingUnit.maxEconomicP
GeneratingUnit.minEconomicP
EquivalentInjection.minP
EquivalentInjection.maxP
ExternalNetworkInjection.minP
ExternalNetworkInjection.maxP
EquivalentInjection.minQ
EquivalentInjection.maxQ
ExternalNetworkInjection.minQ
ExternalNetworkInjection.maxQ

Identified additional request for changes that originated from ENTSO-E. Add as part of these changes:
Rename exiting HydroPump.pumpPowerAtMaxHead to HydroPump.maxP
Rename existing HydroPump.pumpPowerAtMinHead to HydroPump.minP

The extensions in ExtHydroPump, ExtEnergyConsumer, ExtPowerElectronics and ExtGeneratingUnit need to be also moved (these were missed as they are <<NC>> extensions in the Inf* package).

We've agreed to include in CIM18v13.

The economic attributes should be in the 456 profiles.

07-Apr-2025 Review during Nanjing, China meetings:

Chavdar/Todd proposal for review and the following was agreed upon and given the green light move into the model:

* Our proposal is to add normalOperatingMode attribute on the SynchronousMachine (to be added to the EQ profile)

* For the GeneratingUnit and all "normalXXX" attributes shown below the following general sentence...

"This attribute uses generation sign convention, i.e. positive sign means flow into a node."

...should be added to the end of the description of each Power related attribute:

- allocSpinResP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- autoCntrlMarginP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- baseP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- initialP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- maxEconomicP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- maximumAllowableSpinningReserve: "This attribute uses generation sign convention, i.e. positive sign means flow into a node. This value is expected to always be positive." (not breaking for this attribute)
- maxOperatingP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- minEcononicP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- minOperatingP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- mustRunP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (breaking change from what we originally defined for <<NC>> for this attribute)
- mustRunQ: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (breaking change from what we originally defined for <<NC>> for this attribute)
- nominalP: NOTE: After review there is NO change to the existing description.
- normalMaxEconomicP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- normalMustRunP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (breaking change from what we originally defined for <<NC>> for this attribute)
- normalMustRunQ: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (breaking change from what we originally defined for <<NC>> for this attribute)
- ratedGrossMaxP: Add to the existing description: "The attribute is only applicable for equipment with generation capability as specified by the SynchronousMachine.type." (not breaking for this attribute)
- ratedGrossMinP: Add to the existing description: "The attribute is only applicable for equipment with generation capability as specified by the SynchronousMachine.type." (not breaking for this attribute)
- ratedNetMaxP: Add to the existing description: "The attribute is only applicable for equipment with generation capability as specified by the SynchronousMachine.type." (not breaking for this attribute)

New "normal" attributes on GeneratingUnit needed for the above Power attributes:
- normalMaxAllowableSpinningReserve: After review it was determine we do NOT need this attribute.
- normalMaxOperatingP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- normalMinEconomicP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)
- normalMinOperatingP: "This attribute uses generation sign convention, i.e. positive sign means flow into a node." (not breaking for this attribute)

It was agreed that for "non-normal" attributes (in SSH) in GeneratingUnit the following is to be added to the descriptions:

"This attribute uses generation sign convention, i.e. positive sign means flow into a node. Depending on the operating mode of the equipment the value can be positive, negative, or zero."

For those that DO NOT have operating modes (i.e. EquivalentInjection, ExternalNetworkInjection, PowerElectronicsUnit, HydroPump, EnergyConsumer) it should have the following general description based on load sign convention:

"Load sign convention is used, i.e. positive sign means flow out of a node into the equipment." (this to be applied for normal and non-normal values)

NOTE: Agreed that for EquivalentInjection, ExternalNetworkInjection, PowerElectronicsUnit, HydroPump, EnergyConsumer classes, any attributes that are ratings-related they should all be positive.

We have agreed on the following new description of GenerationgUnit to better cover motors/condenser:

"A single or set of synchronous machines for converting mechanical power into alternating-current power or for converting alternating-current power to mechanical power i.e. motor. Different operating modes are available to represent synchronous condensers, generators, and motors. For example, individual machines within a set may be defined for scheduling purposes while a single control signal is derived for the set. In this case there would be a GeneratingUnit for each member of the set and an additional GeneratingUnit corresponding to the set."