Logical node properties

When a logical node is selected, the Properties view shows the following attributes selected, the Properties view shows the following attributes

• Application Roles
  This field shows configuration related to application templating. It is mostly informative, although it is editable to cover edge cases. During normal engineering, this field is not supposed to be modified manually by the user.

• Current / Specified Prefix, LN Class, Inst
  A logical node is uniquely identified by the combined quintuple of Prefix, LN Class, Inst, IEDName, LDInst attributes. If the IEDName is not ‘None’, this also establishes a mapping of a logical node in the Specification to an implementing logical node in a device. The set of ‘Specified’ attributes always retain the originally specified value, while the ‘Current’ set reflects the mapping.

• Current / Specified LN Type
  The LN Type of a logical node controls what data objects are available to this logical node. As with the identifying attributes, the LN Type will change when the logical node is mapped to an implementing logical node in a device.

• Description
  The description field serves as a quick documentation. The corresponding TLNode SCL element will also contain this description. The generated pdf documentation will contains the description field.

• Document Reference
  This field shows the path to the Word document that is attached as reference to this logical node and use on the pdf documentation generation.

• Engineering Status
  Possible values are ‘Specified’, ‘Implemented’, and ‘Error’. An error status will also be indicated by a red ‘x' marker to the right of the logical node. A node will have an ‘Error’ status when any of its signals can not be correctly resolved (See Configure Signals ). A logical node that is mapped to a device will have a status of ‘Implemented’, an unmapped node will be ‘Specified’.

• IED Name
  If the logical node is in ‘Specified’ state, this will use the reserved keyword ‘None’, otherwise the name of the implementing IED.

• Implementation only
  This indicates whether a logical node has been modelled as part of the specification, or was brought in from a device during system integration. See Virtual IEDs (Mapping logical nodes).

• LDInst
  If the logical node is in ‘Specified’ state, this will contain the hierarchical path to the function that contains this node. However, this behaviour is purely convenience - there is no semantic requirement on the LDInst while the IED Name is set to ‘None’.

• Prefix update strategy
  For some utilities, the modelling expects the logical node prefix to reflect some part of the architecture. The possible settings are: ‘None’, ‘Function name’, ‘Equipment name’, and ‘Parent name’. For strategies other than ‘None’, the specified prefix will be set to the chosen attribute, and will change if that attribute is renamed. The result of ‘Parent name’ depends on the state of the function that contains the logical node - if it is set to ‘Suppressed in SCL’, the name of the containing bay or conducting equipment is used, otherwise the functions name.