Bug #606
LGOS/LSVS mandatory
0%
Tissue 1741
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.
Updated by Carlos Rodriguez del Castillo almost 4 years ago
- Discuss in Upcoming Meeting changed from No to Yes
Updated by Carlos Rodriguez del Castillo almost 4 years ago
- File t1741.PNG t1741.PNG added
- Category changed from Standard clarification required to Already captured with TISSUE
- Status changed from New to In Progress
- Short Proposal set to Tissue 1741
Since tissue is closed as not applicable to 7-4 but it could be applicable to part 6, we need to discuss it in UF TF.
Updated by Carlos Rodriguez del Castillo almost 4 years ago
- ID changed from 2 to 5
- TF Unique ID changed from 2 # H30 to 5 # H30
Updated by Carlos Rodriguez del Castillo almost 4 years ago
- Due date set to 08/16/2021
- Status changed from In Progress to Triage
- To discuss in WG10 set to No
Updated by Carlos Rodriguez del Castillo almost 4 years ago
- Discuss in Upcoming Meeting changed from Yes to No
- Proposal descriptions updated (diff)
- To discuss in WG10 changed from No to Yes
Updated by Carlos Rodriguez del Castillo almost 3 years ago
- Status changed from Triage to Closed
- To discuss in WG10 changed from Yes to No
- LGOS/LSVS is mandatory if an IED declares the supervision capability on Goose/Sampled Values to the number of suscriptions it declares
- An IED could "supervise" a Goose suscription with quality (quest/oldData)
- A user has to ask what they need through BAP or requirement specifications.