Project

General

Profile

Issues #659

sCtl7 allow that bypassing interlocking is "not-supported"

Added by Richard Schimmel over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Due date:
Discuss in Upcoming Meeting:
No
Clause Reference:
Part 7-2 clause 20.5.2.7
61850 Standard:
7-2, 8-1
Triggering Tissue:
Final Decision:
See attachment 20210504
Initial Test Document:
Updated Test Document:
ucatestproceduresserver61850-8-1ed2_...
Test Case ID:
sCtl7
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:

Description

The sCtl7 testcase requires that an IED allows to bypass the interlock check when the Operate.Check-Interlock bit is not set in the request. Several utilities consider this a safety issue and don't allow such bypass to be possible.

It's clearly defined in the standard to perform the Interlock check when Operate.Check.Interlock bit is set. It does not specify the device "shall" bypass the check when the check bit is not set. The proposal is to update sCtl7 to allow the bypass or not. When not the IED shall respond with AddCause "not-supported".

This proposal is agreed upon by Thierry, Joel, Gunnar and Richard.

Files

Redmine sCtl7 proposal to allow bypass or not at step 2.docx Redmine sCtl7 proposal to allow bypass or not at step 2.docx 18 KB Richard Schimmel, 03/29/2021 02:31 AM
Redmine sCtl7 proposal to allow bypass or not at step 2_20210504.docx Redmine sCtl7 proposal to allow bypass or not at step 2_20210504.docx 18.5 KB Bruce Muschlitz, 05/04/2021 08:32 AM

Also available in: Atom PDF