Project

General

Profile

Feature #6739

How to deal with 'Beh' and 'Health' of isolated functions

Added by Michael Haecker 2 months ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Category:
-
Start date:
03/18/2024
Due date:
% Done:

0%

Estimated time:
ID:
Source:
TF Unique ID:
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:
Standard(s):
Needs More Information:
No
Assigned TF:
61850-10-3 (Functional Testing), 61850-80-6 Substation to Control Centre Communication

Description

For site testing, users shall use the test mode to isolate devices/functions to prevent from flooding control centres with test data.

Whereas data marked "test" can be filtered out, changes of 'Beh' cannot be filtered out. When, for example, changing the active parameter set, the user will create data towards the control centre for LN instances which are activated/inactivated through this change.
[Part 7-4 Annex A: "Regardless of the status of LN.Beh, the quality test attribute of Mod, Beh and Health shall be q.test=false."]

In an automation system where a gateway is used to interface the control centre, this gateway could implement a feature to block the information flow of a device in test. Where a direct link via IEC 61850 is used, such blocking is not possible.

#1

Updated by Carlos Rodriguez del Castillo about 1 month ago

  • Status changed from New to In Progress
  • Assignee set to Andreas Ostermeier
  • Discuss in Upcoming Meeting changed from Yes to No
  • Assigned TF 61850-10-3 (Functional Testing), 61850-80-6 Substation to Control Centre Communication added
  • Assigned TF deleted (None)

This issue should be in the scope of 80-6, if we need a standardized solution for this, and 10-3 for the testing.

Also available in: Atom PDF