789   ConfLdName as services apllies to both server and client

Created: 25 Oct 2011

Status: In Force (green)

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

Links:

Page:

Clause: Table 11

Paragraph:

Category: Issue may impact interoperability of implementations of Edition 2

Issue

The current ConfLdName definition states:
If this element is present, the IED allows as a server to define functional LD names (by means of the LDevice ldName attribute), and a client can receive and interpret correctly SCL and online messages using this capability
i.e. it applies to server / publisher / client / subscriber. However a subscribr could support the ConfLdName capability of the publisher without offering the ConfLdName itself.

Proposal

Create a new capability for client/subscriber so that the ldNaming reception can be supported without having to supported it in its owns modelling for the server/publisher functionality.

Attachments:
    Note: To see attachments you have to log-in first.

Discussion Created Status
30 May 12 In Force (green)
See final capability extensions in the attached table. 02 May 12 Ballot Period
The solution to this Tissue as well as some more engineering capabilites needed for system tools to understand IED capabilities and to model redundant communication are defined in the attached Excel sheet. 21 Feb 12 Ballot Period

 

Privacy | Contact | Disclaimer

Tissue DB v. 21.10.16.1