2011   SocUseMaxPct and SocUseMinPct should be moved from OperationalFunctionLN

Created: 09 Dec 2025

Status: Triage

Part: Part 7-420 (2021; Edition 2, DER)

Links:

Page: 344

Clause: A.3.2.4.3.6

Paragraph: Table A.78

Issue

Although SocUseMaxPct and SocUseMinPct are currently defined within OperationalFunctionLN, these Data Objects are not generic to operational functions. Therefore, they should be relocated to a more appropriate Logical Node.

Proposal

At a minimum, DTCD requires these Data Objects because it already includes SocUseTgtPct. No other Logical Node defines a comparable Data Object related to SoC. Therefore, DTCD appears to be the most suitable candidate for hosting SocUseMaxPct and SocUseMinPct.

Discussion Created Status
Thank you for your explanations regarding the concepts of SocUseMaxPct and SocUseMinPct as they apply to operational functions other than DTCD.

I agree with your assessment.

As this does not appear to be a critical issue, these two DOs will be incorporated into an appropriate abstract class as part of the current namespace work. 		08 Feb 26 Triage
I agree that these data objects do not apply to all the operational functions, but they apply to more than DTCD.

They could apply to any operational function that controls the active power flow and hence affects the SOC of a storage resource. If the SOC is outside the defined range, then the resource will suspend that function.
For example, these data objects could describe the SOC range allocated to frequency support functions DHFW, DLFW.

Operational functions for reactive power flows result in no net change to the SOC over time, but cycle-by-cycle there are current flows.

The state-of-charge is not relevant to the protection related trip and ride-through operational functions. 		29 Jan 26 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 26.1.29.1