In our aproach to the LN philosopy, we encounter that it is more usefull to add all the input/output connections for the proper functionality of the LN as new extended Data Atrributes (CF type). This has the advantage that the present configuration of this connection can be reached by using ACSI services, it can be on line modified and stored as it is standardized for the other CF type attributes. Then if extended logical nodes are used for LEDS, local MMI´s, BIOs etc… all internal conections as well as external can be bounded to data attributes CF type.
To include as extensions the internal/external connection for the LN´s as CF type attributes instead of an auxiliary “Binding to external signals”
First Proposal – Functional Naming:
The proposal is backward compatible with the current SCL files, as long as only IED related naming has been used. If functional naming had been used, then the functional name now must be explicitly written into the LDevice name attribute.
With this proposal the FuncName tag of the header becomes superfluous, except if the option shall exist to use IED related naming, although an LD name has been specified. On the other side it may be that IED CID files demand that the LD name is always in the name attribute, even for IED related names – which could then automatically be generated. These options should be discussed and decided.
If there is now a unique functional LD name at the IED, it seems natural to introduce this also as a reference at the Substation part LNode tags. This allows a customer to define functionally already all LDs he needs within an SSD file. In case that this LNode is later allocated to an IED, the choosen IED LD can take over the LD name. This might however lead to problems if the IEDs LD structure does not match that foreseen in the SSD file, which might lead to interpretation problems. Therefore, this option shall be clearly restricted to SSD files, with ldName reference removed (and may be taken over to IED LDevice name – this is then a local issue of the engineering tool) after allocation of LNode to a ‘real’ IED. This means that the ldName attribute instead of the ldInst attribute of the LNode element in the Substation section is only allowed as long as iedName=None.
This option should be discussed and decided.
Rejected. Not necessary for interoperability, outside philosophy of current data model; similar effect per project can be reached by using the SCL Extref/Input section (which can be stored onto the IED as CID file).
13 Jun 05
First of all:
"Annex A. First Proposal – Functional Naming: ..." as shown in the tissue belongs to tissue # 18. Ignore this text here!
Result of discussion for final proposal:
Comment is not accepted.