354 There is no SCL configuration feedback that reflect local changes.

View All Issues for Part 6 (2004)

If you want to see other tissues for this part.

This tissue has following status: blue

Proposer: Herb Falk , SISCONET

Page: 19

Clause: 7

Paragraph:

Category: Issue for edition 2 of this part

Issue: The general flow of SCL information is a ICD (can be generated by the IED vendor's tool) is provided to a system configuration tool. This tool, in turn, generates an SSD or SCD file. The SCD file can be compressed for exchange to the IED vendor's tool as a CID. The IED vendor's tool then reconfigures the IED.

As part of the reconfiguration, the user at the vendor's tools makes settings/mapping/initial value/GOOSE configuration modifications. How do these changes get fed back into the SCL configuration workflow?

In theory, the IED vendor's tools should re-generate a CID file that can be provided to the system configuration tool. However, there is no requirement in Part 6 that mandates this.

This capability needs to be fully specified with the appropriate schema modification to allow IED vendor tools to export a revised CID.

Proposal: This capability needs to be fully specified with the appropriate schema modification to allow IED vendor tools to export a revised CID.

Discussion	Created	Status ?	Ballot until	Editor
According to the intent of the current version of the standard, the IED tool has to modify the SCD file, which then can be reimported to the same or another system level tool, or to another (station level) IED tool needing this information. It is accepted that this should be explained more explicitely. There is already some work ongoing in this direction for the standardisation of SS - SS communication.	04 Aug 06	blue		ABB Wolfgang Wimmer