Project

General

Profile

Support #425

Restrictions in the configuration to be described in the ICD Service section

Added by Herbert Falk about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Standard clarification required
Start date:
Due date:
% Done:

0%

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

We shall extend the standard to declare the restriction.We may as well have to create recommendations to vendors.But we may further consider that the standard in the future provides already the restrictions (e.g. mandate all control blocks in LLN0)June 2014: Basic idea not to add new restrictions; IED vendors shall follow the standard. A recommendation can be created that provides recommendation to the IED manufacturer about reasonable and not reasonable restrictions. Need as well verify that test cases are good to verify all this.Closed because already included in Ed 2.1 of part 6

Estimated Completion:
Ed 2.1 or Ed 3 of part 6by November 2014 prepare draft recommendation (Jörg (lead), Bruce, Pierre, Chris)
Discuss in Upcoming Meeting:
No
To discuss in WG10:
Short Proposal:

some of these restrictions have been added in Ed 2 or Ed 2.1; the remaining ones need to be addes to SCL. See item 3 (2). PIXIT shall be fully covered by IED service elementWG10 Discussion:Discussion WG10 in Houston: Identify from the PIXITs what is relevant for interoperability / engineering of the system and verify if all that is available in SCLBesides that, there may be the case that devices allow the creation of datasets or report control blocks, but not necessarily within any LN. This is a restriction not currently supported by the standard but exists in devices.

Standard(s):

IEC 61850-6

Needs More Information:
Assigned TF:

Description

Restrictions in the configuration (GOOSE, REPORTS, DATASET) shall be described in the ICD Service section and explained completely in the PIXIT. This will allow (vendor independant) tools to configure the communication via SCD file.

#1

Updated by Herbert Falk about 3 years ago

  • Status changed from New to Closed
#2

Updated by Carlos Rodriguez del Castillo about 3 years ago

  • Subject changed from Restrictions in the configuration (GOOSE, REPORTS, DATASET) shall be described in the ICD Service section and explained complete to Restrictions in the configuration to be described in the ICD Service section
  • Short Proposal changed from some of these restrictions have been added in Ed 2 or Ed 2.1; the remaining ones need to be addes to SCL. See item 3 (2). PIXIT shall be fully covered by IED service element WG10 Discussion: Discussion WG10 in Houston: Identify from the PIXITs what is relevant for interoperability / engineering of the system and verify if all that is available in SCL Besides that, there may be the case that devices allow the creation of datasets or report control blocks, but not necessarily within any LN. This is a restriction not currently supported by the standard but exists in devices. to some of these restrictions have been added in Ed 2 or Ed 2.1; the remaining ones need to be addes to SCL. See item 3 (2). PIXIT shall be fully covered by IED service elementWG10 Discussion:Discussion WG10 in Houston: Identify from the PIXITs what is relevant for interoperability / engineering of the system and verify if all that is available in SCLBesides that, there may be the case that devices allow the creation of datasets or report control blocks, but not necessarily within any LN. This is a restriction not currently supported by the standard but exists in devices.
  • WG10 Proposal changed from We shall extend the standard to declare the restriction. We may as well have to create recommendations to vendors. But we may further consider that the standard in the future provides already the restrictions (e.g. mandate all control blocks in LLN0) June 2014: Basic idea not to add new restrictions; IED vendors shall follow the standard. A recommendation can be created that provides recommendation to the IED manufacturer about reasonable and not reasonable restrictions. Need as well verify that test cases are good to verify all this. Closed because already included in Ed 2.1 of part 6 to We shall extend the standard to declare the restriction.We may as well have to create recommendations to vendors.But we may further consider that the standard in the future provides already the restrictions (e.g. mandate all control blocks in LLN0)June 2014: Basic idea not to add new restrictions; IED vendors shall follow the standard. A recommendation can be created that provides recommendation to the IED manufacturer about reasonable and not reasonable restrictions. Need as well verify that test cases are good to verify all this.Closed because already included in Ed 2.1 of part 6
  • Estimated Completion changed from Ed 2.1 or Ed 3 of part 6 by November 2014 prepare draft recommendation (Jörg (lead), Bruce, Pierre, Chris) to Ed 2.1 or Ed 3 of part 6by November 2014 prepare draft recommendation (Jörg (lead), Bruce, Pierre, Chris)
  • Discuss in Upcoming Meeting set to No

Checking done.

#3

Updated by Carlos Rodriguez del Castillo about 3 years ago

  • Standard(s) set to IEC 61850-6

Also available in: Atom PDF