1955 Relationship between GSESettings and GSE
- Created
- 24 Jan 2025
- Status
- Discussion (red)Open for discussion while the solution is worked out. Any signed-in reader may comment. Show the workflow
- Part
- Part 6 (2025; Edition 2.2)
- Links
- None
- Page
- 147
- Clause
- 9.4.4
- Paragraph
- 1
Issue
Some implementation consider that the GSESetting service is applicable also to GSE element, but as per 8-1 the GSE element and attributes shall be editable by the SCT.
The GSESetting is only about GOOSE control block attributes editability.
Proposal
Add a statement in GSE addres element indicating that GSE is always editable (creation, removal and edition of attributes) as soon as a GOOSE control block exists.
And add a statement in GSESetting service definition that it not applies to GSE.
This is also applicable to SMV
| Discussion | Created |
|---|---|
| Discussion (red) proposal to provide | 10 Oct 25 |
| Accepted accepted | 10 Oct 25 |
|
Triage
Agree with the proposal, Part 8-1 already mandates that the SCT is always allowed to edit the content of a GSE. Tissue 1956 is clarifying that it is also the case for SMV.
This should be treated as an interop tissue because it is creating interoperability issue during integration of devices. |
10 Feb 25 |