Project

General

Profile

Feature #6218

Parameters not available in standardized LN - PhyConnITF

Added by Carlos Rodriguez del Castillo almost 2 years ago. Updated over 1 year ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
Standard extension required
Start date:
11/24/2020
Due date:
05/24/2021 (over 3 years late)
% Done:

0%

Estimated time:
ID:
53
Source:
RTE
TF Unique ID:
53 # RTE
WG10 Proposal:

Clarification from RTE is needed, If the goal is to indicate the type of interface, Communication section could be used to model this interface

Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:
Standard(s):

IEC 61850-7-4

Needs More Information:
Yes
Assigned TF:

Description

New parametres need to be modelled since they are not available in standard LNs.
This issue refer to PhyConnITF parameter, as explained in the attached documents by RTE.


Files

20210326-RTE Use cases 622.docx 20210326-RTE Use cases 622.docx 20.2 KB Use case explanation Carlos Rodriguez del Castillo, 05/25/2021 10:14 AM
20210326-RTE Use cases 622_v2.docx 20210326-RTE Use cases 622_v2.docx 24 KB more details on use cases Maud Merley, 12/04/2022 11:56 PM

Proposal descriptions

Last WG10 comment: Clarification from RTE is needed, If the goal is to indicate the type of interface, Communication section could be used to model this interface


Related issues

Copied from IEC 61850 User Feedback Task Force - Feature #6217: Parameters not available in standardized LN - NamAccRtgIn Progress11/24/202005/24/2021

Actions
Copied to IEC 61850 User Feedback Task Force - Feature #6219: Parameters not available in standardized LN - VRtg, ARtg and HzRtgIn Progress11/24/202005/24/2021

Actions
#1

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Copied from Feature #6217: Parameters not available in standardized LN - NamAccRtg added
#2

Updated by Carlos Rodriguez del Castillo almost 2 years ago

WG10 comment:
PhyConnITF: Clarification from RTE is needed, If the goal is to indicate the type of interface, Communication section could be used to model this interface.
RTE comment:
The use case is to express the communication interface of line differential protections. It is true that this communication interface could be expressed in the communication part,
but in this case it is not clear which SubNetwork protocol type should be used (enumeration restricted to IP, 8-MMS, and physical), if the communication interface is not an IP type.
To be clarified by the TF: should proprietary communication between IEDs at the 2 ends of the line be expressed as AP?

#3

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Copied to Feature #6219: Parameters not available in standardized LN - VRtg, ARtg and HzRtg added
#4

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • ID changed from 19 to 53
  • TF Unique ID changed from 19 # RTE to 53 # RTE
#5

Updated by Vladan Cvejic over 1 year ago

  • Status changed from New to In Progress
#6

Updated by Vladan Cvejic over 1 year ago

It is concluded that issue has to be presented and discussed on next joint meeting of TC57 & TC38 & TC95 in Lyon (May 25th, 2023). Will be presented by Maud Merley.

#7

Updated by Vladan Cvejic over 1 year ago

  • Discuss in Upcoming Meeting changed from Yes to No

Also available in: Atom PDF