Bug #606
LGOS/LSVS mandatory
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Already captured with TISSUE
Start date:
12/02/2020
Due date:
08/16/2021
% Done:
0%
Estimated time:
ID:
5
Source:
H30
TF Unique ID:
5 # H30
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:
Tissue 1741
Standard(s):
Needs More Information:
Assigned TF:
Description
LGOS/LSVS should be mandatory if GOOSE/SV subscriptions are supported by the IED
Files
Proposal descriptions
Today, we feel it is something that should be explicitly written in the standard, and also in part 6 there should be a way to say LGOS/LSVS is mandatory (IED specification). We have to discuss if it will be in amendment 2.2 or edition 3 but we need it. In the meantime, through user requirements and BAP could be a workaround.
On the other hand, there are some very simple IED implementations that can not have LGOS/LSVS (no MMS) but they have capabilities GOOSE/SV subscribing.
Maybe an ISD is the best way of requiring LGOS/LSVS instead of being mandatory by the standard.