1971 EqGn in DGEN, EqSto in DSTO, and EqLod in DLOD
- Created
- 09 Apr 2025
- Status
- Drafting ImplementationThe agreed solution is being written up as text for the standard. Any signed-in reader may comment. Show the workflow
- Part
- Part 7-420 (2021; Edition 2, DER)
- Links
- None
- Page
- 234, 246, 257
- Clause
- A.3.1.7.3, A.3.1.8.3, A.3.1.9.3
- Paragraph
- Table A.34, A.36, A.38
Issue
Neither EqGn in DGEN, EqSto in DSTO, nor EqLod in DLOD is explained in the main text. If DGEN instance No. 1 is referred to by EnGn of DGEN instance No. 2, all data objects will have identical values. It is difficult to imagine a scenario where instance No. 2 is necessary.
Additionally, the presence conditions for EqSto in DSTO (mandatory) and EqGen in DGEN (Omulti) are not reasonable.
Proposal
The first option is to delete the three data objects from each logical node.
The second option is to explain the meaning of the data objects or the situations in which they are used, similar to clause 4.2.5.5.4.
The third option is to change the presence conditions of EqGn in DGEN and EqSto in DSTO to optional.
The first or second option is preferred.
| Discussion | Created |
|---|---|
|
Drafting Implementation
(options 2 and 3)
Proposed updated descriptions for the data objects and set presence condition to Omulti for each of them DGEN.EqGn Reference to another DGEN instance reflecting a different view of the same physical resource or resources. For example reflecting the ratings for controllable resources only. DLOD.EqLod Reference to another DLOD instance reflecting a different view of the same physical resource or resources. For example reflecting the ratings for controllable resources only. DSTO.EqSto Reference to another DSTO instance reflecting a different view of the same physical resource or resources. For example reflecting the ratings of controllable resources only. Plus DMDR Clarify that the equivalents apply to the DER that is modelled by this DMDR DMDR.EqGn Reference to the equivalent DGEN instance reflecting the generation aspects of this DMDR. DMDR.EqLod Reference to the equivalent DLOD instance reflecting the load aspects of this DMDR. DMDR.EqSto Reference to the equivalent DSTO instance reflecting the storage aspects of this DMDR. DSTO No change DSTO.EqGn Reference to the equivalent DGEN instance reflecting the generation aspects of storage DSTO.EqLod Reference to the equivalent DLOD instance reflecting the load aspects of storage |
19 Aug 26 |
|
Drafting Implementation
Discussed in February 2026 meeting
We have received more information from Laurent Guise about the intention behind these data objects. These data objects are intended for use-cases where there are different aggregations of the same physical resources. See clause 4.2.5.5.6 Expressing multiple breakdown of the same resource (generation or load) and Figure 24 – Example of modelling two breakdowns of the same set of resources (first controllable, second not controllable). We noted that the explanatory text in this clause does not mention the EqGn, EqLod data objects. EqGn is mentioned in Figure 24, but this is not searchable in the PDF. Decision: propose some explanatory text for part 7-420, and/or for the DO descriptions |
23 Jul 26 |
| Discussion (red) Contact Laurent Guise to see if he can provide some examples. | 14 Nov 25 |
|
Discussion (red)
Page 463 lists the data objects and usage.
EqGn ORG (DGEN) Reference to the equivalent DGEN instance reflecting the generation aspects of the DER (DER_StorageLN) Reference to the equivalent DGEN instance reflecting the generation aspects of storage (DMDR) Reference to the equivalent DGEN instance reflecting the generation aspects of the DER EqLod ORG (DLOD) Reference to the equivalent DLOD instance reflecting the load aspects of the DER (DER_StorageLN) Reference to the equivalent DLOD instance reflecting the load aspects of storage (DMDR) Reference to the equivalent DLOD instance reflecting the load aspects of the DER EqSto ORG (DSTO) Reference to the equivalent DSTO instance reflecting the generic storage aspects of the storage unit (DMDR) Reference to the equivalent DSTO instance reflecting the storage aspects of the DER The references seem appropriate for DER_StorageLN / DSTO to refer to the associated DLOD,DGEN I agree that it makes no sense to have these references: DGEN.EqGn DLOD.EqLd DTSO.EqSTO The description for DMDR should be clarified: If the DMDR represents a combination of no more than 1 DGEN, 1 DLOD, and/or 1 DSTO, then it should be defined with the data objects EqGn, EqLd, EqSTO. If the DMDR represents (or may represent in the future) an aggregation of many resources, then it should be defined with multiple data objects InclGn, InclSto, InclLod. |
04 Nov 25 |
| Discussion (red) Accepted for discussion | 04 Nov 25 |
| Accepted Accepted for discussion | 04 Nov 25 |
|
Triage
Let me revise the last sentence in the proposal.
The first option is preferable. If the second option is adopted, the third option should also be considered. |
09 Apr 25 |