GE Multilin G30 Generator Protection System C-15APPENDIX C C.5 IEC 61850 IMPLEMENTATION VIA ENERVISTA UR SETUPCThe root file structure of an ICD file is illustrated below.Figure C–2: ICD FILE STRUCTURE, SCL (ROOT) NODEThe Header node identifies the ICD file and its version, and specifies options for the mapping of names to signalsThe Communication node describes the direct communication connection possibilities between logical nodes by means oflogical buses (sub-networks) and IED access ports. The communication section is structured as follows.Figure C–3: ICD FILE STRUCTURE, COMMUNICATIONS NODEThe SubNetwork node contains all access points which can (logically) communicate with the sub-network protocol andwithout the intervening router. The ConnectedAP node describes the IED access point connected to this sub-network. TheAddress node contains the address parameters of the access point. The GSE node provides the address element for stat-ing the control block related address parameters, where IdInst is the instance identification of the logical device within theIED on which the control block is located, and cbName is the name of the control block.The IED node describes the (pre-)configuration of an IED: its access points, the logical devices, and logical nodes instanti-ated on it. Furthermore, it defines the capabilities of an IED in terms of communication services offered and, together withits LNType, instantiated data (DO) and its default or configuration values. There should be only one IED section in an ICDsince it only describes one IED.842795A1.CDRSCLHeader (id, version, revision, toolID, nameStructure)CommunicationIED (name, type, manufacture, configVersion)DataTypeTemplates842796A1.CDRCommunicationSubNetwork (name)ConnectedAP (iedName, apName)AddressGSE (IdInst, cbName)P (type)Other P elementsTextAddressP (type)Other P elementsTextOther GSE elements
