CDV61850-6©1EC:2002 -6- 57WG10 2 Normative References The following normative documents contain provisions that,through reference in this text. constitute provisions of this International Standard.At the time of publication,the editions in- dicated were valid.All normative documents are subject to revision,and parties to agree- ments based on this International Standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below.Members of IEC and ISO maintain registers of currently valid International Standards. W3C,Extensible Markup Language (XML)1.0,http://www.w3.org/TR/2000/REC-xml- 20001006 W3C.Name spaces in XML,http://www.w3.org/TR/1999/REC-xml-names-19990114 W3C,XML Schema Part 0:Primer,http://www.w3.org/TR/2001/REC-xmlschema-0-20010502 W3C,XML Schema Part 1:Structures,http://www.w3.orq/TR/2001/REC-xmlschema-1- 20010502 W3C,XML Schema Part 2:Data Types,http://www.w3.org/TR/2001/REC-xmlschema-2- 20010502/ RFC 1953.GZIP file format specification version 4.3,http://www.ietf.org/rfc/rfc1952.txt IEC 61850-5,Communication networks and systems in substations-Part 5:Communication Requirements for functions and device models IEC 61850-7-1,Communication networks and systems in substations-Part Basic communi- cation structure for substations and feeder equipment-Principles and models IEC 61850-7-2,Communication networks and systems in substations-Part Basic communi- cation structure for substations and feeder equipment -Abstract communication service in- terface(ACSI) IEC 61850-7-3,Communication networks and systems in substations-Part Basic communi- cation structure for substations and feeder equipment-Common data classes IEC 61850-7-4,Communication networks and systems in substations-Part Basic communi- cation structure for substations and feeder equipment-Compatible logical node classes and data classes IEC 61850-8-1,Communication networks and systems in substations Part 8-1:Specific Communication Service Mapping (SCSM)-Mapping to MMS(ISO/IEC 9506 Part 1 and Part 2) IEC 61850-9-1,Communication networks and systems in substations -Part 9-1:Specific Communication Service Mapping (SCSM)-Serial unidirectional multidrop point to point link IEC 61850-9-2,Communication networks and systems in substations -Part 9-2:Specific Communication Service Mapping(SCSM)-Mapping on a IEEE 802.3 based process bus IEC 61346-1:1996,Industrial systems,Installation and equipment and industrial products Structuring principles and reference designations-Part 1:Basic rules Version 8CDV,August 2002
CDV 61850-6 © IEC:2002 – 6 – 57/WG10 Version 8CDV, August 2002 2 Normative References The following normative documents contain provisions that, through reference in this text, constitute provisions of this International Standard. At the time of publication, the editions indicated were valid. All normative documents are subject to revision, and parties to agreements based on this International Standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. Members of IEC and ISO maintain registers of currently valid International Standards. W3C, Extensible Markup Language (XML) 1.0, http://www.w3.org/TR/2000/REC-xml- 20001006 W3C, Name spaces in XML, http://www.w3.org/TR/1999/REC-xml-names-19990114 W3C, XML Schema Part 0: Primer, http://www.w3.org/TR/2001/REC-xmlschema-0-20010502 W3C, XML Schema Part 1: Structures, http://www.w3.org/TR/2001/REC-xmlschema-1- 20010502 W3C, XML Schema Part 2: Data Types, http://www.w3.org/TR/2001/REC-xmlschema-2- 20010502/ RFC 1953, GZIP file format specification version 4.3, http://www.ietf.org/rfc/rfc1952.txt IEC 61850-5, Communication networks and systems in substations – Part 5: Communication Requirements for functions and device models IEC 61850-7-1, Communication networks and systems in substations – Part Basic communication structure for substations and feeder equipment – Principles and models IEC 61850-7-2, Communication networks and systems in substations – Part Basic communication structure for substations and feeder equipment – Abstract communication service interface(ACSI) IEC 61850-7-3, Communication networks and systems in substations – Part Basic communication structure for substations and feeder equipment – Common data classes IEC 61850-7-4, Communication networks and systems in substations – Part Basic communication structure for substations and feeder equipment – Compatible logical node classes and data classes IEC 61850-8-1, Communication networks and systems in substations – Part 8-1: Specific Communication Service Mapping (SCSM) – Mapping to MMS(ISO/IEC 9506 Part 1 and Part 2) IEC 61850-9-1, Communication networks and systems in substations – Part 9-1: Specific Communication Service Mapping (SCSM) – Serial unidirectional multidrop point to point link IEC 61850-9-2, Communication networks and systems in substations – Part 9-2: Specific Communication Service Mapping (SCSM) – Mapping on a IEEE 802.3 based process bus IEC 61346-1: 1996, Industrial systems, Installation and equipment and industrial products – Structuring principles and reference designations – Part 1: Basic rules
CDV61850-6©1EC:2002 -7- 57WG10 3 Definitions In general the glossary defined in part 2 of this standard apply.The following definitions are used in this part additionally or with some added semantics: 3.1 Access point a communication access point to an IED.This may be a serial port,an Ethernet connection. or a client or server address dependent on the used stack.Each access point of an IED to a communication bus is uniquely identified.Each server has exactly one (logical)access point. 3.2 Subnetwork a communication system connection between IEDs with serial communication facilities.All devices connected to a subnetwork can directly communicate to each other,without an inter- vening router.Routers or gateways can connect subnetworks. 3.3 Device any physical device,not only IEDs as in the other parts of IEC 61850.In the context of a switchyard these are primary apparatuses like transformers and circuit breakers,in the con- text of substation automation all IEDs. 3.4 Connectivity node(ConNode) a connectivity node is a connection point between terminals of primary devices which has the only task to connect them electrically with no resistance;e.g.a bus bar as connectivity node connects bus bar disconnectors.The connection to a device is done at a device terminal.A connectivity node can connect an arbitrary number of terminals(devices). 3.5 Subdevice a part of a PrimaryDevice,which might especially be a phase of a three-phase device Version 8CDV,August 2002
CDV 61850-6 © IEC:2002 – 7 – 57/WG10 Version 8CDV, August 2002 3 Definitions In general the glossary defined in part 2 of this standard apply. The following definitions are used in this part additionally or with some added semantics: 3.1 Access point a communication access point to an IED. This may be a serial port, an Ethernet connection, or a client or server address dependent on the used stack. Each access point of an IED to a communication bus is uniquely identified. Each server has exactly one (logical) access point. 3.2 Subnetwork a communication system connection between IEDs with serial communication facilities. All devices connected to a subnetwork can directly communicate to each other, without an intervening router. Routers or gateways can connect subnetworks. 3.3 Device any physical device, not only IEDs as in the other parts of IEC 61850. In the context of a switchyard these are primary apparatuses like transformers and circuit breakers, in the context of substation automation all IEDs. 3.4 Connectivity node (ConNode) a connectivity node is a connection point between terminals of primary devices which has the only task to connect them electrically with no resistance; e.g. a bus bar as connectivity node connects bus bar disconnectors. The connection to a device is done at a device terminal. A connectivity node can connect an arbitrary number of terminals (devices). 3.5 Subdevice a part of a PrimaryDevice, which might especially be a phase of a three-phase device
CDV61850-6©1EC:2002 -8- 57WG10 4 Abbreviations In general the glossary and abbreviations defined in part 2 of this standard apply.The fol- lowing abbreviations are particularly useful for understanding this part and are repeated here for convenience CIM Common Information Model of IEC 61970-301 DO DATA in IEC61850-7-2,Data object class or instance,depending on context DTD Document Type Definition SCL Substation Configuration description Language UML Unified Modelling Language according to Booch Jacobson Rumbaugh URI Universal Resource Identifier XML Extensible Markup Language Version 8CDV,August 2002
CDV 61850-6 © IEC:2002 – 8 – 57/WG10 Version 8CDV, August 2002 4 Abbreviations In general the glossary and abbreviations defined in part 2 of this standard apply. The following abbreviations are particularly useful for understanding this part and are repeated here for convenience. CIM Common Information Model of IEC 61970-301 DO DATA in IEC61850-7-2, Data object class or instance, depending on context DTD Document Type Definition SCL Substation Configuration description Language UML Unified Modelling Language according to Booch / Jacobson / Rumbaugh URI Universal Resource Identifier XML Extensible Markup Language
CDV61850-6©1EC:2002 -9- 57WG10 5 Intended engineering process with SCL Engineering of a Substation Automation system may start either with the allocation of func- tionally pre-configured devices to switchyard parts/products functions,or with the design of the process functionality,where the allocation of functions to physical devices is made later based on functional capabilities of devices and their configuration capabilities.Often a mixed approach is preferred:a typical process part such as a line bay is pre-engineered,and then the result is used within the process functionality as often as needed.For SCL this means, that it must be capable of describing: 1.Pre-configured IEDs with a fixed number of logical nodes (LNs),but with no binding to a specific process-only may be a relation to a very general process function part. 2.Pre-configured IEDs with a pre-configured semantic for a process part of a certain struc- ture,e.g.a double busbar GIs line feeder. 3.Complete process configuration with all IEDs bound to individual process functions and primary equipment,enhanced by the access control object definitions (access allow- ances)for all possible clients. 4.As item 3 above,but additionally all predefined associations and client server connec- tions between logical nodes on data level.This is needed if an IED is not capable of dy- namically building associations or reporting connections (either on client or on server side). The last case is the complete case.Both case 3 and 4 are the result after SAS engineering while cases 1 and 2 are possible results after IED pre-engineering. The scope of SCL as defined in this document is clearly restricted to these purposes: 1.IED capability description(points 1 and 2 above) 2.System description(points 3 and 4 above) for the purpose of system communication engineering and description of the engineered system communication for the device engineering tools in a standardised way. The resulting object model however could also be the base for other engineering tasks,either directly,or with some additions.Therefore,and because of additional needs of SCSMs,this standard considers the language as defined here as the core model,and defines,how exten- sions of this core model for SCSMs as well as other (engineering)purposes can be done in a standardised way. Figure 2 explains the usage of SCL data exchange in the above mentioned engineering proc- ess.The grey shaded boxes above the dashed line indicate where SCL files are used.The box /ED capabilities corresponds to a result of steps 1 and 2 above,the other box to steps 3 respective 4 above The IED configurator is a manufacturer specific tool that shall be able to import export data (e.g.files)defined by this part of the standard.It provides IED specific settings and gener- ates IED specific configuration files,or it loads the IED configuration into the IED. An IED shall only be considered compatible in the sense of this standard series,if Version 8CDV,August 2002
CDV 61850-6 © IEC:2002 – 9 – 57/WG10 Version 8CDV, August 2002 5 Intended engineering process with SCL Engineering of a Substation Automation system may start either with the allocation of functionally pre-configured devices to switchyard parts / products / functions, or with the design of the process functionality, where the allocation of functions to physical devices is made later based on functional capabilities of devices and their configuration capabilities. Often a mixed approach is preferred: a typical process part such as a line bay is pre-engineered, and then the result is used within the process functionality as often as needed. For SCL this means, that it must be capable of describing: 1. Pre-configured IEDs with a fixed number of logical nodes (LNs), but with no binding to a specific process - only may be a relation to a very general process function part. 2. Pre-configured IEDs with a pre-configured semantic for a process part of a certain structure, e.g. a double busbar GIS line feeder. 3. Complete process configuration with all IEDs bound to individual process functions and primary equipment, enhanced by the access control object definitions (access allowances) for all possible clients. 4. As item 3 above, but additionally all predefined associations and client server connections between logical nodes on data level. This is needed if an IED is not capable of dynamically building associations or reporting connections (either on client or on server side). The last case is the complete case. Both case 3 and 4 are the result after SAS engineering, while cases 1 and 2 are possible results after IED pre-engineering. The scope of SCL as defined in this document is clearly restricted to these purposes: 1. IED capability description (points 1 and 2 above) 2. System description (points 3 and 4 above) for the purpose of system communication engineering and description of the engineered system communication for the device engineering tools in a standardised way. The resulting object model however could also be the base for other engineering tasks, either directly, or with some additions. Therefore, and because of additional needs of SCSMs, this standard considers the language as defined here as the core model, and defines, how extensions of this core model for SCSMs as well as other (engineering) purposes can be done in a standardised way. Figure 2 explains the usage of SCL data exchange in the above mentioned engineering process. The grey shaded boxes above the dashed line indicate where SCL files are used. The box IED capabilities corresponds to a result of steps 1 and 2 above, the other box to steps 3 respective 4 above. The IED configurator is a manufacturer specific tool that shall be able to import / export data (e.g. files) defined by this part of the standard. It provides IED specific settings and generates IED specific configuration files, or it loads the IED configuration into the IED. An IED shall only be considered compatible in the sense of this standard series, if
CDV61850-6©1EC:2002 -10- 57WG10 It is accompanied either by an SCL file describing its capabilities,or by a tool,which can generate this file from the IED. It can use a system SCL file to set its communication configuration,as far as setting is possible at all (i.e.as a minimum its needed addresses),ot it is accompanied by a tool which can import a system SCL file to set these parameters to the IED. The System configurator is an IED independent system level tool that shall be able to import/ export data(e.g.files)defined by this part of the standard.It imports configuration files from several IEDs,as needed for system level engineering,and used by the configuration engi- neer to add system information shared by different IEDs.Then the system configurator gen- erates a substation related configuration file as defined by this part of the standard,which may be fed back to the IED configurator for system related IED configuration. IED Capabilities (LN.DO) IED Database System Con- figurator Association Pre-configured exchanges Relationship to primary topology Engineering Workstation IED Confi- gurator File Transfer(REMOTE) File Transfer (LOCAL) Substation Gate- way IEC61850 Service IED IED IED IED Figure 2-Reference model for information flow during the configuration process The part below the dashed line of Figure 2 indicates the ways in which IED configuration data produced by means of the IED configurator can be brought into the IED.This can be done · By local file transfer from an engineering workstation connected locally to the IED.This file transfer is outside the scope of this standard. By remote file transfer e.g.by the file transfer method of this standard.The file format is not defined within this standard,but naturally SCL format is a possible choice. Version 8CDV,August 2002
CDV 61850-6 © IEC:2002 – 10 – 57/WG10 Version 8CDV, August 2002 • It is accompanied either by an SCL file describing its capabilities, or by a tool, which can generate this file from the IED. • It can use a system SCL file to set its communication configuration, as far as setting is possible at all (i.e. as a minimum its needed addresses), ot it is accompanied by a tool which can import a system SCL file to set these parameters to the IED. The System configurator is an IED independent system level tool that shall be able to import / export data (e.g. files) defined by this part of the standard. It imports configuration files from several IEDs, as needed for system level engineering, and used by the configuration engineer to add system information shared by different IEDs. Then the system configurator generates a substation related configuration file as defined by this part of the standard, which may be fed back to the IED configurator for system related IED configuration. Figure 2 - Reference model for information flow during the configuration process The part below the dashed line of Figure 2 indicates the ways in which IED configuration data produced by means of the IED configurator can be brought into the IED. This can be done • By local file transfer from an engineering workstation connected locally to the IED. This file transfer is outside the scope of this standard. • By remote file transfer e.g. by the file transfer method of this standard. The file format is not defined within this standard, but naturally SCL format is a possible choice. IED Database System Configurator IED Capabilities (LN, DO) IED Configurator Association Pre-configured exchanges Relationship to primary topology Engineering Workstation Substation Gateway IED IED IED IED File Transfer (REMOTE) File Transfer (LOCAL) IEC 61850 Service