G2 IMPLEMENTATION MODEL FOR GOOSE CONFIGURATION VIA SCL
CHAPTER 3: IEC 61850 COMMUNICATION
A variation of this sequence is to use the manufacturer's IED setup tool before the Configurator. In this case, the
Configurator begins by importing the IID file rather than the ICD file.
IID files can also be used long after the project is over to verify that the project settings are still present in the IED. The IID
file contains the values of configRev, paramRev, and confRev, which are identical to those in the CID file if no setting
changes have been made since the CID file was loaded.
3.10.3 Configuration process with IED setup tool
The GOOSE configuration process can also be completed up to the point where the configuration is sent to the IED without
involving the IED. The IED setup tool provides the same ability as the IED to generate ICD and IID files and to consume CID
files. See the following figure.
Use of the IED setup tool for configuring GOOSE is optional under normal conditions. However, if the hardware
configuration of the IED is changed, for instance by changing the number or type of contact I/O modules, use of the IED
setup tool can be required.
Figure 3-15: SCL file flow using IED setup tool
3.10.4 IED Capability Description (ICD) file
The ICD file contains one SCL element. The SCL element contains one Header element, one Communication element, and
one IED element.
The Header element contains an id element attribute that has the make and model of the applicable IED.
The ICD file describes an information model compliant with the standards that models all values that the IED is able to
publish via GOOSE. These values are modeled within the so-called Public elements, that is, elements other than Private
UR FAMILY – COMMUNICATIONS GUIDE