Project

General

Profile

Feature #409

Too loose or non existing guideline for organization of structure tree (construction of each LD, LN etc)

Added by Herbert Falk almost 2 years ago. Updated almost 2 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
Standard extension required
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
4.1
Source:
ENTSO-E
TF Unique ID:
4.1 # ENTSO-E
WG10 Proposal:

WG to define types for functions / subfunctions and possible correlation of logical device hierarchyto be adressed to the 61850-6-100 (need a realistic date)

Estimated Completion:
Will be solved with extension of SCL to define function types and subtypes. Input will as well be coming from ENTSO-EDC1 should be soon, but we do not know. Let's see the plenary report
Discuss in Upcoming Meeting:
No
To discuss in WG10:
Short Proposal:

These are a couple of different issues(1) The requirement to standardise logical devices was not idientified so far and goes beyond the interoperability requirement. However, it would help to the end user to understand the functionality of an IED and to harmonise between projects from multiple vendors. With the new concept introduced in part 6, to describe functions / subfunctions, it was as well the idea that the standardisation domains shall define types for functions and subfunctions. This can be a first step. It needs to be discussed if functions / subfunctions shall correlate to logical device hierarchies

Standard(s):
Needs More Information:

Description

Too loose or non existing guideline for organization of structure tree (construction of each LD, LN etc). Manufacturer is filling with their own private parts. Usage of GGIO to cover more then signaling part (wide range of protection function parameters are not covered with predefined LN's). Continuous standardization work is required to standardise commonly used data and data attributes such as protection parameters that are found in most IEDS developed for our domain.

#1

Updated by Herbert Falk almost 2 years ago

  • Status changed from New to In Progress
#2

Updated by Vladan Cvejic almost 2 years ago

  • Subject changed from Too loose or non existing guideline for organization of structure tree (construction of each LD, LN etc). Manufacturer is fillin to Too loose or non existing guideline for organization of structure tree (construction of each LD, LN etc)
  • Short Proposal changed from These are a couple of different issues (1) The requirement to standardise logical devices was not idientified so far and goes beyond the interoperability requirement. However, it would help to the end user to understand the functionality of an IED and to harmonise between projects from multiple vendors. With the new concept introduced in part 6, to describe functions / subfunctions, it was as well the idea that the standardisation domains shall define types for functions and subfunctions. This can be a first step. It needs to be discussed if functions / subfunctions shall correlate to logical device hierarchies to These are a couple of different issues(1) The requirement to standardise logical devices was not idientified so far and goes beyond the interoperability requirement. However, it would help to the end user to understand the functionality of an IED and to harmonise between projects from multiple vendors. With the new concept introduced in part 6, to describe functions / subfunctions, it was as well the idea that the standardisation domains shall define types for functions and subfunctions. This can be a first step. It needs to be discussed if functions / subfunctions shall correlate to logical device hierarchies
  • WG10 Proposal changed from WG to define types for functions / subfunctions and possible correlation of logical device hierarchy to be adressed to the 61850-6-100 (need a realistic date) to WG to define types for functions / subfunctions and possible correlation of logical device hierarchyto be adressed to the 61850-6-100 (need a realistic date)
  • Estimated Completion changed from Will be solved with extension of SCL to define function types and subtypes. Input will as well be coming from ENTSO-E DC1 should be soon, but we do not know. Let's see the plenary report to Will be solved with extension of SCL to define function types and subtypes. Input will as well be coming from ENTSO-EDC1 should be soon, but we do not know. Let's see the plenary report
  • Discuss in Upcoming Meeting set to No

Checking done.

Also available in: Atom PDF