CIM Issues #5076: Convention and usage of operational limits of GeneratingUnit and injections - WG13 Issues - UCAIug Issue Tracking System

CIM Issues #5076

Convention and usage of operational limits of GeneratingUnit and injections

Added by Chavdar Ivanov over 3 years ago. Updated 7 months ago.

Status:

In Progress

Priority:

High

Author/Contact Info:

chavdar.ivanov@griddigit.eu

Base Release:

CIM17

Solution to be Applied To:

CIM18 or CIM17 amendment

Solution Version:

Solution Applied By:

Completion Date:

CIM Keywords:

61970-Production

Breaking Change:

Breaking Change Description:

CIM Impacted Groups:

WG13

Requestor:

Chavdar Ivanov

Standard(s):

61970-301, 61970-452, 61970-456

Version:

301Ed7.1

Clause:

Sub-Clause:

Paragraph:

Table:

Originally Closed in Version:

Origination Date:

09/17/2021

Origination ID:

Originally Assigned To:

Description

There is ambiguity in the usage and definition of the following attributes
GeneratingUnit.maxOperatingP
GeneratingUnit.minOperatingP
EquivalentInjection.minP
EquivalentInjection.maxP
ExternalNetworkInjection.minP
ExternalNetworkInjection.maxP
EquivalentInjection.minQ
EquivalentInjection.maxQ
ExternalNetworkInjection.minQ
ExternalNetworkInjection.maxQ

GeneratingUnit and the injections can operate both in generator and in motor mode. It is not clear what is the sign convention for the limits. Is it positive when generating and negative when consuming? If yes a GeneratingUnit of type motor needs to have its minOperatingP and maxOperatingP negative. However do we require that abs(minOperatingP) is < abs(maxOperatingP)? If not doing this one can do maxOperatingP=-5 > minOperatingP=-100 which will need to be most probably imported in an application as Pmax=100 and Pmin=5, meaning we do not have 1:1 mapping in the sense of meaning maxOperatingP and minOperatingP.

Whatever the solution is this needs to be compatible with the understanding of ReactiveCapabilityCurve and xvalue there in case of motor operation

Similar clarification is necessary for EquivalentInjection and ExternalNetworkInjection where we do not have the operating mode in EQ, but we do have limits there.

Proposed Solution

Assign to the Physical Device Subgroup (9/22/2021)

Decision

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.