2011 SocUseMaxPct and SocUseMinPct should be moved from OperationalFunctionLN
- Created
- 09 Dec 2025
- Status
- EditorialA correction to the wording, with no effect on the technical content. Show the workflow
- Part
- Part 7-420 (2021; Edition 2, DER)
- Links
- None
- 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 |
|---|---|
|
Editorial
Improved description for SocUseMaxPct (last sentence)
Maximum percent of state-of-charge (SOC) for this function to be enabled. SocUseMinPct and SocUseMaxPct can 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 should suspend operation of that function. For example, they could describe the SOC range allocated to frequency support functions DHFW, DLFW. SocUseMinPct and SocUseMaxPct are not relevant to limits and the protection related trip and ride-through operational functions: DHVT, DVLT, DLFT, DHFT, DWMN, DWMX |
07 Aug 26 |
|
Editorial
Proposed descriptions for the data objects:
SocUseMaxPct Maximum percent of state-of-charge (SOC) for this function to be enabled. SocUseMinPct and SocUseMaxPct can 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 should suspend operation of that function. For example, they could describe the SOC range allocated to frequency support functions DHFW, DLFW. The state-of-charge is not relevant to the protection related trip and ride-through operational functions. SocUseMinPct Minimum percent of state-of-charge (SOC) for this function to be enabled. For more information see SocUseMaxPct. |
07 Aug 26 |
| Editorial Set status to Editorial not Approved (Editorial) | 23 Jul 26 |
| Approval (Editorial) More explanatory text can be added to the relevant sections in the document | 23 Jul 26 |
|
Triage
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 |