Professional Documents
Culture Documents
,(&6WDWLRQ
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 GUARAN-
TEED PROPERTIES. IN THE INTERESTS OF OUR CUSTOMERS, WE CONSTANTLY SEEK TO
ENSURE THAT OUR PRODUCTS ARE DEVELOPED TO THE LATEST TECHNOLOGICAL STAN-
DARDS. 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 Västerås
Sweden
Telephone: +46 (0) 21 34 20 00
Facsimile: +46 (0) 21 14 69 18
www.abb.com/substationautomation
Contents
Chapter Page
Chapter 4 PCM 600 and CCT tool set for station engineering.... 35
PCM 600 and CCT tool set for station engineering ........................... 36
PCM 600 views and windows ............................................................ 37
PCM 600 the toolbar and the mouse ............................................ 41
PCM 600 options for operation .......................................................... 44
PCM 600 access .......................................................................... 44
Connectivity package support for PCM 600 ...................................... 50
PCM 600 Set up communication link per IED 670............................. 52
PCM 600 Set up communication link per Generic IEC 61850 IED 52
CCT views and windows.................................................................... 53
The toolbar and the mouse........................................................... 56
Spreadsheet features ................................................................... 57
CCT Column visibility control........................................................ 61
CCT options and features.................................................................. 64
Execution mode ............................................................................ 65
Logger options .............................................................................. 65
Contents
Chapter 1 Introduction
1
Introduction to the IEC 61850 Station Chapter 1
Engineering guide Introduction
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 tech-
nical data sorted per function. The technical reference manual should be used as a technical ref-
erence 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 per-
forming 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 Operator’s Manual (OM) contains instructions on how to operate the protection IED dur-
ing normal service once it has been commissioned. The operator’s 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.
2
Introduction to the IEC 61850 Station Chapter 1
Engineering guide Introduction
The IEC 61850 Station Engineering guide contains descriptions of IEC 61850 station engi-
neering 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.
Requirements
The system engineer must have a thorough knowledge of protection and/or control systems, pro-
tection/control equipment, protection/control functions and the configured functional logics in
the IED 670 devices. The installation and commissioning personnel must have a basic knowl-
edge in the handling electronic equipment.
3
Introduction to the IEC 61850 Station Chapter 1
Engineering guide Introduction
Documents related to the PCM 600 and CCT tool set Identity number
Connection and Installation components 1MRK 013 003-BEN
Test system, COMBITEST 1MRK 512 001-BEN
Accessories for IED 670 1MRK 514 012-BEN
Getting started guide IED 670 1MRK 500 065-UEN
SPA and LON signal list for IED 670 1MRK 500 075-WEN
IEC 61850 Data objects list for IED 670 1MRK 500 077-WEN
Generic IEC 61850 IED Connectivity package 1KHA001027–UEN
Protection and Control IED Manager PCM 600 Installation sheet 1MRS755552
Engineering guide IED 670 products 1MRK 511 179–UEN
Revision Description
- First release
4
About this chapter Chapter 2
IEC 61850 station engineering
5
Station engineering in IEC 61850 Chapter 2
IEC 61850 station engineering
This chapter contains some explanations about the definitions made by the standard. They may
be requested to get a better understanding and as a reference when the different engineering steps
made with the tools PCM 600/CCT are described. It is expected, recommended that the reader
has a general knowledge about the IEC 61850 standard and especially of the parts 6 and 7.
Station
System
IED
DB
DB
Vendor B
Configurator
Vendor C
Substation Configuration
stat.SCD
ied.ICD
IED IED IED
Configurator Configurator Configurator
Vendor A Vendor B Vendor C
Configured IED
ied.CID
IED IED
SA
HSI NCC GW
Gateway
Vendor A Vendor B
Substationn
en06000105.vsd
6
Station engineering in IEC 61850 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:
7
Station engineering in IEC 61850 Chapter 2
IEC 61850 station engineering
8
Designation model of IEC 61850 Chapter 2
IEC 61850 station engineering
A substation of any size consists of buildings, a lot of primary equipment, substation control
equipment and a lot more. Each item has a name and will be identified by explaining to which
part it belongs to. The rules will differ from country to country and by each utility.
=DeStat (DemoStation)
=E1 (e.g. 135 kV)
=Q1 =Q2 =Q3
=- WA1
=- WA2
en06000108.vsd
9
Designation model of IEC 61850 Chapter 2
IEC 61850 station engineering
The IEC 61850 standard is based on the hierarchical addressing and designation model in a sta-
tion. It follows in this way the structure of the substation equipment independent of IED struc-
ture 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 desig-
nations.
• 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 in-
dependent of a language, project etc.
• the standard use only single characters per level which makes the total designa-
tion very short and therefore saves bytes to be transmitted.
• by using this designation model in IEC 61850 it allows to use an easy project in-
dependent 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
Designation model of IEC 61850 Chapter 2
IEC 61850 station engineering
Station = DeStat
=E1 =Q1
=-QB1 =-QB2
FC = ST Pos
stVal LD2
q RBRF
LD1
t
=-QB9 PTRC
origin
=P
=B PDIS
MMXU1
=-BI1 PTEF
=-BU1
PTOC
RREC
=-QC9
en06000110.vsd
Figure 3: IEC 61850: Object identification model based on IEC 61346 (FuncName)
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
Designation model of IEC 61850 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.
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.ige-
vu.de”. The documents can be found on the page “Veröffentlichungen”.
The following extracts of the designation trees shows the position of the used elements.
12
Designation model of IEC 61850 Chapter 2
IEC 61850 station engineering
F Protective equipment
FA Surge arrester
FP Protective relay
Q HV switching equipment
QA Circuit breaker
QB Disconnector
QC Earthing switch
S Controlling equipment
B Control unit
W Transporting equipment
A Busbar
Signal and control cable,
H
data bus (optical)
en05000646.vsd
13
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
It is of course not needed to know the XML file in its details and do any step which requests
XML knowledge, but the organization of the information within the SCL files (ied.ICD and/or
station.SCD) might be of interest. Especially to know where the engineering additions like
DataSets and Control Blocks belongs to.
The SCL XML file is defined in five sections or descriptions, which are specified in IEC
61850–6 clause 9. These sections are:
• 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 es-
tablish 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 be-
cause they are logically defined as part of the Logical nodes (see IEC 61850–7–2 clause 9). The
CCT needs the correct configured communication section when it comes to GOOSE engineer-
ing.
The Data type templates section is requested to give the correct content description of each Log-
ical 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
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
Header
Header
Id FuncName
ToolId or
Nam eStructure IEDName
Substation
VoltageLevel
Bay
LNode
IED LD LN
Station
IED LD LN
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
DOI
IED
SettingControl
DataTypeTemplates
LNodeType
DO
DOType
DOType
DA SDO
DAType
DAType
BDA
Enum Type
Enum Type
en06000111.vsd
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 struc-
ture and/or in the communication structure. All available Logical nodes of an IED are linked to
the substation section.
15
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
A reference to the GoCB is included in the communication section when the GoCB is config-
ured.
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.
In part 6 clause 8.4 of the standard the object and signal designation rules are described. The
identification for the signals are therefore also used in the telegrams defined in IEC 61850–8–1
is named “Technical key”. The technical key is used within the SCL description to identify and
reference objects. See chapter 2, section 1 "Station engineering in IEC 61850" about the concept
based on IEC 61346. PCM 600 generates an “SCL Technical key” independent of the naming
given by the project. The PCM 600 generated technical key is based on the definitions given in
IEC 61346 and for electrical substations. When a project is using its own naming model this will
be used by the SCL description as technical key. PCM 600 allows to select the version which
should be used in the SCL files when exporting a station.SCD file.
1. a user defined part identifying the Logical device LD in the process (LDName)
2. a function related part to distinguish several LNs of the same class within the
same LD/IED (LN-Prefix)
3. the standardized LN class name and the LN instance number, which distinguishes
several LNs of the same class and prefix within the same LD/IED
4. a signal identification inside a LN consisting of data and attribute name as de-
fined in IEC 61850–7–3 and IEC 61850–7–4
16
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
en06000112.vsd
The above figure is taken from the standard IEC 61850–6 (figure 5).
The standard defines two options how to use part 1 and part 2 above:
17
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
Substation 1
LDCL1
LN
LN
LN
LN
LDCL2
LN
LN
LN
LN
VL1 2
VL2 2
6
Substation section IED section Substation section
1 2 3 4 5
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 be-
longs to the LDName part. It identifies the equipment or sub-equipment object in the primary
18
Substation Configuration description Chapter 2
Language (SCL) 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 nam-
ing is based in the process objects only.
The LNName is in this option the LN class and the LN instance (6) only.
Substation 1
LDCL1
LN
LN
LN
LN
LDCL2
LN
LN
LN
LN
VL1 2
C
IED section IED section
A B
19
Substation Configuration description Chapter 2
Language (SCL) 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 re-
lated naming model (IEDName) will be used.
• Ethernet as medium
• MMS (Manufacturing Message Specification) protocol as defined in ISO 9506–1
and IOS 9506–2.
The IEC 61850 standard describes in part 7–2 the Abstract Communication Service Interface
(ACSI) in a media and protocol independent form. Part 8–1 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
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
IED IED
(client) (client)
- Access Point (AP) - Access Point (AP)
- Address - Address
- GSE; GoCBs - GSE; GoCBs
Communication Communication
Subnetwork AP
AP
en06000101.vsd
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
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
Client Client
IED 1 IED 2
Subnetwork 1
VL 1 VL 2
Client Client
IED 1 IED 2
Subnetwork 1
Subnetwork 2
VL 1 VL 2
en06000103.vsd
Both variants fulfil the requirements and performance. Variant 2 may be used, when the avail-
ability question is discussed. In this case only one voltage level of the station is lost when a sub-
network fails. The client IEDs must be able to handle two access points.
22
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
ITMI. They are the receiver of information in monitoring direction and send-
er 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
Server IED
SB1.LD1
Logical
Node
LLN0
LPHD Data
SXCBR1 Mod
SCSWI1 Beh
SXSWI1 Health
Data
SCSWI2 NamePlt Attribute
SXSWI2 Pos ctlVal
SXSWI3 OpCnt q
SCSWI4 BlkOpn t
CVMMXU1 Control
en06000104.vsd
The above figure is a short summary about the logical organization of the signals below the IED.
23
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
• the LN LLN0 is a special LN per LD and contains the DataSets, the various con-
trol 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 orga-
nization 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.
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
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
LD1
DATA-SET
LLN0 LD1/LLN0.AppPos
LPHD LD1/SXCBR1.Pos FC=ST
SXSWI2 Pos
SCSWI3
SCSWI4 q
SXSWI4 Pos t
SCSWI5 Origin
CVMMXU1
en06000106.vsd
• 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 = Func-
tional Constraint Data Attributes) is included in the SCL file in the IED section in the Logical
device subsection. As specified in IEC 61850–7–2 clause 9, the DataSets are part of a Logical
node. They are most likely included in the LLN0.
25
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
The contents of a BRCB is listed in IEC 61850– 7–2 in clause 14, table 23. The BRCB contains
a lot of attributes which are of interest to handle and secure the communication between the cli-
ent 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 ad-
ditional events will be generated as a follow up it is useful to wait for exam-
ple 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 oth-
er 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 inter-
rogation). 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 Da-
ta-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 com-
munication. 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 7–3. The other two
belonging to the configuration of control blocks. The five trigger options are:
• dchg = data-change
26
Substation Configuration description Chapter 2
Language (SCL) 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 min-
utes).
• general interrogation
- This trigger is forced by the clients (= station level IED; NCC gateway, sta-
tion 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 im-
age of the actual process signal status can be transmitted to the client.
The selected client IED with the corresponding LN (e.g. ITCI) is included in the SCL structure
of the Report Control description of the IED section.
CCT is doing it when the client LN is linked with the name field of the BRCB by the
drag-and-drop method.
The description of the BRCB with selected DataSet, configured parameters and selected IEDs
is included in the SCL file in the IED section in the LN0 structure for the LD where this LN0
belongs to.
27
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
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
28
Substation Configuration description Chapter 2
Language (SCL) IEC 61850 station engineering
Receive
Receive
Receive
Receive
Receive
Receive
Send
Send
Send
Data-set Data-set Data-set
LN LN LN
LN LN
LN
LN LN LN
LN
LN LN LN LN LN
Subnetwork
Comm. Comm.
GSE GSE
Server Server
LD1 LD1
GoCB
GoCB
GoCB Input
Input
Input GoCB
GoCB
GoCB Input
Input
Input
DataSet
DataSet
DataSet DataSet
DataSet
DataSet
LN0 LN0
en06000109.vsd
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
Substation Configuration description Chapter 2
Language (SCL) 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 com-
munication (request — respond on application level). The return message is not a must. It de-
pends 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 at-
tribute. 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 re-
ceive the telegram. The GOOSE message includes sequence number etc. to verify that all mes-
sages 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.
GOOSE messages bypass the server and send direct from the communication part on the Ether-
net. This is identified for the communication in the SCL communication section in the GSE el-
ement, where the name of the GoCB is listed under the ConnectedAP.
The IEDs which shall receive the GOOSE are selected by CCT. CCT is doing it when the IED
itself (the IED icon) is linked with the name field of the GoCB by the drag-and-drop method.
30
About this chapter Chapter 3
IEC 61850 Station configuration
tasks
31
IEC 61850 Station configuration tasks Chapter 3
IEC 61850 Station configuration
tasks
• the definition of data objects and their common data classes with their data at-
tributes
• the definition of Logical nodes (LN) as the communication interface for a substa-
tion function (e.g. a protection function)
• the definition of a basic communication structure for substation and feeder equip-
ment
• 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 con-
figuration 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
IEC 61850 Station configuration tasks Chapter 3
IEC 61850 Station configuration
tasks
text
station_PCM.SCD
CCT
y configure DataSets per IED
y configure and link report control blocks
y configure and link Goose control blocks
y export station.SCD file
station.SCD
en06000207.vsd
33
IEC 61850 Station configuration tasks 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 configura-
tion 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 con-
figured 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 activi-
ties
• 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 in-
volved 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
About this chapter Chapter 4
PCM 600 and CCT tool set for
station engineering
35
PCM 600 and CCT tool set for station Chapter 4
engineering PCM 600 and CCT tool set for
station engineering
The two tools are able to do the station configuration tasks as defined by IEC 61850–6. They are
doing it for the IED and subnetwork configuration in a plant structure and in a communication
structure by PCM 600. The signal engineering which is defined by the DataSets, the report con-
trol blocks and the GOOSE messages is done with the CCT.
PCM 600 is a tool which supports in itself the tasks needed to do IEC 61850 station engineering
but it is also the platform for several sets of tool components used to support IED engineering
for ABB IED product families. This manual describes the IEC 61850 station configuration task
only.
It is requested to use the IED engineering guide manuals in addition when ABB IEDs are part
of the IEC 61850 based station project.
The description of the PCM 600 is limited in most cases to the part needed for IEC 61850 station
configuration.
The CCT is a tool which is used by ABB as a base product for signal engineering of several pro-
tocols. This version of CCT is also limited to the tasks needed to do signal engineering for IEC
61850 protocol. The precondition to use CCT is that the plant structure with the IEDs and the
communication structure is build by PCM 600. See chapter 3 "IEC 61850 Station configuration
tasks" for a description of the general tasks for IEC 61850 station configuration by using PCM
600 and CCT.
36
PCM 600 views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
When you start PCM 600 and no project is already selected you will get an empty window with
the base menubar and toolbar only. Once you have selected a project, you will be given the pos-
sibility to select different views. The start menu of a project may look like the menu shown in
the figure below.
Project
Explorer Object
Place for
& Properties
selected tool
Object
Types
en06000028.vsd
37
PCM 600 views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000580.vsd
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 commu-
nication 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 Struc-
ture tab. Select communication and an additional page will be included which shows the com-
munication structure of the PCM 600
en05000562.vsd
38
PCM 600 views and windows 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 prop-
erties like object naming in the HMI picture and so on. It might be necessary to check some prop-
erties 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
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
PCM 600 views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000558.vsd
Object Type
en05000556.vsd
The window Object Type can be used to build up a plant structure using drag and drop and se-
lecting 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 Transmis-
sion IED”.
More details to different views etc. are given in chapter 5 "Set up a project in PCM 600".
40
PCM 600 views and windows 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.
The right button of the mouse is supported. Clicking the right mouse button opens a context sen-
sitive menu. This menu presents all possible actions and selections corresponding to the selected
object.
en05000555.vsd
Figure 22: PCM 600: Conditional selection by the right mouse button
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
PCM 600 views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000554.vsd
The window keeps open after your selection. Depending on the selected object it will show di-
rectly the possible choices.
The PCM 600 stores all changes for which it is responsible directly in the database. This is useful
because these changes are only of type organization and have no influence on IED data. Chang-
es, additions etc. done within a tool are only moved to the project database when they are saved.
This possibility is context sensitive and will be displayed in the PCM 600 base menu bar under
File when a tool has the ability to save.
42
PCM 600 views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000574.vsd
43
PCM 600 options for operation Chapter 4
PCM 600 and CCT tool set for
station engineering
1. Log Configuration
• to organize the log file which is produced during the sessions and shown in
the Output view of PCM 600
2. Category Manager
• allows the definition of user groups with different rights to work with PCM
600 according to their need and task.
3. System Settings
• specifies the basic decision about access rights for PCM 600 by the authen-
tication method
4. User Manager
• is used to edit the list of persons or users which can use PCM 600 when an
authentication method is selected
Changes in the System Settings, Category Manager and User Manager can only be done by a
user of the category type “System Engineer”.
The used alternative is selected in the Authentication. Select the System Settings window to
choose the authentication.
44
PCM 600 options for operation Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000614.vsd
PCM 600 must be reinstalled and all projects will be lost if this password is not available!
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 in-
stalled.
• YES = Authentication is used. Select the method with one of the two choices:
2. PCM Authentication or
3. Windows Authentication
45
PCM 600 options for operation Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000613.vsd
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.
• 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
PCM 600 options for operation Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000610.vsd
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
PCM 600 options for operation Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000617.vsd
Category Manager
Different categories of default user are defined for PCM 600:
• 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 opera-
tion
- has no access to the engineering tools
- has no user management rights
48
PCM 600 options for operation Chapter 4
PCM 600 and CCT tool set for
station engineering
en05000615.vsd
49
Connectivity package support for PCM 600 Chapter 4
PCM 600 and CCT tool set for
station engineering
How to install a new product package or to add an additional communication protocol is de-
scribed in the documentation for PCM 600.
To engineer the ABB IED 670 product family you must have enabled the use of these tools and
protocols in the connectivity package manager. Please check that before you may start the PCM
600.
en05000561.vsd
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
Connectivity package support for PCM 600 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 proto-
col.
• LON Connectivity Package
- This package is not needed for IED 670 products. It is used for products us-
ing 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 us-
ing SPA to communicate with PCM 600.
51
PCM 600 Set up communication link per IED Chapter 4
670 PCM 600 and CCT tool set for
station engineering
When an additional link from PCM 600 to the IED 670 is requested see 'Engineering guide for
IED 670 products'.
The IP address used for the Ethernet channel with IEC 61850 protocol has to be filled in by the
PST tool as part of IED 670 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 dis-
turbance 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
CCT views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
When you start CCT you will get a screen with the different panels but no contents. Once you
have selected a project, you will get the possibilities to select different panels. The typical screen
with an open project may look like shown in the figure below.
Project
Navigator Control
&
Action
IEC 61850
Data Engineering
Properties
en06000033.vsd
Figure 31: CCT: Base screen example
CCT has different panels (in PCM 600 called views). The wording panel is taken here because
the CCT use it.
Possible panels:
53
CCT views and windows 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 address-
ing rules.
54
CCT views and windows 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 ex-
pected. 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.
• 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".
The list of selections shown when the Attribute Editor is selected are not foreseen for IEC 61850
views.
• Attribute Editor
• Data Set Engineering
• Report Control Engineering
• Goose Control Engineering
55
CCT views and windows 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 re-
quested 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
en06000036.vsd
en06000035.vsd
56
CCT views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000113.vsd
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.
57
CCT views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
Row selection by
Allow Grouping Show filter row Filter action
text searching
Grouping
Column header
Filter
Pinning
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
CCT views and windows 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.
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”
Column sorting
To sort the sequence of columns to your own criteria can be done by the standard MicroSoft
methods. Select the header element of a column and move it left or right to the position you want
to have it. The position where it will be placed will be shown by two red arrows. In the same
standard way it is possible to adjust the width of a column by selecting the right border of the
column and move it.
Grouping
Grouping allows to sort the rows of a spreadsheet in groups. The different groups which will ap-
pear depends on the type and contents of the selected row for grouping.
59
CCT views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000046.vsd
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
CCT views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
To delete a row or several rows you have to select these rows by the standard MicroSoft methods
(CTRL or SHiFT button pressed). Press the keyboard Delete key to delete the selected rows. A
confirmation window will pop up and you have to confirm your action.
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 se-
quence of data objects and data attributes in a complex data object structure). You have to dese-
lect the spreadsheet and select it again to get the logical sequence back.
Select the column in which you are searching. Type the first character of the element. The first
row which matches will be highlighted. Each time you type the character the next row which
matches will be highlighted.
The use and definition of the different columns is described in chapter 8, section 3 "BRCB en-
gineering" and section 4 "GoCB engineering".
61
CCT views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000114.vsd
Selected = all possible columns of this group are shown. Not selected = all columns are disabled.
Selected and shaded = each column can be selected individually
62
CCT views and windows Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000090.vsd
Figure 38: CCT: GoCB panel with all possible columns selected
en06000091.vsd
Figure 39: CCT: GoCB panel with some columns not shown
63
CCT options and features 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
64
CCT options and features Chapter 4
PCM 600 and CCT tool set for
station engineering
en06000115.vsd
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 tak-
en and the user level keeps on Standard.
en06000037.vsd
As described in chapter 4, section 6 "CCT views and windows" CCT writes a log about all ac-
tivities. 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
CCT options and features 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:
• 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
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 Naviga-
tor panel. The visible naming of the elements (Nodes) can be arranged to your demand by se-
lecting the available name elements and concatenate them in a sequence. This can be arranged
in the IEC 61850 Structure Option.
66
CCT options and features 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.
• 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 de-
mands.
67
CCT options and features Chapter 4
PCM 600 and CCT tool set for
station engineering
68
About this chapter Chapter 5
Set up a project in PCM 600
69
Set up a project in PCM 600 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 download-
ed 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 substa-
tions. 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
Managing projects in PCM 600 Chapter 5
Set up a project in PCM 600
These projects are handled by the MSSQLPCMSERVER which is included in the PCMData-
Base.
It is possible
• to import projects
• to create new projects
• to export projects
• to delete projects out of the PCMDataBase
To open a project select File>Open/Manage Projects. The Open/Manage Project window will
pop up.
New Import
en05000552.vsd
71
Managing projects in PCM 600 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
72
Managing projects in PCM 600 Chapter 5
Set up a project in PCM 600
en05000609.vsd
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 oppo-
site 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
Managing projects in PCM 600 Chapter 5
Set up a project in PCM 600
74
About this chapter Chapter 6
Set up a project in CCT
75
Managing projects in CCT Chapter 6
Set up a project in CCT
It is possible
• to open projects
• to create new projects
• to save the actual project
• to close projects
en06000119.vsd
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 sta-
tion.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
Managing projects in CCT Chapter 6
Set up a project in CCT
en06000040.vsd
77
Managing projects in CCT Chapter 6
Set up a project in CCT
en06000120.vsd
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 Com-
munication 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
Import/export station.SCD files Chapter 6
Set up a project in CCT
en06000118.vsd
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
Import/export station.SCD files 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 sta-
tion.scd project may look like shown in figure 48
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
Import/export ied.ICD files Chapter 6
Set up a project in CCT
CCT can be used to configure DataSets and report control blocks (BRCBs) for a single IED be-
fore it is integrated in a station project. This makes sense when the IED is used more then once
in the project. Import of the ied.ICD file to CCT, do DataSet and BRCB engineering and export
it back allows to use the extended IED as a template for similar or same control or protection
IEDs.
In the actual version of PCM 600 it is only possible to include client IEDs in a station project
via CCT.
81
Import/export ied.ICD files Chapter 6
Set up a project in CCT
en06000117.vsd
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.
82
Import/export ied.ICD files Chapter 6
Set up a project in CCT
• they are not included in the substation section. In this case it is a formal informa-
tion which has no influence on the normal signal engineering for reports or for
GOOSE messages
en06000121.vsd
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
Import/export ied.ICD files Chapter 6
Set up a project in CCT
84
About this chapter Chapter 7
Station configuration with PCM 600
Chapter 7 Station
configuration with
PCM 600
85
Set up a substation for IEC 61850 Chapter 7
Station configuration with PCM 600
You will build up the plant structure according to your project requirements. To do this PCM
600 offers some elements which build the hierarchical order from a Center down to the IEDs in
a bay. The organization of the station according to IEC 61850–6 is done in PCM 600 on the basis
of the 'Product related naming' (IEDName). This is shown in chapter 2, section 3.1 "The Substa-
tion section", figure 8.
Level (2.) is optional all other level are a must to identify an IED.
Once a plant structure is built the identification should be renamed by the names/identifications
used in your project and to the specification for object identification as described in chapter 2
"IEC 61850 station engineering". Use the right mouse button to build the plant structure and to
rename the elements.
en05000565.vsd
86
Set up a substation for IEC 61850 Chapter 7
Station configuration with PCM 600
select IED
en05000557.vsd
Figure 54: PCM 600: Set up a plant structure by using Object Type window
1. A technical key, which is used on engineering drawings and for signal identifica-
tions. This is contained in the attribute name as identification of each object. If
this value is used as reference to an object, it is contained in an attribute name
87
Set up a substation for IEC 61850 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 ob-
jects. 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 seman-
tics of desc shall also be relative within an object hierarchy.
PCM 600 takes care for these two possibilities. The two possible designations naming are avail-
able 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 specifi-
cations 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 se-
lected 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 stan-
dard 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 Proper-
ties in the row Caption.
en06000029.vsd
88
Set up a substation for IEC 61850 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:
It should also be checked and notified when one of the user IEDs (most likely the client IEDs)
have additional rules for the length of each level etc. Be careful and make a general concept for
all partners in the project. See the standard IEC 61850–6 and chapter 2 "IEC 61850 station en-
gineering" for more details.
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
Set up a substation for IEC 61850 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.
en05000643.vsd
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
Set up a substation for IEC 61850 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
When the pre-configured IED versions are not delivered in a zip file. Skip this window by se-
lecting No PreConfig File. Check the availability of pre-configured IED versions in the CAP
531 template folder.
91
Set up a substation for IEC 61850 Chapter 7
Station configuration with PCM 600
en06000031.vsd
The vendor has to supply an ied.ICD or ied.SCD file for each IED.
en06000032.vsd
92
Set up a substation for IEC 61850 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 but-
ton menu.
Note
The actual version of PCM 600 does not support the integration of client IEDs in the plant struc-
ture nor in the communication structure.
This is actual only possible by adding the client ied.ICD file in the CCT and configure the com-
munication section in the CCT with the additional client IED. See chapter 6, section 3 "Im-
port/export ied.ICD files" how to do it.
93
Set up communication for IEC 61850 Chapter 7
Station configuration with PCM 600
The communication structure can be checked by selecting it in the Project Explorer beside the
Plant structure. By opening the tree structure it is visible that the OPC server of the PCM 600
itself is on top with the NETWORK below.
All bay IEDs configured in the Plant Structure must be shown and connected to the NET-
WORK. In the figure below also the client IEDs are presented after re-import the station.SCD
file from the CCT to PCM 600 for final IED 670 engineering.
en06000208.vsd
The Logical devices of an IED are listed when opening the IED. This is for information only
94
Set up communication for IEC 61850 Chapter 7
Station configuration with PCM 600
en06000209.vsd
95
Import/Export station.SCD files Chapter 7
Station configuration with PCM 600
Station
en06000025.vsd
96
Import/Export station.SCD files Chapter 7
Station configuration with PCM 600
en06000026.vsd
97
Import/Export station.SCD files 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 num-
ber of IEDs.
en06000027.vsd
98
About this chapter Chapter 8
Signal engineering with CCT
99
IEC 61850 Attribute Editor Chapter 8
Signal engineering with CCT
The structure and content of a Logical node is defined in IEC 61850–7–3 and IEC 61850–7–4.
It describes the data objects, the data attribute classes and the base types as mandatory or option-
al elements of a Logical node. The IED products define their Logical nodes based on this stan-
dards. But these Logical nodes are described as LN types, because these LN contain only the
used and available data objects etc. So each IED product will have its own set of used Logical
node types.
The SCL structure takes care of this in the Data Type Templates section where all used and
available Logical node types, their data object types and their data attribute types and when giv-
en their additional base types of type Enumerated are included. The reference to the LN types is
given in the IED section for each logical node by the LN type name as part of the Logical node
identification.
en06000045.vsd
Figure 65: CCT: IEC 61850 Attribute editor (viewer)
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
IEC 61850 Attribute Editor 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).
101
Data set engineering Chapter 8
Signal engineering with CCT
select FC
select LN
add DataSet
select DO
select DA
en06000043.vsd
Figure 66: CCT: Generating a DataSet
When the Data Set Engineering pane is selected you will get a pane which includes four list box-
es. One is for information only (Filtered Preview). The other three are needed to configure a
DataSet:
• Data Sets
- lists all available DataSets with their names located in that Logical node
102
Data set engineering Chapter 8
Signal engineering with CCT
Remark
Analyzing all defined data attributes defined in IEC 61850–7–3 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 in-
formation are handled by other IEC 61850 communication services and are not part of a report.
103
Data set engineering Chapter 8
Signal engineering with CCT
select DA only
DO with stVal; q; t
en06000048.vsd
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
104
Data set engineering 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.
These DataSets may be modified or extended in a project. The possibility to do it must be an-
nounced 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 ur-
gent was done by ABB experts and may be checked by the project
105
BRCB engineering Chapter 8
Signal engineering with CCT
3 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
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.
• add a new BRCB row to the list by clicking Add... Report Control in the bottom
area of the pane
106
BRCB engineering Chapter 8
Signal engineering with CCT
• give the BRCB a unique name according to the rules described in IEC 61850–7–2
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
• IEC 61850–6 clause 9.3.8 and listed in table 22, table 23 and table 24
• IEC 61850–7–2 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 con-
trol".
107
BRCB engineering Chapter 8
Signal engineering with CCT
BRCB attributes
23
en06000205.vsd
108
BRCB engineering Chapter 8
Signal engineering with CCT
109
BRCB engineering Chapter 8
Signal engineering with CCT
110
BRCB engineering Chapter 8
Signal engineering with CCT
111
BRCB engineering Chapter 8
Signal engineering with CCT
112
GoCB engineering Chapter 8
Signal engineering with CCT
4 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
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 informa-
tion 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 61850–7–2
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 cor-
responding 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
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: CCT: Project Navigator with selected Input of a GOOSE message
• IEC 61850–6 clause 9.3.10 and listed in table 22 for the additions in the IED sec-
tion
• IEC 61850–6 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 communi-
cation section
• IEC 61850–7–2 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 con-
trol".
115
GoCB engineering Chapter 8
Signal engineering with CCT
GoCB attributes
1
en06000206.vsd
116
GoCB engineering Chapter 8
Signal engineering with CCT
1 Client 6, clause 9.3.13, table The name of the IED from where the input comes
IED 30,1
2 Order Sequence order of all IEDs linked to the GOOSE message
117
GoCB engineering Chapter 8
Signal engineering with CCT
118
/
&
6
,
3
.
"##1PXFS5FDIOPMPHJFT"#
4VCTUBUJPO"VUPNBUJPO1SPEVDUT
4&7ÊTUFSÌT
4XFEFO
5FMFQIPOF
'BDTJNJMF
*OUFSOFUXXXBCCDPNTVCTUBUJPOBVUPNBUJPO
1SJOUFEPOSFDZDMFEBOEFDPMBCFMMFEQBQFSBU&MBOEFST/PWVN