CHAPTER 3: IEC 61850 COMMUNICATION
E3-2.0 IMPLEMENTATION MODEL FOR GOOSE CONFIGURATION VIA SCL
UR SERIES – COMMUNICATIONS GUIDE
3-179
3
3.11 E3-2.0 implementation model for GOOSE configuration via SCL
3.11.1 Introduction
This section specifies the E3-2.0 GOOSE subscription implementation model in UR 7.30 and later releases.
The "E3 - Spanish Electricity Companies for Studies on IEC 61850" is a working group formed by the main Spanish
electricity companies, which agreed on requirements to comply with for devices to be installed in their substations under
the IEC 61850 Edition 1.0 standards. These requirements are contained in the document GROUP OF SPANISH ELECTRICITY
COMPANIES FOR STUDIES ON IEC 61850 - MINIMUM COMMON SPECIFICATION FOR SUBSTATION PROTECTION AND
CONTROL EQUIPMENT IN ACCORDANCE WITH THE IEC 61850 STANDARD, edition 3 (09.06.10). In that document, ANNEX D:
GOOSE AND SV SUBSCRIPTION MODELING sets out requirements for two means of using the IEC 61850 6 Edition 1.0
Substation Configuration Language (SCL) to model GOOSE and Sampled Value configuration. Option A specifies a model
wherein all subscription information is contained within the IED element modelling the subscribing IED. Option B specifies a
model wherein a portion of the information required by the subscriber is contained in IED elements modelling the
publishers.
While both options are technically compliant with edition 1.0 of the standard, Option B also is consistent with the standard
envisioned for SCL. Except for being implemented under edition 1.0 of the standard, Option B is the same as the G2
Implementation Model, which is outlined later.
To satisfy customer preference, UR 7.30 and later releases allow SCL files to use either the G2 implementation model or the
E3-2.0 implementation model. E3-2.0 is essentially E3 Option A, but with changes required to make it compliant with
edition 2.0 of the standard.
3.11.2 Workflow
Workflow of SCL files under E3-2.0 is the same as described in the G2 implementation model. This is summarized in the
figure that follows.
•
Both the UR and UR Setup software can generate ICD files, which contain all the factory default settings. Settings not
modelled in Public elements are modelled in a Private element.
•
Both the UR and UR Setup software can generate IID files, which contain the settings as configured at the time the IID
file was generated. IID files contain only a single IED element, the IED element modelling the target IED. In E3-2.0 IID
files, all settings are included.
•
Both UR and UR Setup software can receive CID files. When the UR receives a CID file, it automatically verifies that it
can implement the specified functionality, and if no problems are detected, reboots using the settings in the CID file.
Although not shown in the figure, the most recently accepted CID file can be retrieved from the UR.
•
The UR and UR Setup software exchange 61850 configuration, including GOOSE configuration, using IID and/or CID
file transfer exclusively. Modbus is retained as an alternative for non-61850 settings. Other than IP Address settings,
SCL file transfer is the only means to configure 61850.
Summary of Contents for UR series
Page 5: ...TABLE OF CONTENTS UR SERIES COMMUNICATIONS GUIDE v INDEX...
Page 6: ...vi UR SERIES COMMUNICATIONS GUIDE TABLE OF CONTENTS...
Page 20: ...1 14 UR SERIES COMMUNICATIONS GUIDE FOR FURTHER ASSISTANCE CHAPTER 1 INTRODUCTION 1...
Page 216: ...2 196 UR SERIES COMMUNICATIONS GUIDE MEMORY MAP CHAPTER 2 MODBUS COMMUNICATION 2...
Page 428: ...A 2 UR SERIES COMMUNICATIONS GUIDE REVISION HISTORY APPENDIX A MISCELLANEOUS A...