1400   It is unclear how to subscribe to a GOOSE/SV in SCL

Created: 04 Jun 2015

Status: In Force (green)

Part: Part 6 (2009-12; Edition 2)

Links: #1397 Subscription limitation visible in IxD file




Category: No impact on this part


There are multiple methodologies that could be utilized to configure a subscription to a GOOSE or SV. There needs to be a single mechanism in order to facilitate interoperability and conformance testing.


From the User Feedback TF (Regina, CA):

Subscriptions to GOOSE/SV messages shall be through the configuration of the IEDName in the control block of the publisher to subscribe to a published GOOSE message.

ExtRef shall be used to indicate which DataSet members are to be used from a subscribed message and by which logical node.

Discussion Created Status
16 Jul 15 In Force (green)
The S361 should be S36 (according to ED.2). 24 Jun 15 Ballot Period
With S361 the configuration of IEDName at GOOSE/SV control blocks is already mandatory for a system configuration tool. With Tissue 1397 also the creation of Input sections gets mandatory. It is up to the system engineer to really use these functionality as needed by other tools. 18 Jun 15 Ballot Period
Clarification regarding the discussion during the WG10 meeting in Regina:
- GSEControl.IEDName is useful information for communication and security engineering. Of course it can be be derived from the ExtRefs.
- ExtRefs is useful for signal engineering.
09 Jun 15 Discussion (red)
In the current SCL at each control block the IED intended to receive a message can be specified (for GOOSE and SV the IEDName element).
ExtRef are already defined in SCL as only means to indicate at a receiver / subscriber which data it shall receive. For spontaneous sending this data must be in a data set at the publisher. Thus, from SCL point of view the proposal is fulfilled.
Note also that the editing of the Input section and the creation of the Input section from configured data flow (IEDName at GoCB / SvCB / RCB) is mandatory for a system tool (SICS S37/S38/S39 will become mandatory)
09 Jun 15 Discussion (red)
The publishers IEDName can be derived from the IEDName which points to the data source in the ExtRef. Thus ALL subscribing Information is available at one single place. (ExtRef). The Publisher needs not to know the Receiving IEDs ( Broadcast principle). 07 Jun 15 Triage


Privacy | Contact | Disclaimer

Tissue DB v.