Project

General

Profile

Feature #599

ICD files do not match requirements (several issues) - increase in engineering efforts

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

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Profile or Guideline
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
12
Source:
IOP_2019
TF Unique ID:
12 # IOP_2019
WG10 Proposal:

Generate guideline of best practices.Feb-20: Check with BruceJun-20: Check with Herb

Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:

Generate WP of best practices.IOP to record a best practices guideline as a result of the IOP

Standard(s):
Needs More Information:

Description

ICD files did not match requirements.

The icd file delivered for the initial configuration had a generic (out of the box) data model. The SCT was not able to map all required information into the IED – multiple iterations were required until the ICD file was finally reflecting the requirements.

Sometimes, that was just the data model as such (i.e., the control of a switch (CSWI.Pos) was preconfigured as status-only and could not be changed by the tool as the data model did not provide the structure for control) – the system design engineer had to communicate verbally with the IED what is needed and got a new file back with the modifications in the IED tool.

Sometimes, GOOSE messages could not be configured. Again – through verbal interaction, the system design engineer told the IED design engineer what he needs as signals and the IED engineer configured the dataset for the GOOSE control block accordingly, such that it could then support the requirements. This required additional iterations.

The process needs to be clarified! According the standard, an icd file is a – if needed pre-configured – file that matches the requirements from the substation. The less flexibility an IED tool provides regarding configurability by the system tool, the more preconfiguration is needed. That requires the essential design work to be done in multiple tools.

To avoid this, the standard should enforce flexibility of the IED tools with regard to engineering capabilities through the system tool.


Proposal descriptions

UCAIug to generate guideline of best practices.

#1

Updated by Vladan Cvejic almost 2 years ago

  • Subject changed from ICD files did not match requirements. The icd file delivered for the initial configuration had a generic (out of the box) data to ICD files do not match requirements (several issues) - increase in engineering efforts
  • Status changed from New to In Progress
  • Short Proposal changed from Generate WP of best practices. IOP to record a best practices guideline as a result of the IOP to Generate WP of best practices.IOP to record a best practices guideline as a result of the IOP
  • WG10 Proposal changed from Generate guideline of best practices. Feb-20: Check with Bruce Jun-20: Check with Herb to Generate guideline of best practices.Feb-20: Check with BruceJun-20: Check with Herb
  • Discuss in Upcoming Meeting set to No

Checking done.

#2

Updated by Carlos Rodriguez del Castillo 7 months ago

  • Discuss in Upcoming Meeting changed from No to Yes
#3

Updated by Vladan Cvejic 7 months ago

  • Status changed from In Progress to Resolved
  • Discuss in Upcoming Meeting changed from Yes to No
  • Proposal descriptions updated (diff)
  • To discuss in WG10 set to No

Also available in: Atom PDF