Project

General

Profile

Improvement #5330

LNode iedName attribute usage needs to be clarified

Added by Camille Bloch over 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Standard clarification required
Start date:
03/23/2022
Due date:
% Done:

0%

Estimated time:
ID:
Source:
SCL IOP 2021
TF Unique ID:
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:
Standard(s):

IEC 61850-90-30

Needs More Information:
No
Assigned TF:

Description

During IOP 2021, an SST was using the iedName attribute of LNode to specify the expected IED to implement the LNode in system, and this was seen as an issue by an SCT.

The part 6 do not clearly indicates if the iedName have to be a reference to a real device or if it can be used in such way to specify a name without IED created.

Part 6 indicates that "iedName identifies the IED on which the LN reside", but do not mandate it to exists.

This usage of iedName without virtualIED could be missleading as we do not know if this indicates that the iedName is virtual or if this is an error in the configuration because the IED is not correctly configured.

Proposal descriptions

@Editor of Part 6 - (for Amendment 2) - additional statement required to clearly state/clarify how and when to use iedName and what does it mean when, for example, no virtual IED is present.

@Editor of Part 6-100 - clarification has to be in line with work in 6-100. Generic requirement: to show how external files are integrated/merged into the project.

Part 6-100 is now 61850-90-30.

Also available in: Atom PDF