1963   DPMC error in Mmulti, Omulti constraints

Created: 13 Feb 2025

Status: Drafting Implementation

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

Links:

Page: 220

Clause: A.3.1.5.3

Paragraph: Table A.30

Issue

Problem reported by j61850DocBulder V2.04

[main] ERROR IEC61850_7_420 DERPowerManagementLN::DPMC : [constraint 'Mmulti' for inexisting 'EcpRef'][constraint 'Omulti' for inexisting 'CeaEngzCtl','CeaEngzCtlSt']

Proposal

Believed related to attribute renaming
EcpRef with OutDepRef
CeaEngzCtl,CeaEngzCtlSt with CeaEgzCtl

DPMC allows multiple setpoint DOs

To be discussed

EITHER delete erroneous constraints in UML model
OR
revise model so that DPMC can be used with multiple ECP and/or
multiple Cease to energize controls


Discussion Created Status
14-Nov-2025 Its not clear why CeaEgzCtl should be multi.
Leave this as a single optional control
Correct the constraints in the UML
14 Nov 25 Drafting Implementation
Accepted for discussion 04 Nov 25 Discussion (red)
Discussed in WG17 meeting 4th March 2025 04 Nov 25 Accepted
Discussed 24-Mar-2024
DPMC can handle multiple units => most data objects should be multiple.
2 main use cases:
a. 1 DPMC has one set of data-objects - the DMPC aggregates or distributes setpoints as relevant
b. 1 DPMC has multiple data objects - the DMPC is a container for the data points from each of the DER units

Conclusion: in short term - change constraints to match latest data object names.

It would be good to have some examples in part 7-520.
24 Mar 25 Triage
Correction: EcpRef has been replaced by OutEcpRef

Proposal - delete erroneous constraints in UML model
Keep the model as per the published document.
04 Mar 25 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 26.1.29.1