2014 The combination of Ithe EDName value and attributes shall be unique in a given ControlBlock
- Created
- 06 Jan 2026
- Status
- TriageNew, and not yet classified. The working group decides whether to take it forward as a technical issue or to close it. Show the workflow
- Part
- Part 6 (2025; Edition 2.2)
- Links
- None
- Page
- 130
- Clause
- 9.3.10
- Paragraph
- Restrictions
Issue
Nothing is stated regarding the uniqueness of IEDName elements (value and attributes) within a given control block.
See the example bellow, which creates interoperability issues between configuration tools, and is valid with XSD validation.
<GSEControl datSet="DataSet_LPHD1" name="Control_DataSet_LPHD1" confRev="40001" appID="IED1/LIGNE_SYS_IED_1/LLN0/Control_DataSet_LPHD1" type="GOOSE">
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
<IEDName apRef="F">LineIED</IEDName>
Proposal
It should be stated in the standard that the combination of the IEDName value and attributes shall be unique within a given Control Block (e.g., in the "Restrictions" paragraph below Table?28, Attributes of the IEDName element).
| Discussion | Created |
|---|---|
|
Triage
I agree. It is also related to Tissue 1987, where the discussion is about the target information. The Subscription is done at the IED level on a given AP. Not on a given LN.
The LN knows nothing about the message subscription, it only knows about the subscription of an external signal. |
07 Jan 26 |