Beruflich Dokumente
Kultur Dokumente
-RRSZEXMSR
JVSQ
%&&
Engineering guide
IEC 61850 Station
COPYRIGHT
WE RESERVE ALL RIGHTS TO THIS DOCUMENT, EVEN IN THE EVENT THAT A PATENT IS
ISSUED AND A DIFFERENT COMMERCIAL PROPRIETARY RIGHT IS REGISTERED. IMPROPER
USE, IN PARTICULAR REPRODUCTION AND DISSEMINATION TO THIRD PARTIES, IS NOT
PERMITTED.
THIS DOCUMENT HAS BEEN CAREFULLY CHECKED. HOWEVER, IN CASE ANY ERRORS ARE
DETECTED, THE READER IS KINDLY REQUESTED TO NOTIFY THE MANUFACTURER AT THE
ADDRESS BELOW.
THE DATA CONTAINED IN THIS MANUAL IS INTENDED SOLELY FOR THE CONCEPT OR
PRODUCT DESCRIPTION AND IS NOT TO BE DEEMED TO BE A STATEMENT OF GUARANTEED PROPERTIES. IN THE INTERESTS OF OUR CUSTOMERS, WE CONSTANTLY SEEK TO
ENSURE THAT OUR PRODUCTS ARE DEVELOPED TO THE LATEST TECHNOLOGICAL STANDARDS. AS A RESULT, IT IS POSSIBLE THAT THERE MAY BE SOME DIFFERENCES BETWEEN
THE HW/SW PRODUCT AND THIS INFORMATION PRODUCT.
Manufacturer:
ABB Power Technologies AB
Substation Automation Products
SE-721 59 Vsters
Sweden
Telephone: +46 (0) 21 34 20 00
Facsimile: +46 (0) 21 14 69 18
www.abb.com/substationautomation
Contents
Chapter
Chapter 1
Page
Introduction ..................................................................... 1
Introduction to the IEC 61850 Station Engineering guide.................... 2
About the complete set of manuals for an IED ............................... 2
About the IEC 61850 Station Engineering guide ............................ 3
Intended audience .......................................................................... 3
Related documents......................................................................... 4
Revision notes ................................................................................ 4
Chapter 2
Chapter 3
Chapter 4
Contents
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 1
Introduction
Chapter 1 Introduction
About this chapter
This chapter explains concepts and conventions used in this manual and provides information
necessary to understand the contents of the manual.
Chapter 1
Introduction
1.1
Application
manual
Technical
reference
manual
Installation and
commissioning
manual
Operators
manual
Engineering
guide
en06000097.vsd
The Application Manual (AM) contains application descriptions, setting guidelines and setting
parameters sorted per function. The application manual should be used to find out when and for
what purpose a typical protection function could be used. The manual should also be used when
calculating settings.
The Technical Reference Manual (TRM) contains application and functionality descriptions
and it lists function blocks, logic diagrams, input and output signals, setting parameters and technical data sorted per function. The technical reference manual should be used as a technical reference during the engineering phase, installation and commissioning phase, and during normal
service.
The Installation and Commissioning Manual (ICM) contains instructions on how to install
and commission the protection IED. The manual can also be used as a reference during periodic
testing. The manual covers procedures for mechanical and electrical installation, energizing and
checking of external circuitry, setting and configuration as well as verifying settings and performing directional tests. The chapters are organized in the chronological order (indicated by
chapter/section numbers) in which the protection IED should be installed and commissioned.
The Operators Manual (OM) contains instructions on how to operate the protection IED during normal service once it has been commissioned. The operators manual can be used to find
out how to handle disturbances or how to view calculated and measured network data in order
to determine the cause of a fault.
The IED 670 Engineering guide (EG) contains instructions on how to engineer the IED 670
products. The manual guides to use the different tool components for IED 670 engineering. It
also guides how to handle the tool component available to read disturbance files from the IEDs
on the basis of the IEC 61850 definitions. The third part is an introduction about the diagnostic
tool components available for IED 670 products and the PCM 600 tool.
Chapter 1
Introduction
The IEC 61850 Station Engineering guide contains descriptions of IEC 61850 station engineering and process signal routing. The manual presents the PCM 600 and CCT tool used for
station engineering. It describes the IEC 61850 attribute editor and how to set up projects and
communication.
1.2
1.3
Intended audience
General
This manual addresses system engineers, project engineers involved n the engineering process
for a project, installation and commissioning personnel, who use technical data during engineering, installation and commissioning, and in normal service.
Requirements
The system engineer must have a thorough knowledge of protection and/or control systems, protection/control equipment, protection/control functions and the configured functional logics in
the IED 670 devices. The installation and commissioning personnel must have a basic knowledge in the handling electronic equipment.
1.4
Chapter 1
Introduction
Related documents
Documents related to the PCM 600 and CCT tool set
Identity number
1KHA001027UEN
1MRS755552
1.5
Revision notes
Revision
Description
First release
Chapter 2
IEC 61850 station engineering
Chapter 2
IEC 61850 station engineering
1.1
System Sepcification
stat.SSD
System
Configurator
Station
DB
Vendor B
IED
DB
Vendor A
Vendor C
Substation Configuration
stat.SCD
ied.ICD
IED
Configurator
Vendor A
IED
Configurator
Vendor B
IED
Configurator
Vendor C
Configured IED
ied.CID
IED
HSI
Vendor A
IED
Control
Vendor C
SA
Gateway
IED
Protection
Vendor B
IED
Control
Vendor C
IED
NCC GW
Vendor B
IED
Protection
Vendor B
Substationn
en06000105.vsd
Figure 1:
Chapter 2
IEC 61850 station engineering
The standard defines two tools and four file types for station engineering. The above figure
shows these tools and files in their relation. In the ideal situation from top down the engineering
process and the used tools and files have the following relation:
Chapter 2
IEC 61850 station engineering
Chapter 2
IEC 61850 station engineering
=DeStat (DemoStation)
=E1 (e.g. 135 kV)
=Q1
=Q2
=Q3
=- WA1
=- WA2
=-QB1
=-QB2
=-QB1
=-QB2
=-QB1
=-QB2
=-QA1
=-QA1
=-QA1
=-QB9
=-BI1
=-BU1
=-QB9
=-BI1
=-BU1
=-QB9
=-BI1
=-BU1
=-QC9
=E1.Q1
=-SB1
IED
Control
=-QC9
=-FP1
IED
Protection
=-QC9
=E1.Q2
=-SB1
=-FP1
IED
Control
IED
Protection
=E1.Q3
=-SB1
IED
Control
=-FP1
IED
Protection
=AA1
=-SA1
en06000108.vsd
Figure 2:
Chapter 2
IEC 61850 station engineering
The IEC 61850 standard is based on the hierarchical addressing and designation model in a station. It follows in this way the structure of the substation equipment independent of IED structure and organization.
This designation and addressing model is also visible in the IEC 61850 telegrams because the
address is presented in MMS as an ASCII string, so the address can be seen directly in a readable
form.
The above figure shows a virtual example station. The identification is based on the IEC 61346
concepts. Reasons to use the IEC 61346 model:
the IEC 61346 has the task to define structuring principles and reference designations.
the standard is international in the same way as IEC 61850 is
the standard has made a concept which can be used in all industrial systems independent of a language, project etc.
the standard use only single characters per level which makes the total designation very short and therefore saves bytes to be transmitted.
by using this designation model in IEC 61850 it allows to use an easy project independent identification.
The designation of a Logical node and its signals (DO) is needed to identify it to the primary
object etc. The hierarchical order in a substation is the path to identify the LN.
10
Chapter 2
IEC 61850 station engineering
Station = DeStat
=Q1
=E1
=-QB1
CSWI
=-QB2
=-QA1
XCBR1
FC = ST
Pos
stVal
q
RBRF
LD1
=-QB9
origin
LD2
PTRC
=P
=B
MMXU1
PDIS
=-BI1
=-BU1
PTEF
PTOC
RREC
=-QC9
en06000110.vsd
Figure 3:
The designation path to get the position of the circuit breaker as an example would be:
DeStat => E1 => Q1 => LD1 => QA1 => XCBR1 => Pos => stVal
in IEC 61850 = DeStat.E1Q1/LD1QA1XCBR1.Pos.stVal
11
Chapter 2
IEC 61850 station engineering
The above model of designation identification is possible when the station configuration is based
on the FuncName method in IED 61850. This is specified in the Header section of the SCL
file. The standard identifies these object or signal designations as the technical key. The standard
recommends to use the IEC 61346 based designation model, but it is not a must. But a similar
naming structure is requested when an existing identification concept has to be used.
2.1
The IEC 61346 defines the rules etc. and gives explanations how to organize the structure and
the use of the characters but it does not give a model for each industrial area. This has to be done
by working groups.
For the substations for electrical energy distribution the German community of interest IG
EVU has taken this task. Member of the IG EVU are beside others the main vendors and the
main utilities of Germany. The papers are available and free of charge via Internet www.igevu.de. The documents can be found on the page Verffentlichungen.
The following extracts of the designation trees shows the position of the used elements.
12
Chapter 2
IEC 61850 station engineering
en05000647.vsd
Figure 4:
13
Chapter 2
IEC 61850 station engineering
the Header
the Substation description (section)
the Communication description (section)
the IED description (section)
the Data Type Templates
The first two sections can be seen as tasks to organize the IEDs within the substation and to establish the communication. These tasks are done by the PCM 600 tool. The Logical nodes as part
of the IED are logically linked to the substation section by PCM 600. The signal engineering
task and routing of the signals is the task of the CCT tool. Its precondition is that PCM 600 has
done the complete organization on the two sections substation and communication.
The DataSets and Control Blocks configured by the CCT tool are located in the IED section because they are logically defined as part of the Logical nodes (see IEC 6185072 clause 9). The
CCT needs the correct configured communication section when it comes to GOOSE engineering.
The Data type templates section is requested to give the correct content description of each Logical node type to all user of the information. These are the clients. Each IED and vendor may
have/has its own Logical node type definitions.
14
Header
Header
Chapter 2
IEC 61850 station engineering
FuncName
or
IEDName
Id
ToolId
Nam eStructure
Substation
VoltageLevel
Bay
IED
LD
LN
IED
LD
LN
Station
LNode
Communucation
Subnetwork
Connected AP
IED Nam e
AccessPoint
Address
GSE
IED Nam e
AccessPoint
Address
GSE
IED
Services AccessPoint
Server
Authentication
LDevice
LN0
LN
DataSet
DOI
DAI
Report Control
GOOSE Control
Inputs
SettingControl
IED
DOI
DataTypeTemplates
LNodeType
DO
DOType
DOType
DA
SDO
DAType
DAType
BDA
Enum Type
Enum Type
en06000111.vsd
Figure 5:
Figure 5 shows a principle structure of the SCL XML file with its five sections. The arrows show
the link between the different sections given when an IED is integrated in the substation structure and/or in the communication structure. All available Logical nodes of an IED are linked to
the substation section.
15
Chapter 2
IEC 61850 station engineering
A reference to the GoCB is included in the communication section when the GoCB is configured.
The above graphical presentation of the XML file is a standard view of XML editors. It gives a
better picture about the structure of the XML contents.
3.1
16
Chapter 2
IEC 61850 station engineering
en06000112.vsd
Figure 6:
The above figure is taken from the standard IEC 618506 (figure 5).
The standard defines two options how to use part 1 and part 2 above:
1. Function related naming
identified in the SCL header with NameStructure = FuncName
2. Product related naming
identified in the SCL header with NameStructure = IEDName
Within one SCL project only one option can be used.
17
Chapter 2
IEC 61850 station engineering
Substation
LDCL1
LN
LN
LN
LN
LDCL2
LN
LN
LN
LN
VL1
2
3
Bay1
LD1
Bay2
4
LN
LN
LN
LN
LD1
LD1
LN
LN
LN
LN
Bayx
LN
LN
LN
LN
2
3
Bay1
LD1
Bay2
4
LN
LN
LN
LN
Bayy
LD1
LD1
LN
LN
LN
LN
LN
LN
LN
LN
LD2 > LNs
LD3 > LNs
LN class
LN instance no
6
Substation section
IED section
Substation section
en06000099.vsd
The part 1 = LDName of signal identification is build out of the objects Substation (1), Voltage
level (2), bay (3) and the LD (4). The LN Prefix in this case is an additional element which belongs to the LDName part. It identifies the equipment or sub-equipment object in the primary
18
Chapter 2
IEC 61850 station engineering
structure. The typical example is the circuit breaker QA1, when the LN classes XCBR, CSWI
and CILO are used. It has to be regarded that in this model the IED is not included and the naming is based in the process objects only.
The LNName is in this option the LN class and the LN instance (6) only.
LDCL1
LN
LN
LN
LN
LDCL2
LN
LN
LN
LN
VL1
2
3
Bay1
Bay2
IED 1
IED 2
LD1
IED x
LD1
LN
LN
LN
LN
VL2
Bayx
LD1
LN
LN
LN
LN
LN
LN
LN
LN
Bay1
Bay2
IED 4
Bayy
IED 5
LD1
LN
LN
LN
LN
IED y
LD1
LD1
LN
LN
LN
LN
LN
LN
LN
LN
LD2 > LNs
IED section
IED section
LN class
LN instance no
en06000100.vsd
19
Chapter 2
IEC 61850 station engineering
The LDName part is build in this option out of the objects IED (A) and LD (B). The link to the
primary process is not given in this model.
The LNName is in this option the LN Prefix, the LN class and the LN instance no (C).
The LN prefix allows in this model to identify several versions of a LN class. For example the
eight different versions the LN class PDIF.
The link between the IED and the primary process (Substation (1), Voltage level (2), bay (3)) is
given in the substation section of the station.SCD file but not in the signal identification in the
telegram. The project may decide how to deal with this matter. The IED name may be extended
with a short form of the three missing levels. The IEDName must be unique in this designation
model.
Remark:
The standard defines the maximum length for the signal naming and for identification parts to
32 ASCII characters each. This has to be regarded for the object identification for part 1 to part
4 (see figure 6). In addition it might be possible that client IEDs have additional restrictions
which have to be taken into account.
Most vendor have to use the LN Prefix to identify their versions etc. Therefore the product related naming model (IEDName) will be used.
3.2
Ethernet as medium
MMS (Manufacturing Message Specification) protocol as defined in ISO 95061
and IOS 95062.
The IEC 61850 standard describes in part 72 the Abstract Communication Service Interface
(ACSI) in a media and protocol independent form. Part 81 specifies the mapping of this ACSI
to the existing MMS.
The communication section in the SCL file describes the minimum of what is needed to identify
how information is routed between the IEDs in a project. This is.
20
Chapter 2
IEC 61850 station engineering
IED
(client)
IED
(client)
Communication
Communication
Subnetwork
AP
AP
Communication
Communication
Communication
IED
(server)
IED
(server)
IED
(server)
en06000101.vsd
Figure 9:
Figure 9 shows the contents of the communication section. Additional information about the
server etc. is part of the IED.
The link to the IEDs is done by PCM 600 when the IED is placed and the link to the subnetwork
established. The list of Connected AP in the communication section of the SCL file includes
all IEDs with their APName.
A station as shown in figure 3 the station uses two voltage levels with a set of bays and IEDs per
bay. The communication network can be done in several ways for this station. The most typical
variants are shown in figure 10.
21
Client
IED 1
Chapter 2
IEC 61850 station engineering
Client
IED 2
Subnetwork 1
IED 1
IED 2
IED x
IED 4
VL 1
IED 5
IED y
VL 2
Client
IED 1
Client
IED 2
Subnetwork 1
Subnetwork 2
IED 1
IED 2
IED x
VL 1
IED 4
IED 5
IED y
VL 2
en06000103.vsd
Figure 10:
Both variants fulfil the requirements and performance. Variant 2 may be used, when the availability question is discussed. In this case only one voltage level of the station is lost when a subnetwork fails. The client IEDs must be able to handle two access points.
3.3
22
Chapter 2
IEC 61850 station engineering
ITMI. They are the receiver of information in monitoring direction and sender of commands (control). These LNs have no data objects. They are only
used to do the link of the report control blocks (BRCBs) from the server
IEDs.
bay level IEDs
- all IEDs on bay level are server IEDs.
Subnetwork
AP
IED
Server
SB1.LD1
Logical
Node
LLN0
LPHD
Data
SXCBR1
Mod
SCSWI1
Beh
SXSWI1
Health
SCSWI2
NamePlt
Data
Attribute
SXSWI2
Pos
ctlVal
SCSWI3
Loc
stVal
SXSWI3
OpCnt
SCSWI4
BlkOpn
SXSWI4
BlkCls
Origin
SCSWI5
CBOpCap
ctlModel
CVMMXU1
Control
en06000104.vsd
Figure 11:
The above figure is a short summary about the logical organization of the signals below the IED.
23
Chapter 2
IEC 61850 station engineering
the LN LLN0 is a special LN per LD and contains the DataSets, the various control blocks, inputs (from GOOSE messages) etc.
The LN LPHD is a special LN per LD and contains data objects which describe
the status of the physical device (the IED)
each Logical node represents a function and contains a number of data objects
(DO)
each DO is represented by a number of data attributes (DA)
The data objects are representing information signals which may be routed to station level IEDs.
So the signal engineering task is to select the requested signals (DOs) and link them to the client
IEDs as receiver. The control services are not directly engineered. They are included in the data
objects which handle both directions the command (control) and the response (monitoring). So
when routing the DO in monitoring direction the control is then also known by the clients.
The organization of the IED from LD down to DAs can be viewed in the CCT tool. This organization concept has to be taken into consideration when DataSets are configured.
The number of data objects and data attributes per DO is defined by the used LN type in this
IED. The contents is taken from the Data Type Templates which belong to an IED type.
3.4
Signal engineering
DataSets
IEC 61850 has defined DataSets and report control blocks for signal transmission in monitoring
direction. DataSets are also used for GOOSE messages in horizontal direction. Which data objects or single data attributes should be collected in a DataSet is not specified and can be done
to rules which may be defined in a project. The following figure shows a DataSet where all position information of the apparatuses of a bay are put into one DataSet.
The vendor of an IED can define DataSets as defaults which are part of the IED and always
available. They need to be linked to the client IEDs only when you want to use them as they are.
The vendor has to declare when these DataSets can be modified to projects need or not.
24
Chapter 2
IEC 61850 station engineering
LD1
DATA-SET
LLN0
LD1/LLN0.AppPos
LPHD
LD1/SXCBR1.Pos FC=ST
SXCBR1
Pos
LD1/SXSWI2.Pos FC=ST
SCSWI1
SXSWI1
LD1/SXSWI1.Pos FC=ST
Pos
LD1/SXSWI3.Pos FC=ST
LD1/SXSWI4.Pos FC=ST
SCSWI2
SXSWI2
Pos
SCSWI3
SXSWI3
Pos
SCSWI4
SXSWI4
stVal
q
Pos
SCSWI5
t
Origin
CVMMXU1
en06000106.vsd
Figure 12:
All data objects or their data attributes which are signals in monitoring direction
can be selected for a DataSet
only those data attributes of a data object can/will be selected which have the
same function constraint (FC).
data objects with different FC can be selected for a DataSet. For example DOs
with FC = ST and DOs with FC=MX can be member in one DataSet.
a single data attribute can be selected when it is specified with a trigger option.
For example the data attribute stVal of the data object Pos can be selected as a
member of a DataSet, because it is specified with the trigger option data change
detected (dchg).
The description of the DataSets with name and the list of data object members (FCDAs = Functional Constraint Data Attributes) is included in the SCL file in the IED section in the Logical
device subsection. As specified in IEC 6185072 clause 9, the DataSets are part of a Logical
node. They are most likely included in the LLN0.
3.4.1
25
Chapter 2
IEC 61850 station engineering
The contents of a BRCB is listed in IEC 61850 72 in clause 14, table 23. The BRCB contains
a lot of attributes which are of interest to handle and secure the communication between the client and the server and may be set once as default in a project. Others are of application interest
in the way events are handled in a project.
Buffer time
- This parameter describes how long the report should wait for other expected
events before it will send the report to the client. When it is known, that additional events will be generated as a follow up it is useful to wait for example 500 ms for additional events stored in the report. This feature reduces the
number of telegrams transmitted in case of a burst of changes. But on the other side it increases the overall transaction time for events from IED input to
presentation on HSI which is normally defined to be one second!
Trigger options
- The data attributes know three different trigger options (dchg, qchg, dupd).
Within the BRCB the two other can be defined (integrity and general interrogation). The attribute Trigger option is a multiple choice and allows to
mask the supported trigger options in this BRCB.
Integrity period
- When integrity is selected in the trigger option attribute, it is needed to define
an integrity period to force the transmission of all data listed in the DataSet.
This is done by the attribute Integrity period. This feature can be used as a
background cycle to ensure that the process image in all partners is the same.
Nobody is perfect and someone in the long chain from the contact up to the
NCC may have lost an event. The background cycle can repair it.
General interrogation
- A general interrogation is only done on request from a client. Not all Data-sets may contain information which is needed for a general update of the
client. For example data with T(ransient) = TRUE are not part of a GI. When
the BRCB attribute general interrogation is set to TRUE a GI request from
the client will be handled. The report handler will transmit all data defined in
the Data-set with their actual values. The IEC 61850 standard defines that all
buffered events shall be transmitted first before the GI is started. A running
GI shall be stopped and a new GI shall be started, when a new GI request is
received while a GI is running.
Purge buffer
- This BRCB attribute can be used by a client to clean the event buffer from
old events. The events are discarded on request of the client. This feature can
be used to delete old events not transmitted to the client due to stopped communication. After the link is reestablished the client can decide to clean the
buffer or to receive the history.
Trigger Options
IEC 61850 has defined in total five different TrgOp. Three of them belonging to data attributes
and marked per data attribute in the column TrgOp of the CDC tables in part 73. The other two
belonging to the configuration of control blocks. The five trigger options are:
26
dchg = data-change
Chapter 2
IEC 61850 station engineering
The classical trigger. Whenever a process value has changed its value either
binary or a measurement a transmission is done. How it is detected and how
the Logical node is informed is not part of the standard.
qchg = quality change
- Looking to the possibilities of the quality data attribute type (q) any changes
in the quality description will be transmitted.
dupd = data value update
- This trigger option give the possibility to define that a transmission should
be done on a condition which can be controlled by the application.
integrity
- This trigger will force the transmission of all process values defined in the
Data-set when a timer value (the integrity period) expires. It can be used for
example to do a process signal update in the background (e.g. every 15 minutes).
general interrogation
- This trigger is forced by the clients (= station level IED; NCC gateway, station HMI, ...). Normally a GI is asked for, when the client and the server start
or restart a session. When the client is able to receive the actual values and
when the Logical device has scanned all process values at least once, an image of the actual process signal status can be transmitted to the client.
27
IED
HSI
Client 1
IED
NCC GW 1
IHSI1
Client 2
ITCI1
Chapter 2
IEC 61850 station engineering
IED
NCC GW m
Client m
ITCI2
Subnetwork
Server 1
LLN0
DATA-SET
LD1/LLN0.AppPos
IED 1
LD1/SXCBR1.Pos FC=ST
LD1/SXSWI1.Pos FC=ST
LD1/SXSWI2.Pos FC=ST
LD1/SXSWI3.Pos FC=ST
LD1/SXSWI4.Pos FC=ST
en06000107.vsd
Figure 13:
28
Data-set
Data-set
LN
LN
LN
LN
Receive
Data-set
LN
LN
LN
Receive
Send
Receive
Receive
Send
Receive
Receive
Send
3.4.2
Chapter 2
IEC 61850 station engineering
LN
LN
LN
LN
LN
LN
LN
LN
Subnetwork
Comm.
Comm.
GSE
Server
Server
LD1
LD1
GoCB
GoCB
GoCB
Input
Input
Input
DataSet
DataSet
DataSet
GSE
GoCB
GoCB
GoCB
LN0
Input
Input
Input
DataSet
DataSet
DataSet
LN0
en06000109.vsd
Figure 14:
The Generic Object Oriented Substation Event (GOOSE) class model is used to distribute input
and output data values between IEDs on bay level (in horizontal direction) through the use of
multicast services. GOOSE messages bypass the server and enables a fast transmission from
publisher to one or several subscribers (receivers).
29
Chapter 2
IEC 61850 station engineering
GOOSE messages are unidirectional, send only messages which request an application specific
method to secure that sender and receiver of the message operates safely. This implies that the
receiver of the GOOSE message distributes also GOOSE messages and close the loop for communication (request respond on application level). The return message is not a must. It depends on the application in which way a confirmation may be done.
The GOOSE message concept will be used for all application functions where two or more IEDs
are involved. Typical example is the station-wide interlocking procedure.
The very simplified figure above shows the GOOSE concept for three IEDs which interchange
GOOSE messages between each other.
To send GOOSE messages a GoCB must be defined and a DataSet is needed which contains the
data objects of single data attributes to be send.
A GOOSE message is forced to be transmitted when a trigger change is detected for a data attribute. All members of the Data-set will be copied in the send buffer with their actual value and
the message is sent. All subscriber which knows the address of this GOOSE message will receive the telegram. The GOOSE message includes sequence number etc. to verify that all messages are received.
The concept what has to be done in case of a lost message etc. is part of the application and not
described in the standard.
The DataSet for GOOSE messages are configured in the way described above.
A GoCB has to be defined per GOOSE-DataSet.
GOOSE messages bypass the server and send direct from the communication part on the Ethernet. This is identified for the communication in the SCL communication section in the GSE element, where the name of the GoCB is listed under the ConnectedAP.
30
Chapter 3
IEC 61850 Station configuration
tasks
31
Chapter 3
IEC 61850 Station configuration
tasks
the definition of data objects and their common data classes with their data attributes
the definition of Logical nodes (LN) as the communication interface for a substation function (e.g. a protection function)
the definition of a basic communication structure for substation and feeder equipment
the practical mapping of the communication to an existing protocol the MMS
the definition of the engineering process for a substation control system in a configuration description language for communication in electrical substations
We refer to the IEC 61850 standards in their actual version as a basis for the engineering tasks
described inhere by using the PCM 600 and the CCT. The main parts which are of interest are
described in a brief form in chapter 2 "IEC 61850 station engineering".
A short form of the complete station and signal engineering sequence can be described as shown
in the following figure.
32
Vendor A
prepare
ied.ICD
files
Vendor B
prepare
ied.ICD
files
Chapter 3
IEC 61850 Station configuration
tasks
Vendor X
prepare
ied.ICD
files
PCM 600
y
y
y
y
y
text
station_PCM.SCD
CCT
y
y
y
y
station.SCD
Vendor A
prepare
ied.CID
files
Vendor B
prepare
ied.CID
files
Vendor X
prepare
ied.CID
files
IED
IED
IED
en06000207.vsd
Figure 15:
33
Chapter 3
IEC 61850 Station configuration
tasks
do the similar tasks for the other bay IEDs with their IED engineering tools
and export the ied.ICD files or take the ied.ICD files from a vendors library
import all other ied.ICD files to their position in the station via Generic IEC
61850 IED.
check the communication subnetwork that all IEDs are connected to the
same subnetwork
give each bay IED its IP address
export the station_PCM.SCD file
2. Signal engineering for the IEC 61850 signals with CCT
create a project in CCT, if it not already exists for the station
import the station_PCM.SCD file created by PCM 600
actually import client IEDs with their ied.ICD file to the station configuration by CCT
link the client IEDs to the communication subnetwork and define the access
point
save, close and load the CCT project again; only when client IEDs are added
by CCT first time
check the pre-configured DataSets for report control blocks for your needs
and for each IED. Generate additional DataSets for RCBs when requested
generate the needed DataSets for GOOSE messages
create and configure Buffered Report Control Blocks (BRCB) for each data
set used for vertical communication.
link each DataSet for vertical communication to a BRCB
link the IED clients Logical node (ITCI IHMI) to the BRCBs
create and configure GOOSE Control Blocks (GoCB) for each DataSet configured for GOOSE messages
link the GOOSE DataSets to a GoCB
link the IEDs which shall receive the GoCB to the GoCB
update IEC 61850 data flow (CCT specific function)
export the station.SCD file for further use by the IED configuration tools
3. Preparation of ied.CID files per IED and download them to the IEDs
import the station.SCD file to all IED configuration tools for further activities
for ABB bay IEDs use the PCM 600 for IED engineering
do signal marshalling with the SMT tool in all ABB IED 670s which are involved to receive GOOSE messages
download the updated ied.CID file to the IED 670 with the SMT tool
do similar tasks for all other IEDs with their IED configuration tool
This is a short form of the complete procedure for IEC 61850 with PCM 600 and CCT.
The additional tasks for signal engineering for IEC 61850 in an IED 670 are described in the
'Engineering guide for IED 670 products'.
34
Chapter 4
PCM 600 and CCT tool set for
station engineering
35
Chapter 4
PCM 600 and CCT tool set for
station engineering
36
Chapter 4
PCM 600 and CCT tool set for
station engineering
Project
Explorer
&
Object
Types
Place for
selected tool
Object
Properties
en06000028.vsd
Figure 16:
37
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000580.vsd
Figure 17:
Possible views:
Project Explorer
Object Properties
Output
Object Type
Project Explorer
The Project Explorer window is the skeleton of the project organization. It is used to show the
project in two different structures:
The plant structure is the most commonly used view and shows the organization of the stations
in the geographical order top down from a defined highest level (e.g. the network control center
(NCC)) down to each IED logically connected to a bay in the station. The plant structure is used
to select the tools per IED.
The communication structure is not needed for normal operation. It is used to view the communication network and links from the PCM 600 to each IED. Only the private communication
from the PCM 600 to each IED is managed and handled by the PCM 600.
To select the communication structure do a right mouse click on the area next to the Plant Structure tab. Select communication and an additional page will be included which shows the communication structure of the PCM 600
en05000562.vsd
Figure 18:
38
Chapter 4
PCM 600 and CCT tool set for
station engineering
Object Properties
The Object Properties window is a standard Microsoft window which allows the user to view
and when needed to modify properties of the selected object. In the PCM 600 frame this window
is used by some tools like GDE to insert the IP address of the IED selected and some other properties like object naming in the HMI picture and so on. It might be necessary to check some properties for communication to adapt and synchronize the communication network. The shown
properties in the object properties window follow the selected object in the Project Explorer or
in a tool.
en05000559.vsd
Figure 19:
Modifications are only possible in cells with their content shown in bold. Renaming of objects
can be done more easily by using the Rename capability in the plant structure, which is made
available by pressing the right mouse button.
Output
The Output window is shown on the bottom array of the PCM 600 screen when selected. It is a
log script which is used by PCM 600 to list all activities, warnings, error messages etc. which
come up during operation of the PCM 600. It might be needed and used when a task does not
operate as expected. The information in the output list may provide a clue as to why it does not
operate etc. The Output view is not needed for normal operation and can be closed.
39
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000558.vsd
Figure 20:
Object Type
en05000556.vsd
Figure 21:
The window Object Type can be used to build up a plant structure using drag and drop and selecting the object type from the list of possible objects. It is opened in the same place and then
the Plant Structure is presented. It is selected by clicking on the Object Types tab at the bottom
of the window.
The Object Type window contains some different panes depending on selected structure. For the
plant structure view the two panes are selectable by clicking the menubar General or Transmission IED.
More details to different views etc. are given in chapter 5 "Set up a project in PCM 600".
40
Chapter 4
PCM 600 and CCT tool set for
station engineering
IED tools
These tools are not used for IEC 61850 station configuration.
Each started IED tool will be visible in the residual screen area surrounded by the three windows
Plant Structure, Object Properties and Output. For normal operation only the Plant Structure is
needed and it is recommended to close the other two windows. More then one tool can be open
at the same time for one IED or for some IEDs in parallel. But only one tool at a time is active.
The tool is selected either by its tool tab or by selecting the IED.
See the IED engineering guide manuals for more derails.
2.1
en05000555.vsd
Figure 22:
Depending on selection as given in this example the alternative choice could be to select New....
In this case a new window will pop up and it shows the same selection possibilities.
41
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000554.vsd
Figure 23:
The window keeps open after your selection. Depending on the selected object it will show directly the possible choices.
42
Chapter 4
PCM 600 and CCT tool set for
station engineering
Figure 24:
43
Chapter 4
PCM 600 and CCT tool set for
station engineering
3.1
44
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000614.vsd
Figure 25:
User authentication
The tasks and action in each branch can be sorted like this:
1. Use Authentication
NO = no selection. Everybody can use the PC where this PCM 600 is installed.
YES = Authentication is used. Select the method with one of the two choices:
2. PCM Authentication or
3. Windows Authentication
Select the User manager.
45
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000613.vsd
Figure 26:
The User Manager window has four input fields. Three of them are used to define the access for
a user for either PCM or Windows authentication. The field Real Name might be used to identify
the user, when the user name is a short version of his name.
The PCM authentication uses the following inputs to identify a user:
User Name
Set Password (optional)
User Category. The user category is defined in the category manager. It belongs
to the user name and is not part of the authentication check.
User Name
Windows Account.
User Category. The user category is defined in the category manager. It belongs
to the user name and is not part of the authentication check.
Set Password is not used!
PCM authentication
When the PCM authentication method is used a Login window pops up after start of PCM 600.
The user has to identify himself with his user name and the password when it is used for access
control.
46
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000610.vsd
Figure 27:
Windows authentication
In the Windows authentication method each user must have a different account on this PC. Only
in this case a selective input is possible. In this case the user has already identified himself to the
PC, when he started Windows. So a separate access control is not needed.
A user can change his password, by entering his old password once, and then the new password
twice. The system engineer can change passwords without knowledge of the old passwords.
47
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000617.vsd
Figure 28:
Category Manager
Different categories of default user are defined for PCM 600:
48
System Engineer
- has access to all tools and functions
- is the only one who can edit user management
Application Engineer
- has access to all tools for engineering the IEDs
- has access to the system monitoring tools to check during commissioning
phase the correct operation of the IED
- has no user management rights
System Monitoring User
- has access to the system monitoring tools to monitor the IEDs during operation
- has no access to the engineering tools
- has no user management rights
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000615.vsd
Figure 29:
49
Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000561.vsd
Figure 30:
Always use the latest version of a tool package or protocol. This can be easily done in the
menubar Set Latest.
In the above Connectivity Package Manager window the following packages are available
50
Chapter 4
PCM 600 and CCT tool set for
station engineering
It will be used to include the ied.ICD file of bay IEDs in the station.SCD file.
It will be used, when the DRH tool is used to read the DR files from all IEDs
running the IEC 61850 protocol. See IED engineering guide manual for more
details about the disturbance report handler (DRH).
IEC 61850 Connectivity Package
- This package is needed for IED 670 products, which communicate with
PCM 600 on Ethernet, TCP/IP and using elements of the IEC 61850 protocol.
LON Connectivity Package
- This package is not needed for IED 670 products. It is used for products using LON to communicate with PCM 600.
IED 670 Connectivity Package
- This package is needed in the latest revision to engineer IED 670 products.
It contains the description of the IED 670 products.
SPA Connectivity Package
- This package is not needed for IED 670 products. It is used for products using SPA to communicate with PCM 600.
51
Chapter 4
PCM 600 and CCT tool set for
station engineering
5.1
PCM 600 Set up communication link per Generic IEC 61850 IED
A Generic IEC 61850 IED (Gen-IED) can only communicate with the PCM 600 in the same way
as the IED 670 products are when using the IEC 61850 protocol. That is only given for the disturbance file reading from the relays. The DRH tool is responsible for that task. For more details
about the DRH tool see 'Engineering guide for IED 670 products'.
52
Chapter 4
PCM 600 and CCT tool set for
station engineering
Project
Navigator
Control
&
Action
IEC 61850
Data Engineering
Properties
Figure 31:
CCT has different panels (in PCM 600 called views). The wording panel is taken here because
the CCT use it.
Possible panels:
53
Chapter 4
PCM 600 and CCT tool set for
station engineering
Project Navigator
The Project Navigator shows the four sections in a SCL project in different levels of details. The
known four sections are:
Substation section
- for information only. Only the sequence: Station > Voltage level > Bay is
shown
Communication section
- for information only. Only the configured Subnetworks and their configured
Access points are shown
IED section
- the tree structure can be expanded from > to: IED > LD > LN > DO > DA
including the full extension of complex data objects
- added DataSets, Report Control Blocks (RCB) and GOOSE Control Blocks
are shown below the LN level when enabled to be included (normally below
LLN0).
- the configured Data objects (DO) are listed with all their Data attributes in
the Attribute Editor within the IEC 61850 Data Engineering pane
Data Type Templates
- similar to the IED structure all existing LNodeTypes, DO Types, DA Types
and Enum Types are shown in a tree structure.
- The LN Types and their DOs are listed in the Attribute Editor within the IEC
61850 Data Engineering pane. The structure of DO Types, DA Types and
Enum Types is not shown in the Attribute Editor
Properties
The Object Properties window is a standard Microsoft window which allows to view and when
needed to modify properties of the selected object. Due to the fact, that CCT operates only with
the IED section properties should only be modified for the IED and the level below where useful
and needed to be adopted. It has to be regarded, that most of the properties are under control of
the configuration done by the station configurator PCM 600 or by the vendor of the IED.
This is also valid for changes done for example in the given IED naming. It must be known that
changing the IED name has influence on the substation section which is not supported by the
CCT. The station configurator PCM 600 has control over the station wide naming and addressing rules.
54
Chapter 4
PCM 600 and CCT tool set for
station engineering
Remark:
The role of CCT is to do signal engineering and signal routing. The PCM 600 is responsible for
the station configuration and naming within the project. The IEC 61850 Attribute editor may be
used for monitoring and view of Logical nodes and their data objects and data attributes only.
Even when it is possible to modify values, this may be done only in cooperation of the owner of
this value which will be PCM 600 or the vendor of the IED.
Remark
Changes in the Properties may have influences to other SCL sections which are not updated by
the CCT. When doing changes the position and influence of the attribute may be well known.
They may have also influence on the IED configuration, which is vendors responsibility.
Output
The Output window is shown on the bottom array of the CCT screen when selected. It is a log
script which is used by CCT to list all activities, warnings, error messages etc. which come up
during operation of the CCT. It might be needed and used when a task does not operate as expected. The information in the output list may give a hint why it does not operate etc. The Output
view is not needed for normal operation and can be closed.
There are two different views given:
Out
- shows all messages unfiltered
Log
- shows only those messages with a category that is at least the same as the
threshold defined in chapter 4, section 7.2 "Logger options".
Attribute Editor
Data Set Engineering
Report Control Engineering
Goose Control Engineering
55
6.1
Chapter 4
PCM 600 and CCT tool set for
station engineering
File
- is described in chapter 6, section 1 "Managing projects in CCT".
View
- enables to show a hidden panel again. The various panels are selectable.
- allows to organize all possible panel in their default position again
Tools
- updates all links and writes the object elements for the data organization requested by BRCBs and GoCBs in the IED and communication section.
Called Update DataFlow
- does SCL file import and export of station.SCD files (SCL File) or import of
ied.ICD files (ICD File). Export of ied.ICD files is selected in the Project
Navigator with the right mouse button and selected IED.
en06000034.vsd
Figure 32:
en06000036.vsd
en06000035.vsd
Figure 33:
56
Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000113.vsd
Figure 34:
To find a node, write the name in the field and press return. The search function is not branching
into a lower level for searching.
The other use of the right mouse button is to import / export ied.ICD files in the IED section.
See chapter 6, section 1 "Managing projects in CCT" for more details.
6.2
Spreadsheet features
Based on MicroSoft.net concepts CCT allows the use of some features which may be used in
long lists to search and to filter specific information.
57
Allow Grouping
Chapter 4
PCM 600 and CCT tool set for
station engineering
Filter action
Row selection by
text searching
Grouping
Column header
Filter
Pinning
Figure 35:
en06000039.vsd
Pinning
Clicking the symbol in a column header will fix or release the column to be shifted, when the
spreadsheet is moved in horizontal direction. The column will automatically shift to the next
right ascending position of fixed columns, when the columns left from the selected one are not
fixed. So to get a correct sequence of fixed columns start to fix the columns from left to right.
58
Chapter 4
PCM 600 and CCT tool set for
station engineering
Filtering
This is the MicroSoft standard method of filtering in a column. Clicking the filter icon pops up
a drop down list with possible choices. The first four choices are standard, the following one is
the list of possible elements in this column. Selecting an element out of the list will mark all rows
where the filter criteria matches in a way as described by the toolbar Filter action selection.
Filter selection possibilities
The Filter Action drop down list in the Toolbar allows to select a variant of how the filtered and
not filtered rows should be marked and made visible:
HideFilteredOutRows
1. hides all rows which do not match the filter criteria
DisableFilteredOutRows
1. shows all rows but disables the possibility to make changes (edit) in the rows
which do not match the filter criteria
AppearanceOnly
- will leave all rows visible but colors the rows which do not match the filter
criteria. The color is predefined.
Default
- is the same then HideFilteredOutRows
59
Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000046.vsd
Figure 36:
Sequence of operation:
select a column as grouping criteria and drop it in the grouping area above the
spreadsheet
- the name of the selected column will appear in a new icon and the complete
spreadsheet is reorganized according to grouping possibilities
- It is possible to select another column for grouping which will be then the
second level of grouping within each group of the first level grouping
toggling the button Show Grouping in the Toolbar will show the spreadsheet in
grouped and in normal view
to deselect grouping select the column icon in the grouping area above the
spreadsheet and drop it somewhere in the spreadsheet.
60
Chapter 4
PCM 600 and CCT tool set for
station engineering
Sorting
You may sort one or several rows in alphanumeric order by selecting the columns you want to
sort and click the direction for sorting button in the Toolbar.
Be aware that a sequential order as it was given by the spreadsheet before is lost (e.g. the sequence of data objects and data attributes in a complex data object structure). You have to deselect the spreadsheet and select it again to get the logical sequence back.
6.3
The use and definition of the different columns is described in chapter 8, section 3 "BRCB engineering" and section 4 "GoCB engineering".
61
Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000114.vsd
Figure 37:
62
Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000090.vsd
Figure 38:
en06000091.vsd
Figure 39:
63
Chapter 4
PCM 600 and CCT tool set for
station engineering
Environment
- Execution Mode
- LoggerOptions
IEC 61850 Options
- not supported in this CCT version
- the shown DataSet rules are used in an ABB internal CCT version to build
the default DataSets for IED products. These DataSets are always included
in the ABB IEDs.
Navigator Structure Options
- IEC 61850 Structure Options
- LogicalNode Types Structure Options; not supported in this CCT version
- LogicalNodes by IED Structure Options; not supported in this CCT version
MicroSCADA System Options
- not supported in this CCT version
NCC Gateway Communication Options
- not supported in this CCT version
en06000116.vsd
Figure 40:
64
7.1
Chapter 4
PCM 600 and CCT tool set for
station engineering
Execution mode
en06000115.vsd
Figure 41:
This window is for information only. The User Role may not be changed. The three selections
are for development purposes only. In the actual delivered configuration the changes are not taken and the user level keeps on Standard.
7.2
Logger options
en06000037.vsd
Figure 42:
As described in chapter 4, section 6 "CCT views and windows" CCT writes a log about all activities. This log is made visible by selecting the panel Output. In normal operation and with
skilled knowledge about the way it operates the list will include only the history of your actions.
The output view may be used when a problem occurs and it is not apparent why.
65
Chapter 4
PCM 600 and CCT tool set for
station engineering
It is also used when a failure occurs or when any other abnormal sequence occurs which may be
clarified by ABB. The log file is requested by ABB when you communicate a failure or any other
item. It is therefore requested to keep the log file history for this purpose. You may clear your
hard disc from the burden of the CCT history from time to time. Ways to configure the log:
7.3
Log Category
- allows a selection from which message type upwards the messages should be
listed in the Log window of the Output panel
Log File Size
- this is the size per file! A daily file of 1MB is hard to achieve. Be aware of
the volume when you select a daily file. Clear the history from time to time!
CCT extends the file name with the date when the file was started. So a daily
log makes it easy to identify the file which is of interest.
Append Log File
- will continue to write in the existing file when a new session is started. The
different parts of each session can be identified by date and time.
Write Daily Log
- we recommend enabling this function. A daily file makes it easier for search
in a list as well to check other dates etc.
Log File Path
- the path is fixed and can not be modified
Log File Name
- the name is fixed and can not be modified
en06000038.vsd
Figure 43:
CCT works with the IED section, the communication section and indirect with the Data Type
Template section. The organization structure of these section is presented in the Project Navigator panel. The visible naming of the elements (Nodes) can be arranged to your demand by selecting the available name elements and concatenate them in a sequence. This can be arranged
in the IEC 61850 Structure Option.
66
Chapter 4
PCM 600 and CCT tool set for
station engineering
This is possible for six different Node types and for each node type up to three naming elements
(Token) can be chosen. The available naming elements depends on the node type. You have to
chose a Separator between the naming elements to get the string readable.
Supported Node Types:
Communication section
- Subnetwork
- Connected access points
IED section
- IED
- Logical Node
- Access point
Data Type Templates
- Logical Node type
select a Node Type row or add a new one by clicking the Add button
select a node type out of the drop down list
select the various Token (1 to 3) and select a naming element out of the drop
down list
fill in the separators of your own choice
when you leave the selected row, CCT detects the changes and starts to update
the complete sections and the Project Navigator with the new presentation form.
This takes some ten seconds depending on project size etc. Wait until CCT has
finished the update.
To see the result you have to close the option window and open the sections in
the Project Navigator
An empty Token is left out. Make some examples to see the results and configure it to your demands.
67
68
Chapter 4
PCM 600 and CCT tool set for
station engineering
Chapter 5
Set up a project in PCM 600
69
Chapter 5
Set up a project in PCM 600
A project contains all information about the station configuration, the IEDs, the
engineering of the IEDs when done with PCM 600, the uploaded and downloaded files and internal files produced by PCM 600 and the tool components used to
run the project.
A project is stored under the directory of PCMDataBase on the PC or workstation
on which PCM 600 is installed. PCM 600 runs various projects under the control
of PCM 600. But only one project can be active at a time. These imported projects
are handled by the MSSQL$SERVER which is part of PCMDataBase.
Projects may be grouped into two categories:
- Engineering projects for IEC 61850 based stations. Engineering projects are
focused on the complete engineering of a substation with its IEDs. The most
practical size for a project is a substation.
- System monitoring projects. System monitoring projects are focused on the
monitoring information from the operating IEDs located in several substations. The most practical size for a project depends on the structure of the
grid and customer's responsibility. This is described in the 'Engineering
guide for IED 670 products'.
re-import the station.SCD file from CCT to update the ABB IED products and to
generate the ied.CID files
do signal engineering for the IEDs which are receiver of GOOSE messages.
70
Chapter 5
Set up a project in PCM 600
to import projects
to create new projects
to export projects
to delete projects out of the PCMDataBase
New
Import
en05000552.vsd
Figure 44:
71
Chapter 5
Set up a project in PCM 600
you may also select the project in the traditional way from the list shown in the
menubar File>list of last used projects.
Import a project
open the tree Projects on my computer.
select the icon Import Project.
a standard Windows file selection window will pop up
navigate to the directory where you have stored exported projects
select your project to import (suffix = PCMP)
PCM 600 will import the project. The contents will be reorganized according to
the PCM 600 internal needs. Depending on project size this can take some time.
the imported project will be listed under the tree Projects on my computer.
select the imported project and open it.
en05000608.vsd
Figure 45:
72
Chapter 5
Set up a project in PCM 600
en05000609.vsd
Figure 46:
export a project
open the tree Projects on my computer
select the project you want to export
select the icon Export Project
a standard Windows file selection window will pop up
navigate to the directory where you want to store the project
the file name may be adapted to your needs
PCM 600 prepares the contents of the project for import. The procedure is opposite to the task listed under import a project
the project still exists in PCM 600 and can be continued to be used
delete a project
open the tree Projects on my computer
select the project you want to delete
select the icon Delete Project
a warning window will pop up
be sure you have exported the project first before using it later
confirm that you want to delete the project
PCM 600 will delete all files etc. about this project from its PCMDataBase
rename a project
this is only possible when the project is not active in PCM 600
close the project when active
73
74
Chapter 5
Set up a project in PCM 600
Chapter 6
Set up a project in CCT
75
Chapter 6
Set up a project in CCT
to open projects
to create new projects
to save the actual project
to close projects
en06000119.vsd
Figure 47:
Open Project
select File > Open Project to open an existing project. This is only possible when
no project is active at this time. When you want to run another project you have
to close the running one first.
a MicroSoft standard window to select a file pops up. Rout to your directory
where the project you want to open is stored.
select the project and open it
CCT will read the data base and opens the project. This will take some time and is partly shown
in a progress bar at the bottom of the CCT window.
When the project is loaded you may check that it is the one you are looking for. A typical station.scd project may look like the figure below shows in the four SCL sections. The right
screen-shot shows the structure with available DataSets and report control blocks below a
LLN0.
76
Chapter 6
Set up a project in CCT
en06000040.vsd
Figure 48:
77
Chapter 6
Set up a project in CCT
en06000120.vsd
Figure 49:
CCT prepares the basics in the data base and generates the internal structure of an IEC 61850
SCL file. When it has finalized its preparation task the Project Navigator shows a basic structure
with a placeholder in the substation section for a first Voltage Level and under the Data Type
Templates section the list of IEC 61850 defined Base types of type Enum. The IED and Communication sections are empty.
Save
this action is always possible
CCT stores all values in the data base, so all additions and modifications are taken to the data
base.
Close Project
this action is always possible
CCT asks to save the changes made, when it shall close the project and changes are pending.
CCT will close the project which will take some time when it has to save the project before.
78
Chapter 6
Set up a project in CCT
2.1
en06000118.vsd
Figure 50:
CCT starts to read the station.SCD file and prepares the internals to operate the project with the
file. This will take some time and is partly shown in a progress bar at the bottom of the CCT
window.
79
Chapter 6
Set up a project in CCT
When the file is established you may check that it is the one you was looking for. A typical station.scd project may look like shown in figure 48
2.2
The CCT will generate a station.SCD file by keeping those parts which are not touched by the
CCT which is the Substation and Data Type Templates section. The communication and IED
section may have been modified and extended by CCT.
In addition CCT creates a set of ied.ccf files per IED in the project. These files include the SCL
part which is of interest for the named IED only. They may be used to re-import the IED part to
the IED configurator tool directly. These files are located at the same place as the station-SCD
file.
80
Chapter 6
Set up a project in CCT
3.1
81
Chapter 6
Set up a project in CCT
en06000117.vsd
Figure 51:
CCT starts to read the ied.ICD file and prepares the internals to operate the project with the
file(s). This will take some time and is partly shown in a progress bar at the bottom of the CCT
window.
When the file(s) is/are established you may check that they are the ones you was looking for.
3.2
82
3.3
Chapter 6
Set up a project in CCT
they are not included in the substation section. In this case it is a formal information which has no influence on the normal signal engineering for reports or for
GOOSE messages
en06000121.vsd
Figure 52:
The CCT will generate an ied.ICD file for the selected IED. The file may be re-imported to the
IED configurator tool for further use.
83
84
Chapter 6
Set up a project in CCT
Chapter 7
Station configuration with PCM 600
Chapter 7 Station
configuration with
PCM 600
About this chapter
This chapter describes how a station can be configured to fulfil the IEC 61850 requirements for
signal engineering. The configuration of the substation from voltage level to bay and IEDs and
the configuration of the communication structure is part of this chapter.
85
Chapter 7
Station configuration with PCM 600
en05000565.vsd
Figure 53:
86
Chapter 7
Station configuration with PCM 600
select IED
en05000557.vsd
Figure 54:
1.1
87
Chapter 7
Station configuration with PCM 600
starting with a string denoting the reference target object type, and ending with
the string Name. The technical key is used within SCL for referencing other objects. Observe that name is a relative identification within a hierarchy of objects.
2. A user oriented textual designation. This is contained in attribute desc. Attributes
are not allowed to contain carriage return, line feed or tab characters. The semantics of desc shall also be relative within an object hierarchy.
End of reference to the standard.
PCM 600 takes care for these two possibilities. The two possible designations naming are available per object in the object properties for all hierarchical levels beginning with the station as
highest level.
The technical key is automatically generated by PCM 600 based on the rules and type specifications of IEC 61346 and the definitions done for substations by a technical committee. The
technical key is shown in the Object Properties under SCL TechnicalKey.
the start point is the station which is predefined by AA1 where 1 is the index.
Leave the station name untouched, even when it is the wrong station name. PCM
600 needs this start definition to build the technical key by itself.
the second hierarchical level is the voltage level. The voltage level has to be selected in the Object Properties from a drop list. The corresponding character is
automatically included in all objects. The drop list explains the voltage range for
each character so it should be no problem to select the right character. The list is
build on the definitions of the standard.
the bay and the IED is appended with the coding defined in the IEC 61346 standard and the substation definition lists.
The user oriented textual designation is visible in the plant structure for each object. It is the
name given by default or changed via the Rename possibility. It is shown in the Object Properties in the row Caption.
en06000029.vsd
Figure 55:
88
Chapter 7
Station configuration with PCM 600
In the above figure the bay named in the example B_TR42 is visible in the object properties
with the two designations. The technical key AA1C1Q1 can be read like this:
1.2
When selecting an IED 670 a wizard is displayed which helps you to make the correct selection.
It includes:
a set of ordered functions available for engineering the logic and operation of the
functions
89
Chapter 7
Station configuration with PCM 600
It is important to understand, that the list of delivered functions correspond to the list of available
function blocks in the IED itself. You can not use more function blocks than ordered.
An IED is selected by:
en05000643.vsd
Figure 56:
Pre-configured IED
A pre-configured IED is described by:
the delivered hardware loaded with the basic functions and logic, ready for use
after some project specific engineering additions like IO signal marshalling etc.
the delivered engineering configuration
- configured logic with basic functions active for direct use
- predefined signals for IO which needs only to be routed to physical IO boards
the optional functions are available in the engineering tool fully configured and
presented in a template
90
Chapter 7
Station configuration with PCM 600
A pre-configured IED is ready to use after some minor engineering additions, which are in any
way project specific. Similar to the order specific version it includes only those functions and
options which are ordered and available in the IED itself.
en05000644.vsd
Figure 57:
When the pre-configured IED versions are not delivered in a zip file. Skip this window by selecting No PreConfig File. Check the availability of pre-configured IED versions in the CAP
531 template folder.
1.3
91
Chapter 7
Station configuration with PCM 600
en06000031.vsd
Figure 58:
The vendor has to supply an ied.ICD or ied.SCD file for each IED.
en06000032.vsd
Figure 59:
92
Chapter 7
Station configuration with PCM 600
The SCL file import starts and a progress window shows the status. A message will indicate the
conclusion of a successful import. The IED name may not change by loading the file. Check and
adapt the IED name to the projects definition with the Rename selection in the right mouse button menu.
Note
The actual version of PCM 600 does not support the integration of client IEDs in the plant structure nor in the communication structure.
This is actual only possible by adding the client ied.ICD file in the CCT and configure the communication section in the CCT with the additional client IED. See chapter 6, section 3 "Import/export ied.ICD files" how to do it.
93
Chapter 7
Station configuration with PCM 600
en06000208.vsd
Figure 60:
The Logical devices of an IED are listed when opening the IED. This is for information only
94
Chapter 7
Station configuration with PCM 600
en06000209.vsd
Figure 61:
95
Chapter 7
Station configuration with PCM 600
Station
en06000025.vsd
Figure 62:
96
Chapter 7
Station configuration with PCM 600
en06000026.vsd
Figure 63:
97
Chapter 7
Station configuration with PCM 600
start Import when you have completed your definitions. A progress window
will show the import procedure which will take some time depending on the number of IEDs.
en06000027.vsd
Figure 64:
3.1
98
Chapter 8
Signal engineering with CCT
99
Chapter 8
Signal engineering with CCT
en06000045.vsd
Figure 65:
The attribute editor can be used to get an overview and to verify the content of a Logical node.
Select a Logical node or a data object below the LN in the Project Navigator. Select Attribute
Editor in the IEC 61850 Data Engineering pane.
100
Chapter 8
Signal engineering with CCT
The visible list may be sorted in the sequence as shown in the figure above. In the example figure
a Logical node of type CVMMXU is selected. This LN type is used in IED 670 products and
represents the standard measured values of a bay. A part of the list of data attributes of the data
object TotW is shown. The different columns from left to right contain the description values
of each data attribute in a row listed in column one (Name).
No. Title
IEC 61850
Name
6, clause 9.5.4, table 44 Reference of the last named data attribute or basic type
described in this row
Descr.
6, clause 9.5.4, table 44 Description in free text form of the data attribute
FC
TrigOPt.
dchg
6, clause 9.5.4, table 44; Trigger a report transmission when the value changes. E.g. new
72, clause 10.2.2.4.3; position of a disconnector.
73 in all data class
tables
TrigOpt.
qchg
6, clause 9.5.4, table 44; Trigger a report transmission when the quality value changes.
72, clause 10.2.2.4.3; E.g. oscillatory of a binary signal because of a sensor failure
73 in all data class
etc.
tables
TrigOpt.
dupd
6, clause 9.5.4, table 44; Trigger a report transmission when a data value is updated.
72, clause 10.2.2.4.3; E.g. counter values are frozen and ready for transmission
73 in all data class
tables
Basic
Type
6, clause 9.5.4, table 44, Basic type according to definition in IEC 6185072 clause
72, table 2; 73 in all
5.5.2 and the enumerated types in IEC 6185073 clause 6
data class tables
(Attribute Types)
Type
6, clause 9.5.4, table 44 only used if Basic Type = Struct or Enum to refer to the appropriate enumeration type or DAType when Struct is given.
Value
6, clause 9.5.4.4
Value of the data attribute when it can be taken from the SCL
file
10
Short
Address
6, clause 9.5.4.3
The short address of a data attribute which can be used for several purposes. Do not modify them.
11
Value
Kind
6, clause 9.5.4.1
12
Count
6, clause 9.5.4, table 44 Used by the engineering tools internal. Optional for data
attribute of type structure. Shall state the number of array elements in the case where the attribute is an array.
101
Chapter 8
Signal engineering with CCT
select FC
select LN
add DataSet
select DO
select DA
en06000043.vsd
Figure 66:
When the Data Set Engineering pane is selected you will get a pane which includes four list boxes. One is for information only (Filtered Preview). The other three are needed to configure a
DataSet:
102
Data Sets
- lists all available DataSets with their names located in that Logical node
Chapter 8
Signal engineering with CCT
Remark
Analyzing all defined data attributes defined in IEC 6185073 only data attributes with FC =
MX or ST are marked with the capability to generate a trigger. And they belong to process data
objects which contain the process information used at runtime. All other data attributes belong
to control (commands), settings, functional configuration parameters or descriptions. These information are handled by other IEC 61850 communication services and are not part of a report.
103
Chapter 8
Signal engineering with CCT
select DA only
DO with stVal; q; t
en06000048.vsd
Figure 67:
Remark
CCT has to update the contents of all four list boxes whenever a new object, item etc. is selected.
To do this it reads the main part of data base to identify which objects etc. have to be presented.
This takes some time and it is not directly shown by an hourglass or similar. A small help in this
situation would be to start the Windows Task Manager and minimize it. The small dynamic icon
in the low right corner shows when the CPU is active.
Task Manager
en06000204.vsd
Figure 68:
104
Chapter 8
Signal engineering with CCT
select the Data Set Engineering tab in the IEC 61850 Data Engineering pane
select the Logical node where the new DataSet should be located. This should be
in normal cases the LLN0 of a LD.
when requested and agreed in a project it is possible by the IEC 61850 standard
to locate the DataSet in any LN. This is not allowed for DataSets which are used
by GOOSE messages. These DataSets are only allowed in LLN0 !
press the Add button to add a new Data Set in the Data Sets list box
give the DataSet a name. The name must be unique within the station to be able
to identify it in the communication between a client and a server IED.
select the FCD or FCDA which should be member of the DataSet in the IED Data
Model list box.
select the correct FC out of the list in the Func. Constraint list box
click Add to add the FCD, FCDA to the Data Set Entries list box
click Modify when the selected member of the Data Set Entries list box should
be replaced or modified by the FCD, FCDA selected in the IED Data Model list
box
Repeat the procedure for all DataSets which are needed in this IED. Continue to do it for all IEDs
where additional DataSets are requested.
2.1
Predefined DataSet
The IEC 61850 standard allows to have predefined DataSets which the vendor of an IED has
included in his product. These predefined DataSets will be visible when you open an IED and
will be listed under the LLN0.
These DataSets may be modified or extended in a project. The possibility to do it must be announced by the vendor of the IED.
ABB has defined four predefined DataSets for the IED 670 products:
MeasFlt
- includes those measured values which will be transmitted on dchg trigger
given by a threshold value (deadband)
StatIed
- includes the behavior status of all Logical nodes
StatNml
- includes the trip signals (operate) of all protection Logical nodes
StatUrg
- includes the urgent alarms of the Logical nodes. The definition of what is urgent was done by ABB experts and may be checked by the project
105
BRCB engineering
Chapter 8
Signal engineering with CCT
BRCB engineering
The concept of buffered report control blocks (BRCB) is described in a brief form in chapter 2,
section 3.4 "Signal engineering".
en06000047.vsd
Figure 69:
When the Report Control Engineering pane is selected you will get a pane which contains a list
with several columns and some or a lot of rows. Each row represents a BRCB description with
all BRCB attributes which are of interest.
When already client IEDs are linked to that BRCB this is visible by the icon element to expand
the BRCB for next level rows. Each next level row contains the identification of a linked client
IED.
The five main steps to generate a BRCB are:
106
add a new BRCB row to the list by clicking Add... Report Control in the bottom
area of the pane
BRCB engineering
Chapter 8
Signal engineering with CCT
give the BRCB a unique name according to the rules described in IEC 6185072
clause 14.2.2.2 and the rules defined in the project
select the DataSet out of the list of available DataSets for this BRCB. Always
only one DataSet per BRCB. See the example in the figure above
link the BRCB to the client IEDs which should receive these event telegrams.
This is done by selecting the icon of the Logical node of the client IED (e.g. ITCI
or IHSI) and link it to the name field of the corresponding BRCB by using the
drag-and-drop method. Repeat this for all client IEDs which should receive the
information. See the arrow in the figure above.
configure the BRCB attributes to the standards defined in the project.
do Update DataFlow by selecting this task via the menubar Tools > IEC 61850
Data Flow Engineering. CCT will now add the needed information in the SCL
file in:
- the IED section for the 'BRCB' in the Logical node defined for this DataSet
and therefore for the BRCB. Should be normally LLN0
- the IED section with the identification of the connected client IEDs per
BRCB
en06000036.vsd
Figure 70:
IEC 618506 clause 9.3.8 and listed in table 22, table 23 and table 24
IEC 6185072 clause 14.2 and mainly listed in table 23
the attributes used by the CCT to get the description from the user are all listed
in the CVC selection box for the BRCB.
For the identification of a column the same text is used in the BRCB list and in the CVC. To see
them in the CVC completely you have to select an element. The complete description will pop
up, when there is more text then in the visible part. The sorting order for the column may be
changed to your demands. So the only element to make the link to CVC is the identification text
of the column. How to operate the CVC see chapter 4, section 6.3 "CCT Column visibility control".
107
BRCB engineering
Chapter 8
Signal engineering with CCT
BRCB attributes
1
23
en06000205.vsd
Figure 71:
108
BRCB engineering
Table 1:
Chapter 8
Signal engineering with CCT
BRCB attributes
No. Title
IEC 61850
Name
Descr.
DataSet
The name of the data set to be sent by the report control block;
datSet can only be empty within an ICD-File.
Integrity
Period
Integrity period in milliseconds see IEC 61850-7-2. Only relevant if trigger option period is set to true
If TrgOp is set to integrity, the attribute IntgPd shall indicate the
period in milliseconds used for generating an integrity report.
An integrity report shall report the values of all members of the
related DATA-SET. BufTm shall have no effect when this
change issues a report.
A value of 0 shall indicate that no integrity reports shall be
issued.
NOTE: An integrity scan may transmit the same values as a
general interrogation. The integrity scan is issued by the server.
The general-interrogation is issued by the client.
Config.
Ref.
Buff
Buff.
Time
109
BRCB engineering
Chapter 8
Signal engineering with CCT
No. Title
IEC 61850
Max.
Enabled
10
Report
6, clause 9.3.8, table
Enabled 23,1
Description
11
TrigOpt.
Dchg
12
TrigOpt.
Qchg
data-change (dchg)
quality-change (qchg)
data-update (dupd)
integrity
genral-interrogation
The trigger options dchg, qchg, and dupd refer to the attribute
trigger option (TrgOp) of the DataAttribute of the common
DATA classes in IEC 61850-7-3. The trigger options integrity
and general-interrogation shall be trigger conditions defined by
the attributes IntgPd and GI of the BRCB respectively
Details related to the generation of a report based on the different trigger options shall be as specified in 14.2.3.2.3.
13
TrigOpt
Dupd
14
TrigOpt.
Period
15
16
Time
Stamp
17
110
BRCB engineering
Chapter 8
Signal engineering with CCT
No. Title
IEC 61850
18
Reason
Code
Data
Ref.
20
Buffer
Overfl.
21
22
Conf.
Ref.
23
Segm.
111
BRCB engineering
Table 2:
112
Chapter 8
Signal engineering with CCT
No. Title
IEC 61850
Id
ReportControlId
LogicalNodeId
Order
Client
Logical
Node
Name
GoCB engineering
Chapter 8
Signal engineering with CCT
GoCB engineering
The concept of GOOSE control blocks (GoCB) is described in a brief form in chapter 2,
section 3.4 "Signal engineering".
en06000050.vsd
Figure 72:
When the Goose Control Engineering pane is selected you will get a pane which contains a list
with several columns and some rows. Each row represents a GoCB description with all GoCB
attributes which are of interest.
When already IEDs are linked to that GoCB this is visible by the icon element to expand the
GoCB for next level rows. Each next level row contains the identification of a linked IED.
GOOSE messages are not handled by the server. They are directly send by the communication
handler as Unicast messages. The access to the Ethernet may need additional address information and timing parameters to monitor the correct sending. These parameters can/must be set per
GoCB in an additional address definition row.
113
GoCB engineering
Chapter 8
Signal engineering with CCT
add a new GoCB row to the list by clicking Add ... GSE Control in the bottom
area of the pane
give the GoCB a unique name according to the rules described in IEC 6185072
clause 15.2.1.1 and the rules defined in the project
select the DataSet out of the list of available DataSets for this GoCB. Always
only one DataSet per GoCB. See the example in the figure above
link the GoCB to the IEDs which should receive these GOOSE message. This is
done by selecting the icon of the bay IED and link it to the name field of the corresponding GoCB by using the drag-and-drop method. Repeat this for all bay
IEDs which should receive the information. See the arrow in the figure above.
configure the GoCB attributes to the standards defined in the project.
configure the address parameters to the standards defined in the project
do Update DataFlow by selecting this task via the menubar Tools > IEC 61850
Data Flow Engineering. CCT will now add the needed information in the SCL
file in:
- the IED section for the 'GoCB' and for the 'Input' structure elements in the
LLN0
- the communication section for the GSE structure
precondition to do the update dataflow is a correct and complete communication
section including all IEDs with their subnetwork and access point identification
en06000036.vsd
Figure 73:
Each IED which is selected to receive the GOOSE message will get the description of an 'Input'
structure in its SCL IED section in the LLN0 of the LD. It is then the task of IED engineering to
route the input signals of a GOOSE message to the application which deals with the information.
See the brief description in chapter 2, section 3.4 "Signal engineering".
114
GoCB engineering
Chapter 8
Signal engineering with CCT
en06000092.vsd
Figure 74:
IEC 618506 clause 9.3.10 and listed in table 22 for the additions in the IED section
IEC 618506 clause 9.3.13 and table 30 for the designation of the input block in
the receiver IED
IEC 61850 clause 9.4.4 and listed in table 34 for the additions in the communication section
IEC 6185072 clause 15.2 and table 28
the attributes used by the CCT to get the description from the user are all listed
in the CVC selection box for the GoCB.
For the identification of a column the same text is used in the GoCB list and in the CVC. To see
them in the CVC completley you have to select an element. The complete description will pop
up, when there is more text then in the visible part. The sorting order for the column may be
changed to your demands. So the only element to make the link to CVC is the identification text
of the column. How to operate the CVC see chapter 4, section 6.3 "CCT Column visibility control".
115
GoCB engineering
Chapter 8
Signal engineering with CCT
GoCB attributes
1
en06000206.vsd
Figure 75:
Table 3:
116
No. Title
IEC 61850
Name
Descr.
A description text.
DataSet
The name of the data set to be sent by the GSE control block.
For type=GSSE, the FCDA definitions in this data set shall be
interpreted as DataLabels according to IEC 61850-7-2. The
attribute datSet can only be empty within an ICD-File.
Type
If the type is GSSE, then only single indication and double indication data types are allowed for the data items referenced in
the data set, otherwise all data types are allowed. Note that on
stack level, each type might be mapped differently to message
formats. The default type value is GOOSE
Identifier.
GoCB engineering
Chapter 8
Signal engineering with CCT
No. Title
IEC 61850
Config.
Ref.
Descr.
Textual description
MaxTime
6, clause 9.4.4
MAC
Address
6, clause 9.4.3
ApplicationId
VLAN ID
VLAN
Prio
Client
IED
Order
117
GoCB engineering
118
Chapter 8
Signal engineering with CCT
G
8
T
&
"
D
Q
F
455IpSphsywrtp45
Rgfty4xftyIih
R8$"&Up
Rpipy
Spwpsyp'!#
!
9fhtxtwp'!#!#&%
Bypyp'fgghxgftyfxfty
Itypiyphhwpifyiphwfgpwwpifpf8wfyipGx