IEC 61850 User Feedback Task Force

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.