284   icd-to-scd-to-icd clarifications

Created: 31 Jan 2006

Status: In Force (green)

Part: Part 6 (2004)


Page: 10

Clause: 5

Paragraph: all

Category: Issue for edition 2 of this part


There must be a detailed description on the responsibilities for the engineering process in multi-vendor environments. A lot of things are left now in a "gray zone", having negative impact on the user friendliness of the icd-to-scd-to-icd engineering process.


Clause 5 should be extended with a step-by step example of the icd-to-scd-to-icd cycle example, with clear drawn responsibilities for every part involved (what is the IED-specific tool doing? what is the system-specific tool doing?) and with eventual compatibility problems that might arise.

Discussion Created Status
It is not the task of IEC61850 to define detailled tools and engineering processes. Clasue 5 describes clearly the general concept, that an IED has to be accompanied by an ICD file describing its functional and engineering capabilities, and that some system related tool(s) create(s) from this the SCD file, containing the system view as needed by the IED tools for integrating the IED into the system. The task of the IED tool then is to bring this into a language which the IED understands, and load it to the IED. 31 Jan 06 In Force (green)


Privacy | Contact | Disclaimer

Tissue DB v.