Created: 03 Jun 2015
Status: In Force (green)
Part: Part 7-1 (2011; Edition 2)
Links: #1401 Supervision of GOOSE/SV capabilities
Category: Issue for edition 2 of this part
Currently, there is no defined methodology to manage/configure LGOS and LSVS in an interoperable fashion. As an example, it is unclear if there needs to be a LGOS for every GOOSE subscription and how the binding between the subscription and LGOS instance that is supervising the subscription.
From the User Feedback Taskforce (Regina June 2015):
1). For IEDs, each GOOSE/SV subscription, there shall be one LGOS or LSVS provided. If the IEDs that have only ClientServices, then there need not be an instantiation of LGOs or LSVS.
2). For IEDs that have supervision capabilities, the ICD shall contain at least one installation (e.g. LNInst) of that supervision function. It shall not provide instances that number more than the maximum number of subscriptions declared in the Service Capabilities.
3). If the number of configured subscriptions exceeds the number of supervision Logical Nodes, then the SCD needs to be provided to the appropriate ICT. The exported IID shall contain, as a minimum, the number of supervision logical nodes that match the number of descriptions.
4). If # of supervision logical nodes (e.g. LGOS) = # of subscriptions (e.g. GOOSE subscription) required by the design (in the SCD),
- If valImport = TRUE, the SCT can configure the reference between the LGOS and the GCB
- If valImport = FALSE, a round trip is needed between ICT and SCT. The ICT shall then assign/configure the supervision logical nodes.
5). If # of supervision (e.g. LGOS) is larger than # of subscription (e.g. GOOSE subscriptions) required by the design (in the SCD), and the SCT could assign the LGOS to subscribed GCB, the ICT may delete the remaining LGOS (and update the SCT trough roundtrip).
6). If # of LGOS larger or equal to # of GOOSE subscription required by the design (in the SCD), and the SCT did not assign the LGOS to subscribed GCB, the ICT assigns the LGOS to GCB and may delete the unused LGOS (and update the SCT trough roundtrip).
7). If a round trip is needed, once the ICT has configured relations between a LGOS and a GCB, and later a GOOSE susbscription is deleted, ICT may not reconfigure the already existing relations between LGOS and GCB (e.g. we have LGOS1 and LGOS2 configured to two GOOSE susbcriptions, if later the first GOOSE subscription is deleted, the second one must remain associated to LGOS2). However, if later a new subscription is added, it may reuse LGOS1.
NOTE: if a LGOS has no GCB associated (reference = empty string), that means that this LGOS is not active. This can be further generalized: whenever we have an ORG data object with an empty string it means that there is no object referenced.